-
Notifications
You must be signed in to change notification settings - Fork 26
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
ID 379 change please #184
Comments
So this can be done, but you should be aware that any station that hasn't restarted between when I change it and the flight will still possibly upload with the old callsign. It's probably better to just allocate another v2 ID. |
Please change it for now, we take the risk ;-) The sondes are programmed and on their way by mail packet. |
OK, that's done. You might want to remind people to restart their stations! |
Did that, on the FB channel, thanks !
Op wo 27 sep 2023 om 00:49 schreef Mark Jessop ***@***.***>:
… OK, that's done. You might want to remind people to restart their stations!
(Also remind them to update :-) )
—
Reply to this email directly, view it on GitHub
<#184 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABCFGJUSNAWZXIOL3LTCUS3X4NLY7ANCNFSM6AAAAAA5GJIG7M>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Hi, can ID 379 temporarily (until we request) be changed to
SPECTRE
(without 4fsk ) for the upcoming jota flight ?
(scheduled for saturday the 21th of October 08:30 UTC, 17 balloons on one frequency )
Thanks!
The text was updated successfully, but these errors were encountered: