Connecting S7-1200 to MindSphere via SIMATIC IOT2040 Gateway

Overview

Connecting a SIMATIC S7-1200 to the MindSphere cloud platform requires an intermediary gateway because the S7-1200 CPU does not expose an OPC UA Server interface and its standard firmware does not support the encrypted HTTPS transport that MindSphere REST endpoints require. The SIMATIC IOT2040 (6ES7647-0AA00-1YA2) and the dedicated MindConnect IOT2040 (6ES7647-0AA02-1YA2) are the canonical industrial gateways Siemens designed for this role. This article covers the three practical integration paths, the underlying S7 communication mechanics, the data tag mapping, the network and security configuration, and the verification steps that confirm a healthy uplink.

Connection Path Comparison

Prerequisites

1. S7-1200 CPU with firmware V4.2 or later. For the MQTT path, firmware V4.4 or later is required for the built-in MQTT client blocks. Supported CPUs include CPU 1211C, 1212C, 1214C, 1215C, and 1217C.
2. TIA Portal V15.1 or later for project configuration and firmware update delivery.
3. Active MindSphere tenant with at least one MindConnect IOT slot, one MindConnect Lib developer token, or an IoT Extension service subscription, depending on the chosen path.
4. SIMATIC IOT2040 with Yocto Linux image V2.4.0 or later, SSH access enabled, and root credentials rotated from default.
5. Network reachability from the IOT2040 or S7-1200 outbound to *.mindsphere.io on TCP 443 (HTTPS) or TCP 8883 (MQTTS) through any corporate firewall or proxy.
6. Time synchronization (NTP) on every component. MindSphere rejects payloads with timestamps that drift more than 60 seconds from server time.

Path A: MindConnect IOT2040 Native Configuration

The MindConnect IOT2040 ships with the MindConnect Linux agent preinstalled. The agent handles S7 polling, store-and-forward buffering, and the secure mTLS handshake to MindSphere automatically.

Step-by-Step

1. Connect the MindConnect IOT2040 to the engineering network and power it on. The default IP is 192.168.200.1/24 on eth0. Reconfigure via the serial console or the local web UI on https://192.168.200.1 if needed.
2. Open a browser to the agent's onboard UI at https://<iot-ip> and complete the Initial Commissioning wizard. The wizard prompts for the MindSphere tenant URL, a MindConnect onboarding token, and a device name.
3. Configure the S7 data source. From the agent UI, add a new data source with the following parameters:

4. Map each DB or memory address to a MindSphere datapoint using the agent's data point configurator. For a real (4-byte float) in DB10 starting at byte 0, the agent expects an address string such as DB10.DBD0 (Data Block, Double Word, offset 0).
5. Save the configuration and restart the MindConnect agent service: systemctl restart mindconnect-agent
6. Verify the data source is online in the MindSphere Asset Manager and that datapoints show non-zero sample counts.

Path B: Standard IOT2040 with MindConnect Library (C/C++)

When only a standard IOT2040 is available, the MindConnect Library (C/C++) allows a custom daemon to read S7 tags via the Snap7 open-source client and publish them to MindSphere as time series. The library is delivered as a Yocto SDK package and is documented in the MindSphere developer documentation at documentation.mindsphere.io.

Step-by-Step

1. Install build dependencies on the IOT2040:

   opkg update
   opkg install gcc git cmake libssl-dev libcurl4-openssl-dev

2. Clone and build the MindConnect Library:

   git clone https://github.com/mindsphere/mindconnect-c-lib.git
   cd mindconnect-c-lib && mkdir build && cd build
   cmake .. && make && make install

3. Clone and build the Snap7 client library against the IOT2040's x86 toolchain:

   git clone https://github.com/davenardella/snap7.git
   cd snap7/build/x86_64_linux && make

4. Write the gateway daemon. The high-level loop is:

// Pseudocode - compile with mindconnect-c-lib and snap7
S7Client plc;
plc.ConnectTo("192.168.0.10", 0, 1, 2); // rack 0, slot 1, conn 2

McClient cloud;
cloud.Initialize("./config.json"); // contains tenant, agent key, secret

while (running) {
    float tag[8];
    plc.DBRead(10, 0, sizeof(tag), &tag); // 32 bytes from DB10

    McTimestamp ts = McGetNow();
    for (int i = 0; i < 8; ++i) {
        cloud.PublishValue("DB10_REAL_" + std::to_string(i), tag[i], ts);
    }
    cloud.Flush();
    std::this_thread::sleep_for(std::chrono::milliseconds(1000));
}

5. Deploy the daemon as a systemd service /etc/systemd/system/s7-mindsphere.service with Restart=always and a 5-second RestartSec to survive transient network drops.
6. Activate with systemctl daemon-reload && systemctl enable --now s7-mindsphere and inspect logs via journalctl -u s7-mindsphere -f.

Path C: S7-1200 MQTT Publisher with IoT Extension

From S7-1200 firmware V4.4, the user program can call the TCON, TSEND, and TRCV extended instructions to publish MQTT frames directly to the MindSphere IoT Extension broker. This path removes the IOT2040 from the data plane for the time-series uplink but still relies on outbound internet access from the S7-1200's CP interface.

Step-by-Step

1. In TIA Portal, open the S7-1200 project, mark the CPU, and add the MQTT client instructions to the program blocks. The instructions are part of the S7-1200 Motion & Logic library, installed automatically with TIA Portal V15.1 or later.
2. Configure the connection in the Connection Properties dialog:

3. Build a JSON payload in a global DB. A minimal measure frame is:

   {
     "timestamp": "2024-06-12T10:15:00.000Z",
     "values": [
       {"name": "DB10_REAL_0", "value": 23.7},
       {"name": "DB10_REAL_1", "value": 12.4}
     ]
   }

4. Trigger publication from the OB1 cycle on a 1-second timer using the PUBLISH instruction. Use the CP 1243-1 (6GK7243-1BX30-0XE0) for TLS termination; the basic CPU does not include TLS.
5. Register the S7-1200 as an IoT Extension device in the MindSphere cockpit and assign the IoT Extension role to the corresponding asset.

S7 Communication Protocol Details

All three paths rely on S7 communication as the PLC-side transport. The S7-1200 implements the S7 protocol on top of ISO-on-TCP (RFC 1006) on TCP port 102. The header structure used by every S7 read/write PDU is:

The S7-1200 returns a maximum PDU size of 240 bytes. Snap7 and the MindConnect agent handle PDU fragmentation automatically, but custom daemons should not request more than 222 bytes of payload per call to leave headroom for the variable address specification.

Data Tag Mapping Reference

Tag names in MindSphere are flat strings with no . separators. Replace dots with underscores in the MindConnect mapping to avoid parsing errors in the Asset Manager.

Network and Security Configuration

1. Firewall: Allow outbound TCP 443 (HTTPS) and TCP 8883 (MQTTS) from the gateway IP to *.mindsphere.io. Restrict inbound to the engineering VLAN only.
2. MindSphere authentication: MindConnect agents use OAuth 2.0 client credentials. The onboarding process issues a 4096-bit RSA key pair; the private key is stored at /etc/mindconnect/keys/private.pem with mode 0600. Loss of the private key requires re-onboarding the device.
3. PLC access protection: Configure CPU access level 3 (read/write) in TIA Portal under CPU Properties > Protection > Access Level. Use a password of at least 10 characters, including upper/lowercase and digits, to block unauthorized S7 reads.
4. Time sync: Point the IOT2040 and the S7-1200 CP to an internal NTP server. Drift of more than 60 seconds causes MindSphere to discard the batch.

Verification

1. In MindSphere Cockpit > Asset Manager, confirm the asset shows Connected with a green status indicator. The Last Update timestamp should refresh on every polling interval.
2. Open MindSphere > Fleet Manager > Insights and create a temporary chart for one of the mapped datapoints. Verify the trace line is continuous with no gaps longer than two polling intervals.
3. From the IOT2040 shell, check the agent heartbeat:

   curl -k https://localhost:8443/health
   # {"status":"UP","agentVersion":"3.5.1"}

4. Run a one-shot S7 read from a TIA Portal online session to confirm the gateway and CPU are not contending for connection resources.

Troubleshooting Matrix

Official Reference Documentation

• Siemens Industry Online Support — S7 communication with node-red on SIMATIC IOT2000
• Siemens Community — Connecting S7-1200 PLC with MindSphere