-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Adaptive Hover not working with PWM Actuators #156
Comments
I think the |
Fixed in dev branch 2509dc1 |
Please test and also check if the rc throttle limit is working as expected or if |
@ljb2208 |
Hi Felix, no not as yet. Hopefully I will this weekend. Will let you know On Wed, Mar 21, 2012 at 7:04 PM, Felix Ruess <
|
Still not working as per issue #166. Also guidance_v_delta_t is being set to the negative of the feedforward and feedback commands, however the feedforward command is still calculated as a positive number. Feedback command also looks to be positive as well, although I haven't checked that each of the terms are positive. |
thx, somehow missed that in the merge... |
When using a rotorcraft with PWM actuators, the thrust_applied value passed to the gv_adapt_run function is not correct.
For PWM Actuators the following is defined in the airframe config:
SUPERVISION_MIN_MOTOR 1030
SUPERVISION_MAX_MOTOR 2000
In guidance_v.c is the following code
int32_t cmd_hack = Chop(stabilization_cmd[COMMAND_THRUST], SUPERVISION_MIN_MOTOR, SUPERVISION_MAX_MOTOR); gv_adapt_run(ins_ltp_accel.z, cmd_hack);
This results in cmd_hack not being calculated correctly.
Temporary fix was to add new defines in guidance_v.c and use these to bound the stabilization_cmd[COMMAND_THRUST] to between 3 and 200.
The text was updated successfully, but these errors were encountered: