S7-300 Migration: CPU 314 IFM to CPU 312C Compatibility Guide

Replacing a discontinued SIMATIC S7-300 CPU 314 IFM (MLFB 6ES7 314-5AE01-0AB0) with the current compact CPU 312C (MLFB 6ES7312-5BF04-0AB0) is a routine lifecycle migration in plants that have standardized on the S7-300 family. Both CPUs sit in the same STEP 7 V5.x programming environment, use the same MPI/DP backplane, and share the same instruction set baseline, so the migration looks straightforward on paper. In practice, three engineering constraints drive the bulk of the work: the 312C exposes far fewer onboard digital and analog channels, the work-memory and Micro Memory Card (MMC) requirements are different, and the default address map shifts because the integrated I/O starts at a different image offset. This reference walks through the technical deltas, the STEP 7 project changes, the offline validation path with S7-PLCSIM, and the on-site commissioning sequence required for a clean, downtime-controlled swap.

For the broader Siemens migration framework - including the move to SIMATIC S7-1500 if you eventually go that direction - see the official Guide for Migrating SIMATIC S7-300/S7-400 to SIMATIC S7-1500. The rewire, hardware reconfiguration, and program-conversion steps in that document apply to intra-S7-300 replacements like the one covered here.

1. Migration Scenario and Affected Hardware

The CPU 314 IFM is an older compact CPU that integrates the program execution, an integrated function module (IFM) for special functions, and a fixed population of onboard I/O directly on the central module. It was designed for small, stand-alone machines that needed analog channels and digital channels without extra signal modules (SMs). Because the IFM variant was phased out, spare-part users are pushed toward the 312C, which is the current compact-class S7-300 CPU with the closest form factor and the same STEP 7 V5.x toolchain.

Key MLFBs covered by this guide:

• Source CPU: SIMATIC S7-300 CPU 314 IFM, 6ES7 314-5AE01-0AB0 (discontinued, firmware family compatible with STEP 7 V5.x)
• Target CPU: SIMATIC S7-300 CPU 312C compact, 6ES7312-5BF04-0AB0, firmware V3.x, STEP 7 V5.5 + SP2 or later

2. Hardware Comparison: CPU 314 IFM vs CPU 312C

The table below summarizes the head-to-head specs that drive the migration. Values are taken from the S7-300 CPU 31xC and CPU 31x operating instructions and the S7-300 module data manual.

Two design changes stand out: the 312C has roughly 50 percent fewer onboard DI/DO channels and no onboard analog at all. Every analog channel the application currently uses on the IFM must be replicated by an external SM 334 or SM 335 module in the new rack.

3. Onboard I/O Reduction and Required Expansion Modules

Count the channels before quoting the swap. The 314 IFM provides 16 DI / 16 DO / 4 AI / 1 AO directly on the CPU. The 312C provides 10 DI / 6 DO and no analog channels. The shortfall must be made up by adding SM 321 (DI), SM 322 (DO), and SM 334 (AI/AO) modules on the rail.

3.1 Digital Channel Budget

3.2 Analog Channel Budget

If the application uses the 4 AI / 1 AO for transducer scaling, PID control, or valve actuation, a typical mitigation is to drop in a single SM 334 AI4/AO2 (6ES7334-0CE01-0AA0) plus an SM 321 (6ES7321-1BH02-0AA0) for the missing digital inputs. Confirm spare slots on the rail - the 312C supports the same eight SM/FM maximum, but the 314 IFM was often deployed with very few external modules because of the integrated I/O.

3.3 Wiring Migration

Because the 312C has a single 40-pin front connector, the wiring diagram cannot be reused as-is. The two 40-pin connectors on the 314 IFM split digital I/O across two terminal blocks; the 312C compresses the digital I/O into one 40-pin connector and reserves the rest of the footprint for the two counter/frequency channels (X11). Re-strip the field wiring and remap terminal-by-terminal rather than trying to use a 1-to-1 pin cross-reference table.

