IM151-8 PN/DP Integration via PROFINET I-Device Configuration

David Krause20 min read
PLC HardwareSiemensTechnical Reference
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

1. Problem Statement: Two Parallel IM151-8 PN/DP Filler Systems

Two SIMATIC ET200S filler systems are each controlled by an independent IM151-8 PN/DP CPU module. Each station runs an identical user program: Q0.0 = "Filler_Open", I0.0 = "Filler_Home", and so on. The two stations currently have no PROFINET link between them, no shared SCADA, and no shared symbol table.

The integration requirement is to bring both stations under a single master controller while keeping the physical I/O segments of each filler separate. The two IM151-8 PN/DP heads cannot be merged into one because the second station is being re-purposed as a remote I/O device. The challenge is that, with a single CPU, the byte-by-byte identical peripheral images of the two stations overlap on every digital bit, every analog channel, and every shared flag/DB.

Symptoms encountered without correction:

  • Both "filler open" outputs energize simultaneously when either station triggers
  • Inputs from Station 2 falsely appear on Station 1's HMI tags
  • Data blocks (DB) with the same number but different contents collide
  • OB1, OB82 (diagnostic interrupt), OB100 (restart) execute once but reflect only one set of program state
  • OB35 / OB40 cyclic and hardware interrupt sources accumulate alarm floods
Critical: Simply copying Station 2's program into Station 1 and downloading is not valid. STEP 7 / TIA Portal will not detect symbol overlap on absolute addresses, but the process I/O will physically fight, and any DB write to the same DB number from one station's program logic will corrupt the other station's data without any compile-time warning.

2. Hardware Identification and Catalog Reference

The integration solution must respect the actual module variants installed in the field. The following order numbers are relevant:

Module Order Number (MLFB) Function Notes
IM151-8 PN/DP CPU 6ES7151-8AB00-0AB0 ET200S CPU, PROFINET IO Controller + PROFIBUS DP Master Firmware V3.x
IM151-8 PN/DP CPU 6ES7151-8FB00-0AB0 ET200S CPU, PROFINET + DP, extended memory Firmware V3.x
IM151-3 PN 6ES7151-3AA20-0AB0 ET200S head module, PROFINET IO Device only No CPU, no program execution
IM151-3 PN HF 6ES7151-3BA60-0AB0 ET200S head module, PROFINET, I-Device capable Recommended for new deployments
PM-E 24 V DC 6ES7138-4CA01-0AA0 Power module for ET200S 2 A load current supply
DI 24 V DC 6ES7131-4BD01-0AA0 8 DI module Standard digital input slice
DO 24 V DC / 0.5 A 6ES7132-4BD01-0AA0 8 DO module Standard digital output slice

The integration target depends on which IM151-3 variant is on the second station:

  • IM151-3 PN (standard, 6ES7151-3AA20-0AB0) — operates only as a PROFINET IO Device. Use Method B or Method C below.
  • IM151-3 PN HF (6ES7151-3BA60-0AB0) — supports PROFINET I-Device. Use Method A if both stations must keep a CPU.

Reference: Siemens PROFINET System Description (entry ID 109747175) and the SIMATIC ET200S System Manual.

3. Integration Architecture Comparison

Three architectures resolve the dual-station duplicate-address problem. Each trades complexity against hardware change.

Aspect Method A — I-Device (Keep both IM151-8) Method B — FB Instance Separation Method C — Peripheral Address Remap
Hardware change on Station 2 None Replace IM151-8 with IM151-3 PN Replace IM151-8 with IM151-3 PN
Station 2 program execution Local (own OB1) None (passive I/O) None (passive I/O)
Symbol overlap handling Transfer area (e.g. IB 100 / QB 100) Different absolute I/O per FB instance Different process image partition
Engineering effort Medium (GSD export/import) High (refactor both programs) Low (only HW Config + symbol table)
Cyclic determinism Independent OB1 in each station Single OB1 on master, time-sliced FBs Single OB1 on master, unified process image
Diagnostics granularity Per-station OB82 Single OB82, channel errors multiplexed Single OB82, channel errors multiplexed
Fail-safe behavior Station 2 keeps running if Station 1 fails Station 2 dark if Station 1 fails Station 2 dark if Station 1 fails
PROFINET devices 2 IO Controllers + 1 I-Device 1 IO Controller + 1 IO Device 1 IO Controller + 1 IO Device
Recommendation: If the customer's scope forces replacement of Station 2's IM151-8 PN/DP with an IM151-3 PN, use Method C first (lowest risk, smallest program delta). Use Method B when Method C would push I/O outside the supported process image area or when symbol reuse with shared FC/FB logic is required.

