The PCD3.M3xxx, PCD3.M5xxx and PCD3.M6xxx do feature different possibilities for using the port 10 (D-Sub connector) and port 2 (terminal block).
-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
-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
5440 FW 1.16.52 FW >= 1.16.69 HW F ok ok HW G1 No 24V on MPI ok PCD3.M5560 FW 1 [...] Why the MPI adapter doesn’t work on the MPI port of the PCD3.M5547, PCD3.M5567, PCD3.M5540, PCD3.M5440 or PCD3.5560? (FAQ #101814) [...] Controller SBC PCD3 system PCD3.M2xxx Compact CPU base units with onboard I
5440 FW 1.16.52 FW >= 1.16.69 HW F ok ok HW G1 No 24V on MPI ok PCD3.M5560 FW 1 [...] Why the MPI adapter doesn’t work on the MPI port of the PCD3.M5547, PCD3.M5567, PCD3.M5540, PCD3.M5440 or PCD3.5560? (FAQ #101814) [...] Programmable Controller SBC PCD3 system PCD3.M2xxx Compact CPU base units with
-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