i am trying to code my robot with an autonomous chooser on the brain before a match starts and i was to have the (wait until the autonomous start)
I’m wondering why wait until is there in the first place. I don’t see any use of it, as far as I can tell, but I may be small braining right now.
i think its a big brain move then you only have to charge the battery,tighten nuts and bolts and select the auton less work for you to do in the comps
but i am trying to find a way to have it wait to start the auton when the autonomous period starts
No I mean after the button press and it goes to run auton, there’s a wait until sitting there, I believe that’s what OP is asking about.
Edit: Oh, you are OP. If you’re trying to make it wait, then i don’t really know. You’d have to dive into the specific code inside Vex, which I don’t even know if you can access, to see if a variable is there that you can check. I think @jpearman can help better with this than I can, since I don’t do blocks.
@adrienschlag Care to weigh in, or do you want to hold back your secrets? 
@Deathtooall13 621A had an auton chooser via controller so that they only had to run a single program, and then choose its starting condition. There were some other quirks that still need to be fixed (stopping threads at the end of auton/start od driver), but it overall worked well.
might have to chek in on that
We’ll see what Adrien wants to do, it’s their code 
I’m fine with sharing my auton selection code! As long as you don’t claim it as your own, feel free to use it! I’m going to make it more template-like before I share it, so once I’m done with turning it into a template I’ll reply to this comment with the code.
3 Likes
thx @adrienschlag this will help out and don’t worry i wont claim it as my own ill make sure ill give you credit in the build journal
Alright, here’s the code!
autonSelectionTemplate.v5blocks (81.0 KB)
Feel free to ask me if you have any questions!
2 Likes
I don’t know if this is what you’re looking for but an alternative solution my team used was just to have an orange jumper clip that depending on what port it was in, would run a specific auton when started.
Vex jumper clip:
The code looked something like this:
if (bumperA = true) {
//run right side
}
if (bumperB = true) {
//run left side
}
I’m not sure if this is exactly what you’re looking for but it is an alternative solution if you can’t figure the autonomous selection menu. We chose to do it this way because we could select the auton before even turning on the program which saved battery power.
can you do a video breakdown of how it works
nevermind on the video i just needed to make a bolean
I might try this, but is it VRC legal? Because I searched it up and it only said cortex on it (in the website) and not V5 or VR.
yea it is i already talked to a admin
2 Likes
It’s legal. You use the 3 wire ports on the top of the v5 brain where you’d plug in pneumatic solenoids or 3 wire sensors. You initialize the port as a bumper switch and then you can switch which port the jumper clip is in to change the auton because the jumper clip always outputs true.
1 Like
here is the code i used
vex spin up full code(unfinished).v5blocks (43.9 KB)
i forgot to remove the motor controls but there you go but is plug and play on the brain
I think @Pyrotechnics is correct in questioning the jumper clips legality.
This would be how you would wire and program it, but per <R6b>, cortex parts are not allowed (unless cross-listed as v5, see <R6a>), and the jumper product page only lists them as “cortex” components, not “V5” (nor do they appear in searches filtered for “V5” or “VRC Legal”).
Due to this, I [personally] have doubts about their legality, and would caution against using them on a competition robot. Use at your own risk, and remember that
Teams are responsible for providing documentation proving a part’s legality in the event of a question.
One possible workaround could be using a bumper or limit switch in an always closed configuration instead of the jumper clip.
thats what i was talking about