Siemens CPU313C-2DP Onboard I/O Not Responding in STEP 7

1. Problem Overview

The Siemens SIMATIC S7-300 CPU 313C-2DP (Siemens order number 6ES7 313-6CF03-0AB0, firmware family V2.x and V3.x) is a compact CPU with integrated digital inputs (DI16), digital outputs (DO16), and analog inputs (AI5/AO2) located on the front panel. A recurring field failure mode occurs when the integrated I/O appear physically functional (status LEDs illuminate when field contacts close) but the process image in STEP 7 V5.4 SP5 online monitoring shows no logic transition.

In the affected case, the CPU accepted the downloaded program, the online connection was established, the user had verified the wiring against the manual, and the LEDs confirmed the input transitions. Despite this, signals at I 0.0 and the associated output Q 0.0 failed to animate under monitoring. A separately installed SM 321 module (6ES7 321-1BH02-0AA0) on the same rack functioned correctly, isolating the failure to the onboard I/O section of the CPU313C-2DP.

2. Affected Hardware and Software Versions

3. Root Cause Analysis Matrix

4. Required Tools and Prerequisites

• STEP 7 V5.4 SP5 installed and licensed
• PC adapter (MPI/USB) — 6ES7 972-0CB20-0XA0 (PC Adapter USB) or MPI/DP cable
• Digital multimeter (DMM) capable of measuring 24 VDC and continuity
• Spare 40-pin front connector (e.g. 6ES7 392-1AM00-0AA0) or hook-clip leads for direct probing
• Spare MMC (6ES7 953-8LF11-0AA0 or newer 8 MB card) formatted to FAT16
• Spare CPU313C-2DP of identical MLFB for substitution test
• Access to SIMATIC S7-300 CPU 31xC and CPU 31x Manual
• Access to SIMATIC S7-300 SM 321 Signal Modules Manual

5. Wiring Verification (Most Likely Cause)

The CPU313C-2DP onboard DI16 is organized on a 40-pin front connector. Unlike a stand-alone SM 321 DI module (such as the 6ES7 321-1BH02-0AA0 tested working in this case, which is fed internally through the backplane bus), the integrated inputs of the CPU 31xC require an external 24 VDC supply on Pin 1 (L+) and Pin 20 (M) of the front connector. The LED for each input is wired to indicate field voltage, but the digital status (1) is only generated when the input optocoupler receives both L+ on Pin 1 and the field signal on its assigned input pin.

1. Remove the front connector from the CPU.
2. With the field supply OFF, use a DMM in continuity mode to verify Pin 1 is isolated from Pin 20 (no short).
3. Apply 24 VDC ± 5 % between Pin 1 (+) and Pin 20 (−). This is the sensor supply for the onboard DI, separate from the 24 VDC that powers the CPU module itself (which is supplied at the top of the CPU via the 4-pin power connector, L+/M).
4. Verify with the DMM that 24 VDC is present at every input pin you intend to use, by touching Pin 1 to the chosen input pin through a 1 kΩ test resistor (do not short directly).
5. The corresponding channel LED on the CPU front face should illuminate and the process image in STEP 7 should flip to 1 within 1.4 ms (typical input delay for type 1 24 V inputs).

5.1 Front Connector Pinout (CPU 313C-2DP integrated DI/DO)

Refer to the CPU 31xC Operating Instructions for the binding pinout for the specific MLFB variant installed; pinout differs slightly between the older 6ES7 313-6CF03-0AB0 and the later -0AB0 rev.

6. Hardware Configuration Verification (HW Config)

1. Open SIMATIC Manager → your project → double-click Hardware.
2. Confirm the rack slot 2 contains a CPU whose MLFB exactly matches the physical module (e.g. 6ES7 313-6CF03-0AB0, firmware V2.6 or V3.3). A mismatched MLFB compiles and downloads cleanly but does not behave like the installed module.
3. Click the CPU → Properties → Inputs tab. Verify each onboard DI is set to Standard DI (default). If a channel is set to Count, Frequency measurement, or Pulse Width Modulation, that channel no longer appears in the input process image.
4. Click the CPU → Properties → Outputs tab. Verify DO is Standard DO.
5. Click the SM 321 in slot 4 → confirm input addresses begin at I 4.0 (or whatever HW Config assigns). A misaligned addressing slot in HW Config will not overlap the onboard I 0.x but will silently shift SM offsets if the wrong order is dragged in.
6. Compile and Save (Station → Save and Compile).

7. STEP 7 Online Diagnostics Procedure

1. Establish online connection: PLC → Go Online (or F5).
2. Read the diagnostic buffer: PLC → Diagnostic/Setting → Information → Diagnostic Buffer. Look for SF events such as:
   • 0x1470 0001 – Parameter assignment error (configuration does not match module)
   • 0x3931 0001 – MMC write-protected or defective
   • 0x43A1 0001 – Module removed / inserted during operation
   • 0x2520 0001 – Distributed I/O failure (PROFIBUS side, not relevant here)
