User Manual

P/N R64216 v3.1 Page | 55
unrecoverable. Frequent synchronization will limit your potential for data loss since all information is
backed up on the SRS Data Server.
2. System Performance Evaluation: Frequent synchronization allows for regular monitoring of incoming
data. Algorithms designed to evaluate data quality and SRS performance, are executed daily for all
data contained on the SRS Data Server. These evaluations enable the SRS Customer Service team to
identify potentially malfunctioning hardware or problems with use of the system. With daily
synchronization, these errors can be caught and corrected quickly, thus improving the overall quality
of data collection.
Due to the reasons stated above, it is recommended that synchronization of SRS data be performed following
EVERY data collection session. During occasions where daily synchronization is not feasible, weekly
synchronization is REQUIRED.
Weekly Diagnostic Check
While every effort is made to ensure the SRS hardware (MxEncoders, Sideline Controller, Access Point, Alert
Pager System, Field Case) is functioning properly, over the course of a season, damage or excessive wear may
occur. The absolute worst time to identify equipment problems is during competition as this can lead to
missed data. The good news, however, is the vast majority of problems can be caught using a few simple
diagnostic techniques.
Follow the procedure below to verify that your equipment is working correctly. If the equipment is not working
as expected this procedure will walk you through basic troubleshooting steps.
1. Remove Batteries: Remove all batteries from the MxEncoders after 1 week of use.
2. Demo Session: Setup the SRS in the location where the battery change is occurring using your typical
setup procedure. Create a demo session. (You can either create the demo session in RedZone and
then synchronize your local database or your can create the session through HIT Analyzer.)
Remember that any impacts that are created during a demo session will be invalidated, so if a helmet
is accidentally dropped or impacted, the recorded impact will be safely eliminated from future
analyses. (Note: HIT Analyzer should be launched after all old batteries have been removed)
3. Install Batteries: Install charged batteries into all MxEncoders.
4. MxEncoder Communication: Enter your session and make sure that all MxEncoders have successfully
communicated with the system. If communication has not occurred (i.e. a helmet is still listed as
‘inactive’), check for the following:
o Installed MxEncoder: First check to see if an MxEncoder is installed within the player’s
helmet. Players have been known to remove MxEncoders without notification to team
personnel
o MxEncoder Turns On: Place your hand inside the non-communicating helmet at the location
of the on/off sensor. This should be sufficient to turn the unit on
o Re-Install Battery: Check to see if a battery was installed in the helmet. Frequently
MxEncoders are ‘missed’ during the battery changing procedure, especially when replacing
batteries for a large group of helmets
o Charged Battery: Was the battery fully charged? Try replacing with another battery that is
known to be charged. Note: Over time and frequent recharging, batteries may no longer
respond to recharging. If this occurs, contact Riddell Customer Service to arrange
replacement