About AlexS

We are actually working on a proof of concept. This is one solution but does not need to be the preferred/best solution. There are also other ways to get the data. E.g. get some arrays of 16bit register values with this Modbus TCP App and then write an own snap app which converts the data and stores it into the datalayer... Generally, this would be an useful improvement for the Modbus TCP App. It would be nice to know if this will be done in the future and when it will be done circa. ... View more

The Bytes within a word are transmitted as expected. That means, 16 bit values are received correctly by the Modbus TCP App. But when I want to receive a DWORD or FLOAT the words have to be swapped. Example: server has a DWORD 0xDEADBEEF which is at address 0x3000 then the LowWord (0xBEEF) will be at address 0x3000 and the HighWord (0xDEAD) will be at address 3001. If I tell the client at Modbus TCP App it has to read an UINT32 from address 3000, I get a value of 0xBEEFDEAD. My communication partner has a fix little-endian wordorder when used as a server. By using it as a client everything (bytes, words, ...) can be swapped as needed to adapt to different systems. To my knowledge there are many systems who use different byte-/wordorders to transmit their data. ... View more