Hi @Alex-Kushleyev @modaltb @Eric-Katzfey
I still have the same error when i use my custom board. Could you verify my board pinouts.
Posts made by Jetson Nano
-
RE: FLIR LEPTON 3.5 Thermal camera with VOXL 2posted in Ask your questions right here!
-
RE: microhard integration with voxl2, not able to get the data.posted in Ask your questions right here!
@tom I had an additional query , when i connect the microhard ground module to the windows system, I am able to get the portal on browser through the ip address 192.168.168.100. when I assign the ip to the QGC, it is not loading.
This was not an issue in ubuntu, in ubuntu the QGC was loading automatically. -
RE: M0173 dual tracking camera errorposted in Ask your questions right here!
@Alex-Kushleyev, I using voxl2 with M0173 board with camera config 29.
The errors are now solved, I made the necessary changes and reconfigured every server and pipeline and calibrated the cameras. -
RE: M0173 dual tracking camera errorposted in Ask your questions right here!
@tom @Alex-Kushleyev @Eric-Katzfey
I calibrated the camera, now i am not getting error while running the qvio-server, but different debug messagevoxl2:~$ voxl-qvio-server loading config file ================================================================= odr_hz: 30.000 use_camera_height_bootstrap: 1 camera_height_off_ground_m: 0.085 enable_init_while_moving: 0 cam_imu_timeshift_s: 0.000 cam_imu_timeshift_s_uncertainty: 0.000 T_cam_wrt_imu_uncertainty: 0.001 0.001 0.001 R_cam_to_imu_uncertainty: 0.005 0.005 0.005 accl_fsr_ms2: 156.000 gyro_fsr_rad: 34.000 accl_noise_std_dev: 0.316 gyro_noise_std_dev: 0.010 cam_noise_std_dev: 100.000 min_std_pixel_noise: 0.500 fail_high_pixel_noise_points: 1.665 limited_imu_bw_trigger: 25.000 gps_imu_time_alignment_s: 0.000 T_gps_wrt_imu: 0.000 0.000 0.000 enable_mapping: 1 enable_gps_vel: 0 en_auto_reset: 1 auto_reset_max_velocity: 10.000 auto_reset_max_v_cov_instant: 0.100 auto_reset_max_v_cov: 0.010 auto_reset_max_v_cov_timeout_s: 0.500 auto_reset_min_features: 3 auto_reset_min_feature_timeout_s: 1.000 en_standby_mode: 1 standby_skip_frames: 1 mask_file_path: vio_cam config: cam 0: enable: 1 name: tracking_front pipe_for_preview: tracking_front pipe_for_tracking: tracking_front_misp_norm is_occluded_on_ground: 0 imu: imu_apps is_extrinsic_present: 1 extrinsic cam wrt imu: parent: imu_apps child: tracking_front T_cam_wrt_imu: 0.037 0.000 0.001 RPY_imu_to_cam: 0.0 90.0 90.0 R_cam_to_imu: 0.000 -0.000 1.000 1.000 0.000 -0.000 -0.000 1.000 0.000 cal file: opencv_tracking_front_intrinsics.yml is_cal_present: 1 cam cal intrinsics: width: 1280 height: 800 fx: 460.295 fy: 462.185 cx: 635.691 cy: 396.209 n_coeffs: 4 is_fisheye: 1 D: 0.0752 -0.0103 0.0157 -0.0074 ================================================================= existing instance of qvio-server found, attempting to stop it thread is locked to cores: 4 5 6 7 waiting for imu waiting for cam connected to imu server waiting for cpu_monitor connected to camera server Connected to cpu-monitor Client requested hard reset WARNING failed to init in time, trying again WARNING failed to init in time, trying again Client requested hard reset WARNING failed to init in time, trying again Client requested hard reset Client requested hard resetStill I am not able to get data from voxl-mapper. how can I use the vio data from open-vins-server rather qvio-server
voxl2:/$ voxl-mapper Loading our own config file Loading extrinsics config file existing instance of voxl-mapper found, attempting to stop it Trying to init tsdf server created tsdf server waiting for server at /run/mpa/vvhub_body_wrt_fixed/ waiting for server at /run/mpa/tof Connected to VIO server Initializing ESDF structs Connected to depth pipe ESDF Thread is now locked to the following cores: 4 5 6 INFO waiting for VIO to start INFO waiting for VIO to start INFO waiting for VIO to start INFO waiting for VIO to start INFO waiting for VIO to start -
RE: VOXL FPV Racing 4-in-1 ESC with flight core v2 and voxl2posted in Ask your questions right here!
@Alex-Kushleyev Thank you for the support. I will make the changes you have mentioned.
-
RE: VOXL FPV Racing 4-in-1 ESC with flight core v2 and voxl2posted in Ask your questions right here!
@Alex-Kushleyev Thank you for the help . I changed the parameter and now the ESC has been initialised. motor are able to rotate.
Also is there any other parameter i should be aware of -
RE: VOXL FPV Racing 4-in-1 ESC with flight core v2 and voxl2posted in Ask your questions right here!
@Alex-Kushleyev here you had mentioned a version where the change has been made with respect to the delay.
https://forum.modalai.com/post/21951 -
RE: VOXL FPV Racing 4-in-1 ESC with flight core v2 and voxl2posted in Ask your questions right here!
@Alex-Kushleyev
Yes it is running in the 250k baud rate.
I did not verify with the voxl-esc tools. I directly connected it to the FC.
I am using the voxl-fpv-dev version of px4 -
RE: VOXL FPV Racing 4-in-1 ESC with flight core v2 and voxl2posted in Ask your questions right here!
nsh> voxl_esc stop ERROR [voxl_esc] timeout, forcing stop ERROR [voxl_esc] failed restoring uart to original state ERROR [voxl_esc] error closing uart nsh> voxl_esc start ERROR [px4_work_queue] wq:ttyS4 not available ERROR [px4_work_queue] init failed INFO [voxl_esc] Starting VOXL ESC driver INFO [voxl_esc] Params: VOXL_ESC_CONFIG: 1 INFO [voxl_esc] Params: VOXL_ESC_MODE: 0 INFO [voxl_esc] Params: VOXL_ESC_BAUD: 250000 INFO [voxl_esc] Params: VOXL_ESC_FUNC1: 101 INFO [voxl_esc] Params: VOXL_ESC_FUNC2: 104 INFO [voxl_esc] Params: VOXL_ESC_FUNC3: 102 INFO [voxl_esc] Params: VOXL_ESC_FUNC4: 103 INFO [voxl_esc] Params: VOXL_ESC_SDIR1: 0 INFO [voxl_esc] Params: VOXL_ESC_SDIR2: 0 INFO [voxl_esc] Params: VOXL_ESC_SDIR3: 0 INFO [voxl_esc] Params: VOXL_ESC_SDIR4: 0 INFO [voxl_esc] Params: VOXL_ESC_RPM_MIN: 5500 INFO [voxl_esc] Params: VOXL_ESC_RPM_MAX: 15000 INFO [voxl_esc] Params: VOXL_ESC_T_PERC: 90 INFO [voxl_esc] Params: VOXL_ESC_T_DEAD: 20 INFO [voxl_esc] Params: VOXL_ESC_T_EXPO: 35 INFO [voxl_esc] Params: VOXL_ESC_T_MINF: 0.150000 INFO [voxl_esc] Params: VOXL_ESC_T_COSP: 0.990000 INFO [voxl_esc] Params: VOXL_ESC_VLOG: 0 INFO [voxl_esc] Params: VOXL_ESC_PUB_BST: 1 INFO [voxl_esc] Params: VOXL_ESC_T_WARN: 0 INFO [voxl_esc] Params: VOXL_ESC_T_OVER: 0 INFO [voxl_esc] Params: GPIO_CTL_CH: 0 nsh>can you verify whether it is a parameter related error. I have mentioned the parameters in the above thread.
-
RE: VOXL FPV Racing 4-in-1 ESC with flight core v2 and voxl2posted in Ask your questions right here!
@Alex-Kushleyev When I run it for sometime it is makes the ESC blink once.
then once again if I run the command it gives the following statement
Error [voxl_esc] Task already running -
RE: VOXL FPV Racing 4-in-1 ESC with flight core v2 and voxl2posted in Ask your questions right here!
Voxl2 is connected to Flight core v2 through telem 1.
ESC is connected to flight core through telem 2.
the parameters are the following
-
RE: VOXL FPV Racing 4-in-1 ESC with flight core v2 and voxl2posted in Ask your questions right here!
@Alex-Kushleyev Thank you for reverting back. I will verify this and get back.
I changed the firmware version to the
voxl-fpv-devstill the FC is not detecting the ESC.if i start esc through voxl_esc start , it is starting
could please verify the parameters I mentioned.
nsh> voxl_esc status INFO [voxl_esc] Max update rate: 0 Hz INFO [voxl_esc] Outputs on: no INFO [voxl_esc] UART port: /dev/ttyS4 INFO [voxl_esc] UART open: no INFO [voxl_esc] INFO [voxl_esc] Params: VOXL_ESC_CONFIG: 1 INFO [voxl_esc] Params: VOXL_ESC_MODE: 0 INFO [voxl_esc] Params: VOXL_ESC_BAUD: 250000 INFO [voxl_esc] Params: VOXL_ESC_FUNC1: 101 INFO [voxl_esc] Params: VOXL_ESC_FUNC2: 104 INFO [voxl_esc] Params: VOXL_ESC_FUNC3: 102 INFO [voxl_esc] Params: VOXL_ESC_FUNC4: 103 INFO [voxl_esc] Params: VOXL_ESC_SDIR1: 0 INFO [voxl_esc] Params: VOXL_ESC_SDIR2: 0 INFO [voxl_esc] Params: VOXL_ESC_SDIR3: 0 INFO [voxl_esc] Params: VOXL_ESC_SDIR4: 0 INFO [voxl_esc] Params: VOXL_ESC_RPM_MIN: 5500 INFO [voxl_esc] Params: VOXL_ESC_RPM_MAX: 15000 INFO [voxl_esc] Params: VOXL_ESC_T_PERC: 90 INFO [voxl_esc] Params: VOXL_ESC_T_DEAD: 20 INFO [voxl_esc] Params: VOXL_ESC_T_EXPO: 35 INFO [voxl_esc] Params: VOXL_ESC_T_MINF: 0.150000 INFO [voxl_esc] Params: VOXL_ESC_T_COSP: 0.990000 INFO [voxl_esc] Params: VOXL_ESC_VLOG: 0 INFO [voxl_esc] Params: VOXL_ESC_PUB_BST: 1 INFO [voxl_esc] Params: VOXL_ESC_T_WARN: 0 INFO [voxl_esc] Params: VOXL_ESC_T_OVER: 0 INFO [voxl_esc] Params: GPIO_CTL_CH: 0 INFO [voxl_esc] INFO [voxl_esc] -- ID: 0 INFO [voxl_esc] Motor: 1 INFO [voxl_esc] Direction: 1 INFO [voxl_esc] State: 0 INFO [voxl_esc] Requested: 0 RPM INFO [voxl_esc] Measured: 0 RPM INFO [voxl_esc] Command Counter: 0 INFO [voxl_esc] Voltage: 0.000000 VDC INFO [voxl_esc] INFO [voxl_esc] -- ID: 1 INFO [voxl_esc] Motor: 4 INFO [voxl_esc] Direction: 1 INFO [voxl_esc] State: 0 INFO [voxl_esc] Requested: 0 RPM INFO [voxl_esc] Measured: 0 RPM INFO [voxl_esc] Command Counter: 0 INFO [voxl_esc] Voltage: 0.000000 VDC INFO [voxl_esc] INFO [voxl_esc] -- ID: 2 INFO [voxl_esc] Motor: 2 INFO [voxl_esc] Direction: 1 INFO [voxl_esc] State: 0 INFO [voxl_esc] Requested: 0 RPM INFO [voxl_esc] Measured: 0 RPM INFO [voxl_esc] Command Counter: 0 INFO [voxl_esc] Voltage: 0.000000 VDC INFO [voxl_esc] INFO [voxl_esc] -- ID: 3 INFO [voxl_esc] Motor: 3 INFO [voxl_esc] Direction: 1 INFO [voxl_esc] State: 0 INFO [voxl_esc] Requested: 0 RPM INFO [voxl_esc] Measured: 0 RPM INFO [voxl_esc] Command Counter: 0 INFO [voxl_esc] Voltage: 0.000000 VDC INFO [voxl_esc] voxl_esc: cycle: 0 events, 0us elapsed, 0.00us avg, min 0us max 0us 0.000us rms voxl_esc: output update interval: 0 events, 0.00us avg, min 0us max 0us 0.000us rms INFO [mixer_module] Param prefix: VOXL_ESC control latency: 0 events, 0us elapsed, 0.00us avg, min 0us max 0us 0.000us rms Channel Configuration: Channel 0: func: 0, value: 0, failsafe: 0, disarmed: 0, min: 5500, max: 15000 Channel 1: func: 0, value: 0, failsafe: 0, disarmed: 0, min: 5500, max: 15000 Channel 2: func: 0, value: 0, failsafe: 0, disarmed: 0, min: 5500, max: 15000 Channel 3: func: 0, value: 0, failsafe: 0, disarmed: 0, min: 5500, max: 15000 -
RE: M0173 dual tracking camera errorposted in Ask your questions right here!
@tom Yes I am using the starling 2 drone. I changed the camera modules to the latest cameras with M0173 board.
where will I find the serial number? -
RE: M0173 dual tracking camera errorposted in Ask your questions right here!
@Alex-Kushleyev can you please share the calibration file opencv_tracking_open_intrinsics.yml and opencv_tracking_down_intrinsics.yml.
-
RE: VOXL FPV Racing 4-in-1 ESC with flight core v2 and voxl2posted in Ask your questions right here!
@Eric-Katzfey i am using http://voxl-packages.modalai.com/dists/fc-v2/dev/modalai_fc-v2_1.14.0-2.0.95.px4 version and also tried with http://voxl-packages.modalai.com/dists/fc-v2/dev/modalai_fc-v2_1.14.0-2.0.90.px4.
The ESC should start blinking blue LED to represent achieving data from FC. It is not happening. -
VOXL FPV Racing 4-in-1 ESC with flight core v2 and voxl2posted in Ask your questions right here!
Hello @Eric-Katzfey @Alex-Kushleyev @tom
I am using voxl2 , with flight core v2 and VOXL FPV Racing 4-in-1 ESC. I would like to know how to setup this pipeline. what are the parameters that requires to be changed and what are values.
could anyone help me this approach
The Flight controller is not recognising the ESC. -
M0173 dual tracking camera errorposted in Ask your questions right here!
Hello @Alex-Kushleyev @Eric-Katzfey @tom @modaltb can anyone help me with this error.
I am using the sdk 1.4.0 with the m0173 board with the configuration 29. While I run the voxl-qvio server I am getting error of missing files both opencv_tracking_front_intrinsics.yml and opencv_tracking_down_intrinsics.yml. even after manually placing them there are other errors occuring.voxl2:/$ voxl-qvio-server loading config file ================================================================= odr_hz: 30.000 use_camera_height_bootstrap: 1 camera_height_off_ground_m: 0.085 enable_init_while_moving: 0 cam_imu_timeshift_s: 0.000 cam_imu_timeshift_s_uncertainty: 0.000 T_cam_wrt_imu_uncertainty: 0.001 0.001 0.001 R_cam_to_imu_uncertainty: 0.005 0.005 0.005 accl_fsr_ms2: 156.000 gyro_fsr_rad: 34.000 accl_noise_std_dev: 0.316 gyro_noise_std_dev: 0.010 cam_noise_std_dev: 100.000 min_std_pixel_noise: 0.500 fail_high_pixel_noise_points: 1.665 limited_imu_bw_trigger: 25.000 gps_imu_time_alignment_s: 0.000 T_gps_wrt_imu: 0.000 0.000 0.000 enable_mapping: 1 enable_gps_vel: 0 en_auto_reset: 1 auto_reset_max_velocity: 10.000 auto_reset_max_v_cov_instant: 0.100 auto_reset_max_v_cov: 0.010 auto_reset_max_v_cov_timeout_s: 0.500 auto_reset_min_features: 3 auto_reset_min_feature_timeout_s: 1.000 en_standby_mode: 1 standby_skip_frames: 1 mask_file_path: vio_cam config: cam 0: enable: 1 name: tracking_front pipe_for_preview: tracking_front pipe_for_tracking: tracking_front_misp_norm is_occluded_on_ground: 0 imu: imu_apps is_extrinsic_present: 1 extrinsic cam wrt imu: parent: imu_apps child: tracking_front T_cam_wrt_imu: 0.037 0.000 0.001 RPY_imu_to_cam: 0.0 90.0 90.0 R_cam_to_imu: 0.000 -0.000 1.000 1.000 0.000 -0.000 -0.000 1.000 0.000 cal file: opencv_tracking_front_intrinsics.yml is_cal_present: 1 cam cal intrinsics: width: 640 height: 480 fx: 286.951 fy: 288.010 cx: 339.072 cy: 232.400 n_coeffs: 4 is_fisheye: 1 D: -0.0135 0.0046 0.0000 0.0000 ================================================================= existing instance of qvio-server found, attempting to stop it thread is locked to cores: 4 5 6 7 waiting for imu waiting for cam connected to imu server waiting for cpu_monitor connected to camera server Connected to cpu-monitor ERROR expected 1280x800 img, got 640x480 Image resolution must match what's in the selected lens cal file ERROR expected 1280x800 img, got 640x480 Image resolution must match what's in the selected lens cal file ERROR expected 1280x800 img, got 640x480 Image resolution must match what's in the selected lens cal file ERROR expected 1280x800 img, got 640x480 Image resolution must match what's in the selected lens cal file ERROR expected 1280x800 img, got 640x480 Image resolution must match what's in the selected lens cal file ERROR expected 1280x800 img, got 640x480 Image resolution must match what's in the selected lens cal file ERROR expected 1280x800 img, got 640x480 Image resolution must match what's in the selected lens cal file ERROR expected 1280x800 img, got 640x480 Image resolution must match what's in the selected lens cal file ERROR expected 1280x800 img, got 640x480 Image resolution must match what's in the selected lens cal file ERROR expected 1280x800 img, got 640x480 Image resolution must match what's in the selected lens cal file ERROR expected 1280x800 img, got 640x480 Image resolution must match what's in the selected lens cal file ERROR expected 1280x800 img, got 640x480 Image resolution must match what's in the selected lens cal file ERROR expected 1280x800 img, got 640x480 Image resolution must match what's in the selected lens cal file ERROR expected 1280x800 img, got 640x480 Image resolution must match what's in the selected lens cal file ERROR expected 1280x800 img, got 640x480 Image resolution must match what's in the selected lens cal file ERROR expected 1280x800 img, got 640x480 Image resolution must match what's in the selected lens cal fileand another error is voxl-mapper not starting because of vio error.
which is better qvio or ov.
voxl2:/$ voxl-mapper Loading our own config file Loading extrinsics config file existing instance of voxl-mapper found, attempting to stop it Trying to init tsdf server created tsdf server waiting for server at /run/mpa/vvhub_body_wrt_fixed/ waiting for server at /run/mpa/tof Connected to VIO server Initializing ESDF structs Connected to depth pipe ESDF Thread is now locked to the following cores: 4 5 6 INFO waiting for VIO to start INFO waiting for VIO to start INFO waiting for VIO to start INFO waiting for VIO to start INFO waiting for VIO to start INFO waiting for VIO to startvoxl2:~$ 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.0 -0.0 0.0| INIT | STALLED ERROR validating 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.0 -0.0 0.0| INIT | STALLED ERROR validating 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.0 -0.0 0.0| INIT | STALLED ERROR validating 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.0 -0.0 0.0| INIT | STALLED ERROR validating 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.0 -0.0 0.0| INIT | STALLED ERROR validating 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.0 -0.0 0.0| INIT | STALLED ^C received SIGINT Ctrl-Cvoxl2:~$ voxl-inspect-vio waiting for server dt(ms) | T_imu_wrt_vio (m) |Roll Pitch Yaw (deg)|features|quality| state| 33.3 | 0.00 0.00 0.00| 0.0 -0.0 0.0| 0 | -1% | FAIL |C received SIGINT Ctrl-C closing and exitingvoxl2:~$ voxl-inspect-vio-cams cam 0: enable: 1 name: tracking_front pipe_for_preview: tracking_front pipe_for_tracking: tracking_front_misp_norm is_occluded_on_ground: 0 imu: imu_apps is_extrinsic_present: 1 extrinsic cam wrt imu: parent: imu_apps child: tracking_front T_cam_wrt_imu: 0.039 0.000 0.001 RPY_imu_to_cam: 0.0 90.0 90.0 R_cam_to_imu: 0.000 -0.000 1.000 1.000 0.000 -0.000 -0.000 1.000 0.000 cal file: opencv_tracking_front_intrinsics.yml is_cal_present: 1 cam cal intrinsics: width: 640 height: 480 fx: 286.951 fy: 288.010 cx: 339.072 cy: 232.400 n_coeffs: 4 is_fisheye: 1 D: -0.0135 0.0046 0.0000 0.0000 cam 1: enable: 1 name: tracking_down pipe_for_preview: tracking_down pipe_for_tracking: tracking_down_misp_norm is_occluded_on_ground: 1 imu: imu_apps is_extrinsic_present: 1 extrinsic cam wrt imu: parent: imu_apps child: tracking_down T_cam_wrt_imu: -0.089 -0.007 0.033 RPY_imu_to_cam: 0.0 0.0 180.0 R_cam_to_imu: -1.000 -0.000 0.000 0.000 -1.000 -0.000 0.000 0.000 1.000 cal file: opencv_tracking_down_intrinsics.yml is_cal_present: 1 cam cal intrinsics: width: 640 height: 480 fx: 286.951 fy: 288.010 cx: 339.072 cy: 232.400 n_coeffs: 4 is_fisheye: 1 D: -0.0135 0.0046 0.0000 0.0000 R_imu_apps_to_body: 1.000 -0.000 0.000 0.000 1.000 -0.000 0.000 0.000 1.000| Pipe Name | bytes | wide | hgt |exp(ms)| gain | frame id |t | feature_tracker_overlay | 6144000 | 1280 | 1600 | 0.00 | 0 | 0 | 332.4 | 5.4 | 261.0 | RGB | hires_down_large_color |18495360 | 4056 | 3040 | 33.23 | 6678 | 12245 | 1538.8 | 5.6 | 832.8 | NV12 | hires_down_large_encoded | 2336 | 4056 | 3040 | 33.23 | 6678 | 12247 | 1397.2 | 5.6 | 0.1 | H264 (P) | hires_down_large_grey |12330240 | 4056 | 3040 | 33.23 | 6678 | 12247 | 1369.4 | 5.7 | 557.7 | RAW8 | hires_down_small_color | 1179648 | 1024 | 768 | 33.23 | 6678 | 12251 | 1327.3 | 5.8 | 54.7 | NV12 | hires_down_small_encoded | 64 | 1024 | 768 | 33.23 | 6678 | 12251 | 1312.8 | 5.8 | 0.0 | H264 (P) | hires_down_small_grey | 786432 | 1024 | 768 | 33.23 | 6678 | 12249 | 1296.7 | 5.8 | 36.5 | RAW8 | hires_down_snapshot | 786432 | 1024 | 768 | 33.23 | 6678 | 12211 | 8 | hires_front_large_color |18495360 | 4056 | 3040 | 33.23 | 6678 | 12266 | 1946.7 | 5.5 | 813.1 | NV12 | hires_front_large_encoded | 20304 | 4056 | 3040 | 33.23 | 6678 | 12268 | 1592.5 | 5.4 | 0.8 | H264 (P) | hires_front_large_grey |12330240 | 4056 | 3040 | 33.23 | 6678 | 12268 | 1548.0 | 5.5 | 545.2 | RAW8 | hires_front_small_color | 1179648 | 1024 | 768 | 33.23 | 6678 | 12271 | 1503.0 | 5.6 | 53.2 | NV12 | hires_front_small_encoded | 2496 | 1024 | 768 | 33.23 | 6678 | 12284 | 1545.8 | 6.1 | 0.1 | H264 (P) | hires_front_small_grey | 786432 | 1024 | 768 | 33.23 | 6678 | 12273 | 1532.1 | 5.7 | 36.0 | RAW8 | hires_front_snapshot | 786432 | 1024 | 768 | 33.23 | 6678 | 12233 | 8 | ov_overlay | 2211840 | 1280 | 1728 | 12.00 | 1596 | 12487 | 298.3 | 4.5 | 80.3 | RAW8 | tof_conf | 43200 | 180 | 240 | 0.06 | 0 | 4174 | 149.1 | 9.2 | 3.2 | RAW8 | tof_depth | 43200 | 180 | 240 | 0.06 | 0 | 4174 | 148.8 | 9.2 | 3.2 | RAW8 | tof_ir | 43200 | 180 | 240 | 0.06 | 0 | 4174 | 147.8 | 9.2 | 3.2 | RAW8 | tracking_down | 1024000 | 1280 | 800 | 12.00 | 1596 | 12457 | 189.0 | 14.6 | 119.8 | RAW8 | tracking_down_bayer | 1024000 | 1280 | 800 | 12.00 | 1596 | 12459 | 190.2 | 14.9 | 121.8 | RAW8 | tracking_down_misp_grey | 1024000 | 1280 | 800 | 12.00 | 1596 | 12459 | 189.5 | 14.9 | 121.8 | RAW8 | tracking_down_misp_norm | 1024000 | 1280 | 800 | 12.00 | 1596 | 12458 | 209.6 | 14.6 | 119.8 | RAW8 | tracking_front | 1024000 | 1280 | 800 | 12.00 | 1596 | 12492 | 198.6 | 16.5 | 135.5 | RAW8 | tracking_front_bayer | 1024000 | 1280 | 800 | 12.00 | 1596 | 12491 | 196.6 | 16.5 | 135.5 | RAW8 | tracking_front_misp_grey | 1024000 | 1280 | 800 | 12.00 | 1596 | 12492 | 177.6 | 16.5 | 135.5 | RAW8 | tracking_front_misp_norm | 1024000 | 1280 | 800 | 12.00 | 1596 | 12491 | 201.4 | 16.5 | 135.5 | RAW8 ERROR: only read 0 bytes of data, expected 10240000 | 12.00 | 1596 | 12392 | 8 ERROR: only read 0 bytes of data, expected 1024000voxl2:~$ voxl-inspect-services Scanning services... Service Name | Enabled | Running | CPU Usage ------------------------------------------------------------------- docker-autorun | Disabled | Not Running | modallink-relink | Disabled | Not Running | voxl-auto-logger | Disabled | Not Running | voxl-camera-server | Enabled | Running | 204.0% voxl-cpu-monitor | Enabled | Running | 0.9% voxl-dfs-server | Disabled | Not Running | voxl-elrs-startup | Disabled | Not Running | voxl-feature-tracker | Enabled | Running | 75.7% voxl-flow-server | Disabled | Not Running | voxl-imu-server | Enabled | Running | 3.6% voxl-io-server | Disabled | Not Running | voxl-lepton-server | Enabled | Running | 3.4% voxl-lepton-tracker | Disabled | Not Running | voxl-logger | Disabled | Not Running | voxl-mapper | Enabled | Running | 2.2% voxl-mavcam-manager | Enabled | Running | 0.0% voxl-mavlink-server | Enabled | Running | 1.8% voxl-modem | Disabled | Not Running | voxl-open-vins-server | Enabled | Running | 29.8% voxl-osd | Disabled | Not Running | voxl-portal | Enabled | Running | 1.8% voxl-px4-imu-server | Disabled | Not Running | voxl-px4 | Disabled | Not Running | voxl-qvio-server | Disabled | Not Running | voxl-rangefinder-server | Enabled | Not Running | voxl-remote-id | Disabled | Not Running | voxl-softap | Enabled | Completed | voxl-state-estimator | Disabled | Not Running | voxl-static-ip | Disabled | Not Running | voxl-streamer | Enabled | Running | 0.0% voxl-tag-detector | Disabled | Not Running | voxl-tflite-server | Disabled | Not Running | voxl-time-sync | Disabled | Not Running | voxl-uvc-server | Disabled | Not Running | voxl-vision-hub | Enabled | Running | 3.4% voxl-vrx | Disabled | Not Running | voxl-vtx | Disabled | Not Running | voxl-wait-for-fs | Enabled | Completed |