I have an older BetaFPV 95 with version 1.0 flight controller and I mistakenly decided to upgrade the firmware in Betaflight 4.4 and now motor 2 wont work. I saved CLI dump off of it before I updated flight controller but apparently the firmware "BetaFPV411rx" is for a different version of the flight controller and resources are wrong in the CLI. "A00" is the address motor 2 is set for in the CLI presently. Not sure what to do now, I have tried to find correct firmware for board with no luck. Appreciate any help I can get with this. thanks

Assuming your Beta95X (V1) has the BetaFPV F405 AIO V3.0 FC in it you need to flash the BETAFPVF405 Betaflight target to it. When you get prompted to apply custom default settings it will then apply the correct Betaflight configuration for that target including correct motor mappings. Motor 2 in the BETAFPVF405 target gets mapped to "B01" (see HERE).

If you post the cli dump you saved prior to the update, we can take a look at it real quick and figure out what betaflight version was originally on it, as well as what target it used- that way you can flash it back to how it was originally.

Or if you want to figure that out for yourself, it’ll be somewhere in the first few lines of the dump.
It should say something like:
#version
#betaflight/(targetnamehere) x.x.x <—betaflight version here

Edit- Snow beat me to it, and gave you the target name.

(22-Apr-2023, 11:46 PM)SnowLeopardFPV Wrote: Assuming your Beta95X (V1) has the BetaFPV F405 AIO V3.0 FC in it you need to flash the BETAFPVF405 Betaflight target to it. When you get prompted to apply custom default settings it will then apply the correct Betaflight configuration for that target including correct motor mappings. Motor 2 in the BETAFPVF405 target gets mapped to "B01" (see HERE).

I am pretty sure it’s a betafpv411rx board but I could be wrong. That is what was in my CLI dump anyways. Attaching some pictures of the board.

Is yours an "X" version of the Beta95 or just a normal (non-X) version?

There were no pictures attached to your last post.

How to upload pictures -> https://intofpv.com/t-how-to-upload-pictures

If you are using the simplified view of the forum via a phone or a tablet you might need to temporarily switch to the desktop view to upload your images. You can do that by scrolling right to the bottom of the page and clicking on the "Switch to Full Version" link. Once you are done you can then switch back to the mobile view again by scrolling right to the bottom of the page again and clicking on the "Mobile Version" link.

Must be doing something wrong as my pictures aren’t posting. Even at only 53kb per picture.

     Thanks, Guess I was doing it wrong the first time.  I cant find my CLI now either. Still looking. If I find it I will paste it.

(23-Apr-2023, 01:07 AM)SnowLeopardFPV Wrote: Is yours an "X" version of the Beta95 or just a normal (non-X) version?

There were no pictures attached to your last post.

How to upload pictures -> https://intofpv.com/t-how-to-upload-pictures

If you are using the simplified view of the forum via a phone or a tablet you might need to temporarily switch to the desktop view to upload your images. You can do that by scrolling right to the bottom of the page and clicking on the "Switch to Full Version" link. Once you are done you can then switch back to the mobile view again by scrolling right to the bottom of the page again and clicking on the "Mobile Version" link.

Thanks for the help, pictures posted. I think its just a 95 but purchased it 3-4 years ago so Im not really sure.

OK, so it's the old non-pusher Beta95X and you're right in that it is using an F411 MCU on the FC. I guess the very early ones used an F411 FC which was then changed to an F405 FC even on the V1 Beta95X.

If you're saying that the BETAFPVF411RX firmware target is providing the wrong motor mapping, then until you can locate the original CLI dump taken prior to you flashing new firmware to the quad then there isn't much we can do other than play guessing games. I tried to find a CLI dump of the same quad posted by someone else, but I've not yet been able to find one. The one posted on the BetaFPV support page for the V1 Beta95X is for the F405 FC. They don't seem to have uploaded any dump files for the F411 FC version.

The specifications for the board on the product page for the BetaFPV F4 1-2S AIO V1.0 (HERE) does actually state that it uses the BETAFPVF411RX target so I have no idea. So we really need to see your original pre-upgrade CLI dump to try and figure things out.

(23-Apr-2023, 11:03 AM)SnowLeopardFPV Wrote: OK, so it's the old non-pusher Beta95X and you're right in that it is using an F411 MCU on the FC. I guess the very early ones used an F411 FC which was then changed to an F405 FC even on the V1 Beta95X.

If you're saying that the BETAFPVF411RX firmware target is providing the wrong motor mapping, then until you can locate the original CLI dump taken prior to you flashing new firmware to the quad then there isn't much we can do other than play guessing games. I tried to find a CLI dump of the same quad posted by someone else, but I've not yet been able to find one. The one posted on the BetaFPV support page for the V1 Beta95X is for the F405 FC. They don't seem to have uploaded any dump files for the F411 FC version.

