Warning #1: Compass calibration and reducing interference is far more important than with 2.9.1b
Warning #2: GPS glitches can cause sudden and aggressive position changes while in loiter mode. You may wish to reduce the Loiter PID P to 0.5 (from 1.0) to reduce aggressiveness (see image below of where this gain can be found in mission planner).
Warning #3: optical flow is not supported but will be back in the next release (AC-3.0.2 or AC-3.1.0).
Warning #4: loiter turns does not maintain altitude. This bug will be fixed in AC-3.0.2.
Warning #5: This release has only been lightly tested on Traditional Helicopters.
Improvements over 2.9.1b include:
WPNAV_SPEED, WPNAV_SPEED_UP, WPNAV_SPEED_DN, WPNAV_ACCEL allows configuring speeds and acceleration during missions
How to upgrade:
1. Make sure you are using Mission Planner 1.2.59 or newer (get it here)
2. Click on the MissionPlanner's Hardware, Install Firmware screen. The version numbers should appear as "ArduCopter-3.0.1", then click the appropriate frame icon and it should upgrade as per usual.
3. Reduce the Loiter and Alt Hold PIDs if you have modified them from the defaults. The modified PID values for the 3DR frame can be seen in the image below.
Note: Nav parameters have been combined with Loiter so do not be concerned if you can't find them.
5. Try out the new version in stabilize mode first, then alt-hold, then loiter and finally RTL and Auto.
Numerous How-To videos are available:
Special Thanks to Marco, DaveC and the large number of testers on the pre-release thread who put their copters at risk during the extended testing period. Some of their videos can be found here, here, here, here, here and here. Thanks also to MichaelO for the MP changes required for this release.
All feedback welcome. Please put your questions, comments (good and bad!) below.
Some results from voltage measurements:
Verified BEC supply 5,116V
JP1 connected. Made the voltage measurements on APM diode/fuse.
- BEC supply on input rail 5,106V with no accessories plugged (GPS, COMPASS, TELEMETRY)/ with accessories 5,086V.
- BEC supply on output rail 4,3V (observed constant variation between 3,2V and 4,4V) / without accessories nominal 4,6V.
- Noted that BEC under load supplies 5,08V
- Disconnected battery and powered APM via usb, observed 4,9V when the BEC is connected on output rail. Curiously when moved the BEC to input rail the APM voltage dropped to 4.3V.
It is strange that the voltage drop through the APM diode seems to be much more than the expected 0,3V.
I am almost certain that my power supply configuration contributed to the crash. However I am wondering why it didn’t happen in any of the several flights that I made before...
Hi All.. Hoping for a little help with log files on RC5. All the info I can find relates to Windows and with iOS it all works quite differently. I am struggling to just simply navigate to view the info I am looking for? I am in the initial flight tuning stage of a new Pixhawk on a 950mm Hex and just starting to do a few hover flights etc to check my data in logs. It is not familiar when using the graph controls etc. and am hoping for a little guidance on how to select the right info from the logs and how to adjust 7 view. It's not as simple as grabbing a section to zoom etc? Any help would be great.. Below file is screen print of first hover and graph gyro x,y,z. The values look good, but I'm not sure with the new graph tools that i am viewing correctly? And... um.... What next?
I have three AP; one 2.0, another one 2.5 both are from 3DR and one 2.5 from chine that I used to run some test
Two month ago I burn the 3,3 regulator of the chine one, so I read the topic with the procedure to change it and did.
When I was in the investigation process to find a solution I think that somebody had written that if you installed de 3.0 release in a chine AP board you could burn the 3.3 regulator.
I have my test chine board again alive and I have installed 2.9.1 release and is working with no problem a small test quad. , but I would like to installed the 3.0 firmware.
I would like to know if somebody else has read what I think I read, if I am right or wrong.
I am looking forward to hearing from you guys any comments.
Thank in advance, Leopoldo
If you burned the 3.3v reg., then it is burned no matter which firmware you install. The reason why your copter seems working with older 2.9.1 firmware is because those running at lower SPI speed and masking the problem.
The problem is there, it just that you don't see it. Your IMU sensors (gyros, accels.) are still exposed to 5 volts which they are designed to work with 3.3volts only...
The only solution is to replace the regulator...