Dimension Three Touch (D3T) Setup GUI Common Issues

Dimension Three Touch (D3T) Setup GUI Common Issues

  • Only one connection from the GUI to console is allowed at a time. It's best to install this software on only one machine so you don't have two GUIs fighting over the same socket.
  • If you see in the visibilities list ??idx: (number) instead of the name of the destinations, the problem is that the Blade ID and IP are missing from the Engines Tab. It looks like this when it’s wrong:

The other clue that you’re not connected to the engine is that none of the sources previously checked are selected in the list (because the GUI isn’t talking to any engine).

  • If you take a saved console config from one studio and restore it to another (you might think to do this to copy the visibilities from one studio to another if they share sources) keep in mind that it copies everything from all the tabs over, including the engine tab, so you must go change the Blade ID and IP before editing, lest you start saving visibilities and VDIPs to the wrong console.
    • Related Articles

    • Dimension Three (D3) vs. Dimension Three Touch (D3T)

      There are two versions of the Dimension Three: Dimenstion 3 (D3) Dimension 3 Touch (D3T) As the name implies, the D3T has a touchscreen. Also, the D3T uses a different operating system. Therefore they have different backend apps and setup programs. ...
    • LXE Setup GUI Doesn’t See Modules/Navigator Doesn’t See Blades

      If the LXE GUI doesn’t see the modules and/or Navigator doesn’t see the blades check the Windows Firewall. The WNIP network will be considered a “public” network by Windows, which has the most restrictive rules in Windows, and it’s blocking our ...
    • LXE Setup GUI Doesn’t See Modules/Navigator Doesn’t See Blades

      If the LXE GUI doesn’t see the modules and/or Navigator doesn’t see the blades check the Windows Firewall. The WNIP network will be considered a “public” network by Windows, which has the most restrictive rules in Windows, and it’s blocking our ...
    • Wide Orbit WheatNet-IP Logic Setup

      These instruction sets apply to WideOrbit Automation for Radio versions 2.x to 3.7.x. Newer versions are likely similar. WideOrbit can address SLIO’s on blades via the Wheatnet ACI. For this setup you will need WO automation for Radio Device Server ...
    • Wide Orbit WheatNet-IP Logic Setup

      These instruction sets apply to WideOrbit Automation for Radio versions 2.x to 3.7.x. Newer versions are likely similar. WideOrbit can address SLIO’s on blades via the Wheatnet ACI. For this setup you will need WO automation for Radio Device Server ...