System information

Section 4. The CR1000 Type Datalogger
4-7
4.7.4 Deleting Program Files
When loading a new datalogger program to the CR1000 type datalogger, the
old datalogger program can remain in datalogger memory for future use or
reference. Although data tables are recreated and the data for the currently
running program will be lost when a new program begins running on the
datalogger, the old program does not have to be deleted. However, if the
datalogger memory becomes too full or if the old program is no longer needed
the File Control transaction provides a method of deleting files either when
sending a new program to the datalogger or as an independent transaction. The
FileCmd codes in the File Control transaction include the following options:
 0x01: Compile and run the new program
 0x02: Toggle the “run on power-up” option on the datalogger program
specified
 0x03: Make the specified file hidden so it cannot be downloaded or
viewed.
 0x04: Delete the specified file
 0x05: Format the datalogger
 0x06: Compile and run the program without deleting data tables
 0x07: Stop the running program
 0x08: Stop the running program and delete all associated files
 0x09: Make the specified file the new operating system
 0x0a: Compile and run the program without changing the “run on power-
up” file
 0x0b: Pause execution of the running program
 0x0c: Resume execution of the running program
 0x0d: Stop the running program, delete associated files, and run the
specified program while marking it as the “run on power-up” program
 0x0e: Stop the running program, delete associated files, and run the
specified program without changing the “run on power-up” attribute
The CR1000 type datalogger can store files in memory for future use or
retrieval. If the files contained on the CR1000 type datalogger are not known,
obtain a list of the files by requesting a file named “.DIR” with the File Upload
transaction. Once the list of files has been retrieved, use the File Control
transaction to make necessary changes to the files or file attributes.
4.8 Understanding Table Definitions and Table
Signatures
Since the CR1000 type dataloggers store data in tables, the datalogger and the
application must understand and agree on the structure of each table in order to
collect data. Table definitions contain the parameters that describe each table,
record, and field in the datalogger and are contained in a file on the datalogger
with a “.TDF” extension. This file is obtained from the datalogger using the
File Upload transaction.
Table definitions are used by the application to know what tables and fields
exist and what data to expect from each table when collecting values from the
CR1000 type datalogger. In order to ensure the integrity of this table
information, the application should calculate signatures for the tables within
the table definitions. One signature should be calculated for each defined table
and should be stored and used by the application to verify that the table has not
changed when collecting data.