-Bus Data mode"). Saia PCD® COSinus based systems (PCD2.M480, PCD2.M5xx0 and PCD3) are not concerned. Reason The reason for this behavior is that the PCD/PCS does not correcly answer telegrams where [...] appears if the used firmware on the CPU does not support the "active and non ACK" filter for the S-Web alarming functionality (e.g. a PCD2.M150 with firmware 0D3). Symptom Instead of the [...] to the firmware supporting the according feature (see table below). System minimal FW PCS1.Cxxx 0E3 PCD1.M1x5 0E3 PCD2.M150 0E3
COSinus FW 1.28.37 was released as maintenance version for the systems: - PCD1.M0xx0/M2xx0, PCD2.M4x60, PCD3.Mxx60, PCD3.M6880 and PCD3.T665/T666/T668 . In June 2017: the COSinus FW 1.28.16 was introduced into production for the systems: - PCD1.M0xx0/M2xx0, PCD2.M4x60, PCD3.Mxx60, PCD3.M6880 and PCD3.T665/T666/T668 . the BACnet and LonIP FW 1.28.16 was put into production [...] the following PCD's with 8 MB onboard firmware memory: PCD1.M0xx0/M2xx0, PCD2.M4x60, PCD3.Mxx60, PCD3.M6880 and PCD3.T665/T666/T668 The table below does show the hardware dependencies in
-Bus Data mode"). Saia PCD® COSinus based systems (PCD2.M480, PCD2.M5xx0 and PCD3) are not concerned. Reason The reason for this behavior is that the PCD/PCS does not correcly answer telegrams where [...] appears if the used firmware on the CPU does not support the "active and non ACK" filter for the S-Web alarming functionality (e.g. a PCD2.M150 with firmware 0D3). Symptom Instead of the [...] to the firmware supporting the according feature (see table below). System minimal FW PCS1.Cxxx 0E3 PCD1.M1x5 0E3 PCD2.M150 0E3
-Bus Data mode"). Saia PCD® COSinus based systems (PCD2.M480, PCD2.M5xx0 and PCD3) are not concerned. Reason The reason for this behavior is that the PCD/PCS does not correcly answer telegrams where [...] appears if the used firmware on the CPU does not support the "active and non ACK" filter for the S-Web alarming functionality (e.g. a PCD2.M150 with firmware 0D3). Symptom Instead of the [...] to the firmware supporting the according feature (see table below). System minimal FW PCS1.Cxxx 0E3 PCD1.M1x5 0E3 PCD2.M150 0E3
PCD7.R56x PCD3.R56x BACnet modules for Saia PCD2.M5xx0 / PCD3 [...] memory modules and on the INTFLASH (if available). These are: PCD1.M2xxx (INTFLASH) PCD2.R6000 PCD3.R550, PCD3.R551, PCD3.R561 PCD3.R600 PCD7.R550, PCD7.R551, PCD7.R561 INTFLASH of a PCD3 Compact or a PCD1.M
Communication / BACnet On a PCD3.M6860 it’s possible to [...] 1 or ETH2 of the PCD3.M6860. In PG5 it’s possible to activate at the same time BACnet on ETH1 and ETH2 but we strongly recommend to use/activate BACnet only on one of the two Ethernet ports to avoid a bad behavior on BACnet. The activation and selection of the used Ethernet port for BACnet communication on the PCD3.M6860 is done in PG5 2.2 or PG5 2.3 in the device configurator
BACnet and PCD FW for PCD1.M2xx0, PCD3.Mxxx0, PCD2.M5xx0 which could be used as maintenance firmware for PCD's with 4 MB firmware memory
BACnet FW and coresponding PCD FW for PCD1.M2220-C15, PCD1.M2160, PCD2.M4x60, PCD3.Mxx60 and PCD3.M6880 The FW >= 1.28.xx does support the BACnet standard revision 14. This firmware should [...] this release The Memory Module PCD7.R562 or PCD3.R562 is required to run this FW (PCD7.R560, PCD7.R561, PCD3.R560, PCD3.R561 are not supported anymore) Existing BACnet projects (based on standard [...] 2.1.311 or newer) to prevent the loading of the FW 1.24.xx or 1.26.xx to a not compatible PCD.
Package does include the FW for the PCD1.M2, PCD2.M5, PCD3.M and the BACnet FW. This firmware does support the modules PCD7.W600 and PCD7.R610 Do use at least the PG5 firmware downloader version 2.1.311 or newer (included in PG5 patch 2.1.311 or newer) to prevent the loading of the FW 1.24.xx to a not compatible PCD.
BACnet FW and coresponding PCD FW for PCD1.M2xx0, PCD2.M4x60, PCD2.M5xx0, PCD3.Mxxx0, and PCD3.Mxx60. The FW =< 1.26.xx does support the BACnet standard revision 9 . Do use at least the PG5 firmware downloader version 2.1.311 or newer (included in PG5 patch 2.1.311 or newer) to prevent the loading of the FW 1.24.xx or 1.26.xx to a not compatible PCD.