-
Notifications
You must be signed in to change notification settings - Fork 9
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
Support APRS Telemetry Scaling and Naming #17
Comments
This ticket is next up in importance for #LaunchWithFaraday buoy use. Will definitely help any station sending telemetry as well! Heads-up @rossengeorgiev and @PhirePhly on our service using |
Nice work! It is looking great |
OK Here are a few seconds of parsing to the screen a "telemetry-message":
|
Those are just configuration for how to interpret the values in telemetry. They need to be remembered per callsign. One downside is, if you miss the configuration messages, you can't really interpret telemetry. In same cases, people will send them once manually and never again. |
Thanks @rossengeorgiev . Yeah I was just documenting the packets for telemetry scaling/naming here. Agreed at the general approach needed to use them and will default to raw telemetry values if no recent scaling/naming is found. |
Ahh I have some working code placing APRS parameters into influxdb as fields. However, it appears I may want to use tags instead: This stinks. influxDB Grafana templating is how I wanted to solve this problem. Being able to query for the values makes sense. Well there are far fewer fewer telemetry stations so this may work. I'll also have to figure out how to pack in the key value pairs for a SHOW style query such that I can regex correctly. |
Alright, I'm stumped. There doesn't seem to be a good way around this with influxDB and Grafana only supporting SHOW queries for Grafana templates. I'm tempted to use mysql but that sorta defeats the purpose of @kb1lqd what do you think and is scaling/telemetry names/units something we want for Hackaday Supercon? Seems kind of important to me but I'm open to considering not. Seeing raw data is only so useful. |
Scaling seems to be working in the latest commit on issue17 branch in my repository. I'm at least scaling Faraday content and should apply scaling to any other station which sends out this data. By default I scale to bits. Data will only update to correct scaling when equations packet is sent out. Also I had to update the Faraday configuration for APRS to set the scaling values. Currently, all Faraday radio's are scaled to the same equations when received on a base station. Overall the APRS application does need some TLC. |
Summary
aprslib provides parsing of scaling values and channel names. We should use these...
http://aprs-python.readthedocs.io/en/latest/parse_formats.html#telemetry-configuration
Problem Explanation
Supporting Information
The text was updated successfully, but these errors were encountered: