Vector T7 KEY NEW FEATURES
- Device Position in Vest or Waist Mounted
- Significantly Smaller Device Compared to T6 (46%) and S7 (73%)*
- Live Jumps
- Basketball Movement Profile
- 24-device charging dock with portable travel case
* Storage capacity reduced to 14 hours of memory with significant reduction in unit size.
- Indoor Tracking Capability
- WiFi Enabled Dock
- Local Positioning – Catapult ClearSky 10Hz+
- Wireless Communication – Ultra-Wideband (UWB) and BT
- Wireless Range - Up to 250m (UWB)
- 6 Hour Battery Life
- Heart Rate - Polar 5.5kHz Compatible (all models)
- Accelerometer - 3D +/- 16G. Sampled at 100Hz
- Gyroscope - 3D 2000 degrees/second at 100Hz
- Magnetometer - #D ±4900 μT at 100Hz
|Data Feature||Vector T7||Vector S7||Details|
Basketball Movement Profile
Dynamic - Turning and change of direction movements
Running - Steady jogging/running movements
Active - Walking-like movements
Settled - Standing-like movements
Jumping - Jumping movements
|Live + Post||Live + Post||
Do not support interchangeability between the vest and waist location measurements.
|Live + Post||Post||
Jump height in Low/Medium/High segments
Estimated distance via inertial sensors
Distance, Velocity and Acceleration
|Live + Post||Live + Post||
ClearSky system required
Basketball movement profile (BMP) Jump Metrics will be available live and post with Vector T7. Jump Metrics are calculated following a sequence of movement patterns beginning when a vertical movement is detected via accelerometers. If that vertical movement is not associated with a forward acceleration force, heuristic rules are applied to the data associated with air time, take-off and landing to identify a jump event and intensity. The new jump metrics in the basketball movement profile differ from IMA jumps which will remain available in the software. If users have not collected and analysed jump data previously, it is recommended that the new BMP jumps are preferred. If using IMA jumps currently, BMP jumps should be used alongside current data until sufficient historical data exists and a switch can be made. Users should note that when using RHIE metrics, jumps that form part of this calculation will remain as IMA jumps until further updates to the software.
DIFFERENCES IN PLAYERLOAD (au) BETWEEN T7, T6 and S7
The Vector T7 device will produce increased PlayerLoad when compared directly to Vector S7 or Vector T6 devices. These differences are attributed to the smaller mass and size of the Vector T7, which introduces a greater level of sensitivity to high frequency movements and impact. Table 1 summaries these expected differences.
DIFFERENCES IN T7 PLAYERLOAD (au) BETWEEN TRUNK AND WAIST
Internal testing has observed differences in PlayerLoad based on the location of where a Vector T7 is worn by the athlete (Table 2). For the same activity, PlayerLoad reported a greater output when worn at an anterior waist location compared to when worn at the trunk between the scapulae. As the intensity of movement increased, the absolute difference in PlayerLoad between tag locations was also seen to increase.
IMA Acceleration/Deceleration and Change of Direction (COD) metrics will also be impacted by device location/orientation. When the T7 is worn in the traditional vest, the reported values will be comparable to previously collected data with either T6 or S7. However, when positioning the T7 on the waist, users will need to consider differences in data when using either posterior or anterior locations. In a posterior waist location, the orientation of Acceleration, Deceleration and COD metrics (L vs. R), will remain the same though differences in values will exist for the same rationale as differences in Player load. When the device is in an anterior waist position, the Acceleration, Deceleration and COD metrics will be in the reverse orientation (i.e. Acceleration will be Deceleration and COD R will actually be L) as the unit is facing an opposite direction. Differences in values will be expected similar to a posterior position. If an anterior waist position is used, it is suggested that the default name is changed for IMA Acceleration/Deceleration (i.e. Acceleration will be Deceleration) and COD (i.e. left will become right) in the OpenField Cloud.