Posts: 863 Threads: 43 Likes Received: 286 in 202 posts Likes Given: 12 Joined: Nov 2018 Reputation: 5 My brother, whom I'm getting into FPV, bought one. There are no LED's lighting up on the underside when trying to bind or hook up to Betaflight. Is the FC toast or is there something I can do to fix it for him?
Deal Here's the Deal
10" 6S FR10-G Long Range, 5" 6S Rooster, 5" 6S Badger, 5" 6S QAV-S, 5" 4S Badger, 5" 4S Phreakstyle Slam, 5" 6S Yema, 5" 4S Stark, 3" 4S Gecko, and a 3S 2.5" Tadpole, all of which are Crossfire. Tinyhawk, Tinyhawk S, and a DJI Spark. And projects on the bench....
![[-]](https://intofpv.com/images/collapse.png) • Posts: 21,414 Threads: 595 Likes Received: 9,037 in 6,688 posts Likes Given: 1,428 Joined: Jun 2018 Reputation: 796 Do you get no LEDs if you plug in a USB or a LiPo, or only for one of those?
And can you connect to Betaflight via the USB port? • Posts: 863 Threads: 43 Likes Received: 286 in 202 posts Likes Given: 12 Joined: Nov 2018 Reputation: 5 When plugging in a lipo, only three beeps, and no LED's light up on the underside. Will not connect to Betaflight. All my other quads, five total, connect fine.
10.6.0 Betaflight.
Deal Here's the Deal
10" 6S FR10-G Long Range, 5" 6S Rooster, 5" 6S Badger, 5" 6S QAV-S, 5" 4S Badger, 5" 4S Phreakstyle Slam, 5" 6S Yema, 5" 4S Stark, 3" 4S Gecko, and a 3S 2.5" Tadpole, all of which are Crossfire. Tinyhawk, Tinyhawk S, and a DJI Spark. And projects on the bench....
• Posts: 21,414 Threads: 595 Likes Received: 9,037 in 6,688 posts Likes Given: 1,428 Joined: Jun 2018 Reputation: 796 If you plug in both a LiPo and the USB cable, can you connect to Betaflight then? • Posts: 863 Threads: 43 Likes Received: 286 in 202 posts Likes Given: 12 Joined: Nov 2018 Reputation: 5 Negative....
Deal Here's the Deal
10" 6S FR10-G Long Range, 5" 6S Rooster, 5" 6S Badger, 5" 6S QAV-S, 5" 4S Badger, 5" 4S Phreakstyle Slam, 5" 6S Yema, 5" 4S Stark, 3" 4S Gecko, and a 3S 2.5" Tadpole, all of which are Crossfire. Tinyhawk, Tinyhawk S, and a DJI Spark. And projects on the bench....
• Posts: 21,414 Threads: 595 Likes Received: 9,037 in 6,688 posts Likes Given: 1,428 Joined: Jun 2018 Reputation: 796 What appears in Windows Device Manager when you plug the USB cable in? And do you hear the usual Windows "bing bong" sound when you plug it in or not? • Posts: 863 Threads: 43 Likes Received: 286 in 202 posts Likes Given: 12 Joined: Nov 2018 Reputation: 5 No sound, and it doesn't show up under "Device Manager".
Deal Here's the Deal
10" 6S FR10-G Long Range, 5" 6S Rooster, 5" 6S Badger, 5" 6S QAV-S, 5" 4S Badger, 5" 4S Phreakstyle Slam, 5" 6S Yema, 5" 4S Stark, 3" 4S Gecko, and a 3S 2.5" Tadpole, all of which are Crossfire. Tinyhawk, Tinyhawk S, and a DJI Spark. And projects on the bench....
• Posts: 21,414 Threads: 595 Likes Received: 9,037 in 6,688 posts Likes Given: 1,428 Joined: Jun 2018 Reputation: 796 Sounds like it could be a faulty FC. The Crazybee boards aren't known to be the best, especially the ones prior to the V3 boards. The Mobula 7 HD comes with a V2 board. The odd thing is that the ESCs are playing the first part of the startup tunes so the ESCs at least must be working from LiPo voltage. You didn't try flashing a new version of Betaflight firmware did you (or your brother)? Just thinking that maybe the wrong target might have been flashed to it thus disabling MSP (which is for the USB connection). I would try and connect it in DFU (boot) mode. To do that you will need to look on the underside of the Mobula 7 and locate the boot button on the FC throug the frame. Then ise something to hold that button in while connecting the USB cable. The boot button is the little white button on the left, just below the word "Boot"... ![[Image: crazybee-f4-pro-fc-v2-frsky-top.jpg]](https://oscarliang.com/ctt/uploads/2019/07/crazybee-f4-pro-fc-v2-frsky-top.jpg) • Posts: 863 Threads: 43 Likes Received: 286 in 202 posts Likes Given: 12 Joined: Nov 2018 Reputation: 5 I was able to get it into DFU mode. I saw a video that said connect to OMNIBUSF4, but that exact one doesn't show up. Which one do I choose?
Deal Here's the Deal
10" 6S FR10-G Long Range, 5" 6S Rooster, 5" 6S Badger, 5" 6S QAV-S, 5" 4S Badger, 5" 4S Phreakstyle Slam, 5" 6S Yema, 5" 4S Stark, 3" 4S Gecko, and a 3S 2.5" Tadpole, all of which are Crossfire. Tinyhawk, Tinyhawk S, and a DJI Spark. And projects on the bench....
• Posts: 21,414 Threads: 595 Likes Received: 9,037 in 6,688 posts Likes Given: 1,428 Joined: Jun 2018 Reputation: 796 21-Oct-2019, 12:39 AM (This post was last modified: 21-Oct-2019, 12:42 AM by SnowLeopardFPV.) If you can get into DFU mode then flash Betaflight 4.0.6 to the flight controller using the CRAZYBEEF4FR target. This is assuming you have the version of the Mobula7 HD with the built-in FrSky receiver because I know you got your brother a Taranis. Then run the following in the CLI to restore the original factory settings... Code: # name
name Mobula7 HD
# resources
resource PWM 1 D07
resource PWM 3 D11
resource PWM 5 D10
resource PWM 6 A11
resource PWM 7 F08
# timer
# dma
# mixer
# servo
# servo mix
# feature
feature -TELEMETRY
feature -AIRMODE
feature MOTOR_STOP
feature LED_STRIP
feature ANTI_GRAVITY
feature DYNAMIC_FILTER
# beeper
# beacon
# map
map TAER1234
# serial
serial 0 2048 115200 57600 0 115200
# led
led 0 4,7::CO:2
led 1 5,7::CO:2
led 2 6,7::CO:2
led 3 7,7::CO:2
led 4 8,7::CO:2
# color
# mode_color
# aux
aux 0 0 0 1300 2100 0 0
aux 1 1 1 1200 1550 0 0
aux 2 28 1 1550 2100 0 0
aux 3 35 2 1550 2100 0 0
# adjrange
# rxrange
# vtx
# rxfail
# display_name
# master
set rx_spi_protocol = FRSKY_D
set motor_pwm_protocol = DSHOT600
set vbat_min_cell_voltage = 310
set vbat_warning_cell_voltage = 320
set ibata_scale = 1175
set small_angle = 180
set pid_process_denom = 1
set osd_warn_esc_fail = OFF
set osd_vbat_pos = 2091
set osd_rssi_pos = 2081
set osd_tim_1_pos = 54
set osd_tim_2_pos = 2102
set osd_flymode_pos = 2456
set osd_g_force_pos = 65
set osd_throttle_pos = 2423
set osd_crosshairs_pos = 2253
set osd_current_pos = 2400
set osd_mah_drawn_pos = 2433
set osd_craft_name_pos = 2442
set osd_warnings_pos = 329
set osd_disarmed_pos = 2346
set vtx_channel = 8
set vtx_power = 3
set vtx_freq = 5880
set frsky_spi_tx_id = 244,206
set frsky_spi_offset = -37
set frsky_spi_bind_hop_data = 0,180,125,70,15,195,140,85,30,210,155,100,45,225,170,115,60,5,185,130,75,20,200,145,91,35,215,160,105,50,230,175,120,65,10,190,135,80,25,205,150,95,40,221,165,110,55,0,0,0
set frsky_x_rx_num = 12
# profile
profile 0
set p_pitch = 50
set i_pitch = 50
set d_pitch = 30
set f_pitch = 60
set p_roll = 50
set i_roll = 45
set d_roll = 27
set f_roll = 60
set p_yaw = 72
set i_yaw = 55
set f_yaw = 100
# rateprofile
rateprofile 0
set roll_expo = 23
set pitch_expo = 23
set roll_srate = 75
set pitch_srate = 75
# save configuration
save
• Posts: 863 Threads: 43 Likes Received: 286 in 202 posts Likes Given: 12 Joined: Nov 2018 Reputation: 5 Yes, it is the model with the FrSky receiver. He bought himself the 2019 X9D plus. Now it's up to me to get everything to work.
I'll have to give it a try tomorrow after work.
Deal Here's the Deal
10" 6S FR10-G Long Range, 5" 6S Rooster, 5" 6S Badger, 5" 6S QAV-S, 5" 4S Badger, 5" 4S Phreakstyle Slam, 5" 6S Yema, 5" 4S Stark, 3" 4S Gecko, and a 3S 2.5" Tadpole, all of which are Crossfire. Tinyhawk, Tinyhawk S, and a DJI Spark. And projects on the bench....
• Posts: 863 Threads: 43 Likes Received: 286 in 202 posts Likes Given: 12 Joined: Nov 2018 Reputation: 5 Sorry it took me so long. With the cold weather coming we've been super busy at work getting all of our above ground work done so we can hide underground all winter, hehe.
I tried what you suggested. There are two CRAZYBEEF4FR targets, (LEGACY and HAMO). Only the LEGACY allows 4.0.6 to be selected. I click on "Load Firmware" online, and it says it's loaded. I click "Flash Firmware" and nothing happens.
So, that's where I'm at....
Deal Here's the Deal
10" 6S FR10-G Long Range, 5" 6S Rooster, 5" 6S Badger, 5" 6S QAV-S, 5" 4S Badger, 5" 4S Phreakstyle Slam, 5" 6S Yema, 5" 4S Stark, 3" 4S Gecko, and a 3S 2.5" Tadpole, all of which are Crossfire. Tinyhawk, Tinyhawk S, and a DJI Spark. And projects on the bench....
• Posts: 21,414 Threads: 595 Likes Received: 9,037 in 6,688 posts Likes Given: 1,428 Joined: Jun 2018 Reputation: 796 (26-Oct-2019, 02:16 PM)Deal-E-O Wrote: I tried what you suggested. There are two CRAZYBEEF4FR targets, (LEGACY and HAMO). Only the LEGACY allows 4.0.6 to be selected. I click on "Load Firmware" online, and it says it's loaded. I click "Flash Firmware" and nothing happens. The unified targets (with a 4 letter manufacturer identifier at the end) were only introduced for Betaflight 4.1, so you will need to use legacy for any older versions. Are you manually putting the FC into boot mode with the button on the board as mentioned in post #8 of this thread? Because of the issue you have, you will need to manually put the FC it into boot mode before you can flash new firmware to it. Then check that "DFU" is showing in the dropdown box at the top of Betaflight Configurator before you try and flash the firmware to it. • Posts: 863 Threads: 43 Likes Received: 286 in 202 posts Likes Given: 12 Joined: Nov 2018 Reputation: 5 Legacy doesn't work either.
Yes, manually putting FC into boot mode. DFU does show, and still same result as above.
Deal Here's the Deal
10" 6S FR10-G Long Range, 5" 6S Rooster, 5" 6S Badger, 5" 6S QAV-S, 5" 4S Badger, 5" 4S Phreakstyle Slam, 5" 6S Yema, 5" 4S Stark, 3" 4S Gecko, and a 3S 2.5" Tadpole, all of which are Crossfire. Tinyhawk, Tinyhawk S, and a DJI Spark. And projects on the bench....
• Posts: 12,098 Threads: 125 Likes Received: 3,739 in 2,836 posts Likes Given: 99 Joined: Feb 2017 Reputation: 388 • |
