ERROR [muorb] SLPI: MAG #0 failed: TIMEOUT!
-
@Will Also, what type of drone you you have? What are the specifics of your hardware configuration?
-
@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 -
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 MCUwhat 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 ----------------------------------- -
@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 :
-
No valid data from Compass 0 on SDK 1.1.2 :
-
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
-
@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?
-
@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.
-
@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.
-
@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 -
@tom @Eric-Katzfey I have the same problem, did you fix it? if yes, how did you fix it?
-
@Amin-Bassiri Did you try my above suggestion using the latest SDK release?
-
@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
-
@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