Creating SINAMICS Projects in PCS 7 V9.0: S7T Config Workflow

Overview: PCS 7 V9.0, S7 Technology, and SINAMICS Integration

SIMATIC PCS 7 V9.0 is Siemens' distributed control system (DCS) used for process automation in industries such as chemical, pharmaceutical, power, and water/wastewater. PCS 7 V9.0 ships with WinCC Explorer (HMI/SCADA runtime and configuration), STEP 7 / SIMATIC Manager (programmable logic controller engineering), and the optional S7 Technology option package for motion control. The S7 Technology package is delivered as the S7T Config application and the S7TECCAM library / function blocks that expose technology objects (TO) such as speed axes, positioning axes, and cams to the S7-400 CPU.

When SINAMICS drives (S120, G120, G150, S150) are deployed alongside PCS 7, the typical engineering path is:

1. Create or open a STEP 7 project in SIMATIC Manager.
2. Insert a SIMATIC S7-400 station (or S7-410 for PCS 7 V9.0 / V9.1) with the correct CPU firmware.
3. Add S7 Technology objects via S7T Config and assign them to the SINAMICS drive telegram.
4. Bind the technology object to PROFIBUS / PROFINET communication via the drive's PROFIdrive / PROFIsafe telegrams (typically Telegram 1, 2, 3, 5, 102, 103, 105, 106).
5. Use STARTER (or Startdrive in TIA Portal) for parameter-level commissioning of the SINAMICS drive itself.

The most common source of confusion at this point is the assumption that S7T Config is a stand-alone project editor that can create a new STEP 7 project on its own. It cannot. S7T Config is a technology object editor that lives inside a STEP 7 project. This article clarifies the correct workflow and resolves the "I cannot create a new project in S7T Config" issue reported after installing PCS 7 V9.0 on a Windows workstation that already contained STEP 7, WinCC Explorer, and S7 Technology.

Problem Details: S7T Config Does Not Create New Projects

After installing PCS 7 V9.0 on top of an existing STEP 7 + WinCC Explorer + S7 Technology installation, the user observes the following symptoms:

• Symptom 1: Opening S7T Config directly from the Windows Start menu and selecting File → New either produces no action or prompts the user to select a STEP 7 project file (.s7p) that already exists.
• Symptom 2: An existing project that already contains SINAMICS drive objects can still be opened and edited, but a fresh technology object insertion fails because the host project context is missing.
• Symptom 3: No "S7 Technology" entry appears under the Windows Start menu, even though the option package is correctly installed (verified in SIMATIC Manager via Options → Option Package Installer or Help → About).

All three symptoms share a single root cause: the engineer is attempting to use S7T Config as the entry point of the project lifecycle, which is architecturally incorrect. S7T Config is bound to the STEP 7 (SIMATIC Manager) project container; it is not a peer tool that can compete with SIMATIC Manager for project creation.

Root Cause: Architectural Boundary Between SIMATIC Manager and S7T Config

The S7 Technology option package installs two distinct components on the engineering station:

The correct interpretation of the Siemens manual SIMATIC Engineering Tools S7 Technology, section 4 "Fundamental procedure for configuration", is that the configuration workflow is initiated in SIMATIC Manager, not in S7T Config. S7T Config is launched from inside SIMATIC Manager (right-click the CPU → Start S7T Config) and uses the active project's station and CPU as its anchor.

Prerequisites for a Clean S7T / SINAMICS Workflow

Before initiating the corrected workflow, verify the following on the engineering station (ES):

1. Operating system: Windows 10 Enterprise LTSC 2019 (x64) or Windows Server 2016 / 2019, matching the PCS 7 V9.0 Readme / Installation Notes.
2. SIMATIC PCS 7 V9.0 with installed component SIMATIC S7-400 CPU (part of STEP 7 V5.6 SP2 bundled with PCS 7 V9.0).
3. STEP 7 V5.6 SP2 or later installed and licensed (HFx hotfix recommended for V9.0 SP1/SP2).
4. S7 Technology V4.6 SPx (matches the STEP 7 build shipped with PCS 7 V9.0). Verify via Start → SIMATIC → STEP 7 → Option Package Manager.
5. WinCC Explorer V7.4 SP1 (or higher update) for the OS server / OS client.
6. SINAMICS STARTER V5.4 (or Startdrive V16 in TIA Portal if the drive is engineered in TIA).
7. The SINAMICS drive firmware and CBE20 / PROFIBUS CBE option module should be at the version listed in the SIMATIC S7-300/400 S7 Technology Function Manual compatibility table.

