Hi, I’m the Toradex AI Assistant.
I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.
Did you like my answer? 
Troubleshooting CERHOST V3.3 Connection Issues
Based on the Toradex documentation, here are several approaches to resolve the connection issue with your twelfth instrument:
Check Remote Display V3 Configuration
First, verify that the problematic instrument is properly configured for Remote Display V3 over Ethernet(1). The documentation indicates that you should:
-
Copy the correct files to the Colibri FlashDisk folder:
- Copy the folders
\AutoRun\ and \AutoCopy\ to the Colibri \FlashDisk\ folder(1)
-
Verify the correct executable is being used based on your WinCE version(1):
- For WEC2013: Use
CerDisp.exe from the WinCE2013 folder
- For WCE5, WCE6, or WEC7: Use
CerDisp.exe from the WinCE folder
Manual Connection Troubleshooting
Since automatic detection isn’t working, try establishing a manual connection(1):
- On the problematic instrument, manually start
cerdisp.exe and click the “Start” button
- On your PC, run
CerHost.exe and choose File → Connect
- If the Colibri module doesn’t appear in the device list, manually enter the instrument’s IP address and press OK(1)
Known Issue with Software Keyboard
The documentation mentions a specific issue with Remote Display V3 over Ethernet(1):
“We noticed that the Remote Display V3 (over Ethernet) loses connection as soon as the software keyboard (SIP) appears or disappears from the screen. This issue has been fixed in release 3.1 of the tool.”
Ensure you’re using Remote Display V3.1 or later to avoid this connection stability issue.
Ethernet Configuration Verification
Check the Ethernet controller configuration on the problematic instrument(2). For different Colibri modules, the registry keys vary:
- Colibri PXA270: Uses DM9000 controller with registry key
[HKLM\Comm\DM90001](2)
- Colibri PXA300/310/320: Uses AX88796 variants with different registry keys(2)
- Colibri T20/T30: Uses USB-attached AX88772B controller(2)
Multiple Ethernet Adapter Considerations
If your instruments have multiple Ethernet adapters, verify the debug interface configuration(3). The documentation shows that when multiple adapters are present, you may need to configure the registry to enable the second adapter for debugging(3):
[HKEY_LOCAL_MACHINE\Comm\TCPIP\Linkage]
"Bind"=multi_sz:"AX88772B2","AX8877B1" ; List all adapter instances
(3)
Alternative Shortcut Configuration
Try creating a specific shortcut for the problematic instrument using the format documented in the Shortcut article(4):
42#"\USB HD\CERDISP2.EXE" –h10.0.4.xx –c
(4)
Replace 10.0.4.xx with the specific IP address of your problematic instrument.
Since eleven instruments work correctly and only one fails with identical configuration, this suggests a device-specific issue rather than a network or PC configuration problem. Focus on verifying the Remote Display software version and manual connection methods on the problematic instrument.
Best regards, Toradex AI Assistant.
