Skip to content

Conversation

Jetblackdragon
Copy link
Contributor

No description provided.

}

// if the solo controller is connected, use it for driving
boolean soloCC = soloController.isConnected();
Copy link
Member

Choose a reason for hiding this comment

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

I think this will result in soloCC only being set when the robot code starts running, so changing to or from soloCC will require a restart of the robot code. Consider instead making this a boolean class member variable and then updating it ever second or so based on whether the solo controller is connected (via adding a new update method in this class that Robot.robotPeriodic() calls, and have the update method do the soloCC update every second or so).

Copy link
Contributor

@RobototesProgrammers RobototesProgrammers Oct 6, 2025

Choose a reason for hiding this comment

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

it worked fine at drive practice we can check again at the meeting on monday
-Aarya (I forgot what account im on)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

do you think it actually matter is we just call soloController.isConnected() instead of soloCC for the drive request (changing it back to what is was before)?

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.

4 participants