See this thread where I gave the wrong answer.
Quicktune
It works of a f4. I used it with a heewing fx-405 v2. No sd card needed. I had problems with a matek f405 te. I had gps configuration problems.
I did see that thread, my question was more of if the script is able to be used in Copter firmware as well, as all I’ve found so far is related to plane firmware, in the custom firmware builder. If I build for a copter target in the custom firmware builder and include that “plane” specific feature like @Rolf mentioned in the other thread, will I be able to use it when flying a copter?
@Target0815 if the protocol is the same then we should just be able to support it by adding the baudrate to the list supported by F.Port2
If I gave you a test firmware could you try it? What board would you need it for?
1 Like
unfortunately you can’t use it with copter, the copter lead developers declined to have it supported in copter. On copter you have to use the lua script for quicktune
Ah I see. Thanks, @tridge !
We have just released plane 4.6.0-beta3. This is a minor update over beta2.
- Board specfic changes
- AEROFOX-H7 support
- AET-H743-Basic support
- ESP32 memory initialisation fix
- MicoAir743AIO and MicoAir743v2 support
- OrqaF405Pro supports ICM42688 IMU
- TBS Lucid Pro support
- Plane related enhancements and bug fixes
- RC aux channel option documented for C++ QuikTune
- TECs uses external HAGL (if available) for landing
-
DDS/ROS2 pre-arm check and copter takeoff service
-
Bug Fixes and minor enhancements
- BATTx_OPTIONS param desc fixed
- BLHeli telemetry ESC index fixed on boards with IOMCU
- CAN manager logging critical race condition fixed (only occurred if CAN_LOGLEVEL was 1 or higher)
- DShot EDTv2 logging fixed
- ICM45686 IMU FIFO read rate fixed (could read unnecessarily quickly)
- LDRobot LD06 proximity driver prevents possible read buffer overrun
- LDRobot LD06 proximity driver averages over 2deg slices (was 12 deg)
- RunCam/OSD menu movements obey RC channel reversal
- Topotek camera gimbal pitch rate control direction fixed
- TradHeli AutoTune rate and accel limiting fixed
- VTOL-quiktune script gets QUIK_ANGLE_MAX to prevent bad oscillation if tuning algorithm fails
As always we very much appreciate any help we can get with beta testing so all feedback is very welcome!
3 Likes
Flights and transitions with a small tri- tilt VTOL (Matek H743 Wlight, Qstabilize, FBWA) without any anomalies. With a small fixed wing, take-off, FBWA and guided mode (guidance controlled by LUA script) worked with 4.6.0 beta 3 perfectly.
Rolf
2 Likes
4 Likes
Hello, I have been flying with custom build of 4.6.0beta2 without problems. Now I have compiled 4.6.0beta3 with same many custom defaults for MatekF405-Wing-bdshot (like remove VTOL and add some old drivers and more exotic features). I have tried latest stable and beta Mission Planners and got this:
This is just after uploading new firmware with any setup.
Any ideas?
One flight with the sub250g Zohd Drift. Nothing spectacular apart from the known degradation / intended change for planes without airspeed sensor, the workaround was communicated.
Minor annoyance, the deprecation warning for fence_autoenable=1 should be 50 chars, not 51 chars. I only see “3” in Yaapu with my ELRS customization.
One minor bug found after testing RC_LONG_FAILSAFE.
Clearing RC_LONG_FAILSAFE switches OSD back to screen 1 for unknown reason.
Another thing. There seem to be new log messages that are not handled by tools yet.
Logline 0: Read data without having a valid format descriptor - Message type is 118
And a last thing that I noticed, not sure when it was introduced though, I have to manually add my trim pitch to DesPitch to get the correct value for DesPitch in Logs. Is this tracked somewhere?
Hi,
This is probably a very quick one to answer and I hope I have posted in the appropriate location, the release notes above state support for TBS Lucid Pro, I have tried flashing one and I am able to flash successfully, but then it appears to be dead, no led’s flashing or anything.
I can activate the DFU and flash back to INav everything is OK, is this because Chibios still does not support the AT32F435RMT7 that the TBS Lucid Pro is using?
Thanks.
The details of the version of the Lucid Pro that Ardupilot supports is here:
TBS Lucid Pro
Thanks. yes that’s exactly what I followed, but having done so the FC powers up with no LED’s and when you plug it into the PC its not detected.
That page says - MCU - STM32F405 32-bit processor running at 168 MHz
TBS lists MCU AT32F435RMT7, 288MHz.
I think that’s the problem and its due to ChibiOS not supporting AT32 based chips.
Steve.
Another long range flight with 4.6-beta4, ~15km / 28min, almost no wind, no steep climbs or descent.
Only issue found was that altitude correction for baro drift Ek3-OGN-HGT-MASK Bit0 does not work for me.
Raises origin 10m above ground while baro alt is close to 0. I think it was already buggy in plane 4.5.7. I haven’t found the value yet that OSD displays as -10m altitude on touchdown but I’m digging.
EDIT: Found the value and the suspected cause, apparently a wrong field evaluation ~94m instead of ~88m, propagates backwards into relative altitude when corrections have finished.
1 Like
I flew 4.6.0 Beta 4 on a T-1 ranger VTOL. No firmware related issues. Quick tune on the Matek F405-VTOL board worked great.
Edit: I forgot to mention, I am getting the spamming of Sending unknown message (45).
2 Likes
We’ve released plane 4.6.0-beta4. Sorry for being slow in making this post!
The full changes vs -beta3 are in the Release Notes and copied below:
- Board specfic changes
- BETAFPV F405 supports DPS310 baro
- BETAFPV F405 board variants added
- Driver enhancements
- CADDX camera gimbal support
- UltraMotion CAN servo support
- Copter specific fixes and minor enhancements
- SysId mode uninitialised variables fixed
- ARMING_NEED_LOC blocks arming regardless of mode until position estimate is good
- Bug Fixes and minor enhancements
- AM32 ESC passthrough fixed
- BMP581 baro initialisation fix
- DDS/ROS2 driver waits indefinitely until companion computer running ROS2 starts
- Lua script potential deadlock fix when initialising mavlink in script
- Mcast and HW CAN bridging disabled by default
- Plane’s TILT log message only logged on tilt-rotors
- ROMFS race condition when opening files that caused apparent script corruption fixed
- Serial flow control support on UARTS 6 to 8
- Serial passthrough fix to restore parity upon completion
- Serial protocol parameter fix to include I-Bus Telemetry
- uAvionix ping200X driver fixes
- Video stream information lua script param index fixed (avoids param conflict with other scripts)
- ViewPro object tracking fixed
1 Like
I noticed some issue on auto-landing completion.
I thought it was a glitch or that I touched a switch accidentally but it is reproducible.
The plane does land, but does not disarm afterwards.
Instead it switches to RTL with a message:
Mission complete, changing mode to RTL
Mode:11 ModeNum:11 Reason:8