Siemens STARTER Download: SINAMICS Commissioning Software Installation Guide

STARTER (SIMOTION/SINAMICS Commissioning Tool) is Siemens' standalone Windows application for parameterizing, commissioning, and diagnosing SINAMICS low-voltage and medium-voltage drives plus SIMOTION motion controllers. For over fifteen years, STARTER has been the de facto commissioning environment for SINAMICS S120 chassis units, S150 active front-ends, G120/G130/G150 builds, S110, S120 Combi, and SIMOTION P/D controllers. Although Siemens has progressively migrated commissioning workflows to Startdrive in the TIA Portal for newer drive platforms (S210, S200, G220, V90 PN, ET200 motor starters), STARTER remains the only fully-supported commissioning tool for thousands of installed bases running SINAMICS firmware V2.x, V4.x, and V5.0.

This guide consolidates the current methods for obtaining a legitimate, malware-free copy of STARTER, the prerequisites for installation on modern Windows hosts, the Automation License Manager workflow, the typical commissioning sequence, and a migration path for engineers moving projects to Startdrive.

1. STARTER vs Startdrive: Tool Selection Matrix

Before downloading, confirm which tool fits your drive firmware. Mixing tools with unsupported firmware causes parameter set corruption, invisible parameter filters, and F0135 (DRIVE-CLiQ topology error) faults at first download. The selection depends on drive family, firmware version, and project context (legacy service vs new TIA Portal project).

If your drive is in the "STARTER V5.3+ or Startdrive V16+" row, both tools will work today, but Startdrive is the strategic platform. New installations in 2024 and beyond should be planned with Startdrive in TIA Portal, with STARTER retained only for service, archive restoration, and migration of existing projects.

2. System Prerequisites

2.1 Operating System Compatibility

STARTER has well-documented Windows compatibility that has expanded over time. The current release (V5.5) supports the following configurations:

2.2 Required Runtimes

STARTER is built on .NET Framework and requires the following runtimes:

• .NET Framework 4.7.2 minimum (V4.4–V4.5)
• .NET Framework 4.8 (V5.1+)
• Visual C++ 2015–2022 Redistributable (x64)
• Microsoft Windows Installer 4.5+
• SQL Server Compact 3.5 SP2 (V4.x) or 4.0 (V5.x) for project database

2.3 Hardware Requirements

• CPU: Intel Core i3 / i5 2 GHz or equivalent AMD; multi-core recommended for large projects
• RAM: 4 GB minimum, 8 GB recommended for projects with more than 10 drive objects
• Disk: 5 GB free (STARTER base is ~2 GB; support packages add 1–2 GB each)
• Display: 1920×1080 recommended; minimum 1024×768
• Interface: One or more of: PROFINET/PROFIBUS Ethernet port, RS232 (legacy S120), USB (for CU305 or MMC reader)

2.4 Pre-Installation Tasks

1. Disable or whitelist STARTER setup in endpoint protection software (Trend Micro, Symantec, McAfee, and CrowdStrike often quarantine the Siemens DLLs and block the installer mid-flight)
2. Ensure local administrator rights on the engineering station
3. Verify 5 GB+ free disk space on the system drive (C:\)
4. Close all Siemens software (TIA Portal, SCOUT, ALM) before starting the installer
5. Remove older STARTER versions if upgrading from V4.x to V5.x (clean install is recommended to avoid COM registration conflicts)
6. Configure the PG/PC interface in Windows Control Panel for the connected fieldbus (PROFINET, PROFIBUS, or Ethernet/IP)
7. Verify that no SIMATIC HMI or TIA Portal components are using port 4410 (ALM default) or 5001 (STARTER web server preview)

3. Where to Download STARTER: Four Official Channels

3.1 Siemens Industry Online Support (SIOS) — Primary Channel

The official public source is the Siemens Industry Online Support portal. Navigate to the "Software & Firmware" filter and search for "STARTER commissioning tool" or the related article number for your drive family. The latest version of STARTER is bundled under the SINAMICS product family, with separate downloads for:

• STARTER base installer (~900 MB compressed, ~2.2 GB extracted)
• SINAMICS support packages (one per firmware version: e.g. "SINAMICS S120 V5.5 support package", ~500 MB each)
• SCOUT bundle (for SIMOTION commissioning, includes STARTER plus motion control extension)
• DCC (Drive Control Chart) editor add-on (optional, ~300 MB)

The advantage of SIOS is automatic version cross-referencing: when you select a specific SINAMICS drive, the portal lists the matching STARTER version in the "Companion Software" or "Service & Support" section, eliminating the trial-and-error of mismatched tool/firmware pairings. Each download entry includes a release date, MD5/SHA-256 checksum, and known-issue list.

3.2 Drive-Specific Product Pages

Each SINAMICS drive product page on SIOS lists related tools at the bottom of the page. Drilling into the specific drive → "Downloads" → "Software" reveals the supported STARTER versions and the matching support package. This is the most reliable method for engineers working with one drive family because the portal filters out unsupported tool/firmware combinations. The product page also lists predecessor tools (DriveMonitor, SimoComU) for legacy installations where a STARTER version is not available.

3.3 Siemens Sales / Local Representative

If SIOS access is restricted by company firewall or proxy, contacting a local Siemens sales representative or authorized distributor provides access to the latest version through Siemens FileExchange. FileExchange is a controlled file-sharing service that issues time-limited HTTPS links (typically 14 days, single download with optional password). For multi-site deployments with strict change control, this method also provides a SHA-256 checksum on the download page for integrity verification, and the representative can include a printed readme with the new features list.

3.4 Physical DVD / Engineering Bundle

Legacy engineering bundles (sold 2005–2015) included a STARTER DVD plus a USB hardware license dongle (parallel port or USB). Spare DVDs can still be ordered from Siemens spare parts under various MLFBs (e.g. 6SL3072-0AA00-0AG0 historically referenced the STARTER V4.5 DVD). New orders should request the current SIOS download link rather than physical media, as DVDs typically contain outdated STARTER versions and may require a separate support package download to match current SINAMICS firmware.

4. STARTER Version History and Firmware Compatibility

The V4.x to V5.x jump was largely cosmetic: project files (.sdf) are forward-compatible from V4.4+ to V5.5. Older projects (V4.1–V4.3) require an intermediate save in V4.4 or V4.5 before opening in V5.x. A Save As in V4.4 normalizes the database schema, which V5.x can then read directly.

5. Installation Procedure

The standard installation follows these steps. Expect 15–25 minutes on a typical engineering workstation, longer on older PCs with slow disk I/O.

1. Extract the STARTER ZIP archive to a folder with full NTFS permissions (e.g. C:\Temp\STARTER_V55). Avoid paths with spaces or non-ASCII characters.
2. Right-click setup.exe → "Run as administrator".
3. Select the installation language (English, German, French, Italian, Spanish, Chinese Simplified, Chinese Traditional, Japanese, Korean, Russian).
4. Accept the license agreement (EULA covers both STARTER base and SINAMICS support packages).
5. Select Typical install for most users. Custom allows excluding specific support packages (e.g. for SIMOTION if you only commission SINAMICS drives).
6. Confirm the install path. Default is C:\Program Files (x86)\Siemens\Automation\STARTER for V4.x or C:\Program Files\Siemens\Automation\STARTER V5.5 for V5.x.
7. If Automation License Manager is not installed, the installer prompts to add it. Always accept; STARTER requires ALM even for unlicensed use.
8. Select the desired SINAMICS support packages. You can install multiple, but only the matching version is loaded for a given project.
9. Click "Install" and wait for the file copy and COM registration phase (~10 minutes on SSD).
10. Reboot the workstation to complete USB driver and ALM service registration.
11. Launch STARTER from the Start menu: "Siemens Automation" → "STARTER V5.5" → "STARTER".

5.1 Silent / Unattended Installation

For multi-site rollouts, STARTER supports a silent install using the -s switch:

setup.exe -s -SMS -INSTALLDIR="C:\Program Files\Siemens\Automation\STARTER V5.5" -LANG=en

For SCCM, PDQ Deploy, or Intune deployments, the recommended command line is:

setup.exe -s -SMS /v"/qn REBOOT=ReallySuppress INSTALLDIR=\"C:\Program Files\Siemens\Automation\STARTER V5.5\" ADDLOCAL=ALL"

The /v switch passes MSI parameters to the embedded MSI driver. Always include REBOOT=ReallySuppress to prevent surprise reboots on locked-down engineering PCs. The MSI log is written to %TEMP%\SiemensInstall.log for troubleshooting.

5.2 Post-Install Configuration

1. Set the PG/PC interface: Control Panel → "Set PG/PC Interface" → select the network adapter bound to PROFINET (e.g. Intel I219-V with TCP/IP auto).
2. Configure ALM: Start → "Siemens Automation" → "Automation License Manager" → verify the local license storage path is C:\ProgramData\Siemens\Automation\License\.
3. Set the project backup path: STARTER → Tools → "Settings" → "Workbench" → "Save interval" (default 10 min — increase to 2 min for risk-averse engineering).
4. Enable automatic firmware download prompt: Tools → "Settings" → "Online" → "Confirm firmware update" (uncheck for batch production deployment).
5. Configure the project storage default path: Tools → "Settings" → "Project storage" → point to a corporate file share (e.g. \\engineering\STARTER_Projects) for team collaboration.

