Resolving SINAMICS S110 CU305 PN Starter 4.5 Connection Loss

David Krause13 min read
SiemensTroubleshootingVFD / Drives
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

Resolving SINAMICS S110 CU305 PN Connection Failure in Starter V4.5.1.5

Starter V4.5.1.5 reports the SINAMICS S110 CU305 PN as a bus node with a question mark when the control unit ships with firmware 04.40.45. The drive was visible to DCP discovery but could not be accepted into the project, and a direct TCP/IP connection could not be opened. This article breaks the failure into its two independent root causes, then walks through the commissioning and recovery path used in the field, including a fallback to TIA Portal / Startdrive when the legacy Starter catalog cannot match the firmware.

Field observation: Help → Installed devices in Starter reports SINAMICS S110 CU305 PN V4.4.3 V04.40.44.00 / SSP SINAMICS V4.4 SP3 V04.40.44.00_11.26.00.00. This is the exact SSP catalog ceiling; FW 04.40.45 is not listed and the device is rendered with a "?" until a newer SSP is installed.

1. Problem Statement

The reported failure is reproducible as follows:

  • PC running Starter V4.5.1.5 with SSP SINAMICS V4.4 SP3 installed.
  • Target hardware: SINAMICS S110 CU305 PN with firmware V4.4.45 (04.40.45), connected to the engineering PC via a direct Ethernet cable on the X150 P1/P2 PROFINET ports.
  • Starter's accessible nodes view shows the S110 with a question mark overlay; the node cannot be accepted into the project tree.
  • Online connection fails; the drive does not respond to standard TCP/IP commissioning attempts.

The "?" is a catalog miss, not a cable fault. Starter cannot match the device's reported firmware identity to any entry in the installed SSP, so it refuses to bind the device to a project slot. A second, independent fault is usually also present: the CU305 PN ships with PROFINET interface 1 set to 0.0.0.0, which prevents a TCP-based commissioning connection from being opened even when the device is identifiable.

2. Affected Hardware, Firmware, and Software

Component Version in the failure case Required / Compatible
Control Unit CU305 PN (6SL3040-1JA01-0AA0) Any CU305 PN hardware
Drive firmware 04.40.45 (V4.4 SP5 branch) Matches SINAMICS V4.4 family
Power Module (example) PM340 (6SL3210-1SE/1SB/1SF series) All PM340 sizes supported by S110
Commissioning tool Starter V4.5.1.5 Starter 4.5.1.x, 4.4.1.x, 4.3.x or TIA Portal with Startdrive
SSP catalog SSP SINAMICS V4.4 SP3 (max FW 04.40.44) SSP V4.4 SP4 / SP5 or Startdrive V14+ device library
Interface in use X150 P1 (PN port 1, LAN) X150 P1/P2 (PROFINET), X126 (service) also valid for point-to-point

3. Root Cause Analysis

The reported fault is the visible symptom of two layered problems. Fix only one and the connection will still fail.

3.1 Default IP on the PROFINET interface

PROFINET interface 1 on a factory-fresh or recently reset CU305 PN has the IP address 0.0.0.0 and DHCP mode active. Starter performs a DCP identify-all broadcast, then opens a TCP connection to the discovered IP. With 0.0.0.0, no TCP socket can be established regardless of how the cable is wired. This is the same behavior the user observed: the node is visible (DCP success) but unreachable (TCP failure). Assigning a valid IP is a strict prerequisite.

3.2 SSP / firmware version mismatch

Starter's project tree is bound to the device catalog that ships inside the installed Support Package. The default SSP for Starter V4.5.1.5 is V4.4 SP3, whose highest supported firmware entry is 04.40.44.00. When Starter polls the drive, the drive announces FW 04.40.45. The catalog lookup returns no match, and Starter renders the device as a generic unknown PROFINET node with a "?". The fix is to either install a newer SSP that recognizes FW 04.40.45, or to switch to a commissioning tool that carries a newer device library (Startdrive).

3.3 Why downgrading is not recommended

Downgrading FW 04.40.45 to 04.40.44 will clear the catalog miss but it is a destructive operation: all saved parameters on the CF card / non-volatile memory are overwritten, motor data may need to be re-commissioned, and any safety-related parameters (e.g., Safety Integrated configurations) must be re-validated. Only fall back to a downgrade when the project is in factory state or all parameter backups are present.

