OP77B PSR Backup File: Restoring and Migrating Siemens HMI

David Krause21 min read
HMI / SCADASiemensTroubleshooting
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

Overview: The PSR File and OP77B Mismatch

The Siemens SIMATIC OP77B is a compact 4-inch text/graphic HMI panel from the legacy OP7x series, designed primarily for S7-200 and S7-300/400 PLC integration via PPI, MPI, and PROFIBUS DP. The panel is a direct successor to the OP7, OP17, and OP27 text-based panels and re-uses much of the same screen architecture while adding 4-bit grayscale graphics and an expanded tag database.

When a field engineer receives a backup file with a .psr extension (typically 200 KB to 2 MB depending on project complexity) and attempts to use it on an OP77B, the file will not open, the restore will fail, and the configuration software (ProTool or WinCC Flexible) will reject the file with format errors or device-type mismatches. The .psr extension is the backup file format used by older Siemens text-based HMI panels (OP3, OP5, OP7, OP15, OP17, OP25, OP27, OP35, OP37) and the corresponding first-generation graphic panels. The OP77B uses the .psb backup format and is configured with WinCC Flexible (2004 SP3 and later) or ProTool/Pro V6.0 SP3. There is no direct converter from .psr to .psb, and a .psr backup cannot be re-flashed onto an OP77B because the runtime firmware, screen architecture, and tag database of the older OP series are not byte-compatible with the OP77B firmware.

This article documents the diagnostic workflow for a .psr-on-OP77B scenario, the correct ProSave procedure for OP77B backup and restore, the migration path from the older OP panel family, and the recovery options when only a .psr backup exists without the original editable project file.

Key takeaway: A .psr file is a runtime image, not a project. To recover an editable project, the original .pdb (ProTool) or .hmi (WinCC Flexible) source file must be located. If only the .psr exists, the panel must be identified and re-flashed to a compatible legacy OP, or the project must be rebuilt from screen captures and PLC documentation.

Siemens HMI Backup File Extension Reference

The Siemens SIMATIC HMI product line uses several distinct backup file extensions, each tied to a specific panel family and configuration tool. Mixing extensions across families is the most common cause of "cannot open file" errors in the field.

Siemens HMI backup and project file extensions by panel family
Extension Format Panel Family Configuration Software
.psr Compressed binary runtime backup OP3, OP5, OP7, OP15, OP15C, OP17, OP25, OP27, OP35, OP37 (text/early graphic) ProTool V2.x–V5.x + ProSave
.psb Compressed binary runtime backup OP77A, OP77B, TP170A/B, TP177A/B, OP170B, TP270, MP270, MP370, C7-635/636 ProTool V6.0 SP3 or WinCC Flexible 2004+
.pdb / .pdl Editable source project All panels configured with ProTool ProTool / ProTool/Pro
.hmi Editable source project (compressed) All panels configured with WinCC Flexible WinCC Flexible 2004 / 2007 / 2008 SP3
.zap15 / .zap16 / .zap17 / .zap18 Compressed TIA Portal archive Comfort Panels, Basic Panels (KTP), Unified Comfort Panels TIA Portal V13+
.ard AutoText runtime data export Slate / Text panels ProSave (Export/Import)
.csv Recipe data export Most panels WinCC Flexible Recipe view
.rtf / .txt Alarm log export Most panels WinCC Flexible / ProSave

The crucial distinction is that .psr and .psb are not interchangeable. ProSave checks the device type embedded in the backup header and refuses to write a .psr image to an OP77B even if the file is renamed to .psb, because the internal structure (recipe database layout, alarm buffer, screen ID space, tag address map) differs between the older OP firmware and the OP77B firmware. The OP77B catalog number, the panel's firmware version, and the configuration tool's project version must all align for a restore to succeed.

Why PSR Files Don't Open in ProTool or WinCC Flexible

ProTool and WinCC Flexible expect editable project files (.pdb/.pdl or .hmi), not compiled runtime backups. The .psr file is the result of compiling a project with ProTool and downloading it to the panel; it contains the runtime image, recipe data, and password database, but it does not contain the editable screen definitions, script logic, or tag database in a recoverable form for the OP77B configuration software.

