You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ This will automatically install all dependencies. Depending on your Python insta
17
17
18
18
`rclogvis` analyses drone telemetry data recorded by EdgeTX/OpenTX remote control handsets and saved in comma-separated values (CSV) format files. For instance, Betaflight transmits several telemetry parameters via ExpressLRS or other radio link protocols to the RC handset. These typically include information about the RC link quality, drone attitude, power consumption, and eventually GPS data such as position, speed, altitude and heading.
19
19
20
-
As a first step, you must discover all the available telemetry sensors in your EdgeTX remote control handset. This is done on the model's telemetry page, Model -> Telemetry -> Sensors.
20
+
As a first step, you must discover all the available telemetry sensors in your EdgeTX remote control handset. This is done on the model's telemetry page under Model -> Telemetry -> Sensors.
21
21
22
22
Once that is done, you must configure the logging of the telemetry data to the RC handset's internal storage or SD card. This is achieved by adding a special function with the "SD Logs" action on the radio, located under Model -> Special Functions. This function should become active when the drone is armed, i.e. when the arm switch is activated. The logging interval depends on the telemetry update rate via the RC link. In particular, it should be slower than the telemetry update rate. For ExpressLRS, the telemetry packet intervals for different link configurations are available on the [telemetry bandwidth page](https://www.expresslrs.org/info/telem-bandwidth/). In practice, a logging interval of 0.2 - 0.3 seconds works well for a standard 150 Hz ExpressLRS link setup.
0 commit comments