Instruction manual

SECTION 3. REPORT: SPLIT
PC208W, Version 3.0, Instruction Manual 3-9
other input files until their starting times are
reached.
Included in the time synchronize function is the
ability to start relative to the current PC TIME
(computer time). This feature allows a .PAR file
to be run on different data without changing the
Start Conditions, provided the Input Data File is
collected at a fixed frequency and SPLIT is run
at a fixed frequency. For example, assume that
PC208W is used in scheduled data collection
mode which automatically appends data to an
archive file. SplitR is executed using the “After
Call do” option in PC208W. In this case the
frequency of data collection and data reduction
is the same. Time values in the data file (day,
hrmn, sec.) are different each time the data are
collected, but by telling SPLIT where to Start
reading relative to the PC clock, the Start
Conditions do not need to be changed. To
accommodate variations in the data collection
and reduction frequencies, an interval in
minutes or seconds may be specified as shown
in the examples below.
:3[-60,5] tells SPLIT to start at the closest 5
minute interval that is less than the PC time
minus 60 minutes. If the PC time is 1404,
SPLIT calculates 1304 and looks for hour 1300
to start reading.
2[-3]:3[-120,60] tells SPLIT to find the closest
60 minute interval that is less than the PC time
minus 3 days and 2 hours. If the PC time is the
day of year 159, hour 0017, SPLIT will start
reading on data output at 2200 hours on day
155.
2[-3]:3[-120]:4[20,5] tells SPLIT to find the
closest 5 second interval that is less than the
PC time minus 3 days, 2 hours and 20 seconds.
If the PC time is 27 seconds after noon on day
30, SPLIT will begin reading on data output at
1000 hours and 05 seconds on day 27.
CAUTION: SPLIT will not start reading if
the exact specified starting time cannot be
found. The interval (5 minutes, 60 minutes,
and 5 seconds in the examples above)
must be evenly divisible into 60 minutes.
3.3.3 STOP CONDITION
The Stop Condition is expressed with the same
syntax as the Start Condition, with the exception
that there is no time synchronization. If the
Stop Condition parameter is left blank, SPLIT
will execute until the end of the file. Logical
"and" and "or" statements can be used when
specifying the Stop Condition (Section 3.3.2).
The Stop Condition specifies when to stop
processing data. This feature allows segments
of data to be removed from large data files. For
instance, if a data file contains one month of
data and just one day is desired, the start and
stop values allow the user to get just that day’s
data. The array containing the Stop Condition is
not included in the output file. If the stop value
is not found, SPLIT will display a dialog box that
gives the option to select a new file and
continue processing the data. This feature is
useful when data are contained on several
diskettes.
The C and F commands alter the meaning of
the Stop Condition.
3.3.3.1 "C" Option: Formatting Event Tests
Containing Conditional Output Arrays
The C option is used to combine data from two
or more conditional arrays on to one Split output
line. A conditional array is one that is only output
when a defined event occurs.
Assume that two or more conditional Output
Arrays with unique Output Array IDs compose a
test period, followed by an unconditional Output
Array that defines the end of a test. The
unconditional "end of test" Output Array is at the
end of each test, but the conditional Output
Arrays may or may not be present. The data file
is comprised of several of these tests.
As an example, let's look at a vehicle test
application. The start of the test is when the
vehicle is turned on, and the end of the test is
when the vehicle is turned off. The conditional
output arrays could be:
• monitoring the engine temperature and
outputting data to a unique array when the
temperature exceeds a limit
• outputting data to a unique array when the
brakes are applied
• outputting data when engine RPM exceeds
a limit