Adding in Feedback Servos Section - #17
Conversation
|
Just merge the Feedback servos, I'm working on CR |
|
Not possible. |
BeepBot99
left a comment
There was a problem hiding this comment.
You used triple backticks (e.g., ```CRServoEx```) everywhere for inline code. Inline code uses single backticks (e.g., `CRServoEx`). Triple backticks are for code blocks. You can clone the repo locally and run npm install and npm run dev to preview the website on localhost to see if it's correct.
| == | ||
| ::: | ||
|
|
||
| Note that this is a little different than the ```FeedbackCRServoEx```. There are not currently any overloaded constructors as opposed to the other class. This will probably be updated soon. But in the meantime, you have to do it this way. |
There was a problem hiding this comment.
Let's just fix this now. Are you able to do this, or should I?
There was a problem hiding this comment.
I'll fix it later today or tomorrow. But I need to get my local NEXT working
|
OK i fixed the things |
| @@ -0,0 +1,81 @@ | |||
| # Continuous Rotation Servos | |||
|
|
|||
| Continuous rotation servos are servos that instead of moving to a position use power to move. They are more comparable to motors in that sense than a traditional servo. | |||
There was a problem hiding this comment.
This is unnecessary (and not descriptive enough IMO). nextftc.dev is not FTC Docs or gm0.
|
|
||
| ## Example Tracking | ||
|
|
||
| :::tabs key:code |
There was a problem hiding this comment.
Please add the corresponding Kotlin example.
|
|
||
| ## Features | ||
|
|
||
| Both `FeedbackCRServoEx` and `FeedbackServoEx` share the same method internally of `getCurrentPosition()` or `currentPosition` in Kotlin. This returns the current position of the servo in radians from 0 to 2 pi. |
There was a problem hiding this comment.
This is worded incorrectly; it would be better to say "both share a currentPosition property."
|
Fixed pt 2 |
I added some basic documentation for Feedback servos since some people have no clue they even exist.