Saia-Burgess Controls AG
Manual
Manual PCD 1 / PCD 2 Series
│ Document 26
/
737 E
N22 │ 2013-11-26
Appendix
A-5
Protocols on serial ports
A
A.3
Protocols on serial ports
A.3.1 Protocols supported by the firmware
Protocol overview and
support by firmware for
the different CPUs
Purpose
Supported by
PCD1.M1xx
PCD2.M1
10
PCD2.M120
PCD2.M150
PCD2.M170
PCD2.M480
PGU
with
pin 6
(DSR) of
the PGU connector
set
to logical “1”
(P800, Full
Protocol)
Programming, debugging; replaced
on newer releases by an equivalent
function with S-Bus Parity mode
PGU
with
pin 6
(DSR) of
the PGU connector
set to
logical “1”
(Parity mode,
Full Protocol)
Programming, debugging
1)
1)
1)
S-Bus PGU
on the PGU
port, with
pin 6
(DSR) of
the PGU connector
set to
logical “0”
(Data, Parity or
Break mode, Full Protocol)
Programming, debugging,
visualization. Also allows access via
gateway to stations within a different
S-Bus network
2)
2)
2)
2)
Serial S-Bus
on any serial
port (Data, Parity or Break
mode)
Exchange of data with other
controllers or with RIOs; previously
called just S-Bus
3)
3)
3)
3)4)
Mode D
(reduced version of
P800)
Exchange of data over point-to-point
connections
5)
5)
5)
Character mode
(MC1 to
MC5)
Transmission of characters or text
over serial ports; basis for creating
own protocols in the user program
6)
6)
6)
1) Requires the use of the PCD8.K111 programming cable
2) Requires an appropriate configuration in hardware settings
3) Requires an assignment of the port in the user program (SASI). For new applications, Data mode should always be
selected. Exceptions: on PCD7.D7xx terminals, Parity mode is used
4) Break mode is not supported; Parity mode cannot be used on port 1
5) Obsolete; for new applications, use Serial S-Bus Data mode instead
6) MC5 Mode (RS-485 with immediate release of data line after transmission of the last character) requires the
following minimum firmware versions:
PCD1.M1x0: V080
PCD2.M110 / M120: V090
PCD2.M150: V0C0
PCD2.M170: V010
A.3.2 Protocols implemented in the user program
Based on Character mode (and a very good knowledge of LI programming), any
desired protocols can be implemented.
Our system partners have already done this for a large number of protocols, enabling
our controllers to communicate with components from a variety of manufacturers, e.g.
via Modbus, M-Bus etc.
Please refer to the Links page at
for links to system partners.
