1. Problem Summary: Catalog Mismatch During STEP 7 to TIA Portal V12 Migration
When migrating a STEP 7 Classic project (STEP 7 V5.x) into TIA Portal V12, the hardware catalog frequently does not contain an exact match for every module physically present in the existing rack. Engineers typically encounter two recurring symptoms:
- The hardware catalog only lists a CPU firmware version newer than the firmware actually installed on the physical module — for example, the catalog shows V2.6 while the physical CPU 6ES7 314-6CG03-0AB0 was shipped with V2.0.
- The hardware catalog only lists a higher MLFB (order number) of an I/O module than the module physically installed — for example, the catalog shows 6ES7 421-1BL01-0AA0 while the rack contains 6ES7 421-1BL00-0AA0.
Both cases are symptoms of an evolving hardware catalog that is synchronized with the active distribution date of the TIA Portal version. The catalog does not contain withdrawn or older MLFBs unless the engineer installs a Hardware Support Package (HSP). In the scenario described in the source report, however, a deeper architectural error is present: the I/O module 6ES7 421-1BL00-0AA0 belongs to the SIMATIC S7-400 family, while the CPU 6ES7 314-6CG03-0AB0 is an S7-300 device. The two families are not interchangeable. This must be corrected before any catalog or firmware question becomes meaningful.
2. Module Identification: Decoding the SIMATIC MLFB
Siemens order numbers (MLFBs) embed the device family in the group identifier. Recognizing the group identifier is the first step in any migration analysis.
| Order Number (MLFB) | SIMATIC Family | Module Function |
|---|---|---|
| 6ES7 314-6CG03-0AB0 | S7-300 | CPU 314C-2DP, compact CPU with integrated I/O (16 DI / 16 DO / 5 AI / 2 AO) and PROFIBUS DP master/slave interface |
| 6ES7 421-1BL00-0AA0 | S7-400 | SM 421 digital input module, 32 DI × 24 V DC, designed for the S7-400 central rack only |
| 6ES7 421-1BL01-0AA0 | S7-400 | SM 421 digital input module, 32 DI × 24 V DC, successor variant of the 1BL00; identical function, updated components |
Before pursuing any catalog or firmware action, confirm what is physically mounted in the rack. Read the order number printed on the front of each module and cross-check it against the device label or the BOM / parts list. The "32 × DI 24 V DC" function is also available in the S7-300 family as the SM 321 (6ES7 321-1BL00-0AA0). The S7-300 and S7-400 MLFBs are deliberately different and cannot be interchanged.
3. Resolving the Family Mismatch
Three options exist when the migration uncovers a family mismatch between the CPU and the I/O module:
- Replace the SM 421 with the S7-300 equivalent. The functionally identical S7-300 module is the SM 321 6ES7 321-1BL00-0AA0 (32 DI, 24 V DC). If the physical module is actually an SM 421 in an S7-300 rack (which is mechanically impossible), the project must be corrected to use the S7-300 MLFB. If the physical module is genuinely an SM 321, the project should be re-targeted to that MLFB.
- Replace the CPU with an S7-400 CPU. If the installation is genuinely S7-400 hardware and the CPU was misread, swap the CPU for the correct S7-400 family member and rebuild the configuration around the SM 421.
- Re-survey the rack. Read every module label in the station. In migration projects it is common to find that the original documentation was incorrect, that a partial conversion was performed in the field, or that a wrong MLFB was ordered as a replacement at some point in the asset's life.
Once the rack contents are correct for a single SIMATIC family, proceed to the catalog and firmware questions below. These apply to either family.
4. CPU 314C-2DP Technical Reference
The CPU 6ES7 314-6CG03-0AB0 belongs to the SIMATIC S7-300 compact CPU line. Key parameters relevant to the migration:
| Parameter | Value |
|---|---|
| Work memory (code) | 96 KB |
| Work memory (data) | 96 KB |
| Integrated DI / DO / AI / AO | 16 / 16 / 5 / 2 |
| Bit memory | 2 048 bits (256 bytes) |
| S7 counters / timers | 256 / 256 |
| PROFIBUS DP interface | 1 × DP master/slave |
| Max. DP slaves (master mode) | 32 (limited by address space and power budget) |
| Programming languages | LAD, FBD, STL, S7-SCL, S7-GRAPH (with optional packages) |
| Front connector | 1 × 40-pin (for integrated I/O) |
| Memory card | Micro Memory Card (MMC), required for operation |
The factory firmware is V2.0. The highest firmware available for this MLFB is V2.6.11. TIA Portal V12's hardware catalog contains the V2.6 entry, not the V2.0 entry, because V2.0 is no longer in active distribution at the time of the V12 release.
5. SM 421 Family Reference (1BL00 vs. 1BL01)
The SM 421 occupies a single slot in the S7-400 central rack. Relevant parameters for the migration analysis:
| Parameter | 6ES7 421-1BL00-0AA0 | 6ES7 421-1BL01-0AA0 |
|---|---|---|
| Number of inputs | 32 DI | 32 DI |
| Input voltage | 24 V DC | 24 V DC |
| Galvanic isolation | Yes, in groups of 8 | Yes, in groups of 8 |
| Input delay (selectable) | 0.1 / 0.5 / 3 / 15 ms (typical group) | 0.1 / 0.5 / 3 / 15 ms (typical group) |
| Diagnostic functions | Group error, channel-level on selected groups | Group error, channel-level on selected groups |
| Front connector | 2 × 40-pin | 2 × 40-pin |
| Power consumption (backplane) | ≈ 0.6 A at 5 V | ≈ 0.6 A at 5 V |
| Function | Identical | Identical |
The 1BL01 is a successor variant of the 1BL00 with identical function, identical pinout, and identical diagnostic behavior. It is a hardware revision change (component obsolescence, second-source parts), not a functional upgrade. The two are interchangeable at the project level when both are present in the catalog.
6. CPU 314C-2DP Firmware Update Path (V2.0 → V2.6.11)
The CPU 6ES7 314-6CG03-0AB0 ships with firmware V2.0 from the factory. TIA Portal V12 was released with firmware V2.6 already in its hardware catalog. The catalog does not include the V2.0 entry because V2.0 is no longer in active distribution. Three courses of action are available.
6.1 Update the CPU firmware to the catalog version (recommended)
The recommended approach is to update the CPU firmware to the version that matches the catalog entry used in the project. The current highest available firmware for the 6ES7 314-6CG03-0AB0 is V2.6.11, distributed by Siemens as a firmware update package.
To perform the update, download the firmware file from the Siemens Industry Online Support entry Firmware update for S7-300 CPUs (entry 12019198). The download contains a SIMATIC firmware update file that can be transferred to the CPU either via the SIMATIC Memory Card (MMC) or over the online interface of TIA Portal / STEP 7. During the update the CPU is in STOP and the existing user program is retained on the MMC.
6.2 Downgrade to an older firmware
It is technically possible to downgrade, but rarely advisable. V2.0 firmware is no longer in distribution; the file may still be retrievable from legacy archives but is not officially supported at the time of writing. If the V2.0 firmware must be preserved on the CPU for any reason (validation, signature, vendor agreement), the project must be re-targeted to a TIA Portal version that still contains the V2.0 catalog entry, or an older STEP 7 V5.x project must be retained in parallel for that station.
6.3 Retain V2.0 and use STEP 7 V5.x
If the firmware cannot be updated and the V2.0 catalog entry is missing from TIA Portal, do not assign the V2.6 catalog entry to a V2.0 CPU. A project built against V2.6 will download to the CPU, but at first run the CPU reports a firmware-version mismatch in the diagnostic buffer and may refuse to enter RUN. The clean solution in this case is to remain on STEP 7 V5.x for this station, or to update the firmware.
7. Step-by-Step: Performing the Firmware Update via MMC
- Insert a SIMATIC MMC of at least 2 MB capacity (recommended 4 MB or larger) into the programming device's MMC adapter.
- Open the MMC contents in Windows Explorer and place the firmware file (S7_FW__314C_2DP_V02611.bin or equivalent as provided by the Siemens package) at the root of the card. No folder structure is required.
- Power off the CPU. Insert the MMC into the CPU's slot. Power the CPU back on.
- The CPU detects the firmware file on the MMC and prompts for confirmation on the front-panel display. Use the operating-mode selector to confirm (Yes / No prompt). The CPU performs the update, indicated by a progress bar on the display.
- When the update completes, the CPU performs an automatic restart and enters the configured startup mode. The new firmware version appears in the device information (online → accessible devices → online & diagnostics → module information).
- Perform an MRES to clear residual runtime data. Reload the user program and verify the diagnostic buffer is empty.
7.1 Alternative: Firmware Update via TIA Portal Online Interface
- Connect the programming device to the CPU via MPI / PROFIBUS / Ethernet (with the appropriate CP).
- In TIA Portal V12, choose Online → Accessible devices and confirm the CPU is reachable.
- Open Online & diagnostics on the CPU. Navigate to Functions → Firmware update.
- Browse to the firmware file on the local drive. Confirm the target version and click Execute update.
- Wait for the update to complete. The CPU automatically restarts and reconnects.
8. MLFB Substitution Rules: When a Newer Order Number Replaces an Older One
For modules of the same family, Siemens maintains a forward-compatible substitution table. An older module can usually be replaced by its successor in the configuration without changing the project semantics.
| Direction | Behavior | Recommendation |
|---|---|---|
| Old in project → New in rack | Generally works; project is loaded as configured, physical module accepts the new variant | Acceptable for commissioning / migration. The catalog must contain the new MLFB. |
| New in project → Old in rack | May work; depends on whether the older module accepts the new GSD / module record | Try, but be prepared to revert the project to the older MLFB. Always validate against the diagnostic buffer and the I/O status table. |
| New MLFB not in catalog | Cannot be selected; project cannot be downloaded to that slot | Install the latest Hardware Support Package (HSP). See Section 9. |
| Different family (S7-300 ↔ S7-400) | Never works; the rack connector and bus are different | Replace the module with the correct family equivalent. Do not attempt substitution. |
For the 1BL00 → 1BL01 substitution on the SM 421, Siemens documents the 1BL01 as a successor with identical function, identical pinout, and identical diagnostic behavior. Substituting the newer MLFB in the project for a rack containing the older MLFB is permitted at commissioning; the reverse (project has 1BL00, rack has 1BL01) requires the catalog to contain the 1BL00 entry, which is the situation encountered in the source report.
9. TIA Portal V12 Hardware Catalog Behavior
Unlike STEP 7 V5.x, where the hardware catalog is updated by installing new Hardware Support Packages (HSPs), TIA Portal V12 ships with a hardware catalog that is frozen to the distribution date of the version. The catalog contains the modules that were in active distribution on that date. Modules released or withdrawn after that date are absent.
This is a deliberate design: it guarantees that any project saved on one TIA Portal V12 installation is reproducible on any other TIA Portal V12 installation. The trade-off is that older or newer modules require an HSP. The absence of the V2.0 firmware entry for the CPU 314C-2DP and the absence of the 1BL00 entry for the SM 421 in the V12 catalog are both expected, and both are correctable by installing the appropriate HSP.
10. Installing Hardware Support Packages (HSP)
Hardware Support Packages extend the TIA Portal hardware catalog with modules that are not part of the base installation. Siemens releases HSPs on a continuous basis; the latest set compatible with V12 is required when older or newer modules must be configured.
The official procedure is documented in Siemens Support entry 72341852 – Support Packages for the hardware catalog in the TIA Portal (HSP). The condensed procedure for TIA Portal V12 is:
- Open TIA Portal V12 with the project loaded.
- From the menu, choose Options → Support Packages. The Support Packages dialog opens.
- Click Install / Uninstall Support Packages.
- Browse to the HSP file (.zip or .hsp) downloaded from Siemens Support and confirm.
- Wait for the package to extract. TIA Portal will close and reopen automatically during this process.
- After restart, the new modules appear in the hardware catalog under the appropriate family folder. Older firmware versions for existing CPUs also appear as separate catalog entries.
11. PC and Software Prerequisites for TIA Portal V12
For reference, the platform requirements for TIA Portal V12 are aligned with the system requirements of the V12 generation. The current general system requirements are listed in the Siemens TIA documentation portal at General software and hardware requirements (this page documents the current generation; consult the V12-specific manual for exact V12 figures):
| Resource | Minimum | Recommended |
|---|---|---|
| Operating system | Windows 7 SP1 (32/64-bit), Windows Server 2008 R2 SP1 | Windows 7 SP1 64-bit |
| RAM | 2 GB (small projects) | 8 GB (larger projects typical of migration) |
| Free disk space | 20 GB on S-ATA drive | 50 GB+ SSD |
| Network | 100 Mbit/s Ethernet for online / HMI coupling | 1 Gbit/s |
| Display | 1024 × 768 | 1920 × 1080 |
For projects that contain S7-300 stations with extensive hardware (rack full of SMs, multiple CPs, several PROFIBUS slaves), 8 GB of RAM is the practical minimum. S-ATA disk is acceptable but slows project load and compile operations noticeably; an SSD is recommended for any TIA Portal install above V12.
12. Migration Workflow: STEP 7 V5.x → TIA Portal V12
Use the following sequence when porting a STEP 7 V5.x project that contains a CPU 314C-2DP and S7-300 family hardware:
- Inventory the physical rack. Read every MLFB and every firmware label. Record the SIMATIC family of each module.
- Resolve any family mismatch. Replace or correct modules so that the rack contains one consistent family. The 6ES7 421-xBLxx-0AA0 must be removed from the project if the CPU is an S7-300 device.
- Open the STEP 7 V5.x project in TIA Portal V12 using Project → Migrate project. The migration wizard translates the S7 program and the hardware configuration.
- Open the device configuration of the migrated CPU. Compare the catalog entry used by the migration wizard with the physical module. If they differ, decide between updating firmware on the module or installing an HSP and re-targeting the project to the older MLFB.
- Install the latest HSP for V12 to expand the catalog (Section 10).
- Compile the project (Station → Compile) and download to the rack. Verify with the online diagnostics that the module status is "OK" and that the diagnostic buffer contains no entries referencing the firmware version or the module identity.
- Place the station in RUN. Verify the I/O status table for at least one full process cycle.
13. Verification Checklist
| Item | Expected Result |
|---|---|
| Module status (online → accessible devices → online & diagnostics) | All modules report "OK", no "Maintenance demanded" or "Fault" |
| Diagnostic buffer (CPU → online & diagnostics → diagnostic buffer) | No entries referencing "Firmware version mismatch", "Module identification", or "PROFIBUS slave failure" |
| CPU operating state (RUN/STOP) | RUN after project download, no spontaneous STOPs |
| I/O status table (watch table on the process image) | Inputs change in response to field signals, outputs drive the load as configured |
| Memory card contents (project card view) | Project on the MMC matches the TIA Portal project (compare block hashes) |
| Firmware version reported by CPU | Matches the catalog entry used in the project (e.g., V2.6.11) |
14. Troubleshooting Matrix
| Symptom | Root Cause | Corrective Action |
|---|---|---|
| Catalog does not list the physical CPU firmware | TIA Portal V12 catalog is fixed at release date; older firmware has dropped out | Update CPU firmware to the catalog version (recommended) or install the matching HSP |
| Catalog does not list the physical MLFB | Same as above, or the module is from a different family | Install the latest HSP, or correct the family mismatch |
| CPU enters STOP after download with "Firmware mismatch" in the diagnostic buffer | Project built against a newer firmware than physically present | Update the CPU firmware or rebuild the project against the older firmware entry |
| "Module does not exist" in the configuration | Slot contains a module of a different family (e.g., SM 421 in an S7-300 project) | Physically inspect the rack, replace the module with the correct family equivalent (SM 321 for the 32 DI function) |
| Online diagnostics: "Maintenance demanded" on a digital input | Wiring fault, sensor failure, or channel not parameterized in the project | Check wiring, verify the channel is enabled in the device configuration, clear the diagnostic buffer after repair |
| Project download fails with "Slot configured but empty" | Project references a slot that has no module | Open the device configuration, compare with the physical rack, correct the slot assignment |
| PROFIBUS slave not coming up after migration | Slave address conflict, baud-rate mismatch, or GSD file incompatibility | Verify slave addresses and baud rate, re-install the latest GSD for the slave |
| HSP install fails with "Incompatible with this TIA Portal version" | The HSP is for a newer TIA Portal version (e.g., V13/V14/V15/V16) | Download the V12-compatible HSP from Siemens Support; HSPs are version-specific |
15. Common Errors and Corrections
Error: Treating the 1BL00 → 1BL01 catalog gap as a firmware problem.
Correction: The 1BL00 and 1BL01 are not firmware versions. They are different MLFBs. The "01" in the position immediately before the "-0AA0" suffix denotes the hardware revision of the module, not its firmware. Firmware updates use a separate "Firmware V..." label on the module's front and are added to the project as a property of the selected MLFB, not as a separate catalog entry. Always read the module label carefully and match it to the corresponding MLFB, not to a firmware version.
Error: Assuming a CPU firmware update changes the CPU's MLFB.
Correction: The MLFB is the hardware order number and is printed on the front of the module. Firmware updates do not change the MLFB. A CPU 6ES7 314-6CG03-0AB0 remains a 6ES7 314-6CG03-0AB0 after the firmware is updated from V2.0 to V2.6.11.
Error: Substituting an S7-300 SM in a project for an S7-400 SM in the rack (or vice versa) because the function is identical.
Correction: The two families are physically and electrically distinct. The substitution table applies only within a family. For "32 DI 24 V DC" the S7-300 module is the SM 321 (6ES7 321-1BL00-0AA0) and the S7-400 module is the SM 421 (6ES7 421-1BL00-0AA0). The leading digit "3" vs "4" is the family indicator.
Error: Installing the latest HSP without first verifying TIA Portal version compatibility.
Correction: HSPs are version-specific. An HSP for TIA Portal V15 will not install on V12. Download the V12-compatible HSP from the Siemens support portal filter for "TIA Portal V12".
16. Field-Proven Caveats
- Some 1BL00 modules were factory-reworked to 1BL01 specification under a Siemens service bulletin. Such modules carry the original 1BL00 label and a 1BL01 sticker. Read the front label, not the box label or shipping documents.
- Firmware updates to a CPU 314C-2DP require a SIMATIC MMC of at least 2 MB and at least 1 MB free on the card. Verify before starting the update.
- After a firmware update, the CPU retains its IP address and MPI/DP address but clears the diagnostic buffer and the run-time counters. Note any counters that are required for process records before performing the update.
- When using TIA Portal V12, the catalog of available CPUs depends on the installed HSP. If a CPU appears in the catalog but the firmware is older than expected, check Options → Support Packages → Installed to see which HSP is providing the entry.
- Do not mix project files between TIA Portal versions. Save a separate copy before installing a new HSP if there is any chance the new catalog will be picked up by an existing device selection.
- If a migration of an S7-300 station includes any PROFIBUS slaves, re-install the latest GSD files for the slaves in TIA Portal V12 to ensure the migrated configuration matches the running slave.
Do I have to update the CPU 314C-2DP firmware to use TIA Portal V12?
Not necessarily, but it is the cleanest path. If the project is built against the V2.6 catalog entry, the CPU must run V2.6 or higher. Update the firmware to V2.6.11 using the package available from Siemens Support entry 12019198. If the firmware must remain at V2.0, retain the project in STEP 7 V5.x.
Can the SM 421 (6ES7 421-1BL00-0AA0) be used with an S7-300 CPU?
No. The SM 421 is an S7-400 signal module and is not compatible with the S7-300 backplane bus, addressing, or mechanical format. The functionally identical S7-300 module is the SM 321 6ES7 321-1BL00-0AA0. Replace the physical module or correct the project to match the actual hardware family.
Why does TIA Portal V12 not show the older 1BL00 catalog entry for the SM 421?
The TIA Portal hardware catalog is fixed to the distribution date of the TIA Portal version. Modules no longer in active distribution drop out of the catalog and must be re-added through a Hardware Support Package. Install the latest V12-compatible HSP using Options → Support Packages as described in Siemens Support entry 72341852.
Can I substitute 6ES7 421-1BL01-0AA0 in the project for a 6ES7 421-1BL00-0AA0 in the rack?
Yes, in most cases. The 1BL01 is the official successor of the 1BL00 with identical function, pinout, and diagnostic behavior. The reverse substitution (older MLFB in the project, newer in the rack) is not permitted in the project tree unless the older MLFB is present in the catalog via an HSP.
Where can I find the official firmware file for the CPU 314C-2DP (6ES7 314-6CG03-0AB0)?
The firmware file is published in Siemens Industry Online Support. Search the support portal for the MLFB 6ES7 314-6CG03-0AB0 or follow the direct link 12019198 – Firmware update S7-300 CPUs. Always verify that the downloaded file matches the exact MLFB of the physical module before applying it.