@stensma What version of Java are you using? Oracle or OpenJDK?

I emailed you the fix I gave in the other thread. It is probably the same issue.

This issue has happened again, and the same folder caused the problem.

ASCII File Reader has been off for a long time, so that did not prevent the issue from re-occurring.

edit: This is happening on Mango v3, but not on Mango v1 or on an Ubuntu install.

The MangoEs has been running now for a few days with the latest sw upgrade, and I still got timeout alarms this is reported in another already existing thread.
All ports active now seem to work fine.
/Per

Model and so...:
Actaris CF ECHO II Qp 2.5
0_1471819501872_CFECHO-II-15mm-50mm.pdf

// Per

For a V3 MangoES, the RS485 and ttymUSB ports are symlinks based on the device port, so you can rely on that name being given to the device in a particular port. A full disk can definitely prevent many things from functioning... it doesn't even have enough memory for the TAB button to function on the command line!

Sounds to me like you have two devices that are not compatible to be on the same network.

There are two types of modbus reads for holding registers. One is where Mango requests a single register and the other is where Mango requests multiple registers. For 4 byte registers it's normal for the device to require the multiple register read so that makes sense. You could try changing your Max Register read to 2 which should be ok for your device with 4 byte registers but your other device may not like this so you might be forced to create two separate networks for each type of device.

Doing the update as we speak!

:-)