Skip to content
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

[Modbus] Explaining data types #340

Open
egekorkan opened this issue Dec 6, 2023 · 2 comments
Open

[Modbus] Explaining data types #340

egekorkan opened this issue Dec 6, 2023 · 2 comments
Assignees
Labels
modbus related to modbus protocol binding

Comments

@egekorkan
Copy link
Contributor

We should explain the mapping of the xsd types to what Modbus libraries would understand, i.e. saying that xsd:int is signed integer 32-bit.

@egekorkan egekorkan added the modbus related to modbus protocol binding label Dec 6, 2023
@relu91 relu91 self-assigned this Jan 31, 2024
@Kaz040
Copy link

Kaz040 commented Mar 11, 2024

I looked into the payloadDataType and I think the list of the xsd types in the binding template should be edited. I think data types like xsd:decimal and xsd:integer should not be included because they both have no limit (-infinity to infinity) plus they are used to generate other built-in-types that are limited(see the image below).

image

Also, since a register in modbus is 16 bits long (2 bytes), is there is any modbus implementation that will use a byte datatype? The same thought goes for unsignedByte

Lastly, I think we should make provision for timestamp datatype. some implementation might use it.

@danielpeintner
Copy link
Contributor

FYI: the type hierarchy can be found here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
modbus related to modbus protocol binding
Projects
None yet
Development

No branches or pull requests

4 participants