4. PROFINET I-Device Concept (Method A)

An I-Device (intelligent PROFINET device) is a PROFINET node that is simultaneously an IO Device to a higher-level IO Controller and an IO Controller for its own lower-level PROFINET devices. The IM151-8 PN/DP supports I-Device mode from firmware V3.0.3 onward (STEP 7 V5.5 SP2 / TIA Portal V13+).

The I-Device exchanges data with the higher-level controller through one or more transfer areas. Each transfer area is a contiguous byte range in the I-Device's process image that the higher-level controller sees as its own input or output area.

Direction Slot Subslot Example Address in I-Device Example Address in IO Controller Length
I-Device → IO Controller 0 1 IB 100 ... IB 131 IB 200 ... IB 231 32 bytes
IO Controller → I-Device 0 2 QB 100 ... QB 131 QB 200 ... QB 231 32 bytes

Slot 0 / subslot 1 corresponds to the IM151-8 PN/DP PROFINET interface (the head module). Slot 0 / subslot 2 is reserved for the port interface module. The IO Controller's program references IB 200 exactly as if it were a local input module, but the bytes are physically wired to the second station's peripherals.

When the higher-level IO Controller is in STOP, the I-Device continues to execute its own OB1 locally. Outputs assigned to the transfer area behave according to the I-Device's substitution value behavior (configurable: zero, last value, or substitute value). Configure this explicitly under "I-Device Properties → Operating Mode → Behavior on Controller Stop".

5. Method A — Step-by-Step (STEP 7 Classic, SIMATIC Manager)

  1. Open HW Config of the I-Device station (the IM151-8 that becomes the subordinate CPU). Right-click the PROFINET interface and select Properties > I-Device.
  2. Enable the Operate as I-Device checkbox. The PROFINET device role changes from "IO Device" to "I-Device".
  3. Click "Transfer Areas" and add a new area:
    • Type: Input area (data from I-Device to IO Controller)
    • Slot: 0
    • Subslot: 1
    • Start address in I-Device: 100 (decimal)
    • Length: 32 bytes
  4. Add the output area with the same length, start address 100, slot 0, subslot 2.
  5. Export the I-Device as a GSD file: Station > Export > GSD file. The export will reference the I-Device by its PROFINET device name (assigned in step 6).
  6. Assign PROFINET device name: in the I-Device's HW Config, set device name to im151-8-idevice-01 and IP to 192.168.0.20, subnet mask 255.255.255.0, router 192.168.0.250.
  7. Import the GSD into the master IM151-8's project: Options > Install GSD. The I-Device appears in the catalog under PROFINET IO > I-Device.
  8. Drag the I-Device onto the master's PROFINET subnet. Set the master's view of the transfer area to start at IB 200 / QB 200.
  9. Download HW Config to both stations. Use the Assign PROFINET Device Name tool (Accessibility > Target Device) to write the device name to the I-Device's PROFINET interface.

Verification (Method A)

  • In the master CPU's online view, force Q200.0. Confirm that the I-Device's Q100.0 follows (visible via online watch on the I-Device CPU).
  • Trigger an input on the I-Device (e.g., field-switch closing I0.0 on Station 2). Confirm I200.0 on the master updates within one PROFINET update cycle (default 1 ms).
  • Disconnect the PROFINET cable to the I-Device. The master's OB82 must fire; the SF LED on the master must illuminate; the I-Device's outputs must enter substitution state.

6. Method B — FB Instance Separation (Single CPU, One IM151-3 PN)

This method applies when Station 2 has been reduced to an IM151-3 PN head module with no program execution. The master IM151-8 PN/DP runs one consolidated OB1, and each filler's logic is encapsulated in an FB that takes its I/O references as formal parameters. Each call uses its own instance DB and binds the formal I/O parameters to a different absolute address.

6.1 FB Definition

FUNCTION_BLOCK FillerControl
VAR_INPUT
  i_FillerHome  : BOOL;   // home limit switch
  i_StartCmd    : BOOL;   // HMI start command
  i_StopCmd     : BOOL;   // E-stop / HMI stop
END_VAR
VAR_OUTPUT
  q_FillerOpen  : BOOL;   // pneumatic valve
  q_FillerRun   : BOOL;   // run indicator
END_VAR
VAR
  s_State       : INT;    // 0=idle, 1=running, 2=dwell, 3=close
  s_Timer       : TON;    // dwell timer
END_VAR
BEGIN
  // ... step sequence using only formal parameters
END_FUNCTION_BLOCK

6.2 Instance Calls in OB1

// Station 1 instance - addresses default to byte 0
CALL "FillerControl" , "DB_Filler_1"
  i_FillerHome := I0.0
  i_StartCmd   := M10.0
  i_StopCmd    := M10.1
  q_FillerOpen := Q0.0
  q_FillerRun  := Q0.1;

// Station 2 instance - bind to different peripheral bytes
CALL "FillerControl" , "DB_Filler_2"
  i_FillerHome := I4.0    // IM151-3 PN slot 1, byte 0 of Station 2
  i_StartCmd   := M20.0
  i_StopCmd    := M20.1
  q_FillerOpen := Q4.0    // IM151-3 PN slot 1, byte 0 of Station 2
  q_FillerRun  := Q4.1;

6.3 Why the FB Pattern Works

The FB has no absolute I/O references inside its code body. The step sequence, timers, counters, and state machine live entirely in the instance DB's static variables. Two calls to the same FB produce two independent state machines. The output Q0.0 on the first call and the output Q4.0 on the second call resolve to physically separate PROFINET slots in the master's process image, which in turn resolve to physically separate I/O modules on the two ET200S stations.

Both instance DBs must be unique. STEP 7 will refuse to download if DB_Filler_1 and DB_Filler_2 have the same number but different contents — the safest approach is to let STEP 7 auto-number multi-instances (DB100, DB101, …) and rename only symbolically.

7. Method C — Peripheral Address Remap in HW Config

Method C is the lowest-effort path when Station 2 is reduced to an IM151-3 PN: leave both stations' programs almost untouched, but remap Station 2's peripheral byte addresses in the master's HW Config so they do not collide with Station 1.

  1. In the master CPU's HW Config, locate the IM151-3 PN head module (drag from catalog PROFINET IO > ET200S > IM151-3 PN).
  2. Place the IM151-3 PN on the master's PROFINET subnet. Assign device name et200s-station2 and IP 192.168.0.21.
  3. Slot 1 of the IM151-3 PN holds Station 2's first I/O module. Double-click the module and set its Start Address to 4 (decimal) instead of the default 0.
  4. Slot 2 (next I/O module) inherits the next free address: 5 for digital, 512 for analog, etc.
  5. Save, compile, download.

Symbol Table Edit (Method C)

Open the master's Symbol Table and edit every Station 2 symbol:

Old Symbol Old Address New Address New Symbol (recommended)
Filler_Open Q0.0 Q4.0 Filler2_Open
Filler_Home I0.0 I4.0 Filler2_Home
Filler_Pressure PIW 304 PIW 512 Filler2_Pressure
Filler_Speed PQW 304 PQW 512 Filler2_Speed

The analog channel remap follows the same rule: PIW 304 / PQW 304 in Station 1, PIW 512 / PQW 512 in Station 2. STEP 7 reserves the analog address space at 256-word boundaries; if Station 1 already uses 304..320, move Station 2 to the next free 256-word block.

8. OB, FC, FB, DB Conflict Resolution

When two identical programs are merged into one CPU, every named block collides. The CPU will accept whichever block was downloaded last; the other block's content is silently discarded. The following table enumerates the affected blocks and the resolution rule.

