log file attached.....running AC3.3.1 on Pix, was in loiter then guided mode just hovering at 5m for a while, all good, then sent the land command thru GCS and it just accelerated wildly to the right eventually ramming into my car and then into the ground, GPS masts broken, broken arm and motor mount, and nice gash on my car's door....
what the heck is Err: 0-44 mean? never seen that before but it happned just before I issued the land cmd, I dont see any mechanical issues and thou it appears there is some EKF issue right after the Err: 0-44 I dont see any specific EKF error
Randy or Leornard? please help! thanks
I did experiment with a second GPS puck, and found the response you mentioned. The M7 acquires sats much quicker, but doesn't match the M8 in performance. For the first 3-5 minutes in a new location, the 2nd sat would be primary. Once the better unit acquired 2 more sats, it would be primary reporting,and the vehicle would think it is 3 meters where it last thought.
I envisioned that if I ever lost my masted puck, I would have a second as backup. Unfortunately that behavior of a several meter jump would not be a viable mitigation. I never flew it for that reason.
I second that and thought the same thing.
After further research I found that glitch protection is in EKF and is more configurable. See Bill B's explination below and the EKF-Glitch params. Ivan's problem was a second GPS and a switch over at a bad time. You would think that a GPS switch would be the same thing as a glitch, but I don't know. It may not be. Maybe EKF needs to address this issue. Don't use a 2nd gps until this is fixed.
and I replied to him to let him know this is not the case, what he was seeing was the vehicle impacting my truck and rolling 180 when doing so....there was no mechanical issue at all
Make sure your throttle is set to 0 when you initiate auto land or if your auto mission has auto land as a final waypoint.
my two cent, when your UAV is 10m above the land ground, this is very critical moment. because all the satellites you tracking in the open sky now changes very dynamically when you are approaching house, car, mirror, lake, trees, since these objects can bring lot's signal noise and multipath and also block some good GDOP, HDOP satellites. GDOP or HDOP highly depend on your satellites span and volume. sometimes you only have 60 degree open sky in landing zone, the HDOP and GDOP will be very bad suddenly.
we are developing low cost RTK for UAV. Then you can setup a Base station in open sky (such as in your roof, or yard). and you can test the UAV with Rover installed. if the Rover give you very accurate height in you targeted landing zone, then you can the confidence to use RTK to auto landing. we are tracking tree constellation, GPS, GLONASS, Beidou, ,and both L1 and L2 frequency. which is more stable than usual GPS.
checkout our website: tersus-gnss.com, I also attach some features here.
Triple constellations, 5 frequencies support (GPSL1/L2+BDS B1/B3+GLONASSL1);
192 GNSS channels;
Centimeter level positioning accuracy;
Rapid RTK integer ambiguity resolution;
Up to10 Hz position/velocity/time solutions;
Low power consumption;
Compact design – 60mm x 130mm;
Dual COM interfaces in TTL logic level;
External antenna input through SMA connector;
Data output: NMEA-0183;
Correction: RTCM 2.x/3.x and CMR
Have you ruled out multipath issues?
Signal multipath: Errors can be introduced when signals are reflected of buildings of geographical entities such as large rocks, etc. As the less direct path will be longer and take extra time, this can add errors into the system if the receiver recognizes the reflected signal.
i.e. reflection from windows of house, car, etc.
actually i think i have no other left but to blame this on multipath issue....because of the low altitude i was flying at.
the crazy thing is i have duplicated the landing scenario which caused the crash like 10 more times since then and not even a glitch....nothing...works flawlesly...
I guess lesson learnt, auto landing is risky and 2 GPS is not safe yet