Now I'm getting a bizzarre 12000 character limit message
on comments which are 11500 characters short of that limit
OK, I observed some late-stage "developments"
I switched the 485 connection polarity. (always a crap shoot whether A is - and B is + or reverse)
I configured RS485: as Over TCP Master
![](src)
I am getting this traffic on the 485 wires as reported by ModbusSlave:
Rx:000229-00 23 00 00 00 06 02 03 1B 5D 00 02
Rx:000230-00 24 00 00 00 06 02 03 1B 5E 00 02
Rx:000231-00 25 00 00 00 06 02 03 03 E8 00 02
For some reason ModbusSlave is not replying to the queries
I tried RawMode on/off.
Because I am using non-standard port 503 for the RTU traffic,
I am not seeing any of the other TCP traffic on the 485
So it seems it is semi sort of almost working.
I'll connect the actual device and see if it responds
and figure out ModbusSlave's brain damage later...
I notice that I can do the Test Configuration on the ModTCP connections and get data immediately.
I would prefer to change the "internal" ID to 11 and let the RTU devices use ID 1 but there seems to
be some mystery dependency on ID1 for the other modbus stuff to keep working.
If I can't resolve it I'll just cave and change the 485 device ID to 11 or 2