The flight controller i am using is an Omnibus F4 pro v3.
I have a quadcopter with Matek H743, i will install 4.6.2 and see if that works OK.
Does 4.6.2 take up more memory than the 4.5.7?
Edit: v4.6.2 is working fine on Matek H743.
Loaded 4.6.2 on a X21-F777 FC, Yaapu works fine with a Frsky R9mini Rx set to Fport and Frsky X20 Tx running Ethos
Matek H743 reads Yaapu fine with v4.6.2, and R9mm. It has 2MB flash.
Omnibus F4 pro v3 doesnât read Yaapu with R9mm⌠It has 1MB flash.
Could lack of memory be the cause?
Hi @Colindo,
OK, so the feature may not be included on smaller boards (Iâm just guessing) so the custom build server may be used to include it.
If this is the case then we will need to have a discussion in the dev team about what we can do about this sort of thing. We certainly see a good number of users wanting to use a feature thatâs not included in the minimalist firmware we supply on the F4 boards and at the same time we simply canât fit every feature on the F4 boards.
The version 4.5.7 is OK for my F4 board. It does all i need. Other than that i can use the H743 board for future upgrades.
4.6.2 with BLHeli_S, 16.7 ESC pass-through is not working. 4.6.1 is okay.
#4.6.2
2025/07/31 14:47:42: Opened serial port
2025/07/31 14:47:42: MultiWii API version received: 1.42.0
2025/07/31 14:47:42: Flight controller info, identifier: ARDU version: 3.3.1
2025/07/31 14:47:42: Running firmware released on: Mar 16 2018 08:42:29
2025/07/31 14:47:42: Board: ARCH, version: 0
2025/07/31 14:47:42: Unique device ID received - 0x02100263334470f39333335
2025/07/31 14:48:03: Trying to read 4 ESCs
2025/07/31 14:48:14: Failed processing command cmd_DeviceRead after 10 retries.
2025/07/31 14:48:14: ESC 1 read settings failed Message not OK MessageNotOkError: Message not OK
2025/07/31 14:48:14: Error: MessageNotOkError: Message not OK
2025/07/31 14:48:14: Failed reading ESC 1
2025/07/31 14:48:26: Failed processing command cmd_DeviceRead after 10 retries.
2025/07/31 14:48:26: ESC 2 read settings failed Message not OK MessageNotOkError: Message not OK
2025/07/31 14:48:26: Error: MessageNotOkError: Message not OK
2025/07/31 14:48:26: Failed reading ESC 2
2025/07/31 14:48:37: Failed processing command cmd_DeviceRead after 10 retries.
2025/07/31 14:48:37: ESC 3 read settings failed Message not OK MessageNotOkError: Message not OK
2025/07/31 14:48:37: Error: MessageNotOkError: Message not OK
2025/07/31 14:48:37: Failed reading ESC 3
2025/07/31 14:48:49: Failed processing command cmd_DeviceRead after 10 retries.
2025/07/31 14:48:49: ESC 4 read settings failed Message not OK MessageNotOkError: Message not OK
2025/07/31 14:48:49: Error: MessageNotOkError: Message not OK
2025/07/31 14:48:49: Failed reading ESC 4
2025/07/31 14:48:51: Closed port
#4.6.1
2025/08/04 16:11:45: Chrome (138.0.0.0) on Windows
2025/08/04 16:11:54: NotFoundError: Failed to execute 'requestPort' on 'Serial': No port selected by the user.
2025/08/04 16:14:24: Port selected
2025/08/04 16:14:27: Opened serial port
2025/08/04 16:14:27: MultiWii API version received: 1.42.0
2025/08/04 16:14:27: Flight controller info, identifier: ARDU version: 3.3.1
2025/08/04 16:14:27: Running firmware released on: Mar 16 2018 08:42:29
2025/08/04 16:14:27: Board: ARCH, version: 0
2025/08/04 16:14:27: Unique device ID received - 0x02900383334471431383339
2025/08/04 16:14:28: MSP command failed: Offset is outside the bounds of the DataView
2025/08/04 16:14:29: MSP command failed: Offset is outside the bounds of the DataView
2025/08/04 16:14:30: MSP command failed: Offset is outside the bounds of the DataView
2025/08/04 16:14:31: MSP command failed: Offset is outside the bounds of the DataView
2025/08/04 16:14:32: MSP command failed: Offset is outside the bounds of the DataView
2025/08/04 16:14:33: MSP command failed: Offset is outside the bounds of the DataView
2025/08/04 16:14:34: MSP command failed: Offset is outside the bounds of the DataView
2025/08/04 16:14:36: Trying to read 4 ESCs
2025/08/04 16:14:37: Read ESC 1: J-H-40 - BLHeli_S, 16.7
2025/08/04 16:14:39: Read ESC 2: J-H-40 - BLHeli_S, 16.7
2025/08/04 16:14:40: Read ESC 3: J-H-40 - BLHeli_S, 16.7
2025/08/04 16:14:42: Read ESC 4: J-H-40 - BLHeli_S, 16.7
2025/08/04 16:14:42: Done reading ESCs
1 Like
Ok this is clearly the passthrough fixes in 4.6.2, Iâll have to se if I can find a BLHeli_S ESC to test.
1 Like
04/08/2025 11:42:48 : Frame: QUAD/BF_X
04/08/2025 11:42:48 : RCOut: DS600:1-4 NeoP:9
04/08/2025 11:42:48 : KakuteH7Mini-Nand 003F001D 35325119 38383730
04/08/2025 11:42:48 : ChibiOS: c6d0293e
04/08/2025 11:42:48 : ArduCopter V4.6.2 (1ebd4d99)
Yaapu: on a home test it seems to work:
BTW, FC does not have ÎźSD socket. I donât know if it is considered a âsmall boardâ.
1 Like
Aw, I think I see this with Bluejay too.
(in a branch forked off commit 77cf38b9faad2815e194c7a2cb6625624e2bc879).
Not sure if it is the same issue or not, but I was trying to switch direction of one motor yesterday on a build where passthrough reportedly used to work, and failed (despite multiple attempts at re-reading the configuration).
By the way, these re-reading attempts were unusually slow, I believe taking more than 10 seconds per single attempt on a motor. This used to be much faster, both successful and failed reads.
It seems like Iâve found a bug in the SBF GPS driver introduced in Copter-4.6: GPS 1: SBF is not fully configured (5/0/4/3)
Seems LOIT_SPEED/WPNAV_SPEED are not working properly. I have both set to 3500cm/s (about 125km/h) however I am unable to fly faster than 2000cm/s (default max value) including RTL (using WPNAV_SPEED) limited to 2000cm/s (~70km/h). I do not have this issue with 4.5.7
Itâs also constrained by ANGLE_MAX and the JERK and ACCEL limits to get there - worth looking at those
1 Like
This lengthy post is quite old now but still applicable for the parameters that matter:
High Speed Auto Mission
2 Likes
I will check, but I am pretty sure that with settings I have now I was reaching over 100km/h without issues. However⌠tool a look into the logs, and seems pitch is maxing out at 30deg. And there might be that I had it set to 45. Will check.
Set it to 80deg Thatâs what I have done.
I quickly tested today and indeed lean angle was too small, and this is some coincidence, that default angle 30deg corresponds almost exactly max speed 20m/s. I wonder now if I need to re-tune with higher angle or not.
Depends on how you tune. I manually tune using Transmitter Based tuning and will certainly thrash it around >30deg to test attitude control.
1 Like
In general the most critical attitude controller gains are for the lower level rate controller which doesnât directly depend upon the vehicleâs lean angle. At higher speed the vehicle will have more disturbances so the tune may need to be better but itâs not really a different tune.. just a better tune.
2 Likes
i use Flyspark F4V1 fc. when i install firmware, select Speedybeef4 and upload, download from internet after that unplug board press ok and plug in wait 20 seconds Error: no response from board show. pl give me solution
How do you know thatâs the right firmware for that board?