Campbell CR510, Operator'S Manual

Page: 39 / 264

SECTION 1. FUNCTIONAL MODES
1-9
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.
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.
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 (Windows 1-4) does not actually
need to be changed; the same value can be
keyed in and entered.
ENTERING 98765 for the number of bytes to
allocate for program memory (5th Window)
COMPLETELY RESETS THE CR510.
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 CR510, 5
minutes for a CR510-1M, and 10 minutes for a
CR510-2M. Please be patient while the reset
takes place; if the CR510 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 Operating Sytem
(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.
NOTE: Instruction 19 calculates one
signature for the program and the Operating
System. Because this is a combined
signature, it is not the same as the
signatures in Windows 1 or 2.
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.