ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    ERROR [muorb] SLPI: MAG #0 failed: TIMEOUT!

    VOXL 2
    5
    14
    497
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • W
      Will
      last edited by

      Hi,

      I consistently encounter the MAG failed alarm. Upon inspecting the PX4 listener, I observe that the error_count is not 0. Could you assist me in identifying the potential reasons for this error? Thank you.

      voxl2:/$ px4-listener sensor_mag
      TOPIC: sensor_mag
      sensor_mag_s
      timestamp: 277247992 (0.016736 seconds ago)
      timestamp_sample: 277247418 (574 us before timestamp)
      device_id: 396809 (Type: 0x06, I2C:1 (0x0E))
      x: 0.1197
      y: -0.1379
      z: 0.1803
      temperature: nan
      error_count: 42
      is_external: True

      voxl2:/$ voxl-px4
      Found DSP signature file
      INFO [px4] mlockall() enabled. PX4's virtual address space is locked into RAM.
      INFO [px4] assuming working directory is rootfs, no symlinks needed.

      | ___ \ \ \ / / / |
      | |/ / \ V / / /| |
      | __/ / \ / /      | |
      | | / /^\ \ ___ |
      _| / / |_/

      px4 starting.

      INFO [px4] Calling startup script: /bin/sh /etc/modalai/voxl-px4.config 0
      Running on M0054
      INFO [muorb] SLPI: Creating qurt thread hpwork

      INFO [muorb] SLPI: Successfully created px4 task PX4_hpwork with tid 83
      INFO [muorb] SLPI: Creating qurt thread lpwork

      INFO [muorb] SLPI: Successfully created px4 task PX4_lpwork with tid 82
      INFO [muorb] SLPI: Creating qurt thread wkr_hrt

      INFO [muorb] SLPI: Successfully created px4 task PX4_wkr_hrt with tid 81
      INFO [muorb] SLPI: Creating qurt thread client_sync_thread

      INFO [muorb] SLPI: Successfully created px4 task PX4_client_sync_thread with tid 80
      INFO [muorb] SLPI: Creating qurt thread wq_manager

      INFO [muorb] SLPI: Successfully created px4 task PX4_wq_manager with tid 79
      INFO [muorb] SLPI: Creating qurt thread qshell

      INFO [muorb] SLPI: Successfully created px4 task PX4_qshell with tid 78
      INFO [qshell] Send cmd: 'icm42688p start -s'
      INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
      INFO [muorb] SLPI: qshell gotten: icm42688p start -s
      INFO [muorb] SLPI: Creating qurt thread wq_SPI1

      INFO [muorb] SLPI: Successfully created px4 task PX4_wq_SPI1 with tid 77
      INFO [muorb] SLPI: *** SPI Device ID 0x26000a 2490378
      INFO [uorb] Advertising remote topic sensor_accel
      INFO [uorb] Marking DeviceNode(parameter_server_set_used_request) as advertised in process_remote_topic
      INFO [muorb] SLPI: Marking DeviceNode(parameter_server_set_used_response) as advertised in process_remote_to
      INFO [uorb] Advertising remote topic sensor_gyro
      INFO [uorb] Advertising remote topic imu_server
      INFO [muorb] SLPI: on SPI bus 1
      INFO [muorb] SLPI: icm42688p #0 on SPI bus 1 (devid=0x0)
      INFO [muorb] SLPI:

      INFO [muorb] SLPI: Ok executing command: icm42688p start -s
      INFO [muorb] SLPI: Sending qshell retval with timestamp 162829520, current timestamp 162829521
      INFO [uorb] Advertising remote topic qshell_retval
      INFO [qshell] qshell return value timestamp: 162829520, local time: 162832909
      INFO [muorb] SLPI: Marking DeviceNode(parameter_client_reset_request) as advertised in process_remote_topic
      ERROR [muorb] SLPI: Cannot reset all parameters on client side
      INFO [uorb] Marking DeviceNode(parameter_client_reset_response) as advertised in process_remote_topic
      INFO [muorb] SLPI: Advertising remote topic parameter_update
      INFO [muorb] SLPI: Marking DeviceNode(parameter_client_set_value_request) as advertised in process_remote_to
      INFO [uorb] Marking DeviceNode(parameter_client_set_value_response) as advertised in process_remote_topic
      INFO [logger] logger started (mode=all)
      Starting Holybro magnetometer
      INFO [qshell] Send cmd: 'ist8310 start -R 10 -X -b 1'
      INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
      INFO [muorb] SLPI: qshell gotten: ist8310 start -R 10 -X -b 1
      INFO [muorb] SLPI: Creating qurt thread wq_I2C1

      INFO [muorb] SLPI: Successfully created px4 task PX4_wq_I2C1 with tid 75
      INFO [muorb] SLPI: *** I2C Device ID 0x60e09 396809
      INFO [muorb] SLPI: ist8310 #0 on I2C bus 1 (external)

      INFO [muorb] SLPI: Ok executing command: ist8310 start -R 10 -X -b 1
      INFO [muorb] SLPI: Sending qshell retval with timestamp 165852955, current timestamp 165852956
      INFO [qshell] qshell return value timestamp: 165852955, local time: 165853837
      Starting Holybro LED driver
      INFO [qshell] Send cmd: 'rgbled_ncp5623c start -X -b 1 -f 400 -a 56'
      INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
      INFO [muorb] SLPI: qshell gotten: rgbled_ncp5623c start -X -b 1 -f 400 -a 56
      INFO [muorb] SLPI: *** I2C Device ID 0x7b3809 8075273
      INFO [muorb] SLPI: rgbled_ncp5623c #0 on I2C bus 1 (external)

      INFO [muorb] SLPI: Ok executing command: rgbled_ncp5623c start -X -b 1 -f 400 -a 56
      INFO [muorb] SLPI: Sending qshell retval with timestamp 165888791, current timestamp 165888792
      INFO [qshell] qshell return value timestamp: 165888791, local time: 165889480
      INFO [qshell] Send cmd: 'icp10100 start -I -b 5'
      INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
      INFO [muorb] SLPI: qshell gotten: icp10100 start -I -b 5
      INFO [muorb] SLPI: Creating qurt thread wq_I2C5

      INFO [muorb] SLPI: Successfully created px4 task PX4_wq_I2C5 with tid 74
      INFO [muorb] SLPI: *** I2C Device ID 0x9c6329 10249001
      INFO [muorb] SLPI: probe probe succeeded. data = 0x1 0x48
      INFO [muorb] SLPI: icp10100 #0 on I2C bus 5

      INFO [muorb] SLPI: Ok executing command: icp10100 start -I -b 5
      INFO [muorb] SLPI: Sending qshell retval with timestamp 165921057, current timestamp 165921058
      INFO [qshell] qshell return value timestamp: 165921057, local time: 165921609
      INFO [qshell] Send cmd: 'modalai_esc start'
      INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
      INFO [muorb] SLPI: qshell gotten: modalai_esc start
      INFO [muorb] SLPI: Creating qurt thread wq_hp_default

      INFO [muorb] SLPI: Successfully created px4 task PX4_wq_hp_default with tid 73
      INFO [uorb] Advertising remote topic test_motor
      INFO [uorb] Advertising remote topic sensor_mag
      INFO [muorb] SLPI: Ok executing command: modalai_esc start
      INFO [muorb] SLPI: Sending qshell retval with timestamp 165961204, current timestamp 165961204
      INFO [muorb] SLPI: Opened UART ESC device
      INFO [uorb] Advertising remote topic sensor_baro
      INFO [qshell] qshell return value timestamp: 165961204, local time: 165962290
      INFO [qshell] Send cmd: 'mixer load /dev/uart_esc quad_x.main.mix'
      INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
      INFO [muorb] SLPI: qshell gotten: mixer load /dev/uart_esc quad_x.main.mix
      INFO [muorb] SLPI: Creating qurt thread wq_rate_ctrl

      INFO [muorb] SLPI: Successfully created px4 task PX4_wq_rate_ctrl with tid 71
      INFO [muorb] SLPI: Ok executing command: mixer load /dev/uart_esc quad_x.main.mix
      INFO [muorb] SLPI: Sending qshell retval with timestamp 166023373, current timestamp 166023374
      INFO [qshell] qshell return value timestamp: 166023373, local time: 166024932
      INFO [uorb] Advertising remote topic actuator_outputs
      INFO [uorb] Advertising remote topic multirotor_motor_limits
      INFO [qshell] Send cmd: 'voxlpm start -X -b 2'
      INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
      INFO [muorb] SLPI: qshell gotten: voxlpm start -X -b 2
      INFO [muorb] SLPI: Creating qurt thread wq_I2C2

      INFO [muorb] SLPI: Successfully created px4 task PX4_wq_I2C2 with tid 4169
      INFO [muorb] SLPI: *** I2C Device ID 0x784411 7881745
      INFO [uorb] Advertising remote topic battery_status
      INFO [muorb] SLPI: voxlpm #0 on I2C bus 2 (external)

      INFO [muorb] SLPI: Ok executing command: voxlpm start -X -b 2
      INFO [muorb] SLPI: Sending qshell retval with timestamp 166066506, current timestamp 166066507
      INFO [qshell] qshell return value timestamp: 166066506, local time: 166067902
      INFO [uorb] Advertising remote topic power_monitor
      Starting Holybro GPS
      INFO [qshell] Send cmd: 'gps start -d 7 -b 115200'
      INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
      INFO [muorb] SLPI: qshell gotten: gps start -d 7 -b 115200
      INFO [muorb] SLPI: Creating qurt thread gps

      INFO [muorb] SLPI: Successfully created px4 task PX4_gps with tid 70
      INFO [muorb] SLPI: Ok executing command: gps start -d 7 -b 115200
      INFO [muorb] SLPI: Sending qshell retval with timestamp 166109271, current timestamp 166109272
      INFO [qshell] qshell return value timestamp: 166109271, local time: 166110180
      INFO [qshell] Send cmd: 'px4io detect'
      INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
      INFO [muorb] SLPI: qshell gotten: px4io detect
      INFO [muorb] SLPI: serial port fd 2
      ERROR [muorb] SLPI: px4io read failed
      ERROR [muorb] SLPI: px4io io_reg_get(0,0,1): data error -5
      ERROR [muorb] SLPI: IO not installed
      ERROR [muorb] SLPI: Detection attempt 2 failed
      ERROR [muorb] SLPI: Detection attempt 1 failed
      ERROR [muorb] SLPI: Detection attempt 0 failed
      ERROR [muorb] SLPI: Failed to execute command: px4io detect
      INFO [muorb] SLPI: Sending qshell retval with timestamp 166159427, current timestamp 166159428
      INFO [qshell] cmd returned with: -17
      INFO [qshell] qshell return value timestamp: 166159427, local time: 166162532
      ERROR [qshell] Command failed
      M0065 not detected, starting Spektrum RC driver
      INFO [qshell] Send cmd: 'spektrum_rc start -d 8'
      INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
      INFO [muorb] SLPI: qshell gotten: spektrum_rc start -d 8
      INFO [muorb] SLPI: Creating qurt thread spektrum_rc_main

      INFO [muorb] SLPI: Successfully created px4 task PX4_spektrum_rc_main with tid 67
      INFO [muorb] SLPI: Ok executing command: spektrum_rc start -d 8
      INFO [muorb] SLPI: Sending qshell retval with timestamp 166191950, current timestamp 166191951
      INFO [qshell] qshell return value timestamp: 166191950, local time: 166192806
      INFO [qshell] Send cmd: 'sensors start'
      INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
      INFO [muorb] SLPI: qshell gotten: sensors start
      INFO [muorb] SLPI: Creating qurt thread wq_nav_and_controllers

      INFO [muorb] SLPI: Successfully created px4 task PX4_wq_nav_and_controllers with tid 66
      INFO [muorb] SLPI: Ok executing command: sensors start
      INFO [muorb] SLPI: Sending qshell retval with timestamp 167257291, current timestamp 167257292
      INFO [uorb] Advertising remote topic vehicle_angular_acceleration
      INFO [uorb] Advertising remote topic vehicle_angular_velocity
      INFO [qshell] qshell return value timestamp: 167257291, local time: 167259265
      INFO [muorb] SLPI: Creating qurt thread wq_INS0

      INFO [muorb] SLPI: Successfully created px4 task PX4_wq_INS0 with tid 65
      INFO [uorb] Advertising remote topic vehicle_imu
      INFO [uorb] Advertising remote topic vehicle_imu_status
      INFO [uorb] Advertising remote topic sensors_status_imu
      INFO [uorb] Advertising remote topic vehicle_acceleration
      INFO [uorb] Advertising remote topic vehicle_air_data
      INFO [uorb] Advertising remote topic vehicle_magnetometer
      INFO [uorb] Advertising remote topic sensor_preflight_mag
      INFO [uorb] Advertising remote topic sensor_selection
      INFO [uorb] Advertising remote topic sensor_combined
      INFO [qshell] Send cmd: 'ekf2 start'
      INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
      INFO [muorb] SLPI: qshell gotten: ekf2 start
      INFO [muorb] SLPI: Ok executing command: ekf2 start
      INFO [muorb] SLPI: Sending qshell retval with timestamp 167424471, current timestamp 167424471
      INFO [qshell] qshell return value timestamp: 167424471, local time: 167425271
      ERROR [muorb] SLPI: 0 - vehicle_magnetometer lost, generation 0 -> 7
      INFO [uorb] Advertising remote topic ekf2_timestamps
      INFO [qshell] Send cmd: 'mc_pos_control start'
      INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
      INFO [muorb] SLPI: qshell gotten: mc_pos_control start
      INFO [muorb] SLPI: Ok executing command: mc_pos_control start
      INFO [muorb] SLPI: Sending qshell retval with timestamp 167467771, current timestamp 167467772
      INFO [qshell] qshell return value timestamp: 167467771, local time: 167468914
      INFO [qshell] Send cmd: 'mc_att_control start'
      INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
      INFO [muorb] SLPI: qshell gotten: mc_att_control start
      INFO [muorb] SLPI: Ok executing command: mc_att_control start
      INFO [muorb] SLPI: Sending qshell retval with timestamp 167514133, current timestamp 167514134
      INFO [qshell] qshell return value timestamp: 167514133, local time: 167515295
      INFO [qshell] Send cmd: 'mc_rate_control start'
      INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
      INFO [muorb] SLPI: qshell gotten: mc_rate_control start
      INFO [muorb] SLPI: Ok executing command: mc_rate_control start
      INFO [muorb] SLPI: Sending qshell retval with timestamp 167572385, current timestamp 167572386
      INFO [qshell] qshell return value timestamp: 167572385, local time: 167573816
      INFO [qshell] Send cmd: 'mc_hover_thrust_estimator start'
      INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
      INFO [muorb] SLPI: qshell gotten: mc_hover_thrust_estimator start
      INFO [muorb] SLPI: Ok executing command: mc_hover_thrust_estimator start
      INFO [muorb] SLPI: Sending qshell retval with timestamp 167620574, current timestamp 167620575
      INFO [qshell] qshell return value timestamp: 167620574, local time: 167621626
      INFO [qshell] Send cmd: 'land_detector start multicopter'
      INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
      INFO [muorb] SLPI: qshell gotten: land_detector start multicopter
      INFO [muorb] SLPI: Ok executing command: land_detector start multicopter
      INFO [muorb] SLPI: Sending qshell retval with timestamp 167651810, current timestamp 167651811
      INFO [qshell] qshell return value timestamp: 167651810, local time: 167652884
      INFO [uorb] Advertising remote topic vehicle_land_detected
      INFO [muorb] SLPI: 168050471: reset position to last known position
      INFO [muorb] SLPI: 168050471: reset velocity to zero
      INFO [uorb] Advertising remote topic vehicle_local_position
      INFO [uorb] Advertising remote topic vehicle_odometry
      INFO [uorb] Advertising remote topic estimator_states
      INFO [uorb] Advertising remote topic estimator_status
      INFO [uorb] Advertising remote topic estimator_status_flags
      INFO [uorb] Advertising remote topic estimator_innovations
      INFO [uorb] Advertising remote topic estimator_innovation_test_ratios
      INFO [uorb] Advertising remote topic estimator_innovation_variances
      INFO [uorb] Advertising remote topic sensor_gps
      INFO [uorb] Advertising remote topic vehicle_gps_position
      INFO [muorb] SLPI: Advertising remote topic position_setpoint_triplet
      INFO [muorb] SLPI: Advertising remote topic mission
      INFO [commander] LED: open /dev/led0 failed (22)
      INFO [muorb] SLPI: Advertising remote topic led_control
      INFO [muorb] SLPI: Advertising remote topic tune_control
      INFO [PreFlightCheck] Failed EKF health preflight check while waiting for filter to settle
      INFO [muorb] SLPI: Advertising remote topic vehicle_control_mode
      INFO [muorb] SLPI: Advertising remote topic vehicle_status
      INFO [uorb] Advertising remote topic rate_ctrl_status
      INFO [uorb] Advertising remote topic actuator_controls_0
      INFO [muorb] SLPI: Advertising remote topic actuator_armed
      INFO [muorb] SLPI: Advertising remote topic commander_state
      INFO [muorb] SLPI: Advertising remote topic vehicle_status_flags
      INFO [muorb] SLPI: Advertising remote topic vehicle_command
      INFO [commander] Handling Commander command 176
      INFO [muorb] SLPI: Advertising remote topic vehicle_command_ack
      INFO [mavlink] mode: Onboard, data rate: 100000 B/s on udp port 14556 remote port 14557
      INFO [muorb] SLPI: Marking DeviceNode(vehicle_command) as advertised in process_remote_topic
      INFO [uorb] Advertising remote topic estimator_sensor_bias
      INFO [px4] Startup script returned successfully
      pxh> INFO [muorb] SLPI: Advertising remote topic telemetry_status
      INFO [mavlink] partner IP: 127.0.0.1
      INFO [uorb] Advertising remote topic mavlink_log
      ERROR [muorb] SLPI: MAG #0 failed: TIMEOUT!
      INFO [muorb] SLPI: 174279599: EKF aligned, (baro hgt, IMU buf: 12, OBS buf: 9)
      INFO [uorb] Advertising remote topic vehicle_attitude
      INFO [uorb] Advertising remote topic vehicle_attitude_setpoint
      INFO [uorb] Advertising remote topic vehicle_rates_setpoint
      ERROR [muorb] SLPI: MAG #0 failed: TIMEOUT!
      ERROR [muorb] SLPI: MAG #0 failed: TIMEOUT!
      ERROR [muorb] SLPI: MAG #0 failed: TIMEOUT!
      ERROR [muorb] SLPI: MAG #0 failed: TIMEOUT!
      INFO [PreFlightCheck] Failed EKF sensor bias preflight check
      INFO [PreFlightCheck] Failed EKF sensor bias preflight check
      ERROR [muorb] SLPI: MAG #0 failed: TIMEOUT!
      INFO [PreFlightCheck] Failed EKF sensor bias preflight check
      INFO [PreFlightCheck] Failed EKF sensor bias preflight check
      INFO [PreFlightCheck] Failed EKF sensor bias preflight check
      INFO [PreFlightCheck] Failed EKF sensor bias preflight check
      INFO [PreFlightCheck] Failed EKF sensor bias preflight check
      INFO [PreFlightCheck] Failed EKF sensor bias preflight check

      Eric KatzfeyE 2 Replies Last reply Reply Quote 0
      • Eric KatzfeyE
        Eric Katzfey Dev Team @Will
        last edited by

        @Will Can you update you software to the latest SDK 1.1.2 and retry? It looks like you are running much older software.

        W 1 Reply Last reply Reply Quote 0
        • Eric KatzfeyE
          Eric Katzfey Dev Team @Will
          last edited by

          @Will Also, what type of drone you you have? What are the specifics of your hardware configuration?

          E 1 Reply Last reply Reply Quote 0
          • E
            ejohnson01 @Eric Katzfey
            last edited by

            @Eric-Katzfey @Will Are you observing parts of the system become unresponsive or laggy when you see this?

            We have seen that same print out in our issue here.
            https://forum.modalai.com/topic/2927/dsp-tasks-failing-unless-mini-dm-is-run/16

            1 Reply Last reply Reply Quote 0
            • W
              Will @Eric Katzfey
              last edited by Will

              @Eric-Katzfey

              Can you update you software to the latest SDK 1.1.2 and retry? It looks like you are running much older software.

              Here is the sw version I am running, I will try to upgrade to SDK 1.1.2. Additionally, I'm interested in understanding how the error_count is calculated. I may explore checking the SLPI I2C signal using a scope, thanks.

              voxl-version
