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

Change RC Rate and RC Command #164

Merged
merged 1 commit into from
May 12, 2018

Conversation

McGiverGim
Copy link
Member

Change the meaning of this graphs to more useful values. The RC Command
now shows the input of the sticks in us, and the RC Rate the deg/s of
this input.
image

Fixes #138

@ctzsnooze can you test it to see if I now it is correct?

Some things to discuss:

  • Now, the RC Command values are in us, from 1000 to 2000. I don't know if maybe is easier to the users to let this value in %.
  • The RC Rate values are in deg/s and can be compared, in the same scale, with the gyro or the pid error. I've used the maximum rate configured for some of the axis + 20% as maximum value. The correct value is the maximum gyro rate (using the gyro_scale to calculate it is about 2000 deg/s), but with this value the graphs are too small by default.

After that, my idea is to make another PR renaming some of the other graph fields to more "readable" values.

power: 0.8,
inputRange: 500 * (sysConfig.rcRate ? sysConfig.rcRate : 100) / 100,
power: 0.25,
inputRange: 500*1.20, // +20% to let compare in the same scale with the rccommands
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Spaces around operator missing.

Change the meaning of this graphs to more useful values. The RC Command
now shows the input of the sticks in us, and the RC Rate the deg/s of
this input.
@McGiverGim
Copy link
Member Author

Fixed.

@mikeller mikeller merged commit 1c1cbeb into betaflight:master May 12, 2018
@McGiverGim McGiverGim deleted the change_rcrate_rccommand branch July 18, 2018 10:48
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

Successfully merging this pull request may close these issues.

2 participants