228
saia-pcd.com
PCD2.M5
BACnet MS/TP
BACnet®/IP
PCD3
PCD3
Communication & Interaction
2.6
BA communication systems
2.6.1
BACnet®
Recommendations/system limits
Type
Option
Interface
PG5 configuration, system limits
PCD3.M5560
1× PCD7.R56x
4× PCD3.F215
IP
MS/TP
Recommended for configurations of up to 1000 BACnet objects
Suitable for BACnet® and L
on
W
orks
® in parallel operation
PCD3.M5540
PCD3.M5340
1× PCD7.R56x
4× PCD3.F215
IP
MS/TP
Recommended for configurations of up to 800 BACnet objects
PCD3.M3330
PCD3.M3120
1× PCD3.R56x
3× PCD3.F215
IP
MS/TP
Recommended for configurations of up to 500 BACnet objects
PCD2.M5540
1× PCD7.R56x
4× PCD2.F2150
IP
MS/TP
Recommended for configurations of up to 800 BACnet objects
PCD1.M0160
1× PCD7.R56x
IP
Recommended for configurations of up to 800 BACnet objects
PCD1.M2xx0
1× PCD7.R56x
2× PCD2.F2150
IP
MS/TP
Recommended for configurations of up to 800 BACnet objects
PCD1.M2020
With no Ethernet
1× PCD7.R56x
2× PCD2.F2150
MS/TP
Recommended for configurations of up to 250 BACnet objects
Typical applications of a BACnet infrastructure
Heating, climate and ventilation control
Room automation
Networking dispersed sites
Recording energy data
The standard for building services
BACnet is a manufacturer-independent, globally standardised
communication protocol which is well-established in building
automation systems. BACnet is particularly suitable for hetero-
geneous structures involving automation stations of various
manufacturers. The server/client architecture allows each of the
BACnet devices to exchange data with one another without hav-
ing to adjust to the parameterisation of the other devices.
BACnet is far more than a protocol for merely transferring data;
BACnet itself defines important building automation functions,
such as the recording of historic trends or the monitoring of val-
ues against set limit values, for example. Communication servic-
es (BIBBs, BACnet Interoperable Building Blocks), such as those
for reading and writing content, event-controlled transmission
following changes and the handling of alarms/information
(events) are available.
PCD systems
BACnet is available for all classic PCD systems with the Saia PCD®
COSinus operating system as a communication option. The con-
nection is usually direct via BACnet IP (Ethernet). BACnet MS/TP
(RS-485) is also possible via a communication module.
BACnet always requires a BACnet option module for firmware
expansion. A PCD7.R56x is used for memory slots M1 and M2 for
PCD3.M5, PCD2.M5, PCD1.M2 and PCD1.M0 controllers. The
PCD3.R56x module is available for I/O slots 0…3 for PCD3.M3
controllers with no M1/2 slots.
PCD2.M5 and PCD1.M2 controllers also require a PCD2.F2150 for
connecting BACnet MS/TP, and PCD3 controllers require a PCD3.
F215 communication interface. This module also provides con-
trollers with no Ethernet with a BACnet interface. Controllers
with Ethernet also take on the function of a BACnet IP MS/TP
router. External gateways for connecting MS/TP devices direct to
the management system or other BACnet IP devices, for exam-
ple, are therefore no longer required.
BACnet certificates for PCD1, PCD2, PCD3 controllers;
see
Certificates, PCD
Third party system
