ArduCopter 2.7.1 Released
ArduCopter 2.7.1 will become available on Mission Planner and in the downloads area shortly. This release contains a few important bug fixes as well as the first implementation of the MPU6000 sensor-fusion code.
Detailed changes are in the commit log. Here's a summary:
New:
- Preliminary support for MPU6000 on board sensor-fusion (DMP)
- AP_Limits: Experimental "bounce" mode, for smaller spaces (LIM_RECMODE)
Bugs:
- Bug fix for yaw error buildup on takeoff
- Fix in Auto mode for failsafe handling
- Fixes to 3-axis camera gimbal code
Replies to This Discussion
-
DeveloperPermalink Reply by Marco Robustini on -
@Andre: i think it's unfortunately just a coincidence.
Check if the on board module is alive using FTDI cable and a terminal program, like Putty.
What do you mean with "bricked"?
The release 2.7.1 has some little problems we are trying to solve, some reported by me during the test and unfortunately for now unresolved, but it certainly can not break a module with the new firmware.
-
DeveloperPermalink Reply by R_Lefebvre on -
Marco, "bricked" means that the Xbee stops working, and you have to basically "reset it" using X-CTU. It usually happens to the air module, not the ground module, which might indicate it's a code problem.
I suspect something has happened with 2.7, because I used to only brick about once every 25 flights. But ever since 2.7 or 2.7.1, mine bricks every ~2 flights. Sometimes I don't even get a flight. I unbrick it, put it on, test it, all good. Go outside, power up, bricked... It's extremely annoying.
I finally gave up and tried to switch over to the 3DR Radios, but I can't get the air module working. :( Spent about 4 hours on it, and I give up. Unbricked my Xbee again, and I got a flight out of it last night...
It's also entirely possible that vibration causes the bricking, and it simply gets worse with age. It could just be that with use, the air module ends up having a solder joint crack, and then it gets extremely flaky. I have tried reflowing all the through-hole stuff, and it didn't help. Now I'll have to do the SMD stuff.
-
Permalink Reply by estebanflyer on -
What I do is unplug the xbee, plug the battery, wait 10 seconds and then plug the xbee to power. I think I might be avoiding voltage peaks.
This issue never happened again with 2.7.1 though.
-
3D RoboticsPermalink Reply by Chris Anderson on -
Estaban is right. Bricking happens when voltage gets to the signal pins before the Xbee has booted up. The band-aid is to unplug the Xbees when you're powering on APM, then plug them in.
As for the 3DR modules, they should just work right out of the box. Mine always have, with no conf necessary. Maybe you have a defective unit? (If so, get a RMA and return it for replacement)
-
DeveloperPermalink Reply by R_Lefebvre on -
Ok, I'll try the bandaid and see if that helps. But it's clear to me that "something changed". It used to happen only rarely, now it's constantly happening and I haven't changed the way I'm using them. I just don't know if it's hardware or software problem.
My 3DR Radio didn't work out of the box. I plugged them in, and right off the bat the green LED on the ground module was blinking (seeking). The air module was solid (found it's mate?). That doesn't make much sense. I went into the MP radio configurator, and the air module is completely unresponsive. I plugged the air module into the FTDI Basic board, and nothing I do lets it talk to the computer, the green LED is on solid too. I did manage to program my Ardustation with the FTDI Basic, so it does seem to be working. But the air module is just completely unresponsive.
So yeah, I'll have to send it back I guess.
-
Permalink Reply by Gordon on -
I'll add that my xbee bricked for the very first time straight after loading 2.7.1.
Coincidence? Who knows.
-
Permalink Reply by I.S. on -
Same happened to me! I just plugged my 3DR radios 433Mhz and both have green led solid right after plugging them.
Have you de-bricked the modules?
Regards,
IS
-
DeveloperPermalink Reply by Marco Robustini on -
@Robert: check the solder of the two "pcb sandwich", in my module i've found two broken solder near the antenna connector... renforced and now all is ok.
-
DeveloperPermalink Reply by R_Lefebvre on -
Marco, where do you mean exactly? I reflowed all the solders on the pin header rows already. Everything else is super tiny!
-
Permalink Reply by Darren Stan Oakley on -
Here is my PIDs for my DJI clone frame now with 10/4.5 props and 900kv motors running 2.7.1 with good success.I have tuned any oscillation out now and also have sorted the loiter and alt hold so no bouncing and good tight hold. Have to say with initial doubts I am loving this firmware now. I didnt really have to adjust much in the end.
Now just need to find out why my radios have stopped working( Before I updated to 2.7.1 so not related) :)
-
Permalink Reply by Rana on -
Darren, thanks for sharing your PID screenshot for the 10x4.5 prop with, DJI clone 450 frame, Turnigy 900kv motors.
-
Permalink Reply by estebanflyer on
-
That use to happen to me, and i thought it got fixed in 2.7.1. I had me xbee get bricked easily 50 times. It just stopped at 2.7.1.
Social Networking
Top Content
Contests
Season Two of the Trust Time Trial (T3) Contest has now begun. The fourth round is an accuracy round for multicopters, which requires contestants to fly a cube. The deadline is April 14th.A list of all T3 contests is here.
Groups
-
Japan ArduCopter Group
58 members
-
ArduCopter User Group
1355 members
-
Australia
88 members
-
Moderators
24 members
-
ArduRover User Group
207 members
Advertisement
© 2013 Created by Chris Anderson.
Powered by
