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

Servo Output does not activate until pressed #3

Open
MadRC opened this issue Apr 20, 2020 · 0 comments
Open

Servo Output does not activate until pressed #3

MadRC opened this issue Apr 20, 2020 · 0 comments

Comments

@MadRC
Copy link

MadRC commented Apr 20, 2020

Expected Behavior

Programmed Servo outputs should sit on user set minimum state.

Current Behavior

Servo outputs in Ardupilot do not activate to minimum user set levels until the button on herelink is pressed at least once to trigger detection of the button.

Steps to Reproduce:

Please provide an unambiguous set of steps to reproduce the current behavior

  1. Map A Button in Solex to Ch7 and set Short press PWM to 1200
    2.Map A Button in solex to Ch7 and set Long Press PWM to 1800
  2. Open Mission planner and see servo 7 state, it is not activated on Autopilot boot or radio boot up.

System Information

Happening in Solex, cant test in CGC as no options to map.

Detailed Description

The servo outputs in Ardupilot appear not to activate at all with mavlink input until input action is received at least once. This means if you have a button setting of 1200pwm on single press and 1800PWM to long setting untill you trigger one of these inputs the servo output remains inactive on screen in mission planner and even below the minimum output set in the setting.

It appears untill the button is used at least once the servo output is not active.

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

No branches or pull requests

1 participant