Resolving Siemens IM151HF Address Packing and OB83 Interrupt

Problem Statement: IM151HF Address Packing Disables OB83 Module Interrupt

An ET200S High Feature (HF) station built around the interface module 6ES7 151-1BA00-0AB0 exhibits a configuration conflict in SIMATIC Step7: enabling Address Packing in the IM151HF properties greys out the Insert/Remove Module Interrupt (RSE - Remove/Insert interrupt) option in the same dialog. Once packing is active, the operator has no way to mark the station as RSE-capable, and any OB83 wired in the S7-300 / S7-400 user program will not be triggered by module hot-swap events on this station.

The conflict is hardware-firmware specific. Field engineering has confirmed that the behavior is binding on the 6ES7 151-1BA00-0AB0 revision, while the 6ES7 151-1BA01-0AB0 revision accepts a configured 6ES7 151-1BA02-0AB0 GSD/HW identifier in Step7 - the project loads, both features become co-selectable, and the actual 01-series hardware continues to operate against the upgraded image. The 00-series hardware does not support this load path. This article documents the root cause, lists the available workarounds, and provides the verification procedure to confirm OB83 is firing on every planned hot-swap action.

Affected Hardware and Configuration

Root Cause: Mutually Exclusive Properties in the 6ES7 151-1BA00-0AB0 Image

The 6ES7 151-1BA00-0AB0 interface module ships a firmware image that exposes Address Packing and Insert/Remove Module Interrupt as mutually exclusive configuration attributes at the head-module level. The Step7 HW Config dialog surfaces this constraint by disabling the RSE checkbox the moment the operator selects packing. The reverse is also true: enabling RSE clears the packing selection.

The constraint is enforced inside the IM151HF firmware. The diagnostic result frame that the IM publishes on PROFINET / PROFIBUS does not carry both bits in a single configuration record, and the forwarding engine inside the 00-series module drops the slot-level diagnostic payload when packing is active. This is documented as a known behavior in the ET200S HF manual, and is the reason the 06ES7 151-1BA02-0AB0 firmware revision is required to make both features co-resident.

For the 6ES7 151-1BA01-0AB0 hardware variant, the on-board flash has the capacity to accept a 02-series configuration payload. Step7 still references the module as 06ES7 151-1BA02-0AB0 in the project, and the 01-series silicon responds to the extended capability record. The user-visible result is that the OB83 and packing checkboxes can both be set, the project compiles, and download to the IM succeeds.

The 00-series hardware predates the extended capability record. The forwarding engine in that revision does not parse the new record, so even if the operator manually forces the bits in the project, the module cannot honor both at runtime.

Understanding Address Packing in ET200S HF

Address Packing on the IM151HF combines multiple single-channel digital electronic modules into a packed byte or word inside the process image. Without packing, every 1-channel digital module occupies a full byte of process image space, even when only one bit is wired. Packing eliminates the wasted bits, which is significant for stations with many single-channel DO or DI modules.

• Granularity: Packing works at the slot level. The IM inspects each slot's module width and consolidates adjacent 1-channel modules into a packed channel image.
• Cost: Packing disables per-slot diagnostic granularity. The packed byte is reported as a single channel, and slot-level OB83 events (insert / remove) for the individual modules inside the packed group are not generated.
• Use case: High-density single-channel solenoid or indicator modules where address space is the bottleneck, and where individual hot-swap diagnostics are not required.

Understanding OB83 Insert/Remove Module Interrupts

The Insert/Remove Module Interrupt is the S7-300 / S7-400 mechanism by which the CPU is informed that a module has been physically pulled from or pushed into a slot of a distributed I/O station. The CPU reacts by calling OB83 with a start information block that identifies the logical base address, the event (inserted, removed, faulty, or returned-with-fault), and the slot number.

OB83 is mandatory for any application that must hot-swap an ET200S module without stopping the CPU. The organization block is documented in the S7-300/S7-400 system and standard functions reference. The start information layout is shown in the table below.

OB83 documentation in TIA Portal is published at the Siemens docs portal and is also valid for the classic Step7 V5.x environment: Insert/remove module interrupt organization block (OB 83) (S7-300 / S7-400).

Diagnostic Procedure

1. Open the Step7 project and navigate to HW Config for the ET200S HF station.
2. Double-click the IM151HF slot to open the Properties - IM151HF dialog.
3. Switch to the Address tab and check the Address Packing checkbox.
4. Switch to the Basic Parameters or Operating Mode tab (label varies by Step7 version) and inspect the Insert/Remove Module Interrupt checkbox.
5. Symptom: The checkbox is greyed out and unchecked. This confirms the 00-series hardware or an out-of-date HW identifier in the project.
6. Right-click the IM151HF slot, choose Object Properties > Identification, and read the Order Number and Firmware fields. Confirm whether the entry is 6ES7 151-1BA00-0AB0, ...1BA01-..., or ...1BA02-....
7. Compare with the physical module label on the front of the IM151HF in the cabinet. The label must match the project order number for the configuration to load.
8. Cross-check the diagnostic buffer of the S7 CPU: any failed download of the HW configuration will be logged with event ID W#16#4502 or W#16#4503 (configuration error / parameter assignment error), and the associated diagnostic frame names the slot of the IM151HF.

Solution Path 1: Project Configuration Update on 01-Series Hardware

This is the preferred workaround when the cabinet contains a 6ES7 151-1BA01-0AB0 module. The 01-series silicon accepts the 02-series configuration payload, so the project is upgraded without touching the hardware.

1. In HW Config, right-click the IM151HF slot and choose Replace Object.
2. Navigate to SIMATIC 300 > PROFINET IO / PROFIBUS DP > ET200S > Interface modules > IM151HF > 6ES7 151-1BA02-0AB0 and accept.
3. Open the IM151HF properties dialog and re-confirm both Address Packing and Insert/Remove Module Interrupt are checked.
4. Compile (Station > Consistency Check) and save.
5. Download the HW configuration to the IM151HF only - right-click the slot and select Target System > Download to Module. The CPU must be in STOP for HW Config download of a head module.
6. Verify the diagnostic buffer of the CPU contains event W#16#4302 (module OK) for the IM151HF slot after download.

Solution Path 2: Firmware Update Within the Same Hardware Variant

For cabinets that have the 00-series IM151HF, the only firmware-side change that helps is moving to a 02-series-capable image. The 00-series hardware does not support the load path for this image. If the customer requirement is to keep the 00-series part number in service, the packing-versus-OB83 conflict cannot be resolved at the IM level. The recommended actions are:

• Replace the head module with a 01-series or 02-series part physically. Both are electrically and mechanically compatible in the same ET200S backplane.
• Maintain the existing 00-series part and accept the limitation: pick one feature, either Address Packing or OB83, but not both.

Solution Path 3: Architectural Alternatives

If physical hardware migration is blocked, the application can be refactored to drop one of the two features. The trade-offs are documented below.

Step7 Configuration Procedure for the Working Combination

1. Open the SIMATIC Manager and load the S7 project.
2. In HW Config, locate the ET200S HF station on the PROFINET or PROFIBUS subnet.
3. Replace the head module identifier with 6ES7 151-1BA02-0AB0 (or verify the field-mounted module is at least 6ES7 151-1BA01-0AB0).
4. Open the IM151HF properties dialog and set:
   • Address Packing: enabled
   • Insert/Remove Module Interrupt: enabled
   • Diagnostics Interrupt: enabled (prerequisite for OB83 to fire on the controller)
5. Add OB83 to the S7 program. At minimum, write a counter and a diagnostic buffer entry so that pull/plug events are observable in the controller.
6. Compile and download the HW configuration and the OB83 source.
7. Run the consistency check and the module information dialog to verify no configuration errors remain.

Verification and Commissioning Checks

1. Bring the CPU to RUN.
2. Insert a known-good digital module (e.g. a 2DO HF) into slot 4 of the ET200S HF station.
3. Pull the module within 5 seconds of insertion. The CPU should call OB83 with event W#16#3362 (removed).
4. Re-insert the module. The CPU should call OB83 with event W#16#3361 (inserted) and then W#16#3364 (return-with-fault), which clears once the module is fully online.
5. Read the diagnostic buffer of the CPU and confirm four entries appear in the order: insertion, removed, inserted, OK.
6. Open Module Information for the IM151HF in HW Config (online) and verify the Operating Mode tab shows both features active.
7. Cycle the IM151HF power (24 V off, on) and confirm the configuration reloads with both checkboxes intact. A misconfigured IM151HF will revert to defaults on power cycle.

Diagnostic and Fault Matrix

Module Variant Comparison

Field-Proven Recommendations

• Before opening a Step7 project, physically read the IM151HF order number and firmware label. The cabinet, not the project, is the source of truth.
• Reserve the project identifier for the 02-series whenever the cabinet has at least 01-series hardware. This keeps the option to enable both Address Packing and OB83 in HW Config.
• When hot-swap diagnostics are mandatory, write OB83 first and verify it fires with the pull/plug test in the verification section before adding any application logic on top.
• Do not rely on third-party GSD files for the IM151HF. The Siemens-supplied GSD / HSP exposes the packing-versus-RSE constraint correctly, and third-party variants have been observed to mask the conflict.
• Document the choice in the project header: "IM151HF Packing = ON / RSE = ON" or "Packing = OFF / RSE = ON, poll diagnostics at OB1 tick = 200 ms". This avoids re-discovering the constraint at the next service event.

FAQ