Resolving SIMATIC IOT2050 Digital Input Read Failures

When a SIMATIC IOT2050 (Basic or Advanced) is paired with the Siemens I/O Shield and read attempts through mraa-gpio or Node-RED return a constant 0 regardless of the 24 V DC applied to DI0/DI1, the root cause is almost always one of three configuration errors: the M0 (ground) reference is not wired, the on-board function select is set to something other than DI/DQ, or the wrong GPIO pin number is being polled. This reference walks through pin mapping, the iot2050setup tool, the mraa-gpio CLI, and Node-RED verification so the inputs read correctly in production.

1. Problem Overview

The typical failure pattern observed on production lines is:

• The IOT2050 boots the Example Image V1.2.1 (Basic) or V1.2.2 (Advanced) without errors.
• mraa-gpio list enumerates 20+ GPIO lines including IO0..IO13, A0..A5, and USER.
• iot2050setup reports the GPIOs are configured as DI/DQ.
• Toggling 24 V on the screw terminals of DI0 and DI1 has no effect on the corresponding mraa-gpio get value.
• The user LED and the USER button continue to respond, indicating the host CPU, libmraa, and Node-RED runtime are healthy.

Because the LED/USER button path is alive, the failure is isolated to the I/O shield's digital input front-end or the reference path shared by those inputs.

2. Root Cause Analysis

Three independent defects can produce the symptom set, and they must be ruled out in this order:

3. Affected Hardware and Software

4. IOT2050 Digital Input Pin Mapping

The shield's screw-terminal labels (DI0..DI19) are translated to libmraa GPIO indices by the meta-iot2050 board definition. The mapping is not one-to-one with the Arduino-shield header pins.

Validate the live mapping on the target with:

root@IOT2050:~# mraa-gpio list
00         IO0: GPIO UART
01         IO1: GPIO UART
02         IO2: GPIO UART
03         IO3: GPIO UART
04         IO4: GPIO PWM
05         IO5: GPIO PWM
06         IO6: GPIO PWM
07         IO7: GPIO PWM
08         IO8: GPIO PWM
09         IO9: GPIO PWM
10        IO10: GPIO SPI
11        IO11: GPIO SPI
12        IO12: GPIO SPI
13        IO13: GPIO SPI
14          A0: GPIO AIO
15          A1: GPIO AIO
16          A2: GPIO AIO
17          A3: GPIO AIO
18          A4: GPIO I2C  AIO
19          A5: GPIO I2C  AIO
20        USER: GPIO

To read the IOT2050's software identity, run:

root@IOT2050:~# mraa-gpio version
Version v2.2.0 on SIMATIC IOT2050

5. Required Hardware Setup

Before any software investigation, verify the field wiring conforms to the IOT2050 manual:

1. Connect the 24 V DC supply positive to the shield's DI0 (or DI1..DI19) screw terminal.
2. Connect the 24 V DC supply negative to the shield's M terminal. This is the step most often missed.
3. Bond the shield's M terminal to the IOT2050 chassis ground if the field 24 V supply is isolated from earth.
4. Confirm the shield is firmly seated on the Arduino Uno headers and that the retention screws are tightened to the specified 0.3 N·m torque.

6. Software Configuration with iot2050setup

Launch the configuration tool from the serial console or an SSH session:

root@IOT2050:~# iot2050setup

Navigate to Peripherals and inspect each GPIO group:

• IO0–IO3 (UART/DI): must read DI/DQ for the D0–D3 shield terminals to act as digital inputs.
• IO4–IO9 (PWM/DI): must read DI/DQ to expose D4–D9 as digital inputs.
• IO10–IO13 (SPI/DI): must read DI/DQ to expose D10–D13 as digital inputs.

For Advanced variants with a dedicated I/O shield, the same rule applies. The setting is persisted to /etc/iot2050-setup.conf and applied at the next boot. The change does not take effect without a reboot.

7. Verifying Reads with mraa-gpio

Use the command-line tool to confirm the read path before bringing Node-RED into scope:

# Set pin 12 (DI0) as input
root@IOT2050:~# mraa-gpio set 12 in

# Read with 24 V applied to DI0, M0 bonded to 0 V
root@IOT2050:~# mraa-gpio get 12
1

# Remove 24 V, read again
root@IOT2050:~# mraa-gpio get 12
0

When the result is 0 in both states, repeat the hardware checklist in §5 before assuming a software fault.

8. Node-RED Integration Steps

Once mraa-gpio get toggles correctly, mirror the configuration in Node-RED:

