You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 30, 2025. It is now read-only.
One thing that I see as common denominator is the mapping of specific registers (especially outside of sunspec) to a) their physical meaning and b) the necessary en/decoding. If you which we could join forces and design some kind of meta representation that would allow to create the likes of https://github.com/volkszaehler/mbmd/tree/master/meters/rs485 in a generative way.
The text was updated successfully, but these errors were encountered:
I realized I never responded to your excellent suggestion from so many years ago.
Sorry about that.
I have read it and it did start me thinking; can this be done?
Over the years I have been working on something that may interest you in this light: https://modbus.basjes.nl
This includes an open standard (to be clear, it's my standard) way of describing the mapping schema for a modbus device and also includes a (first version) of a code generator that is capable of generating Java and Kotlin code from that.
I'm archiving this project on favor of that new one.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Continued from sunspec/models#44:
I have for some time been developing https://github.com/volkszaehler/mbmd - different language, different goals.
One thing that I see as common denominator is the mapping of specific registers (especially outside of sunspec) to a) their physical meaning and b) the necessary en/decoding. If you which we could join forces and design some kind of meta representation that would allow to create the likes of https://github.com/volkszaehler/mbmd/tree/master/meters/rs485 in a generative way.
The text was updated successfully, but these errors were encountered: