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

Страница: 386 / 678

Section 8. Operation
Table 91. Data-Preserve Options
if "Preserve data if no table changed"
keep CF data from overwritten program
if current program = overwritten program
keep CPU data
keep cache data
else
erase CPU data
erase cache data
end if
end if
if "erase CF data"
erase CF data from overwritten program
erase CPU data
erase cache data
end if
8.3.4.4 Powerup.ini File — Details
Uploading a CR1000 OS
(p. 522)
file or user-program file in the field can be
challenging, particularly during weather extremes. Heat, cold, snow, rain,
altitude, blowing sand, and distance to hike influence how easily programming
with a laptop or palm PC may be. An alternative is to carry the file to the field on
a light-weight, external-memory device such as a USB:
(p. 653)
or CRD:
(p. 653)
drive.
Steps to download the new OS or CRBasic program from an external-memory
drive are:
1. Place a text file named
powerup.ini , with appropriate commands entered in the
file, on the external-memory device along with the new OS or CRBasic
program file.
2. Connect the external device to the CR1000 and then cycle power to the
datalogger.
This simple process results in the file uploading to the CR1000 with optional run
attributes, such as Run Now , Run on Power Up , or Run Always set for
individual files. Simply copying a file to a specified drive with no run attributes,
or to format a memory drive, is also possible. Command options for powerup.ini
options also allow final-data memory management on CF cards comparable to the
datalogger support software
(p. 95)
File Control feature.
Options for powerup.ini also allow final-data memory management comparable
File Control
(p. 515).
Note that the CRD: drive has priority over the USB: drive.
Caution Test the powerup.ini file and procedures in the lab before going to the
field. Always carry a laptop or mobile device (with datalogger support software)
into difficult- or expensive-to-access places as backup.
Powerup.ini
commands include the following functions:
• Sending programs to the CR1000.
•
Optionally setting run attributes of CR1000 program files.
• Sending an OS to the CR1000.
386