Section 8. Operation
494
8.8.1.1.2 CPU: Drive
CPU: is the default drive on which programs and calibration files are stored. It is
formatted as FAT32. Do not store data on CPU: or premature failure of memory
will probably result.
8.8.1.1.3 USR: Drive
SRAM can be partitioned to create a FAT32 USR: drive, analogous to partitioning
a second drive on a PC hard disk. Certain types of files are stored to USR: to
reserve limited CPU: memory for datalogger programs and calibration files.
Partitioning also helps prevent interference from data table SRAM. USR: is
configured using
DevConfig
settings or
SetStatus()
instruction in a CRBasic
program. Partition USR: drive to at least 11264 bytes in 512-byte increments. If
the value entered is not a multiple of 512 bytes, the size is rounded up. Maximum
size of USR: 2990000 bytes.
USR: is not affected by program recompilation or formatting of other drives. It
will only be reset if the USR: drive is formatted, a new operating system is
loaded, or the size of USR: is changed. USR: size is changed manually by
accessing it in the
Status
table or by loading a CRBasic program with a different
USR: drive size entered in a
SetStatus()
or
SetSetting()
instruction. See
CRBasic Program — Setup Tools
(p. 153).
Measurement data can be stored on USR: as discrete files by using the
TableFile()
instruction. Table
TableFile() Instruction Data File Formats
(p. 497)
describes available data-file formats.
Note
Placing an optional USR: size setting in the CRBasic program
over-rides manual changes to USR: size. When USR: size is changed
manually, the CRBasic program restarts and the programmed size for
USR: takes immediate effect.
The USR: drive holds any file type within the constraints of the size of the drive
and the limitations on filenames. Files typically stored include image files from
cameras (see
Cameras — List
(p. 658))
, certain configuration files, files written for
FTP retrieval, HTML files for viewing with web access, and files created with the
TableFile()
instruction. Files on USR: can be collected using
datalogger support
software
Retrieve
(p. 583)
command, or automatically using the datalogger
support software
Setup File Retrieval
tab functions.
Monitor use of available USR: memory to ensure adequate space to store new
files.
FileManage()
command can be used in the CRBasic program to remove
files. Files also can be removed using datalogger support software
Delete
(p. 583)
command.
Two
Status
table fields monitor use and size of the USR: drive. Bytes remaining
are indicated in field
USRDriveFree
. Total size is indicated in field
USRDriveSize
. Memory allocated to USR: drive, less overhead for directory
use, is shown in datalogger support software
File Control
(p. 583)
window.
Summary of Contents for CR6 Series
Page 2: ......
Page 4: ......
Page 6: ......
Page 32: ......
Page 36: ......
Page 38: ......
Page 76: ...Section 5 Overview 76 FIGURE 20 Half Bridge Wiring Example Wind Vane Potentiometer ...
Page 80: ...Section 5 Overview 80 FIGURE 23 Pulse Input Wiring Example Anemometer ...
Page 136: ......
Page 454: ...Section 8 Operation 454 FIGURE 104 Narrow Sweep High Noise ...
Page 459: ...Section 8 Operation 459 FIGURE 106 Vibrating Wire Sensor Calibration Report ...
Page 535: ...Section 8 Operation 535 8 11 2 Data Display FIGURE 121 CR1000KD Displaying Data ...
Page 537: ...Section 8 Operation 537 FIGURE 123 CR1000KD Real Time Custom ...
Page 538: ...Section 8 Operation 538 8 11 2 3 Final Storage Data FIGURE 124 CR1000KD Final Storage Data ...
Page 539: ...Section 8 Operation 539 8 11 3 Run Stop Program FIGURE 125 CR1000KD Run Stop Program ...
Page 541: ...Section 8 Operation 541 FIGURE 127 CR1000KD File Edit ...
Page 546: ......
Page 552: ......
Page 610: ...Section 11 Glossary 610 FIGURE 137 Relationships of Accuracy Precision and Resolution ...
Page 612: ......
Page 648: ......
Page 650: ......
Page 688: ......
Page 689: ......