Together with the official PG5 2.2.140, Web Editor 8.3.0.740 was released. On this version there is a bug that lead to the situation that the properties window is empty or tabs of the properties window are not visible if the user does click on the layers in the document outline view. If this happens, the Web Editor 8 must be closed and re-opened again. There is a bug-fix version, Web Editor 8.3.0.749 The correction is also included in the web-editors which are supplied together with PG5 2.2.200 or later. A correct properties view looks like this: After the error the action tab is no more
In the FBox 'HVC Configuration' (L60x-1 HVC Cfg) in the FBox family 'RoomControler PCD7_60x V2' it is possible to modify the set point correction from the default value 0.5°K (step) to another value for ex. 0.4°K. So when pressing the buton on the PCD7.L644 once, and the actual setpoint is 21°C the diplays shows 20.5 instead of 20.6°C! After a few seconds the new set value is indeed correctly displayed: 20.6°C! This is only a visualisation probleme during the modifiation of the set point!
The battery voltage is checked in the battery module for undervoltage and overvoltage. New batteries have a too high voltage which causes the overvoltage limit to be exceeded.
If the PCD does have a FW 1.20.xx or higher and no time zone is defined in the PG5 device configurator, then the ‘Hevac Initx’ F-Box with version < 2.7.530 does not change the clock of the PCD if the winter/summer or summer/winter time change should be executed. This problem occurs with all 'Heavac Init' F-Boxes (Hevac 4 to Heavac 8)
Due of an error in the hardware and the firmware the first series (hardware version A and B) of the PCD2.M4x60 is not able to use the analog/ISDN or GMS modem which is connected to the RS232 of the PCD2.M4x60. The error was fixed in the hardware version C. To be able to use the modem correctly it’s necessary to have at least a HW version C and at least a FW 1.26.15 on the PCD2.M4x60.
Due of an error on the firmware installed on the PCD2.W6x5 card with fabrication date between 1835 and 1845, the PCD2.W6x5 card doesn’t work if they are plugged on PCD2.C1000 or PCD2.C2000 extension modules. But the PCD2.W6x5 cards works without problems if they are plugged in PCD1 and PCD2 CPU’s and PCD2.C100/C150 extension modules.
If a S-Bus communication is used between the PCD3 or PCD2.M5xx0 and the MB VGA panel (PCD7.D457Vxxx and PCD7.D410Vxxx) then it may not be possible to write to the PCD variables (depending of the firmware installed on the MB VGA panel).
It isn't possilbe to proceed a second homing after the first attempt faild (e.g. due to a timeout) on the PCD2.H32x modules. What is the reason and how do I get the servo running again?
In case a BACnet firmware module has been installed on a PCD3.Mxxx0 or a PCD2.M5xx0 and a timezone has been configured, the time stamp of an S-Web alarm has an offset to the PCD time. There could be the same behaviour when you are using the SNTP (Simple Network Time Protocol).
If the "MDLS144/288 Data9600 onbit" modem is connected to a "non Saia PCD® COSinus" system (PCD1.M1, PCD2.M1) then it's possible to establish a modem connection to those systems but if the same modem is connected to a "Saia PCD® COSinus" System (PCD1.M2, PCD3, PCD2.M5) then it isn't possible to establish a connection.
