Troubleshooting
Fixing an HMI MER runtime version mismatch
Short answer
The transfer fails because the runtime version and the terminal's ME Station version differ: a PanelView Plus 600 hardware ceiling is firmware 5.10, while Studio 11 defaults to a version 11 runtime. Read the station version at the terminal, select 5.10 in the Create Runtime Application dialog, rebuild, and remove the gradients or PNG images the build errors name until the 5.10 compile passes.
On this page
- Separate a build failure from a transfer rejection
- Find the terminal's version ceiling
- Create the runtime at 5.10, not at Studio's default
- Worked example: PanelView Plus 600 on firmware 5.10.16.09 built in Studio 11
- Strip the graphics the build errors name
- Verify both ends before the machine runs
- When the terminal, not the project, is the limit
- Questions asked
An incompatibility message at transfer means the runtime file and the terminal's runtime engine are different generations. The PanelView Plus 600 hardware tops out at firmware 5.10, so its ME Station can load at most a 5.10 runtime, while FactoryTalk View Studio ME 11 defaults to writing a version 11 file. Select 5.10 in the Create Runtime Application dialog's version list, rebuild, and if the older target refuses to compile, remove the gradients and PNG images the build errors name.
Separate a build failure from a transfer rejection #
The two failures surface at different stages and call for different checks, so read the exact message before editing anything.
- Runtime builds, terminal rejects the transfer as incompatible. Compare the version the file was saved as with the ME Station version shown on the terminal; that mismatch is the subject here.
- Studio reports errors while creating the runtime. The project holds objects or images the selected target cannot compile, so stay in Studio and work from the build output.
- Build succeeds but the terminal still refuses the file. Re-check the generated file's version and the station version, because changing the dialog does not repair a file built earlier.
'Incompatible' on its own does not tell you which stage failed, and the exact wording of the terminal message decides the next step. This workflow also assumes the Studio source project exists; if the only copy of the application is on the terminal, recovering an HMI program when the source file is lost is the job to finish first.
Find the terminal's version ceiling #
Three version numbers live on one of these terminals: the firmware image, the ME Station engine that runs applications, and the MER you create in Studio. The rule that decides this failure links the last two: the ME Station version must match the version the runtime was saved as.
The vendor compatibility note for the PanelView Plus 400/600 family sets the boundary. The hardware supports firmware up to 5.10, and units upgraded to 5.10.10, or shipped with it, cannot be downgraded to earlier releases such as 5.10.x, 5.0.x, 4.0.x or 3.20. On this class of terminal the version is therefore fixed in both directions: no upgrade above 5.10, and on those units no step back below it either. The runtime moves, not the terminal.
Read the station version before touching graphics: on the terminal, open terminal settings, then System Information, then About FactoryTalk View ME Station. The number there is the value the MER must be saved as, and if it differs from what you assumed, settle that first. Should the panel ever need its firmware image reloaded rather than a new runtime, matching file to terminal is the same discipline covered in getting the right firmware file for a legacy HMI panel.
Create the runtime at 5.10, not at Studio's default #
In FactoryTalk View Studio, open the Application menu and choose Create Runtime Application. The dialog sets the runtime name, the option that protects the file against being restored without a password, and the version, which is the setting that decides this failure. It defaults to the Studio version, 11.00 on this workstation; open the version list, select 5.10, then build.
Studio 10.00 and later show a confirmation popup when the target is 9.00 or earlier. That popup is the documented warning for legacy targets, so confirming it is the intended path, not a fault.
Selecting an older version changes only the format the compiler emits. It does not downgrade Studio, it does not raise the terminal's ceiling, and it does not make every object in the project legal for the old format, which is why the build errors in the next section appear.
Worked example: PanelView Plus 600 on firmware 5.10.16.09 built in Studio 11 #
The inputs, and where each comes from:
- Terminal: PanelView Plus 600 at firmware 5.10.16.09, read from the terminal's firmware version screen; this is the case behind the article.
- ME Station version: 5.10, read at terminal settings, then System Information, then About FactoryTalk View ME Station.
- Workstation: FactoryTalk View Studio ME 11.00, whose runtime dialog defaults to a target of 11.00.
- Ceiling and floor: firmware 5.10 for the 400/600 family, with no downgrade below 5.10.x once a unit reaches 5.10.10, from the vendor compatibility note.
The rule in words: a terminal loads a MER only at the version its ME Station runs; the MER's version is whatever the runtime dialog selected; and the station cannot be raised past the 5.10 hardware ceiling.
The arithmetic, written out:
- Default path: dialog target 11.00 against a terminal ceiling of 5.10. Since 11.00 is greater than 5.10, no station on this hardware can load the file, so the incompatibility message appears at transfer.
- Corrected path: dialog target 5.10 against a station at 5.10. The two values are equal, so the terminal accepts the file.
- Range check: the documented floor of 5.10.x and the ceiling of 5.10 leave exactly one workable version.
The result: the only runtime version this terminal can load is 5.10, regardless of which Studio release built the project.
The decision it leads to: whenever the About FactoryTalk View ME Station screen reads 5.10, select 5.10 in the version list. Any higher selection is rejected at transfer, and no firmware move changes that on the 400/600 hardware.
Strip the graphics the build errors name #
A project can edit cleanly in Studio 11 and still fail the 5.10 compile, because the compiler must express every object in the older format. In the case behind this article, removing the gradients and the PNG images let the 5.10 runtime build and transfer; transparency behaves the same way in reported cases, and the practical reading is that these effects belong to runtime generations newer than 5.10. Let the build log be the authority: the error that names the object is the evidence, and a passing 5.10 build is the confirmation.
- Read every build message and change only the object or image it names.
- Replace a gradient fill with a solid color or a two-tone block drawn from native objects.
- Replace a PNG with a simple native graphic; if the message points at transparency, redraw the element without layered transparent images.
- If an error names nothing you can act on, remove one feature class at a time, gradients first, then PNG images, then transparency, rebuilding between each so the change that cleared it is known.
- Leave tags, communications and alarm setup untouched until the build is clean, keep an unedited copy of the original project, and note each change.
Verify both ends before the machine runs #
- The runtime dialog read 5.10 at the moment the file was created, not 11.00.
- The build closed with no outstanding errors; a file produced with errors still live is not a verified application.
- The transfer completed without the incompatibility message and the application starts at the terminal.
- Every screen touched during the cleanup still renders legibly at the terminal.
Before returning the machine to production, walk those screens with the equipment in a safe state: graphics removed to satisfy the older target may have carried status or alarm indications the operators relied on, and a missing indicator is a hazard, not a cosmetic gap.
If the station version and the file version match on paper and the transfer still fails, capture the exact terminal message and the full build log. The next diagnostic step comes from those two artifacts, not from further graphics edits.
When the terminal, not the project, is the limit #
If the design needs gradients, PNG artwork or transparency as drawn, a 5.10-only terminal can never run it and no dialog selection changes that. The decision is then hardware: moving the application to industrial panel PCs that run a current ME Station generation keeps the graphics as designed instead of flattening them for an older target. For the selection work that replacement deserves, the criteria in planning an HMI terminal replacement from an older operator panel carry over unchanged.
For a 400/600 terminal that still runs, though, the rebuild above is the entire job. This transfer ends at the version list, not at new hardware.
Questions asked
Does the runtime have to match the full firmware number, such as 5.10.16.09?
No. The match is made at the ME Station level: a terminal whose station screen reads 5.10 takes a runtime saved as 5.10. The longer firmware number is the terminal's image build, not a value you enter anywhere, so nothing in Studio or the transfer dialog should ever be set to 5.10.16.09. Select 5.10 in the runtime dialog and let the station engine handle its own build.
Does building a version 5.10 runtime change the Studio project file?
No. The version selection controls only the MER that Create Runtime Application writes; the project stays a Studio 11 project and keeps every object, including the gradients and PNGs you removed from the runtime build if you edited a copy. That also means one project can serve two generations of hardware: build a 5.10 file for the old terminal and an 11.00 file for a current one, from the same source.
Can I keep a gradient by exporting it as an image?
Expect the same class of build error: a gradient baked into a PNG is still a PNG, and the PNG class is what the 5.10 compile rejects. The dependable substitutions are native objects, meaning a solid fill or a two-tone block that suggests the same shading. If a picture is unavoidable, let the build log decide: try the simplest format, rebuild, and transfer only once the 5.10 compile closes without errors.
How far back can a current Studio version target runtimes?
Several major versions: a V13-era Studio can still create 5.0 runtimes, and Studio 10.00 and later flag any target of 9.00 or earlier with a confirmation popup. The practical floor for a given install is whatever its version list offers for your terminal class, so read the list rather than assuming. For the 400/600 terminal here the floor is irrelevant, because 5.10 is the only value its station can load.