I have been struggling with the APM2 that I have just installed and have been trying to fly in Auto and RTL modes. I do have the plane flying great in the stabilize mode and the fly by wire mode also works.
When I switch the plane to RTL or Auto mode the plane does fly itself (circle) and hold altitude but it does not go to the waypoint locations and it does not circle over the home or launch point. Every time I have flown I have waited for the blue led to go solid and also the 3Dfix led is solid. I have also connected to the computer outside and in the mission planner it says 3Dfix. I do NOT ever get a red led to stay on. The red led does flash when the board is first powered up but then has never stayed on solid like is says it is supposed to. See the link.
That brings be to my next problem. It was suggested to me to look at the data log and see if there is an actual gps lock. When trying to look at the data log in the mission planner I do not see any horizon changes, speed or altitude changes. It does say the log is playing but I am unable to see any of the planes functions.
I have been struggling with this for a week now and do not know what to try next. If anyone could give me some suggestions that would be greatly appreciated.
Just download the latest MP Ramesh, and download whichever firmware you want to your board. the planner will write over the existing code on the board. It used to be necessary to erase the EEPROM after every download and reset to factory settings, but the MP now does this for you. You can however go into CLI and do an additional reset to be sure if you wish. Personally better to be safe than sorry. Regards:)
many thanks, that really simplifies matters.
OK after trying many things today the AMP drove itself into the dirt. Testing today proved no guidance to GPS locations. During my third test flight while watching the plane circle and fly around lost in the air it suddenly went straight 90 deg down toward the ground. No exaggeration that the plane was flying level and then pitched straight 90 deg nose down. I switched the plane to manual and had the plane about back to 45 deg before it hit the dirt. So at least I know it was not a air frame / servo linkage or radio problem.
Not sure about how 3D robotics will be about warranty on a unit that never worked and now is smashed. I have been emailing them complaining about the issues that I have been experiencing and now I guess I will see what they say. I am very frustrated with this and not sure if I will try it again or not??
Most everything survived with exception to the plane APM and lipos.
Anyone else experienced anything like this?
Sorry to hear about this, I too feel a bit frustrated about APM.
Something similar, but probably not comparable, happened to me with an APM1. First, I had an APM1 that would boot with ArduCopter software, but not with ArduPlane software. This was probably due to some sensor malfunction. It never flew in a plane and was replaced by my dealer. The replacement APM1 worked quite nicely a few times, but then it took my plane plus camera down with some strange malfunction. (See this thread, if you care: http://diydrones.com/forum/topics/crash-investigation-arduplane-2-2...). The only thing to survive was the RC receiver, resulting loss is around 500$...
Most of the software development effort seems to go into ArduCopter software at the moment. Maybe ArduPlane is just not ready for prime time. Or maybe you just shouldn't get startet if you can't afford to loose a certain amount of money every month on your toys. I can't... :) I'm still considering if I should get a new APM or just forget about it for the moment.
One important thing to consider is the fact that 3DRobotics is only creating and selling the hardware for an open source project. I read a very informative post about this somewhere but I can't find it right now. Part of the deal is, you are on your own with your problems. If you are lucky, you will find community help. To be able to provide extensive support 3DRobotics would have to charge a lot more for a device of similar capabilities.
Support around here seems to only take action if something happens more than a hundred times or so. Singular events seem to be ignored mostly, judging from what I've been reading here for the last few months. The only reply in my thread mentioned above is from myself. It's about some conclusions I'm drawing from this whole mess.
Thanks for the reply and I was happy you shared your post. Yes I did get a reply from 3D robotics last week when I was asking for help and they said they do not support the software only the hardware. But I do believe I had hardware issues now after this. Of course I could be wrong but who will ever know now.
One thing that is confusing to me is how the hardware only can be supported. If the software is not available the hardware would not work for me ( and the majority of others).
The only thing that I am upset about is not sending it back right away. I was hoping that I was doing something wrong or that there was a fix that would be brought up or that I would find here. I do thank everyone that offered suggestions and there help.
I do believe I will order another APM and try it again sometime. I might wait until the APM2 is in stock.
Any thoughts on why this happened would still be greatly appreciated.
Like most open source projects, the ArduCopter and ArduPlane software is created by a community of volunteers, most of them here. 3D Robotics only sells hardware--technically, they're just "development boards", like the Arduinos that they're based on--and doesn't develop the software. I know this is confusing, but it's common to open source hardware projects.
Please note that there are nearly 10,000 APM boards out there, and the vast majority are working fine. I'm sorry that you had hardware issues, but 3D Robotics is definitely there to help with those. They take their hardware customer support responsibilities seriously and definitely encourage people to get a RMA and send the board back to be checked out if they're having issues within the warranty period.
The ArduPlane software is being very actively developed in the background, and you should expect a major release in the next couple weeks. It shares all the key libraries with ArduCopter, so all the work you're seeing on copter code is also going to show up in the new ArduPlane code. Most of it is focused on reliability and performance (as well as optimizing the code for APM 2), so I would recommend updating when it's out.
Thanks for the reply. I understand now. Yes it is a bit confusing and I am sure you have probably typed that same message a few thousand times. :)
I am looking forward to trying another APM2 and will look forward to the updates.
It is impressive that volunteers that wrote the software.
I was having similar issues.
I deactivated the Mag/Compass and all is well. I tried everything with the compass, read many threads, waved it around to calibrate it, then couldn't find a thread to set the values the calibration gave me (not declination). I also found that it would quickly switch from Manual to Stablise itself a few times and I had to flick the switch a couple of time to get it back. My radio setup showed no flickering between values?? which may have happened if it wasn't flat at the beginning (just clutching a straws for you)
Before this would fly in circles away from me and couldn't find home, showed in mission planner only Nth - W- S and nothing east of N or S.
Just flew a few 'missions' FPV with minimosd and it was, at last satisfying.
The mag issue means I won't put it in my quad or hex again and will stick with my Naza for now.
I believe it is hardware related as I had a similar issue with APM1, however this time CLI doesn't tell me "bad compass". I am not a programmer etc, so I have no clue like many of these other guys, but switching off the compass worked perfectly, I don't think Arduplane needs it, but Arducopter does.
Working it out is half the fun, crashing is S#$%.
There almost needs to be a flow chart for a procedure sheet depending on the plane build. ISO ???
It really looks like a propeller failure. If so the IMU did its best.
Thanks for the reply. Your circling and flying away from you is exactly like I experienced in all but my last flight. Good to know that you were able to find a fix. The crash I experienced today was not a big deal I just hope to learn something from it.
The thing that messed me up the most was the logs. I am convinced now that there was something wrong. Earlier I figured I was doing something wrong when trying to read the data logs and nothing was working.
So to summarize I did learn to ensure that the data logging is working and to check the data. If things are not working correctly I will send it back to be checked out.
Funny thing is how do the gears in the aileron servos get stripped out in the crash. The plane hit about level directly into the nose. No damage to the wing at all besides striped aileron servo gears. Hitec 65HB servos. The tail boom of the plane cracked right in half and the stabilizer was hooked under the nose on the wire landing gear. Didn't have my phone on me and it was muddy where it crashed other wise I would have some pictures.
You are correct working it out is lots of fun. Glad your FPV missions have went well. Have any pictures of your plane?