Safety reminder: SINAMICS Safety Integrated configurations (SS1, SS2, SOS, SLS, SDI) must be re-accepted and re-validated by qualified personnel after any firmware change. Treat the following procedure as commissioning-time work, not as a hot fix on a running machine.

4. Prerequisites

  • Siemens engineering PC running Windows 10 / 11 (64-bit) with administrator rights.
  • Starter V4.5.1.5 (or any 4.5.x / 4.4.x variant) installed locally.
  • Siemens PRONETA (free) or SIMATIC Primary Setup Tool (PST) installed for IP assignment.
  • Ethernet cable (Cat 5e or better) terminated to RJ45, with at least one crossover-capable port pair (most modern NICs auto-MDIX; direct cable works).
  • PROFINET device name sticker on the S110, or read access via DCP.
  • Optional: TIA Portal V14 SP1 or newer with the Startdrive option installed for the alternative path.
  • Optional: SD card (1 GB+) with the SINAMICS FW 04.40.45 image if a downgrade is later required.

5. Pre-Connection Network Verification

  1. Connect the engineering PC directly to X150 P1 of the CU305 PN. Disable all other network adapters (Wi-Fi, secondary LAN) to prevent DCP confusion.
  2. Set the PC NIC to a fixed address in a private subnet, for example 192.168.0.10 / 255.255.255.0, with no gateway.
  3. Open a command prompt and verify link: ping 192.168.0.10 -n 1 must return from the local interface. If it fails, replace the cable or the NIC.
  4. Run arp -a to confirm no stale PROFINET entries exist; if the S110 was previously reachable on another IP, flush the ARP cache with netsh interface ip delete arpcache.
  5. Disable Windows firewall temporarily on the private profile, or open UDP/34964 (DCP) and TCP/102 (S7 / SINAMICS RFC 1006) inbound and outbound. These two ports are sufficient for Starter commissioning.

6. Assigning a Valid IP Address to the CU305 PN

Use one of the three methods below. Method A is the fastest when only the S110 is on the bench.

6.1 Method A: PRONETA (recommended)

  1. Launch PRONETA and switch to Network Analysis.
  2. PRONETA lists every PROFINET device reachable via DCP. The S110 will appear as an unidentified node with MAC address, original device name (often blank), and current IP 0.0.0.0.
  3. Right-click the S110 → Assign PROFINET name. Enter a name that matches the IO controller configuration, e.g. s110-cu305.
  4. Right-click the S110 → Set IP address. Enter 192.168.0.20, subnet 255.255.255.0, no gateway.
  5. Click Apply. The S110 reboots the PROFINET stack (about 5–10 s). PRONETA now shows the device as online with the assigned IP.

6.2 Method B: Direct STARTER parameter write (advanced)

If a different tool is already online (e.g., a PLC acting as IO controller), the IP can be assigned by writing to the drive's PN configuration parameters. This is also useful when the new IP must persist across power cycles.

Parameter Meaning Example value
p8920[0] PROFINET Name of Station, interface 1 "s110-cu305"
p8921[0..3] IP address (4 octets), interface 1 192, 168, 0, 20
p8922[0..3] Default gateway, interface 1 0, 0, 0, 0
p8923[0..3] Subnet mask, interface 1 255, 255, 255, 0
p8924 DHCP mode 0 (DHCP off)
p8925[0..1] Interface configuration, subslot 0 / 1 1, 1 (PN interface active)

After writing, activate with p8925 = 2 to commit, then perform a POWER ON of the CU305 PN. On the next boot the IP persists in non-volatile memory.

Direct parameter writes require a working online connection. If the drive is unreachable from the start, use PRONETA first; the parameter write path is for the second-visit scenario.

6.3 Method C: SIMATIC Manager / TIA Topology Editor

When the S110 is already part of a PROFINET IO system, the PLC project owns the name and IP. Open the device properties in HWCN / TIA Portal, navigate to PROFINET interface → Ethernet addresses, and assign both the PROFINET device name and the IP from the controller side. The PLC will push the configuration to the S110 on the next IO start.

7. Installing the Matching SSP for Starter

Starter's device catalog is built from Support Packages. To add FW 04.40.45, install a newer SSP that contains the corresponding SINAMICS V4.4 description file. The current SINAMICS V4.4 support package family is the correct branch for this firmware.

  1. Download the latest SSP SINAMICS V4.4 (SP4 or SP5, depending on what is current) from the Siemens support portal under entry ID 109751275 (SINAMICS Support Packages overview).
  2. Close Starter and the SINAMICS commissioning trace tools.
  3. Run the SSP installer as administrator. The default path is C:\Program Files (x86)\Siemens\Automation\STARTER\SupportPackages.
  4. Restart Starter. Open Help → Installed devices and confirm the entry SINAMICS S110 CU305 PN V4.4.x V04.40.45.00 (or the highest FW supported by the SSP) is listed.
If the highest FW shown is still 04.40.44, the SSP you installed is older than expected. Re-check the build timestamp; an SP3 SSP that is sometimes redistributed is the same one Starter V4.5.1.5 shipped with.

8. Establishing the Starter Online Connection

  1. Open Starter and open or create the project that targets the S110.
  2. Right-click the drive → Target device → Accessible nodes.
  3. Starter performs a DCP scan. The S110 should now appear with a green icon and a recognized catalog entry (no "?").
  4. Highlight the device and click Accept. The S110 is bound to the project slot.
  5. Right-click → Connect to target system. Starter opens the TCP connection to 192.168.0.20 on port 102 (S7 / RFC 1006).
  6. After a successful connection, click Load HW configuration to target device to push the project offline image to the drive, then Load to PG/PC to read back the current parameter set.

9. Alternative Commissioning Path: TIA Portal / Startdrive

If an SSP for FW 04.40.45 is not available, switch to TIA Portal with the Startdrive option. Startdrive carries a continuously updated device library that already supports recent SINAMICS V4.4 firmware. The TIA path is also the strategic replacement for Starter for new projects.

  1. Install TIA Portal V16 (or newer) with the Startdrive option.
  2. Create a new project and add the S110 CU305 PN from the device catalog (search order number 6SL3040-1JA01-0AA0).
  3. Open the device view, navigate to PROFINET interface → Ethernet addresses, and assign the device name s110-cu305 and IP 192.168.0.20.
  4. Right-click the drive → Go online. Startdrive will identify FW 04.40.45 and download the matching device description automatically.
  5. Use the Startdrive commissioning wizard to configure the motor (using the motor code on the rating plate), encoder, setpoint source, and telegram (Standard Telegram 1 for speed control, 2 for speed/torque, 3 for positioning with the FB POS of the technology object).
If TIA Portal reports device description not available, update the HSP (Hardware Support Package) for SINAMICS via TIA Portal's HSP installation tool, accessible from the TIA Administrator.

10. Verification and Online Diagnostics

Once the connection is established, run the following checks to confirm the drive is in a known-good state:

Check Procedure Expected result
Firmware identity Read r0018 (firmware version) Returns 04.40.45.00 (or whatever the CF card contains)
PROFINET link Read r8912[0] (PN link state) and r8913[0] (PN port state) Both report 2 (link up, no errors)
Configured IP Read r8931[0..3] Matches 192.168.0.20
Configured name Read r8930[0] Returns s110-cu305
Drive state Read r0002 Returns 0 (commissioning / not enabled) or drive operating state per application
Alarm buffer Read r0945[0..7] and r0947[0..7] No active alarms; review the buffer for F08501 (PROFINET communication fault) or F08502 (PN name missing) if the IP / name steps were skipped
Control / status words Read r0054 (control word 1) and r0052 (status word 1) Bits toggle as expected when setpoints are applied

10.1 Inline connection state diagram

DCP Identify(broadcast, UDP/34964) IP = 0.0.0.0?assign via PRONETA FW in SSP?install matching SSP TCP/102 OKStarter online visible IP valid FW match if "?": SSP miss if link down: cable

11. Firmware / SSP Compatibility Reference

SINAMICS FW Branch Minimum Starter Minimum SSP Minimum Startdrive
04.30.xx V4.3 4.3 SP3 SSP V4.3 V13 SP1
04.40.30 / 04.40.40 V4.4 SP1 / SP2 4.4.1.x SSP V4.4 SP2 V14 SP1
04.40.44.00 V4.4 SP3 4.5.1.5 SSP V4.4 SP3 (default with Starter 4.5.1.5) V15.1
04.40.45.00 V4.4 SP5 4.5.1.5 with newer SSP, or 4.4.1.x with SSP V4.4 SP5 SSP V4.4 SP5 V16 update 4+
04.50.xx V4.5 4.5.1.5 with SSP V4.5 SSP V4.5 V17
04.60.xx V4.6 Starter 4.6.1.x SSP V4.6 V18
Version numbers above reflect the SINAMICS V4.4 SP branch. Always verify the actual release notes of the SSP you download against the firmware on the drive, since Siemens occasionally renumbers internal build IDs without bumping the public version string.

12. Troubleshooting Matrix

Symptom in Starter Most likely cause Fix
Drive visible with "?" overlay, IP 0.0.0.0 Default IP + SSP miss Assign IP via PRONETA, install newer SSP
Drive visible with "?" overlay, valid IP SSP catalog miss only Install matching SSP, restart Starter
Drive not visible at all, no DCP response Cable, port, or firewall Swap cable, try X150 P2, open UDP/34964, disable firewall
Drive visible, TCP connection refused IP / subnet mismatch Verify PC NIC in same subnet; ping the drive IP
Connection succeeds then drops every 30 s Duplicate IP on network ARP-scan the subnet, change the S110 to a free IP
Alarm F08501 at power-up PROFINET name not assigned Assign PROFINET name to match IO controller project
Alarm F08502 at power-up IP address invalid or 0.0.0.0 Assign IP via PRONETA or write p8921
Drive visible, "?" still present after SSP install Starter not refreshed Close and reopen Starter; verify with Help → Installed devices
Same "?" overlay also on PLC line General PC / DCP issue, not firmware Reinstall Starter, repair TCP/IP stack, recheck firewall

13. Recommended Permanent Fix

  1. Migrate the project to Startdrive in TIA Portal. Startdrive is the long-term commissioning tool and is the only path that follows the SINAMICS device library without manual SSP management.
  2. Persist the IP and PROFINET name on the CU305 PN by writing p8920 / p8921 and committing with p8925 = 2, so the drive boots with a usable address even on a fresh PLC project.
  3. Back up the S110 parameters to a CF card after every successful commissioning: in Starter / Startdrive, Copy RAM to ROM, then save the project to the card. This avoids the recurring catalog-miss problem when a support engineer reopens the drive months later with an older tool.

FAQ

Why does Starter show a question mark on the S110 CU305 PN?

Starter renders a "?" when the drive's reported firmware (04.40.45) is not in the device catalog of the installed SSP. The default SSP for Starter V4.5.1.5 caps at 04.40.44, so 04.40.45 is unrecognized until a newer SSP (V4.4 SP5 or higher) is installed.

Does the S110 CU305 PN ship with a default IP address?

Yes. PROFINET interface 1 on a factory-fresh CU305 PN has IP 0.0.0.0 with DHCP mode active. DCP discovery still finds the device, but TCP-based commissioning fails until you assign a valid IP via PRONETA, the Primary Setup Tool, or the controller project.

Is downgrading the S110 firmware the only way to connect?

No. Downgrading to 04.40.44 is one of three options; the other two are installing a newer SSP that includes 04.40.45 support, or switching to TIA Portal with Startdrive. Startdrive is the preferred long-term path because it tracks firmware releases without manual SSP downloads.

Which port on the CU305 PN should I connect to for commissioning?

Use X150 P1 (or X150 P2) on the CU305 PN. These are the PROFINET ports. X126 is a service port with limited commissioning support and should not be used as the primary connection for Starter or Startdrive.

Which TCP and UDP ports does Starter need open?

Open UDP/34964 for DCP discovery and TCP/102 for the S7 / RFC 1006 commissioning channel. On Windows, allow both inbound and outbound on the active profile. Disabling the firewall on the private profile is acceptable for a temporarily connected engineering PC but should be re-enabled once commissioning is complete.

Back to blog