Hi Guys, another newbie here, been lurking around the forum for quite some time but this is my first post.
So far everything has been going great using the resources here, got my Bumblebee quad all setup and flying with the APM2.5, uBlox GPS and 3DR telemetry and my trusty old DX6i, the resources here have been awesome in getting me going.
Major problem occured with my first Auto mission, seemed simple enough and everyone says its easy. The mission plan was to ascend to 10m (I hovered it first), fly to a fence post about 55m away, loiter for 5sec above the fencepost, change speed to 1m/s, return to launch (then I would take control).
What actually happened was; ascended to 10m (cool), then tilted over 15deg and went like a bat outta hell towards the waypoint (fencepost), it blew past the fence post then started a wide turn to come back but was decending, it clipped a guy wire on a telephone pole (25m off course) as it was heading for earth and splattered accross the field. Fortunately with my Trex450 background I knew to buy lots of spare parts when I got the airframe :) None of the electronics appear damaged, but now I'm scared.
I really need some help figuring out what went wrong before I try another mission, why did it take off so fast? The only speed setting in the Mission Planner configuration I can find is WP_SPEED-MAX under Adv Parameter List which is still set at the default of 3 (assumed 3m/s). Looking at the tlog file it quickly reached a speed of 8m/s and eventually reached 13m/s before splattering.
I've attached the log files and flight plan in case this helps in figuring it out, I switched to auto mode about 92% through the file. I'm really having a hard time figuring what I did wrong.
Thanks, Dean
Replies
The Terminal window is a bit unintuitive to use, but this is what I have found works.
Don't do a connect. Just plug in the USB cable (must be USB) and click on the Terminal tab, making sure you have the right serial port and speed selected first..
If you get gibberish, click on the terminal tab again. I have found no need to hit enter 3 or any times. Just clicking the Terminal tab again does the trick.
Then the Log Download button will bring up the window with the list of logs IN the APM and you can select which ones or the whole lot to download.
The files will be date and time stamped with the time you downloaded them NOT the time of the flight, and this can be a little confusing sometimes.
Once you have done this and closed the download window you can click on Log Browse and MP will ask you to select a .log file and show you the .log files in teh folder it is currently looking at (usually the log folder in the MP folder).
Then you will have a window with a graph area at the top and a spreadsheet view of your data in the lower part.
Click on each row and it will tell you at the top of the columns what value is in each column, and it changes from row to row, but when you find things like roll_in and roll and graph them (click graph data button) you will see what you are telling it to do (roll_in for instance) and what it is doing (roll for instance).
Takes longer to explain than do.
could you post the .log file downloaded from the terminal window, and your parameter file, to allow a little better insight into what was happening.
There are a lot of things that MIGHT have gone wrong, but it would help to know what the copter was reacting to, hence the need for the .log file.
During tuning I have gone in and switched on ALL logging as the Developers who were helping were asking the similar questions about what was going on inside the copter.
Learning to read the .log files has really helped me get a grip on wetting and connections that are not working or causing problems.