standard RS 485-Port for S-Bus, to add a Bus-Terminal etc. The wiring is: D-Sub S-Net MPI S-Bus / Terminal ... Pin 3 RxD/TxD-P --------------------- /TX /RX 5 [...] only supported by the PCD4 and PCD6 Reason The reason is, that the "IO Bus Quit fail" is a hardware interrupt created by the PCD4 and PCD6 I/O modules. On the PCD3 and also PCD2 I [...] . Can the S-Net MPI-Port on the PCD3.M5xx0 and on the PCD2.M5xx0 be used as standard RS-485 Port (FAQ #100500) Yes, it is
Notification-Class objects. BACnet: The PCD will now accept AcknowledgeAlarm service requests, which use complete wildcards as timestamps. Main corrections All PCD’s: On S-Bus data mode, if S-Bus CRC contains a S-Bus DLE as last character then S-Bus telegram is incorrect and not accepted from S-Bus recipient. (Since FW 1.28.20) All PCD’s: Not all bytes are transmitted when working with MC4 or [...] does not start COB when it was stopped before with SCOB All PCD’s: Profibus communcation using onboard FDL port. The FCS test for SD2 telegram was not implemented correctly. All PCD’s: When S-Bus
standard RS 485-Port for S-Bus, to add a Bus-Terminal etc. The wiring is: D-Sub S-Net MPI S-Bus / Terminal ... Pin 3 RxD/TxD-P --------------------- /TX /RX 5 [...] only supported by the PCD4 and PCD6 Reason The reason is, that the "IO Bus Quit fail" is a hardware interrupt created by the PCD4 and PCD6 I/O modules. On the PCD3 and also PCD2 I [...] . Can the S-Net MPI-Port on the PCD3.M5xx0 and on the PCD2.M5xx0 be used as standard RS-485 Port (FAQ #100500) Yes, it is
There are some restriction on the PCD2.M480, the port 1 as Master Port doesn't support parity mode. Note: The "Break mode" is not supported on the PCD2.M480!
Please note that PCD7.R400 modules delivered after April 2010 require the PCD2.M480 firmware version 1.08.53 or later Minimum firmware version for USB, Profi-S-Bus, Profi-S-IO, Multiple S-Bus PGU [...] PCD2 / _Firmware Classic Why the RS-485 S-Bus [...] possible that the some of the S-Bus telegrams transferred from the PCD S-Bus master to the S-Bus slaves over RS485 are malformed, and the S-Bus slave does reject the request from the master. This could
standard RS 485-Port for S-Bus, to add a Bus-Terminal etc. The wiring is: D-Sub S-Net MPI S-Bus / Terminal ... Pin 3 RxD/TxD-P --------------------- /TX /RX 5 [...] only supported by the PCD4 and PCD6 Reason The reason is, that the "IO Bus Quit fail" is a hardware interrupt created by the PCD4 and PCD6 I/O modules. On the PCD3 and also PCD2 I [...] . Can the S-Net MPI-Port on the PCD3.M5xx0 and on the PCD2.M5xx0 be used as standard RS-485 Port (FAQ #100500) Yes, it is
standard RS 485-Port for S-Bus, to add a Bus-Terminal etc. The wiring is: D-Sub S-Net MPI S-Bus / Terminal ... Pin 3 RxD/TxD-P --------------------- /TX /RX 5 [...] only supported by the PCD4 and PCD6 Reason The reason is, that the "IO Bus Quit fail" is a hardware interrupt created by the PCD4 and PCD6 I/O modules. On the PCD3 and also PCD2 I [...] . Can the S-Net MPI-Port on the PCD3.M5xx0 and on the PCD2.M5xx0 be used as standard RS-485 Port (FAQ #100500) Yes, it is
. PCD2 / _Firmware Classic Why the RS-485 S-Bus [...] possible that the some of the S-Bus telegrams transferred from the PCD S-Bus master to the S-Bus slaves over RS485 are malformed, and the S-Bus slave does reject the request from the master. This could lead to the situation that for example the PCD S-Bus master don’t receive actual values from E-Line RIO’s or that the program download of a PCD program from the PC to a Slave PCD which is located behind
standard RS 485-Port for S-Bus, to add a Bus-Terminal etc. The wiring is: D-Sub S-Net MPI S-Bus / Terminal ... Pin 3 RxD/TxD-P --------------------- /TX /RX 5 [...] only supported by the PCD4 and PCD6 Reason The reason is, that the "IO Bus Quit fail" is a hardware interrupt created by the PCD4 and PCD6 I/O modules. On the PCD3 and also PCD2 I [...] . Can the S-Net MPI-Port on the PCD3.M5xx0 and on the PCD2.M5xx0 be used as standard RS-485 Port (FAQ #100500) Yes, it is