3. Open Accessible Nodes (PLC → Accessible Nodes). The CPU should appear with its MPI address and rack/slot. Confirm the diagnostic status (green SF = no faults, red SF = fault).
4. Right-click the CPU and select Monitor/Modify. Add variables I 0.0, I 0.1, Q 0.0. Click the Monitor icon (glasses). Force a signal on the field side and watch for status change.
5. Click Force tab to confirm no values are currently forced (a green dot next to a row indicates an active force).

8. Module Information Verification (I/O Status)

1. In SIMATIC Manager online, right-click the CPU 313C in the project tree → Module Information.
2. Select the I/O tab. The status of each onboard DI should toggle between 0 and 1 in real time when the field signal changes.
3. If the status changes here but does not change in OB1 online monitoring, the issue is in the program (e.g. wrong address used in the LAD/FBD/ST code, e.g. I 0.0 vs IB 0 misinterpretation).
4. If the status does not change here either, the issue is hardware — proceed with wiring verification (Section 5).

9. MMC (Memory Card) and Reset Procedure

The CPU 31xC series has no internal non-volatile memory. The MMC is mandatory for retaining the user program and all SFCs/SFBs. A corrupted MMC can cause the CPU to load a partial program where DI/DO update portions are skipped.

1. Power off the CPU.
2. Press and hold the MRES switch.
3. Power on the CPU. Release MRES when all LEDs light briefly.
4. Within 3 seconds, press MRES again for 3 seconds, release for 3 seconds, press MRES a third time for 3 seconds. This performs a full reset (factory reset), formatting the MMC.
5. Reinsert the MMC if it was removed, power on, then redownload the hardware configuration and program.

9.1 Alternative: Online Clear/Reset

1. PLC → Diagnostic/Setting → Clear/Reset.
2. Click Delete All. This clears the RAM load memory but does not format the MMC.
3. PLC → Download the full project.

10. Block Consistency and Recompile

If the user has modified the program after initial download, or has inherited a project with inconsistent block timestamps, the CPU may run the older code while the online view shows the new code.

1. In SIMATIC Manager: Edit → Check Block Consistency (or use the Check Block Consistency button on the toolbar).
2. Click Compile → All. Any block that fails consistency is flagged.
3. Correct reported errors (typically missing or duplicate symbols, mismatched DB length, or wrong UDT version).
4. Re-download with PLC → Download.

11. Hardware Substitution Test

If the above software and wiring checks all pass and the onboard I/O still does not respond, the integrated I/O ASIC on the CPU may be defective. The fact that the user purchased a second CPU 313C and observed identical symptoms suggests the issue is environmental (wiring, power supply, configuration) rather than component failure.

1. Replace the suspected CPU with the spare CPU313C-2DP of identical MLFB and firmware version.
2. Transfer the MMC, or redownload the project.
3. Verify Pin 1 L+ supply is present before powering on.
4. Test with a single input and a single output (no SM 321 installed) to eliminate any interaction with expansion modules.

12. Avoiding the Common Misdiagnosis

The single most common mistake on CPU 31xC onboard I/O is assuming that because a discrete SM 321 (e.g. 6ES7 321-1BH02-0AA0) works without external 24 V on Pin 1, the onboard DI will also work that way. The onboard DI requires an external 24 VDC supply on Pin 1. The LED on the CPU may illuminate from internal pull-up current even without Pin 1, masking the fault, especially on early firmware revisions.

Always confirm:

• Pin 1 = 24 VDC, Pin 20 = 0 V (sensor supply)
• Pin 40 = 0 V (load supply return for outputs)
• Pin 1 and Pin 20 share the same 24 V source as the field wiring (do not invert polarity)

13. Verification Procedure

1. With the CPU in RUN, open a VAT or the program online view.
2. Apply a known 24 VDC signal to input I 0.0 via Pin 1 = L+, signal source switched through the field contact to the chosen input pin.
3. Confirm in Module Information → I/O that I 0.0 = 1.
4. Confirm in OB1 online monitoring that the contact representing I 0.0 animates to 1 within 1.4 ms.
5. If the program drives Q 0.0 from I 0.0, confirm the LED for Q0.0 illuminates and the field voltage at Pin 21 (DO b0) is 24 V (switched).
6. Record diagnostic buffer (right-click → Save) for inclusion in the machine documentation.

14. Diagnostic Buffer Event Reference

15. STEP 7 Software Reference

• SIMATIC S7-300 SM 321 Manual (entry ID 1117740)
• SIMATIC S7-300 CPU 31xC Operating Instructions (entry ID 21462852)
• STEP 7 V5.4 SP5 Readme / Installation Notes (entry ID 18652056)
• STEP 7 Online Help — Block Consistency Check
• CPU 31xC / 31x Hardware Configuration Notes

16. Frequently Asked Questions