Campbell Scientific CR10X TD Operating System Addendum for CR510, CR10X, and C - Page 4

Overview of Data Storage Tables, Converting an existing program to Table Based OS - specifications

Page 4 highlights

TABLE DATA ADDENDUM AD2 Overview of Data Storage Tables Within a data table, data is organized in records and fields. Each row in a table represents a record and each column represents a field. To understand the concept of tables it may be helpful to consider an example. A CR10-TD is to be used to monitor 3 thermocouples (TC). Each hour a temperature for each of the three TC is to be stored. The table has 4 fields : "DATE_TIME TEMP1 TEMP2 TEMP3". Each hour a new "record" would be added. The "hourly" table would then be organized as follows: DATE_TIME TEMP1 TEMP2 TEMP3 01/27/91 10:00:0023.5 24.6 28.2 01/27/91 11:00:0024.2 22.4 23.4 Only the hourly data is stored in the hourly table, Each output interval has its own table. Data tables can also be "event driven" rather than interval driven, that is a new record is stored when a specified event occurs rather than based on time. Each table is completely independent of any other tables and all records in a given table have the same number of fields. The TD operating system supports naming of tables and fields, so any data value can be referenced by the table and field names. For example, the temperature data for the first thermocouple is referenced as "HOURLY.TEMP1". Computer software also allows the station to be named. When multiple dataloggers are in use, this can be used to reference specific data in the network. If, in the previous example, the CR10T site was named DALLAS, the first thermocouple's data values would be referenced by "DALLAS.HOURLY.TEMP1". AD3 Converting an existing program to Table Based OS This section is intended for those familiar with programming an Array based datalogger. AD3.1 Programming changes • Remove all Record Real Time instructions (Instruction 77). • Remove all Serial Data Output and Serial Print instructions (Instructions 96 and 98). • Remove all Initiate Telecommunication (callback) instructions (Instruction 97). • Check all instructions which set the Output Flag (Flag 0). These should be replaced with the Data Table Instruction (Instruction 84). If the Set Active Storage Area instruction (Instruction 80) is used, it should be removed as Instruction 84 provides this functionality. • Check all If Time Instructions (Instruction 92) as the units may change from minutes to seconds. Any instruction 92 that sets the output flag (Flag 0) is replaced by Instruction 84. • Check the Move Time To Input Location Instruction (Instruction 18) as some parameters have changed. AD-2

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62

TABLE DATA ADDENDUM
AD-2
AD2
Overview of Data Storage Tables
Within a data table, data is organized in records and fields.
Each row in a
table represents a record and each column represents a field.
To
understand the concept of tables it may be helpful to consider an example.
A CR10-TD is to be used to monitor 3 thermocouples (TC).
Each hour a
temperature for each of the three TC is to be stored.
The table has 4 fields
: "DATE_TIME TEMP1 TEMP2 TEMP3".
Each hour a new "record"
would be added.
The "hourly" table would then be organized as follows:
DATE_TIME
TEMP1
TEMP2
TEMP3
01/27/91 10:00:0023.5
24.6
28.2
01/27/91 11:00:0024.2
22.4
23.4
Only the hourly data is stored in the hourly table,
Each output interval
has its own table.
Data tables can also be "event driven" rather than
interval driven, that is a new record is stored when a specified event
occurs rather than based on time.
Each table is completely independent
of any other tables and all records in a given table have the same
number of fields.
The TD operating system supports naming of tables and fields, so any
data value can be referenced by the table and field names.
For example,
the temperature data for the first thermocouple is referenced as
"HOURLY.TEMP1".
Computer software also allows the station to be
named.
When multiple dataloggers are in use, this can be used to
reference specific data in the network.
If, in the previous example, the
CR10T site was named DALLAS, the first thermocouple's data values
would be referenced by "DALLAS.HOURLY.TEMP1".
AD3
Converting an existing program to Table Based OS
This section is intended for those familiar with programming an Array
based datalogger.
AD3.1
Programming changes
Remove all Record Real Time instructions (Instruction 77).
Remove all Serial Data Output and Serial Print instructions
(Instructions 96 and 98).
Remove all Initiate Telecommunication (callback) instructions
(Instruction 97).
Check all instructions which set the Output Flag (Flag 0).
These
should be replaced with the Data Table Instruction (Instruction 84).
If the Set Active Storage Area instruction (Instruction 80) is used, it
should be removed as Instruction 84 provides this functionality.
Check all If Time Instructions (Instruction 92) as the units may
change from minutes to seconds.
Any instruction 92 that sets the
output flag (Flag 0) is replaced by Instruction 84.
Check the Move Time To Input Location Instruction (Instruction
18) as some parameters have changed.