Skip to content

Can not use client.convert_from_registers() #2646

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

Closed
Edgar-qiqi opened this issue Apr 22, 2025 · 3 comments
Closed

Can not use client.convert_from_registers() #2646

Edgar-qiqi opened this issue Apr 22, 2025 · 3 comments

Comments

@Edgar-qiqi
Copy link

After installing pymodbus version 3.9.2 via pip and importing from pymodbus import payload, client, the method client.convert_from_registers() remains inaccessible. Additionally, despite documentation stating that pymodbus.logging:BinaryPayloadDecoder was deprecated post-3.9.0, it persists in version 3.9.2. Furthermore, the removal of client.convert_from_registers() conflicts with earlier API specifications. This indicates potential inconsistencies between versioning claims, API documentation, and actual implementation in the 3.9.x release branch.

Image

@Edgar-qiqi
Copy link
Author

Edgar-qiqi commented Apr 22, 2025

Image

Image

@janiversen
Copy link
Collaborator

janiversen commented Apr 22, 2025

We postponed the removal of payload, as you can see in our roadmap, and honestly you are the first to complain about that.

You do not share your code, so I cannot tell you why your app cannot find convert_from_registers. But I can tell you that if convert_from_registers was gone a lot of the test harness would fail (including a larger number of production systems).

Did you follow our examples ??

you write "importing from pymodbus import payload, client", I assume you mean pymodbus.client, but that do not have convert_from_registers, that is part of the client classes. I think you need to look at the examples or the documentation.

@janiversen
Copy link
Collaborator

Closing as this is not a bug in pymodbus, but a wrong usage.

@janiversen janiversen closed this as not planned Won't fix, can't repro, duplicate, stale Apr 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants