rdz_ttgo_sonde
rdz_ttgo_sonde copied to clipboard
dl9rdz
Balloon paths not displaying properly on Sondehub
I have an RDZ tracker setup in Southern Idaho tracking the balloons out of Elko, Nevada. Occasionally on Sondehub it will show two balloons with different serial numbers but only one is live tracking. Then it will display a path out and back for the other balloon as if it was a past flight. I thought this was an isolated incident until installing another RDZ tracker in Lehi, Utah that occasionally does the same thing.
Yesterday I recovered a balloon in Southern Idaho that was launched from Elko, Nevada a few days before and tracked with an RDZ station. When I tried to log the recovery by entering the serial number in Sondehub, the attached screenshot is what I got. It showed a path to the area where I actually recovered the balloon but also a path back to the launch point. Since it shows the balloon at the launch point, I was unable to log the recovery because Sondehub returned an error of "Distance Limit Exceeded." I have never seen or experienced this problem with my Auto_RX stations.
I believe the 6,519 m altitude shown is where the RDZ station first picked up the signal. It's as if the station is reporting earlier data to Sondehub after the last position of a flight is received.
Thanks for reporting this. I will have to investigate. I see that you are using the latest master version, and that should have a fix for this issue, but something seems to be going wrong. I can see the following data in the sondehub database:
last valid frame: 2022-04-21T13:46:28.000Z 20041523 1334583988 42.10449 -113.7306 3180.0 N7ZDX-3
and then: 2022-04-21T23:23:00.000Z 21013116 1334618580 40.96049 -115.6911 6592.1001 N7ZDX-3 2022-04-21T23:23:37.000Z 20041523 1334618617 40.95634 -115.69623 6447.8999 N7ZDX-3 [...] 2022-04-21T23:23:48.000Z 20041523 1334618628 40.95835 -115.69376 6519.0 N7ZDX-3 2022-04-21T23:23:54.000Z 21013116 1334618634 40.95948 -115.69256 6556.3999 N7ZDX-3
This definitely should not happen, and right now I have no explanation for that.
I'm glad you are able to verify that there is an actual issue. Thank you for responding so quickly. Hopefully you'll be able to find the source of the issue. Good luck.
On Mon, Apr 25, 2022, 5:08 PM dl9rdz @.***> wrote:
Thanks for reporting this. I will have to investigate. I see that you are using the latest master version, and that should have a fix for this issue, but something seems to be going wrong. I can see the following data in the sondehub database:
last valid frame: 2022-04-21T13:46:28.000Z 20041523 1334583988 42.10449 -113.7306 3180.0 N7ZDX-3
and then: 2022-04-21T23:23:00.000Z 21013116 1334618580 40.96049 -115.6911 6592.1001 N7ZDX-3
2022-04-21T23:23:37.000Z 20041523 1334618617 40.95634 -115.69623 6447.8999 N7ZDX-3 [...] 2022-04-21T23:23:48.000Z 20041523 1334618628 40.95835 -115.69376 6519.0 N7ZDX-3 2022-04-21T23:23:54.000Z 21013116 1334618634 40.95948 -115.69256 6556.3999 N7ZDX-3
This definitely should not happen, and right now I have no explanation for that.
— Reply to this email directly, view it on GitHub https://github.com/dl9rdz/rdz_ttgo_sonde/issues/297#issuecomment-1109124588, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANRESGSJDGQ3XW2WL7RRRBTVG4QWNANCNFSM5UJLFKYA . You are receiving this because you authored the thread.Message ID: @.***>
Ok, I have made some enhancements to the DFM ID handling. This might fix the problem (in devel-20220426). I will release a new master version some time next week after more testing.
Very good. I'll watch for the new version.
On Tue, Apr 26, 2022, 2:08 PM dl9rdz @.***> wrote:
Ok, I have made some enhancements to the DFM ID handling. This might fix the problem (in devel-20220426). I will release a new master version some time next week after more testing.
— Reply to this email directly, view it on GitHub https://github.com/dl9rdz/rdz_ttgo_sonde/issues/297#issuecomment-1110201866, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANRESGRUFENR57X5HEYUEJ3VHBEMTANCNFSM5UJLFKYA . You are receiving this because you authored the thread.Message ID: @.***>
I don’t know if this will be of any further value or not but right now an RDZ station I built for a guy in Spokane, Washington is producing the problem I described.
From: dl9rdz @.*** Sent: Tuesday, April 26, 2022 2:09 PM To: dl9rdz/rdz_ttgo_sonde @.> Cc: XionUAV @.>; Author @.***> Subject: Re: [dl9rdz/rdz_ttgo_sonde] Balloon paths not displaying properly on Sondehub (Issue #297)
Ok, I have made some enhancements to the DFM ID handling. This might fix the problem (in devel-20220426). I will release a new master version some time next week after more testing.
— Reply to this email directly, view it on GitHub https://github.com/dl9rdz/rdz_ttgo_sonde/issues/297#issuecomment-1110201866 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ANRESGRUFENR57X5HEYUEJ3VHBEMTANCNFSM5UJLFKYA . You are receiving this because you authored the thread. https://github.com/notifications/beacon/ANRESGVGMYZF6QPDIQUD2HTVHBEMTA5CNFSM5UJLFKYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOIIWFMCQ.gif Message ID: @.*** @.***> >
Yes, thanks, this seems to be the same problem, and fixed in the devel version.
Very good.
From: dl9rdz @.*** Sent: Tuesday, April 26, 2022 5:45 PM To: dl9rdz/rdz_ttgo_sonde @.> Cc: XionUAV @.>; Author @.***> Subject: Re: [dl9rdz/rdz_ttgo_sonde] Balloon paths not displaying properly on Sondehub (Issue #297)
Yes, thanks, this seems to be the same problem, and fixed in the devel version.
— Reply to this email directly, view it on GitHub https://github.com/dl9rdz/rdz_ttgo_sonde/issues/297#issuecomment-1110352766 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ANRESGUEKNGZL5PN43IIKOTVHB5YLANCNFSM5UJLFKYA . You are receiving this because you authored the thread. https://github.com/notifications/beacon/ANRESGSLH4PJ6RKLKG3N2ODVHB5YLA5CNFSM5UJLFKYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOIIXKG7Q.gif Message ID: @.*** @.***> >
Is there any chance the new version is ready to download? I’m building a tracker to send to one of the members of my Radiosonde North America group and there is no way he would be able to load the firmware himself if I loaded the old firmware and sent the tracker to him. Very nice guy and fellow Ham, but severely technically challenged. Thanks.
From: dl9rdz @.*** Sent: Tuesday, April 26, 2022 5:45 PM To: dl9rdz/rdz_ttgo_sonde @.> Cc: XionUAV @.>; Author @.***> Subject: Re: [dl9rdz/rdz_ttgo_sonde] Balloon paths not displaying properly on Sondehub (Issue #297)
Yes, thanks, this seems to be the same problem, and fixed in the devel version.
— Reply to this email directly, view it on GitHub https://github.com/dl9rdz/rdz_ttgo_sonde/issues/297#issuecomment-1110352766 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ANRESGUEKNGZL5PN43IIKOTVHB5YLANCNFSM5UJLFKYA . You are receiving this because you authored the thread. https://github.com/notifications/beacon/ANRESGSLH4PJ6RKLKG3N2ODVHB5YLA5CNFSM5UJLFKYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOIIXKG7Q.gif Message ID: @.*** @.***> >
Hello,
Why are you don't using the latest development build from here: https://rdzsonde.mooo.com/download.html
Very good. Thank you.
The last time we spoke you said you wanted to test your changes for a week or so before releasing a final version so I wasn’t sure if that had happened or not.
From: Mooni123 @.*** Sent: Friday, May 6, 2022 8:34 AM To: dl9rdz/rdz_ttgo_sonde @.> Cc: XionUAV @.>; Author @.***> Subject: Re: [dl9rdz/rdz_ttgo_sonde] Balloon paths not displaying properly on Sondehub (Issue #297)
Hello,
Why are you don't using the latest development build from here: https://rdzsonde.mooo.com/download.html
— Reply to this email directly, view it on GitHub https://github.com/dl9rdz/rdz_ttgo_sonde/issues/297#issuecomment-1119690578 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ANRESGTGXVXDOLIQPBWBT6LVIUUWVANCNFSM5UJLFKYA . You are receiving this because you authored the thread. https://github.com/notifications/beacon/ANRESGV4DVF5JQPMX46GC6TVIUUWVA5CNFSM5UJLFKYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOIK6R6UQ.gif Message ID: @.*** @.***> >
I am travelling right now and did not create the new master version yet. But I did not hear anything bad about the devel version, so I might just merge it into the master branch. But anyway, the functionality will be exactly the same as in the current devel version, so feel free to use just that for now.
Perfect. Thank you. I’ve loaded the devel version onto the TTGO board and will test it tonight before sending it to the guy tomorrow. I’ll also share this info with my Radiosonde North America Facebook group.
By the way, here’s the case I designed and use with the TTGO board and your firmware. The front cover shape is the same used with the MySondy in order to fit a 2000 mAh battery. The back cover is deeper and there are no mounting ears on that one. And of course that one has “GO” on the front.
Save travels.
From: dl9rdz @.*** Sent: Friday, May 6, 2022 1:52 PM To: dl9rdz/rdz_ttgo_sonde @.> Cc: XionUAV @.>; Author @.***> Subject: Re: [dl9rdz/rdz_ttgo_sonde] Balloon paths not displaying properly on Sondehub (Issue #297)
I am travelling right now and did not create the new master version yet. But I did not hear anything bad about the devel version, so I might just merge it into the master branch. But anyway, the functionality will be exactly the same as in the current devel version, so feel free to use just that for now.
— Reply to this email directly, view it on GitHub https://github.com/dl9rdz/rdz_ttgo_sonde/issues/297#issuecomment-1119962992 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ANRESGXGTVVNDPKJ4RKKJETVIVZ7LANCNFSM5UJLFKYA . You are receiving this because you authored the thread.Message ID: @.***>
Looks like there might still be an issue with the new version of firmware. However, I only started noticing this after there was a power-bump at the tracker's location. It wasn't displaying on Sondehub after that. I had a person there unplug it, wait then plug it back in. However, doing this obviously shouldn't affect the firmware. The position of the lower balloon in this screenshot is where the RDZ lost signal. It was tracking the same balloon.