Block Type Conflict Source Resolution
OB1 (cyclic main) Both stations run their own OB1 Keep Station 1's OB1 as canonical; copy Station 2's logic into a section of OB1 or into a new FB
OB10..17 (time-of-day) One OB10 active in each station Keep one; remove the other from SFC configuration
OB30..38 (cyclic interrupt) OB35 used by both Keep one OB35 with merged logic, or use OB32 / OB33 with different phase offsets
OB40..47 (hardware interrupt) OB40 triggered by local DI modules on each station Single OB40 in master; identify the source via OB40_POINT_ADDR
OB55..57 (status / update / profile) Rarely used, but possible Keep one canonical block; the master will fire for both PROFINET subnets
OB80 (timeout) Watchdog of each station Single OB80 in master; identify the priority class via OB80_OB_CLASS
OB82 (diagnostic interrupt) Both stations generate diagnostic alarms Single OB82; identify the station via OB82_IO_FLAG and OB82_LOCAL_ADDRESS (high bit indicates head module number)
OB83 / OB84 (pull/plug, CPU fault) Module removal events Single OB83/OB84; PROFINET slot number identifies which station
OB85 (program execution error) Fired when an OB is missing Single OB85
OB86 (rack failure) PROFINET station failure Single OB86; identify the failed station via OB86_RACKS_FLTD / OB86_Z23 (logical address of the failed DP/PN slave)
OB87 (communication error) Fired on PROFINET alarms Single OB87
OB100 (warm restart) Restart OB on each station Single OB100 in master
OB101 (hot restart) Rare on ET200S; only if explicit Single OB101
OB102 (cold restart) Rare on ET200S Single OB102
FC / FB with same name Both stations' libraries Rename the second station's blocks with a suffix (_S2), or unify into one canonical version
DB with same number Both stations' data Re-number one set; merge logic if both are read/written
M (bit memory) Identical M flags in both Re-allocate Station 2's M flags to a different range (e.g., M20.0+)
T / C (timers / counters) Identical timer references Re-allocate Station 2 to T20..T39, C20..C39
OB82 nuance: the local address bits in OB82 are logical addresses, not physical slots. The PROFINET slot number is encoded in the upper byte of OB82_LOCAL_ADDRESS (0x00 = master local, 0x8000+ = PROFINET device index). Build a lookup table mapping logical address ranges to Station 1 / Station 2 inside OB82.

9. PROFINET Device Name and IP Address Plan

Each PROFINET node must have a unique device name and IP address. The master IM151-8 PN/DP itself owns the PROFINET device name of the IO Controller; the IM151-3 PN head module of Station 2 owns its own device name.

Role Device Name IP Address Subnet Mask Router PROFINET Port 1 Port 2
Master IM151-8 PN/DP im151-8-master 192.168.0.10 255.255.255.0 192.168.0.250 Switch port 1 Field service port
Station 2 IM151-3 PN (Method C) et200s-station2 192.168.0.21 255.255.255.0 192.168.0.250 Master port 1 n.c.
Station 2 IM151-8 PN/DP as I-Device (Method A) im151-8-idevice-01 192.168.0.20 255.255.255.0 192.168.0.250 Master port 1 Local PN subnets
HMI / SCADA scada-pc-01 192.168.0.50 255.255.255.0 192.168.0.250 Switch

Reserved address space: 192.168.0.19 for engineering stations (PG/PC), 192.168.0.1029 for PROFINET devices, 192.168.0.5059 for HMI/SCADA, 192.168.0.250 for router, 192.168.0.255 broadcast.

10. STEP 7 Classic Procedure for Method C (Field-Proven Sequence)

  1. Archive both stations' STEP 7 projects. File > Archive.
  2. Open the master CPU's HW Config. Drag the IM151-3 PN from the catalog into the PROFINET subnet.
  3. Set device name and IP per Section 9.
  4. Insert the I/O modules under the IM151-3 PN exactly in the slot order they exist on the physical station.
  5. Edit Start Address on the first I/O module to 4 (digital) or 512 (analog).
  6. Save and compile. STEP 7 will report any address collisions — fix them before download.
  7. Download HW Config to the master CPU only. PLC > Download to Target.
  8. Use PLC > Assign PROFINET Device Name to push the device name to the IM151-3 PN head module. Confirm the BF LED on the IM151-3 PN extinguishes within 5 seconds.
  9. Cycle power on the IM151-3 PN to make the device name persistent in flash.
  10. Download the symbol table only (not the program) and observe the master's online view: I4.0 should mirror the physical input wired to Station 2.

11. TIA Portal Procedure (TIA V15.1+)

  1. Open the project. Select the master CPU in the Project Tree.
  2. In the Device view, expand the master's PROFINET interface. Drag IM151-3 PN from the catalog (right pane) onto the PROFINET subnet of the master.
  3. Right-click the IM151-3 PN > Properties > PROFINET interface > Ethernet addresses. Set IP and PROFINET device name.
  4. Right-click the IM151-3 PN > Properties > Slot assignment. For each module slot, change the I/O start address: digital modules > 4; analog modules > 512.
  5. Compile and download the device configuration.
  6. Use Online > Assign PROFINET device name to write the name to the head module.
  7. Open the master PLC's Symbol Table. Add the Station 2 symbols pointing at the new addresses.
  8. Download the program blocks. Trigger a download of the symbol table by right-clicking it > Compile > Download to device.

12. Verification, Diagnostics, and Troubleshooting Matrix

12.1 Visual Verification

