Configuring First-Time IP Address on Siemens CPU 1512SP-1 PN

Overview

Every SIMATIC S7-1500 central processing unit, including the CPU 1512SP-1 PN (order number 6ES7512-1DM03-0AB0) in the ET 200SP family, is delivered from the factory without a PROFINET IP address. Unlike the CPU 1515-2 PN, which exposes an integrated display for direct IP editing on the front panel, the CPU 1512SP-1 PN has no display and must therefore be commissioned through a software tool over the PROFINET interface of the ET 200SP station or the internal PROFINET port of the CPU.

Three field-proven paths exist for first-time IP assignment:

1. Online accessible devices in TIA Portal (no project required).
2. Standalone tool SINEC PNI (Primary Network Initialization) for out-of-the-box commissioning.
3. Create a new project, insert the CPU from the hardware catalog, and download the device configuration.

All three procedures converge on the same outcome: a reachable IP/subnet/gateway written to the CPU's non-volatile PROFINET interface parameters, after which normal engineering traffic (program download, HMI tags, web server) becomes possible.

Prerequisites

CPU 1512SP-1 PN Hardware Reference

The CPU 1512SP-1 PN occupies slot 1 of the ET 200SP baseUnit. The PROFINET interface is internally routed to the busAdapter slot; inserting a BA 2xRJ45 (e.g., 6ES7193-6AR00-0AA0) or BA 2xFC (e.g., 6ES7193-6AF00-0AA0) provides the physical RJ45 or fiber ports. The interface label X1 corresponds to the PROFINET port 1 of the CPU; X2 (when present) is the second port for switch-mode operation.

For full device-specific information, including limit-monitoring hysteresis/delay behavior and counter reset mechanics, refer to the CPU 1512SP-1 PN (6ES7512-1DM03-0AB0) device manual in the SIMATIC ET 200SP Manual Collection.

Method 1 - Assigning the IP via TIA Portal "Accessible Devices"

This is the fastest method when no project exists yet.

1. Open TIA Portal and switch to Project view.
2. From the project tree select Online → Accessible devices.
3. In the Type of the PG/PC interface dropdown, pick the network adapter physically connected to the CPU (e.g., Intel(R) Ethernet Connection I219-V).
4. In PG/PC interface select the matching TCP/IP driver entry.
5. Click Update accessible devices. TIA Portal performs a DCP multicast discovery (UDP port 34964) and lists every reachable S7-1500 / ET 200SP station, including MAC address, IP, subnet mask, and PROFINET device name (empty for a brand-new CPU).
6. Select the CPU row (the MAC matches the sticker on the CPU front; for ET 200SP it matches the busAdapter label) and click Online & diagnostics to confirm a connection. If the entry shows IP = 0.0.0.0, the connection still opens because DCP is link-local and does not require an IP.
7. Open Online & diagnostics → Functions → Assign IP address (or Assign PROFINET name if you also want to set the device name).
8. Enter IP address, Subnet mask, and optionally a router address. Click Assign IP address.
9. Repeat Update accessible devices. The CPU now appears with the new IP, confirming the write was committed to non-volatile memory.

Method 2 - SINEC PNI (Primary Network Initialization)

SINEC PNI is the Siemens-bundled tool for the very first commissioning of PROFINET devices. It works independently of TIA Portal and is shipped as SINEC PNI V1.0 Service Pack 1 Update 1 (legacy line) and the newer SINEC PNI V2.0 (Microsoft .NET 4.7.2, installable on Windows 10/11).

1. Download and install SINEC PNI from Siemens Industry Online Support; the V2.0 build is typically delivered as SINEC_PNI_V2.0_setup.exe.
2. Launch SINEC PNI and select the network adapter connected to the CPU.
3. Click Search. The tool enumerates all reachable PROFINET stations using DCP. A factory-fresh CPU 1512SP-1 PN appears with IP = 0.0.0.0 and an empty PROFINET name.
4. Right-click the row and choose Assign IP address. Enter the desired IP, Subnet mask, and optionally the PROFINET device name in the same dialog.
5. Click Apply. SINEC PNI writes the parameters over DCP and verifies them by re-reading the device.

