Warning #1: PX4/Pixhawk users upgrading from AC3.1.5 (or earlier) may need to re-do their compass and accelerometer calibration because AC3.2 also uses the backup compass and accels. Pre-arm checks have been added to ensure this has been done.
Warning #2: on the APM2.x the logs must be downloaded using MAVlink instead of the terminal.
AC3.2-rc14 is now available for BetaTesters through the mission planner’s Beta Firmwares link. The full release notes can be found in ReleaseNotes.txt and changes from -rc13 can be seen below.
Feel free to raise issues found during testing on this discussion or in the new support section in the APM Forum.
It’s a big release with “the onion” restructure and a bunch of new features (including these 57 closed items) so we need to re-test almost everything including all flight modes, all mission commands and all the new features. Marco and I will be maintaining (and adding to) this testing list. Issues reported will first be checked by Jonathan, Marco and I and then confirmed bugs/issues will be put on the github issues list (and then hopefully fixed).
Thanks especially to the beta testers who put their copters at risk testing each release. Enjoy!
Changes from 3.2-rc13
1) Safety Features:
a) fail to arm if second gyro calibration fails (can be disabled with ARMING_CHECK)
2) Bug fixes:
a) DCM-check to require one continuous second of bad heading before triggering LAND
b) I2C bug that could lead to Pixhawk freezing up if I2C bus is noisy
c) reset DCM and EKF gyro bias estimates after gyro calibration (DCM heading could drift after takeoff due to sudden change in gyro values)
d) use primary GPS for LED status (instead of always using first GPS)
Replies
I've just tested and updated the sonar/laser range finder wiki pages. There were errors on nearly all the pages!
I know there's a complaint or two about weird offsets coming from the sonar, I haven't looked at that yet but will shortly. It's possible it's related to some of the incorrect info (now fixed).
Randy, you are a busy guy... Many thanks!
Mike
Are there any other flight-controller or mavlink software applications available for these sensors other than the height above ground?
For example ... is there code to use to follow a distance from a wall and/or ceiling?
Thank You
OwlPic,
No nothing like that as far as I know. There are a couple of people working on object avoidance but I can't make any promises immediately about when/if they will come up with something.
Is your pixhawk working properly after that? when you power pixhawk is FMU power led and B/E led working properly?
If not It seems to be a brownout !
What bec and what current sensor you use?How have you connected gimbal?
Ultrojo,
Nicely spotted by Dan Yeakley.
I had a look at the logs too and I think it's likely a brownout very likely caused by a sudden decrease/increase in the throttle caused by a glitch on the throttle channel. This glitching is definitely not good and I'm sure you'll want to try and find the cause but this alone shouldn't cause a brown-out. There is likely some weak-point in the power system so it cannot deliver the current that the six motors requests. Maybe it's the power module, maybe it's the battery, it's hard to say.
What "C" is the battery?
ultrojo,
The copter hovers at about 45% throttle which is a good level actually. Slightly on the powerful side of which is always nice. The motors are all nicely balanced it seems.
I'm not an expert on batteries, but it looks sufficient to me, it's 30C which is not super high but maybe it's enough (?). Basically it must be an issue with not enough current coming out of the battery or through the power module. I'd try one or more of the following:
1. attach one (or more) of the ESC's red wires to the back of the pixhawk to act as a backup power source in case the PM can't provide the 5V required.
2. get a higher C battery
3. attach a small backup battery that delivers between 5 and 5.8V to the back of the pixhawk.
You could actually try to reproduce failure on the ground by flipping the vehicle's propellers upside-down *and rotate them all one position on the frame* and rapidly increase and decrease the throttle in stabilize mode.
Karl,
Ah yes, thanks for that. I've modified my comment above.
Stone1295,
It does matter, and you're right in the way you config yours. If you put the power distribution board between the power module and LiPo you will not get Current readings that are worth anything. This is because the ESCs are getting their power before the current from the battery is being measured by the current sensor in the power module. The way you describe (lipo -> power module -> pdb -> pixhawk) is the way it is meant to work in order to be effective.
I read somewhere that 3.2 now has support for frsky telemetry.
Does this mean we can get data from the Pixhawk/APM, sent to the frsky receiver and then telemetry is broadcast to our taranis?
Has anyone written any documentation about it yet? I would like to try on my APM and my Pixhawk.
Also does anyone know if it is for the older receivers like the D8R-XP, or just for the X8R with sbus?
-
100
-
101
-
102
-
103
-
104
of 262 Next