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

Driver control doesn't start without competition hub #29

Closed
doinkythederp opened this issue Apr 12, 2024 · 1 comment · Fixed by #42
Closed

Driver control doesn't start without competition hub #29

doinkythederp opened this issue Apr 12, 2024 · 1 comment · Fixed by #42
Labels
core Relates to any lowlevel code in vexide-core or vexide-panic.
Milestone

Comments

@doinkythederp
Copy link
Member

Bug Description

When testing locally without a competition happening, my driver control code never starts.

Code to reproduce

TODO, I'll come back to this later once I make a minimum reproducible sample

Expected vs. actual behavior

Operator control code should run even if the robot is not at a competition. In reality it never starts.

Additional information

  • I don't have access to a competition hub so it's possible that driver control code never runs whatsoever.
@Tropix126
Copy link
Member

From testing previously, driver did run when on competition control, so this is likely due to some unnecessary check for the CONNECTED status flag.

@Gavin-Niederman Gavin-Niederman added this to the v0.1.0 milestone Apr 16, 2024
@Tropix126 Tropix126 added the core Relates to any lowlevel code in vexide-core or vexide-panic. label Apr 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Relates to any lowlevel code in vexide-core or vexide-panic.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants