Enabling SIMOTION D4x5-2 Web Server via SCOUT HW Config

Problem Overview: SIMOTION D4x5-2 Web Server Appears Disabled

The SIMOTION D4x5-2 motion controller family integrates an HTML-based web server intended to surface diagnostics, status, axis data, and trace information in any standard browser. On delivered hardware, particularly after a device replacement or when a project is reloaded from an archive, the web server may be inactive even though the controller is otherwise fully operational. Operators attempting to reach the standard URL http://<IP-address>/ receive a connection refusal, a timeout, or a browser error page that masks whether the issue is network routing, firmware state, or the activation flag itself.

A common field misconception is that because SIMOTION stores its configuration on a CompactFlash card, the activation flag could be flipped by editing an XML or INI file on the card from a card reader. This approach does not work. The web server activation is bound to the project configuration (the SIMOTION device archive generated by SCOUT) and is enforced at project-download time. There is no manual toggle on the CF card that a user can write to enable or disable the web server.

Affected Controllers and Firmware Behavior

The D4x5-2 platform spans four performance classes:

All four variants share the same web server architecture and the same activation mechanism. The change in default behavior that introduced the field issue occurred at the following transition:

The default was changed in response to security hardening requirements. From V5.5 forward, every newly created SIMOTION device must have the web server checkbox manually set inside HW Config or SCOUT, otherwise the service remains dormant regardless of project download, firmware version, or card presence.

Root Cause: Why the CF Card Tweak Does Not Work

The SIMOTION runtime stores a binary project image plus a configuration tree on the CF card. The relevant flag for the web server lives inside the SCOUT-generated project that is compiled to *.sim project archives and then converted to the loadable image written to the card. The activation bit is part of the device object model and is consumed by the runtime during boot.

Mounting the CF card in a card reader exposes a FAT file system containing log files, trace buffers, and some XML service files. None of these are the project's HW Config representation. The bit that enables the web server is held in the encrypted/compiled project image, not in a user-editable text file. Even if a binary search found what looked like the activation flag, modifying it without re-signing the project would lead to:

1. Project integrity check failure at boot
2. Refusal to enter RUN operating state
3. Stop state with diagnostic entries indicating project corruption

Prerequisites for Re-activation

Before the web server can be re-enabled, confirm the following prerequisites are in place. Missing any one of them will block the procedure.

• SCOUT installed: SCOUT V5.4 or newer is recommended for FW 5.x devices; SCOUT V5.5 SP1 or later matches the V5.5+ defaults. The exact SCOUT build must support the firmware version of the target controller.
• Project archive present: The original *.zip or *.sim SIMOTION project archive from which the controller was originally commissioned. Without the source project, a new project matching the configured I/O must be built from scratch.
• Communications path to the controller: Either Ethernet (PROFINET / Industrial Ethernet) or PROFIBUS accessible from the engineering station. The IP address of the SIMOTION CPU must be reachable on TCP/IP.
• SCOUT-DB license if required: SCOUT Standard or SCOUT Professional depending on the diagnostic pages you intend to surface.
• Operator rights on the engineering PC: Project modification rights; the same Windows account that originally downloaded the project is generally required.
• Online connection: A tested Accessible Nodes or Set PG/PC Interface path to the device. Reset any firewalls or VPN tunnels blocking TCP ports 102, 5001, or SCOUT-specific service ports.

Step-by-Step Procedure: Enabling the Web Server in SCOUT

The procedure below covers the standard SCOUT TIA workflow. For the legacy SIMOTION SCOUT (pre-TIA), the dialogs are nearly identical but appear under HW Config inside the standalone SCOUT shell.

Step 1: Open the Project in SCOUT

1. Launch SCOUT from the Windows Start menu or the TIA Portal entry point.
2. Use Project > Open and navigate to the SIMOTION device archive.
3. Confirm the project compiles cleanly. If SCOUT reports a dependency error, resolve it before attempting to change the web server flag.

Step 2: Enter HW Config

1. In the project tree, expand the SIMOTION device node.
2. Double-click the SIMOTION D4x5-2 device icon to open the hardware configuration editor.
3. The catalog on the right pane lists slots and module parameters. The web server flag is a CPU-level property, not a slot-level property.

Step 3: Locate the Web Server Checkbox

