Problem Overview
Engineers commissioning a SINAMICS G120 drive equipped with a CU230P-2 Control Unit (CU230P-2 HVAC, CU230P-2 DP, CU230P-2 PN, or CU230P-2 BT) frequently report that the USB commissioning cable fails to enumerate on the PC even though STARTER (or Startdrive) is already installed. Windows Device Manager typically displays the generic SINAMICS G120 device family driver, but no virtual COM port appears, and STARTER cannot establish an online connection to the Control Unit.
The problem is most acute when the Control Unit is on the engineer's desk while the Power Module remains bolted into the customer cabinet. A pre-delivery bench test must therefore be run from a CU that is physically separated from its PM. Adding to the confusion, the SINAMICS G120 Operating Instructions state that the USB driver is supplied on the installation DVD shipped with the drive, which most field engineers never receive when a CU is ordered as a spare or replacement part. This article documents the field-proven procedure to install the missing USB-serial adapter driver, assign the correct PG/PC interface, and bring a CU230P-2 online without ever connecting a Power Module.
Hardware Identification and Variants
Before troubleshooting, confirm the exact Control Unit variant. The CU230P-2 family shares firmware architecture and USB behavior, but fieldbus interfaces differ and influence which commissioning parameters you can edit offline.
| Variant | Article Number (6SL3...) | Fieldbus / Protocol | USB Port |
|---|---|---|---|
| CU230P-2 HVAC | ...-0AE31-... (typical) | USS / Modbus RTU / BACnet MS/TP / FLN P1 | Mini-USB, type B |
| CU230P-2 DP | ...-0AE32-... | PROFIBUS DP | Mini-USB, type B |
| CU230P-2 PN | ...-0AE33-... | PROFIBUS DP + PROFINET | Mini-USB, type B |
| CU230P-2 BT | ...-0AE34-... | USS / Modbus RTU / BACnet | Mini-USB, type B |
The CU250S-2 variants (also part of the G120 family) share the same USB stack and use the identical driver set described below; the procedure is interchangeable.
Prerequisites
Before starting, verify the following:
- Commissioning software: STARTER V4.1.5 or higher (V5.x recommended for current firmware), or Startdrive V15 or higher in TIA Portal. STARTER can still be downloaded as the legacy commissioning tool from the Siemens Industry Online Support entry at STARTER commissioning tool (entry ID 10804985).
- Operating system: Windows 7 SP1, Windows 10 (1809 or later recommended), or Windows 11. Windows 8/8.1 also works but signed-driver behavior changed significantly with Windows 10 1607.
- USB cable: Standard USB 2.0 A-to-Mini-B cable, 3 m or shorter. Active cables or hubs may prevent enumeration.
-
24 V supply for the CU: External 24 V DC (0.5 A minimum, 1 A recommended) wired to terminals
1(+24 V) and2(0 V) on the Control Unit. The CU must be powered independently of the Power Module. - Administrator rights on the PC, required to install the unsigned or WHQL-signed USB driver and to register the PG/PC interface.
Root Cause: Why the USB-Serial Driver Is Missing
The CU230P-2 Control Unit exposes two USB Human Interface Devices on its Mini-USB port: a generic SINAMICS G120 HID-class device and a USB-to-serial bridge based on the FTDI (or, in newer firmware, the Silicon Labs CP210x) chipset. STARTER installs the HID driver automatically when the installer detects a supported Siemens drive family, but the virtual COM port driver is packaged separately inside the STARTER DVD under:
STARTER Installation DVD
└── Driver
└── USB
├── CP210x_VCP_Win_XP_S2K3_Vista_7
└── ftdi2xx.inf / ftdibus.inf
└── Starter.exe
If the engineer installs STARTER from a network share or downloaded ISO without selecting the "Install USB driver" custom option, only the HID portion is registered. Windows Device Manager will then show SINAMICS G120 under Human Interface Devices, but Ports (COM & LPT) will be empty and STARTER's Accessible nodes search will return nothing.
A second failure mode occurs on Windows 10 1607 and later: Microsoft disabled automatic installation of unsigned drivers. If the CP210x or FTDI driver on the DVD predates the Windows version (typical for pre-2017 DVDs), Windows silently rejects it. The device appears as Unknown device in Device Manager.
Step-by-Step: Install the USB Driver Without the Installation DVD
The procedure below works whether or not the original installation DVD is available. It uses only files already present on a STARTER installation or downloads from the chipset vendor's signed Windows driver catalog.
-
Verify STARTER is installed. Open the Start menu and confirm
SIMATIC ManagerorSTARTERappears. If absent, run the STARTER setup as Administrator. - Connect the CU230P-2 to 24 V at terminals 1 and 2. Wait for the RDY LED to settle (steady green or slow orange, no fault blink).
- Plug the USB cable from the CU to the PC. Windows will attempt to enumerate two devices.
- Open Device Manager (devmgmt.msc). Expand Human Interface Devices – you should see SINAMICS G120. Expand Ports (COM & LPT) – if no Siemens USB-Serial Converter (COMx) appears, the virtual COM driver is missing.
-
Locate the driver package:
-
Option A – From STARTER install path: Browse to
C:\Program Files\Siemens\Automation\STARTER\Driver\USBorC:\Program Files (x86)\Siemens\Automation\STARTER\Driver\USB. Look for eitherslabvcp.inf(Silicon Labs CP210x) orftdibus.inf(FTDI). - Option B – From chipset vendor: Download the current signed Windows VCP driver from Silicon Labs CP210x VCP driver or FTDI VCP driver. Pick the x64 build for 64-bit Windows.
- Option C – From Siemens support: Use the relocation procedure described in SINAMICS G120 CU230P-2 operating instructions (entry 109751321) under "PC connection kit / USB driver relocation".
-
Option A – From STARTER install path: Browse to
- Right-click the unknown device (or the SINAMICS G120 HID entry), choose Update driver → Browse my computer for driver software.
- Point to the .inf folder selected in step 5. Tick Include subfolders. Click Next.
- Approve the Windows security prompt to install the driver. If Windows reports a code 52 (digital signature) error, right-click the .inf, choose Properties → Digital Signatures → Details → View Certificate → Install Certificate → Local Machine → Trusted Publishers, then retry.
- Confirm a COM port is assigned. Device Manager should now show Siemens Automation USB-Serial Converter (COMx) under Ports. Note the COM number.
- Restart STARTER so it refreshes its interface list.
bcdedit /set nointegritychecks on only as a last resort during commissioning. Disable test signing again after the driver is loaded: bcdedit /set nointegritychecks off.PG/PC Interface Assignment (S7USB)
With the COM port present, STARTER still requires the PC to bind it to a logical interface called S7USB. Without this binding, STARTER searches only TCP/IP nodes and never sees the local USB link.
- Open Control Panel → Set PG/PC Interface (the 32-bit Siemens applet, not the modern Windows one).
- Click Properties on S7USB. The default selection should be USB.
- If S7USB is missing, click Select..., scroll to S7USB, and add it.
- Confirm the COM port shown in Device Manager matches the S7USB assignment.
- Click OK and close the applet.
In TIA Portal / Startdrive, the equivalent binding is in Online → Accessible nodes. The CU will appear with USB icon once the project is recompiled.
Commissioning the CU230P-2 Without a Power Module
A common misconception is that a Control Unit must be docked to a PM to function. For commissioning purposes the CU only needs:
- 24 V at terminals 1/2 (logic supply).
-
EP / Enable Pulses terminal
31driven high (+24 V). The factory default is no enable, so a CU on the bench will refuse to run even though it powers up.
Apply 24 V to terminal 31 and the CU transitions from Ready (off) to Ready (on). Motor terminals U/V/W remain open-circuit because the IGBTs are inside the PM, which is fine for parameter editing and Modbus testing.
| CU230P-2 Terminal | Signal | Required for bench test? |
|---|---|---|
| 1 / 2 | +24 V / 0 V (logic supply) | Yes |
| 31 | EP enable pulses (high-true) | Yes, to leave commissioning state |
| 5 / 6 / 7 | DI0 / DI1 / DI2 (digital inputs) | Optional |
| 12 / 13 | DO0 (relay) / DO1 (transistor) | Optional, useful for status readback |
| U / V / W | Motor output | Not present on CU alone |
Modbus Parameter Setup Over USB
The CU230P-2 HVAC and CU230P-2 BT expose RS485 Modbus RTU on terminals 29/30. With the drive on the bench, you can fully configure the Modbus map and verify register reads without ever running a motor.
Key parameters:
| Parameter | Description | Typical setting for Modbus testing |
|---|---|---|
| p2020 | Modbus baud rate | 6 = 9600 bps, 7 = 19200 bps, 8 = 38400 bps |
| p2021 | Modbus address | 1...247 (avoid 0 / 248+) |
| p2022 | Modbus parity | 2 = even (default), 0 = none (2 stop), 1 = odd |
| p2023 | Modbus response timeout | 2000 ms (default 0 = no monitoring) |
| p2040 | Process data watchdog time | 1000 ms (set to 0 for bench test) |
| p2051[0] | CW (control word) source connector | 2050[0] for Modbus |
| p2051[1] | SW (status word) source connector | 2050[1] from CU |
| p2080 | BiCo source for status word | r899.0 (drive status bits) |
After writing parameters, perform a Copy RAM to ROM (p0971 = 1) so they survive a power cycle on the customer's cabinet.
STARTER vs. Startdrive vs. TIA Portal
Three commissioning paths exist for the G120 family:
-
STARTER (legacy) – best for older firmware (V4.x), supports offline projects that open in Startdrive. Project files use
.sspextension. - Startdrive in TIA Portal (V15+) – required for firmware V4.7 SP3 and later on the CU230P-2. Adds integrated PLC tag exchange and trace recording. Project files use standard TIA Portal format.
- Web server (SINAMICS G120 Smart Access module) – for the G120C and G120 with Web Server option. Not all CU230P-2 variants support it; check the nameplate for WLAN module ordering data.
If commissioning a brand-new CU230P-2 with firmware V4.7 SP10 or higher, Startdrive in TIA Portal is the only path that includes the latest GSD/GSDML files. Older STARTER projects can be migrated using Project → Migrate to TIA Portal.
Verification and Diagnostics
After driver install and PG/PC binding, run this checklist before declaring success:
- Device Manager check: Ports (COM & LPT) shows Siemens USB-Serial Converter (COMn). HID section still shows SINAMICS G120.
- STARTER online search: Project → Accessible nodes → S7USB returns the CU's IP/USB identifier within 5 seconds.
- Online identification: Click Identify. STARTER should display the CU's article number (e.g., 6SL3246-0AE31-...) and firmware version.
- Parameter upload: Load to PG should succeed without fault F07012 / F08501.
- Trace buffer: Start a 1-second trace on r899 (status word) – the trace graph must update, confirming live data exchange.
Troubleshooting Matrix
| Symptom | Likely Cause | Resolution |
|---|---|---|
| Device Manager shows only SINAMICS G120 under HID, no COM port | Virtual COM driver not installed | Install CP210x or FTDI driver per Step-by-Step above |
| COM port shows, but STARTER cannot find node | PG/PC interface not set to S7USB | Open Set PG/PC Interface, assign S7USB to the COM port |
| Device Manager: Code 52, signature cannot be verified | Unsigned driver, Windows driver signing enforced | Install certificate into Trusted Publishers; reboot |
| CU RDY LED blinks red/yellow at 1 Hz | CU not receiving 24 V, or enable missing | Verify 24 V on terminals 1/2; jumper 31 to 24 V |
| STARTER reports fault F07012 | Parameter upload checksum error | Power-cycle the CU, retry upload, then save to ROM |
| Online search returns drive but Identify fails | Firmware mismatch between STARTER and CU | Update STARTER to V5.4 SP3 or higher, or downgrade CU firmware |
| USB enumerates then disconnects after 5 s | USB suspend on hub; CU losing 24 V | Bypass hub, supply regulated 24 V at 1 A minimum |
| Modbus poll returns exception 04 (slave device failure) | CU not in RUN state; missing enable | Apply 24 V to terminal 31; check p8542 for handshake |
| Modbus poll returns exception 02 (illegal address) | Register not mapped to connector | Wire BiCo from r2050[2] to the desired parameter |
| Driver installs but COM port appears as COM256+ | Windows COM name space exhausted | Reassign to COM1-COM16 via Advanced in Device Manager |
Field Tips and Caveats
- The USB port on CU230P-2 supports hot-plug, but always disconnect STARTER online session before pulling the cable to avoid corrupted parameter blocks.
- When the CU is later installed in the cabinet and powered through the PM, the 24 V external supply must be removed before applying mains to the PM, or ground loops can damage the USB transceiver.
- Never use a USB cable longer than 3 m without an active repeater. The USB-to-serial bridge is sensitive to voltage drop on VBUS.
- If STARTER is installed under a non-default path, search the entire drive for
slabvcp.inforftdibus.infwith PowerShell:Get-ChildItem -Recurse -Filter *.inf -Path C:\ | Select-String -Pattern 'cp210|slabvcp|ftdibus'. - For firmware V4.7 SP10 or later, install the Siemens USB driver package separately from the G120 CU230P-2 operating instructions entry under "Software / Tools"; the modern driver includes both CP210x and FTDI bridges.
FAQ
Where do I download the SINAMICS G120 CU230P-2 USB driver if I do not have the installation DVD?
The driver is bundled with STARTER V4.1.5+ under Driver\USB. If STARTER is already installed, browse to C:\Program Files\Siemens\Automation\STARTER\Driver\USB. Otherwise download the current signed CP210x or FTDI VCP driver from the chipset vendor's website; both work with the CU230P-2 Mini-USB port. See the Siemens Industry Online Support entry for STARTER at entry ID 10804985.
Can I commission a CU230P-2 Control Unit without a Power Module connected?
Yes. Apply a regulated 24 V supply (0.5 A minimum) to terminals 1 (+24 V) and 2 (0 V) on the CU, and jumper terminal 31 (EP enable pulses) to +24 V. The CU will boot, expose the USB interface, and accept parameter changes. Motor terminals U/V/W are absent without the PM, so motor current cannot flow, but all Modbus and fieldbus registers are fully readable and writable.
STARTER shows the SINAMICS G120 HID device but does not list the CU under Accessible nodes. What is wrong?
The virtual COM port driver is missing or the PG/PC interface is not bound. Open Set PG/PC Interface and confirm S7USB is selected and assigned to the COM port shown in Device Manager under Ports (COM & LPT). Restart STARTER after assigning so it rebuilds the accessible-node cache.
Which STARTER version supports firmware V4.7 SP10 on the CU230P-2?
Use STARTER V5.4 SP3 or higher, or Startdrive V16 inside TIA Portal V16. Older STARTER V4.x cannot open projects for V4.7 SPx CUs and will return fault F08501 during online identification. Migrate legacy .ssp projects via Project → Migrate to TIA Portal.
Why does my USB driver install fail with Windows error Code 52 on Windows 10 1607 and later?
Code 52 means the driver is not digitally signed for the running Windows build. Right-click the driver's .inf file, install the embedded certificate into the Trusted Publishers store under the local computer, then retry the driver update. Alternatively, install the latest signed CP210x or FTDI VCP driver directly from the chipset vendor; both ship with current WHQL signatures accepted by Windows 10 and Windows 11.