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
Not natively. I believe there are options using external "translators" based on Arduino's and/or Teensy's that convert Mavlink telemetry to HOTT.
Hi Kurt,
While I have not used the same module you have, I do use the frsky D telemetry on all my copters and there are absolutely no problems on the pixhawk side for the D type telemetry. I also have a couple of friends using the same system and none of them have seen any problems with the pixhawk frsky telemetry either.
Sorry I can't be more help.
Hi Kurt,
These are the settings I am using:
SERIAL2_BAUD,9 (I don't think this does anything)
SERIAL2_PROTOCOL,3
I use a taranis and this thing modified:
http://www.hobbyking.com/hobbyking/store/__8356__Turnigy_Rx_Servo_S...
Like this:
http://ardupilot.com/forum/viewtopic.php?t=9498&p=22663
I have never had any problems.
I use the direct method as you describe (see photo), but sending it to a FrySKy X8R. It works great for me, I simply set up a screen using the default values as 'discovered'. Currently I am playing with an pre 2.1 LUA script and updating the Telemetry ID's, again, so far so good.
This a DIY version of the FUL-1 for Smart ports...Cheap as chips!
https://goo.gl/photos/6ghdRSGUbnu13FdCA
Perhaps the issue is not on 3.3 but OpenTX 2.1.x has completely revamped the telemetry system. Part of that revamping is that no sensors are pre-defined, and must be "discovered" on the fly using the telemetry screens for each model.
If you mention the answer you got at RCGroups, forget it.
I have telemetry running on 3.3RC12 on every port I choose, (Telem1,Telem2,Serial4) as long I have it configured to do that (SERIALx_PROTOCOL), which in my case I have it as 1 because my FrSKy telemetry system is based on the Teensy.
I can't test your setup, but the code hasn't been changed on that area (from the commits list), but have asked to someone that can test.
Do you happen to have a regular FrSky sensor that you could use to test FrSky "standard" telemetry with your Dseries receiver ?
you're right . typo, request to correction added.
No problem. I've already requested some corrections to the telem page https://github.com/diydrones/ardupilot-wiki-issue-tracker/issues/160
After the second mission I could not get a rearm at all even after several minutes.
MP only showed a "Disarmed" message on screen.
I will have to wait until this evening to review the logs.
I was wondering it this had happened to others as well.
-
132
-
133
-
134
-
135
-
136
of 449 Next