Devicemaster General Troubleshooting - Pepperl+Fuchs ICDM-RX/TCP Manual

ICDM-RX/TCP (DeviceMaster) and ICRPC (RocketPort EXPRESS)
Windows Driver Installation
Issue
Windows Driver Verify that the DeviceMaster has installed using the Windows Driver Management
Management Console to confirm that the DeviceMaster displays. Install the device driver, if the
Console? DeviceMaster is not displayed.
Enable Enable the Verbose Event Log feature on the Device General and then reboot the
Verbose mode system.

7.3.2. DeviceMaster General Troubleshooting

This table illustrates some general troubleshooting tips.
General Condition
PWR or Status LED
flashing
PWR or Status LED not lit
Can ping the
Pepperl+Fuchs device,
but cannot open the ports
from a remote location.
(You must have previously
programmed the IP
address, subnet mask,
and IP gateway.)
Cannot ping the device
through Ethernet hub,
switch, or router
Cannot ping or connect to
the DeviceMaster
Indicates that boot program has not downloaded to the DeviceMaster.
1. If applicable, remove the NS-Link driver.
2. Make sure that you have downloaded the latest driver.
3. Install the driver and configure the DeviceMaster using the MAC address.
Make sure that you reboot the system. Refer to Device Driver Installation on
Page 17 for installation information.
Note: If the PWR or Status LED is still flashing, contact Technical Support.
Indicates that power has not been applied or there is a hardware failure. Contact
Technical Support.
The NS-Link driver uses Port 4606 (11FE h) to communicate with the
DeviceMaster.
When using a sniffer to track NS-Link packets, filtering for Port 4606 will easily
track the packet. The packet should also contain the MAC address of the
DeviceMaster and the originating PC so that it can be determined if the packet is
able to travel the full distance one way or not.
If the 4606 packet is found on one side of a firewall or router, using sniffer, and
not on the other side, then that port needs to be opened up to allow the 4606 to
pass.
This will most often be seen with firewalls, but is also seen in some routers.
Isolate the DeviceMaster from the network. Connect the DeviceMaster directly to
the NIC in the host system (see DeviceMaster Connectivity Requirements on
Page 72).
The DeviceMaster family default IP address is often not accessible due to the
subnet masking from another network unless 192.168 is used in the network.
In most cases, it will be necessary to program in an address that conforms to
your network.
If you do not use the NS-Link driver to program the IP address, you only have 10
seconds to disable the bootloader with Redboot to get into the setup utility.
See the ICDM-RX/TCP Installation and Configuration Manual Installation and
Configuration Guide for the Redboot method of programming an IP address.
Check
Explanation/Action
71