rdz_ttgo_sonde
rdz_ttgo_sonde copied to clipboard
dl9rdz
Question: Historical data?
Well, it is not saved on the TTGO, there are no resources for that (maybe in the future some option for storage on SD card might be added - some rudimentary source code is on git for that)
Storage outside depends on what you configure as external destinations where data is sent to :-).
So that is up to you to set up, either using public servers, with sondehub.org, wettersonde.de, and radiosondy.info being the most popular services, or you can also use any of the many options for self-hosted services, including MQTT (which some people combined with some database backend and grafana), aprsmap, chasemapper, etc.
Go to Sondehub.org , enter the probe serial number in the search field, and if data for this probe is found, then click "PLOTS":
Go to Sondehub.org , enter the probe serial number in the search field, and if data for this probe is found, then click "PLOTS":
I want to have my own data stored, not sondehub
Unfortunately I don't have any good references. I just had heard it from a few stations that they are using Grafana in some way. One example was in a discussion here, see https://github.com/dl9rdz/rdz_ttgo_sonde/issues/45
Along the same lines I am wondering about access to the received data telemetry stream via serial port on the TTGO. My potential use case would be a TTGO board connected to a large battery installed at a remote and favorable mountain top location for receiving location data for landed sondes in my area. Telemetry would be parsed and stored by an external uP board such as Raspberry Pi Pico. Once a month, or so, landed sonde data would be retrieved and battery replaced/recharged. Would prefer, for power consumption reasons, to keep WiFi powered off.
The serial port is currently used for logging debug data. You actually will find the telemetry in there if you want to (if you enable the right data feeds.
- the chasemapper connector should log all messages it sends out (simple json) (just the basic data)
- the mqtt connector should log all messages it attempts to sent to a mqtt server (more data, should work even if not connected to mqtt server)
- the sondehub connector should log all messages it sends out (more difficult to parse, these are chunked http requests merging multiple frames) - but only if connected to sondehub
- for axupd it is currently commented out in the source (advantage of axudp is that it is sent for all frames)
Currently there is not guarantee that the output will be the same on future versions.
Perfect! Physically on the TTGO LORA v2.1_1.6 boards this would be the USB port? Thanks!