Configuring SINAMICS S120 CU320-2 Web Server in STARTER V4.6

David Krause14 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

Configuring the SINAMICS S120 CU320-2 Web Server in STARTER V4.6

1. Problem Description

After upgrading a SINAMICS S120 CU320-2 control unit (both DP and PN variants are affected) from firmware 4.5 to firmware 4.6 HF3, the Web server entry disappears from the right-click context menu of the drive object inside the commissioning tool. The drive object is online, the topology loads without errors, expert parameters are visible, and parameter p8987[0] shows the expected default port value of 80. The commissioning tool is SIMOTION Scout V4.4, used here for a SINAMICS-only project. A separate D435-2 DP/PN motion controller in the same subnet exposes its web server without issue, which confirms that the network, the engineering PC, and the browser are healthy.

Two distinct conditions produce this symptom, and both must be ruled out before commissioning the demo:

  • The commissioning tool is SIMOTION Scout rather than STARTER. Scout does not expose the SINAMICS web server configuration dialogs even when the project contains only a CU320-2.
  • The STARTER version installed is older than V4.3.2 SP1, or STARTER and Scout are both installed on the same machine, which is unsupported.
STARTER and SIMOTION Scout cannot coexist on the same Windows installation. A clean STARTER V4.3.2 SP1 (or later) environment is mandatory before the web server context menu will reappear.

2. Root Cause Analysis

The SINAMICS web server is a control-unit-resident HTTP/HTTPS service implemented from firmware 4.5 onward on the CU320-2 DP and CU320-2 PN. Its configuration tree is added by the SINAMICS S120 Web Server option in the STARTER drive object tree. The dialog, including the right-click Web server > Activate/Deactivate commands, is implemented by the STARTER add-in SinStartAddIn.dll registered at install time. SIMOTION Scout ships a different add-in stack (SimotionScoutAddIn) that does not register the SINAMICS web server node. The result is a project that opens, online-commissions, parameterizes, and traces correctly but never reveals the web server configuration context.

Three downstream facts further constrain the fix:

  1. STARTER V4.3.2 SP1 (released for firmware 4.5) is the minimum version that exposes the web server dialog. STARTER V4.4 matches firmware 4.6 and is the version Siemens recommends with 4.6 HF3.
  2. The CU320-2 must contain the firmware extension package that delivers the web server files to /OEM/SINAMICS/HMI/ on the CompactFlash (CF) card. Without these files the parameter p8985[0] can be set to enable the server, but the HTTP listener returns 404 because no AWP (Automation Web Pages) are served.
  3. Both LAN ports on the CU320-2, X127 (Service) and X150 (PROFINET, PN variant only), are candidates for the web server. The interface is selected with parameter p8986. Misalignment between p8986 and the IP address the browser targets is the single most common reason the user can ping the drive but receives "Server Not Found" or "Connection refused" in the browser.

3. STARTER Versus SIMOTION Scout

Both tools share a common code base rooted in the SIMOTION/SINAMICS automation framework, but they are licensed and installed as separate products. Scout is licensed for SIMOTION motion control projects; STARTER is licensed for SINAMICS drive commissioning. The web server user interface for the CU320-2 lives in the STARTER add-in layer.

Feature STARTER V4.4 SIMOTION Scout V4.4
CU320-2 online commissioning Yes Yes (read-only on SINAMICS objects in mixed projects)
Web server right-click menu Yes (from V4.3.2 SP1) No
AWP (web page) upload to CF card Yes No
Topology and drive parameterization Yes Limited
Side-by-side install with the other tool No No
If a mixed SIMOTION + SINAMICS project is required, install STARTER and Scout on two separate physical or virtual machines. Running both inside the same Windows guest or partition is not supported and produces orphaned registry keys that break the web server add-in.

4. Firmware and Tool Compatibility Matrix

CU320-2 Firmware Minimum STARTER Web Server Available Notes
4.4 SP3 STARTER V4.2 No Use SINAMICS Startdrive or external HTTP client
4.5 STARTER V4.3.2 SP1 Yes (basic AWP) First release to ship web server add-in
4.5 SP1 STARTER V4.3.3 Yes Adds HTTPS support
4.6 STARTER V4.4 Yes Improved diagnostic pages, IPv6 on X150
4.6 HF3 STARTER V4.4 (same) Yes Bug fix release; same web server feature set as 4.6
4.7 STARTER V4.5 / Startdrive V15 Yes Adds user-defined AWP variables and OPC UA bridge

Verify the installed firmware from the expert list of the CU320-2 (online) at parameter r0018 (Control Unit firmware version) and r0019 (drive object firmware). The web server is part of the Control Unit firmware, so the relevant value is r0018. If the value is below 4.5, the web server is not present regardless of tool version.

5. Web Server Parameter Set

The SINAMICS web server is entirely parameter-driven. There is no script or FB to import. The four key parameters are summarized below; the full description is in the SINAMICS S120/S150 List Manual.

Parameter Name Default Range / Values Description
p8985[0] Web server enable 0 0 = off, 1 = on Master switch for the HTTP listener on the Control Unit.
p8986 Web server interface 0 0 = X127, 1 = X150 (PN only) Selects the Ethernet port that accepts HTTP/HTTPS connections.
p8987[0] TCP port 80 1 - 65534 HTTP listener port. 80 is the standard; 443 is the typical HTTPS port.
p8987[1] HTTPS enable 0 0 = off, 1 = on When set, the port in p8987[0] serves HTTPS and a self-signed certificate is generated at startup.
p8988 Web server user authentication 1 0 = none, 1 = standard When set to 1 the user is prompted for CU320-2 access level credentials.

Reading the user-supplied value, p8987[0] = 80 is correct, and on a default CU320-2 the menu should be available provided STARTER is installed. The default p8985[0] = 0 means the server is initially disabled; STARTER's right-click command toggles it to 1 and copies RAM to ROM.

5.1 Expert List Quick Filter

Inside STARTER, open Drive > Commissioning > Expert list and enter the filter p8985 to bring all web server parameters to the top. From firmware 4.5 onward, the parameters are writeable in both the online and offline expert lists. After every change perform RAM to ROM and a power cycle of the Control Unit so the listener binds on the new interface and port.

6. Interface and IP Address Configuration

The CU320-2 PN exposes two LAN ports and the CU320-2 DP exposes one:

Port Available On Default Address Default Subnet Role
X127 CU320-2 DP and PN 169.254.11.22 255.255.0.0 Service / commissioning (link-local)
X150 CU320-2 PN only 0.0.0.0 (DHCP/PN) Configured in HW Config PROFINET field network
X126 CU320-2 DP only n/a n/a PROFIBUS

The user's reported addresses are 169.254.11.23 on X127 and 192.168.1.13 on X150. The X127 address is one off the default (the default is .22, the user changed to .23), which is normal when a default gateway is on .22. The X150 address is in a different subnet from the D435-2 (which is on 192.168.1.12) but reachable from the engineering PC. If the web server is bound to X127 by p8986 = 0 but the browser targets 192.168.1.13, the listener simply does not answer.

6.1 Binding the Web Server to the Correct Port

  1. Decide which port the browser will target. For a service laptop, X127 with its default link-local address is the simplest.
  2. Set p8986 = 0 for X127 or p8986 = 1 for X150 (PN only).
  3. Configure the IP address of the selected port to match what the browser will type. The X127 address is set with p8901 / p8903; the X150 PN address is set with the PROFINET device name and IP from the PLC project or from p8920 - p8924.
  4. Copy RAM to ROM and power-cycle.
The web server is a single-listener service. It cannot be active on both X127 and X150 simultaneously. Confirm the drive's r8985 reports Web server active after the power cycle before opening a browser.

7. CompactFlash Card Web Server Files

The CU320-2 boots its web server from AWP files placed on the CF card by STARTER. The path layout is fixed:

/
|-- SIEMENS/
|   `-- SINAMICS/
|       `-- HMI/
|           |-- index.htm
|           |-- menu.htm
|           |-- start.htm
|           |-- ... (static AWP)
|-- USER/
|   `-- SINAMICS/
|       `-- HMI/
|           |-- user_define.htm
|           |-- ... (custom AWP)
`-- OEM/
    `-- SINAMICS/
        `-- HMI/
            |-- oem_define.htm
            |-- ... (OEM AWP)

When STARTER uploads the web server from the Web server > Upload pages command, it copies the Siemens-supplied baseline AWP set into /SIEMENS/SINAMICS/HMI/ on the CF card. User-defined pages go into /USER/SINAMICS/HMI/. A missing /SIEMENS/SINAMICS/HMI/index.htm is the most common reason the browser returns a 404 even though r8985 indicates the server is running.

To inspect the CF card, insert it into a Windows reader while the Control Unit is off; the card mounts as a removable drive. Never edit the Siemens baseline files directly - copy them to the USER tree and modify there.

8. Step-by-Step Configuration Procedure

8.1 Prerequisites

  • Windows 10 (64-bit) or Windows Server 2016/2019 engineering PC.
  • STARTER V4.4 (or V4.4 SP1) installed cleanly. No SIMOTION Scout on the same machine.
  • CU320-2 DP or CU320-2 PN with firmware 4.6 (or 4.6 HF3) loaded.
  • CF card with at least 512 MB free.
  • Ethernet cable between engineering PC and X127 (or X150 for PN).
  • Engineering PC IP address in the same subnet as the chosen CU320-2 port. For X127 default: 169.254.11.21 / 255.255.0.0.

8.2 Configuration Steps

  1. Open STARTER V4.4 and open the CU320-2 project offline.
  2. Right-click the CU320-2 drive object. Confirm the entry Web server > Activate is present. If absent, STARTER V4.3.2 SP1 has not been installed; reinstall STARTER.
  3. Select Web server > Activate. The tool writes p8985[0] = 1 online and prompts for RAM to ROM.
  4. Open the expert list and verify the parameter set:
    p8985[0] = 1   (web server enable)
    p8986    = 0   (X127) or 1 (X150)
    p8987[0] = 80  (HTTP port)
    p8987[1] = 0   (HTTPS off, recommended for first test)
    p8988    = 1   (standard authentication)
  5. Set the interface IP address:
    • X127: p8901 = 169.254.11.23, p8903 = 255.255.0.0, p8904 = 0 (no router).
    • X150: p8920 = 192.168.1.13, p8922 = 255.255.255.0, p8923 = 192.168.1.1, p8924 = 1 (settings active).
  6. Right-click the drive object and select Web server > Copy RAM to ROM.
  7. Right-click and select Web server > Upload pages to push the Siemens baseline AWP set to the CF card.
  8. Right-click and select Target system > Power cycle. Wait for the CU320-2 to complete its startup sequence (about 30-40 seconds). The READY LED turns green; the SF LED must be off.
  9. Open a browser on the engineering PC and navigate to http://169.254.11.23/ (X127) or http://192.168.1.13/ (X150).

9. Verification

After the power cycle, confirm the listener is bound:

  1. From the engineering PC, run ping 169.254.11.23 -n 4. The response must show <1 ms with no loss on the link-local subnet.
  2. Open a command prompt and run curl -v http://169.254.11.23/. The HTTP response must be 200 OK and the body must contain the Siemens HMI banner. A 404 indicates the AWP files were not uploaded to the CF card.
  3. In the STARTER expert list, read r8985. The value 1: web server active confirms the listener is up.
  4. Open a browser, accept the standard authentication prompt, and verify the SINAMICS overview page loads. Test at least one drive object drill-down.
If the browser displays "Server Not Found" or "This site can't be reached" but ping succeeds, the listener is on the wrong interface. Re-check p8986 against the IP address used in the URL.

10. Troubleshooting Matrix

Symptom Likely Cause Action
Right-click menu has no Web server entry SIMOTION Scout used or STARTER < V4.3.2 SP1 Install clean STARTER V4.4 on a separate Windows host
r8985 reports server active but browser 404s AWP files missing from CF card Use Web server > Upload pages in STARTER
Browser "connection refused" on port 80 p8986 binds to the other LAN port Set p8986 to the port matched by the URL IP
Browser "Server Not Found" but ping works Wrong interface or wrong subnet Confirm browser URL IP matches p8986 port IP and subnet
HTTPS fails, HTTP works Self-signed cert blocked by browser policy Add security exception or use a CA-signed cert loaded via p8987[1]
Web server active until next power cycle then off RAM only write, no ROM copy Issue Copy RAM to ROM from the Web server menu
Authentication prompt loops Wrong access level password or p8988 set to 0 with security enabled Reset CU320-2 to factory defaults and re-enter the password
Browser hangs for 60 s then timeout Engineering PC has two NICs and wrong one is routed Disable the second NIC or add a static route for the link-local subnet
D435-2 works, CU320-2 does not Tool was Scout for the D435-2 (a SIMOTION controller) and STARTER for CU320-2 projects, but used cross-licensed Verify Scout is not being used to edit the CU320-2; create a fresh STARTER project
Web server active only on X127 even after p8986=1 PN variant required a PROFINET device name to take the X150 address Assign a PROFINET name from TIA Portal or PLC project, then power cycle

11. Migrating From Firmware 4.5 to 4.6 HF3

The 4.5 to 4.6 jump is technically a minor release for the web server. The same parameter set applies. The two operational changes that affect this scenario are:

  1. STARTER V4.3.x is no longer supported for online commissioning on 4.6 firmware. Upgrade STARTER to V4.4 (V4.4 SP1 recommended with HF3 hotfixes).
  2. The web server add-in now requires the .NET Framework 4.7.2 runtime, which STARTER V4.4 installs as a prerequisite. If the install logs show a failure of the add-in, install .NET 4.7.2 manually before launching STARTER.

The 4.6 to 4.7 path is optional. 4.7 adds user-defined AWP variables and an OPC UA bridge for the web server, which is useful for an OEM demo but not required to expose the basic SINAMICS pages. STARTER V4.5 (or Startdrive V15) is the matching tool. The CF card web server files are compatible forward and back to 4.5; no re-upload is required for a downgrade.

12. Security and Network Hardening

The web server is unencrypted by default. Apply the following minimum hardening before exposing it beyond the service laptop:

  • Set p8987[1] = 1 to enable HTTPS on port 443 and add a CA-signed certificate. Self-signed certificates are functional but generate browser warnings that fail automated tests.
  • Set p8988 = 1 to require the SINAMICS access level password. The default user is Anonymous and the default password is empty if the access level is reset.
  • Bind the web server to X127 only when possible. The link-local 169.254.0.0/16 range is not routed, so X127 is not reachable from a corporate network.
  • If X150 is required, place the drive behind a managed switch port that limits inbound TCP to ports 80/443 and the PROFINET RT frames.
  • Disable unused protocols on the same interface. PROFINET DCP, LLDP, and SNMP remain active on X150 even with the web server on; consult the SINAMICS S120 Communications Function Manual for parameter p8905 to mask services not in use.

13. References to Official Documentation

The full parameter description, AWP scripting reference, and CF card layout for the SINAMICS S120 web server are in the SINAMICS S120/S150 List Manual, function block chapter for the Control Unit. The SINAMICS S120 Function Manual contains the drive-side commissioning procedure. Both manuals are available on the Siemens Industry Online Support portal:

14. FAQ

Why does the Web server entry disappear from the right-click menu in STARTER?

The web server dialog is added by the STARTER add-in shipped with V4.3.2 SP1 or later. SIMOTION Scout does not register the SINAMICS web server add-in, even when the project contains only a CU320-2. Install a clean STARTER V4.4 on a machine without Scout to restore the menu.

Which firmware is required for the SINAMICS S120 CU320-2 web server?

Firmware 4.5 or later on the Control Unit (verified by reading r0018). Firmware 4.6 HF3 with STARTER V4.4 is a fully supported combination. Earlier firmware versions (4.4 and below) do not include the web server function block.

What is the default web server port and how is it changed?

The default TCP port is 80 and is stored in p8987[0]. The range is 1 to 65534, but 80 (HTTP) and 443 (HTTPS) are the only ports worth using in a browser. After any change to p8987[0] or to p8986, perform a copy RAM to ROM and a power cycle.

Can the web server be active on X127 and X150 at the same time?

No. Parameter p8986 selects a single interface; the listener binds to that interface only. Choose X127 for service access and X150 only when the PROFINET network must reach the web server.

The web server is enabled (r8985 = 1) but the browser returns 404. What is wrong?

The CU320-2 starts a 404 listener when the AWP file set is missing from the CompactFlash card. Use Web server > Upload pages in STARTER to push the Siemens baseline pages into /SIEMENS/SINAMICS/HMI/ on the CF card, then power cycle.

Back to blog