Hi,

I'm building a 3D simulation with Godot. In the simulation there is 2 Modbus TCP devices that Godot exposes on localhost (127.0.0.1) on 2 different ports (5010 and 5040) and I want to control them using ProviewR.

With a build of ProviewR v5.7.1, my simulation works.

Yesterday I decided to use ProviewR 5.7.1 Ubuntu release package...
...and it does not work anymore

When running the simulation, libmodbus keeps returning "Connection reset by peer".

I have no idea what to do to debug this issue.

Any idea ?

GodotDemo source code
More context

Hi,

It's me again.

I have rebuild ProviewR version 5.7.1 and 5.7.0 but that not working either.

I have some Wireshark traces. It seems that ProviewR resets the connection every few packets and try again with an other port (old port + 2)

I have attached the trace. Sort by protocol and look at TCP packets

Those are non-standard ports for ModbusTCP - but if you see SOME complete two-way traffic at all, that would not seem to be the problem.

Is your simulation slow responding (and by the way - is it the slave or the master on ModubusTCP??)?

"Reset by peer" often means a blocked port or protocol.

My simulation is quick responding, access to value are asynchronous so as soon as a modbus request is received, a response is sent.

I running this configuration:
I only have one input for the sensor but I have

ModbusMaster
| ________> ModbusSlave (Sensor)
|______> ModbusModule
|________> Signals
Same layout for the "pusher"