Starting STEP 7 with Preset Program, Block, and Network Line

Engineers commissioning large S7-400 fleets often want to open SIMATIC Manager directly to the block and network they need to inspect, not to the empty offline view. STEP 7 V5.x ships a small command-line interface that takes the project path, a block reference, an ObjectID, and a few behavioural flags. This reference documents the full switch set, decodes the path and ObjectID syntax, and supplies a working C# and PowerShell launcher for desktop tools, CMMS hooks, and CI scripts.

Overview

SIMATIC Manager accepts a set of command-line switches that pre-select a project, a block within that project, and (with the right ObjectID) a specific network inside the block. The switches are documented in the integrated help under "Starting Step 7 with default start parameters" and revisited in the Siemens Programming with STEP 7 manual.

The four switches you will work with are:

• /o <logical path> — opens the project, program folder, and block.
• /h <ObjectID> — positions the cursor on a specific network/line using the object's internal ID.
• /keep — re-uses an existing SIMATIC Manager instance instead of starting a new one.
• /onl — opens the project in online mode (connects to the configured CPU).

Path and ObjectID can be used independently. The path alone opens the project at the block root, while the ObjectID is required to land on a specific network. Both path and ObjectID are stable for the lifetime of the project on disk; rename a station or move a block and you must regenerate the ObjectID.

Prerequisites

• STEP 7 V5.4 SP5, V5.5, or V5.6 installed (V5.5 is the most common deployment target for S7-300/S7-400; V5.6 is required for the S7-400H and S7-400F/FH add-ons).
• SIMATIC Manager reachable at %ProgramFiles(x86)%\Siemens\Automation\SIMATIC Manager\Step7\S7MANAG.exe (default install path).
• An S7 project (S7-300, S7-400, S7-400H, S7-400F, WinAC, or ET 200 station) saved on a local or mapped network drive that SIMATIC Manager can resolve.
• A project entry under HKCU\Software\Siemens\Automation\SimaticManager\Projects so SIMATIC Manager can resolve the project name to a file-system path. Opening the project once interactively populates this key.
• For automation: .NET Framework 4.7.2+ or .NET 6/7/8 (Windows) with System.Diagnostics.Process. PowerShell 5.1+ (bundled with Windows 10/11) for the script example.
• For the COM section: the STEP 7 V5.x SDK installed (S7API IDL and headers) and a development environment capable of importing COM type libraries.

Command-Line Switch Reference

Logical Path Syntax and View/Online ID

The /o argument follows a fixed grammar. According to the STEP 7 help, the logical path has the form:

[View ID,online ID]:project name\{object name\}*\object name

Concretely, opening FB1 in S7-Program(1) of a project named MyConfig looks like this:

/o "1,8:MyConfig\SIMATIC 400(1)\CPU416-1\S7-Program(1)\Blocks\FB1"

Each backslash-separated token is one level of the project tree:

1. Project name — must match the folder name on disk and the name registered in the S7Proj registry entries.
2. Station — SIMATIC 400(1) for a standard S7-400, SIMATIC 400H(1) for a redundant pair, SIMATIC 300(1) for an S7-300, SIMATIC PC Station(1) for WinAC, or an ET 200S/ET 200M/ET 200pro station name for distributed I/O.
3. CPU — the rack slot name, e.g. CPU416-1, CPU315-2 PN/DP, CPU 412-3H for an H-CPU.
4. Program folder — S7-Program(1) in the typical case. S7-Program(2) is created only if the project uses a second program (rare, mostly in PCS 7).
5. Block container — Blocks for the standard block folder, or Sources for STL/SCL source files.
6. Block name — e.g. FB1, OB1, DB10, FC100, UDT20, VAT1 (variable table), or an SFB/SFC reference.

Special targets inside a block

To pre-select a sub-object within a block (a single network inside FB1, for example), the path can be extended with a final segment:

/o "1,8:MyConfig\SIMATIC 400(1)\CPU416-1\S7-Program(1)\Blocks\FB1\Network 5"

The trailing segment is matched by display name, not by index. If the network was renamed (e.g. Startup), the renamed name must be used. For S7-SCL sources inside the Sources folder, the same trick works with the source-file name as the trailing segment.

Path examples for common configurations

View ID and Online ID

