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
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
In seltenen Fällen ist die Ether-S-Bus Kommunikation bei Programmen die aus PG5 2.0 oder 2.1.200 in die PG5 2.1.210 importiert wurden nach einem Rebuild All und anschließendem Download nicht mehr in Funktion
Miscellaneous S-Bus, S-Bus on Ethernet TCP/IP DK3964R, MPI, RK512 BACnet, EIB, GENIbus, LON, MP Bus, M-Bus AS-i, Modbus, Modbus/TCP/UDP, Profibus [...] 's, PCD1.M137 , PCD2.M127 , PCD2.M157 , PCD2.M177 Not available on the classic CPU's S-Bus General [...] 's. Details about how to plan S-Bus networks can be found in the documentation area. A system partner provides a tool that allows to optmize the S-Bus communication by setting priorities for different telegrams
. OPC Server for SBC S-Bus PCD8.C59xx OPC [...] of up to 14336 flags Supports the directly configuration of S-Energy counter with serial S-Bus interface: - AWD3 - ALE3 - AWD1. OPC Server version 2.02.16.14 (April 09) New [...] .4.300 Is it possible to run the S-Bus OPC-Server on Windows Vista, Windows 7 and Windows Server 2008? (FAQ #101057) Yes, the
PCD8.OPC-x OPC Server for SBC S-Bus OPC-Server Good to know The main differences between version 2 [...] 5 2.0 SP2 can be selected and doing so the 64bit compatible USB driver from PG5 will be used). All the S-Bus OPC Server versions listed above do run as demonstration version if no license is [...] of up to 14336 flags Supports the directly configuration of S-Energy counter with serial S-Bus interface: - AWD3 - ALE3 - AWD1. OPC Server version 2.02.16.14 (April 09) New
PCD8.OPC-x OPC Server for SBC S-Bus OPC-Server Good to know The main differences between version 2 [...] 5 2.0 SP2 can be selected and doing so the 64bit compatible USB driver from PG5 will be used). All the S-Bus OPC Server versions listed above do run as demonstration version if no license is [...] of up to 14336 flags Supports the directly configuration of S-Energy counter with serial S-Bus interface: - AWD3 - ALE3 - AWD1. OPC Server version 2.02.16.14 (April 09) New
SBC OPC Server for SBC S-Bus
If for example a Scada system communicate over S-Bus slave gateway port or S-Bus PGU port with a slave station via a master gateway port then after a programm download to the gateway PCD (or if the gateway PCD is restarted) the S-Bus slave gateway port or the S-Bus PGU port of the gateway SPS is blocked. In order to communicate again through this ports a system reboot (powerup) of the gateway SPS is needed. This problem could occur on all communication channels between the PC and the PCD (USB, serial, TCP)
