IMDTouchKnowledge BaseShop main store

How-to

How to Run makepic for Crimson 2.0 CompactFlash Images

HMI and touchscreens Published 7 min read

Short answer

Run makepic from a command prompt with the bitmap filename and a picture identifier from 0 through 999 as two separate arguments, for example makepic Photo1.bmp 1. Copy the converted picture to the panel's CompactFlash card and verify it on the physical G3, because it does not render in the PC editor.

On this page
  1. What does makepic do in a Crimson 2.0 project?
  2. Where does makepic.exe install?
  3. How do I set up a working folder for the conversion?
  4. How do I run makepic from the command prompt?
  5. Why does the command fail when the filename looks like picture.bmp 1?
  6. Which picture identifiers can makepic write?
  7. What does the -wide switch change?
  8. Why does the picture show on the panel but not in the PC editor?
  9. Questions asked

Run makepic from a command prompt, not by double-clicking it: the executable name, the complete bitmap filename and a numeric picture identifier go on one line as separate arguments, and the result is verified on the physical G3 panel, never in the Crimson 2.0 editor. The utility installs with Crimson 2.0 and converts a bitmap into the picture format the panel reads from its CompactFlash card, which keeps photo data off HMI memory. The two failures you will actually meet are a filename whose real extension Windows hides, and a number typed inside the filename instead of after it. The steps below set up a short working folder, run the conversion, and prove the picture on the hardware.

What does makepic do in a Crimson 2.0 project? #

It converts a Windows bitmap into the picture file a G3 panel loads from its CompactFlash card, so photo data lives on the card instead of in HMI memory, and the panel's image primitive calls that picture back by number at runtime.

Crimson 2.0 configures Red Lion panel meters, PID controllers and the select G3 HMI models that require it. For photos, the manual's route is the image primitive: a bitmap converted by makepic, stored on the installed CompactFlash card, and referenced by number on screen. The reverse job — turning graphics already on a panel into bitmap files for your records — is a different workflow, and converting legacy HMI graphics to bitmap images for documentation covers that direction.

Where does makepic.exe install? #

The executable installs inside the Crimson 2.0 program folder — on the machine that motivated this walkthrough it sits in C:\Program Files (x86)\Red Lion Controls\Crimson 2.0\makepic — and you copy it to a short working folder instead of running it from that long path.

If Crimson 2.0 is not on the PC yet, get it from Red Lion's download page and run the installer; that is the supported source for this legacy software. One safety note applies to the utility itself: run the makepic.exe that the installation put on your machine, because an executable with the same name from anywhere else has no place on a PC that connects to your control system.

How do I set up a working folder for the conversion? #

Create C:\Pics directly under the drive root — the arrangement that succeeded in the field — copy makepic.exe and one bitmap into it, and name the bitmap simply, Photo1.bmp, so the command never contains a space or a long path.

  1. Create the folder C:\Pics. If policy blocks writes to the drive root, use any writable folder and adjust the paths that follow.
  2. Copy makepic.exe from the Crimson 2.0 installation into C:\Pics, leaving the installed copy where it is.
  3. Copy one bitmap in as Photo1.bmp. One file in and one conversion out keeps the first test unambiguous.
  4. Show filename extensions: in Windows Explorer, open Organize, then Folder and search options, then the View tab, and clear the box marked Hide extensions for known file types.
  5. Read the filename again with extensions visible. A file shown as Photo1 may already be Photo1.bmp, and typing the extension again would create Photo1.bmp.bmp.
  6. After the first picture passes on the panel, repeat for the remaining bitmaps and write down the identifier each one received.

The folder sits one level from the drive letter, so cd C:\Pics is short to type and free of the spaces that Program Files (x86) forces into every path.

How do I run makepic from the command prompt? #

Open Command Prompt, point it at the working folder, then type the executable, the bitmap filename and the identifier as three separate items — makepic Photo1.bmp 1 — and leave the window open so the converter's messages stay on screen.

  1. Open Command Prompt. An administrator prompt was used in the documented case, but plain permissions work when the working folder is writable.
  2. Type C: and press Enter.
  3. Type cd C:\Pics and press Enter; the prompt now ends in the working folder.
  4. Type makepic Photo1.bmp 1 and press Enter.
  5. Read whatever the utility prints and check C:\Pics for the converted output before closing the window.

The prompt text is not part of the command: once the line reads C:\Pics, type only what follows it.

Item in the command What it is Rule
makepic the converter executable run it from the folder that holds it, or type its full path in quotes
Photo1.bmp the source bitmap, one argument complete filename with its real extension visible
1 the picture identifier, its own argument whole number, 0 through 999

When the bitmap lives somewhere with spaces in the path, quote the whole path and keep the identifier outside the quotes — makepic "C:\My Images\Picture1.bmp" 2 — or use the full-path form that also worked in the field, makepic C:\MyImages\picture1.bmp 1. Two errors live at two different stages: if Windows cannot find makepic, the current folder or the copied executable is wrong; if the utility starts but cannot open the image, the filename or its location is wrong. No change to the HMI project fixes either one.

Why does the command fail when the filename looks like picture.bmp 1? #

Because the command interpreter splits the line at spaces, the number belongs after the filename as its own argument, and with extensions hidden the name you see is not the name you type — the classic broken setup is a file literally named with a trailing number.

The machine in question arrived with a folder whose files displayed as picture.bmp 1 and picture.bmp 2. With extensions hidden, those were never bitmap filenames followed by an argument: the underlying names carried the trailing digits, like Photo1 with no .bmp at all, so the converter had no valid bitmap to open. Show extensions, rename once to Picture1.bmp, and put the number on the command line where the converter expects its second argument. If a space survives in the name anyway, quote the path as shown above.

Which picture identifiers can makepic write? #

Any whole number from 0 through 999 — 1,000 possible identifiers — and that range is a naming limit, not a storage guarantee: card capacity and the size of the converted files decide how many pictures actually fit.

The identifier belongs to the conversion command and never to the filename; the panel knows the picture only by this number, so log every assignment. Illustrative sizing, not a panel specification: a 240 × 160 pixel picture at 16 bits per pixel needs 240 × 160 × 2 = 76,800 bytes, which is 75 KB. A card with 40 MB free after the application holds about 40 × 1,024 / 75 = 546 such pictures, and 20 MB free holds about 273. Start the log at 1 and increment per picture; any realistic photo collection has room to spare.

What does the -wide switch change? #

It selects RGB 555 color — 16 bits per pixel — for the converted file, and it goes on the same command line as one more item: makepic Photo1.bmp 1 -wide.

That is the same 16-bit depth the sizing example above assumed, at two bytes per pixel. If a converted picture reaches the panel with wrong colors, convert the same bitmap again with -wide before touching anything else in the project.

Why does the picture show on the panel but not in the PC editor? #

Because CompactFlash pictures are looked up by the panel at runtime — the converted image never becomes part of the PC project — so the only valid check is the physical G3 with the card installed, which is exactly how the documented case behaved.

Copy the converted picture onto the CompactFlash card the panel uses, install the card, and open the screen that calls that identifier. In the field, the pictures appeared on the G3 while the PC editing session showed nothing, and that split is expected: the panel resolves the number at runtime from the card. The decision splits two ways. Keeping the G3 means converting from C:\Pics, logging identifiers, and accepting every picture on the panel itself. When the Crimson 2.0 ceiling becomes the problem instead, the screens move with you — importing legacy HMI screens when migrating to a new panel covers that half — and a PC-based HMI runtime on industrial panel PCs takes the terminal's place at the machine.

Questions asked

Does makepic exist in Crimson 3.0 or Crimson 3.1?

No, and it does not need to: Crimson 3 imports images directly in the editor, so the command-line conversion exists only for the G3 models that top out at Crimson 2.0. Before you buy a used panel, confirm which Crimson generation supports it, because that decides whether picture loading is a few clicks or this command-line workflow.

Which identifier number should I assign to my first picture?

Use 1 for the first bitmap, exactly as in the worked command, then increment for each additional file and write the mapping down. The panel requests the picture by that number alone, the filename never travels with it, and the 0 through 999 range leaves a comfortable margin for a photo collection of any realistic size.

Should I run the command prompt as administrator?

Ordinary permissions are enough when the working folder is one you can write to, such as C:\Pics. The documented success used an administrator prompt, but elevation repairs neither a mistyped path nor a hidden file extension, so treat it as site policy rather than part of the fix. If your account cannot create folders under the drive root, pick any writable folder and adjust the commands.

Is there a simpler way to put a picture on a Crimson 2.0 panel?

Yes, the software can embed images in the project, and for a couple of small graphics that is the faster route. The CompactFlash method earns its extra steps with photo collections, because every embedded picture consumes panel memory while the card carries the bulk of the data instead.

What input does makepic accept, and how do I protect the originals?

The command takes one bitmap filename and one identifier, so a photo library is a series of single conversions. Work from copies in the working folder and keep the master files elsewhere, so a failed run or a wrong-color retry never costs you an original.

Keep reading

  • How-to

    Migrate a PanelView Plus 6 project from ME 5.0 to 10.00

    Yes, the application can move from FactoryTalk View ME 5.0 to 10.00, but the runtime file itself is never version-converted. Confirm the terminal is a PanelView Plus 6 700-1500 or Compact 1000, restore an editable application from the .apa archive or a restorable .mer, convert it in FactoryTalk View Studio ME 10.00, build a new .mer at the 10.00 runtime version, and download it after flashing firmware 10.00-20180411. Part 11 compliance is a separate validation job.

    HMI and touchscreens

  • Troubleshooting

    OP15 project recovery: ComText, ProTool or ProSave

    Recovering a project from a Siemens OP15 starts with the panel's generation, not software preference. First-generation OP5 and OP15 hardware belongs to ComText, second-generation hardware belongs to ProTool, and firmware version 2.2 draws the line. ProSave is not in the decision: it writes a backup image, not an editable project, and the OP15 is not on its supported-device list.

    HMI and touchscreens

  • Troubleshooting

    Why Vijeo Designer direct IO variables show faded

    Faded, dotted %I and %Q values on a link where %M and %MW still read mean the v6.2 file upgrade broke the variable records' equipment and address linkage, not the communication path. Re-link and retype one I/O tag against the M221 equipment, fix the rest through the exported variable list, and rebuild the equipment entry only if the retyped tag still fades.

    HMI and touchscreens