Exercise Routine Execution
The RTS2000 Execute FGCS Exercise Routine program runs on the FGCS Controller. This program uses a *.rtn exercise routine file as input. The input file may be acquired from the local C: drive, from a smart card, or from the RTS2000 Server. When the routine file is acquired from the local system or from the RTS2000 server, the routine execution screen makes provisions for writing the routine to the smart card, if desired, before routine execution is begun.
The Execute Routine program extracts the data from the rows of the exercise routine table, sends the required commands to the FGCS, and accomplishes functions associated with carrying out the routine, such as alerting the user when the next exercise is to start and identifying the position on which the exercise is to be performed. Figures 1, 2, and 3 are screen prints from the operating Execute Routine Program. Figure 1 is the form of the program screen immediately after the "Execute Routine" scenario has been selected from the log-in screen. The screen remains in this state until the user either exits or selects an exercise routine source (Local, Smart Card, or RTS2000 Server). Figure 2 is the form of the program screen after a routine has been acquired and opened. Opening the routine causes the curve file (associated with the first exercise of the routine) and other required information to be downloaded to the FGCS. A thumbnail of the force curve is presented each time curve data are downloaded to the FGCS. The entire routine is presented at the bottom of the screen, with the first exercise highlighted, and pertinent information associated with the exercise loaded into the upper part of the window:
© 2007 Houston Enterprises Inc.
The program then waits for the user to start the exercise. If the exercise is NOT started within a predetermined period of time, the routine is aborted, and the screen returns to the state shown in Figure 1, where it waits for the user to either exit or re-initiate routine execution. If routine execution is started, the program presents the screen shown in Figure 3, where a countdown to start of the first exercise is presented, along with an identification of the number of the next exercise and the total number of exercises remaining in the routine. At the end of the countdown, an audible alert is generated for the user to start the exercise. The user may start the exercise early or late, as desired, without affecting execution of the routine.
During the course of routine execution, the program adds and removes weight as required, and collects exercise results data. At the completion of each exercise, information for the next exercise is downloaded and the countdown to start of the exercise is begun. At any point during routine execution, inactivity for a predetermined period of time will cause the routine to be aborted.
Click on an image below to enlarge
Figure 1.
Figure 2.
Figure 3.
The Execute Routine program makes use of a Force Curve Table Generation routine that is identical to the program that generates the force curve files that support Timed Exercise operation, with the exception that a table addressing a single weight is generated. This program makes it possible for each exercise in the routine to be executed using a different force curve.
While the user is executing the exercise routine, the Routine Execution Program collects data related to performance of each of the exercises. The specific data collected are position (within the stroke) and force, for each FGCS measurement cycle. A seperate results file is created for each exercise in the routine. The results file name is a concatenation of date, time, and exercise routine name, with a .res extension. The user name is included as part of the file header, for inclusion as part of the title of the graphs generated by the results processor. The Exercise Routine Results Processor processes results files to produce information that is usable by the trainer in assessing how the routine was completed.