With the FBox "L60x Config" the same configuration has been downloaded to all the PCD7.L60x modules but not all have the same operating mode!
If the modem is connected to the PGU port the handshake needs to be "FULL" in PG5 2.0. In PG5 1.4 it worked fine if the handshake was "Default".
When connecting a PCD over modem (with PG5 or S-WebConnect) and the connection isn't working at all or is interrupted after a short while, the data compression could be the reason.
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
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
If a software box is placed to communicate with a wrong actuator type, the message "module type" appears into the master box.
This is related to a firmware problem in the PCD3 FW 018. Update to the next official version.
If the master box doesn't recognize the address transmission then the master box gives the message "Timeout".
This error message appears if the used firmware on the CPU does not support the "active and non ACK" filter for the S-Web alarming functionality (e.g. a PCD2.M150 with firmware 0D3).
The page is properly displayed but instead of the values from the PCD a syntax error is indicated.
