Product specifications
SPlus Operations P13 Connectivity Guide PROCONTROL P13 OPC SERVER
2VAA001153C 37
Example:
APPEND, C:\OPC_P13\Data\BOP.pve
3.3.3.4.5 SERVER Instruction
The SERVER instruction allows to target the parameters sets to a certain server only. This can be useful for example for
redundant configurations, where the parameters which have to be different (e.g. VPC ID-bit naming) on the redundant
servers can be targeted to only one server, nevertheless the engineering files can be kept identical for both servers.
Examples:
SERVER, 2
This instruction causes all parameter sets following to be targeted to the server with Server ID = 2 only.
SERVER
This instruction causes all parameter sets following to be targeted to any server independent from the Server ID.
3.3.3.4.6 TELEGRAMERRORS Instruction
The TELEGRAMERRORS instructions allow to activate logging of telegram errors on P42 bus connected via PIF. For
normal data acquisition, the PIF does suppress sporadic single errors (e.g. data word errors are ignored if not occurring
for four successive bus cycles).
If telegram error logging is activated each single address or data error is reported as event message.
The following options are provided:
A: Address error logging
D: Data error logging
N: No telegram error logging (default)
Examples:
TELEGRAMERRORS,A,D
Telegram errors of type A and D are logged.
TELEGRAMERRORS,N
Telegram error logging is switched off.
Remark:
Telegram error logging can be activated or switched off for a running OPC server by means of loading an appropriate
pve-file (only containing a corresponding TELEGRAMERRORS instruction) through the command Load PVs… .
3.3.3.4.7 STATUSERRORS Instruction
The STATUSERRORS instructions allows to activate logging of status errors of data words on P42 bus connected via
PIF. Status error logging does only log data errors passing the error filtering functions of the PIF, i.e. errors which also
invalidate corresponding PVs connected to the data word.
The following options are provided:
A: Address error logging
D: Data error logging
T: Sensor disturbance logging
N: No status error logging (default)
Examples:
STATUSERRORS,A,D,T
Status errors of type A ,D and T are logged.
STATUSERRORS,N
Status error logging is switched off.
Remark:
Status error logging can be activated or switched off for a running OPC server by means of loading an appropriate pve-
file (only containing a corresponding STATUSERRORS instruction) through the command Load PVs… .
3.3.3.4.8 PRIORITYMAP Instruction
The PRIORITYMAP defines mapping of priorities to severities. In the engineering data a priority attribute can be defined
for limits and digital values. The alarm and event OPC server provides severities instead of priorities. For the default
priority-severity mapping see 3.5.1.23.5.1.2