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
Hello Randy, below there's little issues that I'v seen testing AC3.2 on hexacopter.
Condition YAW absolute ok but relative no work.(if I set 90° copter only achieve 30-45°, I thinks issue for relative is regarding the base reference YAW used for calculate relative is no good because every think happens as if it take reference YAW current heading while copter did not finish to yaw to is next waypoint . The better will be to calculate relative yaw from the expected yaw between to waypoint)
Could we have condition yaw working like Do set ROI? I explain, as do set roi, when we set condition YAW, AP maintain this function active through many waypoint until we desactivate it.
Does its normal that rally point no work when invoke from manual flight mode?
For pause auto-mission, it works, but there is possible to move current waypoint number variable to eeprom? like this even when copter no finish big mission, and when it rtl, land and we change batteries (reboot), when we restart mission, automatically copter go to waypoint targeted just before rtl?
Thanks for your feedback.
also I noticed that when switch back to auto mission mode after having paused, all the functions such as do_set or condition_ commands are not reactivated, it would be possible to ensure that all (or the last ones) of the do_set_ and conditon_ be before current waypoint be reprocessed when switching back to automission?
I confirm that rally point no work on PIXHAWK AC3.2.RC3, also when rtl is invoke by failsafe (battery) or manualy, drone start to climb....I switch to manual mode to stop climb.... RTL Alt is set at 15m and I set rally point to 30m......
Probably related to the Failsafe problem, but i have an issue with 2 different copters running micro Vrbrain 5.1 and D4R-II 27ms receivers(3.2 rc2) connected with ppm. Both of them go in failsafe after a while. No Rssi problems on my tarranis. In the mission planner failsafe screen i can see the signal dropping sometimes and coming up again after a few seconds. Since these are to separate machines i am at a guess what would be the reason. Needless to say this is serious issue for me. Any ideas?
I ordered one during the Maifair promotion. It's size and weight are great. When i got mine it was still in development. There where some small issues to take care off. Eventually i got another revision to try out. So now i have 2 of them. Next revision (the one you can order now) should be final. A small minor point is that i do not like the combination cables. they are to long, to stiff and i would like to see female instead of male servo connectors on them. Needless to say these are minor issues. The issue i have with my receivers should be a software issue i hope as there are not to many people complaining about this. Shipping was very fast. 3 days by DHL.
Hello Micha,
I also have a micro vbrain 5 with the firmware ArduCopter-vrubrain-v51-PPM, the board of the second generation is fantastic circuit small and very well done, very light, great for a MicroQuad 250/300 mm.
My problem is that I can not perform the calibration of the ESC, run the initialization procedure as APM2 to do, but you do not calibrate the esc will continue to issue the Beep lack of signal.
I was able to calibrate the esc, only arming the controller and immediately after putting the Throttle to the max and then to a minimum as it usually does, but to restart the esc continue to beep no signal.
I do not know if my problem (esc not compatible, but with APM2 work) or a firmware issue.
how did you do the calibration?
For the cables you are right they are of little use, so I had to delete the supplied connectors and then adapt the inputs and outputs to the standart RC, surely it is to improve the wiring supplied
As for your problem during my tests I have not seen the activation of the failsafe with the Turnigy 9X.
greetings
I always calibrate my ESC's manually. One by one. Just connect the esc to the throttle channel of your receiver instead of the Vrbrain. Power up the esc with your throttle stick up and when it beeps, move the stick all the way down and you are done. I then check if the motor spins up correctly.
Are you using D4R-II with 27ms firmware?
That failsafe thing is just so strange. A third model with the same receiver and firmware connected too a multiwii board performs just fine so that rules out my transmitter.
Hello Micha,
Yes, I also tried individually directly with the receiver, but the strange thing is that at the start and after the initialization of the flight controllers ESC start doing Beep, Beep as if there is no signal from the FC.
Emile told me that the problem of calibrating a release 3.2RC3 released for the beep at the start of the ESC should I increase the parameter TRIM Motor.
No I do not use the D4R-II with 27 ms firmware, I installed this firmware ArduCopter-vrubrain-v51-PPM, as it says on the website of VR μBrain.
greetings
Right, i did not change the firmware on the VRbrain. They came with 3.2 RC2. D'ont tell me there is a separate firmware version for SBUS and PPM? That could explain a lot..
About the esc's, have you tried playing around with the endpoints of your trottle channel on your transmitter?
-
202
-
203
-
204
-
205
-
206
of 262 Next