you are super. auto task scheduling Do you have any work on Wpnav Radius determination command for each waypoint?
Ok you should try 3rd, 4th and 5th IMUs if using MP
@andyp1per
The results are in:
3rd. IMU
4th. IMU
5th. IMU
Would appear itâs the ICM-42670-P thatâs causing the trouble
Something is not right here - I donât see a picture with just the 42688 enabled. Can you try 1st and then 2nd gyro to see if it comes out as one of those?
@andyp1per
Hope you can make sense of this,âŚcause I certainly canât.
Did check those other two and would appear itâs the 2nd. and the 5th. that are causing trouble. - No idea how that works,âŚunless sensor ID/ signal channel is somehow doubled up.
1st. IMU
2nd. IMU
So, Iâve figured If the 2nd. the 5th. are bad, what would happen if I activated the others?
1st, 3rd, & 4th IMU
UPDATE: After trying all sort of combinations Iâve discovered that the HWID page doesnât always update despite Pixhawk being re-booted after each change.
âŚmy head is spinning now. May have to double check some settings again tomorrow.
The âunable to initialize driverâ message is simply saying it canât find an IMU. Of the settings that give you a single working IMU, which gives you the âgyros not healthyâ message?
@andyp1per
Ok. Just been through all the single IMU options again and been refreshing the HWID page each time.
The outcome:
- The 3rd. and 4th. trigger the âgyro unhealthyâ message
- The 2nd., 5th.,6th.,&7th. trigger a âunable to initialize driverâ message
- The interesting thing is the 4th. & 5th. are the only ones with the â58â Dev Type
So, essentially it leaves only the 1st. which doesnât cause any issues at all.
4th.
5th.
On the upside: After disabling the 3rd.&4th IMU I was able to perform a gyro calibration as expected. (using QGC daily) âŚbut I guess not much point with only one sensor working to full extend.