4. Work Memory, Micro Memory Card, and Retentive Behavior

The CPU 312C needs a Micro Memory Card to operate. Without an MMC inserted, the CPU will not start and the SF LED will be lit steady. This is the single most common reason a freshly migrated 312C refuses to go into RUN at first power-up.

4.1 Required MMC Size

4.2 Retentive Mapping

The 314 IFM stored retentive data in internal Flash. The 312C stores retentive data on the MMC, which means the MMC must be ordered with the right number of write cycles for the application. Industrial MMC variants (6ES7953-8Lxxx-0AA0) are rated for 100,000 write/erase cycles minimum.

Update the STEP 7 hardware configuration (HW Config) > CPU Properties > Retentive Memory to reflect the new bit-memory and timer/counter ranges. A safe default is to mark MB0 - MB15, T0 - T15, and C0 - C7 as retentive, but always derive this from the customer specification rather than copying values blindly from the 314 IFM project.

5. Address Mapping Changes and the STEP 7 Rewire Function

This is the most time-consuming part of the migration. The default I/O addresses assigned by STEP 7 to the integrated channels differ between the two CPUs, and adding SMs shifts all subsequent module addresses by 4 bytes (for analog) or 4 bytes per 32-channel group (for digital) in the process image.

5.1 Default Address Map Comparison

Notice that the 312C maps its onboard I/O into the high process image area (byte 124 and above) so that user expansion SMs occupy the lower addresses in the default configuration. This is the opposite convention from the 314 IFM and means the same physical input that was I 0.0 on the 314 IFM will become I 124.0 (or any address you wire on the new SM) on the 312C.

5.2 Using the Rewire Function

STEP 7 V5.5 provides a rewire tool that scans the entire program for absolute address operands and rewrites them. To use it:

1. Open the S7 program in SIMATIC Manager.
2. Open the OB1 (or any block where absolute addresses appear).
3. Select Options > Rewire.
4. Enter the old address (for example, I 0.0) in the Old Address column and the new address (for example, I 124.0) in the New Address column.
5. Click Rewrite. The tool walks the entire S7 program, all DBs, all FBs, and all instance DBs.
6. Repeat for each address that moved.

For bulk changes, build a rewire table in an Excel sheet first. Typical 314 IFM to 312C rewiring example:

Confirm the new SM addresses by opening HW Config and reading the I column directly - never assume the address offsets shown in the catalog.

6. STEP 7 Project Compatibility and Hardware Reconfiguration

Both CPUs are programmed with STEP 7 V5.x. The conversion path is:

1. Open the existing .s7p project in SIMATIC Manager.
2. Right-click the S7-300 station and choose Open HW Config.
3. Delete the old CPU 314 IFM from slot 2.
4. Drag the new CPU 312C (6ES7312-5BF04-0AB0) from the hardware catalog into slot 2. The catalog entry is under SIMATIC 300 > CPU 300 > CPU 312C.
5. Insert the SM 321, SM 322, and SM 334 (or whatever analog module you chose) into the slots immediately right of the CPU.
6. Run the rewire pass described in section 5.2.
7. Compile and save the HW Config. STEP 7 will write a new System Data block and update the module addresses.
8. Download the new hardware configuration to the CPU (or to PLCSIM for offline testing - see section 8).

STEP 7 will not automatically rewrite the program for you. Address changes and DB length changes have to be tracked manually. A common error is leaving the old system data blocks in the project; the download will report "SDB mismatch" and the CPU will keep the old configuration in Flash until the new SDBs are loaded.

6.1 Library Block Re-use

If the existing 314 IFM program called IFM-specific FBs (for example, the integrated analog input handling FB or the IFM-specific counter FB), the matching FBs for the 312C live in the Standard Library under > Standard Library > S7 - SFB / SFC or > Standard Library > PID Control. The 312C ships with integrated counter and frequency measurement FBs:

