Hello @Nathan-Raras and @Nathan-Raras ,

I don't see any Qualcomm device with running "lsusb".
I also have confirmed that the USB-C cable is able to access another VOXL device.
So I have submitted the RMA
d45c5737-8bf3-4c8b-9e7d-851acbfe82a8-image.png

Please let me know if any questions or suggestions.
Thank you very much for supporting.

Hi @Sam-Kiley
We do try to state on there directly the following:
e389e9ff-ddd2-4aa6-a26a-32acb43e1800-image.png
9bd88fcb-93bd-4b28-9565-4ade539bcd12-image.png
So yes, if you bought a 5G card from us in the past for Quectel, it was a different SKU, likely MDK-M0090-3-01-00, not the current offering for Sierra MDK-M0090-3-02-00
5f09fe55-6bb8-46d7-bb3c-4308a94357be-image.png

We do not make the Quectel variants anymore since we source the Sierra's to be NDAA compliant.

@shivam-rana , if you have a few wifi adapters which are currently not detected by VOXL2, if you plug into a standard Linux machine and if they are detected, you should check with chipset is used on those adapters and we can see if that's available (but not currently compiled) option for the VOXL2 kernel. We can add some documentation to help you build your own test kernel with enabled module and see if that works.

The VOXL2 kernel build guide is here : https://docs.modalai.com/voxl2-kernel-build-guide/ but it does not explicitly state how to make modifications to enable additional components. For those folks who have built kernels before, this may be easy to do, but for the first time it could be very difficult to do the right thing, but the change could be very small (one line). So we can see if it's possible to enable the driver that you need, but there would be no guarantees about functionality, since it would be untested (by us).

Alex

Hello, @Stefan-Amundarain ,

Let's try to narrow this down. Can you reproduce the issue without flying?

When the issue occurs, does the camera server restart completely, or you only lose hires camera feed. I suggest running the test on the bench with voxl-camera-server running in foreground so you can easily see what's happening in real time.

Please try to reproduce on the bench all 3 cameras (hires, tracking, TOF) working with your Ark Flow board working as well, then you can just move the platform by hand, if needed, to cause the camera failure and investigate what:

voxl-camera-server outputs output of dmesg

We can go from there.

Also, can you please provide details how the ARK Flow is actually connected to VOXL2 (electrically) and also confirm that the issue does not happen at all without ARK Flow plugged in?

Also, using voxl-portal should not cause the camera server or the portal backend to get bogged down if your image is reasonable size (not full 4k image), but a small 720p is just fine.

