04.01.2015 Views

CR1000 Manual - Campbell Scientific

CR1000 Manual - Campbell Scientific

CR1000 Manual - Campbell Scientific

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Section 8. Operation<br />

Record Element 1 – Timestamp<br />

Data without timestamps are usually meaningless. Nevertheless, the<br />

TableFile() instruction optionally includes timestamps in some formats.<br />

Record Element 2 – Record Number<br />

Record numbers are optionally provided in some formats as a means to<br />

ensure data integrity and provide an up‐count data field for graphing<br />

operations. The maximum record number is &hffffffff (a 32‐bit<br />

number), then the record number sequence restarts at zero. The<br />

<strong>CR1000</strong> reports back to the datalogger support software 31 bits, or a<br />

maximum of &h7fffffff, then it restarts at 0. If the record number<br />

increments once a second, restart at zero will occur about once every<br />

68 years.<br />

8.3.2 Memory Conservation<br />

One or more of the following memory-saving techniques can be used on the rare<br />

occasions when a program reaches memory limits:<br />

• Declare variables as DIM instead of Public. DIM variables do not require<br />

buffer memory for data retrieval.<br />

• Reduce arrays to the minimum size needed. Arrays save memory over the<br />

use of scalars as there is less "meta-data" required per value. However, as a<br />

rough approximation, 192000 (4-kB memory) or 87000 (2-kB memory)<br />

variables will fill available memory.<br />

• Use variable arrays with aliases instead of individual variables with unique<br />

names. Aliases consume less memory than unique variable names.<br />

• Confine string concatenation to DIM variables.<br />

• Dimension string variables only to the size required.<br />

Read More! More information on string variable-memory use and conservation is<br />

available in String Operations (p. 236).<br />

8.3.3 Memory Reset<br />

Four features are available for complete or selective reset of <strong>CR1000</strong> memory.<br />

8.3.3.1 Full Memory Reset<br />

Full memory reset occurs when an operating system is sent to the <strong>CR1000</strong> using<br />

DevConfig or when entering 98765 in the Status table field FullMemReset. A<br />

full memory reset does the following:<br />

• Clears and formats CPU: drive (all program files erased).<br />

• Clears SRAM data tables.<br />

• Clears Status-table elements<br />

• Restores settings to default.<br />

339

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!