Skip to content

Joystick doesn`t work with SCHED_LOOP_RATE set to 300 in a quadplane #29707

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

Closed
raul-ortega opened this issue Apr 6, 2025 · 3 comments
Closed

Comments

@raul-ortega
Copy link

Bug report

Issue details

I recently discovered that with the SCHED_LOOP_RATE parameter set to 300 Hz, I am unable to control my Dolphin VTOL with a joystick connected via Mission Planner. The ailerons barely move, and at most make a kind of jittering noise. However, if I set the SCHED_LOOP_RATE to 50 (as in plane), the problem disappears completely and the ailerons move smoothly and fully.

Version

Arduplane v4.4.4

Platform
[ ] All
[ ] AntennaTracker
[ ] Copter
[X ] Plane
[ ] Rover
[ ] Submarine

Airframe type

Quadplane Tilt Tricopter Vectored Yaw

Hardware type

SpeedyBee F405 Wing

Logs

No logs available

@rmackay9
Copy link
Contributor

rmackay9 commented Apr 7, 2025

HI @raul-ortega,

Thanks for the report, this sounds like the autopilot is running out of CPU and is not able to consume all of the mavlink input. If a regular RC is used, it will probably work fine.

This is not really the place to investigate these issues, I wonder if you've posted in the Plane support forums?

Practically speaking, the best chance of getting this investigated is actually to re-test with the current beta of 4.6.0, then post in the forums here and include an onboard log file and then if possible provide a link here back to that forums post (so that I see it and add it to the 4.6.0 issues list)

Sorry for how involved all this is.

@peterbarker
Copy link
Contributor

@raul-ortega dataflash and telemetry logs are more likely to get you a quick answer.

@rmackay9
Copy link
Contributor

No response from the user so I think I'll close this for now. We will see replies and can re-open then

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

3 participants