firmware (for that you can "download all" after updating the firmware. Note that you'll need the USB port after the update (as your S-Bus address might be gone). Alternatively, you can also copy the [...] . On a PCD3.M6860 it’s possible to use BACnet on the Ethernet port ETH1 and/or on ETH2? (FAQ #102031) 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
communication errors when connecting a PCD/PCS in "Secure S-Bus Data Mode"? (FAQ #101180) In case a "non Saia PCD® COSinus" PCD or PCS1 system is connected with "Secure S-Bus Data mode" (e.g. over a serial cable or over modem) from time to time a telegram is not answered correctly. Symptom A PCD or a PCS connected with another system (e.g. PC or another PCD system) using the "Secure S-Bus Data mode" does not answer a telegram from time to time. This can e.g. be seen by a red LED on transmit or receive FBoxes
communication errors when connecting a PCD/PCS in "Secure S-Bus Data Mode"? (FAQ #101180) In case a "non Saia PCD® COSinus" PCD or PCS1 system is connected with "Secure S-Bus Data mode" (e.g. over a serial cable or over modem) from time to time a telegram is not answered correctly. Symptom A PCD or a PCS connected with another system (e.g. PC or another PCD system) using the "Secure S-Bus Data mode" does not answer a telegram from time to time. This can e.g. be seen by a red LED on transmit or receive FBoxes
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
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
for USB, Profi-S-Bus, Profi-S-IO, Multiple S-Bus PGU: version 020 When using the Ethernet Module PCD7.F650: The minimum firmware version for the Ethernet Module is $0H, recommended 010 or later [...] 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
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
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
