Connection to construction-side central control systems

Transcription

1 1 General Information Often, boiler are a component part of complex (e.g. process, power stations, building complexes, etc.), which possess higher-level command. Depending on requirements, various transmission types (bus, networks) and connection structures are used for signal transmission to the command. The standard boiler system delivery can contain the transmission type PROFIBUS-DP, ETHERNET, MODBUS-RTU, MODBUS-TCP, OPC UA, BACnet or PROFINET IO depending on the selected option. The data can be transmitted on the one hand via communication processors or gateways and the other hand via MEC Optimize (MEC... Master Energy Control). 2 Transmission types The following section(s) describe(s) the presettings, information and data required for processing orders of the selected transmission types. Note: Order-related data (measured values, operating signals, fault messages, possibly external requests, etc.) is documented in a parameter list and a datapoint list, which is located in the control cabinet. An advance delivery of the parameter list or datapoint list is available on request by agreement with the responsible project officer. 2.1 PROFIBUS-DP The boiler system can be connected via PROFIBUS-DP either via the CP342-5 or an X-gateway Profibus DP slave, depending on the control hardware used. See the order-related wiring diagram for the connection that is used. Presettings: Communications processor X-Gateway Profibus DP Slave / CP342-5 Medium steam: DP-address Medium water: DP-address BCO boiler BCO boiler BCO boiler BCO boiler SCO 9 7 CCO 10 - Mode of operation DP-Slave, passive Baud rate 1,5 MBit/s Bus profile Standard Highest PROFIBUS - address 126 GSD file X-Gateway hms-gsd-abx-pdps.zip GSD file CP342-5 SI0180D6.GSD During the bus profile attitude "standard" is considered there is no net and line. DP addresses are only used and assigned when the appropriate control cabinets are part of the standard delivery. The assignments of the DP addresses to the control cabinet numbers and manufacturer numbers are documented in the order-related parameter list, which is supplied with the control cabinet. The GSD file of the communications processor is available on the Internet: (English website) (German website) 1

2 A CP is used as the station type. The GSD files for the gateway and the communication processor are available on the Internet: X-Gateway: CP342-5: (englische Webseite / English website) CP342-5: (deutsche Webseite / German website) Bus parameter: Designation Value Tslot Init 300 t_bit Max.Tsdr 150 t_bit Min. Tsdr 11 t_bit Tset 1 t_bit Tqui 0 t_bit Gap - Factor 10 Retry Limit 1 Tslot 300 t_bit Tid2 150 t_bit Trdy 11 t_bit Tid1 37 t_bit Ttr t_bit (=14.9 ms) Ttr typically 1129 t_bit (=0.8 ms) Watchdog t_bit (=44.4 ms) Note: Order-related data (measured values, operating signals, fault messages, possibly external requests, etc.) is documented in a parameter list and a datapoint list, which is located in the control cabinet. An advance delivery of the parameter list or datapoint list is available on request by agreement with the responsible project officer. 2.2 INDUSTRIAL ETHERNET An Industrial Ethernet connection to the central command system can be made using various protocols and connections. The offer or order confirmation lists which protocol is planned for the project / order. The default presettings and necessary information for order processing are summarised below for the various protocols. Note: Please contact the responsible project officer for special protocols or special settings not contained in the list below. The boiler system can be connected via INDUSTRIAL ETHERNET either via the CP343-1 or the CP1543-1, depending on the control hardware used. See the order-related wiring diagram for the connection that is used Passive connection (as Server) with application protocol S7 communication via TCP/IP, e.g. from on-site OPC server IP addresses are only used and assigned when the appropriate control cabinets are part of the standard delivery. The IP addresses, subnet mask and router address can be changed on the operating panel. If different values (IP addresses, subnet mask and router address) to the presettings are to be set at the factory, then this must be indicated to the responsible project officer at the latest 10 working days after the order confirmation arrives. The assignments of the IP addresses to the control cabinet numbers and manufacturer numbers are documented in the order-related parameter list, which is supplied with the control cabinet. 2

3 Presettings: Communications processor CP343-1 / CP Medium steam: IP-address Medium water: IP-address BCO boiler BCO boiler BCO boiler BCO boiler SCO CCO Subnetmask Router ---- Communication: Transport protocol TCP/IP Mode passive, Server operation one direction, no SEND-Requests Application protocol S7 Industrial Ethernet CPU-Parameter (Slot; Rack) 2; 0 2 x RJ45, 2-port-switch integrated Properties 10/100MBaud, Full/Half Duplex, Autosensing/Autonegotiation, Autocrossover Note: Order-related data (measured values, operating signals, fault messages, possibly external requests, etc.) is documented in a parameter list and a datapoint list, which is located in the control cabinet. An advance delivery of the parameter list or datapoint list is available on request by agreement with the responsible project officer Passive connection (as Server) with application protocol S7 communication via ISO transport connection (H1), e.g. from on-site OPC server MAC addresses are only used and assigned when the appropriate control cabinets are part of the standard delivery. MAC addresses are preset by the manufacturer of the communication processor. If different MAC addresses to the presettings are to be set at the factory, then this must be indicated to the responsible project officer at the latest 10 working days after the order confirmation arrives. The assignments of the MAC addresses to the control cabinet numbers and manufacturer numbers are documented in the order-related parameter list, which is supplied with the control cabinet. Presettings: Communications processor MAC-Address: BCO boiler 1 BCO boiler 2 BCO boiler 3 BCO boiler 4 SCO CCO Communication: Transport protocol Mode Application protocol CP343-1 / CP ISO (H1) passive, Server operation one direction no SEND-Requests S7 3

4 Industrial Ethernet CPU-Parameter (Slot; Rack) 2; 0 2 x RJ45, 2-port-switch integrated Properties 10/100MBaud, Full/Half Duplex, Autosensing/Autonegotiation, Autocrossover Note: Order-related data (measured values, operating signals, fault messages, possibly external requests, etc.) is documented in a parameter list and a datapoint list, which is located in the control cabinet. An advance delivery of the parameter list or datapoint list is available on request by agreement with the responsible project officer Passive connection with application protocol AG_SEND/AG_RECEIVE via ISO transport connection (H1) MAC addresses are only used and assigned when the appropriate control cabinets are part of the standard delivery. MAC addresses are preset by the manufacturer of the communication processor. If different MAC addresses to the presettings are to be set at the factory, then this must be indicated to the responsible project officer at the latest 10 working days after the order confirmation arrives. The assignments of the MAC addresses to the control cabinet numbers and manufacturer numbers are documented in the order-related parameter list, which is supplied with the control cabinet. Presettings: Communications processor CP343-1 / CP MAC-Address: BCO boiler 1 BCO boiler 2 BCO boiler 3 BCO boiler 4 SCO CCO TSAP: (local LSAP) BCO boiler 1 _BCO BCO boiler 2 _BCO BCO boiler 3 _BCO BCO boiler 4 _BCO SCO _SCO CCO _CCO Communication: Transport protocol ISO (H1) Mode passive connection launch, unspecified connection Application protocol AG_SEND/AG_RECEIVE Industrial Ethernet CPU-Parameter (Slot; Rack) 2; 0 2 x RJ45, 2-port-switch integrated Properties 10/100MBaud, Full/Half Duplex, Autosensing/Autonegotiation, Autocrossover Note: Order-related data (measured values, operating signals, fault messages, possibly external requests, etc.) is documented in a parameter list and a datapoint list, which is located in the control cabinet. An advance delivery of the parameter list or datapoint list is available on request by agreement with the responsible project officer. 4

