Warning #1: an issue has been found with Tower's Pause button which can cause the vehicle to fly to an old position if the vehicle has not sent a position update to Tower in some time.
Warning #2: Copter-3.3.2 fixes a bug found in Copter-3.3.1's desired climb rate initialisation which could lead to a sudden momentary drop when switching from Stabilize or Acro to AltHold, Loiter or PosHold.
Warning #3: Copter-3.3.2 fixes an issue found in Copter-3.3.1 which could lead to hard landings in RTL or AUTO if the WPNAV_SPEED_DN was set too high (i.e. >400 or 4m/s) and/or the WPNAV_ACCEL_Z was set too low (i.e. <100 or 1m/s/s).
Warning #4: a bug was found in Copter-3.3 which could cause a sudden crash if you abort a Take-off initiated from a ground station. Video description is here. The bug is fixed in Copter-3.3.1 so we recommend upgrading.
Note #1: AC3.3-rc8 corrected a long standing bug in the HDOP reporting. HDOP values will appear about 40% lower than previously but this does not actually mean the GPS position is better than before.
Note #2: if upgrading from AC3.2.1 the vehicle's accelerometer calibration needs to be done again.
Note #3: set SERIAL2_PROTOCOL to "3" and reboot the board to enable FrSky telemetry like in previous versions.
Note #4: the wiki will be updated over the next few weeks to explain how to use the new features
Copter-3.3.1 is available through the mission planner. The full list of changes vs AC3.2.1 can be see in the ReleaseNotes and below are the most recent changes since AC3.3.
Sadly this version (and all future versions) will not run on the APM2.x boards due to CPU speed, flash and RAM restrictions.
Changes from 3.3:
1) Bug fix to prevent potential crash if Follow-Me is used after an aborted takeoff
2) compiler upgraded to 4.9.3 (runs slightly faster than 4.7.2 which was used previously)
Changes from 3.3-rc11:
1) EKF recovers from pre-arm "Compass variance" failure if compasses are consistent
Changes from 3.3-rc10:
1) PreArm "Need 3D Fix" message replaced with detailed reason from EKF
Changes from 3.3-rc9
1) EKF improvements:
a) simpler optical flow takeoff check
2) Bug Fixes/Minor enhancements:
a) fix INS3_USE parameter eeprom location
b) fix SToRM32 serial protocol driver to work with recent versions
c) increase motor pwm->thrust conversion (aka MOT_THST_EXPO) to 0.65 (was 0.50)
d) Firmware version sent to GCS in AUTOPILOT_VERSION message
3) Safety:
a) pre-arm check of compass variance if arming in Loiter, PosHold, Guided
b) always check GPS before arming in Loiter (previously could be disabled if ARMING_CHECK=0)
c) sanity check locations received from GCS for follow-me, do-set-home, do-set-ROI
d) fix optical flow failsafe (was not always triggering LAND when optical flow failed)
e) failsafe RTL vs LAND decision based on hardcoded 5m from home check (previously used WPNAV_RADIUS parameter)
Thanks for your testing!
Replies
ok
i use this gps: http://www.virtualrobotix.com/profiles/blogs/vrx-gps-ublox-8-the-fi... and a µbrain.
thanks, i will check the connections
Not once but twice I finally narrowed down erratic / inconsistant behavior to a stressed out DF13 connector. Not a big fan of those. But I have since used a dab of hot glue to make certain nothing can ever tug on those little wires.
@Leonard
Attached is link to Auto Tune files. It seems to be pretty good, but while using Follow Me, it over corrects quite badly when pitching. Maybe that's normal?
quadcopter
KDE 515 motors
APC 14x4.7 SF props
650 size frame
16000 mah 4s battery
AUW 2.7kg
Thanks.
https://www.mediafire.com/?7a8co2555u7mjts
re- b) smart battery support
Could anybody elaborate what this does and how it works?
Smart battery like the new 3DR Solo has. It's basically a normal battery with the 3DR Power module built in, but also charging circuits and fancy indicators showing battery capacity and so on. The battery communicates to the pixhawk with i2c i think (or another one of the protocols), so support had to be added for it.
I'm hoping 3dr will release a mounting bracket of some sort so that we can use the Solo batteries in DIY projects.
Thanks. Boy that seems like a waste to have a power module inside every one.
There was a photo here somewhere of the internals of the battery, it looked almost like a DJI one (i mean that it had chipset taking care of all the charging and leds and so on as well as battery info back to the controller). Wouldn't be to hard to just take the Solo battery apart and have some extensions for xt60 and balance plug, and just use any cheapo battery from hobbyking.
I can't find the photo of the internals, but here you can see the prongs that do the actual battery connection, and the middle pin might be something like a USB with multiple copper lines for data...
I really hope it is possible to take the battery case apart and solder in a new battery. You can't do this on a DJI they intentionally go out of their way to make sure the circuit sees this intrusion somehow and renders the unit / battery useless. The 'smart battery' is mostly for revenue generation for DJI I think. My brother lost a phantom because the stupid battery wigged out and thought it was low and landed itself in a lake. Meanwhile it was fully charged before flight and his HUD display clearly showed an %80 charge remaining. I also heard they automatically discharge themselves aka 'storage' after a certain amount of time with no use. So you finally get time to go fly only to discover that fully charged battery isn't anymore. Or maybe you don't realize 'IT' discharged itself and you crash because you didn't realize it did this. Anyway.... I'm no fan of a 'smart' battery I have a brain and a charger I've been fine with it I don't need any help. If the solo battery is like this I'll not be buying a solo for this reason alone. But... I do like how it just plugs in. Very nice.
Hi All and a big thanks to the Dev's and all of you guys writing and testing the beta firmware.
I had a problem with EKF Variance that just sprung up yesterday. I am running Pixhawk on a Cinetank Mk2L with 12" props and t-motor MN3510 motors. Compass id a 3DR external. As far as FC goes it is pretty much stock config.
However, after several flights with no issue I started getting EKF Variance warnings every time I armed. After digging through the logs I found that the compass' were not tracking each other and a permanent offset had appeared. The reported heading seems OK on MP and flight in STAB was ok (although very short as I didn't want to push my luck)
I tried powering off all of the FPV gear etc. and moving the External Compass but no difference. I assumed it was hardware related but two other Pixhawk machines also started to do the same. The small 250 was ok after a couple of recalibrations but the Y6B and the Cinetank required more work.
Erased and reinstalled 3.3rc5 and did a complete setup and this fixed it for a while. Rebooted this morning and once again Compass Variance had appeared. I checked the offsets and Compass 2 had 0,0,0. I am a bit confused as I also rebooted several times last night and it was ok.
Finally, out of frustration I changed the orientation of the external compass and now it seems fine (After recalibrated).
I have also tried COMPASSMOT on and off but this didn't make any difference for me.
External compass offsets are (23,27-75) and Internal (367,-398,-352). Delineation is 12deg 33 min. Heading matches compass perfectly now.
Any ideas? I had a similar issue with another quad but recalibration seemed to fix this. I don't think it is hardware as three machines have all developed EKF VARIANCE warnings and each time (up till now) recalibration seemed to fix it. This time I also needed to point the compass in a different direction.
Overall though I think 3.3rc5 is fantastic in the modes I have tested.
Well that didn't work. Just wanted to confirm, what is EKF_CHECK-2 actually telling me? I know it me and EKV Variance but I can't find anything specific in the wiki.
When I roll back to 3.2.1 it is fine.
Any ideas? Thanks.
-
438
-
439
-
440
-
441
-
442
of 558 Next