Nexus AutoQueue completely automates queuing status updates based on events from FMS.
Access
FTAs must set up AutoQueue because it requires access to FMS or the field network.
How it works
For the first matches in a block, queuing will happen based on the queue time set in Nexus (±1 minute). Once the score is committed for a match, Nexus will automatically progress the queuing status and notify teams.
AutoQueue receives the following events from FMS:
- Match started
- Match score committed
- Break started
- Break ended
When enabled, lead queuers do not manually set match statuses. Instead, ensure the schedule in Nexus is always kept up to date to ensure AutoQueue queues the correct matches. If any of these items are incorrect in Nexus, then matches will not be queued properly:
- Queue times
- Breaks
- Replays
- Match order
When AutoQueue is enabled, do not try to fight the automation- you’ll lose and create a worse experience for teams. If AutoQueue isn’t doing what you want, update the Nexus configuration to correct the information AutoQueue needs to queue properly.
Set up
The set up process depends on which FMS is being used.
FRC (official)
Set up the TBA Companion app on the FTA toughbook and follow the instructions to enable AutoQueue. “TBA Trusted API Keys” are not required if just using the companion for AutoQueue.
FRC (Cheesy Arena)
From the automation tab on the Cheesy Arena settings page, check the Enable Nexus AutoQueue box and click Generate next to the Nexus AutoQueue key input field. Log in with a device account and grant it the Lead queuer role. The key will automatically be generated and saved in Cheesy Arena. The key will continue to work even if the device account loses access, up until a different AutoQueue key is generated.
FTC
AutoQueue for FTC is still in alpha testing. Contact support@ftc.nexus if you’d like to test it at your event.