Product Index   PCD3   Mxxx: CPUs   M6860 CPU with 2 Ethernet

  • PCD3.M6860

  • PCD3 Power-CPU with 2 Ethernet Interface


Presentation about PCD3.M6860

Technical Info Presentation about PCD3.M6860

EN02 Archive .pdf 3.92 MB Download

System Catalogue : PCD3

Extract PP26-215_A120 System Catalogue : PCD3

Automation Stations PCD3

DE12a New .pdf Download
EN12a New .pdf Download
FR12a New .pdf Download
IT12a New .pdf Download

PCD3 Hardware

Manual 26-789 PCD3 Hardware

DE18 .pdf Download
EN18 .pdf Download
FR18 .pdf Download
IT18 .pdf Download


Manual 27-600 IO-Modules

I/O modules for the series PCD1 | PCD2 and PCD3

ENG04 .pdf Download
FRA04 .pdf Download
GER04 .pdf Download
ITA04 .pdf Download

Systemcable and adapter

Manual 26-792 Systemcable and adapter

DE06 .pdf 1.89 MB Download
EN06 .pdf 2.00 MB Download
FR06 .pdf 1.91 MB Download
IT06 .pdf 1.95 MB Download

File System and FTP Server

Manual 26-855 File System and FTP Server

EN07 .pdf Download
IT07 .pdf Download

TCP/IP - Ethernet for the Saia PCD® Serie

Manual 26-776 TCP/IP - Ethernet for the Saia PCD® Serie

DE09 .pdf Download
EN09 .pdf Download
FR09 .pdf Download
IT03 Archive .pdf Download


Manual 26-867 TCP/IP-Enhancements

DE04 New .pdf Download
EN04 New .pdf Download
FR04 New .pdf Download

Application notes including examples PPP, DHCP, DNS and SNTP

Info Application notes including examples PPP, DHCP, DNS and SNTP

DE3 Archive .zip 14.95 MB Download
EN3 Archive .zip 14.73 MB Download

Firmware used in production

The actual COSinus FW 1.20.xx or higher for the main CPU and the extension CPU is available from the COSinus firmware page.


Update Description of the FW

Technical Info Update Description of the FW

EN01 Archive .pdf 0.62 MB Download
The internal power consumption of systems with PCD3 components can be calculated with PG5 Device Configurator
EPLAN product macros, DWG and DXF files can be found here (the dimensions of the PCD3.Mxx60 are identical to the PCD3.Mxx40)
For printing on the Labeling-Strips for PCD3-Modules please use the Device Configurator from PG5 2.1.

Good to know

No more possible to set the PCD3.M6860 in to the firmware download mode with the help of the run/stop switch (since booter version 1.24.11)
See FAQ 101948

The configuration of the PCD3.M6860 is possible since PG5 2.1.100.

There is a program example for the PCD3.M6860 available in the Getting Started section.


Application programs are stored in the onboard flash. For this reason, the CPU of the PCD3.M6860 differs in its behaviour regarding program download, backup and restore requirements from existing PCD3 CPUs.  

The CPU can remain in run during the download process, but always restarts before deploying the new program (download changed blocks in run is not yet possible).


On the PCD3.M6860, both Ethernet ports are active at the same time (and also active for the Ether S-Bus communication, if activated on the device configurator) regardless of the channel number.
The same behavior does also apply for the S-Bus communication F-Boxes, means that the channel defined in the master/slave F-Box has no effect in the relation to the two Ethernet ports.

USB connector on extension (under blue cover) is not used.

Can only be used for FW download if there is no FW (Booter only). FW download normally goes via USB 1 and Ethernet (1 or 2).



There are 2 Ethernet interfaces but only one CPU which processes the Ethernet communication -> Ethernet communication performance is not increased

Communication via Ethernet 2 uses (about 2x) more CPU power than communication  via Ethernet 1

Communication via Ethernet 2 is slower (about 2x) than via Ethernet 1

If there is heavy communication on both Ethernet interfaces the user program execution is slowed down correspondingly

PCD3 / _Firmware Classic

  • MUKE error 100xxxxxH (FAQ #101933)
  • How to find more information based on the error message "SF not loaded"? (FAQ #101568)
  • What does CSF stand for? (FAQ #101566)
  • What are the differences between firmware 1.10.51 and 1.14.23? (FAQ #101470)
  • Why can't I send more than 512 bytes using the STXT instruction? (FAQ #101468)
  • Can I have more than 16 COBs? (FAQ #101467)
  • Why is the error bit 7 or 8 set when I try to execute a "Backup DB to flash"? (FAQ #101466)
  • What are the differences between firmware 1.10.16 and 1.10.51? (FAQ #101422)
  • How to define a comma as separator in interpreted texts? (FAQ #101392)
  • Potential data loss on SD cards bigger than 256 MBytes (FAQ #101377)
  • Is the "full duplex" mode supported by the Ethernet ports of a PCD? (FAQ #101365)
  • Overview of the current production firmware versions (FAQ #101304)
  • What does "Saia PCD® COSinus" stand for? (FAQ #101297)
  • How to implement a software watchdog (FAQ #101285)
  • Why does the S-I/O communication no longer work on a PCD3 or a PCD2.M5? (FAQ #101244)
  • What is the "WebServer2" on Saia PCD® COSinus systems? (FAQ #101191)
  • Can I calulate with IEEE floating point values on a PCD system? (FAQ #101188)
  • Can I read a value from a PCD text and copy it into a register? (FAQ #101187)
  • Is it possible to search an expression within a PCD text? (FAQ #101186)
  • The XOB 8 is no longer called on the systems Saia PCD® COSinus. (FAQ #101137)
  • Why does the communication on the PCD3.F281 not work? (FAQ #101090)
  • Why does a "KRNL ERROR" or a "SWTO Error" occur? (FAQ #101069)
  • What criterias are to be fulfilled for sending e-Mails from the PCD? (FAQ #101054)
  • Why is the message: "Failed to get data on alarm.exe" displayed on the alarming page? (FAQ #100963)
  • Is it possible reading the PCD "IP address" from the user program? (FAQ #100952)
  • How does the system watchdog work? (FAQ #100908)
  • How to dump the memory of a PCD (with Saia PCD® COSinus firmware)? (FAQ #100833)
  • Why are broadcast telegramms not working anymore on the PCD3 or PCD2.M480 (FAQ #100798)
  • Why is the Port 3 on the PCD3.M5340 not running correctly in RS 485 mode? (FAQ #100765)
  • Download of PCD3 firmware fails on END command (NAK response) (FAQ #100742)
  • New firmware version names for Saia PCD® COSinus systems ( (FAQ #100741)
  • Why can't I connect a PCD3.M5xx0 over the serial PGU port? (FAQ #100737)
  • PCD3.Mxxxx Real Time Clock (RTC) corruption (FAQ #100712)
  • Can I use the character mode with XON/XOFF protocol on NT-PCD's? (FAQ #100700)
  • Download of PCD3 firmware fails on END command (no response) (FAQ #100681)
  • Download of PCD3 firmware fails with "NAK response" (FAQ #100679)
  • Different handling of the TBSY flag (in MC mode) between PCD3 / PCD2.M5 and older systems (FAQ #100655)
  • Conflict between communication module (PCD3.F1xx) and memory module (PCD3.Rxxx) (FAQ #100636)
  • allowed Firmware for PCD3.M5540 hardware version D (FAQ #100590)
  • Intelligent modules aren't correctly detected on HW version older than "D" (FAQ #100549)
  • Why is the message: "cannot create page content yet" appears from time to time (FAQ #100527)
  • PCD8.K120 doesn't work after FW download to PCD3 (FAQ #100524)
  • Why does "Sasi Slave" on Port 1 / 0 (RS232) of the PCD3 generate an error? (FAQ #100420)
  • PCD3 problem with "Real TIME CLOCK" Firmware V010 (FAQ #100387)
  • lose Hardware settings after Firmware update (FAQ #100366)
  • FW depending differences in the handling of the diagnosic flags (FAQ #100321)
  • Error LED of PCD is lit! How to find the problem? (FAQ #100269)
  • Download of the wrong FW to a PCD3 possible (FAQ #100259)
  • What EPROM burner is recommended to create firmware chips for PCD's? (FAQ #100256)
  • Firmware version naming of non-Saia PCD® COSinus systems (FAQ #100176)
  • Not all History entries can be found in the Online Help of PG5 (FAQ #100173)
  • Why is the instruction DSP not supported on Saia PCD® COSinus systems? (FAQ #100034)