LED on Master IM151-8 PN/DP LED on Station 2 IM151-3 PN State Meaning Action
RUN green solid RUN green solid Both healthy None — proceed with I/O test
RUN green solid BF red flashing PROFINET connection not established Check device name match in HW Config
RUN green solid BF red solid No physical link Check cable, switch port, port LED on master
SF red solid (master) Diagnostic interrupt pending Read diagnostic buffer; expect OB82 entry
MAINT yellow flashing (master) Maintenance demanded (PROFINET) Open Diagnostics > PROFINET Diagnostics
RUN flashing (master) Master STOP or startup Read module status; check STOP cause

12.2 Web Server Diagnostics

The IM151-8 PN/DP web server (default http://192.168.0.10) exposes:

  • Information > Module Identification — order number, firmware version, serial number
  • Information > PROFINET Diagnostics — port state, link speed, frame errors
  • Diagnostics > Diagnostic Buffer — chronological OB entries
  • Information > Connected I/O — slot-by-sl slot module status

Cross-reference the diagnostic buffer with the PROFINET device name of the failed station to isolate the failure to the right head module.

12.3 PRONETA and Topology Check

Use Siemens PRONETA (free tool) to scan the PROFINET subnet, view the discovered device names, and verify that the IM151-3 PN appears with the correct name and IP. PRONETA also performs an I/O test that lets you force individual output bits on Station 2's modules — useful for verifying Method C address remapping.

12.4 Troubleshooting Matrix

Symptom Likely Root Cause Diagnostic Step Fix
Outputs from Station 1 also energize Station 2 outputs Address overlap, Method C not applied Online watch on QB 0 and QB 4; force Q4.0 and observe both modules Re-do Method C; ensure Slot 1 start address is 4, not 0
Station 2 outputs never update Device name mismatch PRONETA scan; compare with HW Config Re-assign PROFINET device name; cycle power on IM151-3 PN
Inputs from Station 2 read as zero Process image partition not updated Check PIP assignment in HW Config for Slot 1 of IM151-3 PN Assign PIP 1 (default OB1) to the slots used by Station 2
OB82 floods the diagnostic buffer Channel error on a Station 2 module not configured with OB82 Read OB82_LOCAL_ADDRESS; identify the slot Add OB82 if missing; insert channel-grace logic
OB85 fires at startup OB40 / OB82 missing in the consolidated program Read OB85 OB85_RESERVED_2 for the missing OB class Add the missing OB or disable the trigger source
Master SF LED on, BF on Station 2 Different PROFINET device name in PLC than on device PLC > Assign PROFINET Device Name Assign the correct name; reset to factory defaults if multiple devices exist
CPU goes STOP after download Two OB1 blocks with the same number Read diagnostic buffer; look for OB85 with priority class 1 Remove the duplicate OB1 from Station 2's program
FB call always reads inputs as 0 Multi-instance FB uses shared instance DB Online watch on the instance DB; confirm two different DBs were generated Re-call FB with explicit instance DB name; never use multi-instance if sharing data is required
Method A transfer area does not update I-Device export not imported; GSD outdated Catalog right-click > Update catalog Re-export GSD from I-Device project; re-import into master project
Substitution values not respected Wrong setting in I-Device properties PROFINET interface > Operating mode Set "Behavior on Controller STOP" to "Substitute value"

13. PROFINET Performance and Update Time

PROFINET update time on the IM151-8 PN/DP / IM151-3 PN combination is configurable per device in HW Config under PROFINET interface > Real-time settings > Update time. Default is 1 ms. For a two-station filler, 1 ms is adequate for digital I/O and sufficient for analog if update time is increased to 4 ms.

Update Time Suitable For Watchdog Time
250 µs High-speed motion, encoder feedback 3 ms
500 µs Fast discrete I/O 6 ms
1 ms (default) General discrete + analog I/O 12 ms
4 ms Slow analog (temperature, level) 48 ms
16 ms Diagnostic, non-critical 192 ms

The watchdog time is automatically 3 × the update time per the PROFINET specification. Do not configure the watchdog manually; doing so is a common source of unnecessary OB86 (rack failure) entries.

14. Safety Considerations

This article covers standard (non-failsafe) integration. For functional safety (F-CPU, PROFIsafe), the IM151-8 PN/DP F-variant and the F-I/O modules (e.g., 6ES7138-4FA00-0AB0 PM-E F, 6ES7136-4BA00-0AB0 4 F-DI, 6ES7136-4CA00-0AB0 4 F-DO) are required. PROFIsafe addresses are assigned in HW Config and must be unique per slot. Consolidating two F-CPUs into one F-CPU changes the PROFIsafe destination address plan; the TÜV-certified safety program must be re-validated.

Hard rule: Do not consolidate two F-CPUs into a single F-CPU without re-running the safety acceptance test. The acceptance test certificate is bound to the F-CPU hardware order number and the PROFIsafe address plan.

15. Commissioning Checklist

  • ☐ Both ET200S stations' HW Configs archived
  • ☐ Master CPU configured with both PROFINET devices (master's own PROFINET subnet, plus Station 2 as I-Device or IO Device)
  • ☐ All peripheral addresses verified non-overlapping (Method C) or encapsulated (Method B / A)
  • ☐ PROFINET device names assigned and persistent (cycled power)
  • ☐ Symbol table reviewed; Station 2 symbols renamed for clarity (Filler2_*)
  • ☐ OB82 / OB86 present in master program
  • ☐ All FC/FB/DB number conflicts resolved (renamed or re-numbered)
  • ☐ PRONETA scan shows both stations with correct device names
  • ☐ Web server accessible on master and Station 2 (if Method A)
  • ☐ Force test of one output per station; verify the correct physical output responds
  • ☐ Cable test on the PROFINET ring / daisy-chain
  • ☐ Diagnostic buffer empty after a 10-minute soak

Why does Q0.0 conflict arise when two IM151-8 PN/DP systems run identical programs?

Each CPU owns its own process image, but when both stations are placed under one CPU as remote I/O, the master IM151-8 maps Station 1's first digital output slice to byte 0 and Station 2's first digital output slice to the same byte 0 by default. Both modules physically drive outputs at the same logical address, causing simultaneous energization. Resolve by remapping Station 2 to byte 4 (Method C), encapsulating Station 2 in an FB instance bound to a different address (Method B), or using PROFINET I-Device with a transfer area at a non-overlapping address (Method A).

Can an IM151-3 PN head module act as a PROFINET I-Device?

Yes. The IM151-3 PN HF (6ES7151-3BA60-0AB0) supports I-Device mode from firmware V2.0 onward. The standard IM151-3 PN (6ES7151-3AA20-0AB0) does not support I-Device and can only operate as an IO Device. If you require I-Device functionality on Station 2 while keeping the IM151-3 form factor, use the HF variant or keep the IM151-8 PN/DP CPU as the I-Device (Method A).

What is the recommended PROFINET update time for two ET200S stations under one CPU?

For a two-station filler with mixed digital and analog I/O, 1 ms is the default and is adequate. For analog-heavy stations (temperature, pressure), increase to 4 ms. The PROFINET watchdog is automatically set to 3 × the update time and must not be configured manually.

How are diagnostic interrupts (OB82) routed when two PROFINET stations share one CPU?

The master CPU fires OB82 once per alarm event. The logical address in OB82_LOCAL_ADDRESS encodes the slot number in the upper byte and channel in the lower byte; the station can be identified by the slot range — e.g., slots 1–8 belong to Station 1, slots 100–107 to Station 2 (after Method C address remap). Build a switch on OB82_LOCAL_ADDRESS inside OB82 to branch the diagnostic handler per station.

Which OBs must be present in the master IM151-8 PN/DP after consolidating two programs?

OB1 (cyclic), OB82 (diagnostic interrupt), OB83 (pull/plug), OB85 (program execution error), OB86 (rack failure), OB100 (warm restart), and any cyclic interrupt OBs (OB30–OB38) or hardware interrupt OBs (OB40–OB47) actually used by the merged program. A missing OB triggers OB85; the missing OB class is reported in OB85_RESERVED_2.

Can the master IM151-8 PN/DP run two identical OB1 blocks (one per station)?

No. STEP 7 / TIA Portal accepts only one OB1 per priority class. If both stations' programs define OB1, keep one canonical OB1 and merge the second station's logic into either the same OB1 body or into a separately-called FB (Method B). The duplicate OB1 will be silently overwritten on download, and its logic will be lost.

How is the PROFINET device name assigned to an IM151-3 PN head module in the field?

Use PLC > Assign PROFINET Device Name in STEP 7 / TIA Portal, or PRONETA's Network Analysis > Assign Device Name. The device must be reachable on the subnet (BF LED off, link LED solid). After assignment, cycle power on the head module to make the name persistent; otherwise the name reverts to factory default on power-up.

Back to blog