Ns-Link Driver Troubleshooting - Pepperl+Fuchs ICDM-RX/TCP Manual

Devicemaster and rocketport express windows driver
Table of Contents

Advertisement

ICDM-RX/TCP (DeviceMaster) and ICRPC (RocketPort EXPRESS)
Windows Driver Installation
Device Status Message (Continued)
Uninitialized.

7.3.6. NS-Link Driver Troubleshooting

This table includes some tips related to NS-Link drivers for Windows.
NS-Link Condition
Need to program IP
address into the device.
Cannot open port
The Pepperl+Fuchs device
has a lower limitation of
network bandwidth
requirement of 64 Kbps.
The firmware has not uploaded to the DeviceMaster. If this
message is displayed in the History file, it often means that the
DeviceMaster is in the process of being rebooted.
Before programming an IP address it is critical that the DeviceMaster be
operational and passes the power on tests when configured for the MAC
address.
Note: If the DeviceMaster is NOT operational, do NOT attempt to program or
use an IP address with the DeviceMaster.
See Program the IPv4 Address (Network Information) on Page 12 for more
information.
1. Verify that MAC address in the NS-Link driver matches the address on the
DeviceMaster.
2. Verify that you are using the correct NS-Link driver. If necessary, remove
and reinstall a new driver.
3. Isolate the DeviceMaster from the network (see Page 71).
4. Check to see if another program or computer is active on this port.
At this speed the entire available bandwidth is required for the purpose of
uploading the firmware from the driver to the DeviceMaster. At lower speeds,
timing issues will prevent the firmware from being successfully installed to the
DeviceMaster, thus preventing the DeviceMaster from normal operation.
When using the DeviceMaster over a WAN link that is less than the
recommended 64 Kbps, a timing modification may be made that will allow
uploading of the firmware.
Load the driver locally to the DeviceMaster for the purpose of getting the
firmware installed. The PC on the other side of the slow link can then "share" the
port. The sharing may be exclusive as the firmware loader PC may not need to
access the ports.
Descriptions (Continued)
Explanation/Action
78

Advertisement

Table of Contents
loading

Table of Contents