It is only possible to determine whether the PCD's circuit board is fitted with a Swissbit micro-SD memory card by visual inspection.

The attached document describes how to know whether the circuit board of the PCD is fitted with a Swissbit micro-SD memory card.

The attached document describes how to proceed if you want to copy csv-Files (e.g., from HDLog) and Webeditorproject files which are stored on the Intflash of a PCD.

This could be useful if you are replacing an internal micro-SD memory card which is used on the circuit board of the PCD and you want to re-use the files stored on the old micro-SD memory card.

Newer PCD types and newer PCD7.D4xx devices have micro-SD memory card (uSD) on the PCB (printed circuit boards)

The following data’s are stored on the this uSD card on the PCD’s PCB:

• Firmware for the PCD
• Device configurator settings (PG5)
• Application program done with PG5
• Webeditor 8 project (PG5)
• DATA (e.g HDLog) created by the application program in runtime
• Setup, Calibration (PCD7.D443, PCD7.D450, PCD.D470)
• Program Backup on internal Flash

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

If the PCD2/3.W220Z18 card is plugged in to a ‘Power PCD‘ or a PCD2.C1000 or PCD2.C2000 and if all 8 analog inputs channels of the PCD2/3.W220Z18 module are connected to 8 PT100 sensors then the measured PT100 temperature values of the 8 channels are not correct.

‘Power PCD’s’ are:

• PCD1.M2x20, PCD1.M2160, PCD1.M2220-C15
• PCD2.M5540, PCD2.M5440, PCD2.M4160, PCD2.M4560
• PCD3.Mxx60

To solve the issue, use and connect only up to 7 PT100 sensors to the PCD2/3.W220Z18 or do use a PCD2/3.W350 module, if all 8 PT100 are needed.

On the ‘old’ PCD’s like PCD2.M170 or PCD3.M5540 the PCD internal power supply V+ was at 24V

On the ‘new’ ‘Power-PCD’s’ and the PCD2.C1000 and PCD2.C2000 the V+ is 16,5V

The electrical design of the PCD2/3.W220Z18 was done in that the way, that the internal power V+ of 24V was required to handle all 8 PT100 channels.

Since the ‘Power PCD’s’ and the PCD2.C1000/C2000 have a V+ of 16,5V the driver on the PCD2/3.W220Z18 don’t have enough power to handle all 8 PT100 signals correctly.

To solve the issue, use and connect only up to 7 PT100 sensors to the PCD2/3.W220Z18 or do use a PCD2/3.W350 module, if all 8 PT100 are needed.

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

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.

With some specific sensor and configuration, the inputs of a module PCD2/3.W525 could perturbate an other input of the same module

Module PCD2/3.W525 are not designed as other analog input modules (as PCD2/3.W340 or W200 for example). Particularities of the module W525 are the following:

-        Galvanic separation of inputs/outputs.

-        Differential inputs/outputs.

For most of sensors, which are used in differential mode, no problem could be detected from other inputs.

With the use of non-differential sensor, when all (-) parts would be connected together, perturbation might be visible on another channel. As the W525 module has galvanic isolation and due to the design of the module, unwanted return current could appear and disturb other inputs.

If you experience such situation, there is a possibility to connect the (-) of your sensor to the gnd of the module. By doing it this, galvanic isolation of the whole module will not be valid anymore.

Therefore is a special configuration of the jumper possible.

Fbox Update of the E-Line Library causes Problem with I/O refresh in Fupla

Symptoms

PG5 2.2.140 with E-Line Fbox Library V2.1.100.
After the automatical Fbox Update in the Fupla Editor, the Projekt will be Rebuilded and downloaded into the PCD without Errors.
Checking the Funktions Online, there is no Refresh for the States of Inputs and Funktion for the Outputs visible.
An Kommunikation Error is not indicated.

Reason

An Error in the PG5 2.2.140 does not perform a clean update

Solution

Is described in FAQ 101994

In PG5 2.2.220 the Error is fixed

If you want to use the Triac on an Eline module here are the explanation how it is configurable and how it should be wired. For this example the Triac0 is used for a test with a lamp.

See on the following print screen the wiring to use the Triac. The Triac must be tested only with a charge! You can simply connect a lamp 24/230V AC on the TR0 and Nb connector.

In the device configurator choose PWM or phase control.

PWM:

Used for a slow PWM signal for radiator's valves

In the device configurator set the following settings:

Set the Triac Output 0 to PWM.

PWM Time Triac0 should be set between 30s - 600s. In this example it is set to 40s. It is the time for one PWM cycle.

Download the device configurator and you can change the value of the register TriacDutyCycle0.

It could be found in the media mapping of the Eline module. This value can be set between 0-1000 (0-100%). In this example it is set to 250 --> 25%.

The impulse will be on for 25% of the cycle. It will look like on the following print screen.

Phase control:

Used to dim a light for example.

In the device configurator set the following settings:

Set output Type 0 to phase control

Download the device configurator and you can change the value of the register TriacDutyCycle0 of the media mapping of the Eline module. This value can be set between 0-1000 (0-100%).

Dim the lamp by changing the TriacDutyCycle0 value.

1000 means lamp is On with 100%

500 means lamp is On with 50% etc.

Due to the design of E-line family, some Fboxes are not supported.

 Find below a list and a downloadable document

Concerned Products:

- PCD1.G1100-C15 Light and blind module

- PCD1.G360x-C15 Room module

- PCD1.F2611-C15 DALI module and aux. RS-485

- PCD1.W5300-C15 Analogue module

 List of supported Fbox for E-lines Series

Where is the counting limit for Energy meters and Energy Managers/ E-controllers?

What happens when they reach the limit?

The maximum energy consumption value for all counters is 9’999’999.
When a counter reaches this value, it will start counting with 0.

In the Energy Manager and in the E-Controller, the energy consumption value is handled in the firmware.
In runtime, the firmware detects only negative values.
A lower positive value is only detected during a reboot.
In this case, a counter change message appears.
Now you have two possibilities:
1:
You can do a manually reset of the counter value to 0.
That means you have to reject the proposed action on the user interface of the device. 
=> A new file is created with a higher index by the firmware.
The history bar charts are lost and the visualization starts to redraw from the current day.

