I am a high school teacher working with a group of students to design and build a quad copter camera platform. The students have done a super job designing their own frame and mounting all the hardware. The copter flies extremely well in stabilize mode, but it does not follow a flight plan at all. It lingers in the general vicinity and climbs, but does not make a genuine effort to get to the waypoints. We have increased the waypoint P value but it does not appear to have any affect. We will download and analyze the log files tomorrow, but wanted to know if there are any suggestions for how to proceed to analyze this problem.
Sounds like a bad eeprom to me.
It's a long shot, maybe bad telemetry? If you read/write over USB and it does the same thing, then I'd definitely say your poor drone has irreparable brain damage and needs a new APM.
That would be my third APM with the same issue...is that likely?
I must have posted this question in the wrong section of the forum so here it is again as it pertains to APM planner:
I've been getting inconsistent results with the on board logger. My last flight was recorded just fine with the ground station, but APM never recorded the flight. The weird thing is that I had cleared the logs prior to the flight and when I tried to download the log, I got 2 completely worthless logs and a 3rd one which was just waypoints from an older flight.
The next day I ran into the same issue again.
I had a great flight in the morning with the onboard logger working just fine. Landed, downloaded the log, cleared the log. I then turned everything off for a few hours. I went out again in the evening for a quick flight. Loaded a new mission with 2 waypoints. Landed and there were no log to be downloaded again!?! Furthermore the plane could not hold an RTL circle and did not come back from it's intended waypoints. I had to fly it back manually. I'm not sure if those are related issues or not.
Attached is the ground control station log of that flight.
OK now I have tried a number of different tests. The most significant is that when I configure either of my ArduPilot boards for my plane and load and read way points they write and read correctly, but when I load the ArduCopter firmware they start to act flaky when writing and reading waypoints. So it appears to me to be a problem with the ArduCopter version of the firmware. Any thoughts?
What version of ArduCopter are you using? Please upgrade to 2.1 and try again. The EEPROM will clear automatically when you load the new firmware, ensuring a clean slate.
Logging issues have been fixed in the latest code. Please update and try again.
I loaded APM planner 1.1.9 and I've been using ArduPlane 2.26. I went through the eeprom clearing procedure as well as radio calibration and mode setups. I then re-entered my PIDs manually. The weird thing is that I'm getting very large rudder throws now while rolling APM in stabilize mode. It's not something I had before. Yaw settings are all set to 0:
I haven't tested the plane in flight yet so I'm not sure how it will react to those changes.
PID values have nothing to do with the Mission Planner. They're set by default in the firmware, and then modified manually or if you load a new configuration file. If you have a config file, reload that, or load one of the standard ones.
I reloaded the exact same PID values I had previously yet I'm still getting this weird change. In any case I'll give it a test flight to see how it reacts to this.
in "other mix's" look at rudder mix. change it to 0.
OK we're back from Winter Break and have updated the Mission Planner to 1.1.17 and AdruCopter 2.1.0. We are still getting Write/Read errors. Now all the bogus waypoints are Land commands. Still not getting reliable results. Any thoughts??