@Eric-Katzfey Will try that too. Yeah everything had been working until I completed the tracking cameras calibration procedure and enabled qvio. It also since enablin the qvio the temperature can go up to 70 degrees Celsius.
N
NikosMav
@NikosMav
Posts
-
VOXL2 gyro unresponsive after enabling qvio -
VOXL2 gyro unresponsive after enabling qvio -
VOXL2 gyro unresponsive after enabling qvio@NikosMav Also in QGC no orientation is shown, just the position.
-
VOXL2 gyro unresponsive after enabling qvio@Eric-Katzfey Thank you for your feedback, well it does not seem to respond. This the response I got.
pxh> qshell commander start
INFO [qshell] Send cmd: 'commander start'
INFO [muorb] [uORB] Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO [muorb] [qshell] qshell gotten: commander start
INFO [muorb] [qshell] arg0 = 'commander'
INFO [muorb] [qshell] arg1 = 'start'
INFO [muorb] [tasks] Creating pthread commander
INFO [muorb] [tasks] Successfully created px4 task PX4_commander with tid 2097651
INFO [uORB] Advertising remote topic led_control
INFO [muorb] [commander] LED: open /dev/led0 failed (22)
INFO [uORB] Advertising remote topic tune_control
INFO [muorb] [qshell] Ok executing command: commander start
INFO [qshell] qshell return value timestamp: 62472993, local time: 62475486
pxh> INFO [muorb] [health_and_arming_checks] Too many arming check events (1, 14 > 14). Not reporting all
INFO [uORB] Advertising remote topic event
INFO [uORB] Advertising remote topic mavlink_log
INFO [muorb] [health_and_arming_checks] Preflight Fail: Accel Sensor 0 missing
INFO [muorb] [health_and_arming_checks] Preflight Fail: barometer 0 missing
INFO [muorb] [health_and_arming_checks] Preflight Fail: No CPU load information
INFO [muorb] [health_and_arming_checks] Preflight Fail: ekf2 missing data
INFO [muorb] [health_and_arming_checks] Preflight Fail: Gyro Sensor 0 missing
INFO [muorb] [health_and_arming_checks] Preflight Fail: Compass Sensor 0 missing
INFO [muorb] [health_and_arming_checks] Preflight Fail: system power unavailable
INFO [uORB] Advertising remote topic health_report
INFO [uORB] Advertising remote topic failsafe_flags
INFO [uORB] Advertising remote topic actuator_armed
INFO [uORB] Advertising remote topic vehicle_control_mode
INFO [uORB] Advertising remote topic vehicle_status
INFO [uORB] Advertising remote topic failure_detector_status
INFO [muorb] [health_and_arming_checks] Too many arming check events (1, 14 > 14). Not reporting all
INFO [muorb] [health_and_arming_checks] Preflight Fail: Accel Sensor 0 missing
INFO [muorb] [health_and_arming_checks] Preflight Fail: barometer 0 missing
INFO [muorb] [health_and_arming_checks] Preflight Fail: No CPU load information
INFO [muorb] [health_and_arming_checks] Preflight Fail: ekf2 missing data
INFO [muorb] [health_and_arming_checks] Preflight Fail: Gyro Sensor 0 missing
INFO [muorb] [health_and_arming_checks] Preflight Fail: Compass Sensor 0 missing
INFO [muorb] [health_and_arming_checks] Preflight Fail: system power unavailable
pxh> qshell commander calibrate accel
INFO [qshell] Send cmd: 'commander calibrate accel'
INFO [muorb] [uORB] Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO [muorb] [qshell] qshell gotten: commander calibrate accel
INFO [muorb] [qshell] arg0 = 'commander'
INFO [muorb] [qshell] arg1 = 'calibrate'
INFO [muorb] [qshell] arg2 = 'accel'
INFO [uORB] Advertising remote topic vehicle_command
INFO [muorb] [qshell] Ok executing command: commander calibrate accel
INFO [qshell] qshell return value timestamp: 69545323, local time: 69549068
pxh> INFO [uORB] Advertising remote topic vehicle_command_ack
INFO [uORB] Marking DeviceNode(mavlink_log) as advertised in process_remote_topic
INFO [muorb] [commander] [cal] calibration started: 2 accel
INFO [muorb] [commander] [cal] calibration failed: reading sensor
pxh> qshell commander calibrate gyro
INFO [qshell] Send cmd: 'commander calibrate gyro'
INFO [muorb] [uORB] Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO [muorb] [qshell] qshell gotten: commander calibrate gyro
INFO [muorb] [qshell] arg0 = 'commander'
INFO [muorb] [qshell] arg1 = 'calibrate'
INFO [muorb] [qshell] arg2 = 'gyro'
INFO [uORB] Marking DeviceNode(vehicle_command) as advertised in process_remote_topic
INFO [muorb] [qshell] Ok executing command: commander calibrate gyro
INFO [muorb] [commander] [cal] calibration started: 2 gyro
INFO [qshell] qshell return value timestamp: 75230319, local time: 75237494
pxh> INFO [muorb] [commander] No gyros found -
VOXL2 gyro unresponsive after enabling qvio@Eric-Katzfey It is a custom drone with three tracking cameras and one IMX412. Here is a screenshot with the suite code and the response to the suggested commands.
-
VOXL2 gyro unresponsive after enabling qvioAfter calibrating the cameras and enabling the qvio-server, the gyro meets an error in qgc even if the imu works properly in the portal. Trying to calibrate via qgc but gets stuck because it does not get data from the imus and ends up with error 241. The gyro can be calibrated using voxl-calibrate-imu but the problem persists.
I have to add that I have changed the parameters in a way to allow flight in gps denied environments. Could it be possible that a parameter change led to that?