Overview of MP370 Program Transfer Methods
The SIMATIC MP370 is a 12-inch or 15-inch operator panel from the Multi Panel family, historically programmed with Siemens ProTool/Pro (Configuration System, CS) or WinCC flexible 2004 for non-TIA Portal installations. MP370 panels integrate with SIMATIC S7-300 and S7-400 controllers via MPI, PROFIBUS, or Industrial Ethernet and support on-board project storage on PC flash memory cards (CF/PCMCIA-style). Three primary transfer paths exist for moving compiled runtime projects (.fwd/.pdz archives) between the configuration PC and the panel:
- Serial / MPI / PROFIBUS / Ethernet transfer through ProTool Pro or ProSave (live online to a running panel).
- External PC flash memory card swap: extract the card, edit the project offline, write back, insert into the panel.
- Backup/Restore via the panel's Service menu using a PC memory card, then subsequent offline editing of the backup file.
The three paths are not equivalent. Method 1 is the only path that produces a fully re-editable *.pdb source project in ProTool Pro, and it requires the original *_Start.pdb project to have been downloaded with the Enable Upload to Configuration PC option. Method 2 is the only practical method when the panel is decommissioned, password-locked, or the original project is lost. Method 3 is a derivative of Method 2 and is the procedure Siemens documents for in-field panel replacement.
*.fwd) cannot be opened or edited in ProTool Pro. It is a compiled, protected binary. If the field report *.pdb is missing, the only editable recovery path is the memory-card backup file *.pdz or *.arj, which still contains a compiled project, not source. This distinction is the root cause of most "upload failed" cases on MP370 panels.Prerequisites
| Component | Requirement |
|---|---|
| Configuration PC | Windows XP SP3 / Windows 7 (32-bit) with ProTool/Pro CS V6.0 SP3 or WinCC flexible 2004 SP5 |
| HMI software | ProTool/Pro CS V6.0 or higher with same firmware target as the panel |
| Transfer utility | ProSave V9.0 (bundled inside STEP 7 V5.5) or ProSave from ProTool CD |
| Cable | RS-232 null-modem (6ES7 901-1BF00-0XA0) for serial; MPI cable (6ES7 901-0BF00-0XA0) for MPI/PROFIBUS; crossed Ethernet cable for TCP/IP transfer |
| Memory card | PC flash card 8 MB / 16 MB / 32 MB, FAT16 formatted, supported by MP370 backplane slot |
| PLC integration | STEP 7 V5.4 or V5.5 with the MP370 configured as an HMI station inside the S7 project |
| Authorizations | ProTool Pro license dongle or hardlock; ProSave license (often free with STEP 7) |
Verify the panel's firmware and ProTool/Pro target version before any transfer. A mismatch between the panel's ProTool RT version and the project's target version is the most common reason for download rejection (error 0x8004... in the transfer log). Use the panel's Start Center → System → Version menu to read the ProTool Runtime build.
Understanding the MP370 Project Files
ProTool/Pro differentiates three artifact types, and confusing them is the source of most field problems:
| Extension | Role | Editable? | Produced by |
|---|---|---|---|
*.pdb |
ProTool source database, contains all screens, tags, alarms, scripts | Yes (in ProTool Pro) | ProTool Pro CS |
*.fwd |
Compiled runtime file, downloaded to the panel | No | Compiler output of *.pdb
|
*.pdz |
Compressed backup/restore archive of the runtime (sometimes with sources) | No (extract only) | ProSave backup or panel Service menu backup |
*.arj |
Older ARJ-compressed backup, MP370 pre-V6 era | No (extract only) | ProSave legacy |
When the user reports "I have the project but I am not sure whether it is the same exactly with the one in HMI," the correct check is to use ProTool Pro's Project → Compare function, or to compile the local *.pdb and compare its CRC with the CRC of the runtime file currently loaded on the panel (read from the panel Service menu: System → Information → Project CRC).
Method 1: Online Transfer (Upload/Download) over MPI/PROFIBUS/Ethernet
Step 1 - Establish the connection in ProTool Pro
- Open the integrated STEP 7 / ProTool project (
*.s7pS7 project that contains the MP370 station). - Right-click the MP370 station → Open Object. ProTool Pro launches with the HMI project loaded.
- From the ProTool Pro menu, select File → Download → Selection. The "Select Target System" dialog lists the configured connection type (MPI, PROFIBUS, Ethernet).
Step 2 - Configure transfer parameters
| Parameter | Typical value for S7-400 + MP370 |
|---|---|
| HMI station address | 1 (default for MP370) |
| PLC station address | 2 (default for S7-400 CPU 4xx) |
| Network profile | 187.5 kbit/s MPI, or PROFIBUS DP, or TCP/IP |
| Slot | 0 (for Ethernet) or auto-detect (MPI/DP) |
| Enable Upload to Configuration PC | Must be checked to allow reverse upload |
*.fwd runtime. Without it, the panel can be downloaded to, but a subsequent upload will return only the compiled *.fwd, which ProTool Pro will refuse to open as a project. Always re-check this option before any download intended to be reversible.Step 3 - Download to panel
- Click OK. ProTool Pro compiles the source
*.pdbinto a*.fwdfile. - The transfer progress dialog reports the number of bytes sent. Typical MP370 12" project (300-500 screens, 2000 tags) transfers in 3-8 minutes over Ethernet, 8-20 minutes over MPI at 187.5 kbit/s.
- If the panel prompts Transfer, press the Transfer button on the touch screen within 10 seconds, or the request times out.
- Wait for the panel to reboot into the new project. The transfer dialog closes with a success message.
Step 4 - Upload from panel (reverse direction)
- Place the panel in Transfer mode (Start Center → Transfer button).
- In ProTool Pro, select File → Upload → Selection.
- Choose the same connection profile used for download.
- Click Upload. ProTool Pro will read back either a full
*.pdb(if "Enable Upload" was used at download time) or only a*.fwd(if it was not).
*.fwd and ProTool Pro reports "Upload not possible - no editable project data on the target system", the only practical recovery is to use the PC flash memory card backup (Method 2) and edit the message text via the ProTool Pro offline editor of the extracted *.pdz, or to revert to the original *.pdb from the engineering archive.Method 2: PC Flash Memory Card Backup and Restore
This is the path that matches the original question: editing an alarm message on the memory card offline, then putting the card back. The procedure is fully documented in the SIMATIC WinAC MP for MP370 manual (PDF) and in the ProTool Pro online help under Backup/Restore via external storage medium.
Step A - Create a backup from the panel
- Power down the MP370.
- Insert a PC flash memory card (8 MB minimum, 16/32 MB recommended) into the slot on the rear of the panel, label side up.
- Power on the panel. From the Start Center, navigate to Service → Backup/Restore.
- Select Backup to Memory Card. The panel writes a
BACKUP.PDZ(orBACKUP.ARJon older firmware) archive containing the current runtime, all recipes, and the language database. - Wait for the progress bar to complete (typically 1-3 minutes for a 16 MB card).
- Power down and remove the card.
Step B - Edit the backup file offline
- Insert the card into a PC card reader.
- Copy
BACKUP.PDZto a working folder. - Open ProTool Pro on the configuration PC. From the File → Restore menu, select the
BACKUP.PDZand restore it to a temporary directory. The restore extracts a*.fwdplus optional source fragments. - To edit alarm messages, you need the source
*.pdb. If the original*.pdbis available, open it directly in ProTool Pro and skip the restore step. - Modify the alarm text under Messages → Discrete Alarms or Messages → Analog Alarms.
- Recompile the project: File → Compile → All. This regenerates the
*.fwd.
Step C - Write the project back to the memory card
- From ProTool Pro, select File → Download → Memory Card (or Transfer → Memory Card in older builds).
- Choose the PC flash card target. ProTool Pro writes a complete project directory including
*.fwd, firmware stub, recipe templates, and any language files. - Safely eject the card from the PC.
Step D - Restore on the panel
- Power down the MP370 and insert the freshly written card.
- Power on. The panel detects the project on the card and offers Restore from Memory Card during boot, or you can use the Service → Backup/Restore → Restore from Memory Card menu.
- Confirm. The new project with the corrected alarm text becomes active after a brief restart (10-20 seconds).
*.pdb source must exist on the configuration PC; the memory card by itself only contains the compiled *.fwd, and the panel Service menu cannot edit text strings directly.Method 3: ProSave-Based Transfer (Standalone, no STEP 7 Integration)
ProSave is the lightweight transfer utility bundled on the ProTool/Pro CD and inside STEP 7 V5.x. It supports the same connection types (RS-232, MPI, PROFIBUS, Ethernet) but does not require a STEP 7 project. ProSave is ideal for service technicians who do not have the original S7 project but need to refresh the HMI runtime, install firmware, or change the panel's IP address.
Procedure
- Launch ProSave (default path:
C:\Siemens\ProSave\ProSave.exe). - Select device type: MP370.
- Select connection: Serial / MPI / PROFIBUS / Ethernet (TCP/IP).
- Click File → Download and choose the
*.fwdor*.pdzarchive. - ProSave displays the transfer status and any panel-side prompts.
ProSave parameters for Ethernet
| Parameter | Value |
|---|---|
| IP address (panel) | e.g. 192.168.0.10 (set in Start Center → System → Network) |
| Subnet mask | 255.255.255.0 |
| Router (if any) | 192.168.0.1 |
| ProSave port | 102 (S7 / PROFINET default), or panel-specific transfer port 5000+ |
| Timeout | 60 s recommended for serial, 30 s for Ethernet |
WinAC MP Integration with S7-400
The MP370 is one of the few Siemens panels capable of hosting a WinAC MP (Windows Automation Center, Multi Panel) soft-PLC runtime. In this mode, the panel executes an S7-300-compatible CPU image in parallel with the HMI runtime, and the configuration requires the SIMATIC WinAC MP for MP370 installation manual (PDF) and the WinAC MP software CD.
For a panel with WinAC MP:
- Install WinAC MP on the configuration PC from the WinAC MP CD (separate from the ProTool/Pro CD).
- Use ProSave to transfer the WinAC MP firmware to the panel first.
- Use ProTool Pro to download the HMI project to the panel.
- Use STEP 7 to download the S7-300-compatible PLC program to the panel's WinAC MP slot.
When the S7-400 is the master and the MP370 is purely an HMI with WinAC MP disabled, the transfer sequence is just ProTool/Pro plus standard STEP 7 download. WinAC MP activation is signalled in the panel's Start Center → System → WinAC MP status page.
Project Comparison and Verification
To confirm whether the source *.pdb on the PC matches the runtime currently loaded on the panel, use one of these two methods:
Method A - CRC check
- Read the panel-side project CRC: Start Center → System → Information → Project Information. Note the 8-character hex CRC.
- Recompile the local
*.pdbin ProTool Pro. The compile log shows the resulting CRC of the*.fwd. - Compare. Equal CRCs prove identical content; different CRCs prove at least one byte differs.
Method B - Upload and diff
- Upload the project from the panel to the configuration PC (requires "Enable Upload" flag).
- Open both
*.pdbfiles in ProTool Pro side by side (two ProTool instances). - Use Project → Compare to generate a tag-, alarm-, and screen-level diff report.
*.pdb. Preserve these in the engineering archive before any overwrite.Changing an Alarm Message Offline (Direct Answer)
The fastest way to fix a single alarm string on an MP370 integrated with an S7-400:
- Locate the source
*.pdbinside the STEP 7 project (ProjectName\HMI\MP370\*.pdb). - Open it in ProTool Pro. Navigate to Messages → [Message Class] → [Alarm Number].
- Edit the alarm text, click Apply.
- Compile: File → Compile → All.
- Connect the PC to the MP370 (MPI/PROFIBUS/Ethernet).
- Set the panel to Transfer mode.
- In ProTool Pro: File → Download → Selection → check Enable Upload to Configuration PC → OK.
- Wait for the panel to restart with the new alarm text (typical 15-30 s).
If the configuration PC cannot be brought online with the panel (network unavailable, the S7-400 is locked out for production), use Method 2 (memory card) and rewrite the card offline, then swap it into the panel during a scheduled short stop.
Troubleshooting Matrix
| Symptom | Likely cause | Resolution |
|---|---|---|
| Download aborts with "Connection not established" | Wrong station address, mismatched baud rate, RS-232 null-modem missing | Verify cable, set panel MPI address to 1, S7-400 MPI address to 2, baud 187.5 kbit/s; use 6ES7 901-1BF00-0XA0 null-modem cable |
| Upload returns "No editable project data on the target system" | "Enable Upload to Configuration PC" was not set at original download | Re-download with the option enabled; otherwise fall back to memory-card backup or original *.pdb archive |
| Panel displays "Transfer not possible - wrong project version" | ProTool Pro target version newer or older than the panel's runtime | Match ProTool Pro target version to the panel's RT version (Start Center → System → Version); upgrade panel firmware or downgrade project target |
| Memory card not detected in panel | Card larger than 256 MB, wrong file system, or write-protect tab engaged | Use 8-32 MB card, FAT16 formatted; disable write-protect; clean contacts |
| Alarm text shows placeholder $... at runtime | Language file missing from *.fwd package |
In ProTool Pro, ensure all language columns are exported and the language database is included at compile time |
| STEP 7 project does not show the MP370 station | MP370 was added as a standalone ProTool project, not as an integrated HMI station | Insert the MP370 via SIMATIC Manager → Insert → Station → SIMATIC HMI Station and re-link |
| ProSave reports "Device type not supported" | ProSave version predates the MP370 device driver | Update to ProSave V9.0 or later; the MP370 device file is included in the STEP 7 V5.4+ ProSave bundle |
Firmware and Version Compatibility
| Panel ProTool RT version | Compatible ProTool Pro CS | ProSave minimum |
|---|---|---|
| V6.0 SP2 | ProTool/Pro V6.0 SP2 | ProSave V8.0 SP1 |
| V6.0 SP3 | ProTool/Pro V6.0 SP3 | ProSave V9.0 |
| V6.0 SP4 | ProTool/Pro V6.0 SP4 / WinCC flexible 2004 SP2 | ProSave V9.0 SP1 |
| V6.0 SP5 | WinCC flexible 2004 SP5 | ProSave V9.0 SP2 |
MP370 panels are not natively supported by TIA Portal; they sit in the classic ProTool/Pro / WinCC flexible 2004 generation. Migration to a TIA Portal-compatible successor (e.g., Comfort Panel TP900) requires a project migration in WinCC flexible 2008 or TIA Portal V13 SP1+ using the panel migration tool, which is outside the scope of MP370 service transfers.
Memory Card Specifications
| Attribute | Value |
|---|---|
| Card type | PC flash card (PCMCIA Type II) |
| Capacity supported | 8 MB / 16 MB / 32 MB; cards > 64 MB not guaranteed on early MP370 firmware |
| File system | FAT16 |
| Backup file extension |
BACKUP.PDZ (firmware ≥ V6.0 SP2) or BACKUP.ARJ (legacy) |
| Insertion direction | Label up, contact row into the panel slot first |
Step-by-Step Summary: Edit Alarm Text and Push to Panel
- Locate the integrated
*.pdbfor the MP370 inside the STEP 7 project. - Open in ProTool Pro, edit the alarm string, compile to
*.fwd. - Choose the transfer path: online (MPI/PROFIBUS/Ethernet) or offline (memory card).
- For online: set the panel to Transfer mode, click Download in ProTool Pro, ensure Enable Upload to Configuration PC is checked.
- For offline: write the compiled project to a PC flash card using ProTool Pro, then use the panel's Service → Restore from Memory Card menu.
- Verify the alarm text on screen and check the transfer log for Transfer successful plus correct CRC.
Can I just unplug the MP370 memory card, edit the message in ProTool, and put the card back?
Only if the source *.pdb is available on the configuration PC. The memory card contains a compiled *.fwd file that the panel Service menu cannot edit. Pull the card, edit the alarm text in the original *.pdb, recompile, write the project back to the card with ProTool Pro, and reinsert the card. The panel boots the new project from the card automatically.
Why does ProTool Pro refuse to open an uploaded project file?
Because the runtime *.fwd downloaded to the panel is a compiled, protected binary. The upload will only yield an editable *.pdb if the original download was performed with the Enable Upload to Configuration PC option checked. Without that flag, ProTool Pro displays "No editable project data on the target system" and only the compiled file is returned.
How can I tell whether the project on the configuration PC matches the one running on the panel?
Read the project CRC from the panel: Start Center → System → Information → Project Information. Recompile the local *.pdb in ProTool Pro and compare the CRC printed in the compile log. Equal CRCs prove bytewise identity; different CRCs indicate at least one change. For element-level differences (specific alarms, tags, screens), use ProTool Pro's Project → Compare after a successful upload.
What is the difference between ProTool/Pro and WinCC flexible 2004 for an MP370?
ProTool/Pro CS V6.0 is the original configuration tool for the MP370. From firmware V6.0 SP4 onwards, the panel can also be configured with WinCC flexible 2004 SP2 or higher. Both produce a compatible *.fwd, but the project metadata format is not 100% identical. For service work on a long-running system, keep using the tool that originally built the project to avoid tag-database recreation issues.
Do I need ProSave separately, or is it included with STEP 7?
ProSave is bundled with both the ProTool/Pro CD and inside STEP 7 V5.x (typically C:\Siemens\ProSave\ProSave.exe). For MP370 transfers without an integrated STEP 7 project, ProSave is sufficient on its own and supports all connection types (RS-232, MPI, PROFIBUS, Ethernet). For a panel with WinAC MP, the WinAC MP CD supplies a separate firmware image that must be installed via ProSave before the HMI project is downloaded.
Can I edit alarm text directly on the MP370 at runtime?
No. The MP370 Service menu exposes Backup/Restore, Transfer, Network settings, and System information, but it does not include an offline message editor. Alarm text changes must be made in the configuration tool (ProTool Pro or WinCC flexible 2004) and pushed back via download or memory card.