When a user attempts to open a .psr backup in ProTool, the application reports that the file is not a valid project ("The selected file is not a ProTool project"). In WinCC Flexible, the project wizard will not recognize the .psr as a project file ("Unknown file format"), and ProSave (when pointed at a .psr file with the OP77B selected as the target) will fail with an error such as Backup file is invalid for selected device or Firmware version mismatch.

Even with the older OP series that produced the .psr file, the file cannot be "opened" and edited in ProTool; it can only be restored to a panel of the matching type. To recover the editable project from a .psr, the original .pdb or .hmi source must be located, or a partial upload must be attempted from a compatible panel that has been re-flashed with the .psr.

Field note: A common misconception is that a .psr file is "encrypted" or "protected." It is neither—it is simply a compiled binary image that the configuration tool cannot parse as a project. The protection is in the file format, not in the data.

Identifying the Source Panel of an Unknown PSR File

When a .psr file is delivered without documentation, the source panel can be identified through a structured diagnostic sequence. The following procedure requires ProSave and a compatible panel from the legacy OP family (or the suspected source panel if available).

  1. Inspect the file header. Open the .psr in a hex editor (HxD, 010 Editor, or similar). ProTool backups embed a header structure that includes the device type, firmware version, project ID, and compile timestamp. The first several bytes typically contain an ASCII identifier string followed by binary length and version fields. Document the offset positions of these strings for reference.
  2. Document the file metadata. Record the file size, the embedded compile date (if visible in the header), and any text strings found in the header (project name, panel name, language code). A 536 KB .psr is consistent with a moderate text-only project on OP7, OP17, or OP27. Projects with embedded graphics typically exceed 1 MB; pure text projects with extensive recipe and alarm databases may reach 2 MB.
  3. Compare against known panel firmware images. If a Siemens firmware image (.img) for the suspected source panel is available, the header offsets can be cross-referenced. Siemens publishes firmware images on the SIMATIC Customer Support portal under "HMI Operator Panels" → "Updates and Utilities."
  4. Attempt a restore on a compatible panel. If any panel from the OP3/OP5/OP7/OP15/OP17/OP25/OP27/OP35/OP37 family is available, connect via RS232 and run a ProSave restore. A successful restore confirms the source panel family and recovers the runtime behavior for screen-level inspection. If the restore fails with "Backup file is invalid for selected device", try a different family member.
  5. Upload from the restored panel. Once the .psr is restored to a compatible panel, use ProTool's Upload Station function (not a backup) to retrieve the editable project. Note: upload from a text-based OP typically recovers screens, tags, and text tables, but custom graphics and complex scripts may not be fully reconstructible. The recovered .pdb may be incomplete and require manual cleanup before it can be re-deployed.
Backup file received Identify extension .psr Legacy OP panel (OP3–OP37) .psb Modern panel (OP77x, TP, MP) .hmi / .pdb Editable source project file Restore to legacy OP Then upload via ProTool to recover .pdb OR rebuild from scratch ProSave restore to OP77B Verify device model and firmware match Confirm checksum Open in WinCC Flex / TIA Edit and recompile Transfer via ProSave or download from IDE Verify on panel: screen render, tag poll, alarms, recipes Document firmware version, project version, and PLC connection for each successful transfer

Figure 1: Decision flow for incoming Siemens HMI backup files

Note: The exact device type ID and header layout for .psr backups are documented in the legacy ProTool/ProSave developer notes. Confirm the current header structure against the relevant Siemens Knowledge Base entry on the SIMATIC Customer Support portal before relying on byte-level inspection for production recovery. Do not assume the file is corrupt or unreadable just because a hex inspector shows non-ASCII data—the entire backup is a structured binary image, not a text file.

Restoring an OP77B: The Correct PSB Backup Procedure with ProSave

ProSave is the dedicated Siemens utility for OS update, backup, restore, and transfer of SIMATIC HMI panels. It ships as part of the SIMATIC HMI Toolset, WinCC Flexible, or TIA Portal (under the "ProSave" entry in the installation tree, accessible directly or via the WinCC Flexible Panel > Backup/Restore menu). For the OP77B, the relevant ProSave operations are:

  • Backup (read): Reads the panel's runtime image, recipes, alarm buffer, and password table; writes them to a .psb file on the engineering PC.
  • Restore (write): Writes a .psb file from the PC to the panel, overwriting the existing runtime image and on-panel data. The panel reboots into the restored project.
  • OS Update: Updates the panel's operating system firmware from a .img file. Used to recover a panel with a corrupted or out-of-date firmware image.
  • Transfer (PN/MPI): Used during initial commissioning to push the compiled project from WinCC Flexible / TIA Portal to the panel via MPI/PPI/PROFIBUS.

ProSave enforces strict type-checking: a .psb file generated from an OP77A, TP170A, or any other panel model will be rejected when restored onto an OP77B, even if the firmware versions match. The catalog number of the panel, the firmware version, and the configuration tool's project version must all align. A typical mismatch error is "Wrong device type" / "Falscher Gerätetyp" displayed in the ProSave status bar.

Step-by-Step ProSave Backup of an OP77B

  1. Connect the engineering PC to the OP77B. Use a Siemens RS232 PPI/MPI cable (6ES7 901-3CB30-0XA0) for serial connection, or the optional Ethernet/MPI adapter if the panel is fitted with the IF1B Ethernet module. For modern PCs without a built-in RS232 port, use a USB-to-serial adapter based on the FTDI FT232 chipset (verified compatible); ProSave and WinCC Flexible transfer have been validated with FTDI-based adapters on Windows 10 and Windows 11.
  2. Set the OP77B transfer mode. On the panel, navigate to Start > Settings > Transfer (or, on early firmware, hold the lower-left function key during startup). Enable transfer mode and note the MPI/PPI address (default 1) and baud rate (default 187.5 kbps for MPI, 9.6 kbps or 19.2 kbps for PPI). The panel displays "Transfer" in the status bar when ready.
  3. Launch ProSave from Start > SIMATIC > ProSave (or from within WinCC Flexible under Panel > Backup/Restore). On TIA Portal installations, the path is Start > Siemens Automation > ProSave.
  4. Configure the device type and connection. In ProSave, select General > OP77B as the device type. Select the connection type (Serial / MPI / PPI / Ethernet) to match the cable in use. Set the PC interface (COM1 / COM2 / COMx for USB adapters), baud rate, and station address to match the panel. For Ethernet connections, enter the panel's IP address and subnet mask.
  5. Select the Backup tab. Enter the destination path and filename (e.g., C:\HMIBackup\OP77B_Project_20240115.psb). Enable the option to include recipes and alarm logs if required.
  6. Click "Backup". ProSave negotiates with the panel, reads the runtime image, and writes the .psb file. A typical 512 KB–2 MB project takes 30–180 seconds at 187.5 kbps. At 9.6 kbps (PPI), the same transfer may take 5–10 minutes.
  7. Verify the backup. ProSave displays a success message with a checksum. Store the .psb file in a versioned backup repository with a dated filename. Cross-check the file size against the project size in WinCC Flexible's project properties for sanity.

Step-by-Step ProSave Restore of an OP77B from a PSB File

  1. Connect and configure ProSave as in the backup procedure (steps 1–4 above). Confirm the target panel is in transfer mode and reachable.
  2. Select the Restore tab in ProSave.
  3. Browse to the .psb file and select it. ProSave reads the backup header and displays the source panel model, firmware version, and project version.
  4. Confirm that ProSave's reported device type, firmware version, and project version match the target panel. If there is a mismatch, ProSave will warn before proceeding. Do not override the warning unless you are intentionally downgrading or cross-loading.
  5. Click Restore. The panel reboots, accepts the new runtime image, and restarts with the restored project. The transfer takes 30–300 seconds depending on the connection speed and project size.
  6. After restart, verify screen rendering, tag polling, alarm buffer, recipe data, and any password-protected areas. Cycle the panel power once after a successful restore to ensure the runtime image is committed to flash.
Caution: A restore wipes the panel's runtime image and any data stored on the panel (recipes, alarm logs, password table). Always back up the current state to a separate .psb before restoring, unless the current state is intentionally being replaced. A failed or interrupted restore can leave the panel in a non-bootable state, requiring an OS update via ProSave to recover.

Cable, Connection, and Communication Parameters

OP77B communication interfaces and cable requirements
Interface Connector Cable / Adapter Baud Rate Use Case
RS232 (IF1) 9-pin Sub-D male 6ES7 901-3CB30-0XA0 (PC/PPI cable) or standard RS232 null-modem (pins 2-3 crossed, 4-5-6-20-8 bridged) 9.6 / 19.2 / 187.5 kbps Configuration transfer, ProSave backup/restore, OS update, recipe/alarm export
MPI (IF2) 9-pin Sub-D female PROFIBUS DP cable with D-sub connectors, bus terminator enabled at end nodes 187.5 kbps S7-300/400 communication, multi-drop networking, panel-to-panel peer communication
PROFIBUS DP slave (IF2) 9-pin Sub-D female PROFIBUS DP cable with D-sub connectors, bus terminator enabled at end nodes Up to 1.5 Mbps (DP) S7-300/400 high-speed PLC communication, integration as a DP slave
PPI (IF2) 9-pin Sub-D female Siemens PPI cable or S7-200 PC/PPI cable (6ES7 901-3CB30-0XA0) 9.6 / 19.2 kbps S7-200 PLC communication, point-to-point configuration, single-master networks
Ethernet (optional IF1B) RJ45 Standard Cat5e/Cat6 patch cable 10/100 Mbps ProSave over TCP/IP, WinCC Flexible transfer, S7-300/400 Ethernet communication

For ProSave operations, the most reliable connection is the IF1 RS232 port with a Siemens PC/PPI cable (6ES7 901-3CB30-0XA0). The cable's DIP switches must be set to the correct PPI/MPI mode, and the baud rate must be selected on both the cable and the panel. The cable's default MPI address is 0, but this can be reconfigured in the cable's setup utility.

Modern PCs (2015 and later) typically lack a built-in RS232 port. Two options for connecting to the OP77B:

  • USB-to-serial adapter (FTDI chipset): The most reliable option. Verify the adapter uses the FTDI FT232 or FT231X chipset. Prolific PL2303-based adapters have known compatibility issues with ProSave on Windows 10/11 and may require legacy driver versions.
  • Siemens USB PC/PPI cable (6ES7 901-3DB30-0XA0): The newer USB variant of the PC/PPI cable, designed for modern PCs. This is the recommended cable for new deployments.
Field note: Many "transfer failed at 0%" errors are caused by virtual COM port issues. Verify the COM port number in Windows Device Manager and match it exactly in ProSave. If the COM port is higher than COM16, manually reassign to a lower COM number using the USB Serial Port (COMx) Properties > Advanced > COM Port Number dialog.

Migration Path from Older OP Panels to OP77B

If the source panel is one of the older text-based OPs (OP3, OP5, OP7, OP15, OP17, OP25, OP27, OP35, OP37) and the OP77B is intended as a replacement, the migration is a rebuild, not a restore. The screen architecture differs (text-mode 4×20 vs. 160×48 / 240×64 pixel graphics), the tag database structure differs, and the variable addressing may need re-mapping to match the new PLC connection.

Recommended migration workflow:

  1. Locate the original ProTool project (.pdb or .pdl). If unavailable, restore the .psr to a compatible OP panel and attempt a ProTool upload to extract a partial .pdb (text screens and tags only).
  2. Inventory the screens, tags, alarms, and recipes from the original project. Document PLC addresses, message texts, language tables, and navigation structure. Photograph the screens of the running panel for visual reference.
  3. Open a new WinCC Flexible project targeting the OP77B. Use the OP77B device template in the WinCC Flexible project wizard. The catalog number for the OP77B monochrome is 6AV6641-0BA11-0AX0; for the color variant OP77B Color, the catalog number is 6AV6641-0CA11-0AX0.
  4. Recreate screens in the WinCC Flexible editor, using the OP77B's pixel-based graphics rather than the text-mode screens from the legacy OP. Re-use texts, message classes, and tag names where possible. Use the OP77B's native font (Tahoma 14/18/26 pt) for consistency.
  5. Reconnect tags to the new PLC connection (PPI, MPI, or PROFIBUS). The tag names from the ProTool project can be preserved, but the data types and addresses must be re-validated against the current PLC program. Note that ProTool used 16-bit tag addressing; WinCC Flexible supports 32-bit and pointer-based addressing.
  6. Recompile and transfer the new project to the OP77B via WinCC Flexible (Compile > Rebuild All > Transfer) or ProSave.
  7. Commission and verify on-site: cycle power, validate screen navigation, force-tag test, alarm acknowledgment, recipe read/write, and password-protected area access. Document any deviations from the original project for the end-user's records.
Field note: In practice, the rebuild is almost always faster than attempting to decompile or convert a .psr backup. Treat the .psr as a reference for screen content, not as a source for the new project. A typical 50-screen OP7/OP17 project can be rebuilt in WinCC Flexible for the OP77B in 2–4 days for a single engineer, depending on graphics complexity and PLC tag mapping.

Configuration Software: ProTool, WinCC Flexible, TIA Portal

OP77B configuration tool compatibility matrix
Configuration Software Version Status Project File Extension Notes
ProTool/Pro V6.0 SP3 Legacy / Discontinued .pdb / .pdl Required for early OP77B firmware (V1.x). End-of-life since 2014. No Windows 10/11 support.
WinCC Flexible 2004 / 2007 / 2008 SP3 Legacy / Maintenance .hmi Recommended for new and migration projects on OP77B. Compatible with OP77B firmware ≥ V2.x. Windows 7/10 compatibility available with WinCC Flexible 2008 SP3 + Hotfix 14.
TIA Portal V13 SP1 / V14 / V15.1 / V16 Current (for migration only) .zap15 / .zap16 OP77B is not a native TIA Portal device. Use "Migrate WinCC Flexible project" to import a .hmi file, then transfer via ProSave or TIA Portal download.
TIA Portal V17 / V18 / V19 Current .zap17 / .zap18 OP77B migration still works. New development should target KTP400 Basic (6AV6647-0AA11-3AX0) instead.

Siemens' current recommendation for new installations is the SIMATIC KTP400 Basic, which is fully supported in TIA Portal as a native device. The OP77B is a maintenance-only product as of 2017; new development should not be started on the OP77B platform. For existing OP77B installations, the recommended support path is:

  1. Maintain a WinCC Flexible 2008 SP3 installation on a Windows 10 engineering PC for project editing.
  2. Use ProSave (bundled with WinCC Flexible or TIA Portal) for backup, restore, and OS update operations.
  3. Archive the editable .hmi project file in versioned storage (Git, SVN, or a structured backup repository).
  4. For TIA Portal integration (e.g., if the PLC is on TIA Portal), use the "Migrate WinCC Flexible project" function to import the .hmi file, then transfer to the OP77B via ProSave. TIA Portal does not have a native device profile for the OP77B.

Refer to the SIMATIC Customer Support portal for the latest OP77B operating instructions, firmware images, and Knowledge Base entries on WinCC Flexible compatibility with Windows 10/11.

OP77B Hardware Reference

OP77B key technical specifications
Parameter Value
Display 4-inch STN LCD, monochrome (OP77B) or color (OP77B Color)
Resolution 160 × 48 pixels (monochrome) / 240 × 64 pixels (color)
Function keys 8 (F1–F8) + system keys (cursor, enter, escape, help)
Tag limit 256 internal / 256 external tags (with WinCC Flexible)
Alarm buffer 512 alarm events (circular buffer)
Recipe memory 32 recipes, 32 entries each (typical)
User memory 768 KB (flash) for project + runtime
Communication interfaces 1× RS232 (IF1), 1× RS422/RS485 (IF2 for MPI/PPI/DP)
Power supply 24 V DC, ±20% (19.2–28.8 V), typical 0.2 A
Operating temperature 0 °C to +50 °C (front); 0 °C to +45 °C (rear)
Protection class IP65 (front), IP20 (rear)
Catalog number (mono) 6AV6641-0BA11-0AX0
Catalog number (color) 6AV6641-0CA11-0AX0
Dimensions (W × H × D) 150 × 80 × 38 mm (cutout: 138 × 68 mm)

Specifications are derived from the standard Siemens OP77B datasheet. Confirm against the official Siemens product documentation on the SIMATIC Customer Support portal before specifying for new projects.

Troubleshooting Matrix

