-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
Missing PWM_MAIN_REV* params in v1.8.0 #9859
Comments
Which flight controller are you using? |
Ok, but I'm not using the Pixhawk 4. Did you test it with the Pixracer? |
@hamishwillee Can we document this in the user guide? We should change the comment string so it discusses the autopilot component MAIN / AUX are each connected to. The naming is unfortunate:
Pixracer has only FMU, so it has only AUX. I need to figure out why the *_DIS parameters show up at all - there should be none there. |
Fix in code is here: @hamishwillee Please close the issue once documentation is updated. |
@LorenzMeier IF you are asking for the parameter doc changes you made in the code in #9917 to go into the user guide, this should happen automatically in the next 12 hours or so (they get generated into https://docs.px4.io/en/advanced_config/parameter_reference.html#pwm-outputs ) If not, you're going to have to clarify more what the problem is and where you are seeing it. At the moment I don't understand whether you think MAIN/AUX are a problem, or IO/FMU, and in what string you think this needs to be changed. |
I'm not longer able to see the PWM_MAIN_REV* params in the latest v1.8.0 release; neither in QGC v3.3.2 or in the nsh console. The ailerons of my Wing Wing Z-841 are moving in the opposite of the correct stabilization direction. If these params have been removed in v1.8.0, then which param should I now use to revert the roll correction in stabilized mode? Notice that everything works properly in Manual mode so I don't need to change or reset the RC inputs. The issue is within the latest firmware release.
The text was updated successfully, but these errors were encountered: