I just upgraded to ArduCopter 2.5.5 and I am having trouble. Takeoff looks totally eratic. So I started by testing motors using Mission Planner CLI / Setup / Motors. It used to test them starting with front motor and going clockwise testing each motor. The actual motor order as you go clockwise was 146235 (APM2 output numbers) but now I am getting 145236. The 5 and 6 motors have swapped places. Is this only in Setup/Motors that it has changed or is it also in flying modes. I will see if I can do more testing tonight.
I use a 3DR Hexa body with the 880kv motors, APM2, 6.0 Lipo. ArduCopter2.5.5
I'm checking with folks who have a hexa (I don't).
I'm having a look now..
What version of the code were you on before you upgraded? 2.5.4 or something earlier?
I've had a look at the hexa code and it hasn't changed between 2.5.4 and 2.5.5 so I'm at a bit of a loss to explain what the issue is. I would have expected an army of people to complain if there were a software bug in there..
I suppose it's not possible that you just got the 5 & 6 outputs coming out of the APM2 reversed?
The reversing 5 & 6 output was my first thought because of the small 2 wire connector. I checked that out first thing yesterday, but I still went and double checked again today and...... YEP it was the connector. I dont know why I didnt catch this when it was the first thing I thougt of yesterday. Got to start working on this while I am awake. :)
Thanks again Ray
I'm contemplating on installing the new 2.5.5. I'm on 2.5.4 right now and besides having to press the reset button, I haven't had any problems. I received my APM 2 board on April 23, so I wonder if I have one of the affected or "bugged" boards. So far, I've only flown my hexa on stable mode only. Scared to fly it in GPS hold mode or RTL mode. I've heard some people say that it can cause you to lose your robot friend. Any improvements to that on 2.5.5?
James, there was no bug in the true sense, and the fix is out now in any case. If you fly 2.5.5, you don't need to worry about the "bug". Besides, it would manifest itself in stabilize mode, not GPS hold.
Loiter is pretty safe. When you hear scare stories, you have to remember how many people are flying the arducopter. There are 1000s of people flying them. With that number, people are crashing all the time for lots of reasons - mostly hardware issues (like a broken compass will mean your quad won't know which way is north and will fly off in the wrong direction) or perhaps some set-up issue. We should add a check to make sure people don't go into loiter with a broken compass..that's possible to do and I'll add it to my to-do list.
The first time I did loiter, I did it on the ground (I recommend with props off!) with the quad in my hand and I watched how it performed before putting it up in the air.