betaflight / bidircfg

9 stars 15 forks source link

BF 4.0 RC2 - DALRC F405 motors 1 and 2 not spinning (Dshot Bidir) #4

Closed digex closed 5 years ago

digex commented 5 years ago

Describe the bug After installing BF4.0 RC2 and blheli FW 32.6.7 , with bidirectional dshot and rpm filters enabled, motor 1 and motor 2 doesn`t spin.

When I disable dshot_bidir all motors spin correctly.

To Reproduce install BF4.0 RC2 and blheli FW 32.6.7 , enable bidirectional dshot and rpm filters.

Expected behavior After arming motor 1 and 2 does`t spin.

This is installed https://github.com/betaflight/bidircfg/blob/master/DALRCF4.cf

timer C06 0
timer C07 1

dma pin A10 1
dma pin A08 2
dma pin C08 1

set scheduler_optimize_rate=on
set dshot_burst=off
set dshot_bidir=on

set dyn_notch_width_percent = 0
set dyn_notch_range = medium
set dyn_notch_q = 250

set gyro_lowpass_hz = 150
set dyn_lpf_gyro_min_hz = 150
set dyn_lpf_gyro_max_hz = 575

set dterm_lowpass2_hz = 0

set d_min_pitch=29
set d_min_roll=27
set d_min_boost_gain=35

set debug_mode=rpm_filter

set motor_pwm_protocol=DSHOT600
set gyro_sync_denom = 2
set pid_process_denom = 1

save

status

MCU F40X Clock=168MHz (PLLP-HSE), Vref=3.28V, Core temp=50degC
Stack size: 2048, Stack address: 0x1000fff0
Config size: 3032, Max available config: 16384
GYRO=MPU6000, ACC=MPU6000
System Uptime: 16 seconds, Current Time: 0000-01-01T00:00:00.000+00:00
CPU:14%, cycle time: 254, GYRO rate: 3937, RX rate: 33, System rate: 10
Voltage: 1556 * 0.01V (4S battery - OK)
I2C Errors: 0
Arming disable flags: RXLOSS CLI
Dshot reads: 119976
Dshot invalid pkts: 369
Dshot irq micros: 2
Dshot RPM Motor 0: 0
Dshot RPM Motor 1: 4095
Dshot RPM Motor 2: 88
Dshot RPM Motor 3: 78
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 

# diff

# version
# Betaflight / DALRCF405 (DLF4) 4.0.0 Mar 14 2019 / 11:09:55 (360afd96d) MSP API: 1.41

# start the command batch
batch start

board_name DALRCF405
manufacturer_id 

# name

# resources

# timer
timer C06 0
timer C07 1

# dma
dma pin C06 NONE
dma pin A10 1
# pin A10: DMA2 Stream 6 Channel 6
dma pin A08 2
# pin A08: DMA2 Stream 3 Channel 6
dma pin C08 1
# pin C08: DMA2 Stream 4 Channel 7
dma pin C07 NONE

# mixer

# servo

# servo mix

# feature

# beeper

# beacon

# map

# serial

# led

# color

# mode_color

# aux

# adjrange

# rxrange

# vtx

# rxfail

# display_name

# master
set gyro_sync_denom = 2
set dyn_notch_range = MEDIUM
set dyn_notch_width_percent = 0
set dyn_notch_q = 250
set dyn_lpf_gyro_max_hz = 575
set dshot_burst = OFF
set dshot_bidir = ON
set motor_pwm_protocol = DSHOT600
set pid_process_denom = 1
set debug_mode = RPM_FILTER
set scheduler_optimize_rate = ON

# profile
profile 0

set dterm_lowpass2_hz = 0
set d_min_roll = 27
set d_min_pitch = 29
set d_min_boost_gain = 35

# rateprofile
rateprofile 0

# end the command batch
batch end
SebiWolze commented 5 years ago

seems to be the same problem like here: https://github.com/betaflight/betaflight/issues/7759

digex commented 5 years ago

Help. https://github.com/betaflight/betaflight/issues/7759#issuecomment-474729874 set beeper_frequency = 0 not working for dalrc f405 aio Motors 1 and 2 not spinning

JSpielz commented 5 years ago

I have this EXACT same problem.

While I was trying to test out the RPM filter/Bidirectional Dshot, motor number 1 wouldn't spin or boot up and motor number 2 would make the startup tone a couple of seconds after 3 & 4 and not spin as well. After a bit of troubleshooting, I realized that by turning " set Dshot_burst = on" my motors would spin normally and make the startup tone up at the same time. Once I turned dshot_burst back off and changed nothing, the same thing happened.

I started from 4.0 defaults and pasted the snippet for the DalRC F405 from the RPM filter page and that is when I noticed the issue. I didn't change anything else other than the PIDs. I even tried updating the firmware to the current latest build of 4.0 (3/22) and still the same thing.

I just wanted to let you guys know. Hopefully you can solve the issue.

Thanks so much for all your work on BetaFlight!

(I have a DalRC F405, JB30a 4-in-1, TBS Unify 5G8 V3, FlySky X6B, Foxeer Predator V3, Johnny FPV 2700kv 2207)

ghost commented 5 years ago

Same here i can confirm the issue.

bobbfwed commented 5 years ago

Also confirm this is happening. I'm using BF 4.0 RC5 on DALRC F405, and the 32.6.1 test code firmware for my DALRC Engine 40A ESCs. Motors 1 and 2 don't spin, and they don't seem to get startup tone.

EnricoBara commented 5 years ago

Confirm the same as @bobbfwed said

VirtualEnder commented 5 years ago

Fixed in PR #3 waiting on merge.

bobbfwed commented 5 years ago

Just tested it with RC6 and the newest version of commands on https://github.com/betaflight/bidircfg/blob/master/DALRCF4.cf and it worked great!

Rclf commented 5 years ago

same here on clracingf4 ,motors 1 and 2 do not spin. That is on 32.61

Also when connecting to blheli32 suite after check it sees only esc 3 and 4. When checking again it sees all 4 but on the first 2 I get input bad frames. I am reflashing all over both escs and fc, will report again

Dshot reads: 6938 Dshot invalid pkts: 0 Dshot irq micros: 3 Dshot RPM Motor 0: 4095 Dshot RPM Motor 1: 4095 Dshot RPM Motor 2: 0 Dshot RPM Motor 3: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

after applying

timer b00 1 timer b01 1 timer b04 none timer b08 none

dma pin b00 0 dma pin b01 0 dma pin b04 none dma pin b08 none

I get this status but still motors 1 and 2 are not spinning

Dshot reads: 0 Dshot invalid pkts: 0 Dshot irq micros: 3 Dshot RPM Motor 0: 0 Dshot RPM Motor 1: 0 Dshot RPM Motor 2: 0 Dshot RPM Motor 3: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

edit 2. Nope, as soon as I set dshot_bidir=on motors 1 and 2 stop working, everything works when I set dshot_bidir=off.

my hex is KS_BLHeli_32_30A_Multi_32_61

stale[bot] commented 5 years ago

This issue / pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week.

stale[bot] commented 5 years ago

Automatically closing as inactive.