Vio low frequency in Qgroundcontrol/ rc slow response
-
@Eric-Katzfey Maybe you can help me fixed but the vio result on Qgroundcontrol is streaming at 1hz, and the reaction speed of the remote control on Qgroundcontrol is really bad. It reacts slow, is there something I am doing wrong
da55f918-135a-4636-a2b4-8bfb0f634445-image.pngWhat is strange is that from the drone, the vio data ms is fine voxl2:~$ voxl-inspect-qvio
waiting for serverdt(ms) | T_imu_wrt_vio (m) |Roll Pitch Yaw (deg)|features|quality| state| error_codes |
29.3 | -0.00 -0.00 -0.00| -0.0 0.0 0.0| 28 | 27% | OKAY |This is a video of what I mean-> https://drive.google.com/drive/folders/122cPZ1S3Z_gP0yo8nipRGJHqpJTSj9c3?usp=sharing
-
@Eric-Katzfey Maybe you can help me fixed but the vio result on Qgroundcontrol is streaming at 1hz, and the reaction speed of the remote control on Qgroundcontrol is really bad. It reacts slow, is there something I am doing wrong
da55f918-135a-4636-a2b4-8bfb0f634445-image.pngWhat is strange is that from the drone, the vio data ms is fine voxl2:~$ voxl-inspect-qvio
waiting for serverdt(ms) | T_imu_wrt_vio (m) |Roll Pitch Yaw (deg)|features|quality| state| error_codes |
29.3 | -0.00 -0.00 -0.00| -0.0 0.0 0.0| 28 | 27% | OKAY |This is a video of what I mean-> https://drive.google.com/drive/folders/122cPZ1S3Z_gP0yo8nipRGJHqpJTSj9c3?usp=sharing
@stevedan Is this with original code or with the new code I just provided?
-
@stevedan Is this with original code or with the new code I just provided?
-
@stevedan Is this with original code or with the new code I just provided?
-
That's correct. QGC gets a low data rate stream for telemetry only, devices onboard VOXL can access much higher data rates without the wireless link bottleneck.
The "normal" telemetry mavlink data rates are defined by PX4 here:
https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/mavlink/mavlink_main.cpp#L1490The faster "onboard" data rates are defined here:
https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/mavlink/mavlink_main.cpp#L1545From a VOXL shell, you can use the new voxl-inspect-mavlink tool to see the actual data rates being sent by PX4.
voxl-inspect-mavlink mavlink_to_gcs voxl-inspect-mavlink mavlink_onboardNote, the configuration for the mavlink-to-gcs broadcaster lives here
https://github.com/modalai/px4-firmware/blob/voxl-dev/boards/modalai/voxl2/target/voxl-px4-start#L191 -
That's correct. QGC gets a low data rate stream for telemetry only, devices onboard VOXL can access much higher data rates without the wireless link bottleneck.
The "normal" telemetry mavlink data rates are defined by PX4 here:
https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/mavlink/mavlink_main.cpp#L1490The faster "onboard" data rates are defined here:
https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/mavlink/mavlink_main.cpp#L1545From a VOXL shell, you can use the new voxl-inspect-mavlink tool to see the actual data rates being sent by PX4.
voxl-inspect-mavlink mavlink_to_gcs voxl-inspect-mavlink mavlink_onboardNote, the configuration for the mavlink-to-gcs broadcaster lives here
https://github.com/modalai/px4-firmware/blob/voxl-dev/boards/modalai/voxl2/target/voxl-px4-start#L191 -
That's correct. QGC gets a low data rate stream for telemetry only, devices onboard VOXL can access much higher data rates without the wireless link bottleneck.
The "normal" telemetry mavlink data rates are defined by PX4 here:
https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/mavlink/mavlink_main.cpp#L1490The faster "onboard" data rates are defined here:
https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/mavlink/mavlink_main.cpp#L1545From a VOXL shell, you can use the new voxl-inspect-mavlink tool to see the actual data rates being sent by PX4.
voxl-inspect-mavlink mavlink_to_gcs voxl-inspect-mavlink mavlink_onboardNote, the configuration for the mavlink-to-gcs broadcaster lives here
https://github.com/modalai/px4-firmware/blob/voxl-dev/boards/modalai/voxl2/target/voxl-px4-start#L191 -
@James-Strawson Is it possible to modify this rates?
@stevedan The mavlink rates are all configured in /usr/bin/voxl-px4-start. Look at the end of that file. You can change it to whatever you like.
-
@stevedan The mavlink rates are all configured in /usr/bin/voxl-px4-start. Look at the end of that file. You can change it to whatever you like.
Reading along? Create a free ModalAI Forum account to join in.
With an account you can reply, ask your own question, get an email when a ModalAI engineer answers, and mark the reply that solved it. Your place in each thread is saved between visits.
Questions about VOXL, Flight Core, ESCs and ModalAI drones are answered here by the engineers who build them.
Register Login