betaflight / betaflight

Open Source Flight Controller Firmware
GNU General Public License v3.0
8k stars 2.86k forks source link

Motors on F72x not working with final 4.5 #13598

Closed TheIsotopes closed 5 days ago

TheIsotopes commented 2 weeks ago

Describe the bug

since final release the motors on my f7 quad not working anymore.

last fly was with 8d1d8872d without any problems

To Reproduce

using latest final on MATEKF722MINI

plug in the battery, arming the quad and use the throttle but the motors dont turn

motor beeper also not working

Expected behavior

running motors on final release

Support ID

Id: "f69576ff-9b3e-41fb-ae2b-c25f7b783118"

Flight controller

MATEKF722MINI

Other components

No response

How are the different components wired up (including port information)

No response

Add any other context about the problem that you think might be relevant here

No response

hendraramadani commented 2 weeks ago

same problem , motor 3 always has an error TMOTORF7

image

SteveCEvans commented 2 weeks ago

Make sure your ESC is up to date. I’ve just been flying an F722 on 4.5.0 without issue.

TheIsotopes commented 2 weeks ago

@SteveCEvans I'm using latest BlHeli_32 32.10. I haven't seen anything more recent yet.

haslinghuis commented 2 weeks ago

Recommended firmware for BLH32

TheIsotopes commented 2 weeks ago

@haslinghuis OK, that's new to me. I'll test it right away. Have these problems with Blheli_32 already been discussed with the developer?

haslinghuis commented 2 weeks ago

@TheIsotopes We are moving in direction of BlueJay and AM32.

Reported an issue here: https://github.com/bitdump/BLHeli/issues/713

TheIsotopes commented 2 weeks ago

@haslinghuis ok, the same problem also occurs with blheli_32 version 32.7.

Any other good advice?

TheIsotopes commented 2 weeks ago

@haslinghuis @SteveCEvans For your information: I don't use any rpm filter or telemetry, so no dshot_bidir either. I couldn't find the problem on my f405 quads, everything works as expected here.

TheIsotopes commented 2 weeks ago

@haslinghuis ok with set dshot_bitbang = OFF beeper and motors working again.

Should the newer versions of blheli_32 generally not be flashed or do the errors only occur with activated rpm filtering?

haslinghuis commented 2 weeks ago

@TheIsotopes

ITCM_RAM: 14512 B 16 KB 88.57%

betaflight_4.6.0_STM32F7X2_MATEKF722MINI.zip

haslinghuis commented 2 weeks ago

O wow - did not think disabling bitbang would make the difference - so that's why I removed the post :)

Using 32.8 myself since 2019 - when trying 32.10 it did not work on my test subject (H750).

TheIsotopes commented 2 weeks ago

your firmware version only works also with set dshot_bitbang = OFF by using 32.7 and 32.10

haslinghuis commented 2 weeks ago

If you could test RPM filter is working with dshot_bitbang disabled we could update board configuration for MATEKF722MINI.

TheIsotopes commented 2 weeks ago

With your version from above and set dshot_bitbang = OFF the RPM filter will deactivated.

EDIT: same testresult with latest release version

haslinghuis commented 2 weeks ago

@SteveCEvans

Is there a way to improve dshot_bitbang = AUTO detection depending on dshot_bidir setting?

pkojder commented 1 week ago

Same issue with SpeedyBee F7 V3, motors not spining at all (tested in BF Configurator, BlheliSuite32 and after arming a quad from radio). ESC are up to date (32.10). Moreover, enabling Bidirectional DSHOOT shows rpmfilter flag and Poblems with comunication occurs via USB and Bluetooth. After downgrading to 4.3.3 works as a charm. BF 4.5 is definatelly realised to soon. Guys you have screwed.

spadeadam commented 1 week ago

Same issue with Airbot F7 and Blheli-S 4 in 1 Esc, everything works with BF 4.4 then “upgraded” to BF 4.5.0 No motor output , tried DShot 300 and DShot600. Flashed back to BF 4.4 everything works OK again ?

kostamilorava commented 1 week ago

Enabling dshot_bidir fixes this problem for Matek F722 MK4 Link here

blckmn commented 5 days ago

Same issue with SpeedyBee F7 V3, motors not spining at all (tested in BF Configurator, BlheliSuite32 and after arming a quad from radio). ESC are up to date (32.10). Moreover, enabling Bidirectional DSHOOT shows rpmfilter flag and Poblems with comunication occurs via USB and Bluetooth. After downgrading to 4.3.3 works as a charm.

BF 4.5 is definatelly realised to soon. Guys you have screwed.

Did you try setting dshot bit bang = off?

SteveCEvans commented 5 days ago

To confirm, is this issue only being seen with bidirectional DSHOT disabled?

haslinghuis commented 5 days ago

In my understanding on some issues so far:

SteveCEvans commented 5 days ago

Just checked DSHOT600 with a Holybro Tekko32 F3 Metal ESC and TMOTORF7 FC.

With bi-drectional DSHOT disabled I see:

image

And with it enabled I see:

image

So, we're getting the expected inversion, telemetry is working, and the error count I'm seeing as zero.

The DSHOT value is stuck at zero though with bidirectional DSHOT disabled.

SteveCEvans commented 5 days ago

@TheIsotopes Please test https://github.com/betaflight/betaflight/pull/13633

TheIsotopes commented 5 days ago

@SteveCEvans working again, thanks for fixing it.

pkojder commented 5 days ago

Is it normal when i’m arming quad on bench motors are slowly increasing RPMs and when i’m slowly move roll and pitch motors are changing smothly rpm but when i increase trothle to 50% motors motors stops to increase rpms and just respons to throthle normaly but roll and pitch causes motors to to make knock sounds? Wysłane z iPhone'aWiadomość napisana przez J Blackman @.***> w dniu 12.05.2024, o godz. 22:00:

Same issue with SpeedyBee F7 V3, motors not spining at all (tested in BF Configurator, BlheliSuite32 and after arming a quad from radio). ESC are up to date (32.10). Moreover, enabling Bidirectional DSHOOT shows rpmfilter flag and Poblems with comunication occurs via USB and Bluetooth. After downgrading to 4.3.3 works as a charm. BF 4.5 is definatelly realised to soon. Guys you have screwed.

Did you try setting dshot bit bang = off?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>