2:
The second possibility is to accept the appeared proposal from firmware.
=> The history bar charts stays, but the values on the counter and on the user interface aren’t the same anymore.

This FAQ explains under which circumstances, which texts are writeable/editable during runtime.

Non-Saia PCD® COSinus Systems (PCD1.M1xx, PCD2.M1xx)
 
With Flash or EPROM Memory plugged
-          Texts < 4000 are not writeable in runtime
-          Texts >= 4000 are writeable in runtime

 With RAM Memory plugged
-          Texts < 4000 are writeable in runtime but PG5 recognizes if one of these texts has changed*
-          Texts >= 4000 are writeable in runtime


Saia PCD® COSinus-Systems
 
PCD3.Mxxx0 and PCD2.M5xx0
-          Texts < 4000 are writeable in runtime but PG5 recognizes if one of these texts has changed*
-          Texts >= 4000 are writeable in runtime
 
PCD3.Mxx60 and PCD1.M2xx0
-          Texts are configurable in the Build Options, define First Writeable Text.




*If one of these texts have changed, PG5 will give a message when you want to go online with PG5 indicating that the 
 program is not the same. Also these texts will be overwritten when the program is downloaded again. 

It is correct that the indication of a low battery will appears earlier due to more accurate prediction on a new Saia PCD® COSinus system than before on a PCD2/1.M1xx.

There are two main reasons to explain this fact:
 
- The supervision function was improved
The new battery supervision function sets the battery under a very small load to predict the end of battery capacity. In term of battery capacity, this additional load is negligible, but allows the system to warn before the battery is really empty. That gives enough time to exchange the battery and preventing memory lost. This is not the case on the previous generation, where only the voltage was supervised.
 
- There is more memory to support
The recent systems have much larger memory; the resulting standby current to be supplied from the Battery increased short the time duration.
 
Summary of working principle with the Lithium Battery
System with passive battery supervision applied on the following PCD’s:
PCD1.M130, PCD1.M135, PCD2.M110, PCD2.M120 and PCD2.M150
The voltage of the battery is supervised.
SBC advise to change the battery all 1 - 3 years.

System with active battery supervision since 2001 applied on the following PCD’s:
PCD1.M2xxx, PCD2.M170, PCD2.M480, PCD2.M5xxx, and PCD3.Mxxxx 
If the 24VDC power is switched on, then the voltage of the battery is measured during short time all 12 seconds where the battery is submitted to a small discharge.
This allows to warn the application program before the capacity of the battery reach its end.
We estimate that in this case the battery has still two days of reserve capacity for the changing of the battery.
In most recent PCD's the battery change can be done from end-user keeping the 24VDC power supply of the PCD switched ON.
If during the battery change, the 24VDC power supply of the PCD remains switched ON then there is no lost of the SRAM content (means that the PCD medias does retain there values)

A lost of the SRAM content (PCD medias like registers, flags and the application program [application program only if there is no application program stored in the Flash memory] does occurs only if the 24VDC power supply is switch off during the battery change.

The specifications in the manual concerning the typical life time of a Renata battery is still correct (1-3 years).

Today, on April 2013 we are able to give more precise lifetime expectancy for the battery for PCD’s produced since July 2012:

However SBC advices to preventable change of the Lithium battery all 5 years

Note that these values are set conservatively; longer lifetime of the battery can be achieved in the practice.

For PCD’s produced before July 2012, above mentioned times could be shorted by 20% due to larger SRam standby current.

The value of standby current is verified on each device during the production.

The information provided in the history or the "Diagnostic file" of the PCD does not always give enough information for the firmware developpers to find the reason for e.g. a crash of a PCD. If more information is required in order to trace back a crash, a dump of the whole memory (SRAM, DRAM and FLASH) of a PCD can be done. This FAQ does apply to PCD1.M2, PCD2.M480, PCD2.M5xxx, PCD2.M45x0, PCD3 (including PCD3.Mxx60) and PCD7.D4xxxT5F (Programable MB-panels).

Working principle
For dumping the memory of one of the following systems a dedicated small executable SaiaDump.exe is available as standalone tool.

• PCD1.M2
• PCD2.M480
• PCD2.M5
• PCD2.M45x0
• PCD3
• PCD3.Mxx60 (fast CPU)
• PCD7.D4xxxT5F (programmable MB-panels)

Usage of the stand alone tool SaiaDump.exe:
This tool is called by a batch file which will call an executable (SaiaDump.exe) with hardware specific parameters. The executable will establish an USB connection to the PCD and will read out the memory content. This content will be stored in 4 files and all these files will automatically be stored in a *.zip archive.

General remark:
In order to obtain all necessary information it is important that the dump is made while the CPU's memory still contains the last information.
Since this information is lost (overwritten) when the PCD re-boots, it must be achieved that the PCD does not reboot in case of a crash (e.g. Bus Error or Kernel Error).
Therefore a specific SYSWR has been implemented.
This command is to be executed on the PCD e.g. in XOB 16 before a crash occurs (on every boot, because it is reset on each power off).

Software installation of SaiaDump.exe tool

• Download the archive "SaiaDump_V1_3_006_Rev211101.zip" from this FAQ
• Unpack the *.zip archive on your PC or Laptop
• In the extracted folder "SaiaDump" you'll find several batch files (e.g. RUN_DUMP.bat or RUN_DUMP_PCD1M2xx0.bat).
  By double-clicking on the file RUN_DUMP.bat, a dump is started (make sure that PCD is connected with a USB cable and no PG5 is running)
  
  After a successful dump a new *.zip archive with the name "PCDDump_date" will be stored in the same directory.
  Please send this archive (it should contain four files with the extension *.blk or *.bin and a log file) to the support. 

Preparing the PCD
In order to cause the PCD not to reboot in case of a crash, add the following lines to the code of your CPU (and remove the watchdogs, if present).
Alternatively, you can also add and link the file "DontRestartAfterCrash.src" which is contained in the folder "PCD_Preparation" off the "SaiaDump_exe.zip" to the concerned CPU in your PG5 project.

$INIT                   ; Add the following lines to the XOB 16
SYSWR K 9999     ; Instruction to cause the PCD not to
K 1                       ; reboot after a crash
$ENDINIT

This instruction has been implemented first in PCD3 firmware version 03A.
Therefore please also make sure that FW version 03A or higher is installed on the system.
The SBC Dump tool can only dump the memory of a PCD that has boot loader version 035 (created in April 2006) or higher installed.
In case your PCD has a too old boot loader or if you are in doubt of the boot loader version of your PCD, please refer to FAQ 100680 in order to learn more about how to find out the boot loader version and how to update the boot loader version. 

Dumping the PCD memory
After the next crash, the PCD will not re-boot anymore and will blink with all tree LEDs simultaneously instead. Please note that the SYSWR K 9999 (see above) must have been introduced before the crash and the LEDs must blink in this state! In this (and only in this) situation it is possible dumping the memory of the PCD:

Use of the stand alone tool SaiaDump.exe:
Launch the SaiaDump.exe for retrieving valuable debug information (it is also possible dumping the PCD if the PCD is in boot loader state or run for test purposes, but no valuable debug information can be retrieved from these files).
For launching the SBC Dump is should be enough to double-click the file RUN_DUMP.bat.

Additional information for PCD3.Mxxx7
The same tool can also be used for dumping the memory of a PCD3.Mxxx7. But note that the usage of the SYSWR listed above is not to be used.

FAQ updates

• December 2021(Version 1_3_006_Rev211101)
  - Support also the PCD2.M45x0
• March 2013 (version 1.3.006)
  - Support also the PCD7.D4xxxT5F (programmable MB-panels)
• July 2011 (version 1.3.005)
  - created batch files for easy launch or the SBC Dump executable 
  - added log file creation during dump process
• November 2010 (version 1.2)
  - supports new hardware: PCD1.M2 and PCD3.Mxx60 (fast CPU)
  - supports the new USB driver (for 64Bit OS) 
  - removed the firmware files from the package in order to make it smaller
• June 2010 (version 1.1)
  - increased SRAM memory Dump (2 MByte) for recent PCD systems (PCD3, PCD2.M5).
  - update of firmware delivered in the package to 1.10.51. 
• Mai 2009
  Version 1.0 of the SBC Dump: This version does also dump the internal SRAM of the PCD.

The PCD CPUs can be protected with a password. Once the CPU is password protected it is not possible reading its hardware or user program any more.

How can I protect my PCD with a password?
The protection is done by configuring a password in the hardware settins and downloading this configuration (make sure you have enabled the "Password" in the download window).

How can I remove the password?
There are two possibilities to remove the password from the PCD:

• You can re-download the hardware configuration (with the password protection in the Hardware Settings unchecked). Again, make sure you have enabled the "Password" in the download window. You will be prompted for the password when downloading the new configuration.
• You can clear the whole memory of the PCD or the PCS. Doing so will not only remove the password but will erase the whole configuration and user program of the PCD! The "Clear Memory..." function can be found in the menu "Online" of the PG5 "Online Configurator".

Restrictions

• The procedure "Clear Memory..." does not yet work for all CPU types (e.g. the PCD3 memory can not be cleared with this function). (An alternative way could be removing the battery and removing the power supply in case the user program is stored in RAM).
• The minimal PG5 version featuring the "Clear Memory..." function is PG5 1.4.120.

On the PCD1, and PCD2.M110/120/150 it is possible to put a memory chip as extension memory. The table below contains a list of the supported extension memory chips for classic PCD's.

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.

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.

Yes it’s possible to connect a PCD directly to the internet, but you have to protect your PCD against unauthorised access or cyber-attacks.

To protect the PCD against unauthorised access or cyber-attacks, it’s imperatively needed to take some protective measures.

Information about protective measures can be found on the support hp

If you need a PCD with cyber security levels SL3+ and based on ANSI ISA 62443 then checkout our PCD3.M6893 (QronoX PCD), this PCD was developed for cybersecure applications.

Information's can be found here.

Some PCD types (Classic and xx7) have stored their firmware on 4 Mbit flash chips plugged on the main board. Further on the user memory/backup memory of many PCDs may be extended by mounting a flash chip. This FAQ contains a list of those memory chips in relation to the usage.

The possible applications for the 4 MBit flash chips

The possible applications for 1 MBit flash chips

Inputs / Outputs < 256 are in the process image and are read cyclic. The access can be per example: L IW 128 (Load Input Word 128)

Inputs / Outputs > 256 are not in the process image and can only be read directly, per example: L PIW 258 (Load Periphery Intput Word 258)

An EPROM was created in the same way as EPROMS for Classic PCDs are created, but it doesn't work.

Reason
The difference between classic an xx7 bin-files is, that you have to choose "Swap bytes" for the xx7 firmware. Otherwise the burned EPROM will not work.

For programming with GALEP the procedure is:
- Open the bin file
- choose the device
- choose Edit/Swap Bytes

A new firmware chip has been introduced (SST39SF040). Firmware version is 3.1

Once a firmware downgrade to a firmware version older than 3.1 is done on a flash SST 39SF040, no firmware upgrade is possible anymore.

Yes, the relevant national agents are listed on the page www.saia-pcd.com (please refer to the further down this FAQ for a direct link).

For customers from all other countries and Switzerland, our telephone hotline is +41 (0)26-672 71 11.
Available Monday to Thursday from 0800 to 1200 and 1300 to 1700 hrs and on Fridays from 0800 to 1200 and 1300 to 1600 hrs. Technical support can be provided on this line in German, English or French.

.For the xx7 series in particular, see under:

www.sbc-support.ch/xx7/xx7doc.htm .

Saia-Burgess Controls AG has implemented all the CPU functionalities in the operating system as firmware components. We do not use any "miracle chips". As a result, there is no dependence on anyone. However, it brings the customer the advantage of speedy modifications/extensions to the operating system.

System integrators without Saia PCD® experience who, for cost reasons, use the high performance/functionality of the Saia PCD® to replace a powerful Siemens controller (S7-400) in one-off projects to construct manufacturing systems. In particular, when there is an underlay of many other intelligent Siemens devices used, whose connections have not been designed exclusively on the basis of open standards. Explanation: We test and check very systematically and at great expense compatibility with such tools as Step®7 /Higraph/SCL, etc. However, we cannot and will not copy and debug the characteristics and behaviour of a powerful Siemens PLC as a system controller for Siemens "Total Integrated Automation“.

Manufacturers of standard products who see the potential of control technology for product differentiation/profiling, while simultaneously wanting to take advantage of the user acceptance and resource pool of the Step®7 environment. Explanation: These customers can make best use of the high performance/functionality of the Saia PCD® and of our high levels of flexibility and PLC competence.

Price benefits are primarily achievable when the emphasis is on communications and special solutions. Saia-Burgess Controls AG does not cover the entire spectrum of the Siemens environment, however, in many cases it has an attractive solution for OEM customers. Please also note the following 2 FAQs.

Yes, it’s possible to use the interrupt inputs of the xx7 CPU’s as normal inputs.

The address of the interrupt inputs is PEB 65534 or 65535 depending of the used xx7 CPU.

The interrupt 0 is mapped to the bit 0, the interrupt 1 to the bit 1 of the PEB 65534 or PEB 65635 and so on. 

There is no need to define any special behaviour to be able to read the interrupt inputs as normal inputs. 

Overview PCD system / number of interrupts / base input address for interrupt

Program example to read the interrupt inputs: 
L PEB65535
T MB 10

// M 10.0 is interrupt 0
// M 10.1 is interrupt 1

When going online with Step7 the LED's RUN HALT and ERROR are flashing.

Problem
The CPU is running, when connecting with the programming tool and going online it can happen that all LED's RUN HALT and ERROR are flashing.

Reason
If the CPU has an old firmware and a new version of Step 7 is used this can happen do to some new telegramms in Step7 which can not be handled by our firmware.

Solution
Update your firmware to the actual version

The actual firmware version is available on the support site. We recommend to update to the last official version.

Yes, but only on the PCD3.M5547 and on the PCD2.M487

Important note: the function "accessible nodes" will not  work, because it is not possible to scan the whole network in a few secondes.

Basically the FC's and FB's from the Siemens Library are supported. Otherwise if the FC / FB is made for a function that does not exist on our CPU, it will not work.

Problem
The function "copie RAM to ROM" doesn't work on a PCD1.M137

Reason
Probably you have choosen the wrong CPU type. When choosing a 414 CPU for a PCD1 this function won't work

Solution
Choose a 413 CPU

Yes. In addition, all PCD2.Mxx7 controllers offer the possibility of programming via a serial port (RS 232). With the PCD2.M1x7, the MPI protocol is active by default at interface A in connection with the PCD7.F120 interface module. With the PCD2.M487, the MPI protocol is active by default at interface 0 (PGU). The default transmission speed here is 19.200 Baud, but can be increased to 38.400 Baud. The MPI protocol can also be switched over to other interfaces. This requires parameters to be set for a CDB (Configuration Data Block). Detailed information about the configuration data block is provided in Manual 26/797. This documentation can be downloaded under:
www.sbc-support.ch/xx7/xx7doc.htm

Yes. When designing a project with SBC hardware, the I/O Builder software tool is required (free of charge). This tool can be downloaded from the following Internet address: www.sbc-support.ch/overview/xx7Configuration.htm

A complete list of instruction execution times is not available. Since there are other processors present with a different operating system from the Simatic controllers, it is not very meaningful to compare individual instructions. The best way to obtain a realistic comparison is to execute the application program directly on the corresponding xx7 series controller. For additional support, contact:
support@saia-pcd.com 

A complete list of instruction execution times is not available. Since there are other processors present with a different operating system from the Simatic controllers, it is not very meaningful to compare individual instructions. The best way to obtain a realistic comparison is to execute the application program directly on the corresponding xx7 series controller. For additional support, contact:
pcdsupport@saia-pcd.com 

Basically, yes. However, care should be taken to check whether any

Siemens system functions that may be used also exist in the operating system of

the xx7 series. Further information will be found in Technical Information TI

26/353 (operating system xx7) Detailed information about programming these

functions can be obtained from Manual 26/797. This documentation can be

downloaded under:
www.sbc-support.ch/xx7/xx7doc.htm

Full compatibility is not available. Xx7 series controllers are Step®7 programmable. Restrictions mainly occur when special, local modules from the Simatic communications processor and function module environments are mandatory. Due to the difference in hardware construction, they cannot be integrated into an xx7 system. In this area, SBC offers economical alternative solutions that entail little engineering expenditure. In addition, the instruction sets and module addressing of xx7 controllers corresponds approximately to those of the CPU412/414 from Siemens.

Basically, yes. The operating system of the Saia PCD® xx7 series interprets Step®7 STL code. This means that a Step®7 program is executable in all STL based languages, such as LAD, FDB, Higraph, SCL and S7-Graph, and therefore also on a Simatic controller. Program modifications will be necessary when calling system functions specific to Saia (e.g. special modules, such as for communications or to access peripherals that are not present). For more details on system functions, see Technical Information TI 26/353 (xx7 operating system) under www.sbc-support.com

Basically, yes. The operating system of the Saia PCD® xx7 series interprets Step®7 STL code. This means that a Step®7 program is executable in all STL based languages, such as LAD, FDB, Higraph, SCL and S7-Graph. Program modifications may be necessary when calling system functions specific to Siemens (e.g. special modules, such as communications processors) or accessing peripherals that are not present. For more details on system functions, see Technical Information TI 26/353 (xx7 operating system) under www.sbc-support.ch/xx7/xx7doc.htm .

Yes, it’s possible to use the interrupt inputs of the xx7 CPU’s as normal inputs.

The address of the interrupt inputs is PEB 65534 or 65535 depending of the used xx7 CPU.

The interrupt 0 is mapped to the bit 0, the interrupt 1 to the bit 1 of the PEB 65534 or PEB 65635 and so on. 

There is no need to define any special behaviour to be able to read the interrupt inputs as normal inputs. 

Overview PCD system / number of interrupts / base input address for interrupt

Program example to read the interrupt inputs: 
L PEB65535
T MB 10

// M 10.0 is interrupt 0
// M 10.1 is interrupt 1

The modul PCD3.W745 is missing in the IO Builder version 2.003.000

Problem
The analog module PCD3.W745 is not available in the current version of the IO Builder 2.003.000 (Language English)

Solution
As workaround select under Extras/Options in the IO-Builder German or French as Language. The PCD3.W745 is only missing in the Englisch version.

There are a couple of common causes for this case. Please take care of the points mentioned below.

Up to 13 free configurable rows for configuration of the I/O data exchange area can be inserted in "HW Config".

The PCD2.F770 has a limited memory area for configuration of the I/O data exchange area of 80 Bytes. Each Row in "Configuration"-tab of "DP slave properties" Window needs 5 bytes of the configuration area and 3 Empty Slots (= 15 Byte) are generated unvisible for the user. Therefore 65 Byte are left for up to 13 free configurable rows. The "DP slave properties" Window apears after a double-click on the slave-station in "HW Config" of "SIMATIC® Manager".

§ix100105§

Local SBC hardware (I/O modules) is configured with the I/O Builder. Then the I/O Builder is used to generate an STL source, which is imported into the S7 project and compiled. The hardware configuration is therefore defined in a data block (DB1, DB 511 or DB 1023). When reconstructing or modifying the HW configuration, a PCD restart (Stop/Start) is always required. The I/O Builder can be downloaded free-of-charge from Internet address: www.sbc-support.ch/overview/xx7Configuration.htm

Yes. When designing a project with SBC hardware, the I/O Builder software tool is required (free of charge). This tool can be downloaded from the following Internet address:
www.sbc-support.com

Full compatibility is not available. xx7 series controllers are Step®7 programmable. Restrictions mainly occur when special, local modules from the Simatic communications processor and function module environments are mandatory. Due to the difference in hardware construction, they cannot be integrated into an xx7 system. In this area, SBC offers economical alternative solutions that entail little engineering expenditure. In addition, the instruction sets and module addressing of xx7 controllers corresponds approximately to those of the CPU412/414 from Siemens. For applications that go beyond this, please contact us.
support@saia-pcd.com

CPU configuration (MPI address, clock memory byte, interrupt OBs, etc.) and network configuration (Profibus, Ethernet) takes place with Simatic Manager. Transferred CPU settings become effective with the transition from STOP->RUN. Addressing and configuration of I/O modules and SBC-specific CPU or interface settings take place with data blocks created using the I/O Builder software tool (available free-of-charge). This tool can be downloaded from Internet address: www.sbc-support.ch/overview/xx7Configuration.htm  Network configuration (Profibus, Ethernet) also takes place with Simatic Manager.

On older PCD’s it was possible to set the PCD3.Mxx6x in to the firmware download mode by switching the run/stop switch (below the M1 memory slot) quickly several times during the start-up of the PCD.
On newer PCD’s it’s no more possible to set the PCD in the firmware download mode with this procedure.                 

Reason:

New PCD3 power CPU’s (PCD3.Mxx6x) are delivered from factory with a new booter version.
This new booter version does change the behaviour of the Run/Stop switch on the PCD3 power CPU’s in that way, that it’s no more possible to put the CPU in the “boot” state mode by switching the Run/Stop switch (below the M1 memory slot) quickly several times during the start-up of the PCD.

The “boot” state mode is used to download the FW in to the PCD.

The following systems are concerned:
• PCD3.Mxx60
• PCD3.Mxx67
• PCD3.Mxx80
• PCD3.M96xx

Version number of the booter:
• 1.24.11 or newer

How to detect the booter version of a PCD?
Either with the information on white sticker on the back of the PCD

or from the hardware information of PG5 online configurator.

How to set the PCD in the “boot” state mode?
It’s possible to put the PCD in the “boot” state mode with the help of the Run/Halt
push button (near of the USB connector) as described in the PCD3 manual.

Extract from PCD3 manual:

Remark:

Use the Run/Halt push button to put the PCD in the “boot” state mode.
This works on all PCD’s independent of the booter version.

An update of the booter is not required on old PCD’s

The external MPI adapter which can be connected to the MPI Port of the PCD does need to be supplied with 24VDC.

Depending of the hardware version of the PCD, on some FW this 24VDC supply on the MPI doesn’t work.

The table below does show the dependency between the hardware and the firmware in relation with the 24VDC supply on the MPI port.
Classic PCD

xx7 PCD

The port numbers which have to be used on Step7 depends on the used communication module and on the place where the module is plugged in to the PCD.

General rule for the port number:

What does the error -104 of the modem library mean?

Problem
The xx7 modem library indicates an error -104.

Reason
This error indicates that an error occured during the initialisation of the port. Usually because the selected mode is not valid / supported.
Per example on the PCD3.Mxx7 the port 0 is per default configured as MPI port, see the related FAQ for more details. In case the modem library is using port 0 as well, this leads to error -104.

Solution
The default MPI configuration can be transfered to an other port (see related FAQ). In case the modem should be used with MPI protocol this has to be handled with the modem libary.

Yes, it’s possible to use the interrupt inputs of the xx7 CPU’s as normal inputs.

The address of the interrupt inputs is PEB 65534 or 65535 depending of the used xx7 CPU.

The interrupt 0 is mapped to the bit 0, the interrupt 1 to the bit 1 of the PEB 65534 or PEB 65635 and so on. 

There is no need to define any special behaviour to be able to read the interrupt inputs as normal inputs. 

Overview PCD system / number of interrupts / base input address for interrupt

Program example to read the interrupt inputs: 
L PEB65535
T MB 10

// M 10.0 is interrupt 0
// M 10.1 is interrupt 1

There is a difference in the "SBC Format" between "old" xx7 CPU's (PCD2.M127, 157, 177) and Saia PCD® COSinus based CPUs (PCD3, PCD2.M5xxx7 and PCD2.M487). The way to read analogue values from PCD2/3.W2xx and PCD2/3.W100, W3x0, W500 in the "SBC-Format" is not the same.

Due to technical reasons the "SBC format" changed for the new NT CPU's (PCD3, PCD2.M487 and PCD2.M5xx7).

For the 10 Bit analogue modules like the W200 series the format changes as shown in the table below:

* = Value

If the values should be converted from new Saia PCD® COSinus format to the old format, the following instructions can be used:

L       PEW  10     //10-Bit Saia PCD® COSinus SBC-Format
SLW  6
T      MW    10    //old 10-Bit SBC-Format

For the 12 Bit analogue modules likeW100, W3x0, W500 series the format changes as shown in the table below:

*= Value

If the values should be converted from new Saia PCD® COSinus format to the old format, the following instructions can be used:

L       PEW   70    //12-Bit SBC-NT SBC-Format
SLW  4
T      MW     70    //old 12-Bit SBC-Format

Since the default MPI port is used for CAN or Profibus protocol on the PCD3.M6xx7 port 2 can be configured as MPI port

General
Since there is no MPI port available on the PCD3.M6xx7 the CPU has to be programmed over USB or the PCD3.M6547 can as well be programmed over the profibus port. If an MPI terminal should be connected, port 2 can be activated as MPI port. It is also possible to perform programming in this case, however it is not recommended since the activation is not remanent after power-off.
Configuration
The following CDB entry is necessary to activate MPI on port 2:
§ix100687§

Note that the CDB is only parsed and applied in a STOP-RUN transition. FDL is deactivated as soon as no CDB entry is present to turn it on.

No, it's not allowed to load a PCD3 xx7 with a firmware SBC standard operation system.

a xx7 CPU with SBC standard operation system does not work with all funktionallities.

If a xx7 was nevertheless loaded with the SBC standard operation system, the original operating system can be loaded back without problems.

On PCD2.Mx57 and PCD2.M177 the request can cause a crash when requesting more than 20 entrys. The problem is corrected in firmware version 3.118

Problem
After a Diagnostic Buffer request the CPU is crashing, all LED's are blinking.

Reason
Do to a firmware problem the CPU doesn't handle the request correctly if more than 20 entrys are asked

Solution
Update to version 3.118.  

With Firmware Version 1.201 the program who was stored in PCD7.R400 was not automatically copied into the PCD’s memory when the PCD2.M487 was powered off/on without battery.

The probelm is solved in the actual firmware 1.300.

A new firmware chip has been introduced (SST39SF040). Firmware version is 3.1

Once a firmware downgrade to a firmware version older than 3.1 is done on a flash SST 39SF040, no firmware upgrade is possible anymore.

When mounted vertically, operation is possible in the range 0 ...

+ 55 °C. A document on the extended temperature range

can be downloaded under www.sbc-support.ch/certificates/certificates.htm

EN/IEC 61131-2, VDE 0160, Germanischer Lloyd, Lloyd's Register of Shipping, Det Norske Veritas, Polski Rejestr Statkow,UL-USA, American Bureau of Shipping, UL-CDN. Further information and certificates will be found under www.sbc-support.ch/certificates/certificates.htm 

No. This function is not supported. Our OEM versions of the PCD2 xx7 series offer effective protection by executing parts of the Step®7 application as an operating system extension. Further information is given in Technical Information TI 26/353 (Operating system xx7). This documentation can be downloaded under: www.sbc-support.ch/xx7/xx7doc.htm

Yes. It is activated by calling system function SFC 239 approx.

every 350 ms (320…380ms). Further information is provided in Technical

Information TI 26/353 (Operating system xx7). For detailed information on

programming these functions, consult Manual 26/797. This documentation can be

downloaded under: www.sbc-support.ch/xx7/xx7doc.htm

Yes. The PCD1.M137 has 1 interrupt input, the PCD2.M1x7 has 2 interrupt inputs (or 1 fast counter) and the PCD2.M487 has 4 interrupt inputs (or 2 fast counters) already built into the base unit. When a signal changes at the inputs (or when a count value is reached) an interrupt OB will be called in the application program. Further information may be obtained from Technical Information TI 26/353 (Operating system xx7) Detailed information on the programming of these functions may be consulted in Manual 26/797. This documentation can be downloaded under: www.sbc-support.ch/xx7/xx7doc.htm

No. System resources for any PCD concerned may be consulted in Technical Information TI 26/353 (Operating system xx7) under www.sbc-support.ch/xx7/xx7doc.htm .

Yes. With all xx7 series PCD2 controllers, the operating system can be updated via a serial port. PCD3 systems can be updated using the USB port.

PCD2.M1x7 require a PCD7.F120 interface module to do this. With the PCD2.M487, FW updates can take place directly across the PGU port. With the PCD1.M137, FW updates are only possible by changing the PROM. Further information about FW update procedures for whichever controller, and the cable required for connection to the PC's COM port, can be found under www.sbc-support.ch/overview/xx7family.htm  Just click here on the PCD required, then go to the "Firmware" heading and download instructions and the latest operating system.

Siemens system functions and SBC system functions are available. An overview of system functions is provided in Technical Information TI 26/353. Detailed information is provided in Manual 26/797. This documentation can be downloaded under: www.sbc-support.com/en/product-category/archive/oem-products/pcds-for-step7higraphscl/pcd2m177/

A complete list of instruction execution times is not available. Since there are other processors present with a different operating system from the Simatic controllers, it is not very meaningful to compare individual instructions. The best way to obtain a realistic comparison is to execute the application program directly on the corresponding xx7 series controller. For additional support, contact:
support@saia-pcd.com 

Full compatibility is not available. xx7 series controllers are Step®7 programmable. Restrictions mainly occur when special, local modules from the Simatic communications processor and function module environments are mandatory. Due to the difference in hardware construction, they cannot be integrated into an xx7 system. In this area, SBC offers economical alternative solutions that entail little engineering expenditure. In addition, the instruction sets and module addressing of xx7 controllers corresponds approximately to those of the CPU412/414 from Siemens. For applications that go beyond this, please contact us.
support@saia-pcd.com

The port numbers which have to be used on Step7 depends on the used communication module and on the place where the module is plugged in to the PCD.

General rule for the port number:

What does the error -104 of the modem library mean?

Problem
The xx7 modem library indicates an error -104.

Reason
This error indicates that an error occured during the initialisation of the port. Usually because the selected mode is not valid / supported.
Per example on the PCD3.Mxx7 the port 0 is per default configured as MPI port, see the related FAQ for more details. In case the modem library is using port 0 as well, this leads to error -104.

Solution
The default MPI configuration can be transfered to an other port (see related FAQ). In case the modem should be used with MPI protocol this has to be handled with the modem libary.

In this case the Profibus DP address has to be the same address as the MPI address. Other Profibus addresses will not be accepted or can lead to problems.

PCD3.M5547
If the PCD3.M5547 is used as S-IO Master the Profi S-IO address has to be the same as the MPI address.

PCD3.M6547
If the PCD3.M6547 is used as Profibus DP Slave on the second port (orange terminal port 2), this Profibus Slave address has to be the same address as the MPI address.

In this case the DP profile: "Universell DP / FMS" has to be chosen. Other protocols won't work due to timing problems.

The OB 86 has to be programmed

Problem
If there is a Profibus configuration on the PCD3.Mxxx or on the PCD2.M5547 the CPU goes often in STOP after startup. On a older CPU the same project worked without problems.

Reason
The new systems are faster than the old ones. Therefore it happens quite often that the CPU is already in RUN and the Profibus is not yet ready. Therefore the CPU goes in STOP.

Solution
To avoid this problem we recommend programming the OB86. In case of a Profibus error this OB is called and the CPU does not go into STOP.

No, the PCD2.M5 CPU supports only one TCP/IP address. The two Ethernet connectors ETH1 and ETH2 do act as a switch.

If you need to have two different TCP/IP addresses then you have to use a PCD2.M480 with two PCD7.F655 modules.

For more information please refer to the FAQ 100785

The PCD3.Mxxx7 do use the TCP/IP port 102 in relation with the TCP/IP communication from/to Step7

If you want to access from Step7 to a PCD3.Mxxx7 over an ADSL router then you have to configure the ADSL router in that way, that he do reroute the port 102 to the TCP/IP address of the PCD3. 

It is only possible to read out a maximum of four continuous bytes using load instructions that access the I/O's or the process image input table.

Problem
If you are transmitting per example from a SBC Slave a 16 word  output or input. It is not possible to handle this with the process image input table or with the I/O access.

Solution
To read or write more than four continuous bytes the system functions SFC14 and SFC15 are available.

When using a PCD7.F772 or PCD7.F802 on a PCD2.M1x7 with FW Version 3.110 only the RS 485 communication works. Otherwise the Profibus / LON communication did not work.

Problem
A module PCD7.F772 (Profibus with additional RS 485 port) or PCD7.F802 (LON with additional RS 485 port) is in use. The RS 485 port is working but the Profibus / LON communication does not work.

Reason
Do to a firmware problem these modules are not correctly supported by the firmware. PCD7.F770 or PCD7.F800 will work correctly.

Solution
Update to firmware versio 3.114 or higher

The serial communication on Port 0 works only when the PCD3 (or PCD2.M5547) is switched off, Run/Stop switch is set to Stop.

Problem
The serial communication on Port 0 works not properly.

Reason
Per default the Port 0 is assigned as MPI-Port. This configuration has to be switched to another port, otherwise the Port 0 can not be used for serial communication

Solution
Add the following CDB 1023:

Note that the O in the part 8,O,1 is a letter O for Odd and not a zero. It only works when the implemented CDB has exactely the entrys shown in the picture above (case sensitive).

The CP 342-5 can be slave in a network where a Saia PCD® is Master. The network configuration has to be the same in the Siemens Project as in the SBC Project. You have to import the GSD-File of the CP to the SBC DP-Configurator.

The CP 342-5 is connected to a Siemens CPU (p.e Simatic S7-300). This CPU can be a part of an other DP Network.

Important
The CP 342-5 will only communicate it you call FC1(DP_send), FC2(DP_recv), and FC4(DP_CTRL) in the CPU where the CP is connected to.

Due to performance reasons we decided to renounce the implementation of checks in SFC14/15. Since already with OB86 a loss of a DP slave can be detected a valuable workaround exists for this restriction.<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

A MPI-communication can be done over a serial RS 232 port of each PCD2.Mxx7

Per default the MPI serial Port is on Port 1 (PCD2.M127/M157/M177) or on Port 0 (PGU M487). The only equipment you will need to realise a MPI connection is a serial interface PCD7.F120 and a cable:

D-Sub 9-pol                screw terminal port 1
        2  ------------------------------- 11
        3  ------------------------------- 12
        5  ------------------------------- 10
        7  ------------------------------- 14
        8  ------------------------------- 13

(for M487 on port 0 you will need a PGU cable PCD8.K111)

With the I/O-Builder you can configure each other RS 232-port as MPI-serial port.

SIMATIC® CPUs with integrated CPU (e.g. 414-2DP) do not support FDL-Connections. Therefore a 400 CPU has to be extended with a CP443-5Ext. to use this service:

§ix100124§

For the Operating mode the selection DP Master must be activated:

§ix100125§

Finally choose the profil "Universal (DP/FMS):

 §ix100126§

For the specific FDL connections the SAPs 1-39 are reserved. Broadcast is not supported. Instead broadcasts can be projected. Also for broadcasts the SAP number must be smaller as 40.

No, "DPV1" is not supported! It is absolutely necessary to chose the "S7-compatible" mode.

There are a couple of points to take care. Please read the explanations mentioned below.

1. The "Save configuration data on the CPU" option of the "CP 443-5Basic" must be checked. Unfortunately not every selectable CP supports this option. Therefore a CP must be chosen (e.g. 6GK7 443-5FX01-0XE0 V3.1) that supports this option.

§ix100118§  

2. It is strongly recommend to use "Universal (DP/FMS)" Profile, which will adapt and set up all the bus parameter to work correctly with the selected speed. If this option is selected it will not be possible for the user to change any bus parameter.

§ix100115§

3. You must not use CREF number = 1 which is not available on FMS module PCD7.F700.

§ix100116§

4. Do not use the LSAP = 58 for "Master to Master" connections since this LSAP is normally reserved for "Master to Slave" connection.

§ix100117§

No! The hardware flow control is allways on so it is necessary to wire the signals RTS-CTS correctly! If the XX7 communicates with a device that does not support this kind of flow control, RTS-CTS can be bridged on the PLC.

Modem drivers sends/receives during initialisation and call process telegrams to/from modem. Be sure that your application wan't send/receive also telegrams during this phase.

Never send/receive telegrams until the "CONNECT"-flag of the Modem driver is not high!

Up to 13 free configurable rows for configuration of the I/O data exchange area can be inserted in "HW Config".

The PCD2.F770 has a limited memory area for configuration of the I/O data exchange area of 80 Bytes. Each Row in "Configuration"-tab of "DP slave properties" Window needs 5 bytes of the configuration area and 3 Empty Slots (= 15 Byte) are generated unvisible for the user. Therefore 65 Byte are left for up to 13 free configurable rows. The "DP slave properties" Window apears after a double-click on the slave-station in "HW Config" of "SIMATIC® Manager".

§ix100105§

. A description of

the library is also available at that address.

The PCD7.F80x LON interface module, the Snet 32 design tool for xx7 (which you can download free-of-charge under www.sbc-support.ch/pcd7/fxxx/f8xx/pcd7f8xx.htm ) and a binding tool (which is not available from Saia-Burgess Controls AG).

it.

Yes, this is possible with the PCD2.M177 and PCD2.M487. Please read the rules that must be respected in "Details".

Depending on PCD type, up to 8 interfaces are available. Which PCD supports how many interfaces and with which topology can be found on the support page.

Link to the communication overview page on the suppor site: 
www.sbc-support.ch/overview/xx7family.htm

Protocols supported free-of-charge by the operating system:

• DK 3964 (R) / RK512
  can be found in Manual 26/794 (Serial communication) under:
  www.sbc-support.ch/overview/xx7Communication.htm   

• Modbus ASCII or RTU (as well as Modbus TCP or UDP) 
  supported by the PCD3 and the PCD2.M5547 starting with firmware 1.10.17 (support of Modbus on PCD2.F2xx0 or PCD3.F2xx starting with 1.14.25).
  For more information please refer to the product page of the according system.

Remark
Additionally to the features directly implemented in the firmware, the following protocol implementation developped by our system partners are/were present (the following information could be outdated):

• holgerbischoff.onlinehome.de/html/modbus.html (Modbus)
• www.ludwig-systemelektronik.de (Modbus, Genibus, M-Bus, S-Bus) Module: LS2-F660

Connection of OPs from Saia-Burgess Controls AG or from external manufacturers, global data communications, data exchange via system functions SFC 65-69 (X-Put, X-Get, etc.) The maximum number of stations in an MPI network is 126. The maximum number of CPUs in a global data table in the Simatic-Manager is 15.

Yes. One of our system partners sells a solution in the form of a Step®7 program library. Further information will be found under:  holgerbischoff.onlinehome.de/html/modbus.html Alternatively, you can use a communications module (which plugs in as an I/O module) from another system partner to implement the Modbus protocol. Further information will be found under: www.ludwig-systemelektronik.de Module: LS2-F660
This solution can be used for old systems PCD2.M1x7 and PCD2.M487.
On the PCD3.M5547 and PCD2.M5547 Modbus is implemented in the firmware. Further information is available on the support site.

Yes it's possible that the xx7 PCD does communicate with S-Bus.

For serial communiction:
S-Bus can be implemented using a communications module (which plugs in as an I/O module) from one of our system partners. Further information will be found under: www.ludwig-systemelektronik.de Module: LS2-F660

For Ethernet communication:
If the xx7 PCD is equipped with a TCP/IP card then this PCD is able to act as Ether-S-Bus slave.
More information's could be found on the TCP/IP manual for xx7.

Yes. At present, the following connections can be planned with the PCD2.M157/177 and M487:
- UDP connection
- TCP connection (active/passive)
- ISO on TCP connections (active/passive).
The PCD2.M487 can continue to be programmed via Ethernet. The maximum number of simultaneous connections on Ethernet TCP/IP from/to a PCD (per PCD) is 9 for the PCD2.M157 and 64 for the PCD2.M177/M487. The following OPC servers have been tested:
Company: Ipas: www.ipas-systeme.de/index2.htm  
Company: Inat: www.inat.de 
Company: Langner : www.langner.com
download: www.langner.com/php/nav_4/nav_4_4/nav_4_poweropc.htm 
with Siemens protocol “ISO on TCP”

MPI communication, Profibus-DP, Profibus-FDL, Profibus-FMS, LON,

TCP/IP, serial communications (8 protocols integrated

in the operating system). Further information can be found under: www.sbc-support.ch/overview/xx7Communication.htm 

Saia PCD® are designed to have many communications interfaces directly integrated in the CPU (with plug-in modules up to 8 pcs) and to allow implementation of bus/network gateway functionality (e.g. LON-Ethernet).

With the PCD2.M487, Profibus layers 1 + 2 are implemented as part of CPU FW. This allows an open, multi-protocol operation (e.g. HTTP; MPI and DP in parallel). Saia PCD® users therefore have seamless functional consistency and continuity between Profibus and Ethernet.

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.

Various modules are available: fast counter cards (PCD2.H11x), modules for controlling stepper motor drives (PCD2.H210), modules for controling servo-drives in both single and dual axis versions (PCD2.H31X/H32x). Further information about this is available in Manual 26/757under: www.sbc-support.ch/xx7/xx7doc.htm . Motion modules are supported by a Step®7 library. These can be requested by e-mail addressed to support@saia-pcd.com.

Not all modules are electrically isolated. For detailed information, please see Technical Information TI 26/359 (digital I/O modules) and TI 26/358 (analogue I/O modules). These can be downloaded under www.sbc-support.ch/xx7/xx7doc.htm.

A large number of digital/analogue input/output modules, counting and measuring modules and motion modules are available. For detailed information, please see Technical Information TI 26/349 (PCD2: The PLC with integral added benefit). This can be downloaded under www.sbc-support.ch/xx7/xx7doc.htm.