The PCD2.M480 and the PCD3.Mxxx do not support the baudrates 100, 300 and 600 Baud.
A. Nevertheless it is possible measuring the range 0..20 mA with the analogue input modules for PCD systems. Why do the SBC input modules have a range of 0..20 mA? One advantage of measuring the [...] Product Index Archive PCD6 Nxxx General [...] . PCD6 Series (obsolete) Documentation
A. Nevertheless it is possible measuring the range 0..20 mA with the analogue input modules for PCD systems. Why do the SBC input modules have a range of 0..20 mA? One advantage of measuring the [...] Product Category Archive Programmable Controller PCD6: CPUs in 19 inch racks Nxxx [...] commercially available products. PCD
measures. Information about protective measures can be found on the support hp If you need a PCD with cyber security levels SL3+ and based on ANSI ISA 62443 then checkout our PCD3.M [...] PG5 1.2 and PG5 1.3 internally don’t have the same structure. Since the S-Bus OPC-Sever uses the scommdll to communicate with the PCD’s we have to adapt the S-Bus OPC-Server depending oft the scommdll [...] PG5 1.2 and PG5 1.3 internally don’t have the same structure. Since the S-Bus OPC-Sever uses the scommdll to communicate with the PCD’s we have to adapt the S-Bus OPC-Server depending oft the scommdll
measures. Information about protective measures can be found on the support hp If you need a PCD with cyber security levels SL3+ and based on ANSI ISA 62443 then checkout our PCD3.M [...] PG5 1.2 and PG5 1.3 internally don’t have the same structure. Since the S-Bus OPC-Sever uses the scommdll to communicate with the PCD’s we have to adapt the S-Bus OPC-Server depending oft the scommdll [...] PG5 1.2 and PG5 1.3 internally don’t have the same structure. Since the S-Bus OPC-Sever uses the scommdll to communicate with the PCD’s we have to adapt the S-Bus OPC-Server depending oft the scommdll
Due of a firmware error on the COSinus FW 1.20.25 it’s not possible to communicate over RS232 on the port 0 of the PCD2.M5440 and port 1 of PCD3 CPU’s, but only on PCD’s without Ethernet port. The error is fixed since the FW 1.20.31. Also the FW 1.16.69 doesn’t have this error. PCD’s equipped with a Ethernet port doesn’t have this error. The concerned PCD’s are: • PCD2.M5440 (port 0 / RS232) • PCD3.M6440/M5440/M3230 (port 1 / PCD3.F121) • PCD3.M3020 (port 1 / PCD3.F121) • PCD3.M2030V6 (port 1 / PCD7.F121S) • PCD3.M2230A4T5 (port 1 / PCD7.F121S) Communication over RS485 works
If the PCD2/3.W220Z18 card is plugged in to a ‘Power PCD‘ or a PCD2.C1000 or PCD2.C2000 and if all 8 analog inputs channels of the PCD2/3.W220Z18 module are connected to 8 PT100 sensors then the measured PT100 temperature values of the 8 channels are not correct. ‘Power PCD’s’ are: PCD1.M2x20, PCD1.M2160, PCD1.M2220-C15 PCD2.M5540, PCD2.M5440, PCD2.M4160, PCD2.M4560 PCD3.Mxx60 To solve the issue, use and connect only up to 7 PT100 sensors to the PCD2/3.W220Z18 or do use a PCD2/3.W350 module, if all 8 PT100 are needed.
Yes it’s possible to use BACnet on both ports ETH1 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.
On the master PCD the I/O mapping to Register 4096 until Register 16'383 for RIO-networks (Profibus DP or Profi-S-I/O) doesen't work on PCD3 and PCD2.M480 and PCD2.M5xx0 systems with firmware version 1.08.23.
Is it possible to order the battery module cover (PCD3.M5xxx) and the I/O covers as spare parts?