SINEC PNI is also the only way to assign a station name without a TIA Portal project, which is mandatory when the CPU is later used as a PROFINET IO device. Field experience: a strict Windows firewall or a corporate VPN virtual adapter can suppress the DCP multicast; temporarily disable the firewall rule for Siemens SINEC PNI or move the PC to a private network profile for first-time assignment.

Method 3 - Hardware Download from a New TIA Project

This method is preferred when the project is also being created from scratch and the IP, PROFINET name, and connected IO configuration are known in advance.

1. Open TIA Portal and create a new project.
2. In Devices & networks add a new device → SIMATIC S7-1500 → CPU → ET 200SP CPU → CPU 1512SP-1 PN. The exact order number 6ES7512-1DM03-0AB0 must be selected so the firmware description matches the station.
3. Open Device view → PROFINET interface → Ethernet addresses. Uncheck IP address is set directly at the device and enter the IP, subnet mask, and (if required) router address. Optionally set the PROFINET device name in the same dialog.
4. If an ET 200SP station with IM 155-6 PN is used, configure the lower slots with the required signal modules (DI/DO/AI/AO, technology modules, etc.) and the PN device name of the head module.
5. Compile the device configuration. TIA Portal generates a system data block (SDB) containing all interface parameters.
6. Connect the PC to the CPU's PROFINET port, select the CPU in the project tree, and click Download to device.
7. In the Download to device dialog choose the PG/PC interface, click Update accessible devices (the CPU is found by MAC / DCP), select it, and click Load.
8. Confirm the prompt Assign PROFINET device name — this writes the name from step 3. The IP follows with the configuration download.

This path has a strong advantage: the CPU is fully configured in a single transaction, so no second commissioning step is required to bring the PROFINET IO ring up.

Comparison of the Three Methods

Verification

After the IP has been written, verify that the CPU is reachable from the engineering station:

1. In TIA Portal repeat Online → Accessible devices → Update accessible devices. The CPU row must now show the assigned IP and the MAC address.
2. Open a Windows command prompt and execute ping <cpu-ip>. A reply confirms layer-3 reachability.
3. Open a browser and navigate to https://<cpu-ip>. The CPU web server responds with the diagnostics homepage once it has been activated in the device configuration and a user with the right password has been created (CPU 1512SP-1 PN ships with all web-server users disabled).
4. Open Online & diagnostics → Diagnostics → Diagnostics status in TIA Portal. No red entries and a green RUN LED on the CPU confirm the device has accepted the configuration.
5. From the Windows shell run arp -a; the CPU's MAC must appear bound to the assigned IP, confirming the address has been committed to the device's non-volatile storage.

Troubleshooting Matrix

Field Tips for First-Time Commissioning

• Document the IP, subnet mask, PROFINET device name, and gateway of every station directly on the cabinet layout drawing. An unrecorded address is the most common cause of subsequent support calls.
• Reserve a small block (for example 192.168.0.1 - 192.168.0.20) for the engineering PC and laptops. A fixed engineering address keeps the Accessible devices lookup deterministic.
• Always perform the IP assignment before activating the web server, OPC UA server, or any Open User Communication blocks. Cyclic services started against 0.0.0.0 can leave stale connections in the CPU that are hard to clear without a power cycle.
• After every successful first-time assignment, export the device configuration as a backup (TIA Portal: Device → Backup → Online snapshot). The export captures the SDB in plain XML, which is the only portable record of the in-station IP at the time of commissioning.
• If the CPU 1512SP-1 PN is part of a fail-safe (F-CPU) configuration, the same three methods apply, but the F-activation password must be present in the project before any F-IO can be parameterized.

FAQ