The [View ID,online ID] prefix on the path is an internal selector pair used by SIMATIC Manager to choose between the offline and online view of the same project. The two numbers are decimal indices assigned by SIMATIC Manager when the project is created:

• View ID — selects the view level. 1 is the standard "Component view" used by almost every project. 2 exists for plant view in older PCS 7 configurations.
• Online ID — selects the connection state. 8 is the offline database; 9 (or higher) is the online mirror that SIMATIC Manager populates when you click Go online.

For almost every S7-300/S7-400 workstation the prefix is 1,8. PCS 7 and WinCC projects can show 1,9 for online access. The prefix is fixed per workstation, not per project, and is stored in the shortcut that SIMATIC Manager creates from File → Create Shortcut.

To confirm the prefix on your own machine:

1. Right-click a block in SIMATIC Manager and choose Create Shortcut.
2. Right-click the new .lnk file, choose Properties, and read the Target field.
3. The Target will contain the full command line including the prefix; the digits before the colon are the View ID and Online ID.

ObjectID Structure (/h)

The /h switch takes an ObjectID — a semicolon-delimited string that encodes the path from the project root down to a specific object (down to a network/line pair in extreme cases). The STEP 7 help example is:

/h T00112001;129;T00116001;1;T00116101;16e /keep

The ObjectID has the form:

T<8-hex-digits-of-project>;<type-code>;T<8-hex-digits-of-station>;<level>;T<8-hex-digits-of-object>;<hex-of-object>

The ObjectID is not something you build by hand. The field workflow is:

1. Open the project in SIMATIC Manager and navigate to the network you want a launcher for.
2. Right-click the network title or block, choose Create Shortcut.
3. Open the shortcut's Properties → Target and copy the entire /h argument (the digits after /h up to the next whitespace or /).
4. Paste that string into your own launcher / script verbatim.

/keep and /onl Behaviour

Field testing of the /keep and /onl switches consistently shows that they are not reliable for cursor positioning:

Both behaviours may also be an interaction with missing View ID, Online ID, or ObjectID tokens — Siemens' help file leaves the relationship between /keep and the path syntax under-specified. Treat /keep and /onl as best-effort, not as contract. The /o + /h combination is the only one that consistently positions the cursor.

Step-by-Step: Building the Launch Shortcut

1. Open SIMATIC Manager and load the target project.
2. Navigate to S7-Program → Blocks → target block (e.g. FB1). If you need a specific network, click into that network so the cursor is on its title.
3. Right-click the block or network title → Create Shortcut. SIMATIC Manager drops a .lnk on the desktop that contains a fully-formed command line.
4. Right-click the shortcut → Properties → Shortcut and read the Target field. It will look like:

   "C:\Program Files (x86)\Siemens\Automation\SIMATIC Manager\Step7\S7MANAG.exe" /o "1,8:MyConfig\SIMATIC 400(1)\CPU416-1\S7-Program(1)\Blocks\FB1" /h T00112001;129;T00116001;1;T00116101;16e

