SECTION 1. FUNCTIONAL MODES

The maximum size of Input and Intermediate Storage and the minimum size of Final Storage are determined by the size of RAM chips installed (Table 1.5-1). Input and Intermediate Storage are confined to the same RAM chip as system and program memory, they cannot be expanded onto the second chip which is always entirely dedicated to Final Storage. A minimum 28 Input and 768 Final Storage Area 1 locations will ALWAYS be retained. The size of Intermediate Storage may be reduced to 0.

Intermediate Storage and Final Storage Area 1 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. Storage Area 2 is protected when Input and/or Intermediate Storage is reallocated, but cleared if Storage Area 2 is reallocated.

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 either altering the programs or by entering a larger value for Intermediate Storage size. Final Storage size can be maximized by limiting Intermediate Storage to the minimum number of locations necessary to accommodate the programs entered. 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.

The number of bytes remaining in program memory is displayed in the fifth window. ENTERING 1986 (the total bytes available) COMPLETELY RESETS THE CR10. All memory is erased and the power-up memory check and initialization is repeated as if the power were switched off and on again.

1.6MEMORY TESTING AND SYSTEM STATUS - *B

The *B Mode is used to 1) read the signature of the program memory and the software PROM, 2) display the size of RAM+PROM, 3) display the number of E08 occurrences (Section 3.10), 4) display the number of overrun occurrences (Section 1.1.1), 5) display PROM version number. Table 1.6-1 describes what the values seen in the *B Mode represent. The correct signature of the CR10 PROM is listed in Appendix B.

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 power-up, the signature computed for a PROM is compared with a signature stored in the PROM 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, PROM version and version revision, are helpful in determining what PROM is in the datalogger. Over the years, several different PROM versions have been released, each with operational differences. When calling Campbell Scientific for datalogger assistance, please have these two numbers available.

 

TABLE 1.6-1. Description of *B Mode Data

Keyboard

Display

Description of Data

Entry

ID: Data

*B

01: XXXXX

Program memory Signature. The value is dependent upon the

 

 

programming entered and memory allotment. If the Tables have

 

 

not been previously compiled, they will be compiled and run.

A

02: XXXXX

PROM Signature

A

03: XXXXX

Memory Size 32K ROM + No. K RAM

A

04: XXXXX

No. of E08 occurrences (Key in 88 to reset)

A

05: XXXXX

No. of overrun occurrences (Key in 88 to reset)

A

06: X.XXXX

PROM version number

1-8