Christofer Dutz

OK ... odd that I have no issues reading on my devices, but will have a look tomorrow afternoon (when I have my 4h of PLC4X for this week)

And thanks for submitting a PR ... that's really highly appreciated ;-)

Should be closed now after merging the corresponding PR:

As one of the issues you referenced is closed as "works now" could you please re-test if the problem still exists?

The main problem here is that modbus doesn't have any form of "length indicator" in the protocol. One option would be to call the parse method in the ByteLengthEstimator in...

I've just pushed an update that should make Modbus ASCII and RTU a bit more stable in situations as you describe. Please give the SNAPSHOT a try as soon as...

Reading this issue again, I do think that this issue should be resolved by the addition of the ByteLengthEstimator that tries to parse the message first and uses the size...

Is there a particular reason for setting the option to false? I mean ... yes: The resolution of symbolic addresses should in that case still work asynchronously, but the browsing...

The size should not matter ... might be something else going wrong. A wireshark capture could help, but if you do, I should make you aware that it would contain...

The problem is, that I've found out how to load a symbol, not however hot to load one datatype definition of only one symbol. So currently I would not disable...