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
Try removing the data card and formatting it with your pc put the card back in the pixhawk restart the pixhawk and see if it comes back to life. I have managed to corrupt the card on a couple of occations and when this happens i get these symptoms
Best of luck
Thanks for the advice, but no luck. Still a solid red LED.
Kristian,
Does it make any sounds? If the red light is coming on then it's not completely dead.
Maybe try holding down the safety switch while it boots?
Failing all that I think a log file is created on the sd card if there's a low level failure (i.e. a failure before arducopter even starts). I've had a look on my sd card and I don't immediately see it but I think it's called something like "bootlog.txt". There's a LOGS directory but that's the dataflash logs. There's also a new TERRAIN directory but that just hold terrain info (not yet used). Anyway, the SD card's contents are probably small enough that you could put the contents in dropbox and post a link and I'll have a look.
Thanks Randy for the advice. No sounds from the Pixhawk other than the 3 short little do-re-mi beeps, but I suppose that could be coming from something else, it's hard to tell. But I don't get the startup failed sound or the usual startup ok sound. The safety switch also is flashing quickly. Holding it down after it's powered up does nothing.
Alternatively, if I hold down the safety switch while it's powering up, i still get a solid red light, but safety switch then does not light up. The B/E light flashes quickly and the ACT light is out. Otherwise if I just power it up normally, the B/E light is steady on and the ACT light blinks steady.
But I can't get around the solid red main light.
Here's a link to the content of my SD card (I deleted a bunch of older flight logs to make the file smaller). I couldn't find any bootlog files like you mentioned unless they're hidden.
https://www.dropbox.com/s/h5vnebmweadqobk/Pixhawk%20Card%20copy.zip...
Let me know what you think. Thanks again!
Esteban, my Taranis has a low throttle of around 1100uS, your 988uS seems a bit out for -100% throw with no trim or offset (which you would have avoided).
BTW, have you done or checked the stick calibration on your Taranis since you bought it ?
1100us is too high, most likelly you never did your Taranis stick calibration, or did it a wrong way. My taranis all stick channels are 982-2006. also, I disabled the ratchet on the throttle stick, this way I have a much finer throttle control. I can hover in Stab without constantly adjusting throttle, well maybe 1-2 times a minute.
I don't know if this is relevant to your situation but I noticed with 3.2 copter rc10 when I turn my TX off there is no indication [ in the ground control station ] if FS is set up and working right. In apm_plane even just sitting on the bench it says 'circle' then after 30 seconds 'RTL' just as it should when the TX is shut off. In copter it does not indicate a mode change on the bench. I realized however it is set and works correctly if I turn my TX off while it's flying. I think the fact it knows it's not flying might be why there is no indication it's going into FS on the bench. I carefully tried FS while only up 2-3 feet and confirmed it is in fact working perfectly. I do not however get that message you indicated so as I said.... the above might not be relevant.
Esteban,
Did you follow the instructions on the Throttle failsafe wiki page to test the failsafe? They are quite detailed.
compass-learning should definitely be off (the default value).
Yep, that's me actually. :) To be fair, I'm not completely sure there's a difference. But it definitely didn't seem worse. It could have been a placebo that it seemed better and I just couldn't tell.
Esteban, compassmot and compass live calibration are 2 different things which i think you are confusing. Compassmot is done on the ground. Compass live calibration is usually done just once (usually not even needed), by default it is off. MP will show throttle failsafe even if the copter is disarmed not sure about RTL though, this is exactly how you check that your throttle failsafe setup works. I usually do it w/o battery connected with USB only:
arm-> raise throttle -> move the copter a bit (by hand) -> shut down radio -> MP shows throttle failsafe -> RTL -> Land -> Disarm.
-
86
-
87
-
88
-
89
-
90
of 262 Next