Devices are used to transfer high-level data such as reports, command logs or alarm logs.
To add a device:
For a description of the properties, see below.
Note: SQL devices are configured differently to other types of devices. For information, see Configure SQL Devices.
Device Properties
Property |
Description |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Name |
The name of the device. |
||||||||||
Format |
Specifies how the data is formatted in the device. The format is determined by the type of device, and the data that is sent to the device (see Format Data in the Device). Enter a value of 120 characters or less. If you are logging alarms or command messages, you need to specify a format, or no data is written to the device. See Command Fields for a list of the fields (or field combinations) you can use to format a command logging device. For a list of the fields you can use to format an alarm logging device, see the following: Note: The log device for a command is specified wherever the command is defined. The log device for an alarm is specified at the Alarm Categories form. When producing reports, the format is ignored. (The format defined for the report is used to write the report to the device.) |
||||||||||
Header |
Additional information for the device. Enter a value of 254 characters or less. |
||||||||||
File Name |
The file name of the device. Enter a value of 253 characters or less. |
||||||||||
Type |
The type of device. Enter a value of 16 characters or less.
* When defining RTF report properties, an ASCII device would be selected if the report was to be saved as a file. This property is optional. If you do not specify a type, the device Type is ASCII_DEV unless:
See Print Management. |
||||||||||
No. Files |
The number of history files (see Use Device History Files). Enter a value of 4 characters or less. By default, Citect SCADA creates a single data file for each device. (This data file is called <filename.TXT> or <filename.DBF>, depending whether the device is an ASCII device or database device.) The number of history files you specify here are in addition to the data file. Note: If you do not want history files created, you need to enter 0 (zero) here, and set the [Device]CreateHistoryFiles parameter to 0; otherwise, 10 history files will be created as a default. You need to also verify that the data file is of a fixed size. (If the data accumulates, the file eventually fills the hard disk.) If you specify -1 the data is appended to the end of one file. If you are logging alarm, keyboard commands, or reports to the device, specify the number of files to be created, and the time of each file. |
||||||||||
Time |
The time of day to synchronize the beginning of the history file, in hh:mm:ss (hours:minutes:seconds). Enter a value of 32 characters or less. If you accepted the default number of history files above, and you specify a time and period, 10 history files will be created. If you do not specify a time, the file is synchronized at 0:00:00 (i.e. midnight). If you omit both the time and the period, additional history files will still be created (with the default time and period). If you don't want history files to be created, you need to set the [Device]CreateHistoryFiles parameter to 0 (zero). |
||||||||||
Period |
The period of the history file, in hh:mm:ss (hours:minutes:seconds). Enter a value of 32 characters or less. Alternatively you can:
If you accepted the default number of history files above, and you specify a time and period, 10 history files will be created. If you do not specify a period, the time field will be ignored and the device will assume users will invoke device logging manually. If you omit the time but have specified a period, additional history files will still be created (with the default time mid-night at 00:00:00). If you don't want history files to be created, you need to set the [Device]CreateHistoryFiles parameter to 0 (zero). |
||||||||||
Comment |
Any useful comment. |
||||||||||
Cluster Name |
Select a cluster from the list of clusters defined previously with the in the Topology activity of Citect Studio. If this is a single cluster system this field can be left blank. |
||||||||||
Process |
Select the type of server (or client) on which the process runs that sends data to the device. This field is used to prevent a history file being created while the device is active. If there is no history processing then this field can be left blank. |
Property |
Description |
---|---|
Project |
The project that includes the device. |
See Also
Published June 2018