. Why the RS-485 S-Bus communication between the PCD master and the slave does fail sometime, if FW 1.28.20…1.28.33 is used? (FAQ #102026) It’s 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
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 MC5 mode on F2xxx module All PCD’s: RS485 driver keep [...] PCD’s: Profibus communcation using onboard FDL port. The FCS test for SD2 telegram was not implemented correctly. All PCD’s: When S-Bus IP Nodelist is used it’s possible that the communication using
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 MC5 mode on F2xxx module All PCD’s: RS485 driver keep [...] PCD’s: Profibus communcation using onboard FDL port. The FCS test for SD2 telegram was not implemented correctly. All PCD’s: When S-Bus IP Nodelist is used it’s possible that the communication using
deploying the new program (download changed blocks in run is not yet possible). On the PCD3.M6860, both Ethernet ports are active at the same time (and also active for the Ether S-Bus communication, if activated on the device configurator) regardless of the channel number. The same behavior does also apply for the S-Bus communication F-Boxes, means that the channel defined in the master/slave F [...] 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
deploying the new program (download changed blocks in run is not yet possible). On the PCD3.M6860, both Ethernet ports are active at the same time (and also active for the Ether S-Bus communication, if activated on the device configurator) regardless of the channel number. The same behavior does also apply for the S-Bus communication F-Boxes, means that the channel defined in the master/slave F [...] 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
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 MC5 mode on F2xxx module All PCD’s: RS485 driver keep [...] PCD’s: Profibus communcation using onboard FDL port. The FCS test for SD2 telegram was not implemented correctly. All PCD’s: When S-Bus IP Nodelist is used it’s possible that the communication using
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 MC5 mode on F2xxx module All PCD’s: RS485 driver keep [...] PCD’s: Profibus communcation using onboard FDL port. The FCS test for SD2 telegram was not implemented correctly. All PCD’s: When S-Bus IP Nodelist is used it’s possible that the communication using
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 MC5 mode on F2xxx module All PCD’s: RS485 driver keep [...] PCD’s: Profibus communcation using onboard FDL port. The FCS test for SD2 telegram was not implemented correctly. All PCD’s: When S-Bus IP Nodelist is used it’s possible that the communication using
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 MC5 mode on F2xxx module All PCD’s: RS485 driver keep [...] PCD’s: Profibus communcation using onboard FDL port. The FCS test for SD2 telegram was not implemented correctly. All PCD’s: When S-Bus IP Nodelist is used it’s possible that the communication using
. Why does my RS-232 S-Bus communication not work with the PCD2.F2xx0 and PCD3.F2xx module? (FAQ #101775) The RS-232 S-Bus [...] V020) it may be, that the S-Bus communication over converters (like modem or optical converters) to other devices does not work. The S-Bus communication works fine, if no converters are used in between. Also other communications protocols then S-Bus like "Mode C, Modbus" works fine on the PCD2.F2xx0 and PCD3.F2xx module (with and without converters in between). On the print screen below
