The I/O address 255 is used for the hardware watchdog. Due to this fact this address can not be used as "common" input or output as written in the chapter "Hardware watchdog" from the PCD3 manual.
In case the "SBC Native Image Generation" failed during the installation of PG5 2.0 , it's possible to launch the "SBC Native Image Generation" after the installation of PG5.
On some PC systems it could be observed that a DLL installed by "Symantec Protection Agent 5.1" lead to a crash of PG5 2.0 Project Manager and Fupla.
In case more than one SD flash card produced in the year 2009 are installed on a PCD3, the PCD does not properly initialize the file systems during start up. As result the file systems can not be used
This FAQ lists some points to be considered when installing e.g. PG5 2.0.160 (or any version more recent than PG5 2.0.153). The main issue is the update of the USB device for PCD systems.
Since January 2004 for PCD1.M110 and July 2004 for PCD1.M120/130 are the FW chips soldered on the PCD1.M1x0. This is the modification 1 which was introduced on HW E but this modification can be done
If the PCD3 is equipped with the interface card PCD3.F180 the error "no card echo" can be forced into the "single-master box" during the interface initialize process.
After a successful program download the software is going to initialize the chosen interface. If this process cannot be finished successfully, an error flag will be forced and into the "master box" (s
With PG5 2.0.110 Patch 2 it is not possible using special chars like + for the phone number
