Vector 8 Devices can now be mapped to athletes in the Catapult Vector app, available in the More section of the app, from the menu bar.
This is in addition to existing Device mapping actions that can be performed in the OpenField Console.
Important Notes:
- Athlete Device Mapping is applied on each mapping action and requires internet connection.
- For the configuration to apply to the wearable device, the Dock must have been online to receive the config update, and the wearable device inserted into the Dock.
- Once a device is mapped to an athlete, the submission of the Wearable Device configuration, with the Athlete settings, is automatic.
- Device mappings set/updated for accounts using Vector 8 devices are applied to all sub users in the account.
Athlete List in the Catapult Vector App
- On page load, the teams and athletes for the account are loaded. The account’s default team is the first team that is loaded.
- To switch teams, use the team selection dropdown.
- Athletes for the selected team are presented in the list, sorted by Jersey.
- Each athlete will show either their current Wearable device assignment, or an "Unmapped" status.
Mapping A Wearable Device to an Athlete in the Catapult Vector App
- Selecting an athlete by pressing the device dropdown opens the mapping menu.
- The page header will display the athlete you are selecting a wearable device for.
- The list shows all devices registered to the account on the left, and each device’s current athlete assignment - or an "Unmapped" status - on the right.
Selecting an unmapped device:
- Will apply the device to the selected athlete only.
Selecting a device with a current athlete assignment:
- Will apply the device to the selected athlete AND remove it from the previous athlete.
Once a device is selected, the dialogue will close and the mapping status will be shown in the list:
-
Mapping - Mapping in progress (syncing in progress)
-
Mapped - Mapping complete (synced to Cloud and verified successful)
Mapping Vector 8 Devices in OpenField Console
Note: Device mappings set or updated in Console for accounts using Vector 8 devices will overwrite any conflicting changes made in the Cloud or Catapult Vector app, if those changes occurred after Console was last synced.
Any device athlete mappings applied in the Catapult Vector app will be synced down to all OpenField Console users, when they perform a Sync, regardless of which user is logged into the Vector app.
In Console, these device athlete mappings will appear as the ‘default’ mappings, which are those that appear when the mapping screen is open with no activity open, or when a live activity is open.
Default Device mappings - when no activity is loaded:
It may be necessary to change device athlete mappings in OpenField Console, after mappings have been applied in the Vector app, such as immediately prior to, or during a live activity.
Changing device mappings during a live activity - or when a live activity is open in Console - follows the same logic as changing default device mappings when no activity is open. That is, the default device mapping for the account is updated.
When default device mappings are changed in OpenField Console, and OpenField Console syncs, these mappings will persist for the account in the Cloud and any changes will be reflected in the Vector app.
In addition, because the default mappings have been updated, the Vector device(s) will be reconfigured with the new athlete’s settings the next time they are connected to a Vector 8 Dock with internet access.
It is still possible to update device athlete mappings for historical activities, and these changes will sync to the Cloud, where they will be reflected in the Cloud Editor and reporting. However, updating mappings for historical activities will not affect the default mappings or trigger device reconfiguration after Console sync - unless the historical activity is the most recent activity.
Related articles