6. Automation License Manager (ALM) Setup

STARTER uses Siemens' Automation License Manager for license handling. Three modes are available, each suited to different deployment scenarios:

6.1 Trial License (14 days)

When STARTER launches without a license, it offers a trial activation. The trial unlocks all premium features (DCC, unlimited trace, Safety acceptance test) for 14 days. After expiry, STARTER reverts to base functionality. The trial can be reset only by reinstalling the OS, changing the host ID (e.g. swapping the network adapter MAC), or by contacting Siemens support for a one-time extension. Trial licenses are bound to the engineering PC's host ID and will not transfer.

6.2 Network License Server Setup

1. Install ALM Server on a Windows Server (any 2016/2019/2022 edition). The ALM Server component is included with every STARTER install (select "Custom" → "ALM Server").
2. Activate "ALM Server Service" in Windows Services (Start → "Services" → "ALM_xxxxxxxx" → Startup type: Automatic).
3. Open inbound TCP port 4410 (default ALM RPC) and TCP 4411 (ALM failover) on the server firewall.
4. On each client: Start ALM → "Connect to license server" → enter \\ALMSERVER or IP address.
5. Test the connection: ALM shows the server in green if reachable. A red icon indicates a firewall or DNS issue.
6. Verify the user count: ALM "View" → "Licenses in use" should show zero checkouts before client launch.

Standard licenses for commissioning a single S120 drive line-up (e.g. 6SL3040-1LA00-0AA0 control unit) include three floating seats. License costs vary by region; consult your Siemens representative for current pricing. Floating licenses check out from the server and are released on STARTER exit; if STARTER crashes, the license returns to the pool after 60 minutes (default ALM timeout).

7. First Project: Creating and Going Online

7.1 Offline Project Setup

1. Launch STARTER → "New Project" → enter a project name (e.g. ConveyorLine01_S120). Project names are case-sensitive on Linux shares, so use ASCII characters only.
2. Right-click "Project" → "Insert single drive unit" or "Insert drive object".
3. Select the drive family: SINAMICS S120, G120, etc. The wizard filters subsequent steps based on this choice.
4. Choose the control unit type (CU310-2, CU320-2, CU305, etc.) matching the actual hardware. Wrong selection results in firmware mismatch at first download.
5. Insert the line supply (Active Line Module ALM, Smart Line Module SLM, Basic Line Module BLM) and motor modules per the real topology.
6. Configure the DRIVE-CLiQ wiring in the topology editor to match the physical wiring diagram. Wrong topology causes fault F0135 (DRIVE-CLiQ topology error) at first download.
7. Assign each motor module to a drive object (DO): DO1, DO2, etc. Each DO maps to one drive telegram on PROFINET/PROFIBUS.

7.2 Online Connection

1. Connect the engineering PC to the drive's PROFINET or PROFIBUS port. For S120, the CU320-2 PN port is X150; for S120 with CBE20, ports X1400 P1/P2.
2. Set the accessible nodes: STARTER menu → "Target system" → "Accessible nodes" → STARTER scans the bus and lists all reachable drives by IP/MAC address.
3. Click on the discovered drive and select "Connect to selected target device".
4. STARTER compares the online and offline configuration. If the online firmware differs from the offline support package version, STARTER prompts to install a matching support package (download via SIOS).
5. Click "Download to target device" to push the offline project to the drive. This step erases the drive's parameter RAM and re-flashes the firmware if mismatched.
6. Verify with "RAM to ROM" and "Copy RAM to ROM" to make parameters non-volatile.
7. Save the project to the memory card: right-click drive → "Save to memory card".

7.3 Telegram Configuration

PROFIdrive telegrams define the cyclic data exchanged between the PLC and the drive. STARTER provides wizards under "Configuration" → "PROFIdrive Telegram" for the standard telegrams:

For SIMATIC S7-1200/1500 projects, the standard telegram is selected in the TIA Portal device configuration and must match the STARTER telegram setting. A mismatch causes F01910 (PROFIBUS/PROFINET setpoint timeout) or F08501 (PROFIdrive sign-of-life error).

8. DCC (Drive Control Chart) Programming

DCC is Siemens' graphical function-block programming environment for SINAMICS drives, similar to CFC (Continuous Function Chart) in SIMATIC PCS 7. DCC charts execute on the drive's CU at 4 ms cycle (or 1 ms with the DCC_BASIS option), enabling closed-loop control, encoder evaluation, and signal conditioning without an external PLC.

8.1 DCC Chart Creation

1. Open the project in STARTER and select the drive object.
2. Right-click "Drive object" → "Insert DCC chart". The chart is added to the DO's processing sequence.
3. Open the DCC editor (separate window). The library contains ~150 standard blocks: AND, OR, ADD, MUL, PID, PT1, Integrator, Switch, Demux, Ramp, etc.
4. Drag blocks from the library to the chart sheet. Connect input/output pins by clicking and dragging.
5. Assign the chart's run-time group (e.g. OB1 (4 ms)) under the chart's properties.
6. Compile the project. Errors are listed in the "Compile/Check" tab.
7. Download to the drive. The DCC chart becomes part of the firmware and persists across power cycles.

8.2 Common DCC Pitfalls

• Charts not assigned to a run-time group: the chart compiles but never executes. Always set the run-time group in the chart properties.
• Signal mismatch: connecting a boolean output to a floating-point input causes a runtime error. Use TypeConv blocks to convert.
• Excessive run-time: too many blocks in a 4 ms group overloads the CU. Split into a 16 ms group for slow signals.
• Feedback loop without an integrator: pure proportional loops may oscillate. Add an Integrator block for setpoint tracking.

9. Safety Integrated Commissioning

For drives with Safety Integrated (drive-based safety) features — STO (Safe Torque Off), SS1 (Safe Stop 1), SS2 (Safe Stop 2), SOS (Safe Operating Stop), SLS (Safely Limited Speed), SDI (Safe Direction), SLP (Safely Limited Position), SSM (Safe Speed Monitor) — STARTER provides a dedicated commissioning workflow under "Functions" → "Safety Integrated".

9.1 Safety Acceptance Test

After configuring safety functions, the engineer must perform a documented acceptance test per EN ISO 13849-1 and EN 62061. STARTER automates part of this:

1. Configure safety functions: assign F-DI (Failsafe Digital Input) terminals on the CU or TM54F to the desired safety functions.
2. Set the SLS limit, SDI direction, SLP position range per the risk assessment.
3. Click "Functions" → "Safety Integrated" → "Acceptance test".
4. STARTER guides through a checklist: verify STO by removing the F-DI signal and confirming the drive stops. Verify SS1 by reducing the stop time. Verify SLS by exceeding the speed limit.
5. At the end, STARTER generates a PDF report with CRC32 checksums of all safety parameters, the test results, and a signature line for the responsible engineer.

The acceptance test report is required for CE marking and must be retained for the lifetime of the machine. Without this report, the drive operates in a state flagged as F01600 (Safety acceptance test required) at every power-up.

10. Parameter Backup and Restore

STARTER provides three backup mechanisms, each suited to a different scenario:

10.1 Drive Backup Procedure

1. Connect online to the drive.
2. Right-click the drive object → "Target system" → "Upload to PG".
3. STARTER reads all parameters from the drive's RAM and ROM, plus the trace buffers and fault history.
4. Save the project to disk via "Project" → "Save As".

10.2 Spare Drive Replacement

1. Insert a blank CF card into the spare CU (or use the existing card if cloned).
2. Open the original project's .sdf file in STARTER.
3. Connect online to the spare drive.
4. Click "Download to target device" with the option "Including firmware" checked.
5. Wait for the firmware flash and parameter download (~5–10 minutes for a full S120 chassis).
6. Verify with the acceptance test or a control panel test run.

Spare drive replacement without a project file is possible only if the original CF card is available. Remove the CF card from the failed drive and insert it into the spare — the spare will boot with the original parameters and firmware. This is the fastest field-service method (under 2 minutes).

11. Migrating STARTER Projects to Startdrive (TIA Portal)

For new projects on S120 firmware V5.1+, Startdrive is the strategic platform. Migration is semi-automated:

1. In STARTER V5.3 or V5.5, open the existing project.
2. Save the project as a .sdf file (the default STARTER format).
3. In TIA Portal, open or create a project and add a Startdrive device (TIA V16+).
4. Right-click the device → "Migrate" → "Import STARTER project".
5. Select the .sdf file. TIA Portal converts the parameter set, topology, and DCC charts.
6. Resolve any warnings (e.g. parameter p0700 was renamed in V5.2, F-block references to retired parameters, BICO interconnections to renamed parameters).
7. Compile and download to the drive.

The migration is lossless for plain parameter sets and DRIVE-CLiQ topology. Custom DCC charts, Safety Integrated parameters, and free-function blocks (FFB) may require manual re-mapping. Always keep a backup of the original .sdf file before migration, and validate the migrated project with a control panel test run before authorizing production.

12. Troubleshooting Matrix

13. Frequently Asked Questions