5 2.2.4 Passive connection with application protocol AG_SEND/AG_RECEIVE via ISO-ON-TCP connection (RFC1006) IP addresses are only used and assigned when the appropriate control cabinets are part of the standard delivery. If different values (IP addresses, subnet mask and router address) to the presettings are to be set at the factory, then this must be indicated to the responsible project officer at the latest 10 working days after the order confirmation arrives. The assignments of the IP addresses to the control cabinet numbers and manufacturer numbers are documented in the order-related parameter list, which is supplied with the control cabinet. Presettings: Communications processor CP343-1 / CP Medium steam: IP-address Medium water: IP-address BCO boiler BCO boiler BCO boiler BCO boiler SCO CCO Subnetmask Router ---- TSAP: (local LSAP) BCO boiler 1 _BCO BCO boiler 2 _BCO BCO boiler 3 _BCO BCO boiler 4 _BCO SCO _SCO CCO _CCO Communication: Transport protocol ISO_ON_TCP (RFC1006) Mode passive connection launch, unspecified connection Application protocol AG_SEND/AG_RECEIVE Industrial Ethernet CPU-Parameter (Slot; Rack) 2; 0 2 x RJ45, 2-port-switch integrated Properties 10/100MBaud, Full/Half Duplex, Autosensing/Autonegotiation, Autocrossover Note: Order-related data (measured values, operating signals, fault messages, possibly external requests, etc.) is documented in a parameter list and a datapoint list, which is located in the control cabinet. An advance delivery of the parameter list or datapoint list is available on request by agreement with the responsible project officer. 2.3 MODBUS-RTU Modbus addresses are only used and assigned when the appropriate control cabinets are part of the standard delivery. The assignments of the Modbus addresses to the control cabinet numbers and manufacturer numbers are documented in the order-related parameter list, which is supplied with the control cabinet. 5

6 Presettings: Communications processor X-Gateway Modbus-RTU Slave Medium steam: Modbus-RTU-address Medium water: Modbus-RTU-address BCO boiler BCO boiler BCO boiler BCO boiler SCO 9 7 CCO 10 - Mode of operation Modbus-RTU-Slave RS485 (2-wire-operation, preadjusted), RS232 9 pin SUB-D female connector Baud rate 9,6kBaud Parity even Stop-Bit(s) 1 Note: Order-related data (measured values, operating signals, fault messages, possibly external requests, etc.) is documented in a parameter list and a datapoint list, which is located in the control cabinet. An advance delivery of the parameter list or datapoint list is available on request by agreement with the responsible project officer Data query, Function Codes The Modbus RTU Slave works as a passive node and processes queries to read or write data coming from the Master. The queries are encoded in the form of function calls (Function Codes, Function Calls). The Slave does not initiate communication to the Master automatically. Individual states (Coils) can be read or written in by bit or registers by words. The following Function Codes are supported: MODBUS function Function Code Direction Read Coil / Read individual bit 1 Slave--> Master Read Input Register / Read dataword 4 Slave --> Master Write Coil / Write individual bit 5 Master --> Slave Write Single Register / Write dataword 6 Master --> Slave Coils and registers The Input and Output buffers are structured according to the following pattern: Note: Coils are counted from the direction of the MSB, e.g. Coil 1 corresponds to Bit 16 of Register 1. 6

7 Register# Coil# Buffer Storage location in the buffer Comment Input Buffer h Available Modbus h functions: h - Read Coil (FC1) h - Read Input Register (FC4) h A...00Bh C...00Dh FC...1FDh FE...1FFh Reserved Output Buffer h Available Modbus h functions: h - Write Coil (FC5) h - Write Single Register (FC6) h A...00Bh C...00Dh FC...1FDh FE...1FFh Reserved Note: The order-related assignment of the datapoints to the registers and coils (measured values, operating signals, fault messages, possibly external requests, etc.) is carried out when the control cabinet is delivered (datapoint list located in the control cabinet). An advance delivery of the datapoint list is available on request by agreement with the responsible project officer. 2.4 Modbus TCP (via communication processor) IP addresses are only used and assigned when the appropriate control cabinets are part of the standard delivery. The IP address can be changed at the gateway. If other values (IP addresses, subnet mask and router address) are to be set at the factory as pre-settings, then these must be notified to the project manager within 10 working days at the latest after the order confirmation has arrived. The assignments of the IP addresses to the control cabinet numbers and manufacturer numbers are documented in the order-related parameter list, which is supplied with the control cabinet. 7

8 Communications processor X-Gateway Modbus-TCP Slave IP-Address: BCO boiler BCO boiler BCO boiler BCO boiler SCO CCO Subnetmask Router ---- Communication: Transport protocol TCP/IP Mode Slave Application protocol Modbus TCP Industrial Ethernet CPU-Parameter (Slot; Rack) 2 x RJ45, 2-port-switch integrated Properties 10/100Mbit/s, Full Duplex, Autosensing/Autonegotiation, Autocrossover Note: Order-related data (measured values, operating signals, fault messages, possibly external requests, etc.) is documented in a parameter list and a datapoint list, which is located in the control cabinet. An advance delivery of the parameter list or datapoint list is available on request by agreement with the responsible project officer Data query, Function Codes The Modbus TCP slave works as a passive node and processes inquiries, which come from the Master, about reading or writing data. The inquiries are encoded in the form of function calls (function codes, function calls). The slave does not initiate any communication to the Master by itself. In principle individual states (coils) can be read or written bit-wise, or registers can be read or written word by word. The following function codes are supported: MODBUS function Function Code Direction Read Coil / Read individual bit 1 Slave--> Master Read Input Register / Read dataword 4 Slave --> Master Write Coil / Write individual bit 5 Master --> Slave Write Single Register / Write dataword 6 Master --> Slave Coils and registers The Input and Output buffers are structured according to the following pattern: Note: Coils are counted from the direction of the MSB, e.g. Coil 1 corresponds to Bit 16 of Register 1. 8

9 Register# Coil# Buffer Storage location in the buffer Comment Input Buffer h Available Modbus h functions: h - Read Coil (FC1) h - Read Input Register (FC4) h A...00Bh C...00Dh FC...1FDh FE...1FFh Reserved Output Buffer h Available Modbus h functions: h - Write Coil (FC5) h - Write Single Register (FC6) h A...00Bh C...00Dh FC...1FDh FE...1FFh Reserved Note: The order-related assignment of the datapoints to the registers and coils (measured values, operating signals, fault messages, possibly external requests, etc.) is carried out when the control cabinet is delivered (datapoint list located in the control cabinet). An advance delivery of the datapoint list is available on request by agreement with the responsible project officer. 2.5 Modbus TCP (via MEC Optimize) IP addresses are only used and assigned when the appropriate control cabinets are part of the standard delivery. Precondition: MEC Optimize must be part of the scope of delivery. The IP address of MEC Optimize can be changed on an order-related basis. If other values (IP address and subnet mask) are to be set at the factory as pre-settings, then these must be notified to the project manager within 10 working days at the latest after the order confirmation has arrived. The assignments of the IP addresses to the control cabinet numbers and manufacturer numbers are documented in the order-related parameter list, which is supplied with the control cabinet. 9

10 Communication Interface MEC Optimize Modbus-TCP Slave IP-Address: MEC Optimize Subnetmask TCP-Port Slave 5020 Communication: Transport protocol TCP/IP Mode Slave Application protocol Modbus TCP Industrial Ethernet CPU-Parameter (Slot; Rack) 1 x RJ45 Properties 10/100/1000 Mbit/s, Full Duplex, Autonegotiation Note: Order-related data (measured values, operating signals, fault messages, possible external requirements, etc.) is documented in a parameter list and a datapoint list. The datapoint list is available via the MEC Optimize web application, while the parameter list is enclosed in the control panel. An advance delivery of the parameter list or datapoint list is available on request in agreement with the responsible project officer (but at the earliest however after the control panel has been manufactured) Data query, Function Codes The Modbus TCP slave works as a passive node and processes inquiries, which come from the Master, about reading or writing data. The inquiries are encoded in the form of function calls (function codes, function calls). The slave does not initiate any communication to the Master by itself. In principle individual states (coils) can be read or written bit-wise, or registers can be read or written word by word. The following function codes are supported: MODBUS function Function code Direction Read Coil / Read single bit (from Area 2 - Read & Write Coils) Read Input Discretes / Read multiple bits (From Area 1 Input Discretes) Read Multiple Registers / Read multiple data words (from Area 4 Holding Register) Read Register / Read one data word (from Area 3 Input Register) Write Coil / Write single bit (from Area 2 Read & Write Coils) Write Single Register / Write one data word (from Area 4 Holding Register) Force Multiple Coils / Write multiple bits (from Area 2 Read & Write Coils) 1 Slave Master 2 Slave Master 3 Slave Master 4 Slave Master 5 Master Slave 6 Master Slave 15 Master Slave Write Multiple Registers / Write multiple data words (from Area 4 Holding Register) 16 Master Slave 10

