Campbell CR3000 Micrologger, Руководство оператора

Страница: 220 / 644

Section 7. Installation
220
7.7.10.4 Converting TOB3 Files with CardConvert
The TOB3 format that is used to write data to memory cards saves disk space.
However, the resulting binary files must be converted to another format to be read
or used by other programs. The CardConvert software, included in Campbell
Scientific datalogger support software
(p. 90),
will convert data files from one
format to another. CardConvert Help has more details.
7.7.10.5 TableFile() with Option 64 Q & A
Q: How does Option 64 differ from other TableFile() options?
A: Pre-allocation of memory combines with TOB3 data format to give Option 64
two principal advantages over other TableFile() options. These are:
•
increased runtime write performance
•
short card-eject times
Option 64 is unique among table file options in that it pre-allocates enough
memory on the memory card to store an interval amount of data
1
. Pre-allocation
allows data to be continuously and more quickly wri
tten to the card in ≈1 KB
blocks. TOB3 binary format copies data directly from CPU memory to the
memory card without format conversion, lending additional speed and efficiency
to the data storage process.
Note Pre-allocation of memory card files significantly increases run time
write performance. It also reduces the risk of file corruption that can occur
as a result of power loss or incorrect card removal.
Note To avoid data corruption and loss, memory card removal must
always be initiated by pressing the Initiate Removal button on the face of
the NL115 or CFM100 modules. The card must be ejected only after the
Status light shows a solid green.
Q: Why are individual files limited to 2 GB?
A: In common with many other systems, the datalogger natively supports signed
four-byte integers. This data type can represent a number as large as 231, or in
terms of bytes, roughly 2 GB. This is the maximum file length that can be
represented in the datalogger directory table.
Q: Why does a large card cause long program compile times?
A: Program compile times increase with card and file sizes. As the datalogger
boots up, the card must be searched to determine space available for data storage.
In addition, for tables that are created by TableFile() with Option 64, an empty
file that is large enough to hold all of the specified records must be created (i.e.,
memory is pre-allocated). When using TableFile() with Option 64, program
compile times can be lessened by reducing the number of records or data-output