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

Add resolver interface support #136

Open
npetersen2 opened this issue Aug 10, 2020 · 0 comments
Open

Add resolver interface support #136

npetersen2 opened this issue Aug 10, 2020 · 0 comments
Labels
question Questioning something that could be an issue.

Comments

@npetersen2
Copy link
Collaborator

If someone wants to use the AMDC to spin a motor that uses a resolver for position feedback, the AMDC has no built-in support for them.... They would have to generate the excitation signal, then feed the cos and sin signals in to the analog inputs of the AMDC and do the vector tracking themselves. This is non-trivial!

I propose we add native support for this. There are ICs we can put on the board which do all the hard work for us and spit out theta and omega values (e.g., this IC).

On the REV D hardware, the encoder interface connectors are DB9 and almost all pins are used for the ABZ interface. We should change this to a HD15 connector (like all the power stack / GPIO interfaces). Then, we can put half the signals for resolver and half for encoder. The user can pick which one they want to use by wiring up the connector the right way. We'd have to build a driver for the resolver IC in the FPGA, but this is very doable.

@npetersen2 npetersen2 added the question Questioning something that could be an issue. label Aug 10, 2020
@npetersen2 npetersen2 added this to the REV E milestone Aug 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Questioning something that could be an issue.
Projects
None yet
Development

No branches or pull requests

1 participant