25
COM465IP-COM465DP_D00216_02_M_XXEN/03.2017
5. PROFIBUS DP (COM465DP only)
5.1 PROFIBUS DP side of the COMTRAXX® COM465DP
The gateway and its PROFIBUS address are to be made known to the PROFIBUS master. For this pur-
pose you will need the file BEND0F27.gsd (see "Scope of delivery" on page 13)
A connection from Bender systems with BMS bus and BCOM to PROFIBUS DP using COM465DP can
be necessary for various reasons:
A PROFIBUS DP device is to react to an event in the BMS world
A BMS bus device is to react to an event in the PROFIBUS DP world
The data on the BMS bus are to be displayed, evaluated or depicted together with PROFIBUS DP
data on a PC with PROFIBUS DP software
The data on the BMS bus are to be displayed in the software for a building services manage-
ment system that has a PROFIBUS DP interface
The devices on the BMS side are to be configured via a PC with PROFIBUS DP interface
Certain actions on the BMS side are to be controlled via PROFIBUS DP.
The COM465DP is a PROFIBUS DP slave as per IEC 61158/IEC 61784. This means that there must al-
ways be at least one master on the PROFIBUS side.
COM465DP = PROFIBUS DP V0 slave
PROFIBUS DP address = 1…125 (factory setting: 3)
Data transmission rate = 9.6 kbit/s to 1.5 Mbit/s, the baud rate is detected automatically
5.1.1 Cyclic data exchange
In this manual the Profibus is considered in principle from the point of view of a PROFIBUS DP master.
The communication on the PROFIBUS DP is cyclic. During this process the PROFIBUS master polls all
PROFIBUS slaves in sequence using a query-and-response sequence.
A query is represented by the output data from the master. The COM465DP then responds to the
master. The response is represented by the input data to the master.
Due to the large amount of data on the BMS side, all these data cannot be transferred simultaneously
during the cyclic exchange of data. The PROFIBUS master must therefore define precisely which data
it wants to receive from the BMS device.
The assignment between input data and output data, that is between request and response, is de-
fined via an ID no. The PROFIBUS DP programmer must ensure the next ID no. is output as soon as
the previous request has been answered.
COM465DP is always operated as a slave in the PROFIBUS DP side.