The specifications for the board on the product page for the BetaFPV F4 1-2S AIO V1.0 (HERE) does actually state that it uses the BETAFPVF411RX target so I have no idea. So we really need to see your original pre-upgrade CLI dump to try and figure things out.

Thank you for the information to verify the correct model as it is a non pusher config. I looked and found what I thought was the full CLI dump but apparently I either didn't do dump "all" and just got a partial CLI or used the preset in Betaflight to save the config.
 
Here is the partial config I found.

defaults nosave


# version
# Betaflight / STM32F411 (S411) 4.2.0 Jun 14 2020 / 03:04:43 (8f2d21460) MSP API: 1.43
# config: manufacturer_id: MTKS, board_name: MATEKF411RX, version: ee671311, date: 2019-10-16T11:49:37Z

# start the command batch
batch start

# reset configuration to default settings
defaults nosave

board_name MATEKF411RX
manufacturer_id MTKS
mcu_id 005d00163439511236383737
signature 

# feature
feature -AIRMODE

# beeper
beeper -GYRO_CALIBRATED
beeper -RX_LOST_LANDING
beeper -DISARMING
beeper -ARMING
beeper -ARMING_GPS_FIX
beeper -BAT_CRIT_LOW
beeper -BAT_LOW
beeper -GPS_STATUS
beeper -RX_SET
beeper -ACC_CALIBRATION
beeper -ACC_CALIBRATION_FAIL
beeper -READY_BEEP
beeper -DISARM_REPEAT
beeper -ARMED
beeper -SYSTEM_INIT
beeper -ON_USB
beeper -BLACKBOX_ERASE
beeper -CRASH_FLIP
beeper -CAM_CONNECTION_OPEN
beeper -CAM_CONNECTION_CLOSE
beeper -RC_SMOOTHING_INIT_FAIL

# beacon
beacon RX_LOST

# serial
serial 1 2048 115200 57600 0 115200

# aux
aux 0 0 0 1725 2100 0 0
aux 1 1 1 1300 1700 0 0
aux 2 2 1 1725 2100 0 0
aux 3 28 2 1700 2100 0 0
aux 4 35 3 1700 2100 0 0

# adjrange
adjrange 0 0 1 900 2100 12 1 0 0

# rxrange
rxrange 0 987 2011
rxrange 1 987 2011
rxrange 2 987 2011
rxrange 3 987 2011

# vtxtable
vtxtable bands 6
vtxtable channels 8
vtxtable band 1 BOSCAM_A A FACTORY 5865 5845 5825 5805 5785 5765 5745 5725
vtxtable band 2 BOSCAM_B B FACTORY 5733 5752 5771 5790 5809 5828 5847 5866
vtxtable band 3 BOSCAM_E E FACTORY 5705 5685 5665    0 5885 5905    0    0
vtxtable band 4 FATSHARK F FACTORY 5740 5760 5780 5800 5820 5840 5860 5880
vtxtable band 5 RACEBAND R FACTORY 5658 5695 5732 5769 5806 5843 5880 5917
vtxtable band 6 IMD6     I CUSTOM  5732 5765 5828 5840 5866 5740    0    0
vtxtable powerlevels 2
vtxtable powervalues 0 1
vtxtable powerlabels 25 200

# master
set gyro_lowpass2_hz = 275
set yaw_spin_recovery = ON
set dyn_notch_width_percent = 0
set dyn_notch_q = 200
set dyn_notch_min_hz = 90
set dyn_lpf_gyro_min_hz = 220
set dyn_lpf_gyro_max_hz = 550
set acc_calibration = -127,-55,-354,1
set mag_hardware = NONE
set baro_hardware = NONE
set rc_smoothing_derivative_type = BIQUAD
set dshot_idle_value = 350
set dshot_bidir = ON
set motor_pwm_protocol = DSHOT300
set motor_poles = 12
set yaw_motors_reversed = ON
set small_angle = 180
set gps_sbas_mode = AUTO
set osd_units = IMPERIAL
set osd_warn_batt_not_full = OFF
set osd_warn_batt_warning = OFF
set osd_warn_visual_beeper = OFF
set osd_warn_core_temp = OFF
set osd_warn_rc_smoothing = OFF
set osd_warn_launch_control = OFF
set osd_warn_no_gps_rescue = OFF
set osd_warn_gps_rescue_disabled = OFF
set osd_warn_rssi = ON
set osd_rssi_alarm = 35
set osd_rssi_pos = 2402
set osd_vtx_channel_pos = 2418
set osd_avg_cell_voltage_pos = 2410
set osd_disarmed_pos = 2346
set osd_stat_max_spd = OFF
set osd_stat_endbatt = ON
set osd_stat_battery = ON
set osd_stat_bbox = OFF
set osd_stat_bb_no = OFF
set cpu_overclock = OFF
set vtx_band = 4
set vtx_channel = 4
set vtx_power = 1
set vtx_freq = 5800
set vcd_video_system = NTSC
set frsky_spi_tx_id = 84,156
set frsky_spi_offset = -46
set frsky_spi_bind_hop_data = 5,131,22,148,39,165,56,182,73,199,91,216,107,233,124,15,141,32,158,49,175,66,192,83,209,100,226,117,8,134,25,151,42,168,59,185,76,202,93,219,110,1,127,18,144,35,161,255,255,255
set gyro_1_align_yaw = 1800
set gyro_rpm_notch_harmonics = 1

