I’m wondering how the vex Smart Field Control works; Can we use buttons before the auton starts in order to change auton pathway and strategy or it bans input until the driver control starts? Seems like this season’s auton is probably at least four kinds(2 colors difference due to toggle strategy * 2 paths difference due to starting position).
I’m new to vex programming therefore I want to know how to compile all these different strategies into one program. Is there any document I could follow or explanation on that? Thanks!
Yes, you can use the pre-auton period to select the color, starting position, and auton path. Store those choices in variables, then use conditions to run the matching routine. The VEX Competition Template is a good starting point for organizing multiple auton strategies in one program.
Once you plug your controller into the field, it blocks all input from the controller. Most teams will typically create a auto selector on the brain screen, which still works while plugged in. Everyones is different, but most typically consist of creating buttons on the brain screen. Ive also seen some that use a limit switch or bumper to cycle between autos, or a rotation sensor that decides based on its angle
The VEX field control stops the controller buttons from sending inputs to the brain when in disabled mode. However, there are other methods of changing different autonomous routes. You could select the auton using controller buttons before plugging the controller into the field controller; put a different auton on each of the 8 slots; create a GUI to press since the touch screen still works in disabled mode; use a potentiometer to choose autons by spinning it; or create a program that that stores the desired auton number in a SD card.
If u connect to field control, u can’t use controller to send signals to brain. So u can only change auton routes by touching screen. Or u can select the routes before connecting to the field control. Hope this may help u
I think most of the advice in this thread is really good but I would caution against:
“You could select the auton using controller buttons before plugging the controller into the field controller”
I’m not 100% sure how the program is called while plugged into field control… but sometimes your program might restart or reloop while plugged in… meaning your auton variable could be reset and you will have to power cycle your robot to reselect it using controller buttons (cause unplugged from field control disables the radio connection. I have just had too many auton horror stories to suggest this method.
