Section 8. Operation
501
The number of records in a data table when
CardOut()
or
TableFile()
with
Option 64
is used in a data-table declaration is governed by these rules:
1. Memory cards (CRD: drive) and internal memory (CPU) keep copies of data
tables in binary TOB3 format. Collectible numbers of records for both CRD:
and CPU are reported in
DataRecordSize
entries in the
Status
table.
2. In the table definitions advertised to
datalogger support software
(p. 97),
the
CR6 advertises the greater of the number of records recorded in the
Status
table, if the tables are not fill-and-stop.
3. If either data area is flagged for fill-and-stop, then whichever area stops first
causes all final-data storage to stop, even if there is more space allocated in the
non-stopped area, and so limiting the number of records to the minimum of the
two areas if both are set for fill-and-stop.
4. When
CardOut()
or
TableFile()
with
Option 64
is present, whether or not a
card is installed, the CPU data-table space is allocated a minimum of about 5
KB so that there is at least a minimum buffer space for storing the data to
CRD: (which occurs in the background when the CR6 has a chance to copy
data onto the card). So, for example, a data table consisting of one four-byte
sample, not interval driven, 20 bytes per record, including the 16 byte TOB3
header/footer, 258 records are allocated for the internal memory for any
program that specifies less than 258 records (again only in the case that
CardOut()
or
TableFile()
with
Option 64
is present). Programs that specify
more than 258 records report what the user specified with no minimum.
5. When
CardOut()
or
TableFile()
with
Option 64
is used but the card is not
present, zero bytes are reported in the
Status
table.
6. In both the internal memory and memory card data-table spaces, about 2 KB
of extra space is allocated (about 100 extra records in the above example) so
that for the ring memory the possibility is minimized that new data will
overwrite the oldest data when datalogger support software
tries to collect the
oldest data at the same time. These extra records are not reported in the
Status
table and are not reported to the datalogger support software and
therefore cannot be collected.
7. If the
CardOut()
or
TableFile()
with
Option 64
instruction is set for
fill-and-stop, all the space reserved for records on the card is recorded before
the writing of final-data to memory stops, including the extra 2 kB allocated to
alleviate the conflict of storing the newest data while reading the oldest when
the area is not fill-and-stop, or is ringing around. Therefore, if the CPU does
not stop earlier, or is ring and not fill-and-stop, then more records will be
stored on the card than originally allocated, i.e., about 2 KB worth of records,
assuming no lapses. At the point the writing of final-data stops, the CR6
recalculates the number of records, displays them in the
Status
table, and
advertises a new table definition to the datalogger support software. Further,
if the table is storing relatively fast, there might be some additional records
already stored in the CPU buffer before final-data storage stops altogether,
resulting in a few more records than advertised able to be collected. For
example — on a CR6 storing a four-byte value at a 10 ms rate, the CPU not
set to fill-and-stop, CRD: set to fill-and-stop after 500 records — after
final-data storage stopped, CRD: had 603 records advertised in the
Status
table (an extra 103 due to the extra 2 KB allocated for ring buffering), but 608
Summary of Contents for CR6 Series
Page 2: ......
Page 4: ......
Page 6: ......
Page 32: ......
Page 36: ......
Page 38: ......
Page 76: ...Section 5 Overview 76 FIGURE 20 Half Bridge Wiring Example Wind Vane Potentiometer ...
Page 80: ...Section 5 Overview 80 FIGURE 23 Pulse Input Wiring Example Anemometer ...
Page 136: ......
Page 454: ...Section 8 Operation 454 FIGURE 104 Narrow Sweep High Noise ...
Page 459: ...Section 8 Operation 459 FIGURE 106 Vibrating Wire Sensor Calibration Report ...
Page 535: ...Section 8 Operation 535 8 11 2 Data Display FIGURE 121 CR1000KD Displaying Data ...
Page 537: ...Section 8 Operation 537 FIGURE 123 CR1000KD Real Time Custom ...
Page 538: ...Section 8 Operation 538 8 11 2 3 Final Storage Data FIGURE 124 CR1000KD Final Storage Data ...
Page 539: ...Section 8 Operation 539 8 11 3 Run Stop Program FIGURE 125 CR1000KD Run Stop Program ...
Page 541: ...Section 8 Operation 541 FIGURE 127 CR1000KD File Edit ...
Page 546: ......
Page 552: ......
Page 610: ...Section 11 Glossary 610 FIGURE 137 Relationships of Accuracy Precision and Resolution ...
Page 612: ......
Page 648: ......
Page 650: ......
Page 688: ......
Page 689: ......