In some cases, it is necessary to replace the micro-SD memory card (uSD) of the PCD.

This FAQ describes how to replace the micro-SD memory card (uSD) which is mounted on the PCD controller's PCB (printed circuit boards)  

The attached .pdf describes how to replace the micro-SD memory card (uSD) used on the PCB of the PCD

No

Saia-Burgess Controls devices and software are not affected from Domain Name System (DNS) vulnerabilities published with the report name NAME:WRECK

-

No, Saia-Burgess Controls devices and software are not affected from AMNESIA:33 or from SUNBURST

• AMNESIA:33: Describes Security vulnerabilities in TCP/IP stacks
• SUNBURST: Is a trojan

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.

Solution:

With the FBox 'PCD3.BAT0', selectable from the ‘System information’ family it is possible to switch off the overvoltage limit check on the battery module to prevent the battery LED from being switched on and the battery error message in the application program from being activated if the battery voltage is above the overvoltage limit.

The battery voltage check is performed in the battery module and the changes made by the FBox 'PCD3.BAT0' are stored in the battery module and not in the PCD3.M5/6, PCD2.M45xx.

As all information concerning the overvoltage limit check are stored in the battery module, it is possible to make the modifications in one PCD 'A' and after the modification, to insert the battery module in another PCD 'B'.

Battery modules with hardware version < C have a factory default battery undervoltage and overvoltage check.

Battery modules with hardware version >= C have the battery undervoltage test function ex works.
The battery overvoltage is not checked.

After the FBox 'PCD3.BAT0' has deactivated the overvoltage limit check, modification 8 is activated on the battery module.

Picture shows a battery module with hardware version A and modification 1 and 3

The modification number is displayed also on PG5 Online configurator, hardware information.

After the usage of the FBox 'PCD3.BAT0' the following information is visible on the PG5 hardware information. (Modification 8 was added)

Modification number 8 is only activated for this purpose 'Overvoltage limit check disabled'.

After changes have been made with the FBox 'PCD3.BAT0', the 24VDC power supply to the PCD must be switched off and on again so that the changes relating to the battery LED, battery error message in the application program and the update of the modification number in the hardware information can be adopted.

More information are available on the online FBox help.

Overview battery module hardware version, modification, under- and overvoltage test.

The FBox library ‘SBC Maintenance’ which includes the 'PCD3.BAT0' FBox can be loaded from this FAQ, over the PG5 update manager and will be installed automatically with newer PG5 versions.

No, SBC devices are not affected from the Ripple20 zero-day vulnerabilities since none of our products uses the TCP/IP software library developed by Treck, Inc.

The device configurator gives an error when a card with 16 digital inputs or outputs is configured on base address 240 because the address 255 is reserved for the hardware watchdog!

Can I use the I/O card on this slot?
Whether the media mapping is configured or not, it is possible to put a 16 I/O card on address 240. The only condition is that the last I/O of the card (address 255) isn't used! The message "On the defined module, the last input/output with address 255 cannot be used." can be ignored for digital I/O modules (but not for analogue I/O modules)

Remark
It is planned to change the error message of the device configurator.

Please read this FAQ in case you are updating the PCD firmware from a version previous to 1.16.xx to 1.16.xx (e.g. from 1.14.23 to 1.16.16).

When updating the firmware of the PCD from a version to 1.14.xx (or previous) to version 1.16.xx the content of the memory is lost (user program, hardware configuration, register, flags etc. and the user program backup on the onboard flash).

Reason
The reason for this data loss is that the onboard flash (where the user program backup is stored) is reformatted in order to support the new backup mechanism which also does backup the confiugration of the IP Enhancements (DHCP, DNS, PPP, FTP- and Web server).
Reformatting the flash takes up to one minute right after the download of the new firmware.

• In order to avoid the loss of any data, please "upload all" before updating the firmware (for that you can "download all" after updating the firmware.
  
• Note that you'll need the USB port after the update (as your S-Bus address might be gone).
  Alternatively, you can also copy the user program to flash and upload the content of the media before the update (e.g. with the "Quick Data Transfer).
  
• In this case the program and the hardware configuration will be restored from flash after updating the firmware (for going online and downloading the media content after the FW update).

Additional remarks for PCD3 hardware bought some time ago
PCD3 systems with hardware older than "D" (and PCD3.M3020 and PCD3.M3120 with hardware older than E48) can not be updated to firmware version 1.14.xx and newer because these platforms are not equipped with enough memory to hold the firmware 1.14.xx (or 1.16.xx).
In case a FW 1.14.xx or more recent is loaded to one of these systems, the PCD will remain in the boot loader state after the download of the FW (in this state, a 1.10.xx can be loaded again).

All PCD1.M2 and PCD2.M5 systems can be equipped with a firmware 1.16. and more recent.

Firmware versions before the version 1.10.51 were not supporting retries during the "Upload/Merge" process of the BACnet configurator. In case a telegram got lost during upload of the BACnet configuration (from the PCD to the PC) the transfer was been aborted.

Symptom
During an Upload (for the function "Upload/Merge" of the BACnet configurator) all of the sudden the transfer of the configuration stops. This phenomenon is observed when a telegram is lost. This telegram loss is random, dependent on the network load.

Reason
Firmware versions before the version 1.10.51 were expecting a communication without telegram losses. In case a telegram was lost (due to network problems) the transfer was interrupted by the PCD firmware. Because of the interruption the BACnet firmware was not notified, but it remained in a state of waiting for the completion of the upload process.

Solution
The firmware version 1.10.51 (for the PCD3 or the PCD2.M5) together with the BACnet firmware 1.10.50 are more robust and can cope with telegram losses during the upload of the BACnet configuration. Please update the firmware of your PCD and the one on your PCD7.R56x to the mentioned (or later) firmware versions.

Remark
Please note that the firmware version of both, he PCD and the BACnet module must be updated.

With the Device Configurator it is possible to configure the hardware and calculate the power consumption of the modules. Before we had an Excel sheet to calculate the power consumtion.

Problem
A configuration calculated with the old Excel sheet did not have the same current limitation for the CPUs. The same configuration is maybe rejected by the Device Configurator.

Reason
The reason is, that the maximal current on the V+ is depending on the charge on the 5V power supply. The Excel sheet did not take care of this dependency. This was leading to problems in very few cases. In the Device Configurator this dependency is added to the calculation. Means that each module that charges the 5V, has as well an influence on the maximal current on the V+. Due to this reason a configuration that was declared with the old Excel sheet as o.k can now fail, when configuring it with the Device Configurator.

Solution
We recommend using the Device Configurator. If you are very close to the limit it can be sufficient to have a better power supply. If your power supply has a tolerance of -10/+10% this could be enough to guarantee the configuration to work. More informations about different Power Supplys can be fount in the PCD3 manual chapter 3.2

Some Ethernet devices do generate gratuitous ARP telegrams every time they are connected to an Ethernet network. This telegram informs the router that there is a new IP address on the network and causes it to update its internal MAC addresses table in case the according IP was already mapped to a MAC address.

Background
If a device is replaced on a network and the new device does have the same IP address, it won't be reachable until the router (or other devices that communicate with the replaced system) refreshes the MAC address table.
The gratuitous ARP telegrams are one way to inform a router about a modification of the MAC address bound to an IP address.

Does a PCD generate gratuitous ARP telegrams?
No, a PCD (e.g. a PCD3, a PCD2.M5xxx or a PCD equipped with a PCD7.F655) does not generate gratuitous ARP telegrams when being connected to an Ethernet network (when it gets a "Link"). This feature is not implemented in the stack, and there are no plans for implementing this feature into the stack of the F655 because:

• there is a relatively easy to realize workaround available
• and the gratuitous ARP telegram is only required in case PCD is being replaced (which is not very often)

How to cause the router to update its MAC address?
Instead of relying on a gratuitous ARP telegram, a simple telegram can be sent to the router device every time the link is being detected (indicated by a rising edge of the "Diagnostic Flag+6", or as in the attached code example just regularly every 60 seconds). The telegram to be sent can be done by using the Open Data mode of the PCD.
Attached you can find a small code example which could be used on a PCD3 or a PCD2.M5xx0 (given no other ODM code is implemented on the system). This code can be added to a CPU in PG5 1.4.300 project using the "Add files..." (from the context menu of the "Program Files" folder of the CPU). Additionally, plase update the symbol "RemoteIP" within this file to a fitting IP address on you network and read the header of the file for more information how to work with this code. 

Is it possible to order the battery module cover (PCD3.M5xxx) and the I/O covers as spare parts?

Yes, it is possible ordering these covers separately with the article numbers below:

• I/O cover (protection if no modul is plugged on a slot): order number 4 104 7515 0
• Battery modul cover for PCD3.M5xxx or PCD3.M6xxx : order number 4 104 7493 0

After a succesful download the PCD3 or the PCD2.M5xx0 doesn't go in run. It stays in HALT in XOB 16.

Symptom
The download option "RUN Program after succesful download" is activated. With a specific project, the CPU doesn't go in RUN. It can be started manually without problems. The installed PCD3 firmware is 1.08.23 (1.08.19 for PCD2.M5xx0 or 1.08.21 for PCD2.M480).

Reason
Due to a firmware problem, the CPU goes not in RUN if the project has a specific (big) size. The PCD3 and PCD2.M5xxx and PCD2.M480 CPU's with firmware version <=1.08.23 are concerned.

Solution
Please update the firmware of your

• PCD2.M480 to 1.08.53 or later
• PCD2.M5xx0 to 1.10.16 or later
• PCD3.Mxxx0 to 1.10.16 or later

The firmeware can be downloaded from the support site (the first firmware with the correction is 1.08.31).

Changing the Profi S-Bus settings puts the CPU in HALT with a BUS Error

Problem
If there is a Profi S-Bus configuration already running on a PCD3 and some settings in the "Hardware Settings" are changed. Per example check / uncheck PGU, the CPU goes in HALT with a Bus Error after the download.

Reason
This problem is related to a problem in the firmware

Solution
The next official firmware >03C will correct this problem. As workaround the PCD3 has to be restarted after the download of the new "Hardware Settings".

On the PCD3.M5340 the bus termination can be activated in the PG5 Hardware Settings. A relay is switching the termination on or off.

While the serial PGU port of systems before the PCD3 did always work as PGU port when connecting a PCD8.K111, the serial PGU port of the PCD3 can be configured for using a modem. If this is done, it is no longer possible attaching a PCD8.K111 and establishing a PGU connection.

Symptom
It is not possible going online with the PGU communication mode using a PCD8.K111 programming cable plugged in on the D-SUB labeled "Com/PGU" of a PCD3.M5xx0.

Reason
The port "Com/PGU" of the PCD3.M5xx0 can be used as either PGU port for programming the PCD or for connecting an external modem to the PCD3. In case a modem is connected, the full handshake must be enabled and by doing so the detection mechanism for a PGU connection established with a PCD8.K111 is disabled.
A second reason could be that the firmware 039 is installed on the PCD3. In this case a firmware problem avoids a successful serial PGU connection.

Solution
Connect to the PCD using a USB cable (which always works as programming connection) and upload the current hardware settings of your PCD3.
§ix100519§
After having uploaded the current configuration of the PCD3, check that the checkbox "Full RS232-handshaking on Port 0" is not checked. If it is checked, uncheck it and download the modified hardware configuration in order beeing able going online with a "serial PGU" connection.

If it is still not possible going online with the PCD3, please check the firmware version of the PCD3. Note that the version 039 has a known problem that avoids going online over the Serial PGU connection. In case you are concerned by this problem, please contact your local sales office and request a firmware that fixes this problem (e.g. 03A).

Explanations of what kind of external devices you need to establish a VPN. This feature is explained in

the example with BacNet.

The PCD1.M110, PCS1 and PCD3 are equipped with a supercap. This supercap needs a certain time until it is fully charged.

PCD1.M110/120
It takes about 30min. until the supercap is fully charged (5T). To keep the RAM content at least 2V are needed. The supercap contains 2V after about 5min. After this time the PCD1 will keep the data in RAM for a short time. The  buffer time (30 days for PCD1.M110 and 7 days for PCD1.M120) can only be guaranteed if the supercap is fully charged, that means after at least 30 minutes runtime.

PCS1
It takes about 45min. until the supercap is fully charged (5T). To keep the RAM content at least 2V are needed. The supercap contains 2V after about 6min. After this time the PCS1 will keep the data in RAM for a short time. The full buffer time (5..15 days) can only be guaranteed if the supercap is fully charged, that means after at least 45 minutes runtime.

PCD3
It takes about 6min. until the supercap is fully charged (5T). To keep the RAM content at least 2V are needed. The supercap contains 2V after about 1.5min. After this time the PCD3 will keep the data in RAM for a short time. The full buffer time can only be guaranteed if the supercap is fully charged, that means after at least 6 minutes runtime.

If the PIN-code is activeted on the SIM-card the following init-string is needed: ATS0=2+CPIN=nnnn\r Unfortunately this string does not work on the PCD3.

Problem
The init-string with PIN-code "ATS0=2+CPIN=nnnn\r" does not work on the PCD3.

Reason
There is a problem in the firmware. It will be corrected in the next version >030.

Solution
Until a new version is available the GSM-modem will only work if the PIN-code is deactivated on the SIM-card. In urgent cases contact pcdsupport. A bugfix version will be available soon.

There is a problem when placing a communication module PCD3.F1xx and a memory module (PC3.Rxxx) on the same PCD3.

Problem
If a communication module is per example on slot 0 of the PCD3 and a memory module is per example on slot 1, it is possible that one of them will not work. If one of the modules is removed, the remaining one will work correctly.

Reason
There is a problem in the firmware. As soon as more than one intelligent module (e.g. PCD3.F1xx, PCD3.F2xx, PCD3.R5xx or PCD3.R6xx) are plugged on the PCD3.Mxxxx the detection of the module can fail.
This problem will be corrected in firmware version 031 (but is is existent also in version 030 / $31).

Solution
As long as firmware 031 is not released the two modules will not work properly together. A workaround could be to put the memory module PCD7.R550M04 directly on the communication module. Open the memory module PCD3.R550 and remove the card PCD7.R550. Open the communication module PCD3.F1xx and plug the card on this module.

With PG5 1.4.120 and PCD3.M5/M6 it is not possible to use the internal backup memory

Problem
With PG5 1.4.120 it is not possible to configure 256MByte memory size on the PCD3.M5 / M6 therfore no backup to the internal flash is possible.

Reason
It is not supported by the current firmware

Solution
The problem will be solved with the next official firmware 030. In urgent cases ask the support team for the inofficial version $28.

the minimum firmware version for PCD3.M5540 hardware version D is V023

As written in the manual the PCD3 User LED should work like the Error LED on the battery module. That means, if an error is present it should be lit and if no error is present it should be amber. The user is able to force the LED with a SYSWR instruction.

Problem

With firmware version 024 or lower the LED is working wrong. That means the LED is off when a error is present and the LED is on when no error is present. In the next official firmware it will be corrected.

It is possible to use a SYSWR instruction in the program or in the debugger to force the LED to a USER defined status:

SYSWR instructions:

With FW 024 or lower:
SYSWR  9000
                   K 1                 ; Force the LED to off

 SYSWR  9000
                   K 0                 ; Force the LED to on

With the next official FW:
SYSWR  9000
                   K 0                 ; Force the LED to off

 SYSWR  9000
                   K 1                 ; Force the LED to on

In some cases it is the same hardware, but due to the fact that the system contains a system ID written in EEPROM we can not guarantee that a xx7 PCD works properly with Classic firmware and invers.

Therefore it is not possible to download a Classic firmware to Classic PCDs and xx7 Firmware to xx7 PCDs.

General
A PCD CPU is bought as xx7 system or as Classic system. As described above, the possibility of a conversion is not guaranteed or offered by Saia-Burgess Controls AG.
There is no service "Convert from xx7 to Classic" or similar available at the repair service.

Additional details

• PCD2.M1xx, PCD1.M1xx
  The xx7 hardware is not identical to the classic PCD hardware, as result it can not be converted by a firmware change.
• PCD2.M5, PCD2.M480 and PCD3
  While it could be possible to run a Classic PCD as xx7 PCD (depending on the hardware type etc.), it is e.g. not possible to load a Classic PCD if it was bought as xx7 system (because in this case PG5 will not accept downloading the hardware configuration as the system ID is not correct).

For the correct handling of the new flash modules PCD3.Rxxx an and the PCD3.Fxxx communication modules an "I/O module check" has been implemented in the firmware. Unfortunately this check can cause problems on older hardware versions if more than two PCD3.Cxxx modules (extension cabinets) are used.

Symptom
The communication module PCD3.F121 as well as memory modules PCD3.Rxxx do not work when more then 2 extension cabinets PCD3.Cxxx are connected to a PCD3.
It is possible that the same PCD3 was working correctly but after an update of the PCD firmware this symptom appeared. In this case with the firmware update a new I/O module check has been introduced (please refer to the table below to find out in which versions this I/O module check is implemented).

Reason
An I/O module check has been introduced for the correct identification of the modules. In this way it is possible to avoid e.g. flickering outputs of an output module if a modem is (unintentionally) configured on this I/O slot. Also flash modules can be identified properly before accessing their content.

Unfortunately this check does not correctly recognize the modules plugged in to the PCD if the PCD is equipped with an old CPLD (Complex Programmable Logic Device) version as soon as more than two extension cabinets PCD3.Cxx0 are connected to the PCD.

Solution
Upgrading the CPLD version will solve the problems as the modules will correctly be recognized by the firmware. The upgrade of the CPLD corresponds to the hardware modification 8 on the PCD3 CPUs.

Hardware version D or above
The hardware version D has a correctly programmed CPLD and will therefore also detect intelligent I/O modules if more than 2 PCD3.Cxxx extensions are connected to the PCD3 CPU. No further action is to be taken.

Hardware version
These CPUs need to be updated to hardware modification 8 (CPLD update). Once this is done these PCD3s will support all PCD3.F1xx on slot 0 and also newer intelligent modules like per example the new flash moduls PCD3.Rxxx.
The update can be done with the "Firmware download Assistant in the following ways:

Yes, it is possible to use the S-Net MPI port on the PCD3.M5xxx as free RS 485 port (S-Bus or Mode C per example).

Requirements
- Firmware Version $12 or higher is needed.
- The port has to be assigned as port 3

Wiring

DSub Pin        Signal
        1                 GND
        3               RxD/TxD-P
        8               RxD/TxD-N

The PCD3 ethernet communication stops after a few days/weeks. It doesn't respond to a ping anymore.

Problem
After a few weeks the Ethernet communitation on the PCD3 is not working anymore. No ping is possible. The rest of the program is working properly.

Reason
The problem is related to a firmware problem. A task is blocked. It happens normaly after 3 weeks. After a restart of the PCD the communication is running again.

Solution
A firmware update to version 020 is recommended when using IP-communication.

No the XOB 5 is only supported by the PCD4 and PCD6

Reason
The reason is, that the "IO Bus Quit fail" is a hardware interrupt created by the PCD4 and PCD6 I/O modules. On the PCD3 and also PCD2 I/O modules it is not supported and therfore not available.

Yes, it is implemented in the PCD3 with FW Version $12 or later. On the PCD2.M5xx0 it is supported with every firmware

The S-Net MPI-Port has to be configured as Port 3 instead of Port 10. It can be used as free standard RS 485-Port for S-Bus, to add a Bus-Terminal etc.

The wiring is:

D-Sub S-Net MPI                           S-Bus / Terminal ...
Pin
    3 RxD/TxD-P  --------------------- /TX /RX
    5 GND           --------------------- GND         
    8 RxD/TxD-N  --------------------- TX RX

After an Ethernet module has been replaced (and the IP address remained the same), it is often not possible connecting to the according PCD. The reason is that the PC "remembers" the old MAC address (which is different on every Ethernet module) and tries to connect to the old MAC address.

Symptom
After exchanging a PCD7.F65x or a PCD with Ethernet port, the communication between PC and PCD doesn't work any more. The same phenomenon can also be observed if the PCD is connected via a router (which also has a table where all IP addresses are listed together with its MAC address).

Reason
IP stations do address each other over its MAC address and not over its IP address. The first time a telegram is sent to a IP address, an ARP (address resolution protocol) telegram is sent which queries the MAC address for the relevant IP address. The destination station will then respond with its own MAC address (which will be stored by the originator of the telegram). After the MAC address has been received once, it will be stored on the originator for future use.
If the MAC address of a device changes, but the IP address remains the same, the originator of the communication (or a router or a switch in-between) needs to refresh its MAC table!  

Solution
To make the PC aware of the new MAC address, the PC needs to delete the MAC entry of the according IP address (for that it qureies it again for the next telegram). This is done automatically by the PC but takes some time.
To force a refresh of the MAC entry of an IP addres, the MAC adress of the concerned IP address in the local PC cache has to be deleted by using the arp command in the Windows Command Prompt. This can be done with the command "arp -d Entry_To_Delete":

The command prompt (screenshot above) can be launched from the Windws Start menu; Select "Execute" and type "cmd".

Short discription of  useful  ARP commands

• arp -a   display the  contents of the local cache
• arp -d   claer all contents of the correspond  IP- Adress
• ARP /?  display all possible parameter of ARP-Command
  

Remark
In case there are routers and switches in-between the PC and the PCD, also their cache needs to be deleted. This can be done by restarting the device.

No. Changing modules under tension can result in damage to the modules and CPU.

Remark
Please note that not only the PCD Power supply but also the tension on the I/Os themself (and the power supply of the I/O modules) must be removed before the modules can be removed without risk.