5. Copy the full string and adapt it for your own launcher (C#, batch file, PowerShell, or a custom document management system). The /h argument can be dropped if network-level positioning is not required.
6. Verify by double-clicking the shortcut; SIMATIC Manager must open with the requested block visible and the cursor on the network encoded in the ObjectID.

C# and PowerShell Automation Examples

The following .NET 8 console snippet shows how to wrap the STEP 7 launcher so a custom tool (CMMS, dashboard, or CI script) can open a specific block on demand. It accepts the project name, station, CPU, S7-Program index, and block name as arguments, builds the logical path, and optionally appends the ObjectID captured from a pre-generated shortcut.

using System;
using System.Diagnostics;

namespace Step7Launcher
{
    internal static class Program
    {
        // Default SIMATIC Manager install path. Override with the first CLI argument
        // or via the STEPMANAGER_EXE environment variable.
        private const string DefaultSimaticManager =
            @"C:\Program Files (x86)\Siemens\Automation\SIMATIC Manager\Step7\S7MANAG.exe";

        private static int Main(string[] args)
        {
            if (args.Length < 5)
            {
                Console.Error.WriteLine(
                    "Usage: Step7Launcher.exe <project> <station> <cpu> " +
                    "<s7program-index> <block> [objectId] [subTarget]");
                return 2;
            }

            string project      = args[0];
            string station      = args[1];   // e.g. "SIMATIC 400(1)"
            string cpu          = args[2];   // e.g. "CPU416-1"
            string programIndex = args[3];   // usually "1"
            string block        = args[4];   // e.g. "FB1"
            string objectId     = args.Length >= 6 ? args[5] : null;
            string subTarget    = args.Length >= 7 ? args[6] : null; // e.g. "Network 5"

            // 1,8 is the standard offline component view for S7-300/S7-400.
            string blockPath = $"Blocks\\{block}";
            if (!string.IsNullOrEmpty(subTarget))
            {
                blockPath = $"{blockPath}\\{subTarget}";
            }

            string logicalPath =
                $"\"1,8:{project}\\{station}\\{cpu}\\S7-Program({programIndex})\\{blockPath}\"";

            string arguments = "/o " + logicalPath;
            if (!string.IsNullOrEmpty(objectId))
            {
                arguments += $" /h {objectId}";
            }

            string exe = Environment.GetEnvironmentVariable("STEPMANAGER_EXE")
                         ?? DefaultSimaticManager;

            var startInfo = new ProcessStartInfo
            {
                FileName        = exe,
                Arguments       = arguments,
                UseShellExecute = false,
                WorkingDirectory = Environment.CurrentDirectory
            };

            try
            {
                Process.Start(startInfo);
                Console.WriteLine("Launched: " + exe + " " + arguments);
                return 0;
            }
            catch (Exception ex)
            {
                Console.Error.WriteLine("Launch failed: " + ex.Message);
                return 1;
            }
        }
    }
}

Build and call it:

dotnet publish -c Release -r win-x64 --self-contained false
Step7Launcher.exe ^
  "MyConfig" "SIMATIC 400(1)" "CPU416-1" "1" "FB1" ^
  "T00112001;129;T00116001;1;T00116101;16e" "Network 5"

The same launch can be done from PowerShell with one line:

$exe = "C:\Program Files (x86)\Siemens\Automation\SIMATIC Manager\Step7\S7MANAG.exe"
$arg = '/o "1,8:MyConfig\SIMATIC 400(1)\CPU416-1\S7-Program(1)\Blocks\FB1" /h T00112001;129;T00116001;1;T00116101;16e'
Start-Process -FilePath $exe -ArgumentList $arg

For a persistent service that opens STEP 7 on demand, wrap the C# launcher in a Windows service or a Windows Communication Foundation (WCF) endpoint. The service should hold the ObjectID strings in configuration (not in code) so the launch definitions can be updated without redeploying.

Launch Methods Compared

COM Automation and SDK Notes

For deeper automation than the command line can provide, STEP 7 V5.x ships a COM automation layer. The type library is registered during the STEP 7 V5.x install and is described in the SDK under %ProgramFiles(x86)%\Siemens\Automation\SIMATIC Manager\Step7\S7API. The COM object supports (signature varies by service pack):

• Opening an S7 project by file-system path with a flag controlling offline/online state.
• Selecting an object inside the open project tree (analogous to the /o path).
• Activating a specific block in the editor, optionally tied to an instance DB.

COM automation is the recommended path for service-style applications (an Openness-like broker, for example) because it survives SIMATIC Manager restarts and works over DCOM. References for the IDL definitions and C++ headers are bundled in the STEP 7 V5.6 SDK; managed wrappers can be built with tlbimp.exe and consumed from C# via System.Runtime.InteropServices. If only a launcher is needed, the command-line switches above are sufficient and avoid the COM dependency on the STEP 7 SDK.

Edge cases: H systems, F systems, distributed I/O

Troubleshooting and Verification

Verification checklist

• SIMATIC Manager opens within 5 seconds of the launcher invocation.
• The project name in the title bar matches the requested project.
• The block editor pane shows the requested block (FB1, OB1, etc.).
• The cursor is on the network encoded by the ObjectID, or on network 1 if no ObjectID was supplied.
• No error dialog appears in the SIMATIC Manager session.
• Closing the editor and clicking the same launcher again opens the same block at the same network.

For permanent CI hooks, capture the SIMATIC Manager process ID with Process.GetProcessByName("S7MANAG") and assert it returns one row shortly after launch. PowerShell equivalent:

Start-Process -FilePath $exe -ArgumentList $arg -PassThru |
  ForEach-Object { Start-Sleep -Seconds 3; (Get-Process -Id $_.Id).MainWindowTitle }

FAQ