Modbus RTU to TCP bridging

[christian.hegland@caverion.com]

Thanks Daniel!

I have tried this script, but as far as I can see, this script needs to map all modbus registers through knx before exposing them to modbus TCP again.
Wouldn't that make the original modbus addressing shift, so that I need to create new profiles on my receiving PLC?

So the first mapping defined in the list of registers, eg GA 1/3/67, would be exposed on Modbus TCP as register 0 and so on.

-- list of register mapping, starting from 0
registers = { '1/3/67' }

-- list of register data types, element count must match registers table
regdt = { dt.float32 }

---

I was looking for a solution were i could poll the modbus RTU devices by their actual modbus ID, and same register for each ID.

For instance:

ID: Register: Desc:
151 3019 Voltage A-B for slave #151
152 3019 Voltage A-B for slave #152
153 3019 Voltage A-B for slave #153

Is that possible?