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

Anticogging improvments #53

Closed
1 of 2 tasks
madcowswe opened this issue Nov 6, 2017 · 4 comments
Closed
1 of 2 tasks

Anticogging improvments #53

madcowswe opened this issue Nov 6, 2017 · 4 comments

Comments

@madcowswe
Copy link
Collaborator

madcowswe commented Nov 6, 2017

  • Use setpoint instead of current position to lookup table, in order to keep the compensation on the feed-forward path only
  • Selected harmonics smoothing
    • Upload calibration map
    • FFT - select harmonics - IFFT in python
    • Download smooothed map
@Wetmelon
Copy link
Collaborator

Wetmelon commented Jan 6, 2018

Thinking about this... would it be best to use a position prediction based on p & v, then take something like (prediction + current pos) / 2 as the lookup value?

@madcowswe
Copy link
Collaborator Author

A more concrete plan for the 2nd part:

  1. modify the firmware to scan into a small circular buffer with a "last written idx"
  2. get python to poll it and read the buffer to capture the data
  3. run and plot my analysis script as usual, make sure that still works
  4. said script generates the smoothed version of the cogmap: resample this into a smaller cogbuffer, size TBD, something like 128 samples maybe 256.
  5. Write this resampled cogmap back to ODrive.
  6. modify the anticogging path that's called in every control cycle to use this smaller map and to simply linearly interpolate the nearest samples
  7. figure out a way to store the cogmap as a config member as to make it stay in persistent memory

@Wetmelon
Copy link
Collaborator

Wetmelon commented Sep 8, 2018

If used in conjuction with trajPlan, anticogging is now placed in the feedforward path.

@madcowswe
Copy link
Collaborator Author

madcowswe commented Aug 31, 2020

We plan to use a continuously rolling "integrator" with LPF broadcast of integrand. This supersedes the plans in this issue.

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

2 participants