Campbell Scientific CR10X Measurement and Control System - Manual (Page 45)

SECTION 1. FUNCTIONAL MODES
1-9
Intermediate Storage and Final Storage are
erased when memory is repartitioned. This
feature may be used to clear memory without
altering programming. The number of locations
does not actually need to be changed; the same
value can be keyed in and entered.
If Intermediate Storage size is too small to
accommodate the programs or instructions
entered, the "E:04" ERROR CODE will be
displayed in the
∗0, ∗6, and ∗B Modes. The
user may remove this error code by entering a
larger value for Intermediate Storage size.
Intermediate Storage and Program Memory can
be automatically allocated by entering 0 for their
size. When automatic allocation is used, all
data are erased any time the program is
exchanged and recompiled. Final Storage size
is maximized by limiting Intermediate Storage
and Program Memory to the minimum
necessary. The size of Final Storage and the
rate at which data are stored determines how
long it will take for Final Storage to fill, at which
point new data will write over old.
After repartitioning memory, the program must be
recompiled. Compiling erases Intermediate
Storage. Compiling with
∗0 erases Input Storage;
compiling with
∗6 leaves Input Storage unaltered.
ENTERING 98765 for the number of bytes to
allocate for program memory COMPLETELY
RESETS THE CR10X. All memory is erased
including any stored programs and memory is
checked. Memory allocation returns to the default.
The reset operation requires approximately 1
minute for a CR10X, 5 minutes for a CR10X-1M,
and 10 minutes for a CR10X-2M. Please be
patient while the reset takes place; if the CR10X is
turned off in the middle of a reset, it will perform
the reset the next time it is powered up.
1.6 MEMORY TESTING AND SYSTEM
STATUS -
∗∗∗∗B
The
∗B Mode is used to check the status of the
program’s operating system and lithium battery.
Table 1.6-1 describes what the values seen in
the
∗B Mode represent.
A signature is a number which is a function of
the data and the sequence of data in memory.
It is derived using an algorithm which assures a
99.998% probability that if either the data or its
sequence changes, the signature changes.
The signature of the program memory is used
to determine if the program tables have been
altered. During the self check on reset, the
signature computed for the OS is compared
with a stored signature to determine if a failure
has occurred. The algorithm used to calculate
the signature is described in Appendix C.
The contents of windows 6 and 7, Operating
System (OS) version and version revision, are
helpful in determining what OS is in the datalogger.
As different versions are released, there may be
operational differences. When calling Campbell
Scientific for datalogger assistance, please have
these numbers available.
TABLE 1.6-1. Description of ∗∗∗∗B Mode Data
Keyboard Display
Entry ID: Data Description of Data
∗ B
01: XXXXX Program memory Signature. The value is dependent upon the
programming entered and the total size and allocation of
memory. The signature for the same program will be different in
a CR10X and a CR10X-2M. If the program has not been
previously compiled, it will be compiled and run.
A 02: XXXXX Operating System (OS) Signature
A
03: XXXXX Memory Size, Kbytes (Flash + SRAM)
A 04: XX Number of E08 occurrences (Key in 88 to reset)
A 05: XX Number of overrun occurrences (Key in 88 to reset)
A
06: X.XXXX Operating System version number
A 07: XXXX. Version revision number
A 08: X.XXXX Lithium battery voltage (Measured daily. Should be >2.4. See
Section 14.11 for replacement.)
A 09: XX Low 12 V battery detect counter (Key in 88 to reset)
A 10: XX Extended memory error counter (Key in 88 to reset)
A
11: X.XXXX Extended Memory time of erase, seconds (Updated only during
memory reset or test)