After Cycling the Power, I can then ARM the Quad. after this list of messages posts:
2/8/2021 3:59:20 PM : PreArm: Hardware safety switch
2/8/2021 3:59:12 PM : EKF2 IMU0 is using GPS
2/8/2021 3:59:12 PM : EKF2 IMU1 is using GPS
2/8/2021 3:58:52 PM : u-blox 1 HW: 00080000 SW: 2.01 (75331)
2/8/2021 3:58:51 PM : PreArm: Hardware safety switch
2/8/2021 3:58:50 PM : GPS: u-blox 1 saving config
2/8/2021 3:58:47 PM : EKF2 IMU1 origin set
2/8/2021 3:58:47 PM : EKF2 IMU0 origin set
2/8/2021 3:58:38 PM : EKF2 IMU1 tilt alignment complete
2/8/2021 3:58:38 PM : EKF2 IMU0 tilt alignment complete
2/8/2021 3:58:37 PM : EKF2 IMU1 initial yaw alignment complete
2/8/2021 3:58:37 PM : EKF2 IMU0 initial yaw alignment complete
2/8/2021 3:58:35 PM : GPS 1: detected as u-blox at 115200 baud
2/8/2021 3:58:34 PM : Barometer 1 calibration complete
2/8/2021 3:58:33 PM : Calibrating barometer
**I have conducted mag. calibration more than once in an open area using Mavlink (RF) to reduce influence of metal objects. I have tried recal of the TX and several and ACC recal. Nothing seems to fix this issue except power cycle.
amilcarlucas, I do not think it is a temp. issue. I have tried power up and letting it set for 15 min., no change, I still have to power cycle before I can ARM.
amilcarlucas, thanks for the info., you are the 1st that has been willing to confirm this issue. Isn’t this something that should be addressed in a PR??
Yeah same here @acsrandd1 today I change fw 4.0.3 to 4.0.6 after I saw this messages every power cycle.
Also there is lots of altitude various , i will be post video later
Also disable safety switch , every time accel calibration , and main thing is mag calibration only on “>40sec” how it’s possible , and when I try to some variance then , same time no any issues with the green bar all the way top of green bar
Moksh, I have actually been posting about this issue in one form or another for about 2 months and finally some people are starting to pay attention and respond. So, thanks for responding!
In my opinion, Pre-Arm checks are critical to a good design. Without pre-arm checks the probability of failure becomes excessively high.
Part of my frustration with this particular problem is no one was responding to my queries. I was beginning to think this may be a significant issue that may lead to some major event and eventual mishap. Finally, a few people have begun to respond and now I have a better perspective on the problem i.e. realization this is sort of just how it is, which I can work with!
With that said, I know the dev. guys have a lot on their plate resolving more important issues. But, it does seem to make sense that this issue could be resolved. I am simply suggesting it be put on the list of things to resolve, not a high priority, but still an item that should be addressed at some point.
