Product specifications

SPlus Operations P13 Connectivity Guide PROCONTROL P13 OPC SERVER
2VAA001153C 65
S_XDESCRIPTION
Object type specific error
code
Short
S_XDESCR
IPTION
x
x
x
DistWord
Station Disturbance Word
Short
.DistWord
x
Message Rate
Number of telegram
messages per second
provided by the PIF
Short
.MsgRate
x
The object-specific error codes are described in the following tables:
Table 3-44: Error codes for BUS object
Error Code
(S_XDESCRIPTION)
Meaning
S_STATUS
0
OK
0
1
PIF not running
1
2
No channel active
1
3
Channel A not active
0
4
Channel B not active
0
Table 3-45: Error codes for LINE object
Error Code
(S_XDESCRIPTION)
Meaning
S_STATUS
0
OK
0
1
Communication disturbed
1
Table 3-46: Error codes for STATION object
Error Code
(S_XDESCRIPTION)
Meaning
S_STATUS
0
OK
0
1
Station not reachable
1
2
Station has disturbance
1
3
Disturbance word invalid
1
4
Not monitored
254
3.7.5.2 System Alarms
3.7.5.2.1 System Alarms for Bus and Line
Communication failures to an intraplant bus or serial line are reported as alarms with event category System Event.
Figure 3-49: Example of bus alarms in an OPC alarm & event client
3.8 Redundancy Support
3.8.1 Acknowledge Synchronization
OPC Alarm&Event Servers maintain a list of active unacknowledged alarms. In configurations with redundant OPC
 the same.
If the client application in a redundant configuration does send an acknowledge signal only to one server, the exchange
of acknowledge information must take place between the OPC Servers.
The exchange of acknowledge information can be activated by defining corresponding partner servers.