How-to
How to import HMI images with a transparent background
Short answer
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.
On this page
- Which image formats does the EA9 accept at import?
- Why does the transparent color delete part of my QR code?
- Can I bring in PNG or vector artwork instead?
- How do I separate the QR code from its background before import?
- How do I save the file so the import accepts it?
- What should I check on the panel after the import?
- What happens when the screen background changes later?
- Questions asked
If an EA9 screen needs a picture with no visible background, do the work before the file ever reaches the import dialog. The version 6.8 C-More setup imports bitmaps only, and its transparent-color key removes one chosen color across the whole image, so keying out a black background takes every black QR-code module with it. The fix is editorial, not a setting: lift the code onto its own layer in an image editor, rebuild the background as a solid color matched to the screen, and export a genuine BMP through the editor's save function. Renaming a PNG to .bmp converts nothing. The sections below cover the format limit, the arithmetic of why a shared color gets destroyed, the layered edit, the export, and the scan test that decides when the screen is done.
Which image formats does the EA9 accept at import? #
BMP is the format the import accepts on the EA9 with version 6.8 of the C-More software, so prepare every picture as a bitmap; the file picker does not offer PNG, and no project setting changes that list. The limit lives in the import dialog itself: its file-type filter offers bitmap files, so a PNG on disk is never presented no matter what the screen needs. Any plan that starts with 'get it in as a PNG' is a dead end on this panel class. The practical consequence is that all preparation happens in the image editor before export, which is the workflow the rest of this article follows.
Why does the transparent color delete part of my QR code? #
The transparency function works on one color, not on one object: it makes every pixel that exactly matches the key color disappear, so a black key erases the black background and every black QR module printed in the same shade. The key is a color match, not an object selection. Background, border, and any code module printed in that black all share the same value, and identical values are identical by definition, so the software cannot tell them apart and both vanish together.
Worked example with illustrative numbers: a version-1 QR code is 21 × 21 modules, and with the standard 4-module quiet zone on every side the artwork grid is 29 × 29 modules. Rendered at 8 px per module, the bitmap is 232 × 232 px, or 53,824 px in total. The quiet zone is 841 - 441 = 400 modules, which is 400 × 64 px = 25,600 px of background black. A typical version-1 code prints roughly half of its 441 modules dark, so the same key strikes about 220 × 64 px = 14,080 px of code modules as well. One key color therefore erases 25,600 + 14,080 = 39,680 px, about 74% of the image: three finder corners and most of the data area gone, leaving white dots that no scanner reads. Re-importing the same picture as a BMP with the same key repeats the damage, because the pixels never changed.
Can I bring in PNG or vector artwork instead? #
Vector artwork reaches the panel through Symbol Factory and its File \ Import Symbol path, not through the regular image import, and PNG support is a software-and-panel question, so treat BMP as the only format to rely on for this setup. Symbol Factory places drawn, scalable artwork on the screen without the bitmap import at all, which is the supported door for vector art. Flat PNG support depends on the software generation and the panel model rather than the file; the pairing is mapped out in which HMI software works with which HMI panel hardware. On the setup described here, plan every asset as BMP and treat any other format as something to prove in your own installed version before building screens around it.
PNG transparency also misbehaves on platforms that accept the file. One HMI package crashes on a transparent PNG, a failure covered by a documented PNG transparency crash fix for FactoryTalk View Studio ME V8. Another paints transparent areas solid black, which is the fault a fix for black PNG transparency in WinCC Professional resolves. One working PNG in one project proves nothing about the next.
How do I separate the QR code from its background before import? #
Work in a layered image editor, keep the QR code on its own layer, and rebuild the background behind it instead of keying the color out; that keeps every dark module intact no matter what color the original background used. The steps:
- Open a copy of the source image in an editor that supports layers, and keep the untouched original beside the project as the recovery point.
- Select the QR code and lift it onto its own layer, cutting along the quiet-zone border rather than through a module so the finder corners survive.
- If the artwork has no quiet zone, add one: four modules of plain uniform background on every side, on the same pixel grid.
- Delete or hide the original background layer so only the code layer remains.
- Add a solid-color layer beneath the code, filled with the exact RGB triplet of the screen background behind the image, read from the screen's background color setting in the project.
- Zoom to the final display size and confirm every module, corner and quiet-zone edge is intact before export.
If you would rather keep using the transparent-color key after import, fill that underlay with a color that appears nowhere in the code; with black-and-white artwork, any third color is a safe key, because the key then has nothing in the code to strike.
How do I save the file so the import accepts it? #
Export the finished composite through the editor's real BMP save function, because a renamed file is not a converted file: changing the extension from .png to .bmp leaves PNG pixel data inside a bitmap-labeled shell that the import rejects or misreads. Use Export or Save As, pick BMP, and let the editor write a standard uncompressed bitmap. For full-color artwork the default 24-bit export is the safe choice; for pure black-and-white code art a 1-bit two-color export is enough and keeps the file small. Sizing check on the example bitmap: at 232 × 232 px, 24-bit pixel data is 232 × 696 bytes = 161,472 bytes, about 158 KB with the file header, while the 1-bit version is 232 × 32 bytes = 7,424 bytes. If the editor offers several bit depths and one of them imports wrong, fall back to 24-bit, which every bitmap importer reads. Reopen the saved file once and confirm edges and colors before it goes into the project.
What should I check on the panel after the import? #
Judge the image on the panel at its final size, because scaling and color handling can differ between the editor preview and the display, then scan the QR code with the reader operators will use before you call the screen done. Import the BMP, place the object, and download. In the project preview, check the rectangle's edge: a visible outline means the underlay does not match the screen background, so re-read the RGB triplet and rebuild the file. On the panel, look for missing dark squares, clipped finder corners and stray single-pixel fragments along the edges. If the image sits right but neighboring text shifts or clips after download, that is the same editor-versus-panel layout problem described in HMI text running off the screen after downloading the project.
Close with a scan, not an eyeball: point the reader operators will actually use at the screen from the working distance and angle, and treat any visible hole in the artwork as a defect even when the scan passes. If the code opens safety or maintenance documents, the on-screen copy supplements the printed label on the machine and never replaces it.
What happens when the screen background changes later? #
A solid background layer baked into the BMP is a patch, not transparency: if the screen background changes later, the old patch shows as a rectangle, so re-edit the layered source file and export a fresh BMP for the new color. The repair is cheap only while the layered source exists. Reopen it, change the underlay fill to the new triplet, export and import again, which is minutes of work against re-creating the artwork. Store the layered source, the exported BMP and the project file together, and never edit an exported bitmap in place: each resample softens module edges, and the second or third round-trip is where a code that used to scan starts failing.
Questions asked
Does a newer C-More release import PNG on the EA9?
Treat the import dialog's file-type filter in your own installed version as the authority: open the image import, read the filter list, and design around what it offers. On the version 6.8 setup described here the filter offers bitmaps, so every asset gets prepared and exported as BMP regardless of what a newer release might add.
What pixel size should the exported BMP have?
Match the final on-screen pixel size and keep an integer number of pixels per QR module. The worked example uses 8 px per module on a 29 × 29 module grid, giving 232 × 232 px. Non-integer scaling blurs or drops single modules, which is the most common reason an undamaged file still fails to scan on the panel.
How do I make the underlay color match the screen exactly?
Type the RGB triplet into the editor's color picker; do not sample the finished composite. Sampling picks up anti-aliased pixels along module edges, which sit between the code black and the underlay color, and any sampled value lands slightly off the true background. The exact triplet comes from the screen's background color setting in the project, and it is typed, never sampled.
My keyed code still scans on the bench. Is it done?
Not on one reading. QR error correction can recover a moderate number of destroyed modules, so a code with visible holes can pass a close-range bench scan and still fail at the operator's distance, angle or lighting. Test with the real reader at the real working distance, and treat any visible hole as a defect to repair.