Overview
When a SCALANCE XB216 replaces an existing SCALANCE X216 on a PROFINET network, the S7-1500 controller can only push an IP address and PROFINET device name into the new switch if the switch is configured as a PROFINET IO Device in the TIA Portal project and the controller has the right assigned as the IO supervisor. The XB216 is fundamentally different from the older X216 in this respect: the PROFINET IO device role must be explicitly enabled in the device configuration, and depending on the hardware variant and firmware, the GSD file, topology editor entry, and port interconnection must all match what is in the project before "Download to device" will actually overwrite the factory-default IP (0.0.0.0) and unassigned device name.
This reference walks through the exact sequence to make a CPU 1512SP F-1 PN assign an IP and PROFINET name to a new SCALANCE XB216, and it documents the field-verified failure modes engineers hit when the controller silently refuses to push configuration to the switch.
System Context and Device Identification
Reference architecture used in this article:
| Role | Device | MLFB / Part Number | Notes |
|---|---|---|---|
| IO Controller | SIMATIC S7-1512SP F-1 PN | 6ES7512-1SK02-0AB0 (typical) | PROFINET interface X1 (with separate X2 if present) |
| IO Device | ET 200SP IM 155-6 PN HF | 6ES7155-6AU00-0CN0 / ...-0HN0 | High Feature head module |
| PROFINET switch (new) | SCALANCE XB216 | 6GK5216-0BA00-2AB2 | Managed Layer 2 switch, 16x RJ45, PROFINET IO Device capability |
| PROFINET switch (old) | SCALANCE X216 | 6GK5216-0BA00-2AA2 (legacy) | Replaced in the field |
Confirm the XB216 MLFB against the nameplate before configuration. The XB-200 family ships in two major hardware revisions:
- XB-200 (initial series, up to FW V3.0): PROFINET IO Device mode is available only with a PROFINET-enabled firmware variant. Standard variants do not expose the IO Device role.
- XB-200 (from approx. FW V4.x onward, PROFINET-capable MLFBs): Full PROFINET IO Device functionality is integrated. These are typically ordered with PROFINET conformance class B/C.
Verify the exact article number on the device label, then cross-check the supported functions in the SCALANCE XB-200 operating instructions. A switch ordered without PROFINET capability cannot be promoted to an IO device by firmware update alone.
Prerequisites
- TIA Portal project version that supports the installed XB-200 GSD. For firmware V4.x and later, use TIA Portal V15.1 or newer; for V3.x use V14 SP1 or newer. Always install the latest HSP (Hardware Support Package) so the device appears in the hardware catalog.
- GSD file for the SCALANCE XB-200, installed via "Options > Manage device description files (GSD)" if the device is not in the catalog. Use the GSDML file shipped with the firmware download on the Siemens Industry Online Support portal.
- Firmware on the XB216 compatible with the TIA Portal version. A mismatch between configured firmware and physical firmware will cause online diagnostics fault "Device type / module type does not match."
- PROFINET device name and IP plan ready. The device name must be unique on the PROFINET subnet and conform to PROFINET naming rules (max 240 characters, only letters, digits, dash, underscore; must not start with a digit or dash; must not end with dash).
- Topology knowledge: which physical port on the XB216 connects to which port on the controller and to the IM 155-6 PN HF. This information must be entered in the TIA Portal topology editor.
- Engineering access to the controller (online via the same subnet or via the second interface / route).
Insert the SCALANCE XB-200 as PROFINET IO Device
Per Siemens Support entry 109744272, the insertion sequence and the options visible in the inspector depend on the XB-200 variant. The general procedure is:
- Open the TIA Portal project and navigate to the PROFINET subnet view (Devices & Networks).
- In the hardware catalog, switch the catalog source to the SCALANCE XB-200 folder. Locate the entry for XB216 in the appropriate firmware family.
- Drag the XB216 onto the PROFINET subnet. The device is added as a stand-alone PROFINET node.
- Right-click the XB216 and select "Assign IO Controller". Choose the PROFINET interface of the CPU 1512SP F-1 PN (typically X1) from the assignment dialog.
- Once assigned, TIA Portal exposes the device as a PROFINET IO Device under the controller.
Configure IP Assignment and Device Name
For the controller to push the IP address to the XB216, the option "IO Controller assigns IP address" (or in TIA Portal UI: "IP address is set by the IO controller") must be enabled for the device, and the PROFINET device name must be assignable by the IO Controller.
- Select the XB216 in the network view and switch to Properties > PROFINET interface [X1] > Ethernet addresses.
- In the PROFINET section, enter the planned PROFINET device name (e.g.,
xb216-sw01). - Tick the checkbox "PROFINET device name is assigned by the IO controller" (this is the property that allows the CPU to push a name via DCP on each startup if the device has no valid name).
- Tick the checkbox "IP address is set by the IO controller". By default TIA Portal fills the IP address and Subnet mask fields with the values used during the configuration download — these are the addresses that will be written to the device at startup by the IO controller.
- (Optional) Configure a PROFINET device number (slot 0). The XB216 in IO-Device mode occupies slot 0 for the head module; no additional slots are used for pure switching.
Build the Topology in TIA Portal
The PROFINET diagnostics and the controller's ability to push configuration on startup both rely on the topology editor entries. The X216 had its own port numbering; the XB216 uses a different port numbering scheme and a different order of RJ45 ports. Re-enter the port interconnections:
- Open Devices & Networks > Topology view.
- For each physical cable leaving the XB216, drag a connection from the relevant XB216 port (P1, P2, ... P16) to the partner port on the CPU and on the IM 155-6 PN HF.
- Verify that every used port shows a partner. Unused ports can be left without a partner; they will report "No partner" only if diagnostics are enabled for that port.
- If the existing topology entries still reference the X216 port labels, delete them and re-create the connections with the XB216 as the source. Old entries will be flagged as topology errors and will prevent successful compilation.
Compile, Download, and Assign
- Right-click the CPU 1512SP F-1 PN and select Compile > Hardware (rebuild all). Resolve any device errors before continuing; in particular, "Device type differs from configured device" must be cleared.
- Right-click the controller and choose Download to device > Hardware and software (only if different). The download pushes the IO Controller configuration, including the new device name, IP, and topology, to the CPU.
- TIA Portal offers the option to assign the PROFINET device name to the XB216 during the download sequence. Tick the box "Assign PROFINET device name" and select the target device. Use the "Update list" button to detect the new XB216 by its MAC address (visible in the Web Based Management of the switch).
- Click Assign name. The XB216 reboots and comes back with the assigned name.
- After the CPU completes the download, the controller starts the AR (Application Relationship) with the XB216. Watch the diagnostics: the XB216 should appear with a green check in the online view of "Devices & Networks" and in the diagnostic buffer of the CPU.
Enable PROFINET IO Device Mode on the Switch
The SCALANCE XB-200 has the PROFINET functionality delivered but not always activated. Open the Web Based Management of the switch (default address 192.168.1.1) and verify the following:
| WBM / CLI Path | Setting | Required Value |
|---|---|---|
| Information > PROFINET | PROFINET device mode | Enabled |
| Layer 2 > PROFINET IO | PROFINET IO Device | Activated |
| System > Restart / PROFINET | Reset to factory defaults (one-time) | Run before first assignment if the device was previously used in another network |
If the WBM does not show a PROFINET section, the hardware variant ordered is not PROFINET-capable and the switch must be replaced with a PROFINET-enabled MLFB. There is no firmware-only upgrade path.
Verification
After the sequence above, verify the following live states on the running system:
- Device name: in the XB216 WBM under Information > PROFINET, the name must match the value configured in TIA Portal exactly (case-sensitive).
- IP address: the IP shown in WBM must equal the IP configured in TIA Portal. The factory default 192.168.1.1 indicates that the controller never wrote the IP, which means the controller-side assignment is not active.
- Connection: from the CPU, online > "Accessible nodes" must list the XB216 with its assigned IP. A failure here points to a routing or topology problem, not a configuration problem.
- Diagnostic buffer: the CPU diagnostic buffer must contain an entry "PROFINET IO Device xb216-sw01 is in data exchange" or equivalent. Any "station failure," "device name not assigned," or "IP parameter error" entry indicates a specific step was missed.
- Web diagnostics: from the WBM of the CPU or via the TIA Portal online diagnostics, the XB216 should appear in green.
Troubleshooting Matrix
| Symptom | Likely Root Cause | Corrective Action |
|---|---|---|
| Controller does not assign IP; switch stays at 192.168.1.1 | "IP address is set by the IO controller" not enabled in device properties | Re-check the Ethernet addresses tab and tick the box; re-download to the CPU |
| CPU reports "Device name does not exist" | Device name assignment by IO controller not enabled, or name was never written to the physical device | Use TIA Portal "Assign PROFINET device name" dialog and push the name explicitly |
| XB216 visible in WBM but not as IO Device in TIA Portal online view | No IO Controller assigned, or controller assigned to wrong PROFINET interface | Right-click XB216 > Assign IO Controller; select CPU 1512SP F-1 PN X1 |
| Topology error: "Port P1 has no partner" | Topology editor not updated for the new switch | Re-enter all port interconnections in Topology view |
| Compile error: "Configured device type does not match" | Old X216 device entry not removed; XB216 inserted as additional node | Delete the old X216 device and the old device entry; recompile |
| Switch WBM has no PROFINET section | Non-PROFINET MLFB ordered | Replace with PROFINET-capable XB-200 MLFB; no firmware upgrade available |
| Firmware mismatch warning during download | Configured firmware version newer than physical firmware | Either update the switch firmware or downgrade the configured firmware in TIA Portal |
| IO Device drops out cyclically | Port interconnection wrong, or wrong cable to non-PROFINET port | Verify physical cabling and topology editor entries; check that the ring/monitoring ports are not assigned an IO controller |
Notes on the Old X216 vs. New XB216
The SCALANCE X216 belongs to an older product family whose PROFINET behavior and WBM structure differ from the XB-200 series. When replacing the switch in the field:
- The PROFINET device name and IP must be re-assigned; a new SCALANCE ships with empty PROFINET name and default IP.
- All configuration that was loaded into the old X216 (VLANs, SNMP, port security) is lost and must be re-applied via WBM or via TIA Portal after the IO-Device relationship is up.
- The XB-200 supports the same Layer 2 features, but the menu structure and default CLI command set differ. Plan for a configuration re-load after the IO Device handshake is verified.
Interaction with Higher-Level Network Functions
Once the XB216 is a PROFINET IO Device, the controller is the supervisor for the device's PROFINET parameters. However, the switch continues to operate as a Layer 2 switch independently of the PROFINET AR. The PROFINET AR only governs:
- Device name and IP address (DCP on behalf of the IO Controller)
- Cyclic diagnostics and alarm routing
- Topology check ("neighbor detection" via LLDP)
VLAN, IGMP, Spanning Tree, and port configuration are not part of the PROFINET data exchange and remain local to the switch. Per the TIA Portal documentation on configuring a SCALANCE device as an IO device, "Compile" and "Download to device" only write the PROFINET-related data into the controller; the local switch parameters are not pushed to the SCALANCE by the controller download and must be configured separately via WBM, CLI, or a separate TIA Portal step.
I-Device vs. Plain IO Device
If the XB216 is intended not only to be configured by the controller but also to expose its own PROFINET data (for example, port diagnostics) to the controller as I/O data, the device must be modeled as an I-Device in the TIA Portal project. A plain IO Device assignment only gives the controller the ability to write the device name and IP; it does not exchange cyclic I/O. As described in the TIA Portal I-Device characteristics documentation, an I-Device combines the role of an IO Device with the role of an IO Controller on the same PROFINET interface, which is the correct pattern when the SCALANCE is part of a sub-network that also needs to be visible to the higher-level controller.
Field-Proven Checklist Before Power-Up
- [ ] XB216 MLFB on nameplate is a PROFINET-capable variant.
- [ ] Firmware on the switch matches the TIA Portal configured firmware version.
- [ ] GSD / GSDML installed in TIA Portal and the device is in the hardware catalog.
- [ ] Device inserted in the network view, IO Controller assigned.
- [ ] "PROFINET device name is assigned by the IO controller" ticked.
- [ ] "IP address is set by the IO controller" ticked.
- [ ] Topology editor updated with XB216 port numbering.
- [ ] Old X216 device entry removed from the project.
- [ ] Compile clean, download to CPU, then assign PROFINET device name to the physical switch.
- [ ] CPU diagnostic buffer shows the switch in data exchange.
FAQ
Can the S7-1500 CPU assign an IP address to a SCALANCE XB216 like it does for an ET 200SP?
Yes, but only if the XB216 is configured in the TIA Portal project as a PROFINET IO Device assigned to the CPU, and both "PROFINET device name is assigned by the IO controller" and "IP address is set by the IO controller" are enabled. Otherwise the switch keeps its factory IP 192.168.1.1.
Why does the new XB216 not receive its IP after replacing the X216, even though the topology is identical?
The most common reason is that the old X216 device entry is still in the project, and the new XB216 was added in addition. The controller does not write the IP to a device that does not match the configured GSD and MLFB. Delete the old X216, re-insert the XB216, assign the IO Controller, and re-download to the CPU.
Do I need a PROFINET-enabled variant of the SCALANCE XB-200 to use it as an IO Device?
Yes. The PROFINET IO Device role is only available on PROFINET-capable MLFBs of the XB-200 family. A standard (non-PROFINET) variant does not expose the IO Device role in the Web Based Management and cannot be activated by firmware update.
Which TIA Portal version is required to configure a SCALANCE XB-200 as an IO Device?
TIA Portal V14 SP1 or newer is required for XB-200 firmware V3.x. For firmware V4.x and later, use TIA Portal V15.1 or newer and install the matching HSP or GSDML from Siemens Industry Online Support.
Does the controller download also write the switch's VLAN and port configuration?
No. The IO Controller download only writes the PROFINET-related data (device name, IP, topology). VLAN, Spanning Tree, and port configuration must be applied separately via the SCALANCE Web Based Management or CLI.