Ni4100 keeps shutting down
letMeIn
Posts: 15
in AMX Hardware
Hi. Have a small problem. Our ni4100 keeps shutting down on me after few min of usage. The status light goes off, but the network light is on. I have to unplug the controller for at least 1 minute to get it back working for the next few minutes..
0
Comments
To check the hardware, set PROGRAM DipSwitch, set switch 1 to ON and reboot. Master now only launches firmware but not your code. If the master still fails after some minutes, it may be a hardware issue.
But imho this seems to be more a software issue. Maybe you run into an endless WHILE loop or into an endless loops of Functions (Function1 calls Function2, 2 calls 1, etc). Will the lockup also happen if you are disconecting your RS232 devices?
I run Netlinx Diagnostics program v1.0 and enabled Internal System Diagnostics. The only error message that continuously appears is " Error sending UDP packet (IP=EFFFFAFB) (Error=65).
Another thing that I noticed, not sure if its related or not.
I updated the Master firmware ( to v3_21_354) and with no problem and then tried upgrading Netlinx Controller ( to v1_13_6) and once the file is uploaded it just hangs there. Progress bar is complete, and lower just says "file 1 of 1 please wait". Send button is disabled. Status doesn't change at all. However when I cancel and reboot the system after 20min, when I go to Network tree and highlight Netlinx controller, it shows the software is upto date 1.13.6.
this thing is driving me crazy lol. Tried calling AMx tech support, but I only get the voiceboxes dohhh
Srry for being a noob, but Im new to the AMX , and those problems are driving me crazy. I just want to get it fixed asap and continue programming ..lol
thx for all your help
The message in most cases is created by the UDP ping a NetLinx master sends by default to find panels which may run in URL mode LISTEN, if there is no gateway adress or adress is set 0.0.0.0.
To fix that UDP thing, please check if your master has set a gateway adress. An empty gateway or a gateway 0.0.0.0 are not allowed in IP environment, unfortunately by accident it is possible to do that by terminal or Studio. This should not lock up the master to "dead", but may have effects to network handling. Set a gateway IP fitting to your subnet, but it is not required to have a physical gateway. If I have an isolated AMX network, I use the master's IP or the IP of a WAP as gateway.
hmm
kk changed the gateway, rebooted the system will see what happens
Question, when the system locks up does the AxLink indicator light on the back go off? Also if you have any AxLink or ICSNet devices attached or control cards in the slots disconnect them for now and see if that makes a difference.