Filter
Top Products
Troubleshooting
143
NI-3101-SIG Signature Series NetLinx Integrated Controller
Troubleshooting
This section describes the solutions to possible hardware/firmware issues that could arise during the common
operation of a NetLinx device.
Troubleshooting Information
Symptom Solution
My NI Controller can’t obtain a DHCP
Address.
In requesting a DHCP Address, the DHCP Server can take up to a few
minutes to provide the address to the on-board Master.
• Verify there is an active LAN connection attached to the rear of the
NI-Series Controller before beginning these procedures.
•Select Diagnostics > Network Address from the Main menu and
verify the System number.
• If the IP Address field is still empty, give the device a few minutes to
negotiate a DHCP Address and try again.
My NI Controller shows the same IP
Address after selecting DHCP Server
and clicking the GET IP Information
button.
In requesting a DHCP Address, the DHCP Server can take up to a few
minutes to provide the address to the on-board Master.
When using a controller that has previously been used, there may be
an instance where the IP Address was set as a fixed IP. In this case,
the address would need to be released so a new user could use a
DHCP server provided address.
• Access the HyperTerminal application and try to communicate to the
controller via the COM port.
• Type echo on and press ENTER to send the information to the unit.
• Type get ip to display the actual IP Address used by the unit.
• Release the static/fixed IP Addresses.
• Recycle power to the device and retry obtaining a DHCP address
through NetLinx Studio.
My NI Controller still can’t obtain a
DHCP Address even after
completing the above
troubleshooting tip.
If the NI Controller is not connected directly to an open LAN wall con-
nector, but is rather connected to a LAN Hub:
• Contact Technical Support for a resolution to issues with this type
of connection scenario.
I can’t detect the NI Controller and
my Status LED is blinking
irregularly.
The on-board Master is trying to establish communication.
• Wait a few moments and retry establishing communication using the
latest NetLinx Studio.
• If the problem persists, cycle power to the unit and repeat the above
procedure. Another solution is to attempt communication via another
method (Configuration Port or IP).
• Refer to the Configuration and Firmware Update section on page 17
for more information.
NetLinx Studio only detects one of
my connected Masters.
Each Master is give a Device Address of 00000.
• Only one Master can be assigned to a particular System number. If
you want to work with multiple Masters, open different instances of
NetLinx Studio and assign each Master its own System value.
• Example: A site has an NXC-ME260/64 and an NI-3101-SIG. In order
to work with both units. The ME260/64 can be assigned System #1
and the NI-3101-SIG can then be assigned System #2 using two
open sessions of NetLinx Studio.