You could view the 3 camera streams thru voxl portal during the test or just have the voxl-inspect-cam tool running and inspecting just the streams that you want (you can provide the streams to inspect as arguments to the tool, such as voxl-inspect-cam hires tracking_down tof_depth, etc. Either voxl-portal or voxl-inspect-cam should properly use the camera pipeline with all camera streaming, so that you can catch the fault.

Alex

@smiley , we made a small adjustment to the M0159 board to make it fit into the Hadron better (board outline). That was a small board re-spin (same functionality). Checking on the status..

Alex

@ashwin I don't have the info either but it's similar to VOXL2's weight which is 16g

@goswamid ,

Yes we do sell those parts. Please contact us via online form. https://www.modalai.com/pages/contact-us

The part number you will need is M10000524

Alex

@jbhines929 No problem, thanks for the patience!

@tom

I managed to get ADB working and have reinstalled the VOXL. I went for 1.1.2 version as wanted to see if previous issues i had with both 1.2.0 and 0.9.5 would be present. As of now I am able to ADB to the drone, as well as ssh, with it using the AP mode however my QGroundControl does not see the drone. I have changed within the voxl-mavlink-server.conf the secondary ip address to the one that PC has when connected to the drone IP, and the following services are running. But QGroundControl does not seem to see the connection.

These are the following commands and their outputs. The one VOXL version which worked the best on the VOXL 1 board was 0.9.5 but after updating and switching both between AP mode and connected to Wifi router, there is no responce to the connection. When checking messages send to QGC the terminal is stopped at the step of the screenshot.

Screenshot from 2025-06-05 14-27-27.png
Screenshot from 2025-06-05 14-45-16.png
Screenshot from 2025-06-05 14-46-00.png
Screenshot from 2025-06-05 14-46-45.png
Screenshot from 2025-06-05 14-49-23.png
Screenshot from 2025-06-05 14-50-21.png

I went through the setup process few times and am unsure what could be the issue or what to try next. The QGC version is v4.4.5
In case I can create new thread for this but been trying to get two Seeker drones operational.

Thank you for your time and assistance.

Sincerely

Adam Nekolny

@Jetson-Nano , please confirm the ESC is working by using a usb to serial connection directly to the esc and voxl-esc Python tools on a Linux PC or VM.

You can run simple commands to detect the esc and perform spin tests if needed, this is all documented.

https://docs.modalai.com/voxl-escs/faq/

If the esc is ok, then you will need to double check the FC v2 setup.

Alex

@george-kollamkulam That port is internally connected to the 5V coming from the main VOXL2 power (which is technically 5V 6A). Obviously you would be limited by the connector pins, which are rated around 1A max continuous. Also, drawing too much from this pin, can bring down the whole VOXL2 (if that 5V output on J19 is shorted to GND, for example).

@Yufei-Jiang And I used voxl-configure-cameras and voxl-configure-extrinsics D0006_Sentinel to generate the camera config.

@ashwin

Do you need to be able to control the servo from PX4 or it would be acceptable to have an API you could use on the CPU / Linux on VOXL2 ?

Alex

@zauberflote1 @James-Strawson

I am attaching an issue i am facing, the drone is stable in a mat, but as soon as i bring it back i loses the position and drifts out and goes crazy when i try to give pilot input

INFO] world : 1.000000 1.000000 (2) ERROR in insert_data, detected timestamp out of order ov, 1440558439657 vs 1440591773303 ERROR in insert_data, detected timestamp out of order ov, 1456191779391 vs 1456191779391 ERROR in insert_data, detected timestamp out of order ov, 1460758438920 vs 1460791771472 ERROR in insert_data, detected timestamp out of order ov, 1461691774910 vs 1461691774910 ERROR in insert_data, detected timestamp out of order ov, 1461858441212 vs 1461858441212 ERROR in insert_data, detected timestamp out of order ov, 1462091774232 vs 1462125109024 ERROR in insert_data, detected timestamp out of order ov, 1462258438295 vs 1462291773555 ERROR in insert_data, detected timestamp out of order ov, 1462491774024 vs 1462525106316 ERROR in insert_data, detected timestamp out of order ov, 1462658436524 vs 1462725109597 ERROR in insert_data, detected timestamp out of order ov, 1462825106628 vs 1462891775690 ERROR in insert_data, detected timestamp out of order ov, 1462991771420 vs 1463058439440 ERROR in insert_data, detected timestamp out of order ov, 1464125106211 vs 1464125106211 ERROR in insert_data, detected timestamp out of order ov, 1464291773919 vs 1464291773919 ERROR in insert_data, detected timestamp out of order ov, 1464458441002 vs 1464458441002 ERROR in insert_data, detected timestamp out of order ov, 1464691773398 vs 1464725105273 ERROR in insert_data, detected timestamp out of order ov, 1465425110585 vs 1465558437773 ERROR in insert_data, detected timestamp out of order ov, 1465658438450 vs 1465825104596 ERROR in insert_data, detected timestamp out of order ov, 1465925106418 vs 1466091986731 ERROR in insert_data, detected timestamp out of order ov, 1466091986731 vs 1466225109387 ERROR in insert_data, detected timestamp out of order ov, 1466258441991 vs 1466391773450 ERROR in insert_data, detected timestamp out of order ov, 1467658442251 vs 1467691776314 ERROR in insert_data, detected timestamp out of order ov, 1470658438812 vs 1470658438812 ERROR in insert_data, detected timestamp out of order ov, 1470791773187 vs 1470858439698 ERROR in insert_data, detected timestamp out of order ov, 1470958439854 vs 1471025104073 ERROR in insert_data, detected timestamp out of order ov, 1471125105010 vs 1471191771000 ERROR in insert_data, detected timestamp out of order ov, 1471325106781 vs 1471358439125 ERROR in insert_data, detected timestamp out of order ov, 1471491772927 vs 1472058437406 ERROR in insert_data, detected timestamp out of order ov, 1471658438604 vs 1472225105843 ERROR in insert_data, detected timestamp out of order ov, 1471791775375 vs 1472225105843 ERROR in insert_data, detected timestamp out of order ov, 1471958440114 vs 1472425105999 ERROR in insert_data, detected timestamp out of order ov, 1472125105427 vs 1472592004124 ERROR in insert_data, detected timestamp out of order ov, 1472291774385 vs 1472758439489 ERROR in insert_data, detected timestamp out of order ov, 1472491771728 vs 1472925109124 waiting for enough clone states (1 of 5).... waiting for enough clone states (2 of 5).... waiting for enough clone states (3 of 5).... waiting for enough clone states (4 of 5).... ERROR in insert_data, detected timestamp out of order ov, 1474458439176 vs 1474458439176 ERROR in insert_data, detected timestamp out of order ov, 1474858440061 vs 1475625107196 ERROR in insert_data, detected timestamp out of order ov, 1474891775321 vs 1475625107196 ERROR in insert_data, detected timestamp out of order ov, 1474925109957 vs 1475625107196 ERROR in insert_data, detected timestamp out of order ov, 1474958443290 vs 1475625107196 ERROR in insert_data, detected timestamp out of order ov, 1474991770946 vs 1475625107196 ERROR in insert_data, detected timestamp out of order ov, 1475025106050 vs 1475625107196 ERROR in insert_data, detected timestamp out of order ov, 1475058439748 vs 1475625107196 [WARN] Motion detected, going to full processing ERROR in insert_data, detected timestamp out of order ov, 1475091775165 vs 1475625107196 ERROR in insert_data, detected timestamp out of order ov, 1475125106571 vs 1475625107196 ERROR in insert_data, detected timestamp out of order ov, 1475158441363 vs 1475625107196 ERROR in insert_data, detected timestamp out of order ov, 1475191774279 vs 1475625107196 ERROR in insert_data, detected timestamp out of order ov, 1475225106988 vs 1475625107196 ERROR in insert_data, detected timestamp out of order ov, 1475258438550 vs 1475625107196 ERROR in insert_data, detected timestamp out of order ov, 1475291774540 vs 1475625107196 ERROR in insert_data, detected timestamp out of order ov, 1475325106311 vs 1475625107196 ERROR in insert_data, detected timestamp out of order ov, 1475458439384 vs 1477225106518 ERROR in insert_data, detected timestamp out of order ov, 1475491771415 vs 1477225106518 ERROR in insert_data, detected timestamp out of order ov, 1475691776883 vs 1477558441674 ERROR in insert_data, detected timestamp out of order ov, 1475725110738 vs 1477558441674 ERROR in insert_data, detected timestamp out of order ov, 1475758443863 vs 1477558441674 ERROR in insert_data, detected timestamp out of order ov, 1475791778446 vs 1477558441674 ERROR in insert_data, detected timestamp out of order ov, 1475825110321 vs 1477558441674 ERROR in insert_data, detected timestamp out of order ov, 1475858439383 vs 1477558441674 ERROR in insert_data, detected timestamp out of order ov, 1475891772613 vs 1477558441674 ERROR in insert_data, detected timestamp out of order ov, 1475925110581 vs 1477558441674 ERROR in insert_data, detected timestamp out of order ov, 1475958442873 vs 1477558441674 ERROR in insert_data, detected timestamp out of order ov, 1475991771154 vs 1477558441674 ERROR in insert_data, detected timestamp out of order ov, 1476291770633 vs 1478191770789 ERROR in insert_data, detected timestamp out of order ov, 1476325110946 vs 1478191770789 ERROR in insert_data, detected timestamp out of order ov, 1476358440894 vs 1478191770789 ERROR in insert_data, detected timestamp out of order ov, 1476392017456 vs 1478191770789 ERROR in insert_data, detected timestamp out of order ov, 1476425106258 vs 1478191770789 ERROR in insert_data, detected timestamp out of order ov, 1476458439956 vs 1478191770789 ERROR in insert_data, detected timestamp out of order ov, 1476491775894 vs 1478191770789 ERROR in insert_data, detected timestamp out of order ov, 1476525105946 vs 1478191770789 ERROR in insert_data, detected timestamp out of order ov, 1478325107247 vs 1480091772507 ERROR in insert_data, detected timestamp out of order ov, 1478358437924 vs 1480091772507 ERROR in insert_data, detected timestamp out of order ov, 1478391771674 vs 1480091772507 ERROR in insert_data, detected timestamp out of order ov, 1478425108653 vs 1480091772507 ERROR in insert_data, detected timestamp out of order ov, 1478458442768 vs 1480091772507 ERROR: invalid metadata, magic number=387521565, expected 1448040524 most likely client fell behind and pipe overflowed ERROR in insert_data, detected timestamp out of order ov, 1514291774160 vs 1514291774160 ERROR: features were 0 for a long time! cur: 1, min_req: 15 (are you bench testing?) [VIO_BAD_STATE] No Stable feature. WARNING auto-resetting, Bad VIO, State: true Q: -1 Vel: 1.738034 Uncert: 0.000915 State: 0(1) ERROR DIAGONAL WENT NEGATIVE ERROR DIAGONAL WENT NEGATIVE ERROR DIAGONAL WENT NEGATIVE ERROR DIAGONAL WENT NEGATIVE ERROR DIAGONAL WENT NEGATIVE ERROR DIAGONAL WENT NEGATIVE voxl-open-vins-server: /builds/voxl-public/voxl-sdk/third-party/voxl-open-vins/open_vins/ov_msckf/src/state/StateHelper.cpp:114: Assertion `!found_neg' failed. Aborted voxl2:~$ voxl-inspect-vins waiting for server at /run/mpa/ov_extended T_imu_wrt_vio (m) |Roll Pitch Yaw (deg)| state| error_code 0.00 0.00 0.00| -0.8 -2.7 0.0| OKAY | DROPPED_IMU voxl-open-vins-server disconnected T_imu_wrt_vio (m) |Roll Pitch Yaw (deg)| state| error_code 0.00 0.00 0.00| -0.9 -2.7 0.0| OKAY | ERROR validating EXT VIO t read 8424 bytes, but it should be a multiple of 5268 ERROR validating EXT VIO data received through pipe: read partial packet read 8424 bytes, but it should be a multiple of 5268 ERROR validating EXT VIO data received through pipe: read partial packet read 4224 bytes, but it should be a multiple of 5268 0.00 0.00 0.00| -0.9 -2.7 0.0| OKAY | ERROR validating EXT VIO t read 8424 bytes, but it should be a multiple of 5268 ERROR validating EXT VIO data received through pipe: read partial packet read 2112 bytes, but it should be a multiple of 5268 0.00 0.00 0.00| -0.9 -2.7 0.0| OKAY | ERROR validating EXT VIO t read 8424 bytes, but it should be a multiple of 5268 ERROR validating EXT VIO data received through pipe: read partial packet read 2112 bytes, but it should be a multiple of 5268 -0.00 -0.00 0.00| -0.9 -2.8 0.0| OKAY | ERROR validating EXT VIO t read 8424 bytes, but it should be a multiple of 5268 ERROR validating EXT VIO data received through pipe: read partial packet read 8424 bytes, but it should be a multiple of 5268 ERROR validating EXT VIO data received through pipe: read partial packet read 8424 bytes, but it should be a multiple of 5268 ERROR validating EXT VIO data received through pipe: read partial packet read 6336 bytes, but it should be a multiple of 5268 -0.00 -0.00 0.00| -0.9 -2.8 0.0| OKAY | ERROR validating EXT VIO t read 8424 bytes, but it should be a multiple of 5268 ERROR validating EXT VIO data received through pipe: read partial packet read 2112 bytes, but it should be a multiple of 5268 -0.00 -0.00 0.00| -0.9 -2.8 0.0| OKAY | ERROR validating EXT VIO t read 8424 bytes, but it should be a multiple of 5268 ERROR validating EXT VIO data received through pipe: read partial packet read 2112 bytes, but it should be a multiple of 5268 -0.00 -0.00 0.00| -0.9 -2.8 0.0| OKAY | ERROR validating EXT VIO t read 8424 bytes, but it should be a multiple of 5268 ERROR validating EXT VIO data received through pipe: read partial packet read 7380 bytes, but it should be a multiple of 5268 -0.00 -0.00 0.00| -0.9 -2.8 0.0| OKAY | ERROR validating EXT VIO t read 8424 bytes, but it should be a multiple of 5268 ERROR validating EXT VIO data received through pipe: read partial packet read 7380 bytes, but it should be a multiple of 5268 4.38 -1.43 1.78| -1.6 19.3 -4.9| OKAY | voxl-open-vins-server disconnected ERROR in pipe_client_open opening request pipe: No such device or address Most likely the server stopped without cleaning up Client is cleaning up pipes for the server

@Jetson-Nano you could just use the CPP mavsdk instance to grab the TOF data from a MPA pipe and then leverage that to do your controls via mavsdk (I am assuming just offboard movement). You can connect over port 14551 just ensure you have localhost comms set to true in voxl-vision-hub.

@Andrew-Jue Hi! Could you share how you managed to get your VOXL2 working with motion capture? Did you also use Starling 2 or just a VOXL2 on another platform? It looks like I ran into the same problems as you while trying to get my Starling 2 (also using VOXL2) to position hold with an Optitrack setup

I tried following your troubleshooting steps and replicating your params exactly, and while it seems like it can be toggled into position hold, it doesn't hold its position at all. It just kinda flies off away as soon as I switch it into position hold. I did a screen recording of the outputs of /mavros/vision_pose/pose and /mavros/local_position/pose during flight and noticed that the values for these topics diverges and converges seemingly randomly

Before flight (Left: /mavros/vision_pose/pose, Right: /mavros/local_position/pose)
24e5cb61-9e40-464e-8941-6c60f804f9b4-Screenshot from 2025-06-11 18-24-58.png

During pos hold (Left: /mavros/vision_pose/pose, Right: /mavros/local_position/pose)
73806f5a-aef4-44f7-9cda-90fa7cd39789-image.png

I reviewed the flight logs and it does look like something is commanding it to move away from its position for some reason.
9df2c832-cb27-4fee-af22-ed7b037e9351-image.png

My theory is that the usb wifi on the Starling2 might be introducing some latency that is causing it to fly erratically, although the visual odometry latency seems fine (I think)

f8abeff3-8923-4ead-a9c6-b6a2134ad612-image.png

Do you have any hints as to what the problem might be?

These are the changes I made to switch the Starling 2 to receive data from the Optitrack system:

In /etc/modalai/voxl-vision-hub.conf, changed en_vio to false { "config_file_version": 1, "en_localhost_mavlink_udp": true, "localhost_udp_port_number": 14551, "en_vio": false, "vio_pipe": "qvio", "secondary_vio_pipe": "ov", "vfc_vio_pipe": "ov", "en_reset_vio_if_initialized_inverted": true, "vio_warmup_s": 3, "send_odom_while_failed": true, "horizon_cal_tolerance": 0.5, "en_hitl": false, "offboard_mode": "off", "follow_tag_id": 0, "figure_eight_move_home": true, "robot_radius": 0.300000011920929, "collision_sampling_dt": 0.1, "max_lookahead_distance": 1, "backtrack_seconds": 60, "backtrack_rc_chan": 8, "backtrack_rc_thresh": 1500, "wps_move_home": true, "wps_stride": 0, "wps_timeout": 0, "wps_damp": 1, "wps_vfc_mission": true, "en_tag_fixed_frame": false, "fixed_frame_filter_len": 5, "en_transform_mavlink_pos_setpoints_from_fixed_frame": false, "vfc_rate": 100, "vfc_rc_chan_min": 980, "vfc_rc_chan_max": 2020, "vfc_thrust_ch": 3, "vfc_roll_ch": 1, "vfc_pitch_ch": 2, "vfc_yaw_ch": 4, "vfc_submode_ch": 6, "vfc_alt_mode_rc_min": 0, "vfc_alt_mode_rc_max": 0, "vfc_flow_mode_rc_min": 0, "vfc_flow_mode_rc_max": 0, "vfc_hybrid_flow_mode_rc_min": 0, "vfc_hybrid_flow_mode_rc_max": 0, "vfc_position_mode_rc_min": 0, "vfc_position_mode_rc_max": 2100, "vfc_traj_mode_rc_min": 0, "vfc_traj_mode_rc_max": 0, "vfc_yaw_deadband": 30, "vfc_vxy_deadband": 50, "vfc_vz_deadband": 150, "vfc_min_thrust": 0, "vfc_max_thrust": 0.800000011920929, "vfc_tilt_max": 0.43599998950958252, "vfc_yaw_rate_max": 3, "vfc_thrust_hover": 0.5, "vfc_vz_max": 1, "vfc_kp_z": 5.2899999618530273, "vfc_kd_z": 5.9800000190734863, "vfc_vxy_max": 3, "vfc_kp_xy": 0.63999998569488525, "vfc_kd_xy": 2.559999942779541, "vfc_kp_z_vio": 5.2899999618530273, "vfc_kd_z_vio": 5.9800000190734863, "vfc_kp_xy_vio": 3.2400000095367432, "vfc_kd_xy_vio": 3.9600000381469727, "vfc_w_filt_xy_vio": 10, "vfc_vel_ff_factor_vio": 0.899999976158142, "vfc_xy_acc_limit_vio": 2.5, "vfc_max_z_delta": 3, "vfc_att_transition_time": 0.5, "vfc_stick_move_threshold": 30, "vfc_flow_transition_time": 1, "vfc_q_min": 10, "vfc_points_min": 7, "vfc_en_submode_announcement": 1, "vfc_disable_fallback": false, "vfc_traj_csv": "/data/voxl-vision-hub/traj.csv", "en_voa": true, "voa_upper_bound_m": -0.15000000596046448, "voa_lower_bound_m": 0.15000000596046448, "voa_voa_memory_s": 1, "voa_max_pc_per_fusion": 100, "voa_pie_max_dist_m": 20, "voa_pie_min_dist_m": 0.25, "voa_pie_under_trim_m": 1, "voa_pie_threshold": 3, "voa_send_rate_hz": 20, "voa_pie_slices": 36, "voa_pie_bin_depth_m": 0.15000000596046448, "voa_inputs": [{ "enabled": true, "type": "point_cloud", "input_pipe": "dfs_point_cloud", "frame": "stereo_l", "max_depth": 8, "min_depth": 0.300000011920929, "cell_size": 0.079999998211860657, "threshold": 4, "x_fov_deg": 68, "y_fov_deg": 56, "conf_cutoff": 0 }, { "enabled": true, "type": "point_cloud", "input_pipe": "stereo_front_pc", "frame": "stereo_front_l", "max_depth": 8, "min_depth": 0.300000011920929, "cell_size": 0.079999998211860657, "threshold": 4, "x_fov_deg": 68, "y_fov_deg": 56, "conf_cutoff": 0 }, { "enabled": true, "type": "point_cloud", "input_pipe": "stereo_rear_pc", "frame": "stereo_rear_l", "max_depth": 8, "min_depth": 0.300000011920929, "cell_size": 0.079999998211860657, "threshold": 4, "x_fov_deg": 68, "y_fov_deg": 56, "conf_cutoff": 0 }, { "enabled": true, "type": "tof", "input_pipe": "tof", "frame": "tof", "max_depth": 6, "min_depth": 0.15000000596046448, "cell_size": 0.079999998211860657, "threshold": 3, "x_fov_deg": 106.5, "y_fov_deg": 85.0999984741211, "conf_cutoff": 125 }, { "enabled": true, "type": "rangefinder", "input_pipe": "rangefinders", "frame": "body", "max_depth": 8, "min_depth": 0.300000011920929, "cell_size": 0.079999998211860657, "threshold": 4, "x_fov_deg": 68, "y_fov_deg": 56, "conf_cutoff": 0 }] } In /etc/modalai/voxl-mavlink-server.conf, changed en_external_ap_timesync to 0 { "primary_static_gcs_ip": "192.168.8.10", "secondary_static_gcs_ip": "192.168.8.11", "onboard_port_to_autopilot": 14556, "onboard_port_from_autopilot": 14557, "gcs_port_to_autopilot": 14558, "gcs_port_from_autopilot": 14559, "en_external_uart_ap": false, "autopilot_uart_bus": 1, "autopilot_uart_baudrate": 921600, "autopilot_mission_delay_start": -1, "autopilot_mission_delay_sound": false, "autopilot_mission_notif_dur": 0.1, "en_external_ap_timesync": 0, "en_external_ap_heartbeat": 1, "udp_mtu": 0, "gcs_timeout_s": 4.5 } In vrpn launch file, remapped vrpn_client_node to mavros/vision_pose/pose with 30Hz update frequency Disabled QVIO and ovins Changed PX4 params: EKF2_EV_CTRL to 11, EKF2_EV_QMIN to 0 voxl2:/$ px4-param show ekf2_ev* Symbols: x = used, + = saved, * = unsaved x EKF2_EVA_NOISE [292,568] : 0.1000 x EKF2_EVP_GATE [293,569] : 5.0000 x EKF2_EVP_NOISE [294,570] : 0.1000 x EKF2_EVV_GATE [295,571] : 3.0000 x EKF2_EVV_NOISE [296,572] : 0.1000 x + EKF2_EV_CTRL [297,573] : 11 x EKF2_EV_DELAY [298,574] : 0.0000 x EKF2_EV_HGT_TO [299,575] : 5000 x EKF2_EV_NOISE_MD [300,576] : 0 x EKF2_EV_POS_TO [301,577] : 1000 x EKF2_EV_POS_X [302,578] : 0.0000 x EKF2_EV_POS_Y [303,579] : 0.0000 x EKF2_EV_POS_Z [304,580] : 0.0000 x EKF2_EV_QMIN [305,581] : 0 829/2162 parameters used. Launched mavros with ModalAI's mavros launch script