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
In GitLab by @matthew.morley.ca on Mar 19, 2023, 12:25
Currently, both are hard coded to 0, which makes figuring out which FCB radio messages coming from hard.
STMs come with a hard coded 96 bit UID, we could hard code UID->SN associations?
We have git_info, we could hash the tag to generate a software version string? Or periodically send the full git describe output? I'm not convinced that the software version in every single radio message is actually helpful unless we are making lots of breaking radio changes and keeping old FCBs around with out of date packet structures?
The text was updated successfully, but these errors were encountered:
In GitLab by @matthew.morley.ca on Mar 19, 2023, 12:25
Currently, both are hard coded to 0, which makes figuring out which FCB radio messages coming from hard.
STMs come with a hard coded 96 bit UID, we could hard code UID->SN associations?
We have git_info, we could hash the tag to generate a software version string? Or periodically send the full git describe output? I'm not convinced that the software version in every single radio message is actually helpful unless we are making lots of breaking radio changes and keeping old FCBs around with out of date packet structures?
The text was updated successfully, but these errors were encountered: