Overview
The Siemens Open PMC104 is a legacy open-architecture process and machine control platform that was positioned by Siemens for governor and process control duties in the hydroelectric generation sector. It pairs a standard PC/AT-compatible industrial computer with deterministic I/O and a Siemens-supplied runtime to execute control logic for turbine governors, excitation tie-ins, and ancillary plant. Because the platform was marketed as an "open" system, integration of third-party I/O, custom HMI panels, and SCADA links was a stated design goal rather than a retrofit.
Operationally, the unit behaves like a soft-PLC: the program resides on disk, is loaded into a runtime, executes against polled or interrupt-driven I/O, and exposes a programming interface for engineering changes. This is precisely the reason field engineers still encounter Open PMC104 sites today and ask the same recurring questions:
- Which Siemens tool starts, stops, and connects to the runtime?
- How is a project uploaded from the controller and downloaded back to it?
- How are online modifications made without a full stop/start cycle?
- Is there a documented migration path to a supported Siemens platform?
Those questions, and the scarcity of formal Siemens answers, are the motivation for this reference. The remainder of the document collects the practical information that is publicly verifiable, flags where the documentation gap is real, and points at the supported successor platform: PMC/LS-B version V2.0.
System Status and Documentation Reality
When an engineer first searches Siemens for Open PMC104 material, the result set is noticeably thin compared to mainstream SIMATIC families (S7-300/400/1200/1500). Three structural reasons explain this:
- Product placement. Open PMC104 sits in the hydro/power-generation niche of the Siemens portfolio rather than the general automation catalog. Its marketing was aimed at utility engineers and governor integrators, not the broad factory-automation community.
- Legacy status. Once a Siemens platform is reclassified as legacy, the documentation investment shifts from creation to preservation. Manuals and presentations are kept reachable, but application notes, FAQs, and firmware bulletins stop accumulating.
- Open-architecture deployment. Because integrators frequently combined Open PMC104 with third-party HMIs, governors, and governors' excitation logic, the Siemens-authored documentation is often a starting point rather than a complete recipe.
The historical entry point was the Siemens "automation technology – OpenPMC" landing page, which exposed a Technical Documentation link with installation manuals, commissioning guides, and a migration recommendation. That archive is the single most concentrated source of authoritative information; treat it as the canonical reference for any project where original Siemens hardware is still in service.
Where the source documentation stops, the practical engineering guidance below attempts to fill the gap without overstating what is formally specified. Procedures are written as a competent integrator would execute them on similar Siemens soft-PLC runtimes, with explicit notes where Open PMC104-specific confirmation is required from local Siemens representation.
Programming and Runtime Architecture
Open PMC104 is built on an industrial PC with a real-time or near-real-time operating layer. The control program is stored as project files on local or network storage, and a runtime service reads those files, allocates I/O maps, and executes the application cycle. The split between development environment (engineering station) and runtime (target) is the same model used by SIMATIC WinAC and similar PC-based controllers.
| Layer | Function | Typical Component |
|---|---|---|
| Engineering | Project authoring, compilation, online diagnosis | Siemens PMC programming tool (PC-based) |
| Runtime | Deterministic execution of compiled logic | Open PMC104 runtime service on industrial PC |
| I/O subsystem | Analog/digital I/O, governor valves, speed sensors | PCI/ISA I/O cards or fieldbus couplers |
| Communication | SCADA, HMI, governor panel, excitation | Serial, Ethernet, PROFIBUS, OPC |
Understanding this layering is essential before attempting go-online, because the engineering tool talks to the runtime service, not directly to the I/O cards. If the runtime service is not started, an upload/download/online edit is impossible regardless of network connectivity.
Prerequisites for Go-Online
Before attempting any go-online, upload, download, or online edit, verify the following from the engineering station:
- Programming software installed. Use the Siemens-supplied PMC programming tool matching the project version. Mixing project revisions and tool revisions is the single most common cause of "tool refuses to go online" errors.
-
Target reachable on the network. Confirm IP/subnet or serial parameters with
ping,arp -a, or the equivalent Windows network tools. The engineering PC and the Open PMC104 target must share a routable subnet or be on the same physical serial line. - Runtime is started on the target. The runtime service must be active. On the target's local console, verify the runtime status indicator (LED, HMI status, or service status). A stopped runtime cannot accept a go-online session.
- User rights. Engineering changes typically require an authorized user. Confirm the engineering account on the target accepts connections for the planned operation (upload, download, online edit).
- Project backup. Before any download, capture a complete upload of the current running program. Save it with a timestamped file name. The download will overwrite the live configuration.
Go-Online Procedure
The exact menu paths depend on the specific Siemens PMC programming tool release, but the operational sequence is consistent across soft-PLC platforms.
- Open the project in the engineering tool on the engineering PC.
- Select the target node in the project tree, or open the "Online" / "Connect to target" dialog.
- Confirm the communication path (Ethernet TCP/IP or serial) and the target's network address. Match the address exactly to the runtime configuration.
- Initiate "Go online" / "Connect." The tool will attempt a handshake with the runtime service.
- On successful connection, the online indicator turns active and the tool displays online values for tags and I/O.
Failure modes and their first-line checks:
| Symptom | Likely Cause | First-Line Check |
|---|---|---|
| Connection times out | Wrong IP/subnet or firewall |
ping target, verify Windows Firewall on engineering PC, check any host-based firewall on the Open PMC104 PC |
| Connection refused | Runtime service not started | Connect a monitor to the target, verify the runtime is loaded and started |
| Authentication failure | Wrong user/password | Verify credentials with local administrator; check whether the runtime enforces a user list |
| Project mismatch | Offline project differs from online program | Compare project version/firmware; re-open the matching project |
Upload from the Target
An upload reads the project currently executing in the runtime and saves it on the engineering PC. The upload is the canonical way to recover a project when the engineering source is lost or out of date.
- Go online as described above.
- Select "Upload to PG/PC" (or the equivalent menu item in the PMC tool). The tool reads the running program's source representation, including logic, configuration, and tag tables.
- Save the uploaded project under a new, version-stamped file name. Do not overwrite the engineering source until the uploaded content has been compared and reconciled.
- Diff the uploaded project against the last engineering source. Differences indicate undocumented online edits performed by other integrators and are common on legacy systems.
Because Open PMC104 is an open platform, integrators sometimes performed online-only edits that were never saved back to engineering storage. A fresh upload is the only way to discover these edits.
Download to the Target
A download writes the engineering project into the runtime, replacing the currently executing program. This is the operation with the highest operational risk.
- Confirm an upload backup exists. If not, perform an upload first.
- Place the turbine in a safe state per site procedure (valves closed, breaker open, governor in manual service as required).
- Go online.
- Select "Download to target" / "Download to device." The tool compiles the offline project, transfers it, and prompts for stop/start behavior of the runtime.
- Choose the appropriate stop/start mode. On governor applications, a controlled stop of the runtime is almost always preferred to avoid uncontrolled output transitions.
- After download, monitor the runtime state, the I/O status, and any watchdog indicators for at least one full operational cycle before returning the unit to automatic control.
Online Modifications
Online modifications are edits to the running program without a full download. They are supported on most Siemens soft-PLC platforms and almost certainly supported on Open PMC104, but they are documented unevenly in the legacy manuals.
Typical online edit capabilities and constraints:
| Edit Type | Supported Online? | Notes |
|---|---|---|
| Tag value force/override | Yes | Use for testing; remember to clear all forces before returning to service |
| Constant value change | Yes | Smallest, safest online edit; take effect immediately |
| Logic block edit (FB/FC body) | Often | May require the runtime to buffer the change at a defined execution boundary |
| Adding new blocks or tags | Sometimes | May force a stop/start; verify with the tool's online change report |
| I/O configuration change | No | Almost always requires a stop/start and a download |
| Communication configuration change | No | Requires a download and runtime restart |
After any online modification, perform a controlled save-back to the engineering source on the PC. If the edit is left only in the runtime, the next upload from a different engineering station will lose it.
Migration Path: PMC/LS-B V2.0
The supported successor direction from the Open PMC family is the PMC/LS-B standard software, which is the current Siemens offering for hydro governor and process control applications of this class. The PMC/LS-B V2.0 release announcement (Siemens ID 4131674) confirms that V2.0 is the current shipping version, with continued investment in security and infrastructure hardening consistent with current industrial cybersecurity guidance.
| Item | Value |
|---|---|
| Product | PMC/LS-B standard software |
| Current version | V2.0 |
| Siemens Support ID | 4131674 |
| Origin platform | Open PMC family (incl. Open PMC104) |
| Release status | Generally available via Siemens Industry Online Support |
For sites still running Open PMC104, the recommended planning sequence is:
- Inventory all Open PMC104 hardware, runtime versions, I/O configurations, and connected field devices.
- Upload the current running project from every Open PMC104 node. Archive with timestamps and a written manifest.
- Engage Siemens or a certified PMC/LS-B integrator for a formal migration assessment. The original Technical Documentation archive for Open PMC includes migration recommendations that should be reviewed against the latest PMC/LS-B V2.0 capabilities.
- Plan the cutover during a scheduled outage. Hydro units are typically cut over during annual maintenance windows.
- Retain the legacy Open PMC104 hardware as cold spare for an agreed transition period; legacy spares are often the limiting factor on legacy platforms.
Troubleshooting: Unit Start-and-Stop Cycling
One of the more common legacy symptoms reported on Open PMC104 installations is a unit that repeatedly starts and stops. Because the platform combines a PC-class computer with deterministic I/O and a real-time layer, the symptom can originate from any of the three layers. The matrix below is the practical diagnostic ladder field engineers apply first.
| Subsystem | Likely Cause | Diagnostic | Remediation |
|---|---|---|---|
| Power supply | PC PSU sagging under I/O card inrush | Measure 5 V and 12 V rails at the I/O connector under load | Replace PSU with industrial-rated unit; check for aged electrolytic capacitors |
| Watchdog | Runtime misses a cycle and the watchdog resets it | Inspect watchdog event log on the target | Reduce cycle load, optimize logic, or adjust watchdog timing within Siemens-documented limits |
| Storage | Failing hard disk prevents the runtime from loading reliably | Check S.M.A.R.T. data, scan for bad sectors, check filesystem | Replace with industrial SSD; clone the existing drive first |
| Operating system | Background OS update or driver installation reboots the PC | Inspect Windows event log for forced reboots | Disable automatic updates on the controller; isolate from corporate update policy |
| Governor input | Speed sensor noise causes a startup/overspeed interlock | Scope the speed pickup at the controller terminal | Replace or shield the pickup; check grounding per hydro governor practice |
| External interlock | External permissive (auxiliaries, cooling water) cycling | Trend the permissives in the HMI or SCADA | Repair the field device causing the interlock to drop |
Field Engineering Notes
- Treat the engineering source as the source of truth. If the engineering source and the running program disagree, the running program wins for plant safety; the engineering source wins for documentation discipline. Reconcile both as soon as practical.
- Maintain a media refresh schedule. Industrial PCs in hydro plants are often in service for decades. Replace the boot drive on a 5-7 year cycle, even if it appears healthy, to avoid mid-outage failures.
- Photograph connector pin-outs before re-termination. Legacy I/O cards frequently use proprietary pin-outs that are not in the current Siemens online catalog.
- Isolate the controller from the corporate network. A control PC on a managed network is exposed to update reboots, group policy changes, and antivirus scans. The Open PMC104 controller belongs on a plant-level network with controlled change windows.
- Plan a PMC/LS-B V2.0 migration window now. Spare parts and engineering familiarity for Open PMC104 will continue to decline. Initiating the migration conversation with Siemens or a certified integrator early avoids emergency procurement later.
Summary
Open PMC104 is a capable legacy platform that continues to run in service on hydroelectric governor applications, but the era of routine Siemens support for it has passed. Treat it as a documented but unmaintained system: rely on the original Siemens Technical Documentation archive for the platform, follow standard soft-PLC go-online, upload, download, and online-edit procedures, capture the running project with an upload before any change, and begin a structured migration to PMC/LS-B V2.0 as soon as site planning allows.
Frequently Asked Questions
Which Siemens software is used to go online with an Open PMC104?
Use the Siemens PMC programming tool version that matches the project and runtime. The exact package name and version are listed in the original Open PMC Technical Documentation archive; mismatched tool and runtime versions are the leading cause of failed go-online attempts.
How do I upload a project from an Open PMC104 controller?
Establish an online connection from the engineering PC, then trigger the upload-to-PG/PC function. Save the uploaded project with a timestamped file name and diff it against the last engineering source to detect undocumented online edits.
Can I perform online modifications without stopping the runtime?
Small edits such as tag value changes, constant adjustments, and many logic-block edits can be applied online. Adding new blocks, changing I/O configuration, or changing communication configuration usually requires a stop/start. Confirm with the tool's online change report before applying.
What is the supported migration target from Open PMC104?
The supported successor is the PMC/LS-B standard software, currently at version V2.0 (Siemens Support ID 4131674). Engage Siemens or a certified integrator for a formal migration assessment and schedule the cutover for a planned outage.
Why does my Open PMC104 keep starting and stopping?
The most common root causes, in order, are: failing PC power supply, watchdog resets from cycle overruns, degrading boot media, operating-system forced reboots from automatic updates, noisy speed sensor signals, and unstable external permissives. Capture the runtime and Windows event logs first, then walk the diagnostic matrix above.