Problem Overview: 3RW44 Migration to TIA Portal Stops on Option Package Warning
When migrating a STEP 7 V5.4 or V5.5 project containing a SIRIUS 3RW44 soft starter on Profibus DP into TIA Portal (V13 SP1 or higher), the migration tool raises the diagnostic:
Option package(s) missing in STEP 7 V5.4 or V5.5
The 3RW44 hardware does not appear in the TIA Portal device catalog, the migration log flags unresolved option packages, and the resulting TIA project does not contain a fully-mapped 3RW44 station. The error is non-fatal — the project still opens — but the soft starter is reduced to a generic DP slave with no symbol names, no parameter access, and no HMI tags.
Root Cause: Why TIA Portal Has No Native 3RW44 Option Package
The migration warning is raised by the TIA Portal import wizard because the originating STEP 7 V5.x project references a 3RW44 device whose symbol block, FBD library, or HSP (Hardware Support Package) is not installed on the source PC. The wizard, however, is the secondary symptom — the deeper cause is the lack of a first-class 3RW44 option package for TIA Portal.
| Generation | Native TIA Portal Option Package | Integration Method |
|---|---|---|
| SIRIUS 3RW44 | None (no OP shipped for TIA Portal V13–V18) | Profibus DP slave via GSD file (SIEM81B7.GSE / SI0181B7.GSE) |
| SIRIUS 3RW55 / 3RW5 | SIRIUS Soft Starter ES V15+ and HSP for TIA Portal V15.1+ | Native device in TIA catalog + PROFIBUS / PROFINET GSDML |
Siemens has never published a TIA Portal option package for the 3RW44 itself. Instead, the 3RW44 is integrated as a standard Profibus DP slave using its manufacturer GSD file. This is the only Siemens-supported path for the 3RW44 inside TIA Portal. The 3RW44's full parameter set, diagnostic block, and process image are then made available through the slave's I/O addresses and an optional SIMOCODE-style F-block library.
The migration log entry is essentially a soft warning: it tells you that whatever you had in V5.x (a custom FBD, a vendor library, or an option-package wrapper around the DP slave) was not on the source machine. It does not mean a TIA Portal package is missing on the target — it means no such package exists for the 3RW44 at all.
Prerequisites Before Migration
- TIA Portal V13 SP1 Update 4 or later installed on the engineering station (V15.1, V16, V17, V18 are all valid migration targets).
- STEP 7 V5.4 SP5 or V5.5 SP4 installed on the same PC with the original 3RW44 HSP / option package loaded. The source project must open cleanly in V5.x before migration.
-
Original 3RW44 GSD file available:
SIEM81B7.GSE(3RW44) orSI0181B7.GSE(PROFINET/Profibus). Download from the Siemens Product Support search for "3RW44 GSD". - SIRIUS Soft Starter ES V21 (TIA Portal) — optional, for parameterising the 3RW44 from inside TIA Portal. See Sales release for SIRIUS Soft Starter ES V21 (TIA Portal).
- SIMOCODE ES V13 SP1 or higher (already installed for migration of motor-protection devices in the same project).
- CPU with Profibus DP master port (S7-300 with CP 342-5, S7-400 CPU 41x DP, ET200S IM151 with master, or S7-1500 with CM 1542-5). For S7-1200/1500, the 3RW44 must be retrofitted to PROFINET via the DP/PN coupler (IE/PB Link PN IO).
- Read/write access to the source STEP 7 project directory (the migration wizard copies and rewrites symbols, comments, and the S7 program).
Step-by-Step: Migrating a 3RW44 Project to TIA Portal
Step 1 — Repair the Source STEP 7 V5.x Project
- Open the project in STEP 7 V5.4 / V5.5 with administrator rights.
- Resolve any "option package missing" warning on the source side first. Install the 3RW44 HSP that the original project was built with. If the original is unobtainable, install the latest 3RW44 HSP for V5.5 from the Siemens HSP download area.
- Recompile the entire S7 program: Edit → Compile and Check All. Verify the 3RW44 FB (typically FB100/FB200 class) compiles without errors.
- Run Station → Save and Compile. The 3RW44 should appear in HW Config as a DP slave with diagnostic and parameter slots populated.
Step 2 — Capture a Migration Log
- Launch TIA Portal V13 SP1+ on the same PC.
- Select Project → Migrate project → STEP 7 V5.x project.
- Browse to the
.s7pfile. - Tick Create migration log and store it next to the source project. The log lists every block, every DP slave, and every missing option package it encounters.
Step 3 — Interpret the Option Package Warning
Open the migration log. The 3RW44 entry will look similar to:
WARNING: Option package 'SIRIUS 3RW44 Soft Starter' not found
Affected station: PROFIBUS(1) - SIRIUS 3RW44 [Station address 7]
Action: device replaced by generic DP slave
This is expected and does not require a TIA Portal fix. Record the original Profibus address, the diagnostic slot assignments, and the user-defined symbol names from the V5.x symbol table — you will re-enter them manually in TIA Portal.
Step 4 — Install the 3RW44 GSD in TIA Portal
- In TIA Portal, switch to the migrated project and open the device view of the Profibus master.
- Open Options → Manage General Station Description Files (GSD).
- Browse to the directory containing
SIEM81B7.GSE(or the 3RW44-specific GSD you downloaded). - Tick the GSD and click Install.
- Confirm the entry appears in the device catalog under:
Other field devices → PROFIBUS DP → Drives → SIRIUS → SIRIUS 3RW44.
Step 5 — Reattach the 3RW44 as a DP Slave
- Drag the SIRIUS 3RW44 from the catalog onto the Profibus subnet of the migrated S7 master.
- Set the Profibus address to the same value the 3RW44 had in V5.x (e.g. 7).
- Open the 3RW44 device view and add the standard slots. Typical 3RW44 slot mapping:
| Slot | Module | I/O Length | Use |
|---|---|---|---|
| 0 | 3RW44 device | — | Station diagnostics |
| 1 | DI/DO cyclic channel 1 | 2 byte DI / 1 byte DO | Start/Stop, ready, fault bits |
| 2 | DI/DO cyclic channel 2 | 2 byte DI / 1 byte DO | Warnings, motor running, bypass |
| 3 | Analog process data (optional) | 4 byte | Motor current %, last trip value |
| 4 | Parameter channel (acyclic) | — | Read/write parameter via DP-V1 (RW-DPV1) |
- Reuse the I addresses that V5.x assigned (e.g. IB 20..23 / QB 20..22). This preserves all user logic that references
IW 22,QB 20, etc. - Re-enter the symbol names from the original symbol table:
3RW44_Cmd,3RW44_State,3RW44_Fault, etc.
Step 6 — Replace the Vendor FB (If Used)
V5.x projects commonly call a Siemens-supplied FB (e.g. FB200 SS_3RW44) from OB1. The TIA Portal migration copies the FB source, but its instance DB references the old symbol table.
- Open the migrated FB200 in the TIA Portal program editor.
- Recompile. Any unresolved symbol is highlighted in red.
- For each red symbol, repoint it to the new I/O addresses of the freshly inserted 3RW44 DP slave.
- Alternatively, replace the FB with a custom 3RW44 FB written in SCL that uses the standard DP-V1 read/write record services (WRREC/RDREC) for the acyclic parameter channel.
SIRIUS Soft Starter ES V21 (Optional, Recommended for Commissioning)
While not required for the migration itself, SIRIUS Soft Starter ES V21 (TIA Portal) provides:
- Graphical parameterisation of 3RW44 and 3RW5 devices from inside the TIA Portal project tree.
- Live diagnostics, trace, and parameter upload/download over Profibus DP-V1.
- Centralised firmware updates and parameter-set management across multiple soft starters.
See the official sales release: SIRIUS Soft Starter ES V21 (TIA Portal) — Sales Release. Confirm your TIA Portal version is on the supported list before licensing — the V21 build is tied to a specific TIA Portal release family.
3RW44 Hardware Reference Data
| Parameter | Value |
|---|---|
| Rated operating voltage Ue | 200–460 V (standard) or 200–575 V / 400–690 V (frame-size dependent) |
| Rated power at 400 V | 15 kW (3RW44 17) to 250 kW (3RW44 43) |
| Rated power at 690 V | Up to 710 kW (3RW44 43-...) in inline configuration |
| Control supply voltage Us | 115 V AC or 230 V AC (terminal block selectable) |
| Communication module | 3RW44 00-0AC00 (PROFIBUS DP) or 3RW44 00-0AE00 (PROFINET) |
| Profibus GSD | SIEM81B7.GSE |
| DP-V1 services | RDREC / WRREC supported on slot 4 |
| Number of parameter sets | 3 (set 1 = motor 1, etc.) |
| Soft ramp functions | Voltage ramp, torque ramp, ramp plus voltage limiting, soft start with kick start |
Verification After Migration
- Compile the TIA Portal project. The 3RW44 station must compile with no errors. The 3RW44 DP slave is treated as a standard slave — "s7 compatible" mode.
- Download hardware configuration to the S7 master CPU. The 3RW44 must report ready on its LED and accept the DP handshake.
- Online diagnostics: Online & Diagnostics → PROFIBUS DP → Station 7 (3RW44) → Operating state. Expect Data exchange (DF) state. If the slave stays in Parameterisation (PRM) or Diagnostic (DG), the GSD slot configuration does not match the physical 3RW44 firmware.
- Go online with the S7 program. Monitor the 3RW44 input bytes. A correct migration shows the same bit pattern as the original V5.x online view.
- Functional test: trigger a soft start from HMI / PLC. Verify the actual motor ramps up, the bypass contactor closes, and the ready bit returns to the PLC within the expected 5–30 s window depending on ramp time.
- Optional: SIRIUS Soft Starter ES V21. Open the device from the project tree, perform a parameter upload, and compare it to the original V5.x parameter set (the 3RW44 stores 3 parameter sets in non-volatile memory).
Troubleshooting Matrix
| Symptom | Probable Cause | Remedy |
|---|---|---|
| Migration log: "Option package missing" for 3RW44 | V5.x source did not have 3RW44 HSP | Re-install 3RW44 HSP in V5.x and recompile before re-migrating |
| 3RW44 not visible in TIA Portal device catalog | GSD not installed |
Options → Manage GSD, install SIEM81B7.GSE
|
| 3RW44 inserted but BF (bus fault) LED on | Profibus address mismatch between slave and project | Verify DIP switches on CB04 / PROFINET module match the configured station number |
| 3RW44 stays in PRM state | Slot length in TIA does not match actual DP slave | Recheck the slot configuration against the original HW Config of V5.x |
| Inputs read zero, outputs ignored | I/O address was changed during migration | Reassign I addresses to the V5.x originals (e.g. IB 20..23, QB 20..22) |
| FB200 in TIA Portal does not compile | Symbol table references lost | Re-enter symbols manually or port the FB to SCL with hard-coded I/O addresses |
| Acyclic parameter read (RDREC) returns error B#16#DF | DP-V1 not enabled in TIA Portal slave properties | Open slave properties → Operating mode → enable DP-V1 (RW) |
| 3RW44 trips immediately on first start | Motor current above soft-starter rating, or missing phase | Verify wiring (L1/L2/L3 / T1/T2/T3 not crossed), check phase-failure detection parameter |
| Communication drops under load | Profibus termination missing or wrong baud rate | Add terminating resistor on first/last device; confirm 1.5 Mbps max for 3RW44 |
3RW44 Migration Checklist
- [ ] Source STEP 7 V5.4 / V5.5 project compiles without warnings.
- [ ] 3RW44 HSP installed in V5.x (matching the original build).
- [ ] Migration log saved and reviewed for 3RW44 entries.
- [ ] 3RW44 GSD (
SIEM81B7.GSE) installed in TIA Portal. - [ ] Symbol names restored from V5.x symbol table.
- [ ] Vendor FB (FB200) recompiled or replaced with SCL implementation.
- [ ] HW download to CPU successful, DP slave in Data exchange.
- [ ] Soft start/stop functionally tested with the actual motor.
- [ ] Parameter set uploaded to backup via SIRIUS Soft Starter ES V21 (optional).
Notes for Sites With Mixed 3RW44 and 3RW55 Fleets
If the project also contains newer SIRIUS 3RW55 or 3RW5x soft starters, the migration behaves very differently. The 3RW55 generation has a native TIA Portal option package (HSP) and is fully integrated into the device catalog, including the acyclic parameter channel via GSDML. The 3RW44 will still appear as a generic DP slave, while the 3RW55 will appear as a fully-typed device with faceplates for SIMATIC WinCC Unified / Comfort Panels. Treat them as two separate integration paths inside the same TIA project, but keep the Profibus subnet and the diagnostic concept consistent so that the HMI operator sees both soft starters with the same look-and-feel.
Why does TIA Portal report "Option package missing" for my 3RW44?
There is no native TIA Portal option package for the 3RW44. The warning is generated because the originating STEP 7 V5.x project referenced a 3RW44 HSP that was not installed on the source PC. The fix is to install the 3RW44 HSP in V5.x first, recompile, and then re-migrate. The 3RW44 is then integrated into TIA Portal as a standard Profibus DP slave via its GSD file (SIEM81B7.GSE).
Which GSD file does the SIRIUS 3RW44 use on Profibus DP?
The 3RW44 with the optional 3RW44 00-0AC00 Profibus communication module uses the GSD file SIEM81B7.GSE. Install it in TIA Portal via Options → Manage General Station Description Files (GSD). The device then appears in the catalog under Other field devices → PROFIBUS DP → Drives → SIRIUS → SIRIUS 3RW44.
Can I integrate a 3RW44 on PROFINET inside TIA Portal?
Directly — no. The 3RW44 hardware is a Profibus DP slave. To use it on a PROFINET S7-1500 master, place an IE/PB Link PN IO (e.g. 6GK1 411-5AB10) on the PROFINET subnet, hang the Profibus subnet on the link, and configure the 3RW44 as a Profibus DP slave under the link. Newer 3RW55 / 3RW5 soft starters have native PROFINET GSDML and integrate directly.
Do I need SIRIUS Soft Starter ES V21 to migrate a 3RW44 project?
No. The migration itself only needs TIA Portal V13 SP1+ and the 3RW44 GSD file. SIRIUS Soft Starter ES V21 (TIA Portal) is an optional TIA-integrated parameterisation tool that simplifies commissioning, parameter upload, and diagnostics. It is recommended for new installations and fleet rollouts, but not required to clear the migration warning.
My migrated 3RW44 BF LED is on. What is the fastest check?
Verify the Profibus address set on the 3RW44 00-0AC00 module (DIP switches 1–7) matches the station number in the TIA Portal project. Then check that the slot configuration in the TIA Portal device view matches the original HW Config from STEP 7 V5.x — a single byte-length difference will hold the slave in parameterisation mode. Finally, confirm the Profibus cable is terminated at both ends and that no other device is using the same address.