11 2.5.2 Coils and registers The entire memory area is divided into the following four areas: Area Register or Bit number (or Coil number) Description 1 Bit 0 to Input Discrete (Read bits); Access is gained via the following function codes: FC 2 Read Input Discretes 2 Bit 0 to Read & Write Coils (Read & write bits); Access is gained via the following function codes: FC 1 Read Coil FC 5 Write Coil FC 15 Force Multiple Coils 3 Bit 0 to Input Register (Read register); Access is gained via the following function codes: FC 4 Read Register 4 Bit 0 to Holding Register (Read & write register); Access is gained via the following function codes: FC 3 Read Multiple Registers FC 6 Write Single Register FC 16 Write Multiple Registers Note: The datapoints are assigned on an order-related basis to the Registers and Coils (measured values, operating signals, fault messages, possible external requirements, etc.) via the datapoint list, when MEC Optimize is delivered. 2.6 OPC UA (via MEC Optimize) IP addresses are only used and assigned when the appropriate control cabinets are part of the standard delivery. Precondition: MEC Optimize must be part of the scope of delivery. The IP address of MEC Optimize can be changed on an order-related basis. If other values (IP address and subnet mask) are to be set at the factory as pre-settings, then these must be notified to the project manager within 10 working days at the latest after the order confirmation has arrived. The factory settings are documented in the order-related parameter list, which is supplied with the control panel. 11

12 Communication Interface MEC Optimize OPC UA Server IP-Address: MEC Optimize Subnetmask TCP-Port 4840 Communication: Transport protocol TCP/IP Mode Server Application protocol OPC UA Industrial Ethernet CPU-Parameter (Slot; Rack) 1 x RJ45 Properties 10/100/1000 Mbit/s, Full Duplex, Autonegotiation Data model as seen from an OPC UA client An OPC UA client can gain access to the data of the OPC UA server in compliance with the standards. The address is formatted as follows: ns=<namespaceindex>; <type>=<value> For example: ns=2;s=cms_measured value.bco1_measurements_measured value_boiler pressure value.value Note: Order-related changes to the data model are not possible Security settings The following security strategy is configured ex works in the OPC UA server: None The following information security model is configured ex works in the OPC UA server: None Note: Communication is neither signed nor encrypted and must therefore only be used in closed networks. 2.7 BACnet/IP (via MEC Optimize) IP addresses are only used and assigned when the appropriate control cabinets are part of the standard delivery. Precondition: MEC Optimize must be part of the scope of delivery. The IP address of MEC Optimize can be changed on an order-related basis. If other values (IP address and subnet mask) are to be set at the factory as pre-settings, then these must be notified to the project manager within 10 working days at the latest after the order confirmation has arrived. The factory settings are documented in the order-related parameter list, which is supplied with the control panel. 12

13 Communication Interface MEC Optimize BACnet Controller IP-Address: MEC Optimize Subnetmask UDP-Port Communication: Transport protocol TCP/IP Mode Server Application protocol BACnet/IP Industrial Ethernet CPU-Parameter (Slot; Rack) 1 x RJ45 Properties 10/100/1000 Mbit/s, Full Duplex, Autonegotiation Supported BACnet objects The BACnet controller supports the following BACnet objects: ANALOG_INPUT ANALOG_OUTPUT BINARY_INPUT BINARY_OUTPUT MULTISTATE_INPUT MULTISATE_OUTPUT Note: Order-related changes to object contents are not possible Object: Device The device object provides general information about the controller to all connected clients. The controller's device object contains all the mandatory fields within the standard and is therefore not described here in more detail Object: ANALOGUE_INPUT This object is used to provide an analogue value to a BACnet client. The BACnet ANALOGUE_INPUT object is used to provide the following elements: Object_Identifier Object_Name Object_Typ Status_Flags Event_State Description Device_Type Reliability Out_of_service Present_Value High_Limit Low_Limit 13

