IMDTouchKnowledge BaseShop main store

How-to

Importing flb symbol libraries into EasyBuilder projects

HMI and touchscreens Published 7 min read

Short answer

A .flb file is an Image library: put it in the Library directory of the EasyBuilder installation and load it from the Library menu's Image category. The Group dialog you used expects a .glb file, which is why the format is rejected.

On this page
  1. Why does EasyBuilder refuse my .flb file in the library dialog?
  2. Which library manager handles .plb, .flb and .glb files?
  3. Which folder must the .flb file sit in before EasyBuilder can use it?
  4. How do I load the .flb library into an open project?
  5. Why does the same project report missing libraries on another PC?
  6. Can I recover the icons after choosing disassociate for the missing libraries?
  7. How do I make an imported fan GIF switch states from the PLC?
  8. Does the same method work for a Word lamp with more than two states?
  9. Questions asked

Your .flb file is an Image library, and the dialog you used is the Group library dialog, which only accepts .glb files. Copy the .flb into the Library directory of the EasyBuilder installation, then load it from the Library menu's Image category with the Select Library control. The file is not corrupt and nothing needs reinstalling. This article walks the whole path: which extension belongs to which library manager, where the file has to sit, how the project remembers it, what to do after libraries were disassociated, and how a Bit or Word lamp uses the imported graphics to show a running fan.

Why does EasyBuilder refuse my .flb file in the library dialog? #

The Group library dialog you used lists only .glb files, and your download is a .flb Image library, so nothing is wrong with the file — it simply has to be loaded through the Image library dialog instead.

EasyBuilder installs a base set of libraries together with the software, and the manufacturer's site offers many more, grouped by subject, each arriving as one library file. When a file you can see on disk is refused by a dialog, the dialog's category is the first suspect — ahead of file corruption, ahead of a reinstall. Read the extension, confirm which of the three library types it is, and open the manager that owns that type.

Which library manager handles .plb, .flb and .glb files? #

One manager per extension — .plb opens in Shape, .flb in Image, .glb in Group — and the three types hold different content, so the extension alone decides which manager must load the file.

Library type Extension What it contains Manager to open
Shape .plb Vector objects drawn inside EasyBuilder Shape
Image .flb Graphic symbols made with drawing software, such as GIF fan images Image
Group .glb Grouped screen objects Group

Weintek, EasyBuilder's manufacturer, installs the starting set with the editor and publishes the additional subject libraries as downloads covering both EasyBuilder and EasyBuilder Pro. The decision this table settles: read the extension before opening any dialog, because a file-type filter in the wrong dialog hides or rejects a file that is present and healthy.

Which folder must the .flb file sit in before EasyBuilder can use it? #

In the Library directory of the EasyBuilder installation you open the project with — for the 32-bit EasyBuilder 8000 generation that directory sits under Program Files (x86) — with a second copy kept in the folder where you save the project.

The two copies do different jobs. The installation copy is the working file: the library managers read that directory, so it is the copy the project actually loads. The project-side copy preserves the dependency — it is what travels with your backup and what you copy to the next engineering PC. A library picked straight from a Downloads folder works today and breaks later, because the project stores that folder in its reference. When several EasyBuilder installations share one PC, use the Library directory of the installation that actually opens this project.

How do I load the .flb library into an open project? #

Through the Image category: place the file first, then open the project, choose Image from the Library menu, and pick the file with the Select Library control inside the window that lists the project's libraries. Five steps, in that order.

  1. Copy the downloaded .flb file into the Library directory of the EasyBuilder installation.
  2. Open the project in EasyBuilder.
  3. From the Library menu, open the Image category — not Group.
  4. In the window listing the project's libraries, use the Select Library control and pick your .flb file.
  5. Browse the library contents, confirm the expected symbols are there, and place one on a screen as a test.

If the file still does not appear, two checks settle it. Turn on filename extensions in Windows, because they are hidden by default and a file that downloaded with a doubled extension such as name.flb.txt is a text file to the dialog. Then re-read the active category at the top of the window. Once the library loads and the test symbol renders, save the project so the reference persists.

Why does the same project report missing libraries on another PC? #

Because the project stores the path to each library it uses, and copying the project file alone does not carry those external files — the named library must exist at the stored location on the new PC, or EasyBuilder reports the error on opening.

That is the classic split behavior: the project opens cleanly on the development machine and flags missing libraries on the next one, because the project file carries references, not the graphics themselves. The fix sequence is fixed: close EasyBuilder, copy the named library into the location the message identifies, reopen EasyBuilder. When two PCs have different directory layouts, follow the stored reference the message gives you rather than assuming any folder named Library will do.

Can I recover the icons after choosing disassociate for the missing libraries? #

Not by re-downloading alone: disassociate removed the project's association to those libraries, so the icons vanish until an intact project copy is restored or each object's graphic assignment is rebuilt — restore first, rebuild only if no intact copy exists.

