Copter-3.6.0-rc8 is now available for beta testing. If using MP this can be downloaded after pressing the “Beta Firmwares” link on the Install Firmware screen (QGC and other GCSs have a similar feature I believe).
The changes vs -rc7 are in the ReleaseNotes and also copied below:
TeraRanger Tower EVO lidar support added
PCA9685 and NCA5623 LED support added (replacements for Toshiba LED that is becoming end-of-life)
Missions can start with DO_ commands (first NAV command must still be takeoff)
ChibiOS fixes:
a) DShot and BLHeli stability improvements
b) added OmnibusNanoV6 bootloader
Bug fixes:
a) AP_Stat only saves values to eeprom if they change (reduces CPU impact)
b) boost throttle respects safety switch
c) TradHeli reduce chance of tip-over when landed in Loiter
We will have at least one more release candidate (-rc9) before we go live because we have an outstanding issue with new Loiter’s initialisation (it twitches if Loiter is engaged while the vehicle is moving quickly)… still, I think we are getting close to an official release.
All testing that people can do is greatly appreciated!
How does the fact that the bootloader has been added for the Omnibus Nano V6 affect the installation process of Arducopter to this board? I updated the bootloader on my board with the procedure outlined in the Wiki (using dfu-ultil) and then installed Arducopter w/o issue, I’m just curious for future reference.
it means that hex files including the bootloader and ardupilot in one file are now available for download. That makes it easier for a first time install on a bare board.
Cheers, Tridge
I really want the driver for Lidar Lite V3HP in the next release, I made PR for this library last month, but it haven’t been approved yet. I hope you can help me complete my first PR for Ardupilot.
Basically it works, but i think it’s not respecting AVOID_MARGIN distance, which i set to 8 m but it begun to work at 5,5/6 m. I’m using one single sensor, pointing forward.
I still need some more flights (different shaped obstacles, more kinds of materials) to understand if it’s sensor reading or ardupilot sw to be fixed.
Also, i would like to have opportunity to assign some functions to a switch and pot (turn avoidance by switch, and tune AVOID_MARGIN by a pot (with selectable MIN and MAX values) similar to what i can do with CH6 and PID tuning. Time for a PR?
The problem that the Omnbius F4 Pro connection to the external compass cannot be calibrated still exists. The compass is 5883, and the flight controller can correctly identify it, but it cannot be calibrated.
Yeah me too, i have the Omnibus F4 V6(full size but running the nano firmware), managed to get it most of it working e.g. accel calibration, SBUS working, but i have the same problem.
When you enter the calibation for compass there is no progress bar so no calibration can be done.
Today, I re-purchased a separate external compass MHC5883L, and connected it correctly to the OmnibusF4 Pro V3. After connecting the MP, I can recognize this external compass. I will enter the compass calibration page as soon as possible and start the compass. Calibration, finally have a percentage progress bar, but after the rotation in all directions, the progress bar is finally stuck in the 99% position can not be completed automatically, I did not wait, but chose to click the “Accept” button, and then restarted Fly control, re-enter the compass page and see the value of the calibrated compass.
I installed it on a radiolink minipix, everything works except for the radio inputs.
I using a Flysky receiver with the ibus protocol…Is a bug???
Someone can help me?
F4 V5.1, latest rc8, same problem with compass calibration. PreArm: Compass not calibrated. The external compass with GPS is well recognized. I tried relax mode. When I reach 99% progress meter starts again. I tried to click on the Accept button when around 90%, with the previous version was working ok.
I figured this out…
Do the old style mission planner ‘live calibration’. (Hold down shift or control (i forget which) when clicking the “compass” menu item in MP)
It should work.
Then, go back and do the onboard calibration, and it should save.
At least, that worked for me yesterday, w/ the latest beta.
For me I was able to calibrate with QGC 3.4.2 without any problem. Was not working using latest beta MP. Must be a MP issue. What’s strange, when I come back to MP and go to the Compass Tab, I have a Roll 180 now…
