Troubleshooting
Importing legacy HMI screens when migrating to a new panel
Short answer
A PanelBuilder32 application (.PVA or .PBA) imports directly into FactoryTalk View Studio, so test the conversion on a copy before deciding to rebuild. Converted screens usually arrive intact but need font and alarm-banner resizing; screens locked by an unknown password must come from authorized access or approved documentation, never guesswork.
On this page
- Can you import a PanelView 550 project into FactoryTalk View Studio?
- What do you need before you try the import?
- How do you test the import without risking the original file?
- What needs fixing after a successful conversion?
- Is converting faster than rebuilding the screens from scratch?
- What can you do about screens locked behind an unknown password?
- How do you prove the converted application runs correctly?
- When should you convert and when should you rebuild?
- Questions asked
Yes — FactoryTalk View Studio has a built-in import for legacy PanelView projects, so the PanelBuilder32 application behind a PanelView 550 can usually be converted instead of rebuilt from scratch. The conversion is not work-free: plan to resize text and alarm banners on the converted screens, and treat every screen locked behind an unknown password as unavailable until the project owner grants authorized access. Run the import on a copy, judge the result screen by screen, and fall back to a rebuild only where the file fails or the screens cannot be recovered legitimately.
Can you import a PanelView 550 project into FactoryTalk View Studio? #
Yes — FactoryTalk View Studio includes a built-in import for legacy PanelView projects, so a PanelBuilder32 application saved as a .PVA or .PBA file can be brought into a new PanelView Plus 7 target without rebuilding every screen by hand.
The route is not a terminal-to-terminal transfer. The old application file travels through FactoryTalk View Studio on a PC: the import reads the PanelBuilder32 project, produces an application for the new terminal generation, and the result is then downloaded to the PanelView Plus 7 like any other project. That makes the file on your engineering archive, not the panel on the wall, the artifact that decides this migration. A running 550 proves the application exists; it is not itself the file the import reads.
What do you need before you try the import? #
Before starting, gather five things: the actual PanelBuilder32 application file, a working copy of it, a FactoryTalk View Studio install matched to your PanelView Plus 7 model, written authorization for any password-protected screens, and approved documentation to check the result against.
- The PanelBuilder32 application file, from engineering archives, machine documentation or the original integrator, with its file name and origin recorded.
- A working copy for the import test; the original stays untouched and read-only for the whole job.
- A FactoryTalk View Studio install matched to the target you are standardizing on. Decide that target now: if the plan is a PC-based operator station rather than another dedicated terminal, the hardware class to specify is industrial panel PCs.
- Written authorization from the project owner for any screens the development password protects, and a clear picture of which lock is which — an operator login on the running terminal is runtime security, not permission to edit the project.
- Approved drawings or a process specification, because they become the acceptance reference for anything you have to rebuild.
If no project file turns up anywhere, the remaining option is capturing the application back off the terminal while it still runs; the steps in uploading a program from an old touchscreen HMI cover that capture, and the running panel then doubles as the visual reference during validation.
How do you test the import without risking the original file? #
Run the import on a copy of the application and keep the original file untouched, so a failed or incomplete conversion costs nothing and the source remains available as a rollback for the whole migration.
- Copy the PanelBuilder32 file to the engineering workstation and mark the original read-only.
- Point the legacy PanelView import in FactoryTalk View Studio at the copy, with the PanelView Plus 7 application as the target.
- Open every converted screen, not just the first, and note which came through complete and which are missing or empty.
- Record the screen count before and after, so the cleanup workload has a fixed baseline.
- Leave the original file and all backups exactly as they were.
If the import refuses the file, check what you pointed it at first: the development application, an export and a backup of something else are different artifacts, and selecting the wrong one is the most common false failure. Only when the correct file fails in a Studio version suited to the target does the rebuild decision in the last section apply.
What needs fixing after a successful conversion? #
Expect text sizing to dominate the cleanup: conversions from this panel generation are widely reported to come through with fonts that need adjustment, and alarm-banner text is the item integrators correct most often.
In reported conversions the pattern is consistent: ordinary graphics and layout survive, text lands mis-sized, alarm banners look worst, and multiple text objects on one screen can be selected together and resized in a single operation. Work in that order:
- Start with a representative text-heavy screen, fix its sizing, then carry the same size to the rest through multi-select.
- Recheck every object after a shared resize, because one size change lands differently on different layouts.
- Compare each screen against the running old terminal or the approved drawing, checking clipping, alignment, and labels that no longer identify the right control or value.
- Record any screen you cannot verify because it is locked or arrived incomplete, and treat it as an open item rather than a finished one.
Fix systematic sizing first and leave differences that do not affect operation for last; that sequencing keeps the cleanup in hours instead of days.
Is converting faster than rebuilding the screens from scratch? #
Once the import completes cleanly, conversion almost always wins on hours: text cleanup runs in minutes per screen while a hand-built screen costs an hour or more, and operators accept screens they already know faster than new ones.
Size the decision with your own screen count. Illustrative planning example, not a measured constant: a 20-screen application, cleanup at 15 minutes per screen after the import, and a from-scratch rebuild at 2 hours per screen including tags, alarms and navigation.
- Conversion path: 0.5 h to run the import plus 20 × 15 min = 300 min = 5.0 h of cleanup, for 5.5 h total.
- Rebuild path: 20 × 2 h = 40 h.
- Difference: 40 − 5.5 = 34.5 h, roughly four working days of engineering time.
The per-screen rates are assumptions, so time the cleanup on two real screens after the import test, multiply across the rest, and compare against your own rebuild rate — the ratio decides, not the example's absolute hours. Integrators who run these migrations regularly leave the convert-versus-rebuild call to the customer and cost the two paths separately; when operators know the old screens, conversion plus text cleanup is what they usually deliver, because familiar screens shorten training and fault-finding. When the import fails or most screens are locked and undocumented, the conversion advantage disappears and the rebuild from approved documentation becomes the only verifiable path.
What can you do about screens locked behind an unknown password? #
Nobody should guess or bypass a project password: the legitimate routes are authorized access from the project owner, the original integrator, or the vendor's documented recovery, and otherwise the locked screens get rebuilt from approved documentation.
This is the failure mode that turns a conversion into a partial one. Ask the site owner and, if still reachable, the original integrator for the development password in writing; the vendor's official support channel is the only other route, and a recovery procedure counts only if the vendor documents it. An operator login on the running panel proves nothing about edit access — runtime security and the development-file lock are different protections.
Never infer a locked screen's contents from its neighbors. A screen reconstructed by guesswork cannot be verified against any reference, and approving it means putting an unknown control face in front of operators. Rebuild locked screens from approved drawings and operator requirements instead, mark the application as partially converted, and record which screens were recreated. When the lock means there is effectively no usable project at all, the plan in replacing an old HMI when no project files exist becomes the main path rather than the fallback.
How do you prove the converted application runs correctly? #
A screen that opens in the editor is not a screen that runs correctly, so validate every converted screen against the live controller during a controlled commissioning before the new panel enters production.
Conversion reproduces graphics; it does not prove behavior. Work through the target application against the actual control system and check, screen by screen:
- Every tag or data-source reference resolves to the intended controller address and updates on the display.
- Navigation links reach the screens they claim to reach, in both directions.
- Alarm triggers, messages and banner presentation match the approved specification.
- Operator actions behave as designed — a momentary push behaves momentary, a reset resets the intended bit.
One safety note: treat a converted start, stop or reset control as unproven until it has been exercised against the real machine in a safe state, because a mis-mapped tag is invisible in the editor and indistinguishable from a correct one until it operates. Sign off on runtime evidence — verified screens listed by name — never on the fact that the import completed.
When should you convert and when should you rebuild? #
Convert when the file imports and the remaining work is layout cleanup; rebuild only the screens you cannot access or verify; stop and escalate to the project owner when the file itself is unreachable.
- Import completes and screens open: convert. Budget the text and alarm-banner cleanup per screen, keep the original file as rollback, and schedule validation with the live controller.
- Import completes but text and banners are wrong: still convert. That is cleanup work, not evidence the conversion failed.
- Import rejects the correct file in a suitable Studio version: rebuild from approved documentation, after reconfirming the artifact and the version.
- Screens locked with no authorized access available: rebuild those screens from approved drawings, convert the rest if the file itself opens, and document the split.
- No project file exists anywhere: rebuild, capturing what the running panel can still show while it runs.
Finish with a written migration record and keep the untouched original file with it, so the next technician knows which parts of the application came through a conversion and which were rebuilt by hand.
Questions asked
Do I need PanelBuilder32 installed just to run the import?
No. The import for legacy PanelView projects is built into FactoryTalk View Studio, so the conversion runs from View Studio against the application file the old tool produced. Chasing a copy of PanelBuilder32 is not a prerequisite for the import. If the import refuses a file you believe is valid, confirm the file's identity and your Studio version before concluding the file is corrupt.
Can I recover the application from the running terminal if no file exists?
That depends on the terminal model and its firmware, and the manufacturer's documentation for the specific model is the authority on whether a transfer back to a computer exists. Attempt any capture while the old panel is still installed and powered, because a running terminal doubles as the visual reference for validating rebuilt screens. If no transfer path exists for the unit, rebuild from approved documentation rather than from memory.
What text size should converted screens end up with?
Use the size that fits the worst case, not a fixed number. Open the screen carrying the longest label, resize until that label sits in its box without clipping, then apply the same size to the remaining text through multi-select and recheck every screen individually. Readability at the operator's normal working distance is the acceptance test, not the number in the font field.
The import rejects the file — is the project lost?
Not yet. First confirm the file is the development application and not an export or a backup of something else, then confirm the Studio version suits the target terminal generation. Try a second backup copied on a different date: if that copy imports, the first file is corrupt rather than the path. If every known copy fails, the rebuild-from-documentation route becomes the decision.
What should the migration record contain when the job is done?
Enough for the next technician to audit the result: the source file name, date and origin; the target application and terminal model; a list of screens converted as they came through; a list of screens rebuilt or resized, with the reason; any screens still locked or unverifiable; and the runtime validation results. Keep the untouched original file with the record.