Problem Overview
The SIMATIC S7-300 CPU 319-3 PN/DP (order number 6ES7 318-3EL00-0AB0) is a high-end S7-300 processor that combines a PROFINET interface, a PROFIBUS-DP master/slave interface, and an additional MPI/DP interface in a single module. Although it belongs to the S7-300 family that was historically programmed with STEP 7 V5.x (SIMATIC Manager), the device is fully supported by TIA Portal V15 — but only when both the engineering software and the target firmware are at the correct revision level, and the matching Hardware Support Package (HSP) is installed.
The most common symptoms reported in the field are:
- The CPU does not appear in the TIA Portal V15 device catalog under SIMATIC S7-300 > CPU.
- Drag-and-drop of the CPU into a new S7-300 station fails with "Device not found in catalog" or "HSP missing".
- Online > Accessible nodes returns no S7-300 device even though
pingto the PROFINET interface succeeds. - Upload from device to TIA Portal V15 returns empty blocks, missing symbol table, or "compilation required" errors for SCL sources that were originally built in STEP 7 V5.x.
All four symptoms trace back to the same root-cause family: the TIA Portal V15 installation is missing the HSP that registers the 6ES7 318-3EL00-0AB0 module, or the project was originally created in STEP 7 Classic and the upload path is being attempted through the wrong tool.
Supported Firmware Matrix
The order number 6ES7 318-3EL00-0AB0 ships with firmware V2.6 by default. Siemens shipped three firmware releases against this MLFB, all of which are supported in TIA Portal V15 with the matching HSP:
| Firmware | Release status | TIA Portal V15 minimum HSP | Notes |
|---|---|---|---|
| V2.6 | Initial release for MLFB 0AB0 | HSP 0183 (TIA V15.0 baseline) | Default on shipment; most common in field |
| V2.7 | Functional update | HSP 0191 or later | Bug fixes for PN stack |
| V2.8 | Latest released firmware for 0AB0 | HSP 0202 or later | Required for full TIA V15 SP1 feature parity |
You can read the installed firmware version on the CPU display by navigating Menu > PLC > Information > Firmware Version, or online in STEP 7 / TIA Portal under Online & Diagnostics > CPU Information. The MLFB printed on the front of the module must read 6ES7 318-3EL00-0AB0 — the older 6ES7 318-3EL01-0AB0 uses firmware V3.x and is not the same device.
Root Cause: Why the CPU Is Missing from the Catalog
TIA Portal does not ship with a complete device catalog at install time. Each device family (S7-300, S7-400, ET200, SINAMICS, etc.) is registered into the catalog through a Hardware Support Package. The S7-300 CPU catalog at the TIA V15 baseline DVD only includes a subset of CPUs that were current in 2018. The 6ES7 318-3EL00-0AB0 was added to the catalog as part of HSP 0183 and refined in subsequent HSPs.
When the catalog entry is absent, the CPU cannot be inserted into a project, even though the online connection may still work via the device's PROFINET or MPI interface. This is the single most common reason a control engineer concludes that "TIA V15 does not support" the module.
Secondary causes
- Outdated TIA V15 build. Siemens released V15, V15 SP1, and V15 SP2. Each contains baseline HSP revisions. Older builds may list the CPU but with reduced online functions.
- License / version mismatch. A TIA V15 installation on top of a V14 project migrated into V15 sometimes needs the HSPs to be re-applied after migration.
- Project hardware catalog not refreshed. Even after installing a new HSP, the open project must be re-opened or the device catalog re-indexed before the new entry is visible.
Solution 1: Install the Missing HSP with TIA Updater
Siemens delivers HSPs and TIA Portal Service Packs through the Totally Integrated Automation UPDATER (TIA Updater). This is a separate Windows application that runs alongside TIA Portal and queries the Siemens update server.
Step-by-step procedure
- Close TIA Portal completely.
- Launch Totally Integrated Automation UPDATER from the Windows Start menu (path:
Siemens Automation > Totally Integrated Automation UPDATER). - On first run, configure the update server URL if not preset. The default points to
https://support.industry.siemens.com. - Click "Display available updates". The tool enumerates all installed TIA products (V15, V15 SP1, V15 SP2, etc.) and lists every applicable HSP and Service Pack.
- Select at minimum:
- The latest Service Pack for your TIA V15 (V15 SP2 at the time of writing is the final V15 release).
- The latest HSP for SIMATIC S7-300 available for V15 (HSP 0202 or later is typical).
- Click "Download and install". The download can exceed 4 GB; use a wired connection.
- Restart the PC when prompted — HSP installation touches protected system directories.
- Open TIA Portal V15 and open the project (or create a new S7-300 station). Verify the CPU
6ES7 318-3EL00-0AB0is now present under Devices & networks > Add new device > SIMATIC S7-300 > CPU > CPU 319-3 PN/DP.
HSP_xxxx_xxx_V15_x_x_x_x.exe.Solution 2: Use STEP 7 V5.5 for Legacy Projects
If the CPU was originally programmed in STEP 7 Classic (SIMATIC Manager) and the goal is only to add a few I/O cards or modify a couple of blocks, do not migrate the project to TIA Portal V15 just to upload it. Use STEP 7 V5.5 + SPx directly:
- Install STEP 7 V5.5 with the latest Service Pack and the optional S7-300 HSP for V5.5 (this is a different HSP mechanism than TIA Portal).
- Open SIMATIC Manager and connect to the CPU via PROFINET, PROFIBUS-DP, or MPI.
- Perform an Upload Station to PG. The full project, including symbol table, SCL sources, and comments, is recovered in STEP 7 native format.
- Make the required I/O additions and block modifications.
- Download back to the CPU.
This workflow is the lowest-risk path for legacy S7-300 installations. TIA Portal's online upload path is acceptable for TIA-native projects, but it should not be used as the first choice for STEP 7 V5.x code.
Solution 3: Configure the Online Connection Path
Once the CPU appears in the catalog and the project opens, configure the correct PG/PC interface for online access. For the 319-3 PN/DP, three interfaces are available and the choice depends on the plant network topology:
| Interface | Connector | Default IP / address | Use case |
|---|---|---|---|
| PROFINET (X1) | RJ45 | 0.0.0.0 (unset at ship) | Modern plant network, TCP/IP routing |
| PROFIBUS-DP (X2) | 9-pin D-sub | Address 2 (default) | Existing DP segments, retrofit work |
| MPI/DP (X3) | 9-pin D-sub | Address 2 (default) | Direct PG cable, older tools |
Assigning the PROFINET IP
Because the CPU ships with 0.0.0.0, an initial IP must be assigned before any TCP-based engineering tool can find it. The two practical options are:
-
From the CPU display:
Menu > PLC > Information > IP Address— set IP, subnet mask, and a router if needed. - From SIMATIC Manager: PLC > Edit Ethernet Node — browse the network, select the CPU by MAC, and assign an IP.
PG/PC interface assignment in TIA Portal
- Open the project and select the S7-300 station.
- From the menu, choose Online > Accessible devices.
- In the "PG/PC interface" dropdown, select the network adapter bound to the subnet where the CPU lives (e.g., Intel I219-V — TCPIP for PROFINET access, or the CP5611/CP1623 driver for PROFIBUS).
- Click Start search. The 319-3 PN/DP should appear with its PROFINET name and IP.
Upload Limitations from STEP 7 Classic to TIA V15
The TIA Portal upload-from-device function (introduced and improved across V14, V15, V15.1, V15.2) has known limits when the source program was built in STEP 7 V5.x:
| Object | Recovered in TIA V15 upload? | Notes |
|---|---|---|
| OB / FB / FC source (LAD/FBD) | Yes, as compiled blocks | Original STL/FBD re-render only |
| SCL sources (textual) | No, only the compiled FB/FC | Re-engineer from comments where possible |
| Symbol table | Partial | Only absolute addresses appear; comments and names are lost |
| Password-protected blocks | No, content is hidden | Password must be known beforehand |
| Know-how-protected blocks | No | Always hidden on upload |
| DB with UDT instances | Yes, as compiled DB | UDT structure preserved as long as UDT is also uploaded |
Micro Memory Card Requirement
The CPU 319-3 PN/DP is part of the S7-300 CPU 31xC family which has no integrated load memory. Operation requires a SIMATIC Micro Memory Card (MMC) inserted in the slot on the front of the module. A full project download, a firmware update, and any operation that touches the load memory all require a working MMC.
| Use case | Minimum MMC size | Recommended Siemens MMC order number |
|---|---|---|
| Small program (< 1 MB) | 64 KB | 6ES7 953-8LF00-0AA0 |
| Typical 319-3 program with libraries | 4 MB | 6ES7 953-8LM00-0AA0 |
| Large project with C/C++ runtime | 8 MB or larger | 6ES7 953-8LP00-0AA0 |
| Firmware update buffer | 8 MB | 6ES7 953-8LP00-0AA0 |
Symptoms of a missing or write-protected MMC include SF (System Fault) LED steady on after power-up, STOP LED with no transition to RUN, and download failures with error code 80:006B. Insert the MMC with the CPU powered off; a hot-plug insert is not supported.
Verification Checklist
After installing the HSP and configuring the online path, walk through the following checks to confirm a working TIA V15 ↔ 319-3 PN/DP session:
- Open the project and confirm the CPU 319-3 PN/DP appears in the device tree with order number
6ES7 318-3EL00-0AB0and the actual firmware version installed on the module. - Compile the project (Project > Compile all) with zero errors.
- Go online (Online > Go online). The status indicator next to the CPU should turn green.
- Open Online & Diagnostics and read the diagnostic buffer. No entry should report "Firmware version mismatch" or "HSP inconsistency".
- Download a small hardware change (e.g., add a DI16 module to slot 4) to confirm hardware configuration download works.
- Stop the CPU, download the full project, and restart. The CPU should reach RUN with no SF LED.
- On a second PC with STEP 7 V5.5 installed, repeat the connection via the same PROFINET IP — both tools should be able to establish an online session in parallel.
Troubleshooting Matrix
| Symptom | Likely cause | Action |
|---|---|---|
| CPU not in device catalog | HSP not installed | Run TIA Updater, install latest S7-300 HSP for V15 |
| CPU in catalog but marked as firmware V3.x | Wrong HSP variant pulled in | Verify MLFB is 0AB0 (V2.x firmware), not 0AB0 successor |
| Online search returns no device | PG/PC interface set to wrong adapter | Set PG/PC interface to the NIC on the same subnet as the CPU |
| Online search returns device but Go Online fails | CPU has password protection | Enter password; or use the protected offline project |
| Download fails with 80:006B | No MMC or MMC full | Insert a 4 MB+ MMC and reformat via PLC > Format Memory Card |
| SF LED on, STOP LED on, no RUN | MMC missing or write-protected | Power off, insert MMC, power on, perform memory reset |
| Upload produces empty DBs | Original SCL sources, password-protected | Use STEP 7 V5.5 + original archive for round-trip |
| Compilation warns "HSP outdated" | HSP older than Service Pack | Re-run TIA Updater and install the latest HSP matching the installed SP |
| PROFINET name appears as "<unknown>" | PROFINET device name not assigned | Assign PROFINET name in Online & Diagnostics > PROFINET device name |
Field-Commissioning Tips
When you eventually have the project open in TIA V15 and the CPU reachable online, the following practical tips shorten commissioning on a real plant floor:
- Export the symbol table as CSV from STEP 7 V5.5 before touching the project in TIA Portal. TIA V15 import of symbol tables accepts CSV with the legacy format, which is faster than retyping tag names.
- Keep STEP 7 V5.5 installed on a second engineering PC. A 319-3 PN/DP can host parallel online sessions from V5.5 and V15 — useful for cross-checking block content when source recovery is in doubt.
- Document the PROFINET device name assigned to the CPU. A name reset (factory reset) wipes the name and you will need to re-assign it before the IO controller can find the device on the network.
- Back up the MMC image after every successful project download. Use the online function PLC > Save to memory card to mirror the live program to an external MMC before any field change.
Cross-Platform Notes
Engineers moving from TIA V15 to TIA V16 or V17 should be aware that the same 6ES7 318-3EL00-0AB0 is supported in V16 and V17 with the matching HSP family. Project migration from V15 to V16/V17 preserves the CPU and its I/O configuration. The reverse — downgrading a V16/V17 project to V15 — is not supported and will fail compile.
For an S7-300 fleet that includes both the older 312/314/315 CPUs and the 319-3, keep the HSPs for both S7-300 and S7-300C variants installed. Some S7-300C CPUs (e.g., 314C-2 PN/DP) have separate HSP entries that V15 ships with but that V15 SP1 sometimes refreshes.
FAQ
Does TIA Portal V15 support the S7-300 CPU 319-3 PN/DP (6ES7 318-3EL00-0AB0)?
Yes. TIA Portal V15 supports the CPU on firmware versions V2.6, V2.7, and V2.8 once the matching S7-300 Hardware Support Package (HSP 0183 or later) is installed via the Totally Integrated Automation UPDATER.
Where do I find the S7-300 HSP for TIA V15?
Open the Totally Integrated Automation UPDATER from the Windows Start menu, click "Display available updates", and select the latest HSP for SIMATIC S7-300 in TIA V15. The tool downloads and installs it automatically. Offline installations can use the HSP executable downloaded from the Siemens Support portal.
Why is the 319-3 PN/DP not in my device catalog after installing the HSP?
Re-open the project and refresh the device catalog (Options > Device catalog > Refresh). If it still does not appear, confirm the installed TIA build is V15 SP1 or later and that the HSP matches the installed Service Pack.
Can I upload a STEP 7 V5.x program from the 319-3 into TIA V15?
Yes, but the upload recovers compiled blocks and partial symbol data only. Password-protected blocks, SCL sources, and know-how-protected FBs are not reconstructed. For lossless recovery, use STEP 7 V5.5 + SIMATIC Manager to upload the original project.
Does the 319-3 PN/DP need a Micro Memory Card?
Yes. The CPU has no integrated load memory and requires a SIMATIC MMC (recommended 4 MB or larger, e.g., 6ES7 953-8LM00-0AA0) for program storage, firmware updates, and download operations. Without an MMC the CPU stays in STOP with the SF LED on.