Hi Guys,
I'm relatively new in the APM world so I would appreciate any help or advice.
Recently i upgraded my CX20 with APM MINI V.31 and Ublox M7 (GPS/Compas).
With all modes everything was good until a few days ago when I discovered that the AutoMode and RTL don't execute the mission or return to launch.
I've tried many times with different types of missions and positions but the result was the same...
- The APM reportig is that the AutoMode switch is on but drone always going to loiter (GpsHold), Yaw heading towards the next (first or home) position and it undefined increasing/decreasing the altitude or just stays in the same position and does nothing (loitering).
If I change any other mode she's behavior is as mode expected.
The last try to identify a problem was fatal... I lost 2 ESC's when I tried to control the drone from my Smartphone using ArduPilot (Circle, Guide, Follow, Land..) .0
I checked the settings many times, but no luck to identify the issue.
Attached: The parameters
Thanks in advance,
Kirk
Replies
A flight log from the controller would also help.
Do you have a radio connection to your GCS or only USB connections?
Have you done all the calibrations from the GCS?
What sort of GPS lock are you typically getting?
It sort of sounds like a GPS problem but more info would help.
Hi Mike,
I am sorry for the missing information and the .log file.
Calibrations on all systems are done (RADIO, ESC, GPS, COMPAS etc.). I tried the AutoTune as well but nothing changes.
With the GCS, I don't have any other radio connection except the Bluetooth dongle which is usually off and I use it for uploading the missions (which now doesn't work).For the live flight I used it just to test flight with the DroidPlaner.
The log file is from the last flight where I used the Radio and Bluetooth (DroidPlanner).
By the analysis of the attached log file, I didn't find any strange behavior. GPS is locked, Barometer is OK, Magnetometer is OK. Vibrations are in the acceptable range. The picks in the log are when I landed and on the end when it crashed. During analyzing the logs I am not sure on what should I pay attention so I will appreciate if you analyze my log file so I can understand what to look on in the future analysis.
Cheers,
Kirk
8 1-01-1970 11-00-00 AM.bin
If it loiters OK then it will not be the GPS, but in looking at the log I found this first up.
There were data errors / unreadable data in the log! The data is potentially corrupt and incorrect.
Detected:
126 time corruptions
258 data corruptions
There is not much in the log, have you got most of the logging turned off?
There was only the basics.
The Baro temp and pressure seems inconsistent but that may be due to log corruption.
When you upload a mission, do you read it back to confirm the upload was correct?
I have only had this occur once on an APM clone board and a complete reload of firmware was needed to fix the problem. This was also a clone board that I did not end up using for a commercial hex I was building.
The only other thing I can see is a LOT of mode changes in the log.
Reason?
Hi Mike.
I didn't notice the errors, so your guess is my guess. I'll try do downgrade and upload the 3.2.1 firmware again. I'll test it as soon as the ESC's arrived.
I'm keeping the logging on the basics just to have a log for approx 30-40 min. That is the flying time I have without a gimbal.
Yes, the mission was in the APM when i checked before take off. Mission was with only 4 positions in the same area (square path with same altitude).
I'm thinking of buying an APM MINI PRO. Do you think that is a good idea?
It's a lot of mode changes because I was trying to understand what was going on. I was changing the modes from the DroidPlanner, where I was trying to GUIDE the drone to a specific point and altitude, to follow or to land... As I said earlier, none of that was executed from the APM.
Thanks mate