--------------------------------------------------------------------------------
system-image: 1.5.5-M0054-14.1a-perf
kernel:       #1 SMP PREEMPT Fri Mar 24 00:48:55 UTC 2023 4.19.125
--------------------------------------------------------------------------------
hw version:   M0054
--------------------------------------------------------------------------------
voxl-suite:   0.9.5
--------------------------------------------------------------------------------

pxh> ver all
HW arch: MODALAI_RB5_FLIGHT
FW git-hash: 49dd87bfd8b7f4b4bf3d4f27499ffa1aba251eb0
FW version: 1.12.31 80 (17571712)
OS: Linux
OS version: Release 4.19.125 (68386303)
Build datetime: Oct 26 2022 17:18:59
Build uri: localhost
Toolchain: GNU GCC, 7.5.0
PX4GUID: 10014c474145304449453030303030303030
UNKNOWN MCU

              what type of drone you you have? What are the specifics of your hardware configuration?

              It is sentinel, thanks.

              @ejohnson01 Are you observing parts of the system become unresponsive or laggy when you see this?

              I use voxl-inspect-cpu command to check when there is MAG #0 failed: TIMEOUT, it seems cpu usage is fine, thanks.

              Name   Freq (MHz) Temp (C) Util (%)
-----------------------------------
cpu0        518.4     25.8    20.67
cpu1        518.4     25.4     9.59
cpu2        518.4     25.4     9.19
cpu3        518.4     25.4     8.16
cpu4        710.4     25.4     0.00
cpu5        710.4     25.1     0.00
cpu6        710.4     25.8     0.00
cpu7        844.8     25.8     0.00
Total                 25.8     5.95
10s avg                        5.95
-----------------------------------
GPU         305.0     24.3     0.00
GPU 10s avg                    0.00
-----------------------------------
memory temp:       25.2 C
memory used:   546/7671 MB
-----------------------------------
Flags
CPU freq scaling mode: auto
GPU freq scaling mode: auto
-----------------------------------
              W 1 Reply Last reply Reply Quote 0
              • W
                Will @Will
                last edited by

                @Eric-Katzfey , I've upgraded to SDK 1.1.2, but it has introduced two additional problems. Firstly, the RC is unstable, exhibiting noticeable lag during radio calibration in QGC. I attempted to re-bind the RC using the command "voxl-bind-spectrum -s," but it did not resolve the issue. The second problem is similar to a MAG failure, but it indicates that there is no valid data from Compass 0.

                Upon testing outdoors, I reverted the SDK back to version 0.9.5, and the aforementioned RC issues (lag and instability) disappeared. However, the MAG failure problem reoccurred. It appears that SDK 1.1.2 is affecting the spectrum RC, causing issues. Any guidance or assistance would be greatly appreciated. Thank you.

                • SDK 1.1.2
                system-image: 1.7.1-M0054-14.1a-perf-nightly-20231025
