Skip to content
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

Balloon paths not displaying properly on Sondehub #297

Open
XionUAV opened this issue Apr 25, 2022 · 13 comments
Open

Balloon paths not displaying properly on Sondehub #297

XionUAV opened this issue Apr 25, 2022 · 13 comments

Comments

@XionUAV
Copy link

XionUAV commented Apr 25, 2022

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.

image

@dl9rdz
Copy link
Owner

dl9rdz commented Apr 25, 2022

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.

@XionUAV
Copy link
Author

XionUAV commented Apr 26, 2022 via email

@dl9rdz
Copy link
Owner

dl9rdz commented Apr 26, 2022

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.

@XionUAV
Copy link
Author

XionUAV commented Apr 26, 2022 via email

@XionUAV
Copy link
Author

XionUAV commented Apr 26, 2022 via email

@dl9rdz
Copy link
Owner

dl9rdz commented Apr 26, 2022

Yes, thanks, this seems to be the same problem, and fixed in the devel version.

@XionUAV
Copy link
Author

XionUAV commented Apr 27, 2022 via email

@XionUAV
Copy link
Author

XionUAV commented May 6, 2022 via email

@Mooni123
Copy link

Mooni123 commented May 6, 2022

Hello,

Why are you don't using the latest development build from here:
https://rdzsonde.mooo.com/download.html

@XionUAV
Copy link
Author

XionUAV commented May 6, 2022 via email

@dl9rdz
Copy link
Owner

dl9rdz commented May 6, 2022

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.

@XionUAV
Copy link
Author

XionUAV commented May 6, 2022 via email

@XionUAV
Copy link
Author

XionUAV commented Jul 7, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants