Comtrol DM AIR - Manual (Page 67)

Troubleshooting and Technical Support DeviceMaster AIR User Guide: 2000365 Rev. C - 67
Troubleshooting Checklist
• 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.
• Verify that the hardware MAC address in NS-Link matches the address on the
Comtrol device.
• Verify that the network IP address, subnet mask, and gateway is correct and
appropriate for the network. If IP addressing is being used, the system should
be able to ping the Comtrol device.
• Verify that the IP address programmed into the Comtrol device matches the
unique reserved IP configured address assigned by the system administrator.
• If using DHCP, the host system needs to provide the subnet mask and
gateway.
• 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.
• If using NS-Link for a Microsoft system, you can use one of the Comtrol tools,
which are discussed in the NS-Link User Guide.
- Device Advisor, which helps identify problems is a tab in the Advisor
window of the driver.
- Test Terminal program, which can be used to troubleshoot
communications on a port-by-port basis.
- Port Monitor program, which checks for errors, modem control, and status
signals. In addition, it provides you with raw byte input and output
counts.
- Peer Tracer program, which traces driver events.
• If using NS-Link for Windows hosts, enable the Verbose Event Log feature
under the 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.
PWR or Status LED Description
5 sec. off, 3 flashes, 5 sec. off, 3 flashes ... Redboot checksum failure.
5 sec. off, 4 flashes, 5 sec. off, 4 flashes ... SREC load failure.
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.