14 Units Max_Pres_Value Min_Pres_Value COV_Increment Object: ANALOGUE_OUTPUT This object is used to receive an analogue value from a BACnet client. The BACnet ANALOGUE_OUTPUT object is used to provide the following elements: Object_Identifier Object_Name Object_Typ Status_Flags Event_State Description Device_Type Reliability Out_of_service Present_Value Units Max_Pres_Value Min_Pres_Value COV_Increment Polarity Priority_Array Relinquish_Default Object: BINARY_INPUT This object is used to provide a binary value to a BACnet client. The BACnet BINARY_INPUT object is used to provide the following elements: Object_Identifier Object_Name Object_Typ Status_Flags Event_State Description Device_Type Reliability Out_of_service Present_Value Active_Text Inactive_Text Polarity 14

15 Object: BINARY_OUTPUT This object is used to receive a binary value from a BACnet client. The BACnet BINARY_OUTPUT object is used to provide the following elements: Object_Identifier Object_Name Object_Typ Status_Flags Event_State Description Device_Type Reliability Out_of_service Present_Value Active_Text Inactive_Text Polarity Priority_Array Relinquish_Default Object: MULTISTATE_INPUT This object is used to provide a multi-level value (e.g. a switch setting) to a BACnet client. BACnet name from the standard MULTISTATE_INPUT Description Is written by the driver Object_Identifier Internal object number x Object_Name Name of the object x Object_Type Object type x Status_Flags BACnet status information x Event_State NORMAL (or Fault state) x Fixed value or link on a datapoint element Description Translated description text of the object x Device_Type Data class x Reliability Fixed link to Data acquisition disruption Is set to 12 (COMMUNICATION_FAILURE), if the connection to the PLC is disrupted. Out_of_service Is set if objects are deactivated x Present_Value Current value x State_Text Texts for the individual states x Number_of_States Number of states x x 15

16 Object: MULTISTATE_OUTPUT This object is used to receive a multi-level value from a BACnet client. MULTISTATE_OUTPUT BACnet name from the standard Description Is written by the driver Fixed value or link on a datapoint element Object_Identifier Internal object number x Object_Name Name of the object x Object_Type Object type x Status_Flags BACnet status information x Event_State NORMAL (or Fault state) x Description Translated description text of the object x Device_Type Data class x Reliability Fixed link to Data acquisition disruption Is set to 12 (COMMUNICATION_FAILURE), if the connection to the PLC is disrupted. x Out_of_service Is set if objects are deactivated x Present_Value Current value x State_Text Texts for the individual states x Number_of_States Number of states x Priority_Array Matrix of the command priority x Relinquish_Default Fixed link to Present_Value, so that the present_value is set as the value, if Priority Array is empty. x Parameters of the BACnet controller The BACnet controller is parameterised as follows: Note: Setting values cannot be adjusted on an order-related basis. 16

