CR1000 Manual - Campbell Scientific

Section 8. Operation
8.3.3.2 Program Send Reset
8.3.3.3 Manual Data-Table Reset
• Initializes system variables.
• Clears communications memory.
Full memory reset does not affect the CRD: drive directly. Subsequent user
program uploads, however, can erase CRD:.
Operating systems can also be sent using the program Send feature in datalogger
support software (p. 77). Beginning with CR1000 operating system v.16, settings
and status are preserved when sending a subsequent operating system by this
method; data tables are erased. Rely on this feature with caution, however, when
sending an OS to CR1000s in remote and difficult-to-access locations.
Final Storage (p. 454) data are erased when user programs are uploaded, unless
preserve / erase data options are used. Preserve / erase data options are presented
when sending programs using File Control Send (p. 454) command and CRBasic
Editor Compile, Save and Send (p. 451). See Preserving Data at Program Send (p.
110) for a more-detailed discussion of preserve / erase data at program send.
Data-table memory is selectively reset from
• Support software Station Status (p. 466) command
• external keyboard / display: Data | Reset Data Tables
8.3.3.4 Formatting Drives
CPU:, USR:, USB:, and CRD: drives can be formatted individually. Formatting a
drive erases all files on that drive. If the currently running user program is found
on the drive to be formatted, the program will cease running and any SRAM data
associated with the program are erased. Drive formatting is performed through
datalogger support software (p. 569) Format (p. 454) command.
8.3.4 File Management
As summarized in table File Control Functions (p. 341), files in CR1000 memory
(program, data, CAL, image) can be managed or controlled with datalogger
support software (p. 77), CR1000 web API, or CoraScript. Use of CoraScript is
described in the LoggerNet software manual, which is available at
www.campbellsci.com. More information on file attributes that enhance
datalogger security, see the Security (p. 70) section.
340