ENET 9163 stops communicating

[maherhome]

Hi,

After some time (days?) our ENET-9219 (housed in a ENET-9163) is no longer seen by MAX. I get an Error -50803 from MAX.  HOWEVER, the device can be pinged and I can connect to TCP port 31415 (and 80) using telnet.  We have to power-cycle the device in order for MAX to see it again.

Lights on device look fine.  Firmware version is  1.0.0f.  I'm not sure how out of date that is; I can't seem to find firmware info on ni.com.

Is there some sort of sleep mode it goes into??

Thanks!

Steve

[Brandon_B]

Hello Steve,

Thanks for using NI forums.  Is your 9163 connected to your network or to the computer directly, and are you using a static IP address?  Also, are you communicating with the device throughout this time, or is it just sitting idle?

Regards, 

[maherhome]

 The 9163 is on the network, has a static IP, and is just sitting idle.  We will eventually have it in a hard-to-reach location and need it to stay awake.   

[Brandon_B]

Some devices do have a low power mode but I'm not sure if that can cause the device to lose communication.  Here is a useful KnowledgeBase for troubleshooting the ENET-9163.  Go through it and see if it helps.  In the meantime, I will do some more research on the low-power mode.

Regards,

[maherhome]

Remember, I can still "connect" over the TCP port using telnet, so the network hardware, TCP stack, etc. is still active.

Hmm, the KnowledgeBase link is broken .. 

[Doug_L._Bear]

I believe this is the KnowledgeBase Brandon was referring to:

http://digital.ni.com/public.nsf/allkb/85F0E0316EFBA819862575A2006B8D63?OpenDocument 

In regards to upgrading firmware, please see the marked solution of the following discussion forum:

https://forums.ni.com/t5/LabVIEW/WLS-9163-fails-to-reconnect-in-wireless-mode-after-reboot-in-a/m-p/...

Does your operating area have any sort of interference that could be breaking the signal, so the device still appears connected but is not transmitting proper information for the device to be visible in MAX?

http://digital.ni.com/public.nsf/allkb/D4C24AE4BB62BFA7862574F90072A4B6?OpenDocument 

[maherhome]

The KnowledgeBase had nothing relevant.  I've upgraded the firmware to 1.1.0f2 but still have the same problem - it just "hung" again today.  Again, I can ping the device, connect when telnetting to ports 31415 and 80, but MAX cannot connect to it and my software (to create and run a task) receives the following error:

No transfer is in progress because the transfer was aborted by the client. The operation could not be completed as specified.
Task Name: AnalogInputTask

Status Code: -50405

(I know this error is in the KnowledgeBase article, but again, I DO have successful TCP/IP (and ICMP) communciation with the device)

If I power cycle the device, MAX happily sees the device and my software successfully starts a running task.

Steve

NASA Goddard 

[Brandon_B]

Hello Steve,

I searched the error you were receiving and I found this KnowledgeBase article.  Try adjusting the timeout rate and let me know if that works for you.  I will continue to research some other solutions as well.

Regards,

[maherhome]

Brandon,

The link doesn't work for me ...  

Steve 

[Brandon_B]

I apologize.  Try this:

http://digital.ni.com/public.nsf/allkb/ACDC4A9DDB0FEA12862574F7006DC1C6?OpenDocument 

If this still doesn't work you can go to ni.com and search for "error 50405".  It will be the first article that comes up titled "Error 50405:  Connection Timed Out With a WLS/ENET-9163".

Regards,