Product specifications

SPlus Operations P13 Connectivity Guide PROCONTROL P13 OPC SERVER
48 2VAA001153C
3.4.4.4 PServerAdmin_ActiveBuses, PServerAdmin_ActiveBusesPrtn OPC Item
The PserverAdmin_ ActiveBuses provides the number active buses. The PserverAdmin_ ActiveBusesPrtn provides the
number active buses of the partner server. These items are only available if extended partnernode communication is
configured.
3.4.5 Support for XC80-Telegram
3.4.5.1 General
The P13 control functions corresponding to the PServer control objects provide their state information for the control
room via the so-called XC80-telegram. The XC80 telegram provides information on the position and mode of the object
as also on its disturbances states. This information is represented by corresponding bits in the 16 bit word telegram.
In older P13 plants, not the whole XC80- telegram was available to the HMI for state annunciation but only a subset of
the bits in the XC80-telgram indicating the position and mode information. These bits are then provided as binary input
signals (DIs) with signal code XLxx. The reason for this approach was either to reduce the amount of signals in the HMI
database or to reduce the amount of signals on the P13 buses or both. In some of these plants, the XC80 telegram for a
control object can be requested via a corresponding command on a single multiplexed address. This function is called
DMS.
In newer P13 plants and also some of the older ones, the XC80 telegram would be available for the HMI. This means,
additional disturbance information can be provided without the DMS function. Providing the XC80 telegram via OPC has
the following advantages
 Disturbance information without needing DMS
 Less OPC items to be subscribed -> better performance
 Less DI signals to be loaded, in particular less objects counting for 800xA License
17
Generated XC80-Telgram
In cases, in which the XC80-Telegram is not provided, the PServer can put together the available part of the XC80-
Telegram from the available feedback signals to a generated XC80-Telegram. This allows providing to clients an
interface to the control objects feedback information independent from whether this information is provided as individual
signals or as a telegram.
3.4.5.2 Configuration of XC80 - Telegram
3.4.5.2.1 XC80DEF Instruction
This instruction allows defining the mode for the XC80 acquisition and in case of XC80 provided from bus a
corresponding address reference.
XC80DEF, <Mode>,[<AddrRefs>],[XC80Option]
Where:
Mode: Bus: Telegram provided by bus
Generate: Generate telegram based on feedback signals
AddrRefs:         
address. Address will be taken from the first signal found.
Default: &_XL68/&_XL18/&_XL19
This means, if, for a control object, a corresponding signal is found with one of these signal
codes, the XC80 address is take from this signal.
XC80Option: NoXL
18
: Load only XL signals with events.
Examples:
XC80DEF,Bus,&_XL68/&_XL18
XC80 telegram is provided by bus, the address is provided by XL68.
XC80DEF,Generate
XC80 telegram is generated based on available feedback signals
3.4.5.3 Object Individual XC80 Configuration
For control objects whose XC80 configuration differs from that defined with the XC80DEF instruction, an individual
configuration can be made in the XC80 field in the control object configuration record.
17
DIs used for events (e.g. XL68) have to be loaded also when using XC80.
18
This parameter is not observed by the OPC server but controls the pve-generation in the engineering workbook !