Skip to content

Adding in Feedback Servos Section - #17

Merged
BeepBot99 merged 7 commits into
NextFTC:mainfrom
MooseCoding:main
Nov 27, 2025
Merged

Adding in Feedback Servos Section#17
BeepBot99 merged 7 commits into
NextFTC:mainfrom
MooseCoding:main

Conversation

@MooseCoding

Copy link
Copy Markdown
Contributor

I added some basic documentation for Feedback servos since some people have no clue they even exist.

@MooseCoding

Copy link
Copy Markdown
Contributor Author

Just merge the Feedback servos, I'm working on CR

@BeepBot99

Copy link
Copy Markdown
Collaborator

Not possible.

@BeepBot99 BeepBot99 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

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.

Comment thread src/nextftc/hardware/motors-and-servos/cr-servos.md Outdated
Comment thread src/nextftc/hardware/motors-and-servos/cr-servos.md Outdated
Comment thread src/nextftc/hardware/motors-and-servos/cr-servos.md Outdated
Comment thread src/nextftc/hardware/motors-and-servos/cr-servos.md Outdated
Comment thread src/nextftc/hardware/motors-and-servos/cr-servos.md Outdated
Comment thread src/nextftc/hardware/motors-and-servos/feedback-servos.md
Comment thread src/nextftc/hardware/motors-and-servos/feedback-servos.md Outdated
==
:::

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.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Let's just fix this now. Are you able to do this, or should I?

@MooseCoding MooseCoding Nov 5, 2025

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I'll fix it later today or tomorrow. But I need to get my local NEXT working

Comment thread src/nextftc/hardware/motors-and-servos/feedback-servos.md Outdated
@MooseCoding

Copy link
Copy Markdown
Contributor Author

OK i fixed the things

@zachwaffle4
zachwaffle4 self-requested a review November 20, 2025 20:29
@@ -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.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This is unnecessary (and not descriptive enough IMO). nextftc.dev is not FTC Docs or gm0.


## Example Tracking

:::tabs key:code

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

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.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This is worded incorrectly; it would be better to say "both share a currentPosition property."

@MooseCoding

Copy link
Copy Markdown
Contributor Author

Fixed pt 2

@BeepBot99
BeepBot99 merged commit 092b991 into NextFTC:main Nov 27, 2025
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.

3 participants