Comtrol DEVICE MASTER RTS - Page 27

Troubleshooting and Technical Support 27
Troubleshooting Checklist
• If using a driver for Microsoft systems, verify that you are addressing the port
correctly. In many applications, device names above COM9 require the prefix
\\.\ in order to be recognized. For example, to reference COM20, use
\\.\COM20 as the file or port name.
• Reset the power on the Comtrol device and watch the PWR or Status light
activity.
- If the device has a power switch, turn the device’s power switch off and on,
while watching the LED diagnostics.
- If the unit does not have a power switch, disconnect and reconnect the
power cord while watching the LED diagnostics.
• If using NS-Link for a Microsoft system, you can use one of the tools bundled
with the drivers:
- Device Advisor, which helps identify problems is a tab in the Device
window of the driver.
- Test Terminal program (wcom32.exe), which can be used to troubleshoot
communications on a port-by-port basis.
- Port Monitor program (portmon.exe), which checks for errors, modem
control, and status signals. In addition, it provides you with raw byte
input and output counts.
- Peer Tracer program (peer.exe), which traces driver events.
• If using NS-Link for Windows hosts, enable the Verbose Event Log feature
under the Setup Options tab and then reboot the system.
• Reboot the system and the Comtrol device.
• Remove and reinstall NS-Link.
• If you have a spare Comtrol device, try replacing the device.
Product Type PWR or Status LED Description
DeviceMaster RTS
1-Port Models
4/8/16 (2 Ethernet ports)
16/32RM
5 sec off, 3 flashes, 5
sec off, 3 flashes.
Redboot checksum failure.
5 sec off, 4 flashes, 5
sec off, 4 flashes.
Call Technical Support.
5 quick flashes
The default application is
starting up.
10 sec on, .1 sec off, 10
sec on .1 sec off.
The default application is
running.