kernel:       #1 SMP PREEMPT Thu Oct 26 03:25:38 UTC 2023 4.19.125
--------------------------------------------------------------------------------
hw version:   M0054
--------------------------------------------------------------------------------
voxl-suite:   1.1.2
--------------------------------------------------------------------------------
current IP: wlan0: 192.168.8.1
--------------------------------------------------------------------------------

                • Spectrum RC missing on SDK 1.1.2 :
                  rc_missing.png

                • No valid data from Compass 0 on SDK 1.1.2 :
                  compass_missing.png

                • SDK 1.1.2 log:
                  https://drive.google.com/file/d/1T3paVD9SX4lIZfHOU7uyfxhiSVxO9uMX/view?usp=sharing
                  https://drive.google.com/file/d/1nXZgMKWIL9RCs5P2ZrMhWi6TfNyA9AjX/view?usp=sharing

                Eric KatzfeyE 1 Reply Last reply Reply Quote 0
                • Eric KatzfeyE
                  Eric Katzfey Dev Team @Will
                  last edited by

                  @Will Do you by any chance have more than one Sentinel? If so, do you see the same issue on the other one(s)? Has this Sentinel been involved in any crashes or has it possibly been damaged in some way? Have you seen these issues ever since you first got the drone or did they start appearing later?

                  W 1 Reply Last reply Reply Quote 0
                  • W
                    Will @Eric Katzfey
                    last edited by

                    @Eric-Katzfey , No, I do not have a spare one. The drone I tested has experienced a crash but can still fly stably with SDK 0.9.5, except for occasional MAG #0 failures. However, upon upgrading to SDK 1.1.2, I encountered issues arming the drone, and when I reverted to SDK 0.9.5 at the same location and time, it was able to arm and fly without any problems. Therefore, I believe the issue is not related to the drone itself but may be attributed to differences between SDK 0.9.5 and SDK 1.1.2 concerning the DSMX Spectrum RC. Please assist in investigating this matter. Thank you.

                    Eric KatzfeyE 1 Reply Last reply Reply Quote 0
                    • Eric KatzfeyE
                      Eric Katzfey Dev Team @Will
                      last edited by

                      @Will We test this configuration and haven't seen these issues so I'm guessing that there has been some sort of an issue with the upgrade to SDK 1.1.2 and there is some conflict with files from the previously installed SDK. Most of the team is still out on holiday but when they return next week I'll have someone post instructions on how to do an SDK 1.1.2 installation that attempts to clean out all old files.

                      tomT 1 Reply Last reply Reply Quote 0
                      • tomT
                        tom admin @Eric Katzfey
                        last edited by

                        @Eric-Katzfey @Will In order to do a full factory flash that wipes all partitions and resets them to a factory state, you can do the following:

                        Note the "-w" flag being passed to the install script:

                        cd voxl2_SDK_1.1.2
