ENET 9163 stops communicating

[maherhome]

It looks like a combination of 1) updating the firmware to 1.1.0f2 and 2) increasing the timeout in the registry has fixed the problem.  We had two devices, only one with the firmware upgrade, and MAX (on machine with registry tweak) could only keep in touch with the upgraded device.

Thanks for your help!

Steve 

[maherhome]

Hmm.. it happened again to our 9481 (housed in an ENET-9163), which had the firmware upgrade.

Any other ideas? 

[Brandon_B]

Hello Steve,

So you've gone through all the previous troubleshooting steps (increase timeout, firmware etc.) for the 9481 that we used for the 9163 and are still experiencing problems?  Are you receiving the same timeout error (50405) as before, and has your code changed at all?

Regards,

[maherhome]

Both devices are connected to the same machine so the timeout is used for both.  And yes, I upgraded the firmware on both.

MAX produces the timeout (as well as my software).  (So since MAX produces the problem consider the answer to whether the client sw has changed as "no")

Steve 

[hegb_85]

Hello, I'm having this same problem with a ENET-9472 and ENET-9421.

I also have a serial enet and that one never hangs. The difference is that i'm making a constant polling of the virtual COM in order to obtain a bar code from it.

The DI/DO enets are idle until the barcode "wakes up" the loop where are located the tasks for the DIOs functions.

I've tried to increase the timeout (right now i have 20 seconds) but the error is still present. I didn't make the firmware upgrade because it seems not to solve the problem...

Any other suggestion?

[maherhome]

It turned out that my problem was caused by our IT guys doing network vulnerability scans.  It's not uncommon for these scans to knock over devices like printers.

Steve

[hegb_85]

I'm not sure that vulns scans are hanging the ENET's i'll check with the IT guys if they are doing something...

with the serial ENETs i never have problems it's just the DO/DI devices... any other idea?

[maherhome]

---

ethan85 wrote:

with the serial ENETs i never have problems it's just the DO/DI devices... any other idea?

---

I have no ideas beyond the firmware upgrade and timeout increase mentioned in this topic.  Can you still ping and telnet to the devices when you have problems.

(Oh, and of course the serial ENET's aren't susceptible to the net scans)

[hegb_85]

Yes,

actually i only stop/run the program again and they start working normally

[hegb_85]

Does the ENET uses TCP packets that the IT group could block due to security restrictions?

Actually if I open MAX and I click over a ENET it popups a timeout. the options never get enabled so i can't change IP or something like that. any ideas on this?