We've recently tried to use the DTM Browser to communicate with a ModbusTCP device which has data available for reading on register 30001 upward, and data for writing to at 40001 and upward. I would have expected this to be a common situation, where the DTM Browser Generic ModbusTCP Device would be suitable, however on investigation, the ModbusTCP DTM Browser Generic Device is only able to access 40001 Holding Registers.
Has anyone come across the same issue?
Was there a workaround found (which didn't involve the use of DATA_EXCH / READ_VAR)?
Solved! Go to Solution.
As far as I know IO-scanning (DTM browser) only allows for reading/writing 4XXXX (%MWxxx) registers, meaning only the Modbus function codes 3, 16 and 23 are supported.
Other Modbus function codes, reading/writing 0xxxx, 1xxxx and 3xxxx are supported by function blocks only.
Discuss challenges and get support in energy and automation with 30,000+ experts and peers.
Over 10,000+ support articles are available to help you find answers to your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!