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

High level API should support custom endian for each address #81

Closed
aldas opened this issue May 4, 2021 · 1 comment · Fixed by #83
Closed

High level API should support custom endian for each address #81

aldas opened this issue May 4, 2021 · 1 comment · Fixed by #83

Comments

@aldas
Copy link
Owner

aldas commented May 4, 2021

See discussion #80

I'd prefer the high-level API for my system, but I need another endian (BIG_ENDIAN_LOW_WORD_FIRST)). Is ist possible to change endian directly for each address. Maybe something like this from your example
->int16(657, 'battery3_voltage_wo','BIG_ENDIAN_LOW_WORD_FIRST')
or is it a must to use the low-level solution for another endian?

@gutschein
Copy link

gutschein commented May 4, 2021

Would be nice, but as the change of the default endian was already very helpfull. It may deserve a line in the help in chapter "Endianness":
"Changing the default endian with adding a line at the beginning: Endian::$defaultEndian = Endian::<needed_endian>;"

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

Successfully merging a pull request may close this issue.

2 participants