User Manual

Siemens Building Technologies CM2N8889E / 10.1999
Landis & Staefa Division 3/4
Both the BPS and its partners can be the initiating party:
•
The BPS can call up the defined partners
•
The defined partners can call up the BPS (exception: teleprinter)
Communication is triggered automatically or manually through:
– Events in the configured data points such as error status changes
– COLBAS task outputs
– Operating command DUS
If both partners in a VISONIK BPS are defined as the receiver of a message, the
following sequence applies:
1. Connection to partner 1
2. Connection to partner 2
The following table contains a list of data types the BPS and its partners can exchange:
Type of data Interpretation
BPS event data If requested by the BPS, its own DCS queries the events
(EACQ). In this case, it adopts the dynamic point information of
the BPS such as main values (changed, incl. alarms) operating
hours, etc..
BPS process
image
If requested by the BPS, its own DCS runs a general query
(GACQ). In this case, it adopts all point information of the
respective BPS.
BPS message
buffer
If requested by the BPS, the associated DCS reads its own
message buffer (MACQ). This buffer contains fault messages of
points, operating hours, temperature values, etc..
BPS data
processing buffer
If requested by the BPS (DACQ), the associated DCS reads its
own data processing buffer (storage of values (MACQ). This
buffer contains the value strings of the defined data points
acquired as per the acquisition profile.
Text transfer When communication is initiated, the BPS sends clear texts to
the partner via @pnt.TXC. For example:
"Filter change required – call 6329"
Point reports When communication is initiated, the BPS sends a point report
to the partner via PROT @pnt.TA. For example:
ML $d098'020 ( 1.2 2d20 )
18.01.96 12:11:03 DI=0 DI=EST
Manual operation After establishing connection and entering command DUS, the
BPS can exchange manual operating data with all devices.
Exceptions: Teleprinter, pager.
Not all of the above data types can be exchanged with every partner:
•
Event queries EACQ and general queries GACQ of the BPS are executed only by its
own
DCS (partner 1). This ensures that no information is lost to unauthorised
partners during transfer.
•
MACQ and DACQ are possible only with a DCS (partners 1 and 2).
Transfer and
transfer contents
Initiating party and
communication trigger
Calling sequence
Transfer contents
Important!