Restoring a file and disassociating it are different operations: the first supplies an unresolved dependency, the second deletes the relationship the project needs to find its graphics. The typical EasyBuilder 8000 sequence runs like this — a project uploaded from a panel flags missing libraries, disassociate is chosen, the icons disappear, and downloading the libraries afterwards changes nothing, because no object knows which library entries were theirs.

Keep an untouched copy of the current project before either route; these edits are not reversible.

  • Recover a saved project that predates the disassociate, place its libraries at their stored paths, and open it.
  • If that copy shows its symbols, adopt it as the baseline and re-apply the later edits on top.
  • With no intact copy, load each needed library through its matching manager and reassign the graphic and state images on the affected objects, then save.

Re-selecting the same library cannot repair an object that no longer points at its symbol, and rebuilding objects is wasted work when the references are intact and only the files were missing.

How do I make an imported fan GIF switch states from the PLC? #

With a Bit lamp object: assign the fan-stopped GIF to state 0 and the fan-running GIF to state 1, then point the lamp's read address at the PLC bit that runs the fan — the standard lamp technique, unchanged for imported images.

The GIF carries no variable binding of its own; the object does. Drop a Bit lamp on the screen, map the two states to the two images from your library, and give the lamp the PLC bit as its input. If the tag list still has to reach the project, importing a PLC tag CSV into an existing HMI tag database is quicker than retyping every address. Before downloading to the panel, testing the HMI simulation against a live PLC confirms the graphic flips with the bit.

Does the same method work for a Word lamp with more than two states? #

Yes — one image per configured state, exactly as for the Bit lamp: a Word lamp compares its variable against each state value you configure, so the image count follows the state count you set on the object, not the library.

Worked example — one screen, three device types. A screen carries 3 fans, 2 on/off pumps, and 1 valve with positions 0, 1 and 2:

  • Fans: 3 Bit lamps × 2 states = 6 state-image assignments.
  • Pumps: 2 Bit lamps × 2 states = 4 assignments.
  • Valve: 1 Word lamp × 3 states = 3 assignments.
  • Total assignments on the screen: 6 + 4 + 3 = 13.

The library behind it holds only the distinct images: 2 fan GIFs + 2 pump GIFs + 3 valve GIFs = 7 files. Assignments multiply with the objects; library contents do not — one .flb serves every lamp that reuses its images. Configure the state list on each lamp first, then fill in one image per state from whichever library holds it.

Questions asked

Will renaming a .glb file to .flb make it load in the Image dialog?

No. The extension records how the library was built, not a label you can edit: a Group library holds grouped objects, an Image library holds bitmaps such as GIFs. Renaming changes nothing inside the file, so the Image manager still cannot read it. Download or build a library of the correct type instead.

What is the GIF picture shown beside each library on the download page?

It is a preview, not the library. Each library's page shows one GIF illustrating every symbol the file contains, so you can confirm the content before downloading. You still need the library file itself, copied into the installation's Library directory, before the symbols are usable in a project.

Can I build my own library instead of downloading one?

Yes. Create a new library in the library manager, then import your images into it one by one. For a running fan that means two entries: one GIF with the fan stopped and one with it spinning. Your own library then behaves exactly like a downloaded one in every lamp and object.

Do I need administrator rights to copy a library into the Library directory?

Usually yes on current Windows, because the EasyBuilder installation, the 32-bit EasyBuilder 8000 generation included, sits under Program Files (x86), and writing there is restricted. Accept the elevation prompt when it appears, or copy from an elevated file manager. Afterward, reopen EasyBuilder so the manager lists the new file.

Do Shape and Group libraries import the same way as Image libraries?

Yes, through their own managers: .plb through Shape and .glb through Group, each after the file sits in the same Library directory. The managers differ only in category; the placement rule, the stored project path and the missing-library recovery are identical for all three extensions.

Keep reading

  • Troubleshooting

    Importing a ProTool .lib library into WinCC Flexible

    WinCC flexible cannot import a ProTool .lib object library, and no utility converts .lib files to the .wlf format it expects. Plan the OP270-to-TP177 migration around reusing an existing .wlf library and rebuilding the remaining objects in the TP177 project, then verify each object on the panel.

    HMI and touchscreens

  • How-to

    Importing a PLC Tag CSV into an Existing HMI Tag Database

    A PLC tag CSV imports only when its columns match the format your HMI software documents — .csv for one package, .xlsx for another. Never import into the production project: run it on a copy, use the tag count to tell merge from replace, spot-check one revised address, and confirm each affected tag against live PLC values before download.

    HMI and touchscreens

  • How-to

    How to import HMI images with a transparent background

    On an EA9 panel running version 6.8 of the C-More software, image import takes BMP, so PNG is out; the transparent-color key removes every pixel of one chosen color, which is why a QR code sharing the background black gets destroyed. Separate the code on its own layer in an image editor, rebuild the background as a solid color that matches the screen, and export a real BMP.

    HMI and touchscreens