Step-by-Step: Creating a New S7T-Enabled Project from SIMATIC Manager

This procedure produces a STEP 7 project that contains the S7-400 station, the SINAMICS drive object, and the S7 Technology axis. Use it for any greenfield PCS 7 V9.0 site that needs motion control.

1. Open SIMATIC Manager from Start → SIMATIC → STEP 7 → SIMATIC Manager.
2. Select File → New → New Project. Assign a project name (for example SINAMICS_Coiler_01) and a storage path on a local or project-server drive. Do not use a UNC path that contains spaces.
3. In the project tree, right-click the project node and select Insert New Object → SIMATIC 400 Station. The station object (SIMATIC 400(1)) is added to the project.
4. Open HW Config by double-clicking Hardware under the S7-400 station. Drag the appropriate rack (UR2 / UR2 ALU), power supply (PS 405 10A or PS 407 10A), and CPU (for example CPU 417-4 or CPU 410-5H for a redundant PCS 7 V9.0 controller) from the hardware catalog.
5. Configure the CPU's MPI/DP and PN interfaces. For PROFINET connection to SINAMICS S120 with CBE20, set the PN interface IP address (for example 192.168.0.10) and subnet mask.
6. Drag the SINAMICS S120 drive from the catalog (path: PROFINET IO → Drives → SINAMICS → S120 CU320-2 DP/PN) into the PROFINET IO system. Assign the device name s120-cu320-2 and IP 192.168.0.20.
7. Insert a standard PROFIdrive telegram (typically Telegram 1 for speed control, Telegram 3 for speed control with 2 encoders, or Telegram 102/103/105/106 for positioning). Confirm the I/O addresses (default 256..267 for Telegram 1).
8. Save and compile the hardware configuration. Close HW Config.
9. Right-click the CPU object in SIMATIC Manager and choose Start S7T Config. The S7T Config editor opens in the context of the active project.
10. In S7T Config, use Insert → Technology Object to add a Speed Axis or Positioning Axis. Bind the technology object to the SINAMICS drive's configured telegram and logical I/O addresses.
11. Download the hardware configuration and the S7T configuration to the CPU. Restart the CPU if the firmware flags a stop-causing alarm (for example SF LED on after download).

Step-by-Step: Alternative Drive-Only Commissioning with STARTER

If the goal is to commission a SINAMICS drive without creating a STEP 7 project — for example, during FAT (factory acceptance test) or when pre-commissioning a drive cabinet before the PCS 7 controller is wired up — use STARTER as the project creator. STARTER produces a drive-only project that can later be imported into the STEP 7 project via a .dpx archive.

1. Launch STARTER from Start → Siemens Automation → STARTER → STARTER.
2. Select Project → New → New Project (with Drive Unit) and assign a project name such as S120_CabinetA.dpx.
3. Insert the SINAMICS drive unit via Insert → Drive Unit. Choose the device family (S120, G120, G150, S150, S210), the article number (for example 6SL3040-1MA01-0AA0 for a CU320-2 PN), and the firmware version (for example V5.2 SP3).
4. Configure the drive's power section (Line Module, Motor Module, motor type, encoder). Save the project.
5. Establish online access (PROFINET, PROFIBUS, Ethernet, or USB) and click Connect to target system. Download the parameterization to the drive.
6. Once commissioning of the drive is complete, export the project to a .dpx archive: Project → Archive → Save archive.
7. In SIMATIC Manager, attach the drive to the S7-400 station. Use PLC → Drive → Import STARTER Project (or the menu path provided by the S7 Technology integration plug-in). Select the .dpx archive.

The drive is now visible in HW Config and can be bound to a technology object inside S7T Config.

SINAMICS Drive Telegram Mapping for S7T Integration