These SFBs are in the S7-300 Standard Library and must be present in the S7 program for the counters to work. If the 314 IFM program was based on a vendor-supplied FB that wrapped the IFM function block, replace that wrapper with the standard SFB call in the new project.

7. Instruction Set and Integrated Function Block Differences

The STEP 7 instruction set is essentially identical between the two CPUs, but there are edge cases where the IFM vendor FBs (FC 90 - FC 99 range on the 314 IFM) have no direct equivalent on the 312C and must be rewritten.

• Analog scaling: The 314 IFM scales onboard AI via FC 105 (SCALE) and FC 106 (UNSCALE) calls already in the program. The 312C must scale the SM 334 inputs identically; the FC 105/FC 106 calls in the user code do not need to change, only the source address changes.
• Hardware interrupts: The 312C supports OB 40 hardware interrupts on the digital inputs; the 314 IFM does not expose hardware interrupts in the same way. If the existing program was tied to an IFM event OB, re-target the event to OB 40 in the new HW Config.
• Diagnostic interrupts: The 312C supports OB 82 on the digital SMs; the 314 IFM used a different diagnostic block. Re-target the diagnostic OB in HW Config.
• Time-of-day interrupts: Both support OB 10 - OB 17. The configuration under CPU Properties > Time-of-Day Interrupts is functionally identical.

8. Pre-Migration Validation with S7-PLCSIM

Do not start the swap without first validating the new program against a SIMATIC S7-PLCSIM instance. PLCSIM is bundled with STEP 7 V5.5 Professional and lets you load the converted project into a virtual CPU 312C and exercise the logic before any hardware is touched.

8.1 PLCSIM Validation Procedure

1. In SIMATIC Manager, change the target station from the real CPU to a PLCSIM instance: Options > Set PG/PC Interface > PLCSIM (MPI).
2. Download the converted S7 program to the PLCSIM instance: PLC > Download.
3. Place the PLCSIM CPU into RUN. The RUN LED will toggle in the PLCSIM toolbar.
4. Force inputs in the PLCSIM I/O view to simulate the field conditions (a typical sweep is: each DI, each AI range 4 mA and 20 mA, each counter pulse train at 1 kHz and 10 kHz).
5. Verify each output with the PLCSIM output view. The 312C outputs do not actually switch any field wiring, so this step is safe to do in the office with no rack connected.
6. Run through the OB 100 startup, OB 1 scan, OB 35 (if used), and any OB 40 hardware-interrupt blocks. PLCSIM will not trigger hardware interrupts for SMs that are not in the simulated rack, so add the SM 321 to the simulated rack to get OB 40 coverage.

PLCSIM will catch the most common migration errors before the field engineer ever opens the cabinet: rewire mistakes, SDB download failures, missing FBs, and OB misconfigurations. If a customer schedules a 4-hour outage for the swap, PLCSIM validation is the difference between a clean exchange and a 14-hour troubleshooting session.

9. Step-by-Step Migration Procedure

Use this procedure as the field runbook. Total downtime for a clean swap is typically 1 - 2 hours if PLCSIM validation is complete and the new SMs are pre-wired.

9.1 Prerequisites

• New CPU 312C, MLFB 6ES7312-5BF04-0AB0, with firmware version 3.3 or later
• Micro Memory Card sized for the program (typically 2 MB or 4 MB)
• Signal modules to compensate for missing onboard I/O (section 3.1 - 3.2)
• STEP 7 V5.5 + SP2 or later installed on the engineering station
• SIMATIC S7-PLCSIM V5.4 SP5 or later for offline validation
• Front connector for the 312C (1 x 40-pin, MLFB 6ES7392-1AM00-0AA0)
• Updated wiring diagram, updated bill of materials, updated I/O list with new addresses

9.2 Procedure

