Appendix B. Status, Settings, and Data
Table Information (Status/Settings/DTI)
Related Topics:
• Status, Settings, and Data Table Information (Status/Settings/DTI) (p. 603)
• Common Uses of the Status Table (p. 604)
• Status Table as Debug Resource (p. 485)
The Status table, CR1000 settings, and the DataTableInfo table (collectively,
Status/Settings/DTI) contain registers, settings, and information essential to
setup, programming, and debugging of many advanced CR1000 systems.
Status/Settings/DTI are numerous. Note the following:
• All Status/Settings/DTI, except a handful, are accessible through a keyword.
This discussion is organized around these keywords. Keywords and
descriptions are listed alphabetically in sub-appendix Status/Settings/DTI
Descriptions (Alphabetical)
(p. 611).
• Status fields are read only (mostly). Some are resettable.
• Settings are read/write (mostly).
• DTI are read only.
• Directories in sub-appendix Status/Settings/DTI Directories
(p. 604) list several
groupings of keywords. Each keyword listed in these groups is linked to the
relevant description.
• Some Status/Settings/DTI have multiple names depending on the interface
used to access them.
• No single interface accesses all Status/Settings/DTI. Interfaces used for
access include the following:
Table 141. Status/Setting/DTI: Access Points
Access Point Locate in...
Settings Editor
Device Configuration Utility, LoggerNet Connect screen,
PakBus Graph. See Datalogger Support Software — Details
(p.
450).
Status
View as a data table in a numeric monitor
(p. 521).
DataTableInfo
View as a data table in a numeric monitor
(p. 521).
Station Status
Menu item in datalogger support software
(p. 654).
Edit Settings
Menu item in PakBusGraph software.
Settings
Menu item in CR1000KD Keyboard Display Configure,
Settings
status.keyword/settings.keyword
Syntax in CRBasic program
1
Information presented in Station Status is not updated automatically. Click the Refresh button to update.
Note Communication and processor bandwidth are consumed when generating
the Status and DataTableInfo tables. If the CR1000 is very tight on processing
time, as may occur in very long or complex operations, retrieving the Status table
repeatedly may cause skipped scans
(p. 487).
603