The S7 Technology axis expects the drive to be configured with one of the standard PROFIdrive telegrams. The mapping used in PCS 7 V9.0 with S7 Technology V4.6 is:

Configure the telegram inside HW Config under the SINAMICS drive's Properties → Parameter Assignment and confirm the same telegram is selected inside S7T Config's axis wizard; mismatches between HW Config and S7T Config are a frequent source of F01910 (PROFIBUS / PROFINET setpoint timeout) and F08501 (sign-of-life failure) on the SINAMICS side.

Multi-User Engineering Station (ES) Configuration

The second question raised in the original report asks whether PCS 7 V9.0 supports a C/S (Client/Server) structure for ES so multiple engineers can edit the same project concurrently. The answer is yes, but it requires a specific topology:

• ES Server: A Windows Server 2016 / 2019 hosting the PCS 7 project archive on a network share. PCS 7 V9.0 supports SIMATIC PCS 7 Project Server, which integrates with the SIMATIC Manager's Server view.
• ES Clients: Engineering workstations that open the project from the server share via File → Open → Project on Server. Each client must have a local PCS 7 installation with the same option packages (S7 Technology, CFC, SFC, etc.) at the same version as the server.
• Exclusive object locking: The PCS 7 server uses exclusive locks at the CFC / SFC chart level. Two engineers cannot edit the same chart simultaneously; the second will receive a Chart locked by user <username> dialog.
• Project versioning: Use the SIMATIC Manager's Version → Project Version functions or an external source-control system. Native Git integration is not supported in PCS 7 V9.0; use Siemens' PCS 7 Plant Data Backup or the Subversion / TIA Project Server add-on if a formal VCS is required.

WinCC Explorer Integration and OS Project Creation

WinCC Explorer in PCS 7 V9.0 is the configuration front-end for the Operator Station (OS). It is launched from SIMATIC Manager via Insert New Object → SIMATIC PC Station → WinCC Application and is bound to the same project container as the AS. Common pitfalls when S7 Technology is also in the project:

• The OS picture @@PCS7_Typicals.pdl must include the SINAMICS faceplate (@SINAMICS_S120.pdl or similar) for the drive to be visible in runtime. Import the faceplates from the PCS 7 APL Library before compiling the OS.
• OS server and OS client must both be on the same WinCC version (V7.4 SP1 for PCS 7 V9.0). Mismatched WinCC versions block the S7TM diagnostics buffer import used by S7 Technology alarms.

Troubleshooting Matrix

Verification Checklist

After applying the corrected workflow, validate the result by checking each item below:

1. The STEP 7 project opens in SIMATIC Manager without the "S7T Config cannot find project" warning.
2. HW Config compiles without errors; the SINAMICS drive icon is visible in the PROFINET IO system.
3. S7T Config opens from the CPU context menu and lists at least one technology object (TO) under Technological Objects.
4. A compile / consistency check from the project tree returns No errors, no warnings.
5. After download, the SINAMICS drive goes to Operation (green LED on the CU320-2) and the S7-400 CPU reports RUN with no SF / BF LEDs active.
6. The STARTER online diagnostic buffer shows no F (fault) entries. Only A (alarm) entries are acceptable during commissioning.
7. The WinCC OS runtime picture displays the SINAMICS faceplate with live actual values from the drive.

Common Follow-Up Topics

Engineers who successfully deploy the workflow above often continue with one of the following enhancements:

• PROFIsafe over PROFINET: Add SINAMICS S120 with PROFIsafe (Telegram 30 or 901) and integrate the SINAMICS safety functions (STO, SS1, SS2, SOS, SLS, SDI) into the PCS 7 safety matrix.
• CAM technology: Use S7T Config's Cam technology object for electronic camming, with the cam disk edited in the S7T Cam Editor.
• Redundant AS (H-system): Replace the S7-400 CPU with an AS 410 pair (CPU 410-5H) and configure redundant S7T axis. Note that not all S7T function blocks support redundancy — consult the S7 Technology manual appendix "Blocks for H-systems".
• Migration to TIA Portal: PCS 7 V9.1 and later support a partial migration path via SIMATIC Migration Tool. S7T objects are migrated to TIA Portal technology objects with manual re-binding required.