Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
generate_params.py: add PWM_AUX_* for boards w/o IO and >8 channels
- Loading branch information
Showing
1 changed file
with
16 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
7faaad7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pwm outs above 8 now work perfectly on the corresponding boards with all parameters expect pwm_aux_out is always set to "1234" and does not allow for any change
7faaad7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@taileron which airframe do you use? Some of them override the setting, and it's also set for fixed-wing or multirotor in general (
ROMFS/px4fmu_common/init.d/rc.fw_defaults
).7faaad7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bkueng used octo x, (+extra loaded mount.aux.mix) takes rc.mc_defaults which uses that default as well. I thought, however, that these defaults only apply during set-up and could be changed later.
The same PWM frequency is always output as at the main, even if something else was specified in the aux_rate parameter. Of course, this could be due to the fact that some identical io timers are used for both.
7faaad7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes that was surely the intention but the logic around that is a bit convoluted. All of this will become simpler with dynamic control allocation (SYS_CTRL_ALLOC param, mavlink/qgroundcontrol#9952). You're welcome to test it.