-
Notifications
You must be signed in to change notification settings - Fork 49
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
Abusive path for APRS #9
Comments
After talking to a commercial pilot that has flown with a 300mW APRS transmitter all over North America, it appears that 10,000 feet would be a good transition from no path to the WIDE1-1, WIDE2-1. He even suggested dropping the WIDE1-1 completely |
Hi there, There is no "official" guidance on this and its basically down to the operators discretion. When doing the PITS code we followed these guidelines : However as you raised the issue we will look at making this configurable by the operator possibly even with altitude settings as you have requested. In the mean time you are welcome to adjust the code: https://github.com/PiInTheSky/pits/blob/master/tracker/aprs.c#L330 Cheers |
But you did not follow those guidelines! To wit:
abused. Due to the large DO NOT USE the following: On 10/28/2015 3:31 PM, Upuaut wrote:
Bob Harris |
Good point I think we misinterpreted it. Its in the list to fix thanks. |
Something to consider (and I have guided the students at Profile School That would not cause undue traffic on the national frequency but would I can let you know how it works out after the students launch their BTW, my compliments on nicely written code. While I developed firmware On 10/28/2015 4:27 PM, Upuaut wrote:
Bob Harris |
I'm currently working on some AVR APRS code and will make similar changes I've added settings for the altitude that the path switches at, and whether For PITS I'll probably allow for user-settable paths at altitude (WIDE2-1 Also I've added optional telemetry packets (e.g. for temperature, battery Dave On 28 October 2015 at 23:11, rlharris notifications@github.com wrote:
|
Wicked cool on all points. Thanks for putting up with this grouchy old man. On 10/28/2015 7:21 PM, David Akerman wrote:
Bob Harris |
Done (ages ago - should have been closed then). Path is now configurable using APRS_HighPath (WIDE2-1 or none) for > APRS_Altitude, and WIDE1-1, WIDE2-1 below that. |
Any path (e.g WIDE1-1, WIDE2-1) for a HAB is frowned on in North America since it adds congestion to the network while the balloon is aloft but such a path is valuable for recovery operations when the equipment is near the ground.
It appears that it is a simple change to make the ax25 frame contents change with altitude. I have modified aprs.c to switch between no path and the WIDE1-1, WIDE2-2 at 6000 feet. The value of 6000 feet was selected somewhat arbitrarily given the height of the White Mountains in New Hampshire (the area over which it is anticipated that the balloon will be making its descent). I hope the students with whom I am working will be able to test it.
The text was updated successfully, but these errors were encountered: