SINAMICS G150 Drive Not Active in STARTER: Problem Definition
The SINAMICS G150 is a Siemens cabinet-style low-voltage drive (frame sizes A through H, 75 kW to 2,700 kW) used for pumps, fans, compressors, extruders, and mills. It is built around the CU320-2 control unit, which exists in two hardware variants: CU320-2 DP (PROFIBUS) and CU320-2 PN (PROFINET). When you open the project in STARTER and expand the Accessible nodes tree, you can read the CU320-2 firmware and drive firmware on the right-hand panel — for example, SINAMICS G150 / CU320-2 PN / V4.5 / V4.50.30.01. If the drive object shows the red status "Drive not active", STARTER cannot establish a routing relationship with the control unit and the drive remains unreachable on both Ethernet and PROFIBUS.
The error is almost always caused by a missing or mismatched SINAMICS Support Package (SSP) for the firmware version installed on the drive, or by a STARTER release that is too old to know the drive object. STARTER V4.4 SP1, for example, predates the G150 V4.5 firmware branch and will not list the device unless the matching SSP is installed manually.
Hardware Identification: CU320-2 Control Unit Variants
Before installing any software, confirm the control unit hardware because the SSP branch is keyed to it. The two variants are physically labelled and produce different LED patterns at power-up.
| Feature | CU320-2 DP | CU320-2 PN |
|---|---|---|
| Order number (MLFB) example | 6SL3040-1MA00-0AA0 | 6SL3040-1MA01-0AA0 |
| Default fieldbus | PROFIBUS DP (X126) | PROFINET (X150 P1/P2) |
| RJ45 ports | 2 (X127 service, X140) | 3 (X127 service, X150 P1, X150 P2) |
| Default IP (PN) | n/a | 169.254.11.22 (fallback) |
| Default PROFIBUS address | 3 (DIP switches S1.1–S1.7) | 3 (DIP switches S1.1–S1.7) |
| Service port | X127 (always 169.254.11.22) | X127 (always 169.254.11.22) |
The X127 service interface is the most reliable commissioning path because its IP address is hard-coded and does not depend on PROFINET name assignment. Use X127 whenever PROFINET is misconfigured or unknown.
Root Cause Analysis: Why "Drive Not Active" Appears
STARTER carries a built-in library of device descriptions (the installed devices list under Help → Installed devices). The list covers SIMOTION, SINAMICS S, and SINAMICS G120 baseline firmware. SINAMICS G150 firmware is delivered as a separately installable SSP (file type .zip or .exe, e.g. SSP_Sinamics_G150_V04_50_30_01_14_00_00_00.exe). If the SSP version present in STARTER does not match the firmware version reported by the CU320-2, the drive object is shown as inactive and cannot be opened, downloaded to, or routed through.
Three typical root causes:
- SSP not installed. STARTER V4.4 SP1 was released before G150 V4.5. The G150 device is missing from Help → Installed devices entirely.
- SSP version mismatch. Drive carries V4.50.30.01, but only SSP V4.40.30.01 is installed. STARTER will display the device with a yellow warning icon and refuse to go online.
- Starter release too old. The STARTER executable itself is older than the minimum that supports the SSP release. For example, SSP V4.5 requires STARTER V4.5 (or later SP). V4.4 SP1 cannot consume the V4.5 SSP even after manual install.
STARTER and SSP Version Compatibility Matrix
| Drive firmware | Matching SSP | Minimum STARTER | Recommended STARTER |
|---|---|---|---|
| V4.4 SPx | SSP V4.40.xx.xx | V4.4 | V4.4 SP1 HFx |
| V4.5 (V4.50.30.01) | SSP V04.50.30.01_14.00.00.00 | V4.5 | V4.5 SP1 or later |
| V5.1 | SSP V5.1xx | V5.1 | V5.2 or later |
| V5.2 SPx | SSP V5.2xx | V5.2 | V5.4 / TIA Startdrive |
Prerequisites for Commissioning the G150 from STARTER
- STARTER V4.5 or later installed on Windows 10 / 11 (32 or 64 bit). Confirmed working with V4.4 SP1 only on firmware V4.4 branches.
- SSP installation file matching the drive's firmware. The file naming convention is
SSP_Sinamics_G150_V<FW>_xx_xx_xx_xx.exeor.zip. - PC Ethernet port or USB-to-Ethernet adapter with admin rights to set a static IP in the 169.254.x.x range.
- CAT5e or better crossover / straight cable for X127 (the service port auto-MDIX handles both).
- PROFIBUS DP cable with termination enabled on the drive and disabled on intermediate nodes, for PROFIBUS-only sites.
- Control unit firmware in a known state. If the firmware is corrupted, the Accessible nodes entry will display as
CU320-2 DP/PNwith???in the firmware fields, which indicates a card-level failure, not an SSP problem.
Solution: Installing the Correct SINAMICS G150 SSP
Follow the procedure below to bring the device description into STARTER. This resolves the "Drive not active" flag in roughly 90 % of field cases.
- Read the firmware version reported on the operator panel (AOP30) of the G150 under Menu → Commissioning → Device identification, or note the version from the Accessible nodes panel when STARTER partially lists the device.
- Open Siemens Industry Online Support and search for
SSP SINAMICS G150 Vx.x. Filter by firmware version. Download the matching SSP. Example:SSP-Sinamics-G150-V04_50_30_01_14_00_00_00.zip. - Close all running instances of STARTER, SCOUT, and TIA Portal before installing the SSP. The installer registers the device description into the STARTER installation directory (default
C:\Program Files\Siemens\Automation\STARTER\DeviceDescriptions). - Run the SSP installer with administrator rights. Accept the license note for the SINAMICS G150 family.
- Re-open STARTER. Navigate to Help → Installed devices. Confirm the G150 with the matching firmware version appears in the list. If V4.4 SP1 is in use, the V4.5 entry will not be present and a STARTER upgrade is mandatory.
Configuring the PROFINET (Ethernet) Connection
For the CU320-2 PN, the engineering path is PROFINET. The two routable interfaces are the PN ports X150 P1 / X150 P2 and the service port X127.
Service port X127 commissioning (recommended for first contact)
- Set the PC Ethernet adapter to a static address in the 169.254.0.0/16 segment, e.g.
169.254.11.21with mask255.255.0.0. Do not use a DHCP server — the X127 interface is fixed. - Connect the PC to X127 on the CU320-2. The X127 LED on the control unit should change to LINK within 5 s.
- In STARTER, click Project → Accessible nodes (or the binoculars icon). The G150 should now appear with the firmware string readable. If it still shows "Drive not active", the installed SSP is wrong and the procedure above must be repeated.
PROFINET X150 commissioning
- Assign a PROFINET device name to the drive using PRONETA or via the AOP30 at Menu → Commissioning → PROFINET → Device name. Without a name, the IO controller cannot address the drive.
- Configure the IP address in parameter p8920 (PN IP), p8921 (subnet), p8922 (gateway), and p8925 (PN interface configuration). Activate with
p8925 = 2(set & activate) and power-cycle the CU320-2. - In the STARTER project tree, right-click the drive object → Properties → Ethernet interface. Set the IP and PROFINET name to match the AOP30 values.
- Re-run Accessible nodes. The device now resolves as
Drive activeand a green check appears.
Configuring the PROFIBUS Connection (CU320-2 DP or DP-V1)
For cabinet variants built on the CU320-2 DP, PROFIBUS is the primary bus. The connector is X126.
- Set the PROFIBUS slave address on the DIP switch block S1 of the CU320-2. Valid range 1 to 126, factory default 3. The address is read on the next power-up.
- Verify PROFIBUS termination. The G150 cabinet must have termination enabled at the end of the segment; intermediate nodes must be unterminated.
- Connect the CP5611 / CP5613 / CP5711 / NETLink adapter to X126.
- Install SIMATIC NET PC software so that STARTER can talk to the PROFIBUS card.
- In STARTER, choose Project → Accessible nodes → PROFIBUS. The CU320-2 DP appears as node
3(or whatever DIP address was set). The firmware string should be readable.
Key drive-side parameters for PROFIBUS:
| Parameter | Function | Typical value |
|---|---|---|
| p0922 | IF1 PROFIdrive telegram selection | 1 (Standard Telegram 1) or 999 (free configuration) |
| p2030 | Fieldbus baud rate PROFIBUS | Detected automatically (1.5 Mbit/s typical) |
| p2042 | PROFIdrive PZD sampling time | 0 (4 ms) |
| p0925 | PROFIBUS slave sign-of-life (PZD error count) | Read-only diagnostic |
Online Routing Through STARTER
After the drive is reachable, route through the S7 controller to the drive if you are using a SIMATIC PLC (S7-300/400 with GSD file SIEM8115.GSD, or S7-1500 with GSDML GSDML-Vx.x-Siemens-Sinamics_01PNxxxx.xml):
- In STARTER, insert a SIMATIC station (S7-300 / S7-400) into the same project.
- Configure the S7 interface card (CP343-1 for Ethernet, CP342-5 for PROFIBUS) to point to the same network the drive lives on.
- Right-click the S7 station → Online → Accessible nodes. Verify the CPU is reached.
- Right-click the drive under the S7 station's I/O → Online → Connect to target system. STARTER now tunnels through the S7 to the drive. The Accessible notes flag now reads
Drive active.
Verification Procedure
- Right-click the drive → Online → Connect to target system. The status LED in STARTER turns green and the online state reads
Online / RUN. - Open the Control panel (right-click drive → Control panel) and issue a Take over control priority. Drive enables the speed setpoint on the toolbar.
- From the trace tool, capture a 1 s motor speed ramp from 0 to 50 % of p1082 (maximum speed). Confirm actual speed tracks setpoint without Follow-up fault F07900 (motor speed too high) or F08501 (PROFIdrive PZD failure).
- Execute RAM to ROM (Copy RAM to ROM icon) to persist the online change, then power-cycle the CU320-2 to confirm the change survives.
Field-Commissioning Checklist
| # | Check | Pass criterion |
|---|---|---|
| 1 | CU320-2 LEDs RDY green, COM/DP or COM/PN green or yellow blinking | No red RDY |
| 2 | STARTER Help → Installed devices lists the G150 FW version | Entry present, no warning |
| 3 | Accessible nodes resolves drive | Green check, firmware read back correctly |
| 4 | PROFINET device name and IP set (p8920–p8925) | Persistent after power cycle |
| 5 | PROFIBUS DIP address set (1–126) and termination correct | Bus terminator resistors only at ends |
| 6 | Motor encoder (if present) feedback signal verified | Trace shows clean incremental track |
| 7 | Back-up project stored on CF card and to PC | Filename includes date & FW version |
Troubleshooting Matrix
| Symptom | Likely cause | Action |
|---|---|---|
| Drive not active, accessible nodes shows firmware as V4.50.30.01 | Missing V4.5 SSP | Install SSP V4.5 for G150 |
Drive not active, firmware field shows ???
|
Corrupted CF card or absent firmware | Insert CF card with valid FW, restart CU320-2 |
| Accessible nodes empty on PROFINET | PROFINET name not assigned | Use PRONETA or AOP30 to set the device name |
| Accessible nodes empty on PROFIBUS | Wrong baud rate / termination | Recheck bus terminators, set PC CP to DP master |
| Connection drops after a few seconds | Watchdog in p2042 / p8842 too short | Increase PZD sampling time to 4 ms or 8 ms |
| F08501 PROFIdrive PZD failure | PLC in STOP | Start PLC, restore cyclic PZD |
| F08501 after online routing | Routing table missing or wrong slot | Configure passive S7 routing in Properties → Routing |
| STARTER freezes when opening project | Project created with newer STARTER than currently installed | Update STARTER to match the project version |
Common Drive-Side Fault Codes Encountered During Commissioning
| Fault | Meaning | Engineer action |
|---|---|---|
| F01000 | Internal software error | Check FW/SSP version match; reload CF if persistent |
| F08501 | PROFIdrive PZD failure (sign-of-life) | Restore cyclic PZD, lengthen sign-of-life error tolerance in p2042 |
| F08502 | Sign-of-life of PZD Telegram 1 missing | Re-validate GSD configuration in PLC |
| A08502 | PROFINET connection interrupted (warning) | Check cable, switch, port LED |
| F30001 | Overcurrent | Verify motor nameplate data in p0304 / p0305 / p0307; ramp check |
| F07801 | Motor overcurrent | Check encoder cable shielding; check motor connection (star vs delta) |
Notes on Firmware Branch Selection
The G150 line is in long-term maintenance on the V4.5 branch. Newer features and security patches live in the V5.x branch, but V5.x requires a CF card swap on the CU320-2 and a full parameter reset. For most retrofit jobs (pumps, fans, extruders up to 800 kW), staying on V4.5 with the matching SSP V04.50.30.01_14.00.00.00 remains the supported path and the one that this article targets.
FAQ
What does "Drive not active" mean in STARTER for a SINAMICS G150?
It is an accessibility flag indicating that STARTER cannot parse the device description for the drive's firmware. The drive itself is still operational; the flag only blocks the engineering interface. The most common cause is a missing or mismatched SINAMICS Support Package (SSP).
Which STARTER version supports G150 firmware V4.5?
STARTER V4.5 or later is required, along with SSP V04.50.30.01_14.00.00.00. STARTER V4.4 SP1 (even with the V4.5 SSP manually copied into the DeviceDescriptions folder) cannot host the V4.5 device object.
Can I commission a G150 over the X127 service port without knowing the PROFINET name?
Yes. The X127 port is hard-coded to IP 169.254.11.22 and works even when the PROFINET name is unassigned. Set the PC adapter to 169.254.11.21 / 255.255.0.0 and run Project → Accessible nodes to get first contact.
Why is my CU320-2 PN unreachable on PROFINET after a firmware update?
A firmware update resets parameters p8920–p8925 (PROFINET IP, subnet, name). Re-assign the IP and device name via AOP30 or PRONETA, activate with p8925 = 2, and power-cycle the control unit.
Do I need a separate GSD or GSDML file to route STARTER through a SIMATIC S7?
Yes. For S7-300/400 with PROFIBUS, install SIEM8115.GSD. For S7-1500 with PROFINET, install the matching GSDML-Vx.x-Siemens-Sinamics_01PNxxxx.xml. After installing, run Options → Install GSD in the SIMATIC Manager / TIA Portal and rebuild the hardware configuration.