Also it is possible connecting the Web Server of a PCD3.T760 using WebConnect 2.x, it is not automatically possible downloading a new I/O configuration.
A fupla file generated from the contect menu of the Fupla page navigator, the content of this *.fxp file is empty and leads to a blocked Fupla Editor when trying to import it.
The constellation of the CPU of the PCD2.M5540 and the on-board switch which is leads to the situation that (very few) telegrams may be lost. This fact can lead to the situation that the Error LED of e.g. a SASI IP Master FBox (or any communication FBox) turns red after a certain time of running communication.
Communication on port 3 (PCD2.F520) during startup can lead to a DUART HW ERROR on the PCD2.M150
PCD2.M5xx0 and the PCD3.Mxxx0 systems equipped with firmware 1.10.16 did not correctly calculate the temperature values of NI1000 temperature sensors measured with PCD2/3.W340 input modules.
This phenomenon could be caused by a missing power supply or if the current consumption of the I/O modules exceeds the maximum supply of the extension module. A missing jumper inside the PCD3.C200 can lead to this situation, too!
It can occur that the value measured from the PCD2.W3x5 / PCD3.W3x5 modules 'freeze' during a time of about 1 to 2 minutes. Afterwards, the modules function again and the measured analog input value is updated again in the application program.
Some M-Bus devices (so far only observed on a MBus water counter from the company Allmess / Actris) are very sensitive against inter-character delays.
The onboard outputs "Out0" and "Out1" of the PCD2.M5xxx are not working on hardware version "B" and "C".
The outputs of a PCD2.W525 or a PCD3.W525 need to be configured correctly. If this is the case, it is possible that a problem in the FBox leads to the fact that the outputs are not written correctly.
