Specifications

Section 12. Memory and Data Storage
12-10
“Oh, what a tangled web we weave...” - Sir Walter Scott.
Back in the old days of volatile RAM, life was simple. Nasty at times, but
simple. You lose power, you lose program, variables, and data. Simple. You
re-start from scratch. The advent of non-volatile memory has saved a lot of
frustration in the field, but it requires thought in some applications. For
instance, if the CR1000 loses power, do you want it to power back up with the
same program, or another one? with variables intact or erased? with data intact
or erased?
The key to the CF power-up function is the powerup.ini file, which contains a
list of one or more command lines. At power-up, the powerup.ini command
line is executed prior to compiling the program. Powerup.ini performs three
operations:
1) Copies the specified program file to a specified memory drive.
2) Sets a file attribute on the program file
3) Optionally deletes CF data files from the overwritten (just previous)
program.
Powerup.ini takes precedence during power-up. Though it sets file attributes
for the programs it uploads, its presence on the CF does not allow those file
attributes to control the power-up process. To avoid confusion, either remove
the CF card or delete the powerup.ini file after the powerup.ini upload.
Creating and Editing Powerup.ini
Powerup.ini is created with a text editor, then saved as “powerup.ini”.
Some text editors (such as WordPad) will attach header
information to the powerup.ini file causing it to abort. Check the
text of a powerup.ini file with the CR1000KD to see what the
CR1000 actually sees.
Comments can be added to the file by preceding them with a single-quote
character (‘). All text after the comment mark on the same line is ignored.
Syntax
Syntax allows functionality comparable to File Control in LoggerNet.
Powerup.ini is a text file that contains a list of commands and parameters. The
syntax for the file is:
Command,File,Device
where
Command = one of the numeric commands in Table 1.
File = file on CF associated with the action. Name can be up to 22
characters.
Device = the device to which the associated file will be copied to.
Options are CPU:, USR:, and CRD:. If left blank or with invalid option,
will default to CPU:.
NOTE