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
I would also like to be able to use the meshtastic radio part independent of the rest of the meshtastic firmware.
If we find enough people interested in this, maybe we could think about an coordinated effort to untagle the firmware and separate the MeshService and RadioInterface? Or even extract / rewrite parts of that radio code as a library to serve as a stable future foundation for expansion of the Meshtastic ecosystem (both for the device firmware as well as other use cases)
The current firmware shows quite a lot of signs of organic growth over the past years and would probably benefit from bit of untangling.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
This is a continuation of https://meshtastic.discourse.group/t/how-to-use-meshtastic-as-a-library/8294
I would also like to be able to use the meshtastic radio part independent of the rest of the meshtastic firmware.
If we find enough people interested in this, maybe we could think about an coordinated effort to untagle the firmware and separate the MeshService and RadioInterface? Or even extract / rewrite parts of that radio code as a library to serve as a stable future foundation for expansion of the Meshtastic ecosystem (both for the device firmware as well as other use cases)
The current firmware shows quite a lot of signs of organic growth over the past years and would probably benefit from bit of untangling.
Beta Was this translation helpful? Give feedback.
All reactions