...
How their drone telemetry works on a technical level:
Data comes in in byte arrays that a multi-process program parses and hands off to a different program.
That program converts the byte arrays of cbor format into csv or spreadsheets.
Then a third program takes all the telemetry related csv files and makes a big csv with all the data.
Then that big file is loaded in the plotting application
This may not exactly be how our telemetry works. The technical details don’t really matter though tbh
Basically raw data gets processed a few times into a massive spreadsheet (millions of cells), each cell with a single data entry
All the user can really see is the .csv file
This file is enormous, and functionally useless to the user. They can’t get any useful insights out of that
However, firmware has mentioned that they would like an option to see that raw data as a tab on the telemetry dashboard
Plot Juggler
The .csv spreadsheets are then imported into Plot Juggler
Open-source, so we can poke around if we wanted to
You can save create plot setups, so they have a setup bunch of setups that loads load once the data itself is imported/loaded in
“we have setups for position, velocity, and accel that have targets and actual
Then ones for each of the 4 propeller block with the values for the servos and rotor rpms
then a page with PID tunings”
along with many many other plot setups
Each graph below is a “plot setup” that you can just feed data into
...