With some specific sensor and configuration, the inputs of a module PCD2/3.W525 could perturbate an other input of the same module
This FAQ explains the differences between the old PCD7.F1xx and the new PCD7.F1xxS communication modules.
Starting with hardware version B the communication cards PCD7.F1xxS are fully compatible with the "older" systems (PCD2.M1xx/PCD2.M48x/PCS1/PCD1.M1x5).
No, the PCD7.F110, PCD7.F120, PCD7.F150 and PCD7.F180 can’t be used on PCD1.M2 and PCD2.M4x60 devices. Only the PCD7.F1xxS modules are supported on the PCD1.M2 and PCD2.M4x60 CPU’s.
Fbox Update of the E-Line Library causes Problem with I/O refresh in Fupla
Due to an error on the PG5 2.2.230 BACnet compiler, PCD resource addresses changes (Reg-ister/Flags/DB’s/Text address change of existing symbols) on existing PG5 projects are not detected from the PG5
If the PC where Saia PCD Supervisor is running, was powered off without shutting down the Saia PCD Supervisor then it’s possible that after power on of the PC, the platform daemon used from Saia PCD S
Due to an error on the E-Line S-Bus communication library < 1.2.110, the S-Bus communication stops after a certain time, if the communication mode ‘on Event’ or ‘on Sampling time n’ has been selected
Due to an error on the communication library 2.7.370, the S-Bus communication stops after a certain time or after the download of the program, if the communication mode ‘on Event’ or ‘on Sampling time
This Firmware do fix the issue CVE-2017-9628 related to Ethernet frame padding information leakage. To avoid any problems in relation to this leakage we do recommend strongly to update to the lat
