Status Processing
Status Processing
Status processing
v.8.20
© 2020 Ing. Punzenberger COPA-DATA GmbH
Distribution and/or reproduction of this document or parts thereof in any form are permitted solely
with the written permission of the company COPA-DATA. Technical data is only used for product
description and are not guaranteed properties in the legal sense. Subject to change, technical or
otherwise.
Contents
3 Status bits..................................................................................................................................................... 6
3.1 User status 1 to 8 [M1-M8] and 14 to 16 [M14-M16] ..................................................................... 11
3.2 Select in the network [NET_SEL] ............................................................................................................... 12
3.3 Revision [REVISION] ...................................................................................................................................... 12
3.4 In operation [PROGRESS]............................................................................................................................ 13
3.5 Run time exceeded [TIMEOUT] ................................................................................................................ 14
3.6 Manual value [MAN_VAL] ........................................................................................................................... 14
3.7 General interrogation [GI] .......................................................................................................................... 15
3.8 Spontaneous [SPONT] ................................................................................................................................. 15
3.9 Invalid [INVALID] ............................................................................................................................................ 15
3.10 External standard time [T_STD_E] ............................................................................................................ 16
3.11 Switched off [OFF] ......................................................................................................................................... 16
3.12 Real time - external time stamp [T_EXTERN] ....................................................................................... 17
3.13 Internal time stamp [T_INTERN] ............................................................................................................... 18
3.14 Not sortable [N_SORTAB] ........................................................................................................................... 19
3.15 Fault message transformer value [FM_TR] ........................................................................................... 19
3.16 Run message transformer value [RM_TR]............................................................................................. 19
3.17 Info for variable [INFO] ................................................................................................................................ 20
3.18 Alternative value [ALT_VAL] ....................................................................................................................... 20
3.19 Not updated in the zenon network [N_UPDATE] .............................................................................. 21
3.20 Internal standard time [T_STD] ................................................................................................................. 22
3.21 Cause of Transmission [COTx] .................................................................................................................. 22
3.22 P/N-Bit (N_CONF) .......................................................................................................................................... 24
3.23 Test bit [TEST] .................................................................................................................................................. 25
3.24 Acknowledge writing [WR-ACK] .............................................................................................................. 25
3.25 Writing successful [WR-SUC]..................................................................................................................... 25
3.26 Normal status [NORM] ................................................................................................................................ 25
3.27 Deviation normal status [N_NORM] ....................................................................................................... 26
3.28 IEC status: Blocked [BL_870] ...................................................................................................................... 26
3.29 IEC status: Substituted [SB_870] ............................................................................................................... 26
3.30 IEC status: Not Topical [NT_870] .............................................................................................................. 26
3.31 IEC status: Overflow [OV_870]................................................................................................................... 27
3.32 Command step: Select [SE_870] ............................................................................................................... 27
3.33 External time stamp invalid [T_INVAL] ................................................................................................... 28
3.34 Breaker tripping detected [CB_TRIP] ...................................................................................................... 28
3.35 Breaker tripping detection inactive [CB_TR_I] ..................................................................................... 29
3.36 Value out of the valid range [OR_DRV] ................................................................................................. 30
3.37 ClockNotSynchronized [T_UNSYNC] ...................................................................................................... 30
3.38 Not recorded in the Process Recorder [PR_NR] ................................................................................. 31
3.39 Time deviation [T_DEV] ................................................................................................................................ 31
4 Usage........................................................................................................................................................... 32
4.1 Reaction matrices .......................................................................................................................................... 32
4.2 Dynamic screen elements ........................................................................................................................... 33
4.3 Combined element........................................................................................................................................ 33
4.4 Report Generator ........................................................................................................................................... 34
4.5 Recipegroup Manager ................................................................................................................................. 34
4.6 VBA ...................................................................................................................................................................... 34
4.7 Process Recorder ........................................................................................................................................... 34
Welcome to COPA-DATA help
GENERAL HELP
If you cannot find any information you require in this help chapter or can think of anything that you
would like added, please send an email to [email protected].
PROJECT SUPPORT
You can receive support for any real project you may have from our customer service team, which
you can contact via email at [email protected].
2 Status processing
With the status administration you get a better overview in the process and in the network. Each
variable can have its own statuses. A total of 64 statuses/attributes have been defined.
5 | 34
Status bits
Attention
The driver for internal variables does not support status administration. Use the
driver for simulator variables instead.
In the Runtime there are several possibilities to evaluate the status of a variable, as for example: the
combined element, the reaction matrices (on page 32) and the Report Generator. The status is also
accessible in VBA or VSTA as well as in the Recipegroup Manager.
If a variable is saved in zenon, such as in the Archive, CEL, or AML, the entry consists of three pieces
of information: value, time stamp and state. This means: Each archived value also contains the correct
status.
COMMUNICATION ERROR
Communication errors are also shown in color in the Runtime.
These colors can be adjusted in the project properties in the Graphical design/Status of variable
node.
3 Status bits
The following status bits are available in zenon:
Bit Short term Long name zenon Logic identifier
number
6 | 34
Status bits
7 | 34
Status bits
8 | 34
Status bits
9 | 34
Status bits
10 | 34
Status bits
Information
In formulas all status bits are available. For other use the availability can be
limited.
Note:
The single states are not available for all drivers.
As the statuses of each variable can also be accessed from VBA/VSTA in form of a 64 bit
value, the bit position of each status is also listed in the detailed description below. This
information is necessary for the individual evaluation with VBA/VSTA.
There are two possibilities for display in Runtime: the short form and the long form. These
are separated in the description by a "/".
For each user status, its own text can be defined. This text then is displayed in the different
modules (editors such as Runtime). In this case, the short text and long text is separated by a
semi-colon ";".
To do this, the following entries must be inserted into project.ini:
[STATUS]
STATUS0=MS_K;my status 0
STATUS1=ET;custom text
......
STATUS63=RES;not used
11 | 34
Status bits
The total of 11 user status bits can be used project-specifically. Examof usage for these user status bits
are e.g.: special interlockings of Command Processing or flags for own information.
Information
The user status bit M1 is used by the command processing action Block to mark
the switching point as blocked. The bit is also used in the IEC850 driver when
transferring service tracking data to Runtime.
You can find further information in the command processing manual and in the
IEC850 driver documentation.
The NET_SEL status bit highlights the response variable during command processing in the zenon
network. If the NET_SEL bit is set, another command selection - from a further workspace (for
example from another client in the network) - cannot be executed on the same response variable.
12 | 34
Status bits
Variables can be set to revision. If this status is active, alarms and setting of command processing are
suppressed by the process control system. It is thus possible to simply not show individual equipment
parts from alarming and processing.
Note: Only the alarms and command processing are suppressed. All other limit value properties that
are linked to this, such as Limit value color, Execute function instantly, Invisible, Flashing etc., are
not affected by this and are displayed or executed. The current variable values are also shown on the
screens as before and also archived.
The display can be amended individually using the properties in the zenon
Editor:
Representation/Display status of variable element property: Activates or
deactivates the display.
Status of variable/Communication failure to PLC project property:
Enables the color of the display to be amended.
The status bit in operation together with command processing (only SICAM 230 or zenon Energy
Edition) is used to show that a switch is in operation, as a result of which the switch will change its
position (on/off). The status bit is set and reset when runtime monitoring is started, if this has been
successfully completed or overwritten (TIMEOUT (on page 14)) .
The automatic setting of the bit in Runtime can be activated by activating the Set status PROGRESS
property.
If the written command already matches the response value, the bit is not set. Only response values
ON and OFF can be monitored.
13 | 34
Status bits
The runtime exceeded status is only set by the Command Processing module. The Command action
type sets the bit if the timeout for the Watchdog is exceeded or the command has been ended
negatively. This is also applicable if COT_actterm is received by the PLC with a P/N bit (COT value 10
with N_CONF - status bits 33, 35 and 38).
The display can be amended individually using the properties in the zenon
Editor:
Representation/Display status of variable element property: Activates or
deactivates the display.
Status of variable/Communication failure to PLC project property:
Enables the color of the display to be amended.
This status is set, as soon as a value in an archive has been changed by hand. This can be done in the
Report Generator or in screen Archive revision.
14 | 34
Status bits
In addition, the validation of the the metering point administration sets this status if a measured value
is edited manually.
After initializing Runtime, the first image that is read is named “general request”. That means that the
value has not changed since Runtime start.
This bit is set, if there is a problem in the communication with the driver or with a single variable. Most
of the zenon drivers however are polling drivers, thus only a general problem in the communication
can be indicated (and not a separate one for each variable).
In the event of a fault in the communication, the status bits INVALID and SPONT exclude each other
mutually. However, both bits can be set at the same time for the following exceptions:
Protocol-dependent
In some spontaneous protocols, the controllers have the possibility of marking a value as
invalid, such as IEC 60870 indicator INV, IEC 61850 Quality. Values marked as such then get
the INVALID bit, possibly at the same time as with SPONT. You can find details in the
corresponding driver documentation.
Driver monitoring by Runtime
Runtime monitors the availability of the driver by means of a watchdog. This monitoring is
not applicable for internal drivers. If a driver is no longer available, the INVALID status bit is
also set by Runtime. You can find details in the corresponding driver documentation.
15 | 34
Status bits
Information
The status bit is shown in the Runtime with a red square in the top right corner
of the screen element.
The display can be amended individually using the properties in the zenon
Editor:
Representation/Display status of variable element property: Activates or
deactivates the display.
Status of variable/Communication failure to PLC project property:
Enables the color of the display to be amended.
This status indicates whether the time stamp received by the controller is in winter time (bit set) or in
summer time (bit not set).
This status can occur together with the status T_EXTERN (on page 17).
Note: Please also note the status T_STD (on page 22) for the internal time stamp.
Attention
Note: up to version 7.50, this status bit had a different meaning (old
identification: T_CHG_A)
16 | 34
Status bits
If a variable is not needed online, it can be switched off. So it is no longer read from the hardware
and no longer updated.
This state can e.g. be used to exclude not yet active parts of the process from the alarm handling.
Information
The status bit is shown in the Runtime with a red square in the top right corner
of the screen element.
The display can be amended individually using the properties in the zenon
Editor:
Representation/Display status of variable element property: Activates or
deactivates the display.
Status of variable/Communication failure to PLC project property:
Enables the color of the display to be amended.
The time stamp was supplied by an external device. zenon takes this time value as it is. All zenon
modules use this time stamp.
17 | 34
Status bits
Attention
The status of a variable can be either T_EXTERN or T_INTERN.
If a value has the status T_EXTERN and no T_INVAL, the value of the the
external time stamp is used as a time stamp.
The external time stamp is the time value that the controller has provided
together with the value at the driver.
If a value has the status T_INTERN or has T_EXTERN and T_INVAL,, the value
of the internal time stamp is used as a time stamp.
The internal time stamp is the time point at which the driver has received
the value from the controller.
The time stamp is issued by the zenon driver. As soon as the value is read correctly, it is stamped. All
modules use this time stamp.
Attention
The status of a variable can be either T_EXTERN or T_INTERN.
If a value has the status T_EXTERN and no T_INVAL, the value of the the
external time stamp is used as a time stamp.
The external time stamp is the time value that the controller has provided
together with the value at the driver.
If a value has the status T_INTERN or has T_EXTERN and T_INVAL,, the value
of the internal time stamp is used as a time stamp.
The internal time stamp is the time point at which the driver has received
the value from the controller.
Note: The internal time stamp of variable values supports the full resolution of microseconds (µs).
18 | 34
Status bits
Concerns real-time data flow at the SSI protocol. SSI is used for SK1703 and concerns the AK driver.
Originally: If a telegram arrived much too late, it receives the status N_SORTAB if it could not be
sorted in. As now there is a secondary sorting, the state has no meaning anymore.
Only for SSI protocol: Implausibel transformer value. IN newer protocols this information is
transported via INVALID (on page 15) bit.
Information
The status bit is shown in the Runtime with a red square in the top right corner
of the screen element.
Concerns SSI protocol and IEC870-101: As long as it is stepped this BIT comes along.
19 | 34
Status bits
No longer used.
To substitute a value, it can be switched to the alternative value. At this the value is completely
uncoupled from the process as with Switched off (OFF) (on page 16). Similar to Switch off the last
process value is displayed. There is however the possibility to change the alternate value in the
Runtime; e.g. via the set value dialog
Modify substitute value:
Only changes the alternate value
Switch to and modify alternate value:
Switches to alternate value and changes it to the set value.
Modify spontaneous value:
A set value is sent to the hardware despite an alternate value. The variable however retains
the alternate value.
Switch to spontaneous value:
Switches off the alternate value.
If no value was transferred, the defined alternate value is used otherwise the last valid value is used.
There are further possibilities to affect the alternate value in command processing, via the
Recipegroup Manager or the programming interfaces.
If at the time of the switching to the alternate value the state was invalid (INVALID (on page 15)), the
state remains. The value has the state invalid and alternate value set.
The alternate value is not sent to the connected hardware, but stays in the process image on the
computer. This value is sent to all modules of zenon and further processed there. So it is for example
archived and alarms are created.
Using this state information these values can especially be marked in the report. So on the one hand
the changes are traceable, on the other hand the further processing works with correct values.
20 | 34
Status bits
Example
If an outside temperature sensor is defective, it may send an unrealistic value,
e.g. -280°C. Now the user can enter the correct value instead of the defective
value by reading the temperature, e.g. 14°C. Now this value is archived, alarmed
and logged.
Information
The status bit is shown in the Runtime with a red square in the top right corner
of the screen element.
The display can be amended individually using the properties in the zenon
Editor:
Representation/Display status of variable element property: Activates or
deactivates the display.
Status of variable/Communication failure to PLC project property:
Enables the color of the display to be amended.
In the zenon network, the status bit is set if the network client loses the connection to the Primary
Server or if the variable has the Only read from Standby Server property but the Standby Server is
not available.
21 | 34
Status bits
Information
This status bit is shown in the Runtime with a blue square in the top right corner
of the screen element.
The display can be amended individually using the properties in the zenon
Editor:
Representation/Display status of variable element property: Activates or
deactivates the display.
Status of variable/Communication failure to server project property:
Enables the color of the display to be amended.
INTEGRATION PROJECT
The integration project is a special case. An integration project can be a standalone project that does
however contain network projects.
As a result, the integration project becomes the client for subprojects. In this case, the blue dot
indicates that the primary server of the subproject has not yet supplied the data.
ADDITIONAL INFORMATION
The following applies for some drivers: The status Not updated (N_UPDATE) is set if a value has been
requested from the hardware, but no valid value could be read.
This status indicates whether the time stamp is in winter time (bit set) or in summer time (bit not set).
Note: Please also note the status T_STD_E (on page 16) for the external time stamp.
22 | 34
Status bits
The value of the Cause of Transmission (see IEC60870-5-101 7.2.3) is mapped to status bits 32 - 37. Up
to 6 COTx bits can thus be set (x represents bit numbers 0 to 5).
For example: the lowest bit of the COT value is shunted to status bit 32 and named COT0 in zenon.
The complete COT value can be evaluated in the Runtime via a reaction matrix (multi-numeric or
multi-binary). For each COTx bit the value of the cause of transmission is increased as follows:
COT0 = 2^0 = 1
COT1 = 2^1 = 2
COT2 = 2^2 = 4
COT3 = 2^3 = 8
COT4 = 2^4 = 16
COT5 = 2^5 = 32
EXAMPLE
Typical COT values:
Status Value Cause of transmission Short name
23 | 34
Status bits
Information
The Command Processing module uses the following for watchdog timer of
commands:
COTx
N_CONF
SE_870 Status
Note:
Some Energy drivers support COTx status bits, although the protocol itself
does not contain COT (e.g. DNP3, IEC850).
Some Energy drivers only support an area restricted to the Runtime
monitoring in Command Processing.
Signalizes that the controller has confirmed the command as negative. Corresponds to the P/N bit
(positive/negative response) in the IEC 60870 protocol. During the command in the IEC 61850 too, the
negative confirmations of the Select and Operate command are allocated to the N_CONF status bit.
Applies together with COTx: COT_actcon(7), COT_actterm(10).
Info
The Command Processing module uses the following for watchdog timer of
commands:
COTx
N_CONF
SE_870 Status
24 | 34
Status bits
Signalizes the Test status in accordance with the IEC 60870 standard or in accordance with IEC 61850:
Quality=Test. This status bit can be evaluated in the Combined element and in the Interlocking
formula. The evaluation of the reaction matrix is available as a multi-binary or multi-numeric reaction
matrix.
Is used by the zenon functions Write set value or Write recipe to request a write confirmation from
the driver.
Note: You can find more detailed information in the Variables manual in the Checking writing of set
values chapter.
If, for a Set value or Execute recipe action, a writing confirmation should be requested (WR-ACK (on
page 25)), this status bit is set accordingly after writing.
Note: You can find more detailed information in the Variables manual in the Checking writing of set
values chapter.
The normal status is defined in the variable properties and evaluated in the status bit NORM.
25 | 34
Status bits
For bit variables the driver compares the process status with the defined normal status and writes the
result to the status bit N_NORM.
Signalizes Blockedstatus in accordance with the IEC 60870 standard or in accordance with IEC 61850:
Quality=OperatorBlocked. The controller reports that the value is blocked for transfer and remains in
the status it had before it was blocked. This status bit can be selected in Multi reaction matrices, in
Combined elements and in the Interlocking formula.
In VBA the top 32 bits can be polled with StatusExtValue(). With SetValueWithStatusEx() all 64 status bits can
be polled.
Signalizes Substituted status in accordance with the IEC 60870 standard or in accordance with IEC
61850: Quality.Source=Substituted. The controller reports that the value no longer comes from
hardware but was simulated in the controller. This status bit can be selected in Multi reaction matrices,
in Combined elements and in the Interlocking formula.
In VBA the top 32 bits can be polled with StatusExtValue(). With SetValueWithStatusEx() all 64 status bits can
be polled.
26 | 34
Status bits
Signalizes Not topical status in accordance with IEC 60870 standard. The controller reports that the
value was not updated on the hardware for a certain period of time or is not available. This status bit
can be selected in Multi reaction matrices, in Combined elements and in the Interlocking formula.
In VBA the top 32 bits can be polled with StatusExtValue(). With SetValueWithStatusEx() all 64 status bits can
be polled.
Signalizes Overflow status in accordance with the IEC 60870 standard or in accordance with IEC
61850: Quality=Overflow. The controller reports that the value is outside the predefined bandwidth or
that there is a counter overrun. This status bit can be selected in Multi reaction matrices, in Combined
elements and in the Interlocking formula.
The bit is used in energy protocols in conjunction with the Select before operate function and serves
to make a distinction between the Select- and Execute/Operate-step of a command. Applies together
with COTx: COT_act(6), COT_actcon(7).
Values:
0 = execute
1 = select
Info
The Command Processing module uses the following for watchdog timer of
commands:
COTx
N_CONF
SE_870 Status
27 | 34
Status bits
The invalid time status is set by a driver if the real-time stamp received by the controller is marked as
invalid. In this case, the zenon modules use the received value of the variable with the local time
stamp of the computer. This status bit can be selected in Multi reaction matrices, in Combined
elements and in the Interlocking formula.
Attention
The status of a variable can be either T_EXTERN or T_INTERN.
If a value has the status T_EXTERN and no T_INVAL, the value of the the
external time stamp is used as a time stamp.
The external time stamp is the time value that the controller has provided
together with the value at the driver.
If a value has the status T_INTERN or has T_EXTERN and T_INVAL,, the value
of the internal time stamp is used as a time stamp.
The internal time stamp is the time point at which the driver has received
the value from the controller.
The status bit takes the value 1 if breaker tripping detection has been activated in the Command
processing module and breaker tripping is detected.
28 | 34
Status bits
A change to the value of the variable from 0 to <>0 resets this bit again. This bit is also reset if the
PROGRESS (on page 13) status bit (10) is active. A change to CB_TR_I (on page 29) does not have an
influence on a breaker trip that has already been detected.
This status bit can be explicitly modified with the "Status", "Status on" or "Status off" action in the
command processing. The status bit contains this status up until the value of the variable switches
from <>0 to 0 or from 0 to <>0. A requirement for this is that the CB_TR_I status bit is 0. This means
that breaker tripping detection is not suppressed.
NETWORK
In the network the evaluation is carried out on the server which is responsible for the process. The
evaluation is indeed also carried out on the Standby Server but the result is not written to the status
bits. The current state of CB_TR_I and CB_TRIP are synchronized when the Standby Server is started or
reconnected. If the response variable is a variable on a local computer, the evaluation is also carried
out on the client computer.
Shows that breaker tripping detection is suppressed in command processing for the variable.
The new calculation is triggered in the event of a status change or value change of a variable if this
has been defined in the command processing for calculations in formulas. The formula is not
evaluated and the result is not written to the status if:
one of the variables in the formula does not have a defined value and status yet
or
one of the variables is invalid (INVALID).
This status bit can be explicitly modified with the "Status", "Status on" or "Status off" action in the
command processing. The status bit will then remain in this state until the result of the formula
changes and a different status bit status occurs as a result.
29 | 34
Status bits
Attention: The detection of a breaker tripping (CB_TRIP) and the setting breaker tripping detection
inactive at the same time does not work.
Example: The "RM.Value<1" will detect breaker tripping (CB_TRIP = 1), because CB_TR_I is not yet
active at the time of the value change.
NETWORK
In the network the evaluation is carried out on the server which is responsible for the process. The
evaluation is indeed also carried out on the Standby Server but the result is not written to the status
bits. The current state of CB_TR_I and CB_TRIP are synchronized when the Standby Server is started or
reconnected. If the response variable is a variable on a local computer, the evaluation is also carried
out on the client computer.
Signalizes Out of Range in accordance with the IEC 61850 standard, corresponds to
Quality=OutofRange. The controller reports that the value is outside of the predefined measurement
range. This status bit can be selected in the Combined element and in the Interlocking formula.
Information
You can find further information about this in the documentation for the IEC850
driver in the Quality, time stamp and status bits of the variable chapter.
30 | 34
Status bits
This status bit shows in the Runtime that the variable has not been recorded during playback in the
Process Recorder. No value is therefore known in the playback.
Information
This status bit is shown in the Runtime with a yellow square in the top right
corner of the screen element.
The display of this yellow square is treated as a higher priority than the other
status displays (red or blue).
The display can be amended individually using the properties in the zenon
Editor:
Representation/Display status of variable element property: Activates or
deactivates the display.
Status of variableUnknown value in Process Recorder project property/:
Enables the color of the display to be amended.
WRITE PROTECTION
This bit is only issued by the Process Recorder. Because the bit is for the identification of
non-recorded variables during playback, the bit must not be set the other way.
31 | 34
Usage
The external and internal timestamps are compared in Runtime. If the deviation is greater than the
configured value, the status bit is set. The value is configured in the property Timestamp Deviation
for the tag or data type in the property group Value calculation.
The status bit can then be evaluated in a multi-binary or multi-numeric reaction matrix. In Runtime,
the calculated time difference can be displayed in a screen from type Alarm Message List Filter or
Chronological Event List Filter in the Time difference column. Note that this column is hidden by
default.
4 Usage
Here single statuses can be evaluated and cause alarms. Basically a status can be treated like a value.
As with a value it is also possible with a status to cause certain actions.
As for example:
Generate alarm
Generate entry in CEL
Execute function
Flashing
Color change
Print
Example:
If a value becomes invalid, it gets the state INVALID (on page 15). This happens when the driver loses
the connection to the PLC. You can create a reaction matrix, which causes an alarm, as soon as the
value becomes invalid (INVALID). There is the possibility to evaluate these alarms afterwards.
32 | 34
Usage
It is then possible to display the status in the Runtime with the right mouse key.
In the Runtime the status is displayed by clicking the dynamic element with the right mouse key. As
long as the mouse button stays pressed down, the variable name and the current status of the
variable is displayed.
If the status display is activated, some states are are shown in the top right corner of the element by a
small colored rectangle, such as red for INVALID or ALT_VAL:
This indicates, that the value no longer is spontaneous. By clicking the element with the right mouse
key it becomes obvious, that somebody changed the status to the alternative value.
This means:
1 The color changes
33 | 34
Usage
This is done by using the function variabler with the status as a parameter.
=variabler(Temperature_outside,status)
4.6 VBA
In VBA there are all possibilities to access and change all stati, as long as they are not set by the
process (driver).
34 | 34