1. Back up the existing S7 project, including the source SDBs, to a safe location. Use the menu PLC > Upload Station to PG, save the resulting .s7p and a copy of the source SDBs.
2. In SIMATIC Manager, perform the hardware reconfiguration described in section 6. Save the project as a new .s7p file - keep the original untouched in case rollback is required.
3. Run the rewire pass against the new project (section 5.2). Save and compile.
4. Validate against S7-PLCSIM (section 8). Document the test results in the change log.
5. Schedule the outage. During the outage, place the plant in a safe state (drives disabled, valves in a defined position, safety circuits held).
6. Power down the S7-300 rack. Discharge any 24 V DC bus on the DIN rail.
7. Remove the CPU 314 IFM and label all front-connector wiring with the slot number and pin number.
8. Remove the front connector(s) from the 314 IFM. Note that there are two front connectors; tag them as "FC1" and "FC2" to avoid mixing them up with the single connector that will go on the 312C.
9. Install the new SM 321, SM 322, and SM 334 (or whichever expansion modules you chose) in the empty slots to the right of slot 2. Tighten the module screws to the specified torque (0.8 - 1.1 Nm on the S7-300 rail).
10. Insert the CPU 312C into slot 2. Verify the coding key on the back of the module is correct for the slot.
11. Insert the Micro Memory Card into the MMC slot of the 312C before powering on. The MMC must be pre-loaded with the new S7 program; do this with a PC and a SIMATIC USB prommer (MLFB 6ES7792-0AA00-0XA0) or by downloading to the MMC after the CPU is in STOP.
12. Wire the 40-pin front connector to the 312C. Wire the new SMs to their own front connectors. Cross-check the field-side wiring against the updated wiring diagram.
13. Power up the rack. The CPU 312C performs a RAM test and then attempts to load from MMC. The STOP LED should be solid yellow during this phase.
14. Connect the engineering station via MPI. From SIMATIC Manager, perform a full download: PLC > Download > to Target System. Select all blocks and SDBs.
15. Place the CPU in RUN. Verify that OB 1 scans without SF (system fault), BF (bus fault), or BATF (battery fault) LEDs. The SF LED is the most important - any solid SF after the swap indicates a hardware configuration error or a rewire mistake.
16. Walk through the I/O checkout. For every DI: force the field device and confirm the input bit in the VAT or PLCSIM-equivalent online view. For every DO: command the output bit to 1 and confirm the field voltage. For every AI: apply a known reference (4 mA and 20 mA) and confirm the engineering value. For every AO: command a known output value and confirm the field voltage/current with a calibrated meter.
17. For the integrated counters, exercise each one with a pulse train from a signal generator. Confirm the count value in the instance DB and the direction bit behaviour at the gate input.
18. Hand the system back to operations. Update the as-built wiring diagram, the I/O list, and the backup of the S7 project.

10. Hardware Commissioning and Verification

Commissioning is the last gate before the line runs production. Use this checklist:

10.1 LED Verification

10.2 Diagnostic Buffer Inspection

Open the diagnostic buffer (PLC > Diagnostic Buffer) and walk the last 10 events top-down. The buffer always logs the cause of the most recent stop. The most useful events for a 314 IFM to 312C migration are:

• "Stop by programming device" - normal if you stopped the CPU to download
• "STOP because of missing or defective module" - usually a slot not populated that the SDB expects
• "Parameter assignment error" - the SM 334 needs a different measuring range module than the 314 IFM had configured
• "Communication error" - MPI or DP address conflict

10.3 Time-Out and Scan Time Validation

Use PLC > Module Information > Scan Cycle Time to record the OB 1 minimum, maximum, and current scan time. The 312C is roughly 30 percent faster per bit instruction than the 314 IFM, so a faster scan is expected. If the scan time drops by more than 50 percent, the rewire pass may have removed a call to a heavy FB (such as a PID block) by accident - check the cross-reference list (Options > Reference Data > Display).

11. Troubleshooting Matrix

12. Frequently Asked Questions