Question on binding Gizmos to FMS for practice day and then rebinding them to driver's station for final week before checking in for the competition

[shannonsjones]

I was hoping to run the FMS during our practice / mall day event, which I presume would mean that we need to bind all of the Gizmos to the FMS at the practice day. I believe that means that they would no longer work in wireless mode after the practice day, unless they rebind the gizmo to their driver's station so that it can work wirelessly for the time after the practice day event and before the competition event.

Will binding the Gizmos to the FMS for practice day, then rebinding them to the driver's station afterwards, then rebinding them to the FMS on competition check in cause any issues, or is that going to be an acceptable sequence of events?

I realize once bound to the FMS for practice day, the teams will need to be tethered in their pit spaces during the practice day, until the are re-bound to their driver's station.

[the-maldridge]

I thought for sure I'd sent a reply to this yesterday but didn't actually click the button...

Your understanding is correct of the binding sequence, and it will work as expected. There are some security implications to re-using network keys between practice and competition days, though I would say they're probably acceptable risks at this time. I can give you more accurate information on that not on a public thread.

[shannonsjones]

Thanks. If we do end up using the FMS for practice day, I will either tell teams to rebind them to their drivers stations or have them come see me and I will do it before they leave.

…

On Mon, Sep 16, 2024, 2:42 PM Michael Aldridge ***@***.***> wrote: I thought for sure I'd sent a reply to this yesterday but didn't actually click the button... Your understanding is correct of the binding sequence, and it will work as expected. There are some security implications to re-using network keys between practice and competition days, though I would say they're probably acceptable risks at this time. I can give you more accurate information on that not on a public thread. — Reply to this email directly, view it on GitHub <#26 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BC5QWH3ZFB642SDJDJMFE7LZW4YAZAVCNFSM6AAAAABOHT4IVKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANRWGM2DSOI> . You are receiving this because you authored the thread.Message ID: ***@***.***>