Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website Mango 5 Documentation Website

L

Topics created by loen

L

TcpSlave bug, zombie connections

Modbus4J general discussion
• • • loen

5

0
Votes

5
Posts

2.8k
Views

M

Changes have been checked into the SF CVS repo.
L

Possible bug on Master RTU over TCP ?

Modbus4J general discussion
• • • loen

8

0
Votes

8
Posts

8.9k
Views

L

I'm not sure too.

But notice that the test with tcp to tcp, with rtu encapsulation enabled, has the same problem even if there is no real serial device, and only tcp is involed (see the 3rd post in the thread):

run:
Master TCP started (50ms, tcp rtu -> tcp rtu) ** TCP, both master and slave encapsulated, no serial device, still has the problem

May it me something related to this: http://mango.serotoninsoftware.com/forum/posts/list/532.page ?

The only solution we can figure out (to be tested yet), is to close the TpcMaster on receiving a timeout exception, and create a new TcpMaster.
This involves issuing only single commands and not using batch.

Regards