-
Notifications
You must be signed in to change notification settings - Fork 401
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request]: Reading blocks of registers #743
Comments
Oh gee ... I think I must have completely dropped the ball on this ... looking at the date, I guess this was just the time everything at my last job wen't totally bananas ... sorry for not following up on this. In the last few days I have worked a lot on the modbus drivers and they should be in quite a different state to when you opened this issue ... could you confim it's still an issue? |
For me this is not seen as a bug in your library but as a peculiar response of a real life system. |
Also; I realized a while ago that the only way any library can reliable read this device is when this library has a full schema of the device at hand. Only by following the constraints imposed by this schema can the library do the modbus calls that result in correct data. Note that the mentioned SunSpec has an even harder schema definition. So to get the value of the field I have been experimenting for a few months now on how to get to a form of schema definition that allows for all of these variants. I'm still working on that. So please just treat this as an FYI around the fact that some devices show unexpected behavior if you try to read valid registers in a way that does not meet their schema. |
@chrisdutz This was the mail thread before I put this up. https://lists.apache.org/thread/pyzrwvv5gbrj1bgyx8hyr8k62rzywys8 |
Just to be on the safe side ... I'm a bit unsure as to what needs to be done in this issue ... is this still valid? |
From my perspective this is something I want. I have been working (as a side project) to write the code needed to make this happen. What needs to be done is a lot. Right now I already have a partial prototype that works on my machine. So I propose this issue is closed and I'll ping you when I have something that is good enough to show you. |
What would you like to happen?
As requested by @chrisdutz a wireshark dump when requesting a set of correctly and incorrectly alligned sets of modbus registers.
Notes about this trace:
modbus-tcp:tcp://127.0.0.1:1502?unit-identifier=126
In sequence in a single request I retrieve it:
The console output related to this trace:
Programming Languages
Protocols
The text was updated successfully, but these errors were encountered: