Devicemaster Troubleshooting; Devicemaster Checklist - Pepperl+Fuchs ICDM-RX/TCP Manual

ICDM-RX/TCP (DeviceMaster) and ICRPC (RocketPort EXPRESS)
Windows Driver Installation

7.3. DeviceMaster Troubleshooting

Most customer problems reported to Pepperl+Fuchs Technical Support are eventually traced to cabling or
network problems.
Reboot the system and reset the power on the DeviceMaster, watch the PWR or Status light activity. See
DeviceMaster LEDs on Page 72 for information about the diagnostic LEDs.
• If the DeviceMaster has a power switch, turn the power switch off and on.
• If the DeviceMaster does not have a power switch, disconnect and reconnect the power cord.
5 sec off, 3 flashes, 5 sec off, 3 flashes ...
5 sec off, 4 flashes, 5 sec off, 4 flashes ...
5 quick flashes
10 sec on, .1 sec off, 10 sec on .1 sec off ...

7.3.1. DeviceMaster Checklist

The following table may help you diagnose the problem. If you have a spare, you can replacing it to see if that
resolves the issue.
Issue
Verify that you are using the correct types of cables on the correct connectors and that all
Cabling? cables are connected securely using the ICDM-RX/TCP Installation and Configuration
Manual.
Correct MAC Verify that the hardware MAC address in NS-Link matches the address on the
address? DeviceMaster label. You can also use PortVision DX to verify the MAC and IP addresses.
• Isolate the DeviceMaster from the network by connecting the DeviceMaster directly to
a NIC in a host system.
• See DeviceMaster Connectivity Requirements on Page 72 for network cabling
information.
Network?
• Reduce network traffic by installing a second NIC in the host and connect directly to
the DeviceMaster.
• Verify that the Ethernet hub, switch, or router and any other network devices between
the system and the DeviceMaster are powered up and operating.
• Verify that the network IP address is correct. If IP addressing is being used, the
system should be able to ping the DeviceMaster.
Correct IP
address?
• Verify that the IP address programmed into the DeviceMaster matches the unique
reserved IP configured address assigned by the system administrator.
If using the NS-Link device driver with an in-house application, verify that you are
Correct port addressing the port correctly. In many applications, device names above COM9 require
addressing? the prefix \\.\ in order to be recognized. For example, to reference COM20, use \\.\COM20
as the file or port name.
Is this the
See Checking the Device Driver Version on Page 23.
Latest Driver?
Test the Port or
Install PortVision DX (Page 9) and use Test Terminal (Page 81).
Ports?
PWR or Status LED Description
Redboot checksum failure.
SREC load failure.
The default application is starting up.
The default application is running.
Check
70