Building Automation and Control Network BACnet/IP support for PCD1.M2, PCD2.M5 or PCD3 systems can be added by mounting a BACnet module PCD7.R56x (or PCD3.R56x). This module contains a firmware [...] modules PCD2.F2610 (for PCD1.M2 and PCD2.M5) or the PCD3.F261 (for PCD3.M and PCD3.T666) allow a direct connection to the DALI bus as DALI master, programmed with FBoxes. With one module up to 64 ballasts [...] . For the communication with third party products the open data mode is supported. PCD1.M2120, PCD1.M2160, PCD2.M5540, PCD3.M2120, PCD3.M3330, PCD3.M5340, PCD3.M55x0, PCD3.M6xx0, Ethernet TCP
Ethernet port (PCD7.F655 or the integrated Ethernet ports on the PCD1.M0/M2, PCD2.M5 and PCD3 and all Panels with Ethernet ports) are not designed for this purpose. Possible solution to connect PCD [...] firmwares 1.16.xx have been introduced. The concerned systems are the PCD1.M2xx0, PCD2.M5xx0, PCD3.Mxxx0 and PCD3.Mxx60. This bug is now fix and it is once again possible to use the MPI communication with [...] ) on Saia PCD® COSinus systems (PCD3, PCD2.M5, PCD1.M2 and PCD2.M480). This phenomenon is based on the internal mechanism how the firmware assigns the port. It has not been observed before the usage of
Ethernet port (PCD7.F655 or the integrated Ethernet ports on the PCD1.M0/M2, PCD2.M5 and PCD3 and all Panels with Ethernet ports) are not designed for this purpose. Possible solution to connect PCD [...] firmwares 1.16.xx have been introduced. The concerned systems are the PCD1.M2xx0, PCD2.M5xx0, PCD3.Mxxx0 and PCD3.Mxx60. This bug is now fix and it is once again possible to use the MPI communication with [...] ) on Saia PCD® COSinus systems (PCD3, PCD2.M5, PCD1.M2 and PCD2.M480). This phenomenon is based on the internal mechanism how the firmware assigns the port. It has not been observed before the usage of
Ethernet port (PCD7.F655 or the integrated Ethernet ports on the PCD1.M0/M2, PCD2.M5 and PCD3 and all Panels with Ethernet ports) are not designed for this purpose. Possible solution to connect PCD [...] firmwares 1.16.xx have been introduced. The concerned systems are the PCD1.M2xx0, PCD2.M5xx0, PCD3.Mxxx0 and PCD3.Mxx60. This bug is now fix and it is once again possible to use the MPI communication with [...] ) on Saia PCD® COSinus systems (PCD3, PCD2.M5, PCD1.M2 and PCD2.M480). This phenomenon is based on the internal mechanism how the firmware assigns the port. It has not been observed before the usage of
Ethernet port (PCD7.F655 or the integrated Ethernet ports on the PCD1.M0/M2, PCD2.M5 and PCD3 and all Panels with Ethernet ports) are not designed for this purpose. Possible solution to connect PCD [...] firmwares 1.16.xx have been introduced. The concerned systems are the PCD1.M2xx0, PCD2.M5xx0, PCD3.Mxxx0 and PCD3.Mxx60. This bug is now fix and it is once again possible to use the MPI communication with [...] ) on Saia PCD® COSinus systems (PCD3, PCD2.M5, PCD1.M2 and PCD2.M480). This phenomenon is based on the internal mechanism how the firmware assigns the port. It has not been observed before the usage of
Important note: Since the PCD6 is phased out, it is not possible anymore to send the PCD6.M300 back for modification/upgrade.
Server Newer classic PCD types (introduced after 2000, e.g. PCD2.M170, PCD2.M480, PCD3.Mxxxx, PCS1) do have an integrated Web Server (no extra costs) in the Firmware (FW). To access the Web server the [...] space Communication interfaces are directly mounted onto the main print of a CPU and therefore do not require additional space. A PCD2.M480 may handle up to 8 serial interfaces [...] Characteristics of the Saia PCD® Classic controllers There are some special features and characteristics of the Saia PCD® Classic controllers to be mentioned. The list below tries to give an overview especially
Yes, it is implemented in the PCD3 with FW Version $12 or later. On the PCD2.M5xx0 it is supported with every firmware
No. This is a PG5 restriction. The ethernet configuration can only be loaded to CPU 0. It is not possible to configure the PCD6.M3 with ethernet-module as an other CPU than CPU 0.
In the system catalogue there is a schematic of a PCD connected to a BACnet/IP network which could lead to a missinterpretation. Although BACnet is supported by a PCD3 or a PCD2.M5xx0 and LON on IP will be suppored in future, it won't be possible to run both stacks on the same PCD at the same time.