1. Open the Node-RED editor at http://<iot2050-ip>:1880.
2. Drag an iot2050 in node onto the canvas.
3. Set Pin to 12 (DI0) or 11 (DI1) — do not use the Arduino header number D12 here; the IOT2050 GPIO node expects the libmraa index.
4. Set Mode to Input and leave the debounce at the default 10 ms unless bounce is observed.
5. Wire the node output to a debug node and deploy.
6. Toggle 24 V on DI0; the debug sidebar should show alternating 1/0 payloads.

// Sample Node-RED flow (paste into a flow tab)
[
  {
    "id": "di0probe",
    "type": "rpi-gpio in",
    "z": "iot2050diag",
    "name": "DI0 (pin 12)",
    "pin": 12,
    "intype": "tri",
    "debounce": 10,
    "read": false
  },
  {
    "id": "debug1",
    "type": "debug",
    "z": "iot2050diag",
    "name": "DI0 state",
    "active": true
  }
]

Note: the node-red-contrib-iot2050 palette wraps the same mraa indices used by mraa-gpio. If the palette is missing, install it with:

root@IOT2050:~# npm install -g node-red-contrib-iot2050
root@IOT2050:~# systemctl restart node-red

9. Step-by-Step Troubleshooting Procedure

Follow this sequence when a new shield is integrated or when a previously working station stops reading:

1. Confirm the host is healthy. Toggle the user LED via mraa-gpio set 20 out and mraa-gpio set 20 1. If the LED responds, the CPU/libmraa path is intact.
2. Inspect iot2050setup. Navigate to Peripherals and confirm DI/DQ for IO0–IO13. Save and reboot if any row is mis-configured.
3. Power-cycle the shield. Remove shield 24 V, wait 5 s, re-apply. Some optocouplers latch in undefined states on brown-outs.
4. Verify M0 wiring. Place a DMM between the shield's M terminal and the field 24 V supply's 0 V. Expect < 1 Ω. If open, install a jumper wire.
5. Drive a known input. Apply 24 V to DI0. Measure between DI0 and M with a DMM. Expect 24 V ±10 %.
6. Read with mraa-gpio. mraa-gpio get 12 should return 1. If 0, swap DI0 and DI1 (pin 11) to determine whether the fault is on a specific channel or all channels.
7. Cross-check on Node-RED. Wire the iot2050-in node as in §8. Confirm payload transitions.
8. Capture a syslog slice. journalctl -u node-red -u iot2050-setup --since "-5 min" for any kernel/libmraa fault.
9. Escalate to R&D if all of the above pass and the read still fails on a known-good shield — this is the path that produced the original meta-iot2050 issue.

10. Verification and Field Validation

Once the input reads, perform a 24-hour soak test:

• Program a Node-RED flow that increments a counter on every DI0 rising edge and writes the value to a file node every minute.
• Cross-check the counter against the upstream PLC's pulse count. Discrepancy > 0 indicates missed or extra edges.
• Inspect journalctl -u node-red for the EPIPE or ENODEV errors that occur when a GPIO handle is closed during a high-rate read.

For installations with electrical noise (variable-frequency drives, contactors), add:

• RC snubber (100 Ω + 100 nF) across the contactor coil feeding DI0..DI19.
• Shielded twisted pair from the field device to the IOT2050 shield with the shield bonded at the IOT2050 end only.
• Node-RED debounce raised to 25 ms for mechanical inputs.

11. Diagnostic Reference: Decision Matrix

12. Common Pitfalls and Field Tips

• Don't trust the silkscreen. The screw terminal labeled M on the Siemens shield is not the same node as the IOT2050's chassis/protective-earth terminal. They must be wired.
• Don't assume index = pin number. libmraa indices are remapped by the meta-iot2050 board file; the Arduino header numbering is cosmetic.
• Don't skip the reboot. iot2050setup Peripherals changes only take effect on the next boot. A common failure mode is changing the setting, deploying Node-RED, and concluding the tool is broken.
• Don't read at > 1 kHz without a queue. libmraa on the IOT2050 will drop edges on rapid GPIO reads because Node-RED's event loop yields. For high-speed counting, use the PRU-side counter on the IOT2050 Advanced or an external PLC.
• Don't mix 24 V and 5 V on the same shield. The IOT2050's shield header is 5 V tolerant; the I/O shield level-shifts to 24 V on the field side, but a 5 V signal injected on a 24 V-configured input will be read as a logic high only if the shield's resistor-divider is correct for the chosen mode.

FAQ