Add new port number for airborne application(s) #5281
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
|
|
|
You need to make a PR to protobufs, portnums.pb.h is auto generated. |
|
Thank you, I will make the changes, and push them. |
|
I have done the hopefully correct now change in the meshtantic/protobufs and made a pull request there. |
fifieldt
added a commit
to fifieldt/meshtastic-protobufs
that referenced
this pull request
Nov 10, 2024
Most of the GPS chips we support have the ability to change their operating model "dynamics" based on the intended activities. We currently assume everyone is a pedestrian and configure as such. However, there are users out there on bikes, planes, balloons, and with fixed devices. Where GPS chips support it, we can configure for each of this circumstances and improve performance. For example, fixed nodes might no longer jump around on the map. Planes will have a more responsive and less filtered position. Balloons' GPS won't simply cut out because its gone over an altitude limit. Boats won't have altitudes that make them appear to be floating in the air. Additionally, this could provide the opportunity for a bit of fun in the apps - surface information about the use case so people know when they're connecting to a plane or baloon :) Related to: meshtastic/firmware#3984 Related to: meshtastic#619 Related to: meshtastic/firmware#5281
|
this is a null change. closing in favor of protobuf PR's |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I am very sorry, I forgot to actually change the name of the new port !
I fixed it in the next push to the same branch, but I am not sure how to proceed now.
Sorry for the mess.
I propose a new port number for airborne applications like OGN-Tracer or FANET or ADS-L whch have well establilshed compact position packet formats. It is more efficient to put position in this format, which takes like 16 bytes for OGN than use the GPS generic format where many elements are missing like climb rate ro turn rate.
The new port number would allow efficient (low rate) position reports by objects like amateur balloons.
The formatting would be simple: I define ID's for particulat packet type and they would be embedded as a pack of bytes, the decoding of the pack would follow the particular system.
If this gets accepted, I will proceed to define those ID's
Thank you.
BTW. I am beta-receiving Meshtantic on ground receivers of the Open Glider Network (OGN) and I wonder if it would be worth to upload this traffic to a server of yours ?