profile 0

# profile 0
set dyn_lpf_dterm_min_hz = 77
set dyn_lpf_dterm_max_hz = 187
set dterm_lowpass2_hz = 165
set anti_gravity_gain = 5000
set iterm_relax_cutoff = 20
set p_yaw = 30
set d_min_roll = 20
set d_min_pitch = 22
set d_min_boost_gain = 27

profile 1

# profile 1
set anti_gravity_gain = 5000
set iterm_relax_cutoff = 20
set p_yaw = 30
set d_min_roll = 20
set d_min_pitch = 22
set d_min_boost_gain = 27

profile 2

# profile 2
set anti_gravity_gain = 5000
set iterm_relax_cutoff = 20
set p_yaw = 30
set d_min_roll = 20
set d_min_pitch = 22
set d_min_boost_gain = 27

# restore original profile selection
profile 2

rateprofile 0

# rateprofile 0
set roll_rc_rate = 45
set pitch_rc_rate = 45
set yaw_rc_rate = 45
set roll_srate = 82
set pitch_srate = 82
set yaw_srate = 82
set tpa_breakpoint = 1250

rateprofile 1

# rateprofile 1
set roll_rc_rate = 54
set pitch_rc_rate = 54
set yaw_rc_rate = 54
set roll_srate = 82
set pitch_srate = 82
set yaw_srate = 82
set tpa_breakpoint = 1250

rateprofile 2

# rateprofile 2
set roll_rc_rate = 63
set pitch_rc_rate = 63
set yaw_rc_rate = 63
set roll_srate = 82
set pitch_srate = 82
set yaw_srate = 82
set tpa_breakpoint = 1250

rateprofile 3

# rateprofile 3
set tpa_breakpoint = 1250

rateprofile 4

# rateprofile 4
set tpa_breakpoint = 1250

rateprofile 5

# rateprofile 5
set tpa_breakpoint = 1250

# restore original rateprofile selection
rateprofile 0

# save configuration

[attachment=10587 Wrote:SnowLeopardFPV pid='195215' dateline='1682244219']OK, so it's the old non-pusher Beta95X and you're right in that it is using an F411 MCU on the FC. I guess the very early ones used an F411 FC which was then changed to an F405 FC even on the V1 Beta95X.

If you're saying that the BETAFPVF411RX firmware target is providing the wrong motor mapping, then until you can locate the original CLI dump taken prior to you flashing new firmware to the quad then there isn't much we can do other than play guessing games. I tried to find a CLI dump of the same quad posted by someone else, but I've not yet been able to find one. The one posted on the BetaFPV support page for the V1 Beta95X is for the F405 FC. They don't seem to have uploaded any dump files for the F411 FC version.

The specifications for the board on the product page for the BetaFPV F4 1-2S AIO V1.0 (HERE) does actually state that it uses the BETAFPVF411RX target so I have no idea. So we really need to see your original pre-upgrade CLI dump to try and figure things out.

This CLI dump is the current one. Betaflight autodetected firmware and installed default settings after upgrade. Then I think I used Presets to load old config on top of new firmware. I had updated a few quads and hard to remember what I did exactly. Now I have learned to save CLI dump all.

I finally got it working by rolling it back to a Betaflight 4.2 Betafpv411rx  firmware. But now the flight controller will not work with a freshly charged 2s battery but will work with half charged battery or plugged into usb connected to Betaflight. So I am guessing that something in the CLI is set for a 1S battery since some of the Beta fpv's were 1s. I just don't know what to look for in CLI to change this?

I wonder if your 5v regulator is bad.

(24-Apr-2023, 12:25 AM)voodoo614 Wrote: I wonder if your 5v regulator is bad.

I guess that is possible, just strange It worked fine before I decided to update the firmware. If I plug in a fully charged battery I will get the first 3 beeps from motors and only red Led will light dim. If I plug in usb wire to flight controller all 3 color leds light up and I get all 5 beeps from motors. Also with the newer firmware I had installed with 1 motor not working I dont have this issue with full battery.

I think voodoo is right, and your 5v regulator is dead.