Yes it supports both - but you need to use the STM32 version which I don’t think they have shipped yet.
1 Like
Bench testing is going well no noise. Is this firmware safe to fly with? My plane is a little fragile. So i need a little reassurance. 
1 Like
I flashed and flew plane460-beta5-test today. Abnormal motor noise was gone in all flight modes tested (FBWA, Cruise, Manual, qStabalize, qHover, qLoiter). Plane flew great on this build with no issues noted. Tiltrotar triplane, SpeedyBee f405 wing and SpeedyBee 4in1 ESC running BLheli32 with Dshot 600.
2 Likes
Now that the vtol notch filters work in fixed wing flight. Should we redo autotune?
Today while using 4.6.0 beta 4 with the vtol motor noise fix. My flight controller rebooted itself. It happened after I disarmed. When i picked up the plane the esc made the start up beeps. I checked yappu and sure enough it rebooted. Any idea what happened and is it safe to keep using? Matek f405 TE bdshot FC.cpu load is around 46-58% the upper end during vtol.
No log of the reboot since it happene after i disarmed.
1 Like
we keep logging for 15 seconds after a disarm to help with these sorts of issues. Please post the bin log of the flight. Also please check if there is a crash_dump file on the microSD. If you had a GCS connected then please post the tlog
I think this is the log. Im not 100% sure
did you have a GCS connected? Most GCS will save a tlog for all MAVLink traffic. That tlog could help a lot
Sorry I dont. Could you take a look at my notch filters? Im stuck. There is a noise around 25hz i can seem to get rid of. It varies from 23-33hz so fixed notches dont work. The esc telemtry notches won’t go that far down. Throttle based notches kinda work. Any suggestions would be greatly appreciated. Plane is a 1080mm wing span front tilt rotor vtol. Tricopter
Flew the Beta-5 Test build today on the VTOL (Matek F405-TE) in question and there was no noise.
1 Like
Found another issue, ESC temperature in OSD is occasionally missing.
It seems to be related to arming, i.e. nothing on first arming but on second.
EDIT:
Have to amend that info. I’ve seen ESCTEMP vanishing from OSD inflight.
Seems that this line returns FALSE
ESC RPM is frequently updated. Is it possible that bluejay stops sending temperature by itself?
do you have the bin log which covers a time when the ESCTEMP disappears?
1 Like
Aye, spamming your inbox as always 
EDIT:
There is another issue visible in that log for ESCTEMP.
I’m seeing ESCTEMP jump 28 to 162 or 32 to 164 and alike.
That is bluejay v21.0 on Dys XSD7A.
I’m digging in the get_highest_temperature() function. In the log, ESC.Temp looks clean and the jumps are up to 44degC. I don’t know where the bit7 flipping in OSD comes from.
which inbox? I don’t see it
We have just released 4.6.0-beta5 for testing. This includes some important fixes from beta4.
The largest change relates to how QAssist works, and also what happens if you switch to QHOVER or QLOITER while you the aircraft is a long way outside the Q_ANGLE_MAX angle limit. In both cases the change means the recovery to normal attitude should be faster and more reliable.
As usual, all testing welcome!
Full list of changes from 4.6.0-beta4:
- Board specfic changes
- MFT-SEMA100 compass orientation fix
- SpeedyBee F405 AIO support
- Driver bug fixes and enhancements
- Bdshot locking issue fix for slow boards that could cause the flight controller to crash
- BMP280 barometer error handling during init improved
- CADDX gimbal RC update rate fixed
- Hexsoon 77G and 24G radar support
- IE FuelCell generator data rate increased
- IIS2MDC compass support
- LD19/LD06 proximity sensor data length sanity check fix
- RC output cork/push fix to avoid potential motor knocking
- SBF MosaicX5 packets with invalid length ignored
- SPL06 barometer accuracy improvements
- Ublox M10 configuration fix
- Plane specific fixes and enhancements
- Tiltrotor motor check fixed used in throttle control handover from VTOL to forward flight
- Improved QAssist and VTOL mode recovery from bad attitudes
- Fixed rudder output in VTOL modes
- Added fix for indecision in the roll controller close to inverted
- Ensure tiltrotors use consistent fixed wing and VTOL rates
- Clear inverted control flag on Q-mode entry
- Auto-deploy landing gear on all fixed wing landings when enabled
- Prevent learning bad ARSP_RATIO values when not flying
- Rover specific fixes and enhancements
- Lua bindings for Follow mode
- WATER_DEPTH mavlink message rate fix
- Parameter description improvements
- ADSB_LIST_ALT param desc improved
- Alphabetised type params for CAN, Mount, OptFlow, Proximity, Rangefinder, Serial Manager
- Copter’s battery failsafe action gets “Brake or Land”
- LOG_FILE_BUFSIZE units fixed
- MOT_THST_HOVER range fixed
- SERIALx_BAUD value added for PPP networking
- Bug Fixes and minor enhancements
- Arming check for EKF3 velocity innovations
- Copter’s LOG_BITMASK includes PIDs by default
- DO_SET_ROI_LOCATION mission command support
- MCU min/max voltage logging fix
- MIS_OPTION parameter handling fixed
3 Likes
Just tried flashing and I got Beta4. The discussion board says I’m 7 hours after your post. I checked the firmware web page and its only got Beta 4 for plane. I checked copter and it’s showing Beta 5.
beta5 is still building for plane, sorry. As we have a lot of boards and targets now (a total of over 1600 builds to do) it takes quite a long time.
If you like, you can follow the progress here:
https://firmware.ardupilot.org/Tools/BuildSizes/builds.html
1 Like
You should have received two E-Mails with a tar.xz file ~5-10Mb each.
Maybe I should not mention the addr for every bot to find, sorry ^^;
sorry, I don’t see them. Maybe ping me on discord?
Confirmed fixed.
Did a short flight with 10kt of wind, no issues seen except the issue with the ESCTEMP which can be bluejay not sending anything.
Also found out that I unintentionally build a THRO(W)VL, pun intended.
1 Like