I can concur. I was the ardufan ;-).
First attempt we waited for 3D fix before arming. The wiki mentions this.
Then lifted off and flew a couple of metres and switched to RTL.The quad went left forward in the other direction from where we armed.
To make sure we turned 180 degrees and did the same test. Again it flew left forward.
Next, with MP we manualy entered the home position and redid the test. Same result. Can't figure this one out.
Please post the logs.
See logs attached. Hopefully it can shed some light on the issue.
Very Curious as well. I have tried RTL via channel 7 a few times. In all cases waited for a blue GPS lock, armed motors an few straight ahead about 100 feet in the same direction. Hit RTL and quad did anything but fly straight back as expected. It went right one time, left, away ect.. nothing predictable. Furthermore its unpredictability was a quite a high rate of speed which was fun to wrestle with :)
I will try again as I just figured out how to get logging working and see if the results are similar. (My dataflash card was giving me a problem).
I had this happen in the very early days.
Have you verified the magnometer is working correctly.
In my case it was not and the quad just flew away.
Luckily it hit a tree before it got too far.
Also make sure you have got a solid red light on the oilpan, not just solid blue on the gps.
By the way the magnometer is my most troublesome piece of equipment.
Will surely check the solid red light on the oilpan next time. That's easy.
Do you have a quick check for the magnometer? How to quickly check it?
Good idea about the hand-test. I did that with my tradHeli when I was first trying loiter.
You probably saw my other post to Doug 2 minutes ago but I think you also don't have a mag? Or maybe it hasn't been enabled in the APMissionPlanner's Firmware, APMSetup, Hardware Options screen? It should be enabled by default but when I look at your logs i see a zero mag number.
The way to see this is to open up the APMissionPlanner, push the Terminal button on the top right. Then click the "Log Browse" button, then select the file you posted above. Then find an ATT line (first column), and then scroll over to the Mag Heading column and click the "Graph this button" button...you'll see it's a flat line.
This is what it shoudl look like. It's a bit insane looking but that's the compass heading * 100.
Thanks Lloyd. I can confirm my mag is working, at least without the motors running. My problems are occurring with APM2.
I've engaged the RTL on my Hex a couple of times and watched as it took off due north and down with the RTL point set due west. I had GPS lock for nearly 2 minutes, armed and flew east and up probably 100 meters each and engaged RTL to watch it make a mad dash for some very tall trees to the north. I let it go for what seemed like a long time, just to see if it would correct and just prior to smashing into the trees I switched back to stab mode and recovered the Hex maybe 30 feet short of the tree line. I probably came down 50 meters and went north 75 meters. After this I landed, disarmed, disconnected the battery and fired it all back up and tried again, with nearly the same result.( I decided to abort the RTL much sooner on the second attempt).
I don't have a magnetometer, is one required for RTL? Are there some PID settings that will slow the pace of the mad dash of RTL so that I can do further testing at a lower risk of crash?
Same exact questions and experiences here. I have attempted to change the m/s setting in the Nav WP section on the configuration tab. That did not change the rate in which my copter decided to fly in upon engagement of RTL. I am glad I am not the only one experiencing these problems. My Loiter works great and the copter flies great... but before I attempt any autonomous missions I want RTL to work.