-
Notifications
You must be signed in to change notification settings - Fork 93
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
Add receiver lat/lon/altitude to ChaseMapper #412
Comments
The chasemapper has its own GPS receiver or receives the coordinates of the chaser from the gpsd or on the 55672 port in a separate packet. The balloon telemetry does not include the chaser coordinates (which is why it won't work) Try using the rdzwx-go mobile app it shows distance and direction. https://github.com/dl9rdz/rdzwx-go |
OK, thanks, since the receiver has its GPS location I was looking for a way to get it out of the receiver. -- Thanks |
Another possible solution |
Chasemapper telemetry can include chase car positions, so the TTGO position could be included there. But if it is just about getting the position to some other custom (non-chasemapper) application, there are several options, most preferred first:
|
If you are trying to use the TTGO GPS receiver as a 'car position' input into chasemapper, then the correct format to send data out would be:
If you configure chasemapper to use a car_source type of 'horus_udp', then this will be picked up and used for the car position. There is an assumption made here that all telemetry data and the car are all at the same location... |
Would it be possible to add the lat/lon/altitude fields of the receiver to the ChaseMapper JSON output?
The receiver has a GPS receiver and the data should be available on each balloon transmission sent via ChaseMapper.
This would provide the appropriate data to mobile/portable external tracking systems and allow for easy distance/direction calculations between the receiver and the balloon.
The text was updated successfully, but these errors were encountered: