Integration Overview
The SIMATIC S7-400 and the Modicon Quantum PLC are both mature, high-availability controllers used in process and infrastructure applications. The S7-400, documented on the Siemens S7-400 product page, is positioned as the process controller for data-intensive tasks with availability commitments extending beyond 2035. The Modicon Quantum (140 CPU series) is a Schneider Electric platform with on-board Modbus, Modbus Plus, Ethernet TCP/IP, and a slot-based Profibus DP master/slave module. Because the two platforms were never designed as a tightly coupled pair, integration requires selecting a common fieldbus or industrial Ethernet and provisioning the correct communication processor (CP) modules on each side.
Three viable integration paths exist in practice:
- Profibus DP – preferred when the S7-400 CPU already has an integrated DP port and the Quantum rack can accept a Profibus DP module such as the 140 CRP 811 00 (DP master) or the 140 CRA 211 10 (DP slave).
- Modbus RTU/TCP – used when both controllers already expose Modbus and the application does not demand high-speed deterministic I/O.
- Ethernet TCP/IP – used when an enterprise or process LAN is already in place; the S7-400 requires a CP 443-1 and the Quantum CPU has a built-in Ethernet port.
- Download the latest GSD for the 140 CRA 211 10 from the Schneider Electric vendor portal. Filename pattern:
schne0E1.gsdorqnt_0F29.gsddepending on firmware revision. - In STEP 7 HW Config, choose Options > Install GSD File and select the GSD archive.
- After installation, the Quantum slave appears in the HW catalog under PROFIBUS DP > Other Field Devices > Schneider Automation > Quantum.
- Drag the slave to the Profibus subnet, assign a Profibus address (range 1–125; avoid 0, 126, 127).
- Insert I/O modules from the slave's slot catalog. Typical modules: 16 DI, 16 DO, 8 AI, 4 AO, 4-word status/control. Each module maps to a defined length in the S7-400 process image.
- Set the slave's diagnostic interrupt and watchdog behavior under Properties > DP Slave.
- FC 03 (Read Holding Registers) – primary polling function for status, setpoints, measurements.
- FC 06 (Write Single Register) – command writes (start, stop, mode select).
- FC 16 (Write Multiple Registers) – bulk parameter download.
- FC 04 (Read Input Registers) – read-only analog data; equivalent to FC 03 on input-only registers.
- FC 01/02 (Read Coils / Read Discrete Inputs) – bit-level status.
- Insert CP 443-1 in HW Config, assign IP address, subnet mask, router if any.
- Configure ISO-on-TCP (RFC 1006) connection or TCP native connection. For Unity Pro on the Quantum side, ISO-on-TCP is uncommon; use plain TCP or Modbus TCP.
- Configure S7 connection in NetPro: Insert New Connection > TCP connection / ISO-on-TCP.
- Define a TSAP / port pair: typical Siemens default ports are 102 (ISO-on-TCP) and 2000 (TCP send/receive). For inter-platform open TCP, use port 2002 on Quantum with S7
AG_SEND/AG_RECV. - Use FB12 (
BSEND) / FB13 (BRCV) for block-oriented transfer, or FC5 / FC6 for short data. - Open Project Browser > Communication > Ethernet.
- Add an Ethernet network, assign IP and subnet mask matching the S7-400 CP 443-1.
- Add a TCP/IP Service or Modbus TCP device entry; set the IP address of the S7-400.
- For raw TCP open-socket exchange: use DATA_EXCH blocks with ADDM / READ_ADDR / WRITE_VAR function blocks.
- For 16-bit integers: swap bytes on the S7-400 side before writing to the Profibus/Modbus frame. The S7-400 is big-endian on the wire; Quantum, AB, and most Modbus slaves are little-endian.
- For 32-bit REAL (IEEE 754): the S7-400 uses big-endian IEEE format; the Quantum REAL is also IEEE 754 but little-endian word order. Two byte swaps are required, equivalent to a DWORD swap.
- For bit-packed data (e.g., 16 status bits in one word): byte-swap is acceptable because the bit position within the byte does not change – only the byte order in the word.
- Byte 0 = station status 1 (Profibus standard)
- Byte 1 = station status 2
- Byte 2 = station status 3
- Byte 3 = master address / diagnostic master flag
- Bytes 4–5 = manufacturer-specific identifier (Schneider = 0x0021)
- Bytes 6+ = module status, channel diagnostics
- Integrated DP port conflict. Many S7-400 CPUs (e.g., 6ES7 416-2XK02) have a built-in MPI/DP port. When the MPI panel connector is in use for HMI, the integrated DP is unavailable. Resolve by adding CP 443-5 Extended in a separate slot, or reassign the integrated port to DP-only in HW Config.
- Quantum DP slave slot count. The 140 CRA 211 10 supports up to 16 logical slots. Attempting to insert more modules from the GSD causes a Profibus configuration error, not a Unity Pro compile error.
- Modbus byte swap default. STEP 7 CP 441-2 Modbus master driver default is No Swap. Failure to enable Swap when communicating with a non-Siemens Modbus slave produces inverted 16-bit values without any fault indication.
- Ethernet connection resource exhaustion. Both CP 443-1 and the Quantum CPU allocate connection resources per configured peer. Pre-allocate all S7 connections in NetPro before downloading; otherwise, an incomplete resource map causes intermittent connection drops under load.
- GSD version mismatch. A Quantum DP slave firmware update (e.g., 140 CRA 211 10 firmware V2.6) may require a newer GSD file from Schneider. Old GSDs cause Profibus station-not-found errors during power-up of the Quantum rack.
- Hot Standby considerations. Quantum Hot Standby with CRP 811 00 in both primary and standby racks requires consistent GSD configuration on both sides, plus identical Profibus address on the standby rack's module (the redundancy is transparent at the DP layer).
- F-CPU safety DP. PROFIsafe cannot pass through a Quantum DP slave. PROFIsafe requires Siemens F-CPU on both ends. If safety data must cross, plan a separate path with a paired Siemens safety PLC.
- Time synchronization. Use CP 443-1 SIMATIC time-of-day synchronization (NTP or LAN) on the S7-400 and the Quantum NTP client on the Ethernet port to align event logs across platforms.
- Confirm Profibus cable is terminated at both ends only; intermediate nodes must be pass-through. Verify with a BT200 Profibus tester or by reading the CP 443-5 diagnostic buffer for "bus OK."
- In STEP 7, open HW Config > Profibus Diagnostics; all slaves must show "Slave OK" and "I/O OK" with green indicators.
- Force a digital output bit on the S7-400 side and read back the corresponding input bit on the Quantum (Profibus DP loopback) and verify within one DP cycle.
- For Modbus path, poll register 40001 from the S7-400 using FC 03 and verify the Quantum value reflects the forced tag within the configured scan time.
- For Ethernet path, execute
AG_SENDwith a known payload and verify with Wireshark on a mirror port that the TCP frame completes the three-way handshake and that the Quantum acknowledges within 100 ms. - Power-cycle the Quantum rack and confirm the S7-400 re-establishes Profibus operation without a STEP 7 download.
- Verify diagnostic interrupts (OB82) are not queued during a 24-hour soak test. A persistent OB82 indicates wiring or GSD issues.
- Capture the diagnostic buffer of both CP 443-5 and the Quantum CRP/CRA at end of FAT; both should be empty of warnings.
Each path has distinct hardware, firmware, and configuration implications. The remainder of this reference expands each path with hardware catalog numbers, GSD requirements, register mapping conventions, and commissioning checks.
Prerequisites and Hardware Selection
Before commissioning any of the three paths, verify the following:
| Item | S7-400 Requirement | Quantum Requirement |
|---|---|---|
| CPU firmware | Firmware ≥ V5.x recommended for CP 443-5 Extended; V6.x for current S7-400 CPUs (e.g., CPU 414-3, CPU 416-3, CPU 417-4) | Unity Pro / Concept / Modsoft compatible firmware; CRP 811 00 firmware ≥ V2.0 |
| Engineering tool | STEP 7 V5.5 SP4 or STEP 7 (TIA Portal) for F-CPU and newer HMIs; classic STEP 7 remains the norm for S7-400 Profibus configuration | Unity Pro (EcoStruxure Control Expert) ≥ V13 for Quantum |
| Backplane slot | CP occupies a dedicated slot in the central rack (CR) or expansion rack (ER) with P-bus access; cannot share with IM | Profibus module occupies a Quantum local backplane slot; cannot be used in RIO drop |
| Bus terminations | Active Profibus terminator (6ES7 972-0DA00-0AA0) on both ends of the segment | Same Profibus DP termination rule applies |
| Cable | Profibus DP cable (6XV1 830-0EH10), 2-wire shielded, characteristic impedance 150 Ω | Same Profibus cable type |
Path 1 – Profibus DP Integration (Recommended)
Profibus DP is the most deterministic of the three options and the only path that provides cyclical I/O at the standard 1.5 / 3 / 6 / 12 ms Profibus update rates. The S7-400 typically acts as the DP master because the CPU (e.g., 6ES7 414-3XJ04-0AB0) has an integrated DP port or because the rack carries a CP 443-5 Extended.
Hardware Catalog Numbers – Profibus Path
| Function | Siemens Part | Schneider Part |
|---|---|---|
| DP master module (S7-400) | CP 443-5 Extended, 6GK7 443-5FX02-0XE0 (most common); legacy 6GK7 443-5DX04-0XE0 | — |
| DP slave module (Quantum) | — | 140 CRA 211 10 (DP slave) or 140 CRP 811 00 (DP master) |
| Profibus connector | 6ES7 972-0BB52-0XA0 (90°), 6ES7 972-0BA52-0XA0 (35°), or 6GK1 500-0FC00 with diagnostics LED | 490 NAD 911 03 / 490 NAD 911 04 Profibus connector |
| Repeater | 6GK1 500-0AB10 (OLM) or 6ES7 972-0AA01-0XA0 active RS485 repeater | Same Siemens repeater acceptable |
| GSD file | (S7-400 as master – master GSD not required) | Schneider_GSD for Quantum DP slave module – import into STEP 7 HW Config |
GSD File Installation and Hardware Configuration
When the Quantum is the Profibus DP slave and the S7-400 is the DP master, the Schneider GSD file must be imported into STEP 7:
If the S7-400 is the DP slave (less common) and the Quantum 140 CRP 811 00 is the master, the S7-400 GSD is named siem8010.gsd (for CP 443-5) and is configured inside Unity Pro as a generic Profibus slave with the correct I/O length matching the S7-400 hardware configuration.
Address Mapping Convention
Profibus DP cyclical data lands in the S7-400 process image based on slot order. With the Quantum slave configured with, for example, 16 DI / 16 DO / 8 AI / 4 AO, the mapping in the S7-400 is:
| Quantum Slot | Module | Length | S7-400 I-Address (PIW/IB) | S7-400 Q-Address (PQW/QB) |
|---|---|---|---|---|
| 0 | 16 DI | 2 bytes | IB 0 – IB 1 | — |
| 1 | 16 DO | 2 bytes | — | QB 0 – QB 1 |
| 2 | 8 AI | 16 bytes | PIW 2 – PIW 17 | — |
| 3 | 4 AO | 8 bytes | — | PQW 2 – PQW 9 |
| 4 | Status/Control | 4 bytes | ID 18 – ID 21 | QD 2 – QD 5 |
Mapping is purely cyclic; acyclic parameter data (DPV1) requires Class 1 or Class 2 master services and is enabled in the Quantum via Unity Pro > DPV1 Parameters if firmware permits.
Path 2 – Modbus Integration (Serial or TCP)
Modbus is the universal fallback when Profibus hardware is unavailable or when the application is supervisory data exchange (telemetry, setpoints, status) rather than tight I/O. The Quantum CPU has built-in Modbus master/slave on the Modbus (RS-485) port and Modbus TCP on the Ethernet port. The S7-400 requires a CP 341 or CP 441-2 for serial Modbus, or the CP 443-1 with Modbus TCP for Ethernet Modbus.
Hardware Catalog Numbers – Modbus Path
| Function | Siemens Part | Schneider Part |
|---|---|---|
| Serial Modbus master/slave | CP 441-2 (6ES7 441-2AA05-0AE0) with Modbus master/slave driver loadable; CP 341 (6ES7 341-1AH02-0AE0) with Modbus master driver | Built-in Modbus RS-485 port on Quantum CPU front panel |
| Modbus TCP | CP 443-1 (6GK7 443-1EX20-0XE0 or 6GK7 443-1GX20-0XE0 for IPv6) | Built-in Ethernet port on Quantum CPU (no extra module needed) |
| Modbus driver license | Modbus master license for CP 441-2: 6ES7 870-1AA01-0YA0 | — (license-free on Quantum) |
| Loadable driver | STEP 7 > CP 441-2 > Modbus Master V3.1 or Modbus Slave V2.1 | — |
Modbus Function Code Set
Use the following standard function codes – both controllers implement them natively:
Register Addressing – Word Swap Consideration
The Quantum uses Modicon-style 4xxxx / 3xxxx / 1xxxx addressing. The S7-400 stores integers in big-endian (high byte first) format, while the Quantum traditionally uses little-endian for 16-bit words. The CP 441-2 Modbus driver offers a byte-swap toggle; failing to enable this swap is the single most common field defect in S7-400/Quantum Modbus integration.
| Quantum Register | Quantity | Function Code | S7-400 DBW address (with byte swap enabled) |
|---|---|---|---|
| 40001 – 40016 | 16 status words | FC 03 | DB100.DBW 0 – DBW 30 |
| 40017 – 40024 | 8 setpoint words | FC 03 / FC 06 | DB100.DBW 32 – DBW 46 |
| 30001 – 30032 | 32 measurement words | FC 04 | DB101.DBW 0 – DBW 62 |
| 00001 – 00032 | 32 bit flags | FC 01 | DB102.DBX 0.0 – DBX 3.7 |
Path 3 – Ethernet TCP/IP Integration
Ethernet is the cleanest integration path when both controllers are on the same plant LAN. The S7-400 requires a CP 443-1 for industrial Ethernet communication; the Quantum CPU has a built-in Ethernet port capable of Modbus TCP, EtherNet/IP (scanner/adapter), and the legacy TCP/IP open socket protocol.
Hardware Catalog Numbers – Ethernet Path
| Function | Siemens Part | Schneider Part |
|---|---|---|
| Ethernet CP | CP 443-1, 6GK7 443-1EX20-0XE0 (IPv4); 6GK7 443-1EX30-0XE0 (advanced); 6GK7 443-1GX20-0XE0 (IPv6) | Built-in 10/100 Ethernet on every Quantum CPU (140 CPU 651 / 671 / 672 / 672 60 / 678 61) |
| Industrial Ethernet switch | SCALANCE XC-206-2SFP (managed) or X108 (unmanaged) | Same; ConneXium TCSESM unmanaged / managed |
Configuration Steps – S7-400 Side
Configuration Steps – Quantum Side (Unity Pro)
Connection Limits and Watchdog
The CP 443-1 supports a maximum of 64 ISO-on-TCP connections and 64 TCP connections, of which one is reserved for STEP 7 programming. The Quantum CPU supports up to 64 concurrent Ethernet connections. Configure a keep-alive / heartbeat of 5 s on each side to detect dead peers within one cycle; otherwise the TCP stack may hold a half-open socket for several minutes.
Data Mapping and Byte-Order Discipline
Cross-platform integration failures are dominated by endianness and word-alignment mistakes. Apply the following rules:
Diagnostics, Fault Codes, and Error Codes
CP 443-5 Extended Diagnostic Buffer Codes (Profibus)
| Code | Meaning | Action |
|---|---|---|
| 0x0001 | Bus fault – short circuit or missing terminator | Verify 220 Ω terminator at both ends, check for shield ground loops |
| 0x0002 | Slave not found – address mismatch | Confirm Profibus address in HW Config matches CRA 211 10 rotary switches |
| 0x0004 | Configuration fault – GSD mismatch | Re-import GSD; verify I/O length matches module insertion |
| 0x0008 | Diagnostic interrupt from slave | Read slave diagnostic block via DP RD_REC (SFC59) |
| 0x0010 | Watchdog timeout | Increase DP cycle time or check cable length / repeater |
CP 441-2 Modbus Status Codes
| Status Word | Meaning |
|---|---|
| 0x0000 | Job completed successfully |
| 0x7000 | Job still active – wait or rescan |
| 0x80C8 | Modbus exception 08 – CRC error from slave (rejected, retry) |
| 0x80C1 | Modbus exception 01 – illegal function (FC not supported) |
| 0x80C2 | Modbus exception 02 – illegal data address (register out of range) |
| 0x80C3 | Modbus exception 03 – illegal data value |
| 0x80C4 | Modbus exception 04 – slave device failure |
| 0x80D1 | No response from slave – timeout, address, cable, or terminator issue |
Quantum Diagnostic Words (Unity Pro)
For the 140 CRA 211 10 DP slave, the diagnostic block returned to the S7-400 master includes:
Performance and Timing Constraints
| Path | Typical Cycle / Refresh | Max Payload per Cycle | Determinism |
|---|---|---|---|
| Profibus DP at 12 Mbit/s | 1.5 ms – 12 ms configurable | 244 bytes I / 244 bytes O per slave | High – hardware-driven, OB1 cycle |
| Modbus RTU at 19.2 kbit/s | 50 ms – 200 ms per transaction | 125 registers per FC 03 / FC 16 | Medium – half-duplex, polled |
| Modbus TCP at 100 Mbit/s | 10 ms – 50 ms per transaction | 125 registers per request | Medium – TCP retransmits can extend |
| Ethernet TCP/IP open socket | Application-defined; typically 50 ms – 1 s | Application-defined (up to 8 KB BSEND/RCV) | Low – best-effort TCP |
For control loops with sub-100 ms requirements, Profibus DP is the only practical option among the three. Modbus TCP can achieve 10 ms in a single-pair configuration but loses determinism under switch congestion.
Field-Proven Caveats and Edge Cases
Verification and Commissioning Checklist
Selecting the Right Path
Use the following decision matrix when commissioning a new integration:
| If the application requires… | Choose |
|---|---|
| Cyclical I/O at 1.5 – 12 ms, deterministic, hard real-time | Profibus DP |
| Sub-50 ms supervisory exchange with existing plant Ethernet | Modbus TCP |
| Existing RS-485 cable plant, low bandwidth, slow setpoint changes | Modbus RTU |
| Bulk data (≥1 KB messages), event-driven, file transfer | Ethernet TCP/IP with BSEND/BRCV |
| Safety data exchange | Not supported across vendor boundary – use a Siemens F-CPU pair instead |
Does the S7-400 always need a CP 443-5 for Profibus DP communication with a Quantum PLC?
Not always. Most S7-400 CPUs (CPU 414-3, 416-3, 417-4) include an integrated MPI/DP port that can be configured as a DP master. Use CP 443-5 Extended (6GK7 443-5FX02-0XE0) when the integrated port is committed to MPI for HMI panels, when more than one DP subnet is required, or when DPV1 acyclic services are needed.
Where can I obtain the GSD file for the Quantum 140 CRA 211 10 Profibus slave?
Download the GSD from the official Schneider Electric vendor portal under the Modicon Quantum product section. The file name typically follows the pattern schne0E1.gsd for legacy revisions and qnt_xxxx.gsd for current firmware. Import it into STEP 7 with Options > Install GSD File, then the Quantum appears in HW Config under PROFIBUS DP > Other Field Devices > Schneider Automation > Quantum.
Why are my Modbus 16-bit integers inverted when reading from the Quantum PLC?
The S7-400 transmits Modbus words in big-endian order, while the Quantum and most Modbus devices expect little-endian. Enable the Byte Swap option in the CP 441-2 Modbus master driver (protocol settings) or in the CP 343-1 Modbus TCP block. For 32-bit REAL values, perform a full DWORD swap to reconcile IEEE 754 byte ordering between the two platforms.
Can I run PROFIsafe safety telegrams through a Quantum DP slave to an S7-400 F-CPU?
No. PROFIsafe is a Siemens safety protocol that requires a paired Siemens F-CPU on both ends of the safety relationship. PROFIsafe telegrams cannot be transparently transported through a Schneider DP slave. Implement safety functions with two Siemens F-CPUs in series, or use separate safety relays.
What is the maximum number of S7 connections the CP 443-1 supports with the Quantum Ethernet port?
The CP 443-1 supports up to 64 ISO-on-TCP connections and 64 TCP connections, with one TCP connection reserved for STEP 7 programming. The Quantum CPU supports up to 64 concurrent Ethernet connections. In practice, a single S7-400 to single Quantum integration consumes 1 TCP connection, leaving ample headroom for HMI and engineering access.