Common OP77B / ProTool / PSR file errors and remedies
Symptom Root Cause Diagnostic Remedy
ProTool reports "Unknown file format" on .psr File is a runtime backup, not an editable project Check file extension; inspect header Locate the original .pdb/.pdl or rebuild the project in WinCC Flexible
WinCC Flexible will not import .psr WinCC Flexible expects .hmi source files Try the "Migrate project" wizard (TIA Portal) Locate the original .hmi source file or rebuild from scratch
ProSave "Backup file is invalid for selected device" on .psb Mismatched panel model in backup header Compare catalog number and firmware in ProSave message Use a .psb from the exact same panel model; do not cross-load between OP77A and OP77B
ProSave restore fails at 0% / connection timeout Cable issue, wrong baud rate, transfer mode not enabled Verify transfer mode, COM port, baud rate on both ends Enable transfer on panel, swap cable, set PC COM to 187.5 kbps (MPI) or 9.6/19.2 kbps (PPI); re-seat connectors
Panel shows "Transfer aborted" mid-restore Power loss, broken cable, incorrect firmware image Check power supply voltage, cable integrity, event log Re-establish stable 24 V supply, retry transfer; if firmware is corrupted, perform OS update via ProSave before retrying
Panel boots with "Wrong CF card" / "No project" Empty or corrupt runtime image Inspect panel boot messages Re-transfer the .psb from a known-good backup; if no backup exists, perform OS update + transfer from WinCC Flexible
Project uploads with scrambled texts on OP77B Restore from a different region's text table or language pack mismatch Compare project language and character set Re-create project in correct language, or update panel's font tables via ProSave OS update
ProSave reports "Falscher Gerätetyp" (wrong device type) Target panel's catalog number does not match the backup header Compare panel catalog number against the source of the .psb Use the correct .psb for the target panel model; do not rename extensions
Transfer completes but panel does not boot to project Firmware version mismatch; backup was created on a different firmware version Compare panel firmware version with ProSave's reported backup version Perform OS update to match the backup's expected firmware, then re-transfer the .psb
"Backup file size is too large" error Project exceeds the panel's user memory (768 KB) Check project size in WinCC Flexible project properties Reduce project size: remove unused tags, simplify graphics, archive old alarms/recipes; consider migration to a larger panel (KTP700/1000)
ProSave does not detect USB-to-serial adapter Incompatible chipset or driver issue Check Windows Device Manager; verify COM port number Use FTDI-based adapter with current driver; reassign COM port to a low number (COM1–COM8); restart ProSave as administrator

Frequently Asked Questions

What is a .psr file and why won't it open in ProTool or WinCC Flexible?

A .psr file is a compiled runtime backup from legacy Siemens text-based HMI panels (OP3, OP5, OP7, OP15, OP17, OP25, OP27, OP35, OP37). It cannot be opened as an editable project in ProTool or WinCC Flexible because those tools expect source project files (.pdb/.pdl or .hmi). The .psr can only be restored to a compatible panel of the original family.

Can a .psr file be renamed to .psb and restored onto an OP77B?

No. Renaming the extension does not change the internal structure. The OP77B's ProSave will reject the file because the device type and firmware version embedded in the backup header do not match. The OP77B requires a .psb backup generated from an OP77B-compatible source. Use the ProTool/ProSave source-panel identification procedure to determine the source panel of the .psr, then restore the .psr to a compatible legacy OP panel.

How do I back up an OP77B project?

Connect the engineering PC to the OP77B's IF1 RS232 port using a Siemens PC/PPI cable (6ES7 901-3CB30-0XA0) or a USB PC/PPI cable (6ES7 901-3DB30-0XA0), enable transfer mode on the panel, launch ProSave, select OP77B as the device type, and run the Backup operation to a .psb file on the PC. The typical transfer time for a 1–2 MB project is 30–180 seconds at 187.5 kbps over MPI, or 5–10 minutes at 9.6 kbps over PPI.

I only have a .psr file. Can I recover the original OP77B-compatible project?

Not directly. The .psr is a compiled runtime image with no editable source. Options: (1) locate the original .pdb/.pdl/.hmi source file, (2) restore the .psr to a compatible legacy OP panel and attempt a ProTool upload to extract a partial .pdb (text screens and tags only), or (3) rebuild the project from scratch using screen captures, tag documentation, and PLC address lists. Option 3 is the most common path in field service.

Which software is recommended for new OP77B projects today?

For maintenance of existing OP77B installations, use WinCC Flexible 2008 SP3 with Hotfix 14 on Windows 10. For new installations, Siemens recommends migrating to the SIMATIC KTP400 Basic (6AV6647-0AA11-3AX0), which is fully supported in TIA Portal V17/V18/V19 as a native device. The OP77B is in maintenance phase and is no longer recommended for new development; TIA Portal does not include a native device profile for the OP77B, so any new TIA Portal-based project would require migration of a WinCC Flexible .hmi file.

Back to blog