Problem
When attempting to connect to an Ensemble or Soloist controller the following error message appears:
Solution
First, ensure that the Ensemble/Soloist controller is recognized by the software. Open Configuration Manager and navigate to Controller > Connection Settings.
If the controller DOES NOT appear on the left of the Connection Settings window or is greyed out (indicating a disconnected controller), the Ensemble/Soloist software is not recognizing the controller. The controller should appear in the Connection Settings window regardless of its network settings (IP address, Subnet Mask, etc.)
- Is the controller powered on? Check the green PWR LED or otherwise ensure that the controller is receiving power.
- Power cycle the controller.
If connecting via USB...
- Reinstall the USB drivers for Ensemble/Soloist.
- For the Ensemble, the USB drivers are located at C:\Program Files (x86)\Aerotech\Ensemble\Drivers and Drivers64 (32 and 64-bit systems respectively).
For the Soloist, the USB drivers are located at C:\Program Files (x86)\Aerotech\Soloist\Drivers and Drivers64 (32 and 64-bit systems respectively). - Run the UsbInstall.exe application inside the Drivers/Drivers64 folder to reinstall the USB drivers. A black Command Box type window will appear momentarily. This should install the driver. You may have to disconnect the USB cable and reconnect it for the driver to be applied.
- Try connecting via Ethernet if possible.
If connecting via Ethernet...
- Ensure that any Ensemble/Soloist applications are allowed through the Windows firewall or any external security software. The Ensemble and Soloist controllers use UDP communication on ports 67, 1577, and 32835.
- Use a shielded Ethernet cable.
- Use a RJ-45 crossover cable if going directly from the controller to the PC.
- Use a RJ-45 standard cable if going through a hub or switch.
- For the purposes of troubleshooting, connect directly from the PC to the Ensemble/Soloist controller if possible.
- Try a different Ethernet port on the PC. If you are using a dedicated Ethernet card, try a port on the motherboard.
- Try connecting the controller to a different PC.
- Try connecting via USB if possible.
If the controller DOES appear on the left of the Connection Settings window
- Make sure that the check box next to the controller is checked. This "maps" the controller.
Ensure that the controller's Network settings are correct. Using a static IP address is recommended.
To configure static IP addresses...
If the controller connects successfully from Configuration Manager but DOES NOT connect from .NET, C, C#, C++, etc.
- Ensure that any custom applications are allowed through the Windows firewall or any external security software. The firewall/security software may need to be temporarily disabled as a general troubleshooting step to determine if a more specific rule or exception must be created.
Related articles
-
Page:
-
Page:
-
Page:
-
Page:
-
Page: