In order to achieve a high and constant data throughput with S-Bus, the following guidelines can be helpful for the programmer of S-Bus communication.
PCD1 / _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
PCD1 / _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
three-phase energy meters with S-Bus, M-Bus or Modbus communication. Note also that the format of the serial number has changed for the S-Bus and Modbus (is now ASCII) and due of this it's necessary to [...] Comm. interface Prod.date =1322 S-Bus Register 13 12, 13 Modbus Register 16, 17 16, 17, 18 M-Bus Byte 8, 9, 10, 11 8, 9, 10, 11 [...] . Why is it not possible to communicate over S-Bus with the S-Energy meter (ALD1/ALE3/AWD3)? (FAQ #101591) Due to a
three-phase energy meters with S-Bus, M-Bus or Modbus communication. Note also that the format of the serial number has changed for the S-Bus and Modbus (is now ASCII) and due of this it's necessary to [...] Comm. interface Prod.date =1322 S-Bus Register 13 12, 13 Modbus Register 16, 17 16, 17, 18 M-Bus Byte 8, 9, 10, 11 8, 9, 10, 11 [...] . Why is it not possible to communicate over S-Bus with the S-Energy meter (ALD1/ALE3/AWD3)? (FAQ #101591) Due to a
-Line PCD1 / E-Line Why the RS-485 S-Bus communication [...] 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 a
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 MC5 mode on F2xxx module All PCD’s [...] 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 IP Nodelist is used it’s possible that the
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 MC5 mode on F2xxx module All PCD’s [...] 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 IP Nodelist is used it’s possible that the
PCD1 / _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
There are firmware depending differences in the handling of the Serial-S-Bus communication diagnosic flags TDIA and RDIA. Those flags are refreshed continuously by older FW versions but not by the Saia PCD® COSinus Classic PCD firmware (used for PCD2.M480 and PCD3 controllers).
