Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In expert mode servo tab disappearing after first connection following firmware update #4028

Closed
vardayzsolt opened this issue Jun 15, 2024 · 1 comment · Fixed by #4053
Closed
Labels

Comments

@vardayzsolt
Copy link

Describe the bug

In configurator 10.10.0 (also RC) and fw 4.5.0, servo tab disappears in expert mode after the first connection and reappears only for a single session after flashing again the FC. I have Omnibus F4V3SD connected with 2 servos, with servos included at firmware flash. In former releases of configurator and fw 4.3.0 I did not have this issue. I also tried configurator beta 10.10.1, but the same thing - servo tab disappears in expert mode after the first connection.

To Reproduce

Flashing firmware selecting "Servos" as Other Option to be able to configure servos later. Connect flight controller. Switch expert mode On. Observe Servo tab. Disconnect. Connect again and observe that there is no Servo tab any more.

Expected behavior

Servo tab should remain visible anytime Expert mode is switched On.

Configurator version

10.10.1-debug-b542569

Flight controller configuration

# version
# Betaflight / STM32F405 (S405) 4.5.0 Jun  7 2024 / 15:44:16 (c155f5830) MSP API: 1.46
# config rev: 13e4f8a

# start the command batch
batch start

board_name OMNIBUSF4SD
manufacturer_id AIRB

# name: Scorpion

# resources
resource MOTOR 2 A02
resource MOTOR 3 NONE
resource MOTOR 4 NONE
resource MOTOR 5 NONE
resource MOTOR 6 NONE
resource SERVO 1 A08
resource SERVO 2 A01

# feature
feature -AIRMODE
feature RSSI_ADC

# serial
serial 5 64 115200 57600 0 115200

# mixer
mixer BI

# servo
servo 4 1000 2000 1500 30 -1
servo 5 1000 2000 1335 30 -1

# beeper
beeper -RX_LOST_LANDING
beeper -ARMING_GPS_FIX
beeper -GPS_STATUS
beeper -READY_BEEP
beeper -DISARM_REPEAT
beeper -ARMED
beeper -CAM_CONNECTION_OPEN
beeper -CAM_CONNECTION_CLOSE

# aux
aux 0 0 0 1300 1700 0 0
aux 1 1 1 1300 1700 0 0
aux 2 2 1 1700 2100 0 0
aux 3 13 2 1300 1700 0 0
aux 4 28 3 1300 1700 0 0

# adjrange
adjrange 0 0 2 1300 1700 12 2 0 0

# master
set gyro_lpf1_static_hz = 0
set dyn_notch_count = 1
set dyn_notch_q = 500
set acc_calibration = -35,9,-443,1
set dshot_bidir = ON
set motor_pwm_protocol = DSHOT300
set motor_output_reordering = 1,0,2,3,4,5,6,7
set align_board_yaw = 270
set beeper_dshot_beacon_tone = 2
set small_angle = 90
set pid_process_denom = 2
set debug_mode = GYRO_SCALED
set craft_name = Scorpion

profile 1

# profile 1
set profile_name = video
set anti_gravity_gain = 0
set iterm_relax = OFF
set p_pitch = 85
set i_pitch = 40
set d_pitch = 35
set f_pitch = 0
set p_roll = 40
set i_roll = 40
set d_roll = 30
set f_roll = 0
set p_yaw = 0
set i_yaw = 0
set f_yaw = 0
set d_min_pitch = 35
set simplified_pids_mode = OFF

rateprofile 1

# end the command batch
batch end

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

No response

@haslinghuis
Copy link
Member

You are not using CHANNEL_FORWARDING ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants