SIMATIC IOT2000 Setup Guide: Node-RED, Eclipse, and OPC UA

SIMATIC IOT2000 Hardware Platform Overview

The SIMATIC IOT2000 is Siemens' industrial IoT gateway family. Two variants are referenced in field-tested deployment notes: the IOT2020 and the IOT2040. The IOT2040 is the most-cited device in setup guides and supports a 24 V DC supply, multiple Ethernet ports, USB 2.0 host ports, an RS232/422/485 combination port, a mini-PCIe slot, and a µSD slot that holds the Yocto-based Linux operating-system image. The gateway typically draws 5-11 W depending on the expansion hardware attached. For exact electrical ratings, port counts, CPU, memory, and dimensional drawings, refer to the SIMATIC IOT2000 support entry and the official operating instructions bundled with the device.

The SIMATIC IOT2000 I/O module is a separate add-on that mounts to the gateway and exposes digital and analog channels to the application layer. Both the gateway and the I/O module are available through the Siemens Industry Mall; the I/O module has its own dedicated manual covering wiring, channel count, and electrical limits.

Image Deployment, Network, and Wireless Configuration

The example image is delivered as a disk image. Use a µSD card of at least 8 GB (Class 10 or better, brand-name). Write the image with Win32DiskImager on Windows, with dd bs=4M if=iot2000-image-v2.6.wic of=/dev/sdX status=progress conv=fsync on Linux, or with balenaEtcher cross-platform.

Insert the µSD, apply 24 V DC, and wait about 60 s for the first boot. The IOT2000 example image runs a DHCP server on its first Ethernet port (X1), so a direct patch-cable connection from a PC works without a separate switch. A static fallback address of 192.168.200.1 is also configured on the device.

For console access use PuTTY via the FTDI cable (debug serial) or via SSH over Ethernet. For file transfer use WinSCP (SFTP). The default user is root. Set the host password and SSH configuration at first boot before attaching the device to a production network. The FTDI cable driver and the µUSB serial driver are bundled in the Siemens software pack.

Wired Ethernet. Configure by editing /etc/network/interfaces or by NetworkManager depending on the image revision. Example static address stanza:

auto eth0
iface eth0 inet static
    address 192.168.0.50
    netmask 255.255.255.0
    gateway 192.168.0.1
    dns-nameservers 8.8.8.8 1.1.1.1

Restart with systemctl restart networking. Validate with ip addr show and ping -c 4 192.168.0.1.

USB WiFi. Sticks based on the Realtek RTL8188 and Atheros AR9271 chipsets are field-tested for the IOT. After plugging in, confirm the interface with iwconfig wlan0 and register an SSID:

wpa_passphrase "SSID" "PASSWORD" > /etc/wpa_supplicant.conf
wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf

Add iface wlan0 inet dhcp to /etc/network/interfaces for automatic addressing on the wireless link.

3G mobile radio. A mini-PCIe modem (e.g. Sierra Wireless MC7304 or Huawei ME909s) and the ppp daemon are used. The Siemens "3G connection" how-to covers AT-port initialization, APN definition, and a watchdog that re-establishes the PPP link on failure. Tested modems and WiFi sticks are listed in the starter pack "tested WIFI and mobile radio devices" reference.

For real-time I/O, the Siemens "Realtime Image and Profinet Driver" guide documents a kernel-level Profinet stack that pairs the IOT2040 with a Profinet controller.

Node-RED Programming Environment

Node-RED is a browser-driven flow editor that ships preinstalled on the IOT2000 example image. On image v2.6 the stack is:

The editor listens on TCP 1880. Browse to http://<iot-ip>:1880. The user flow store is at /home/root/.node-red/. Manual foreground start:

Enable autostart on boot:

systemctl enable node-red.service
systemctl start node-red.service

To wipe all flows while keeping installed nodes, delete /home/root/.node-red/flows_iot2000.json and restart the service; a fresh empty flow is generated on next start.

Custom third-party nodes install with npm install <node-name> --unsafe-perm from inside /home/root/.node-red/ followed by a service restart. Siemens-supplied nodes include S7, OPC UA, MindConnect (MindSphere), the IOT I/O module, an NTP Client, and other domain-specific bindings. Node-RED can be upgraded to v1.0.3 on image v2.6 while remaining on Node.js v8; check the official Node-RED supported Node.js list before jumping to newer versions.

OPC UA Server and Client Integration

The IOT2000 can act as an OPC UA client (consuming tags from a SIMATIC S7 controller) or an OPC UA server (exposing its own address space to SCADA). The recommended path is the Siemens-supplied node-red-contrib-iiot-opcua package, which is built on the open-source node-opcua library. The starter pack ships an "OPC UA client in Node-RED" example for reading controller tags and a "Creating an OPC UA server model via Nodeset XML" guide for building a server address space from an XML model file.

Client connection to a SIMATIC S7-1500 OPC UA server:

1. Enable the OPC UA server in TIA Portal under the CPU properties. Default port 4840. Security policy None for lab, Basic128Rsa15 or Basic256Sha256 for production.
2. Drop an OPC UA Client node into a Node-RED flow. Configure Endpoint URL as opc.tcp://<s7-ip>:4840 with the matching security mode and policy.
3. Use OPC UA Item nodes to bind to specific NodeIds, e.g. ns=4;s=|var|CPU_1500.PLC_1.DB1.Real4.

To expose the IOT as a server, drop an OPC UA Server node and define the address space using OPC UA Variable nodes. For larger address spaces, the Nodeset XML method is the production-recommended approach because the entire address space is described once in XML and loaded at startup, avoiding hand-mapping dozens of variables inside Node-RED.

Security policies and message-level security are described in IEC 62541; consult that standard when commissioning certificates, user tokens, and audit logging for production cells.

PLC Communication: S7 and MicroLogix

For direct S7 communication without an OPC UA wrapper, the starter pack documents the node-red-contrib-s7 package built on the node-snap7 C binding.

Typical DB read/write examples used in production nodes:

// Read 4 bytes from DB1 starting at offset 0
node.send({payload: await snap7.read(DB, 1, 0, 4)});
// Write a REAL (1.0f) to DB1.DBD4
await snap7.write(DB, 1, 4, Buffer.from([0x00, 0x00, 0x80, 0x3F]));

For S7-1200/1500 controllers, enable PUT/GET in TIA Portal under the CPU protection settings and grant access to the relevant DBs; otherwise the S7 node times out with an 0x0310 "function not available" error. For S7-300/400, the rack/slot must match the physical hardware position (rack 0, slot 2 for an S7-300 CPU). The field-tested setup note confirms successful communication between an IOT2040 and a SIMATIC S7-1200 programmed through TIA Portal.

For Allen-Bradley MicroLogix controllers through RSLogix 500, the IOT2040 acts as a CIP/Ethernet-IP client. The starter pack documents a flow that uses an Ethernet-IP client node, the controller's Ethernet port (default IP 192.168.1.x/24), and a CIP path of 1,0,<slot>. The IOT must be on the same subnet as the MicroLogix. Field notes confirm that the IOT2040 will communicate with both a SIMATIC S7-1200 and an Allen-Bradley MicroLogix simultaneously using these node packages.

Application Development: Arduino, Eclipse, and Add-Ons

Arduino sketch development. Image v2.6 supports the Arduino IDE targeting the IOT2000's x86 board. Procedure:

1. Install the Arduino IDE on a host PC and connect the PC and IOT to the same network.
2. Add the IOT2000 board-support URL under File > Preferences > Additional Board Manager URLs: https://raw.githubusercontent.com/siemens/iot2000-arduinoide-package/master/package_iot2000_index.json
3. Open Tools > Board > Boards Manager, search for SIMATIC IOT2000, and install the package.
4. Select SIMATIC IOT2000 as the target board, choose the network port under Tools > Port > Network ports, and set the IOT's IP.
5. Compile and upload the sketch. The IDE transfers the ELF over Ethernet to the arduino-sketch-daemon on the IOT, which runs the binary on the next boot.

Verify the daemon is running with systemctl status arduino-sketch-daemon. The µUSB-to-USB cable is required to use the Arduino IDE.

Eclipse C/C++ development. For native C/C++ with full Yocto toolchain integration:

1. Install Eclipse IDE for C/C++ Developers and the Siemens IOT2000 Eclipse plugin from the Siemens support page.
2. Drop the plugin into Eclipse' dropins/ folder and restart.
3. Create a new Siemens IOT2000 C/C++ Project. The plugin generates a Yocto cross-compilation environment, a remote target definition, and a remote launch configuration.
4. Build with Ctrl-B. Eclipse invokes the Siemens Yocto SDK toolchain and produces a binary that runs on the IOT.
5. Use the Remote System Explorer view to deploy the binary to /home/root/<appname> and run it via SSH.

For projects that do not require the Siemens-specific plugin, a generic Eclipse project can be set up with a manually configured cross-compiler path. Shared libraries for the IOT can be built and distributed with the "How to create shared libraries" guide: install the .so into /usr/lib/ on the target, run ldconfig, and add -l<libname> to the compiler flags.

Community Arduino libraries. Community-supplied libraries extend the IOT2000 into common panel-HMI and instrumentation roles:

Each library ships with a sample sketch in the Siemens starter pack and can be dropped into the Arduino IDE once the IOT2000 board package is installed. The "How to create own node" guide covers packaging a custom Node-RED node for distribution through npm.

Database Integration: MariaDB and SQL Server

Image v2.6 ships with MariaDB by default. Field deployment has shown MariaDB is the more reliable choice for low-memory single-board gateways. The SQL Server ODBC driver is heavier for the gateway's CPU and is only recommended when a corporate SQL Server instance is the mandated destination.

Install MariaDB on a clean image:

opkg update
opkg install mariadb-server
/etc/init.d/mariadb start
mysql_secure_installation

Create a database and a user:

