Copter-3.6.0-rc2 has just been released and is available for beta testing using the Mission Planner’s “Beta firmwares” link (and perhaps similarly in other ground stations). This version has been “rebased on master” meaning that it includes all the developments done by the dev team in the last month. The changes are in the ReleaseNotes and also copied below:
ChibiOS support for Holybro Kakute F4
Range finders:
a) Benewake TFmini and TF02 support
b) WASP200 laser range finder support
D-Shot and ESC telemetry support
Vision-position-estimate support for use with ROS
Bug fixes and minor enhancements:
a) TradHeli swash plate servo trim fixes
b) SmartRTL gives pilot yaw control
c) marvelmind reliability improvements
d) CoaxCopter and SingleCopter output fixes
e) Maxbotics I2C sonar health fix
Safety fixes/improvements:
a) GPS/EKF failsafe disabled in Acro/Stabilize modes
b) interlock switch arming check fixed
c) Auxiliary switch de-bouncing
d) pre-arm check for GPS/AHRS difference changed to 2D (to avoid false positives)
e) startup crash fixed when VL53L0X lidar configured but not connected
Thanks in advance for beta testing this new version. I hope to provide more feedback in the coming weeks to some of the questions posted in this category!
Right if you install the beta of MP and go to the install FM page select " Beta firmwares" rc-2 will show up on the copter modes. MP also will show the chibiOS version during the fw install.
Flew 3.6.0 rc-2 ChibiOS on F450 with mRo Pixracer. All went well in Stab, Althold, Loiter, PosHold, Circle, Mission, RTL and Smart RTL.
Motor ESC Telemetry with BLHeli_32 with D-shot set works as does BLHeli pass-threw programming function.
Re: Smart RTL, Yaw works now throughout flight and copter faces next retuning waypoint ( I don’t think it did in rc-1).
I wonder if the “RTL_Cone_Slope” function can be used to prevent the decent from being so liner on the final leg?
Example: Take off, climb to 50 feet vertically, then fly around and when retuning by Smart RTL, on the “final” leg, the flight path slopes down to take off point getting me bit too close to the (real) fence in my side yard. Can’t seem to make it go to that initial 50 foot climb point, then descend. That 's why I wonder about the “Cone” parameter.
So far-so good. I will fly later today with Pixhawk machine if possible.
Great job again.
Thanks,
Joe
@lordneeko,
Re the dates on the files, there’s a web page creation issue there. They have been updated and if you open the git-version.txt file inside is the actual version included. The date on the file on the server has also been updated but on the web page it appears as an old date. It’s on the list to fix but does not real harm except that it adds confusion. txs again for testing!
hi Randy, could you pls confirm how exactly dshot support works on pixracer? it has only 6 pins for esc connectors and when according to wiki i altered servo outputs, it did not work. but it seems if i alter only motor type param - it works - but, pls, could you confirm what exactly needs to be altered?
Paul, I saw you question and on a PixRacer you only set the MOT_PWM_TYPE parameter to “4” to enable D-Shot 150. If you look carefully at the Wiki they only mention the need to change outputs and alter settings for PixHawk type boards. You don’t need to alter the individual port settings (33,34,35,36) on a “PixRacer”; as it doesn’t have the same hardware (an additional co - processor) as on a Pixhawk. I am guessing in the future that may change for Pixhawk; we will just have to check the Wiki as additional releases come out… FYI, on my PixHawk machine, I moved the ESC’s to the AUX ports and changed settings, as per the Wiki, and it worked just fine.
Joe
Thank you, I have that issue on Pixracer that has no separate aux and main outputs. Just 6 out pins. So looks like you cannot use Oneshot125 on 1-4 outs with usual PWM on 5-6.
I just concerned by the fact the issue wasn’t got any label in github, so may be this is something related to my config?