17 Parameter name Function Setting value LocalDeviceID LocalDeviceName DeleteOutOfServiceObjects Internal Priority The local ID for the device object of the BACnet controller. This ID is displayed to all other devices in the network and is therefore one-to-one. The local name for the device object of the BACnet controller. This name is displayed to all other devices in the network. This parameter specifies, whether all objects, which have the "Out of service" status, are to be deleted after a modification of the data model. This parameter specifies the command priority, with which the BACnet controller writes in the priority array of ANALOG_OUTPUT, MULTISTATE_OUTPUT and BINARY_OUTPUT objects, if the value changes in the data model and if the change was not triggered by a BACnet client. So that the values remain consistent, it is necessary that the BACnet controller and the BACnet client write with the same command priority. ClearDataModel This parameter specifies, whether during parameterisation the existing data model is to be deleted and created again, or whether an existing data model is to be modified net = <Network> "IP" <IP address> <Subnet mask> <UDP port> Network: The unique assigned BACnet network number. The BACnet controller can communicate with exactly one BACnet network. IP: Type of BACnet protocol. Only "IP" (BACnet/IP) is supported by the BACnet controller. IP address: The IP address of the network card, through which the BACnet controller can be reached via the BACnet/IP network. If the entry is empty, the BACnet controller opens the UDP port on all of the computer's network adapters. If the UDP port is to be opened on only one defined adapter, the IP address of this adapter must be given. The BACnet controller can therefore open the UDP port on either all the computer's network adapters or on just one. Subnet mask: The subnet mask defines the broadcast addresses, through which broadcasts are sent in the BACnet network. If the entry for the subnet mask is empty (""), the subnet mask for the particular network connection is used. UDP port: Defines the UDP port, which is used for the BACnet/IP communication. The standard port for the BACnet communication is (0xBAC0). 20 BOSCH_CMS_ 0 (Objects with the "Out of service" status are not deleted) 8 (The BACnet controller writes with command priority 8 in the priority array of ANALOG_OUTPUT, MULTISTATE_OUTPUT and BINARY_OUTPUT objects) 0 (The existing data model is modified) net = 1 "IP" "" ""

18 Lang This parameter defines, in which language the parameterised texts are transferred de_de.utf8 (German) BACnet Interoperability Building Blocks (BIBBs) The following BIBBs are supported by the BACnet controller (BIBBs that extend beyond these are not supported): BIBB Interoperability range Description DS-RP-B Data sharing Read property - The B device provides data to the A device. DS-WP-B Data sharing Write property - The B device allows the A device to change a value. DS-COV-B Data sharing Change of value - The B device provides COV data to the A device. DM-DDB-B Device & Network Management Dynamic Device Binding - The B device provides information about its device attributes and replies to inquiries in order to identify itself. DM-DOB-B Device & Network Management Dynamic Object Binding - The B device provides address information about its objects on request. DM-DCC-B Device & Network Management Device Communication Control - The B device reacts to a communication control executed by the A device Restrictions The following restrictions apply to the BACnet controller: The BACnet controller does not support intrinsic event reporting and algorithmic change events. The BACnet controller does not support any clock time synchronisation. 2.8 PROFINET IO The boiler system can be connected via PROFINET IO either via the CP343-Lean or an X-gateway Profibus IO device, depending on the control hardware used. See the order-related wiring diagram for the connection that is used. IP addresses and equipment names are only used and assigned, if the corresponding control panels are also part of the scope of delivery. The equipment name, IP addresses, subnet mask and router address are preset at the factory and can be changed on the system at the operating panel. If other values (equipment name, IP addresses, subnet mask and router address) are to be set at the factory as factory settings prior to delivery of the system, then these must be notified to the project manager within 10 working days at the latest after the order confirmation has arrived. The factory settings are documented in the order-related parameter list, which is supplied with the control panel. The GSDML files of the gateway or the communication processor are available on the Internet: X-gateway: CP343-Lean: (deutsche Webseite / German website) CP343-Lean: (englische Webseite / English website) 18

19 Settings: Communications processor Medium steam: CP343-1 Lean / X-Gateway Profinet IO Device Medium water IP-address Device name IP-address Device name BCO boiler stbco hwbco1 BCO boiler stbco hwbco2 BCO boiler stbco hwbco3 BCO boiler stbco hwbco4 SCO stsco hwsco1 CCO stcco1 - - Subnetmask Router ---- Communication: Transport protocol TCP/IP Application protocol PROFINET IO Mode Device Industrial Ethernet 2 x RJ45, 2-port-switch integrated Properties 10/100MBaud, Full/Half Duplex, Autosensing/Autonegotiation, Autocrossover Note: The order-related assignment of the datapoints to the registers and coils (measured values, operating signals, fault messages, possibly external requests, etc.) is carried out when the control cabinet is delivered (datapoint list located in the control cabinet). An advance delivery of the datapoint list is available on request by agreement with the responsible project officer. 19