I have 2 ProXR Ethernet Scan 16 devices (NCD copyright 2014) working for an Alertus Wall Panic Button. One works great, the other does not seem to transmit a signal. Even though I can go to the URL for it. Is there a firmware upgrade for this, or can I run diagnostics on this? Alertus recommends that I talk to you guys for advise. It has a Lantronix Ethernet port on it which seems to work just fine. Just does not activate when I press the panic button.
Hi,
Standard diagnostics would be to run Base Station from a computer on the same network as the Ethernet module and see if Base Station can find and control/monitor the unit. You will need to make sure that no other software is connecting to the Ethernet module on the board. You can find the Base Station software at Start - NCD.io
You will also need the Ethernet module to be connectable over a TCP socket as a server on port 2101.
Let me know if you have any questions.
Thanks Jacob! OK, I have the device and on a specific IP address. I can go to the URL of that IP and I can see that the connection tab Local Port is set at 2101. The Base Software gets a “Device Identification Failed”. When I click on the Device Identification Button, I get an error that says "Communications Error. Device did not respond as expected.
Is it possible that another software would have the socket open already?
The board only has a single socket and if another software is opening that socket and maintaining that connection it could cause this issue.
Outside of that it could be an issue with the processor on the board itself and the only resolution I could recommend would be an RMA for evaluation: Log In ‹ NCD.io — WordPress
Unfortunately we haven’t sold the Lantronix XPort modules for a number of years so if its an issue with the communication module the whole board would need replaced.
Hello Jacob, so the NCD software works fine with the “good” ProXR and does not work with the “bad” one. Same cable hook up, etc. I have also reseated the 3 IC chips on the board. The other piece of information I have is that the “bad” board has a solid “Ready” LED and the “Busy” LED flashes every 4 seconds. The “Good” board “Busy” LED does not flash at all. Do you have any idea what the flashing Busy LED might mean? I have been told by Alertus that the board is out of warranty, so I cannot RMA it with them.
The Busy LED flashing is indicating that something is communicating with it or attempting to communicate with it which could possibly tie up the socket.
You could try Base Station again, but change the port number used to something like 2102. You will need to manually enter the IP and Port number in Base Station as the automatic network device finder I believe defaults to port 2101. Most software won’t automatically find and detect the non-standard port number.
**Edit:
By change the port number I mean both through Base Station and on the Ethernet module itself.