11 system signatures, 4 tips, 1 use of variable arrays to conserve code space – Campbell Scientific CR800 and CR850 Measurement and Control Systems User Manual
Page 150

Section 7. Installation
150
Seven special variable names are used to access information about a table:
• EventCount
• EventEnd
• Output
• Record
• TableFull
• TableSize
• TimeStamp
Consult CRBasic Editor Help index topic DataTable access for complete
information.
7.7.3.11 System Signatures
Signatures help assure system integrity and security. The following resources
provide information on using signatures.
• Signature() instruction in Diagnostics
(p. 461).
• RunSignature entry in table Status Table Fields and Descriptions
(p. 506).
• ProgSignature entry in table Status Table Fields and Descriptions
(p. 506).
• OSSignature entry in table Status Table Fields and Descriptions
(p. 506).
• Security
(p. 70)
Many signatures are recorded in the Status table, which is a type of data table.
Signatures recorded in the Status table can copied to a variable using the
programming technique described in the Program Access to Data Tables
(p. 148).
Once in variable form, signatures can be sampled as part of another data table for
archiving.
7.7.4 Tips
7.7.4.1 Use of Variable Arrays to Conserve Code Space
CRBasic example Use of Variable Arrays to Conserve Code Space
(p. 151)
shows
example code to convert twenty temperatures in a variable array from °C to °F.
Note When using the () syntax, whether on the disable parameter or with
multiplier and offset on measurement instructions, if the parameter expression is
more than a simple reference to a variable, e.g., disvar() + 5, or multiplier() * 4, or
NOT enable_var(), the () syntax is ignored and reps will not take place for the
expression.