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

Tiny addendum stating that one should treat the Vex 393's as a CR Servo #65

Closed
NoahBres opened this issue Oct 22, 2020 · 2 comments · Fixed by #66
Closed

Tiny addendum stating that one should treat the Vex 393's as a CR Servo #65

NoahBres opened this issue Oct 22, 2020 · 2 comments · Fixed by #66

Comments

@NoahBres
Copy link
Contributor

NoahBres commented Oct 22, 2020

What information should be added?
Add a quick note that you treat vex 393 motors like cr servos and that you need to connect to an SPM. Digression but also maybe mention spm under the servo section?

Does it need it's own page? (Yes/No): No

If it needs a page, which section should it be in? If it doesn't, which page should it be under?
"Examples of using common hardware components" -> CR Servo section

@abidingabi
Copy link
Member

@NoahBres
Copy link
Contributor Author

Tiny addendum:

"The 393 motor acts as a more powerful and faster continuous rotation servo and is treated as a continuous rotation servo from the SDK when programming"

@NoahBres NoahBres changed the title Add info for Vex 393 motor under the CR Servo section Tiny addendum stating that one should treat the Vex 393's as a CR Servo Oct 22, 2020
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 a pull request may close this issue.

2 participants