Section 8. Operation
323
emptystring.Therewillbeonedescriptorforeachfieldnamegivenon
HeaderLine2.
Record Element 1 – Timestamp
Datawithouttimestampsareusuallymeaningless.Nevertheless,the
TableFile()instructionoptionallyincludestimestampsinsomeformats.
Record Element 2 – Record Number
Recordnumbersareoptionallyprovidedinsomeformatsasameansto
ensuredataintegrityandprovideanup‐cou
ntdatafieldforgraphing
operations.Themaximumrecordnumberis&hffffffff(a32‐bit
number),thentherecordnumbersequencerestartsatzero.TheCR800
reportsbacktothedataloggersupportsoftware31bits,oramaximum
of&h7fffffff,thenitrestartsat0.Iftherecordnumberincrementson
ce
asecond,restartatzerowilloccuraboutonceevery68years.
8.3.2 Memory Conservation
One or more of the following memory-saving techniques can be used on the rare
occasions when a program reaches memory limits:
• Declare variables as DIM instead of Public. DIM variables do not require
buffer memory for data retrieval.
• Reduce arrays to the minimum size needed. Arrays save memory over the
use of scalars as there is less "meta-data" required per value. However, as a
rough approximation, 192000 (4-kB memory) or 87000 (2-kB memory)
variables will fill available memory.
• Use variable arrays with aliases instead of individual variables with unique
names. Aliases consume less memory than unique variable names.
• Confine string concatenation to DIM variables.
• Dimension string variables only to the size required.
Read More! More information on string variable-memory use and conservation is
available in String Operations (p. 237).
8.3.3 Memory Reset
Four features are available for complete or selective reset of CR800 memory.
8.3.3.1 Full Memory Reset
Full memory reset occurs when an operating system is sent to the CR800 using
DevConfig or when entering 98765 in the Status table field FullMemReset. A
full memory reset does the following:
• Clears and formats CPU: drive (all program files erased).
• Clears SRAM data tables.
• Clears Status-table elements
To Next Page
Loading...
Need help?
General
