Ni 3100 & Ni 3101 SIG locks up, status led off

John Paul

I have a scenaro where my master ( 3100 and 3101 SIG series) locks up and wont work until i do a hard reboot. I am able to ping the controller and telnet to it. But it wont connect via software and the touch panels cant connect to it. The master firmware is 3.60.353 and device firmware is 1.30.8 for the masters. I have telneted to the device and send commands for the logs. The telnet also locks up so i had to do multiple telnet sessions. I have pasted them all into a single txt file. Requesting any help on how to proceed.

Once i do a reboot, the master works fine. The background on the site, there are 8 masters connected in route mode direct mode. Every day any one or two of these masters locks up with the status led in a off position.

ericmedley

A couple things to check.

First, how is your master-to-master comm set up? Make sure you're only putting the main master's URL in the sub masters and not also putting the sub master's URLs in the main.

What you're describing (failing any programming issues) sounds like a master getting flooded with error messages. While in telnet type in a MSG ON ALL command and see what runtime errors are occurring.

If your M2M setup is incorrect, it will cause these kinds of errors.

John Paul

I have put all the masters under route mode direct, so Master #1 would have a URL list to masters 2-7.

Then master 2 would URL to 3-7

And so on. So it would look like this in each master’s URL list

(ALL URL in Direct mode)

#1 #2 #3 #4 #5 #6 #7 #8

2 3 4 5 6 7 8

3 4 5 6 7 8

4 5 6 7 8

5 6 7 8

6 7 8

7 8

8

No URL list in #8

John Paul

I had done the following changes to the controller recently. I had send these commands via telnet to the different masters.
Set udp bc rate 0
zeroconf disable

Andrew G Welker

John Paul wrote: »

I have put all the masters under route mode direct, so Master #1 would have a URL list to masters 2-7.

Then master 2 would URL to 3-7

And so on. So it would look like this in each master’s URL list

(ALL URL in Direct mode)

#1 #2 #3 #4 #5 #6 #7 #8

2 3 4 5 6 7 8

3 4 5 6 7 8

4 5 6 7 8

5 6 7 8

6 7 8

7 8

8

No URL list in #8

That makes sense, but have you gone through and verified that all masters are still in the route mode direct setting? If one of them happened to reboot itself or get reset somehow then that could cause the issues you are having, as it would try to connect through multiple routes to the masters in its URL list.

ETA: Also, it would be much easier and much more foolproof to leave the masters in the default setting and either put the URL of the 8th master in all of the other masters or the URLS of the other 7 masters in the 8th master. This will still allow them all to communicate, but will probably help to eliminate some issues.

John Paul

i checked on the route mode direct setting on all the masters and its set to route mode. But system 3 to 5 are showing a system 9 also as dead. Now i checked the url listing in these systems and there is no system 9 fed into the url listing. Here is the telnet screen copy


Welcome to NetLinx v3.60.453 Copyright AMX LLC 2010
>show route mode
Show Route Data

---

Route Data: Direct Connect Only Mode

System Route Metric PhyAddress

---

1 1 1 TCP Socket=37 IP=10.10.3.16 Index=5
2 2 1 TCP Socket=32 IP=10.10.3.15 Index=6
-> 3 3 0 Axlink
4 4 1 TCP Socket=23 IP=10.10.3.12 Index=0
5 5 1 TCP Socket=28 IP=10.10.3.11 Index=2
6 6 1 TCP Socket=30 IP=10.10.3.13 Index=1
7 7 1 TCP Socket=34 IP=10.10.3.14 Index=3
8 8 1 TCP Socket=29 IP=10.10.3.18 Index=4
9 9 Dead None
>get ethernet mode
Ethernet mode is fixed: Speed = 100 Duplex = full.