This version runs together with PG5 V2.2.130 or later including English documentation version 2.02.18.03 and Scomm.dll version 2.2.130 It's possible to use this version with PG5 2.3.xxx To use the S-Bus OPC-Server with PG5 2.3, change the path to PG5 2.3 by selecting the option 'File, Path to ScommDrv libraries ...' on the OPC-Server configuration.
When values are read from a PCD7.L1xx or a PCD7.L3xx module, the preparation of the S-Bus response telegram needs about 10 ms. This time is longer than the same task does take on a PCDx.Mxxx CPU. The time used for writing a value to a PCD7.Lxxx module is about equal to the time that is used by a PCDx.Mxxx CPU (because only an acknowledgement needs to be replied).
The RS-232 S-Bus communication may doesn't work at all with PCD2.F2xx0 or PCD3.F2xx modules when communicating over converters (like modem or optical converters) to other devices. On PCD2.F2xx0 and PCD3.F2xx with Firmware less or equal V020 the handling of the RTS signal is wrong.
Product Category Remote I/O PCD7.Lxxx S-Bus RIO General FAQ PCD7 Why I have a blue screen after a panel
Product Category Configurable room controller PCD7.L6xx: S-Bus/LON Room Controller PCD7.L60x-1: Room Controller S-Bus [...] -100.0 Communication on serial S-Bus fails while the AutoConfig Output of the Setup FBox stays '1'! (FAQ #101812) L60x Config, L60x Room [...] with use of the PCD7.L60x S-Bus room controllers (not LON
Compact room controller 24 VAC with 1 triac output for thermal valves (PWM), 2 digital inputs and integrated temperature sensor (without user controls)
including English documentation version 2.02.17.17 (Scomm.dll version 1.4.300) This version runs together with PG5 V1.4.300
including English documentation version 2.02.10.20 (Scomm.dll version 1.3.120) This version runs together with PG5 V1.3
including English documentation version 2.02.09.01 (Scomm.dll version 1.2.130) This version runs together with PG5 V1.2
