Troubleshooting
OP15 project recovery: ComText, ProTool or ProSave
Short answer
Recovering a project from a Siemens OP15 starts with the panel's generation, not software preference. First-generation OP5 and OP15 hardware belongs to ComText, second-generation hardware belongs to ProTool, and firmware version 2.2 draws the line. ProSave is not in the decision: it writes a backup image, not an editable project, and the OP15 is not on its supported-device list.
On this page
Recovering a project from a Siemens OP15 starts with the panel's generation, not with software preference. First-generation OP5 and OP15 hardware belongs to the ComText toolchain, second-generation hardware belongs to ProTool, and the firmware version draws the practical line: below 2.2 you need ComText, at 2.2 or later you need ProTool. ProSave sits outside this decision entirely — it writes a backup image rather than an editable project, and the OP15 is not on its supported-device list. Identify the generation, get the matching tool from Siemens or an authorized distributor, upload from a host the tool was built for, then verify what came back.
Match the tool to the OP15 generation #
The OP15 designation covers two hardware generations that share the same enclosure and keypad layout, so appearance settles nothing. Siemens support guidance for the OP15-A1 states the rule directly: firmware older than 2.2 takes ComText, firmware at 2.2 or newer takes ProTool. ProTool is therefore not a replacement for ComText — the two toolchains support different hardware.
| What the panel tells you | Engineering tool | What an upload gives you |
|---|---|---|
| OP5 or OP15, first generation, firmware below 2.2 | ComText | An editable project |
| OP5 or OP15, second generation, firmware 2.2 or later | ProTool | An editable project |
| OP3, OP7, OP17 | ProTool | Use the exact device entry, not a similar one |
| OP20 and TD10 text displays | ComText family | Keep them out of ProTool-based work |
Record the full designation from the nameplate before requesting anything, and let the firmware version decide when the designation alone does not. The boundary has a documented history of panels refusing the wrong tool, covered in a firmware 2.20 compatibility fix for the OP15 and OP15C.
Worked example, with illustrative version readings. Machine A's OP15 carries firmware 1.5 in its commissioning record: 1.5 < 2.2, so it is first generation and ComText is the tool. Machine B's identical enclosure carries 2.2: 2.2 ≥ 2.2, so it is second generation and ProTool is the tool. One number decides, and nothing visible from the front does.
What each tool actually recovers #
- ComText: the panels that upload an editable project through ComText are the TD10, OP5, OP15, OP20 and OP397, and that statement applies to projects created in ComText. An upload from an OP15 lands as a .o15 project file the same tool opens and edits. ComText is discontinued.
- ProTool: licensed engineering software for the second-generation OP5 and OP15 plus the later panels such as the OP3, OP7 and OP17. Siemens no longer supports it, but it remains the editing path for second-generation projects.
- ProSave: a free Siemens backup and restore utility. Its output is an image you restore to the panel, never a project you open and edit, and the OP15 is not among its supported devices. Take ProSave images of other panels on the machine as extra copies if you wish, but do not build the OP15 recovery around it.
The generation rule is not unique to this family: deciding which HMI software works with which panel hardware is always a compatibility question, never a preference or a version-number guess.
Getting ComText or ProTool the legitimate way #
Both tools come from Siemens — today through Siemens Industry Online Support and its authorized distributors — with the panel's full designation and firmware version in hand. ComText is no longer sold and ProTool is no longer supported, but age does not move either into the public domain: a copy from a colleague or a file-sharing site is unlicensed software with no provenance and no version history. A registered support request for a discontinued tool is the documented route, and it is also how you obtain the matching tool version, which matters in the verification step below. Record the tool name and version with the recovery files so the next engineer does not repeat the search.
The host computer is part of the tool #
ComText is a DOS-era program. The documented working environments are DOS and Windows 95/98: under Windows 95/98, editing may run in a DOS window while the upload and download steps can require restarting the computer into DOS mode. Windows NT is not an established route for it. The tool addresses a physical serial port directly — DOS sees COM1 and COM2 as real UARTs, so a USB-to-serial adapter is invisible to it. The decision: an old laptop with DOS or Windows 98 and a genuine COM port does the whole job.
ProTool belongs to the 32-bit Windows era. Editing a project on a modern machine is one thing; getting the transfer to run on 64-bit Windows is a documented, unresolved problem on Siemens forums. Do the transfer from a 32-bit Windows host, then copy the project file to your everyday machine for archiving.
Upload checklist for the OP15 #
- Record the nameplate designation, the firmware version and the tool you will use, before connecting anything.
- Stop the machine and tell the operator the panel will leave its normal display during the transfer.
- Find and preserve every existing project copy on old engineering computers and archived media; work on copies, never on originals.
- Connect the serial cable the tool's documentation names, on the physical COM port, with the documented interface settings.
- Put the panel into its transfer state as its manual describes, then run the upload from the tool.
- Save the raw uploaded file untouched, with the date, the panel designation and the tool version noted beside it.
Verify the recovered project before you trust it #
Two documented failure modes catch OP15 recoveries after a seemingly successful transfer. First, an OP15C application uploaded through ComText can download back to the panel yet lose much of its function-key operation, so treat the recovered application as unverified until a restore reproduces the original display and key behavior. Second, the uploaded file may refuse to open at all when the ComText version that made the upload differs from the one trying to open it; keep the raw file and fetch the matching version rather than re-uploading. The details are in why an OP15C uploaded file will not open in ComText.
Test any restore on a bench panel or with the machine locked out: a recovered project can change what the panel's keys command, and the machine will obey.
Converting and replacing afterward #
ComText projects move forward through the Siemens Konvert utility, which converts OP5, OP15, TD10 and TD20 projects to ProTool and opens targets such as the OP17 and OP77B. Konvert was documented as German-language only, so budget time for translation if your team works in English. Convert a copy, and expect to tidy screens and key assignments afterward rather than a one-to-one result — the same discipline as reading an old HMI program before panel replacement.
When the panel itself is no longer worth repairing, the recovered application becomes the specification for its successor, and planning an HMI terminal replacement from an older operator panel is the next step; many shops take that moment to move to industrial panel PCs running PC-based HMI software.
Questions asked
Can ProSave upload an editable OP15 project?
No. ProSave writes a backup image that restores to the same kind of panel; it is not a project source file. The OP15 is not on ProSave's supported-device list, so treat any ProSave image as an extra copy taken alongside the real upload, never as the recovery itself.
How do I tell which OP15 generation I have when the enclosures look identical?
Ignore the enclosure, because both generations share it. Read the full designation on the nameplate, then the firmware version: below 2.2 is first generation and ComText territory, 2.2 or later is second generation and ProTool territory. If the sticker is unreadable, Siemens support can confirm the generation from the designation and serial number.
The uploaded file will not open in ComText. Is the upload bad?
Not necessarily. A common cause is a version mismatch: the ComText build that made the upload differs from the one trying to open it. Keep the raw file untouched, record which version uploaded it, and obtain that matching version through Siemens support before re-uploading anything to the panel.
Will ComText run on a current 64-bit Windows PC?
Not natively. It is a DOS-era tool that talks to physical COM1 and COM2 ports, so a USB-to-serial adapter is invisible to it, and 64-bit Windows has no DOS layer at all. Use a period host, such as an old laptop running DOS or Windows 98 with a real serial port, for both editing and transfer.
Which newer panel accepts a recovered ComText project?
Siemens provided the Konvert utility to convert OP5, OP15, TD10 and TD20 projects to ProTool, which opens targets such as the OP17 and OP77B. Konvert was documented as German-language only. Convert a copy, never the only original, and expect to tidy screens and key assignments after the conversion rather than getting a one-to-one result.