...
The configuration dialog box of I/O tags consists of several parts (tabs) that contain similar parameters. The display of particular tabs depends on the category of the particular I/O tag.
General properties
Groups
Process alarms
Destination
Address
Filter
Conversion
Output control
Default value
Polarity
Verification
...
A text string describing the I/O tag. Maximum: 128 characters.
It is possible to use the Dictionary (press CTRL+L to open).
Status text
...
Technical units of the I/O tag. Maximum: 12 characters. Possibility to use the Dictionary (press CTRL+L to open).
Limits
...
| Kotva | ||||
|---|---|---|---|---|
|
...
Timeout
Time delay (in seconds) for the evaluation of process alarm. Process alarm is raised, if a the cause of raising the alarm is valid at least during this period.
Note: the time delay is applied only to status alarms - transition alarms occur immediately when the value is changed.
Block Alarms
The Block Alarms checkbox disables the evaluation of process alarms.
...
It can contain the reference to a column of an object of the Structured variable type in the form ObjectName[0]^ColumnName. In such a case, the KOM process tries to copy the values of arrays with the start address which is configured in tab Address to the relevant column of the structured variable. There is no need to create individual I/O tags for each item of an array or for some other repeated address structure. Only selected communication protocols support this functionality. More additional information is mentioned in the description of a particular communication protocol.
Note: it is also possible to use a non-zero index, e.g. SV.MyVal[7]^MyCol - in this case, values are written into the structured variable starting with the specified row (in example 7).
The copying of values into the column of a structured variable is implemented only for input, the change of a particular value of a structured variable (e.g. in HI or The copying of values into the column of a structured variable is implemented only for input, the change of a particular value of a structured variable (e.g. in HI or via event) will not be transferred as output through the communication into the device.
...
All parameters which are to be processed (e.g. limit setting) are applied according to the setting of the I/O tag where the destination column is configured (i.e. "master" I/O tag). The timestamps of the values inserted into the column of a structured variable are identical to the timestamp of a "master" I/O tag. The value of the "master" I/O tag and its behavior is normal, and it is not influenced byt by the configuration of the destination column.
...
I/O tag address. The address type depends on the communication protocol of the station, which is the parent of a particular I/O tag. The address is stored in the configuration database in a text form. A specific communication protocol converts this address into a binary form. For internal communication protocols of the D2000 system, a protocol-dependent dialog box with the validity check of a specified address is used during the I/O tag address configuration. For external communication protocols (OEM Protocol 1 up to OEM Protocol 16) of the D2000 system, the address is entered directly in text form.
During the saving of the I/O tag configuration, the uniqueness of its address is tested. If the address of the I/O tag is not unique (within a parent station), the system will inform you about the error. 
By choosing the option Yes, a new CNF dialog window opens. Only I/O tags with conflicting addresses sharing a common parent are displayed in this window. The user can (but does not have to) change the address of these I/O tags. 
Minute correction
...
Using the following group of parameters allows for defining a filtering method of analog inputs and outputs - Ai, Ao, Ci, Co, TiR, ToR.
...
Weighed first-order filter.
- Value- value after filtering
- New - filtered value
- Old - previous value
- K - the weight of the new value - a real number from the interval (0.0 .. 1.0).
The Repeat Parameter: This parameter provides compatible weighted filter behavior for change-based and server protocols (IEC-60870-5-101, IEC-60870-5-104, Modbus Server, TG809, BACnet, OPC, OPC UA ...). If a positive value of the Repeat parameter is specified, it determines the period of repeated generation of the value received by the I/O tag - similar to when the same value is repeatedly retrieved for periodically polling protocols (e.g. Modbus Client). So, if a one-time change of the I/O tag value occurs, the weighted filter will gradually progress towards toward the target value by repeating this value.
...
If a new value is less than the Min value, the system will assign the Min value to this new value. If a new value is greater than the 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 the Min value or greater than the Max value, it will be discarded.
...
The system will assign the value from the Value option to a particular I/O tag , when its value belongs in <Value-Range ....Value+Range> interval (this option is used to suppress the "noise" of I/O tag value)
...
Allows rounding the value time to the closest time with a defined period (parameters Hours, Minutes, and Seconds).
...
| 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
| Absolute value | Output = abs(Input ) |
| Bitmask filter AND | Output = ((A + B<<32) & Input ) >> C Note: the filter is configurable only for Integer inputs (Ci), constant A is a mask for the lower 32 bits, constant B is a mask for the upper 32 bits, and constant C indicates an optional shift of the result to the right by C bits. If C is negative, the result is shifted to the left by -C bits. |
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 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 I/O tags of output type (Ao, Co, and ToR), it's possible to configure only the linear conversion because only in this case there is an unambiguous inverse function used during value writing into a particular device.
...
- If the option is enabled, then a value must be entered into the Start value input box and a control object must be defined - Control object input box. The valid mode is defined by means of Manual/Auto radio buttons. A mode may be changed in the D2000 HI process and its changes will be stored in the system database. The operator can change the required value in Manual mode. Its change is also stored in the system database.
- If the option is disabled, then only one of the Auto or Manual modes may be enabled. The operator's right to change the required value is defined by means of their access rights. Changing a required value in the D2000 HI process is allowed to an operator with Control access right level (or higher).
...
The start value is saved in text form. Then it is converted to a corresponding value type and it is set as the value of the I/O tag. If it is not entered or the conversion has not been successful, the initialization of output I/O tags' values is not performed.
Start value checkout 
The button Start value checkout () checks the defined start value and reports failure if the conversion is not successful.
...
- Value - I/O tag with its own value acquired from the communication. Writing a new value of the I/O tag into a particular device is accompanied by a transient state. The new value is confirmed after the communication verifies the writing.
- Command - Output I/O tag, that may not have its own value (cannot acquire it by means of the communication with a particular device). A new value written into the device does not go through the transient state. Control windows in the the D2000 HI process also allow writing the same value several times (e.g. enabled ON and OFF buttons at the same time - unlike the value output tags where only the button of the opposite value than the current one is enabled).
...
Maximum step size for a change
The parameter parameter "Maximum step size for a change" allows limiting the maximum change of value for manual control. This limitation has the character of a recommendation and a user is able to override it.
...
The default value allows replacing an I/O tag value acquired by the D2000 KOM process by , with another one in some cases, (e.g. the sensor device breakaway, a failure of the communication with the device). An I/O tag value may be replaced by a value of another object (so-called control object) or adjusted manually by the operator of the D2000 HI process via the control window.
...
The default value is stored in text form. It is converted to a required value type and then is used as the value of the I/O tag.
If it is not defined or conversion has failed, the initialization of the values of the output I/O tag will not be executed (more info...).
Default value verification
The Default value verification () button will verify entered default value and if is not valid, the system will display the report on it.
...
| Kotva | ||||
|---|---|---|---|---|
|
...
Logical The logical polarity of the I/O tag is adjusted for digital I/O tags - Di, Dout.
...
The tab Verification allows setting confirmation for writing the output (verified) I/O tag using an input object (verifying). The 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 receive 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 useful if the D2000 system is part of a distributed control system (e.g. in energetics), where successful writing of an I/O tag (e.g. setting the setpoint for the generator output) doesn't mean that the real value was changed to a required value (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 after a new value of the I/O tag which represents the real value of the generator output, if it is 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 come within the execution timeout (the Output control tab). 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, waiting is not time-limited.
- If the execution timeout expires, writing to the output I/O tag is considered to be unsuccessful 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 to the I/O tag is unsuccessful only after the execution timeout exceeds.
- If the value of the verifying object is equal to the written value of the output I/O tag (with the Delta tolerance) when the value was written, the writing is acting as if the verification is not enabled, i.e. it does not wait for a 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).
...
An I/O tag (or Eval tag, Switch, ...), the value of which is the reaction to writing to the verified output I/O tag.
...
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 smaller or equal to Delta, the writing is successfully confirmed (Abs(Out-In)<Delta, details for various type combination combinations are shown in the table above). For I/O tags of TxtO type (text output), the parameter is not used.
...
Delta is a percent of range (the range is the difference between the high and low limits of the verified object, i.e. HL - LL ). If the limits are defined dynamically and they are crossed, verification is evaluated according to the last valid Deltaand low limits of the verified object, i.e. HL - LL ). If the limits are defined dynamically and they are crossed, verification is evaluated according to the last valid Delta.
Follow the verifying object value
If this option is active, the output I/O tag copies the value of the verifying object (but without performing writes in the communication). It is thus possible to ensure e.g. initialization after the start or controlling from the scheme by entering changes relative to the current value (e.g. +/- buttons on the scheme).
| Info | ||
|---|---|---|
| ||
I/O tags |
...