...
A text string describing the I/O tag. Maximum: 128 characters.
Possibility to use the Dictionary (to open press CTRL+L).
Status text
Defines a status text for the I/O tag. Status text allows to redefine labels of individual I/O tag values.
...
Technical units of the I/O tag. Maximum: 12 characters. Possibility to use the Dictionary (to open press CTRL+L).
Limits
Technological limits may be defined for I/O tags of AI, AO, CI, CO, TiR and ToR types.
| Kotva | ||||
|---|---|---|---|---|
|
...
Timeout
Time delay (in seconds) for the evaluation of process alarm. Process alarm raise, if a cause of raising the alarm is valid at least within this period.
Block Alarms
The Block Alarms check box disables evaluation of process alarms.
...
Selection of a Display mask, that will be used in process D2000 HI (the Alarm list window - the Event description column) after changing the status of one of the defined process alarms into the Normal state.
Individual items allowing to set parameters of process alarms are ordered in a table. The table contains the following columns:
- Alarm - the column contains all possible causes of raising process alarm for the object.
- State - the radio buttons allows to select just one of State, Transition or None options. Enabled State option means, that process alarm starts when the value of the I/O tag is at least within the period defined by Timeout parameter, in the particular state (the name of particular state is placed in the particular row, in Alarm column - pa_ValueStateName).
- Transition - checked Transition option means, that process alarm starts when the I/O tag value passes to particular state (the name of particular state is placed in the particular row, in Alarm column - pa_ValueStateName).
- None - process alarm is not evaluated when this option is enabled
- ACK - checked ACK option means, that process alarm must be acknowledged by an operator in process D2000 HI. "Transition" process alarm must be always acknowledged.
- Critical - flag of critical process alarm.
- Monitor - the option will write particular change of the I/O tag value state into the log database as a spontaneous value change.
- Display mask - selection of a display mask, that will be used in process D2000 HI (the Alarm list window - the Event description column) after changing the status of one of the defined process alarms to particular state.
Raise signal
Raise signal parameter contains three checkboxes with the following function:
- first checkbox - is placed below State and Transition columns. Enabling (checking) the option, the system generates the signal, if any of configured process alarms occurs
- second checkbox - is placed below Critical column. Enabling (checking) the option, the system generates the signal, if any of configured critical process alarms occurs.
- third checkbox - is placed below Monitor column. Enabling (checking) the option, the system will generate the signal, if any of logged changes of defined process alarms is written into the log database.
Generating the signal means, that the system tag Signal_Trigger is set to TRUE value.
| Kotva | ||||
|---|---|---|---|---|
|
...
Destination column
It can contain the reference to column of object of Structured variable type in the form ObjectName[0]^ColumnName. In such case the KOM process tries to copy the values of arrays with start address which is configured in tab Address to the relevant column of the structured variable. There is no need to create the individual I/O tag for the each item of array or for other repeated address structure. Only some communication protocols support this functionality. More additional information are mentioned in the description of particular communication protocol.
...
I/O tag address. Address type depends on the communication protocol of the station, that is the parent of particular I/O tag. Address is stored in the configuration database in text form. Particular communication protocol converts this address into a binary form. For internal communication protocols of D2000 system, there is used the protocol-dependent dialog box with the validity check of given address during I/O tag address configuration. Address is entered directly in text form for external communication protocols (OEM_Protocol1 up to OEM_Protocol8) of the D2000 system.
At saving the I/O tag configuration, the uniqueness of its address is tested. If the address of I/O tag is not unique, the system will inform about error.
By choosing the option Yes, the new CNF dialog window opens. Only I/O tags with the conflict address and the common parent is shown in this window. The user can (but he need not) change the address of these I/O tags.
...
Values of I/O tags acquired from the communication, which have new time and their values are not changed, will be represented as new values.
Limits by device
This option is available, if the device and communication protocols allow to detect device limits. If the parameter is checked, then limits gained from communication with this device will be used.
...
If a new value is less than Min or greater than Max, the system sets it as an undefined value.
...
If a new value is less than Min value, the system will assign the Min value to this new value. If a new value is greater than Max value, the system will assign the Max value to this new value. This filter may be used to eliminate values, which technically may not break given limits (e.g. throttle stops), but the particular sensor (converter) may also generate values out of limits
...
If a new value is less than Min value, the system will assign the SetMin value to this new value. If a new value is greater than Max value, the system will assign the SetMax value to this new value.
Ignore value if out of limits
If a new value is less than Min value or greater than Max value, it will be discarded.
...
I/O tag values, which are changed by defined Number times in defined time (Time spin button), will pass an object value state to Oscillate.
...
The system will assign the value from Value option to particular I/O tag, when its value belongs in <Value-Range ....Value+Range> interval.
Value delay
The system will assign a value (it is defined by selecting the particular button) to particular I/O tag anly after it is unchanged during defined time [s].
...
Allows rounding the value time to the closest time with defined period (parameters Hours, Minutes and Seconds).
| Kotva | ||||
|---|---|---|---|---|
|
...
| Conversion type | Conversion formula |
|---|---|
| None | - |
| Linear | Output = A * Input + B |
| Polynomial | Output = A * Inputn *B x Input + C |
| Pt 100 | Output = a = -5.802E-05 |
| Simatic S5Time | Conversion of the Siemens Simatic relative time structure. |
A, B, C, n - conversion constants
The above table shows the conversion performed when processing the value received from the device. An inverse conversion is performed when writing to the output I/O tag.
Therefore for For I/O tags of output type (AO Ao, Co and COToR) it's possible to configure only the linear conversion, because only there exists unique inverse function used during value writing into particular device.
...
- If the option is enabled, then a value must be entered into Start value input box and a control object must be defined - Control object input box. Valid mode is defined by means of Manual/Auto radio buttons. Mode may be changed in process D2000 HI and its changes are to be stored in the system database. Operator can change required value in Manual mode. Its change is also stored in the system database.
- If the option is disabled, then only one of Auto or Manual modes may be enabled. Operator's right to change required value is defined by means his/her access rights. Changing required value in process D2000 HI is allowed to an operator with Control access right level or higher.
...
Start value is saved in text form. Then it is converted to corresponding value type and is set as the value of the I/O tag. If it is not entered or the conversion has not been executed successfully, the initialization of output I/O tags' values is not executed.
Start value checkout 
The button Start value checkout () checks defined start value and reports failure if the conversion is not successful.
...
The value of this object is to be used as the value of the output I/O tag in the Auto mode.
Auto
Enabling the option causes the value of the output I/O tag to copy the value of control object.
...
Enabling the option causes the value of the I/O tag to use the value specified in the parameter Start value or operator sets it manually in process D2000 HI.
| Kotva | ||||
|---|---|---|---|---|
|
I/O tag output mode.
- Value - I/O tag with own value acquired from the communication. Writing a new value of I/O tag into particular device is accompanied with the transient state. New value is confirmed after the communication verifies the writing.
- Command - Output I/O tag, that may not have own value (cannot acquire it by means of the communication with particular device). Writing a new value into the device do not pass through the transient state. Control windows in process D2000 HI also allow to write a value several times (e.g. enabled ON and OFF buttons at the same time - for value outputs, there is always enabled the button of the opposite value to the current one).
...
The parameter defines the command execution timeout - writing a value of the I/O tag. If the value of the parameter is different from zero and writing an I/O tag value is not confirmed during the timeout, the writing is not consider as successful and there is occurred process alarm ErrorWriteCmd if defined (the item ErrorWriteCmd in the tab Process alarms).
Output time
The parameter Use D2000 Server time allows to use the time of the computer where process D2000 Server is running as the time for output I/O tag's value. Otherwise, the time acquired by the communication with the device, is used.
| Kotva | ||||
|---|---|---|---|---|
|
...
Default value allows to replace an I/O tag value acquired by process D2000 KOM by another one in some cases, (e.g. sensing device breakaway, failure of the communication with whole device). I/O tag value may be replaced by a value of other object (so-called control object), or adjusted manually by operator of process D2000 HI via the control window.
...
Save changes of the default value mode
If the option Use default value is checked, then a change of the use of default value or disabling the default value from the control window in process D2000 HI is to be stored in the configuration database (it enables or disables the option Use default value).
Force default value on HardError
If the communication process evaluates an I/O tag value as unknown (acquired from the communication or failure of the communication with station), then the default value will be used. After the communication is recovered, the default value is cancelled and the I/O tag gets a value acquired from the communication. This change into the default value or cancelling the default value is not to be written into the configuration database (even if the option Save default value changes is enabled).
Allow switchover to default value in HI
...
The option allows to enable or disable mode change (from Manual mode to Auto mode and vice-versa) on the operator level in process D2000 HI. If the option is enabled, a control object must be entered - Control object item.
Save default value changes
...
Default value verification
Default value verification () button will verify entered default value and if is not valid, the system will display the report on it.
...
Enabling the option, the I/O tag default value will use a number in Default value input box or it will be adjusted manually by operator in process D2000 HI.
...
Logical polarity of the I/O tag is adjusted for digital I/O tags - DI, DO.
- Normal - an I/O tag value is not to be changed.
- Inverse - an I/O tag value is to be inverted.
| Kotva | ||||
|---|---|---|---|---|
|
...
The tab Verification allows to set confirmation for writing the output I/O tag (verified) using an input object (verifying). Verifying object can be an object of I/O tag, Switch or other types (e.g. Eval tag). For the I/O tag with enabled verification to be written successfully, it is not enough to send a value to the communication (and receiving the confirmation of successful writing from the partner station, if the communication protocol allows it), but a value of the verifying object must be received, that confirms the writing.
Verification is meaningful, if the D2000 system is part of a distributed control system (e.g. in energetics), where successful writing an I/O tag (e.g. setting the setpoint for the generator output) needn't mean that the real value was set changed to required level (the generator can be in the manual mode with the regulator disconnected, so the setpoint change of the regulator does not have any effect on the generator output). Only the new value of the measured generator output, that will be the same (with the Delta tolerance) as the value set, means that writing was successful.
...
- Writing a verified output I/O tag is successful, if a new value of the verifying object that confirms the value written will comes within the execution timeout (the tab Output control). Values of the verifying object, which do not meet the condition, will not cause any action (i.e. they do not cause unsuccessful writing).
- If the execution timeout is 0, there is waiting without limit.
- If the execution timeout expires, writing the output I/O tag is not considered to be successful and the alarm ErrorWriteCmd occurs, if it is configured.
- Within the execution timeout, several values of the verifying object may come. The values, which are not equal to the value written (with the Delta tolerance) do not cause the writing to be treated as unsuccessful, i.e. writing the I/O tag is unsuccessful when the execution timeout exceeds.
- If the value of the verifying object is equal with the written value (with the Delta tolerance) of the output I/O tag when writing, the writing is acting like the verification is not enabled, i.e. does not wait for new value of the verifying object, but writing is successful immediately after sending the value to the communication (and after confirmation, if the protocol supports it)
Table: evaluation of equation and validity of the tolerance parameter Delta for various type combinations of verifying object and verified output I/O tag.
| D - logical value I - integer value Q - quaternary value | Tr - relative time Ta - absolute time R - real value | Txt - text | |||||
| Verifying object Verified I/O tag | D | I | R | Ta | Tr | Txt | Q |
|---|---|---|---|---|---|---|---|
| Dout (logical) | equation | equation * | Delta | On/Off | |||
| Co (integer) | equation ** | Delta | Delta | Delta *** | |||
| Ao (real) | Delta ** | Delta | Delta | Delta *** | |||
| ToR (relative time) | Delta | Delta | |||||
| ToA (absolute time) | Delta | Delta | |||||
| TxtO (text) | equation | ||||||
Notes:
* - the value of 0 corresponds to the status B_False, the other values correspond to the status B_True
...
A number that determines the permitted deviation of the values of the verified output I/O tag and the verifying object. If the absolute value of the value difference is lower or equal to Delta, writing is successfully confirmed (Abs(Out-In)<Delta, details for various type combination are shown in the table above). For I/O tags of TxtO type (text output), the parameter is not used.
...