install.sh -w
                        Amin BassiriA 1 Reply Last reply Reply Quote 0
                        • Amin BassiriA
                          Amin Bassiri @tom
                          last edited by

                          @tom @Eric-Katzfey I have the same problem, did you fix it? if yes, how did you fix it?

                          tomT 1 Reply Last reply Reply Quote 0
                          • tomT
                            tom admin @Amin Bassiri
                            last edited by

                            @Amin-Bassiri Did you try my above suggestion using the latest SDK release?

                            Amin BassiriA 1 Reply Last reply Reply Quote 0
                            • Amin BassiriA
                              Amin Bassiri @tom
                              last edited by

                              @tom Yes I'm using the latest SDK, also, my drone can not go to position mode in the outdoor, I changed the parameter for outdoor (px4 parameter), just when I used VIO can use position mode, but sometimes Vio lost the position, we have problem in outdoor navigation. we have 7 drones (RB5) in THI university all of them has same issue

                              tomT 1 Reply Last reply Reply Quote 0
                              • tomT
                                tom admin @Amin Bassiri
                                last edited by tom

                                @Amin-Bassiri Can you open a new thread describing your issue? It'll make it so the rest of the team gets eyes on it

                                1 Reply Last reply Reply Quote 0
                                • First post
                                  Last post
                                Powered by NodeBB | Contributors