CREATE DATABASE plantdata;
CREATE USER 'iot'@'localhost' IDENTIFIED BY 'changeme';
GRANT ALL ON plantdata.* TO 'iot'@'localhost';
FLUSH PRIVILEGES;

From Node-RED use the node-red-node-mysql node with a connection string of mysql://iot:[email protected]:3306/plantdata. For SQL Server, install the Microsoft ODBC driver and follow the Siemens "SQL server connection" guide. Connection-string example:

Time-series data from the IOT should be inserted via parameterised queries rather than string-concatenated SQL to avoid injection. The starter pack shows a common pattern of buffering flow output to an in-memory queue and flushing to MariaDB in batches of 100-500 rows to avoid SD-card wear on the µSD.

SIMATIC IOT2000 I/O Module

The SIMATIC IOT2000 I/O module is a separate add-on that mounts on the side of the gateway and exposes digital and analog channels. Channel count, electrical ratings, and pinout are documented in the SIMATIC IOT2000 I/O module manual. Refer to the official Siemens manual for the exact channel layout before wiring; the I/O module's IEC 61131-2 type-1 digital input characteristics and short-circuit-protected outputs are defined by that standard.

Under Node-RED the I/O module is exposed by the node-red-contrib-iot2000-io package, which provides input and output nodes for each channel. Under Arduino the module is exposed as digital and analog pin numbers (DI, DO, AI, AO) in the Arduino abstraction. Under Eclipse the module registers as a character device at /dev/iot2000-io; the "How to program SIMATIC IOT2000 I/O module" guide covers ioctl commands for raw access. The "SIMATIC IOT2000 I/O module" how-to in the starter pack covers hardware installation and software binding.

The I/O module makes the IOT2000 deployable as a stand-alone controller, eliminating the need for a separate PLC when the application is small (a few DI/DO and one or two AI/AO points) and the deterministic cycle time of a PLC is not required. For applications needing guaranteed cycle time, use the SIMATIC S7-1200/1500 with the IOT2000 as a north-bound gateway.

Cloud Connectivity

Beyond local PLCs, the IOT2000 is often deployed as a north-bound gateway to a cloud platform. Common patterns documented in the starter pack:

• IBM Bluemix / IBM Cloud. Historical reference; Bluemix reached end-of-marketing. The Predictive Maintenance example using Node-RED flows and Watson IoT can be migrated to IBM Watson IoT Platform on IBM Cloud or replaced by AWS IoT Core.
• MindSphere. Siemens' own cloud. Use the MindConnect Lib for MindSphere access; data is published through the node-red-contrib-mindconnect nodes.
• Google Sheets. The "Sending data to Google spreadsheet" example uses a Google Apps Script webhook and a simple HTTP request node in Node-RED. Useful for low-rate telemetry and ad-hoc dashboards.
• cloudmqtt. Broker-based MQTT. The "Connect node-red to cloudmqtt" guide walks through TLS client-cert authentication against a managed MQTT broker.
• LoRaWAN. The LORA communication guide uses an attached LoRa modem (e.g. a Microchip RN2483 on a serial port) to push IOT-side data into a private LoRaWAN network.

For bidirectional control, prefer MQTT over request-response HTTP because the broker manages session state, last-will, and offline buffering. For one-way telemetry to a spreadsheet, HTTP webhooks are sufficient.

Security Hardening and Mass Deployment

Default IOT2000 images are not production-ready from a security standpoint. Apply the following before commissioning:

1. Change the root password and create a dedicated iotadmin user for daily operations.
2. Disable root SSH login by setting PermitRootLogin no in /etc/ssh/sshd_config and restarting sshd.
3. Replace the default self-signed certificate with a CA-signed certificate for the Node-RED editor. Bind the editor to TLS on port 1880 with a reverse proxy, or use the --https option of Node-RED with a private key and certificate file.
4. Configure a host firewall with iptables or nftables to allow only the IOT management VLAN, the S7 PLC subnet, and an outbound cloud endpoint.
5. Follow the "Tips on how to make the IOT2000 secure" procedure in the starter pack, including the systemd watchdog.
6. Lock the filesystem. The read-only overlayfs configuration in image v2.6 means system changes are not persisted across reboot unless /var/lib/overlay is committed. Document which files are persisted and verify after each firmware update.

For fleets of IOT devices, the starter pack documents deployment through resin.io / balenaCloud. The flow is: build a Docker image containing the application and Node-RED flows on a CI host, push to balenaCloud, provision each IOT with a balenaOS image (a balena-forked Yocto build) so the device pulls its image and runs it as a container on first boot, and manage updates and remote shell from the balenaCloud dashboard. For on-prem mass deployment, use the "Readme building an own IOT2000 image" guide to bake a custom Yocto image and deploy the resulting .wic file with a USB SD-card duplicator.

To add programs to autostart, drop a systemd unit into /etc/systemd/system/, then run systemctl daemon-reload and systemctl enable <unit>. Verify boot-time start order with systemd-analyze blame.

Troubleshooting Matrix

FAQ