1. Right-click the CPU module (the D425-2 / D435-2 / D445-2 / D455-2 entry in slot 1 of the device).
2. Choose Properties from the context menu.
3. In the Properties dialog, navigate to the Web Server tab (sometimes labelled Web or Services depending on SCOUT version).
4. Select the Activate web server on this module checkbox.

Step 4: Optional Security Configuration

1. If the SCOUT version provides access control options, set the Users with access list to the engineer or maintenance accounts that should view diagnostics.
2. Configure password protection per user if your site policy mandates it. Read-only access is sufficient for typical diagnostic use.

Step 5: Save, Compile, and Download

1. Click OK to close the Properties dialog.
2. Save the project (Ctrl+S).
3. Recompile the project (Project > Compile and check object consistency).
4. Connect to the target online (Project > Connect to target system).
5. Download the modified project (Target system > Download > Project to target).
6. When prompted about stop / restart, accept the restart. The controller will briefly leave RUN to apply the new configuration.

Step 6: Restart Confirmation

1. Wait for the controller to return to RUN. The online view of SCOUT should show operating state = RUN.
2. The web server daemon starts as part of the runtime initialization. No further user action is required.

Verification: Confirming the Web Server Is Live

After the download and restart, perform the following verifications to confirm the activation succeeded:

1. HTTP GET test: From a browser on the same subnet, navigate to http://<SIMOTION-IP>/. The home page should render with status indicators.
2. Specific diagnostic pages: Access /diag.htm, /cpu.htm, and /axis.htm (paths vary by firmware). Each should return content, not HTTP 404.
3. SCOUT online diagnostic view: In SCOUT, right-click the device and choose Web browser > Open in web browser. SCOUT will launch the default browser pointed at the device.
4. Logbook review: Open the controller's diagnostic logbook in SCOUT. No Web server warning entries should be present.
5. Telnet probe (advanced): From a Windows or Linux shell, run telnet <SIMOTION-IP> 80 and observe the TCP banner. A successful TCP handshake followed by an HTTP response confirms the port is open.

Available Web Server Pages and Their Use

Once enabled, the SIMOTION D4x5-2 web server exposes structured diagnostic pages. The exact page set depends on firmware version but typically includes:

Security Considerations After Re-activation

The V5.5 firmware default change was driven by security exposure risk. The web server is unauthenticated by default in older firmware. Operators re-enabling the service in a post-V5.5 environment should observe the following practices:

• Place the SIMOTION CPU on a dedicated engineering VLAN or automation cell network.
• Disable web server forwarding at the IT/OT firewall boundary.
• If the SCOUT version supports it, enable user-level access control and assign strong passwords.
• Disable the web server after commissioning or maintenance windows if not needed in production.
• Review Siemens security advisories for the firmware release in use; security patches are issued as firmware updates and may require a new web server toggle.

Alternative Diagnostic Methods When the Web Server Cannot Be Enabled

When SCOUT access is unavailable, or the web server cannot be toggled (for example, on a system that has been locked down by corporate IT policy), the following alternatives offer comparable diagnostic visibility:

• SCOUT online diagnostics: Connect via PROFIBUS or PROFINET to access the diagnostic buffer, logbook, and axis state without the web server.
• SIMATIC Automation Tool: Allows batch operations and firmware / project status queries without a full SCOUT installation.
• PRONETA: Siemens network diagnostic tool that scans PROFINET networks and identifies SIMOTION nodes with their firmware, IP, and operating state.
• SIMOTION IT DIAG: OPC XML-DA server built into the controller; provides structured tag access for higher-level HMIs or SCADA packages.
• Integrated trace: SIMOTION trace buffers can be recorded online via SCOUT and exported for offline analysis.

Troubleshooting Matrix

Firmware and SCOUT Compatibility Reference

Web server activation depends on a consistent pairing between SCOUT, the project archive version, and the firmware installed on the controller. The following rules apply:

Mixing an older SCOUT with newer firmware may not expose the web server tab at all. The SIMOTION D4x5-2 Commissioning Manual documents the supported combinations and any required hotfix levels.

Reference Documentation

• SIMOTION D4x5-2 Commissioning Manual
• SIMATIC S7-1500 Web Server Documentation (TIA Portal)

FAQ