1. Problem Description
The ET 200iSP IM 152-1 interface module (article number 6ES7152-1AA00-0AB0) with hardware version 3 rejects a firmware update partway through transmission. The error manifests during STEP 7 / SIMATIC Manager online update as:
Reported error: "File not accepted by module"
The update operation reaches the IM 152-1 over PROFIBUS, the module begins to receive the new firmware file, then aborts mid-transfer without completing the flash procedure. The IM 152-1 returns to its prior firmware state (V2.04 in this case) without becoming bricked, but the new firmware (V2.05) is not applied. The same fault is reproducible across multiple IM 152-1 modules of identical article number and hardware revision on the same PROFIBUS segment.
This issue is specific to the PROFIBUS variant IM 152-1 (6ES7152-1AA00-0AB0). Users of the PROFINET variant IM 152-1PN follow a related but distinct procedure documented separately by Siemens.
2. Affected Hardware and Firmware Identification
| Attribute | Value |
|---|---|
| Article Number (MLFB) | 6ES7152-1AA00-0AB0 |
| Hardware Version | 3 |
| Previous Firmware | V2.04 (successfully applied Dec 2007) |
| Target Firmware | V2.05 (release 2008) |
| Engineering Tool | STEP 7 V5.x (SIMATIC Manager) |
| Engineering Path | Ethernet → CP 443-1 → S7-400 backplane → PROFIBUS CP → PROFIBUS DP segment → IM 152-1 |
| Update Variant Used | Variant 1 (online via STEP 7 HW Config) |
| Symptom | File acceptance aborts mid-stream |
Verify the exact MLFB and firmware baseline before applying any workaround. Navigate in HW Config to the IM 152-1 slot, right-click → Object Properties → Diagnostics, or read the diagnostic buffer (path: PLC → Module Information → Diagnostic Buffer) to capture the current article number, hardware release, and firmware version string.
3. Root Cause Analysis
The "File not accepted by module" message is a generic firmware-loader rejection returned by the IM 152-1 bootloader. On the ET 200iSP platform this loader performs a strict, sequential check of three preconditions before accepting the firmware container:
- Article-number match: The firmware file's embedded MLFB must exactly match the MLFB printed on the module's front label.
- Hardware-version compatibility: The firmware must be marked as compatible with the module's hardware revision. Siemens explicitly states that "when an update of the firmware is performed, it is always necessary to update to the latest version available for the respective article number." This rule implies a one-way compatibility path: certain later firmware versions may drop support for very old hardware revisions.
- Container integrity: The file must arrive without transport-layer truncation (PROFIBUS telegram loss, CRC errors, or timeout).
For the reported case (HW V3, target firmware V2.05) the most probable root cause is incompatibility between firmware V2.05 and the hardware revision 3 module. Siemens' firmware versioning policy for the IM 152-1 reserves the same firmware train for compatible hardware releases, but when Siemens publishes a new minor revision they occasionally tighten the minimum hardware baseline. The December-2007 success on V2.04 does not guarantee V2.05 acceptance because the HW V3 module's bootloader was produced before the V2.05 acceptance window opened.
4. Update Variant Selection
Siemens documents three firmware-update variants for the IM 152-1. The selection is not arbitrary: the failed variant must be abandoned for a different path; do not retry the same variant repeatedly.
| Variant | Path | Medium | When to Use |
|---|---|---|---|
| Variant 1 | STEP 7 HW Config → Target System → Update Firmware | Online via PROFIBUS | Default, HW revision supports target firmware |
| Variant 2 | MMC Update Card (SIMATIC Micro Memory Card) | Local card swap | Online update fails; module is accessible for physical card swap |
| Variant 3 | PROFIBUS direct update (alternative online procedure) | Online via PROFIBUS, different telegram sequence | Variant 1 aborts; module physically inaccessible |
Reference: Operating System Updates for IM152-1 (Siemens Support ID 21344491).
5. Solution 1: MMC Memory Card Update Procedure
The MMC route is the most reliable fallback when an online update is rejected mid-stream. The MMC carries the firmware image directly to the IM 152-1's onboard slot; the bootloader reads from the card rather than over PROFIBUS, eliminating transport-layer truncation as a failure mode.
5.1 Prerequisites
- SIMATIC Micro Memory Card (MMC) with sufficient free capacity (typically 2 MB or larger).
- Field PG or programming device with MMC writer and STEP 7 installed.
- The
.UPDfirmware file for firmware V2.05 (or whatever target Siemens confirms compatible with HW V3). - If the target firmware is genuinely incompatible with HW V3, a different target firmware must be selected before proceeding. Confirm the target via the readme or via Siemens Support.
5.2 Step-by-Step Procedure
- Insert the MMC into the programming device's MMC slot.
- Open STEP 7 / SIMATIC Manager and select File → Memory Card → Update Firmware on Memory Card (the menu text varies slightly between STEP 7 versions).
- Browse to the
.UPDfile matching the IM 152-1 article number6ES7152-1AA00-0AB0. - Confirm the article-number check; STEP 7 will reject a mismatched file.
- Write the firmware to the MMC. Verify the file is written without error.
- Power down the ET 200iSP station at the hazardous-area-approved power isolator; observe the Ex-relevant safety time before opening the enclosure.
- Insert the MMC into the IM 152-1's MMC slot with the correct polarity (label side facing outward per module marking).
- Restore power to the station. The IM 152-1 detects the MMC, validates the firmware, and flashes the image to internal flash.
- Observe the SF and BF LEDs; refer to Section 8 for the LED matrix.
- After the flash completes (BF may blink during the procedure, then go off), remove the MMC.
- Read back the firmware version via PLC → Module Information → Diagnostics to confirm.
6. Solution 2: PROFIBUS Online Update (Variant 3)
When the STEP 7 menu-driven update (Variant 1) aborts, an alternate online procedure documented as Variant 3 in the Siemens firmware-update documentation can be attempted. Variant 3 uses a different transfer sequence and is more tolerant of timing issues on degraded PROFIBUS segments.
6.1 Procedure
- Verify PROFIBUS health: open PLC → Diagnostics → PROFIBUS Diagnostics in STEP 7. Bus error rate must be zero; otherwise correct the segment first.
- Confirm the CP type and slot; the engineering station routes through the CP 443-1 to a PROFIBUS CP in the S7-400 backplane. Both CPs must be in RUN with no diagnostic entries.
- In HW Config, select the IM 152-1 station and choose Target System → Update Firmware as in Variant 1, but in the subsequent dialog select the PROFIBUS update variant explicitly if STEP 7 offers the choice.
- Increase the PROFIBUS retry count in the dialog if available; some STEP 7 SP revisions allow a "robust transfer" option that raises the telegram retry budget.
- Monitor the transfer window; do not interrupt. A typical V2.x firmware image is 1.5 to 2 MB and transfers in 2 to 10 minutes depending on PROFIBUS baud rate (1.5 Mbps typical, 12 Mbps supported).
6.2 PROFIBUS Baud-Rate Reference
| Baud Rate | Approx. Transfer Time for 2 MB Image | Recommended |
|---|---|---|
| 9.6 kbps | Not practical | No |
| 187.5 kbps | ~85 s | Acceptable for short segments |
| 1.5 Mbps | ~12 s | Recommended |
| 12 Mbps | ~2 s (plus PROFIBUS overhead) | Recommended for clean segments |
7. Solution 3: HW Config Re-targeting
If the firmware truly is incompatible with HW V3, the only path to V2.05 is hardware replacement. The compatible successor article number is documented in the Siemens catalog; for the IM 152-1 family the migration path typically ends at the latest MLFB of the same family with HW revision ≥ the minimum required by V2.05. The replaced module must be returned through RMA; confirm via Siemens Support.
8. Error Code and LED Reference
| SF LED | BF LED | ON LED | Interpretation | Action |
|---|---|---|---|---|
| Off | Off | On | Normal operation, PROFIBUS OK | None |
| Flashing | Off | On | Module diagnostic present | Read diagnostic buffer |
| Off | Flashing | On | PROFIBUS not connected / searching baud rate | Check cable, terminator, addresses |
| On | Off | On | Module fault — firmware rejected or CRC fail | Retry with MMC variant |
| Flashing | Flashing | On | Bootloader active — firmware update in progress | Do not power-cycle |
| Off | On | On | PROFIBUS address conflict or no master | Verify PROFIBUS address and master state |
| On | On | Off | Module in self-test or failed boot | Power-cycle; if persistent, MMC re-flash |
Diagnostic buffer entries for firmware rejection typically carry event ID 0xE2FE or similar with detail text "Firmware file rejected — incompatible hardware revision" or "Firmware file checksum error." Capture the buffer contents with timestamp before contacting Siemens Support.
9. Hardware-Version Compatibility Logic
Siemens' firmware policy for the IM 152-1, as stated in the official ET 200iSP firmware-update support entry, is: "always upgrade to the latest version that is available for the respective article number." This applies to the PN variant as well, where the rule is identical.
Reference: Firmware Update: ET 200iSP Interface Module IM 152-1PN (Siemens Support ID 109825299) and Firmware-Update: ET 200iSP Interfacemodul IM 152-1PN (German, Siemens Support ID 109982549).
The practical decision tree for an engineer confronted with a "File not accepted" error:
10. Verification Procedure
After every firmware update — successful or aborted — perform these checks before returning the module to production service.
- Confirm the new firmware version string in PLC → Module Information → Diagnostics. The "Firmware version" field must reflect the target.
- Confirm HW version, MLFB, and serial number unchanged.
- Read the diagnostic buffer; it must be empty of error events.
- Force I/O update on the ET 200iSP station; verify all I/O modules report OK in HW Config.
- Trigger a brief stop/start of the PROFIBUS slave; verify cyclic data exchange resumes without re-init.
- Run a 30-minute burn-in with all I/O channels exercised. Monitor SF and BF LEDs.
- Document the new firmware version, update date, technician name, and STEP 7 project revision in the plant's change log.
11. Service Request Path
If the firmware file is genuinely incompatible with HW V3 and the engineer cannot identify an alternate compatible firmware train, open a Siemens Service Request through the official Siemens Industry Online Support portal. Include:
- Full MLFB (six-digit MLFB including the
-0AB0suffix):6ES7152-1AA00-0AB0 - Hardware version: 3
- Current firmware: V2.04
- Target firmware attempted: V2.05
- Exact error text from the diagnostic buffer
- STEP 7 version and service pack (e.g., STEP 7 V5.5 SP4)
- CP 443-1 firmware version and PROFIBUS CP firmware version
- Plant serial number and module serial number
Siemens Customer Support can confirm whether an intermediate firmware exists that bridges HW V3 to a different update train, or whether module replacement is mandatory.
12. Preventive Measures and Best Practice
-
Read the readme before flashing. Every Siemens firmware package ships with a
readme.txtlisting the minimum hardware revision. Skipping this step is the single most common cause of "File not accepted" errors. - Maintain a firmware matrix in the plant documentation. Track MLFB, HW version, current FW version, and last update date for every IM 152-1 in the fleet.
- Standardize on MMC updates for HW V3 modules. The MMC path eliminates PROFIBUS transport variables and gives a deterministic result.
- Never interrupt power during a firmware flash. The IM 152-1 bootloader protects against partial flashes but a hard power loss can still leave the module in bootloader recovery mode, requiring an MMC re-flash.
- Plan updates during scheduled shutdowns. Firmware updates may briefly interrupt cyclic I/O even when successful.
- Keep STEP 7 current. Older STEP 7 SPs may not recognize newer firmware container formats; Siemens recommends the latest SP level for the deployed STEP 7 version.
- For ET 200iSP stations in Ex zones, observe the plant's hot-work and permit-to-work procedures. The IM 152-1 is hot-swappable only within its Ex certification envelope.
FAQ
What does "File not accepted by module" mean on an IM 152-1 firmware update?
It means the IM 152-1 bootloader rejected the firmware image partway through the transfer. The most common cause is incompatibility between the firmware version and the module's hardware revision. Verify the firmware's readme.txt for the minimum required HW version against the module's actual HW version before retrying.
Can I update IM 152-1 firmware without an MMC card?
Yes. STEP 7 supports an online update via HW Config → Target System → Update Firmware (Variant 1) and an alternate PROFIBUS procedure (Variant 3). However, when these fail the MMC path (Variant 2) is the most reliable fallback because it bypasses PROFIBUS transport issues entirely.
Is HW version 3 still supported by current IM 152-1 firmware?
Support depends on the specific firmware train. Siemens publishes compatibility tables in each firmware's readme.txt and on the Siemens Industry Online Support portal. For modules older than the firmware's minimum HW revision, hardware replacement or use of an intermediate firmware version may be required.
How long does an IM 152-1 firmware update take over PROFIBUS?
A typical 1.5 to 2 MB firmware image transfers in roughly 2 to 12 seconds at 12 Mbps, or 12 to 30 seconds at 1.5 Mbps, plus PROFIBUS handshake and flash time. Total elapsed time is usually under 10 minutes; do not interrupt power during this window.
Where can I download IM 152-1 firmware and confirm HW compatibility?
Official firmware files, readmes, and compatibility matrices are published on the Siemens Industry Online Support portal. Search by article number 6ES7152-1AA00-0AB0 or by support entries 21344491, 109825299, or 109982549. Do not obtain firmware from third-party sites.