4 converting tob3 files with cardconvert, 5 tablefile() with option 64 q & a – Campbell Scientific CR3000 Micrologger User Manual
Page 275

Section 7. Installation
275
DataTable
(TableName,TriggerVariable,Size)
TableFile
(FileName...LastFileName)
'Output processing instructions go here
EndTable
For example, in micrometeorological applications, TableFile() with
Option 64
is
used to create a new high-frequency data file once per day. The size of the file
created is a function of the datalogger scan frequency and the number of variables
saved to the data table. For a typical eddy-covariance station, this daily file is
about 50 MB large (10 Hz scan frequency and 15 IEEE4 data points). CRBasic
example Using TableFile() with Option 64 with CF Cards (p. 275) is an example
of a micromet application.
CRBasic Example 63. Using TableFile() with Option 64 with CF Cards
'The following CRBasic program shows how the instruction is used in micrometeorology
'eddy-covariance programs. The file naming scheme used in TableFile() in this example is
'customized using variables, constants, and text.
Public
sensor(10)
DataTable
(ts_data,TRUE,-1)
'TableFile("filename",Option,MaxFiles,NumRec/TimeIntoInterval,Interval,Units,
OutStat,LastFileName)
TableFile
("CRD:"&Status.SerialNumber(1,1)&".ts_data_",64,-1,0,1,Day,0,0)
Sample
(10,sensor(1),IEEE4)
EndTable
BeginProg
Scan
(100,mSec,100,0)
'Measurement instructions go here.
'Processing instructions go here.
CallTable
ts_data
NextScan
EndProg
7.8.20.4 Converting TOB3 Files with CardConvert
The TOB3 format that is used to write data to CF 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. 76),
will convert data files from one
format to another. CardConvert Help has more details.
7.8.20.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 CF card to store an interval amount of data
1
. Pre-allocation allows