A panel reads the whole card's file structure at power-on, so a bigger CompactFlash card adds seconds to boot even when the project is unchanged. Size the card to the smallest capacity the panel's documentation lists; with no documented limit, fit the smallest card that holds the project and logs. Time boot from power-on to the operating screen before and after any card change.
If a panel started taking two or three times longer to reach its operating screen after a CompactFlash card change, the card's capacity is the first suspect. Panels in this class read the file structure of the entire card during startup, so a bigger card adds seconds even when the project is unchanged. One HMI maker's published guidance reports a 137 GB ceiling for these cards and recommends a small capacity for boot speed. This page shows how to time a boot, tell a card-capacity delay from a project or supply delay, and size the replacement so startup returns to its baseline.
Why a bigger card boots slower
The behavior is documented. One HMI maker's published FAQ answers the capacity question directly: it reports a 137 GB maximum for CompactFlash cards and adds that the bigger the card, the slower the panel boots, because startup has to read the file structure of the entire card.
The mechanism follows from the file system. On a FAT32 card, the allocation table carries one 4-byte entry per cluster, and standard format tools pick 4 KB clusters for a 2 GB volume and 8 KB for a volume of 8 to 16 GB. A 2 GB card holds about 488,000 clusters, so one copy of the table is roughly 1.9 MB; a 16 GB card holds 1,953,125 clusters, roughly 7.8 MB per copy. The panel reads that table plus the directories at startup, and the structure grows with the formatted capacity of the volume, so an unused card still carries the full table. The read follows the card's size, and how full it is changes none of it.
What the documented limits say
Published ceilings differ because each maker documents its own host hardware. Two published examples span the range:
| Documented example | Figure | What it decides |
|---|---|---|
| One HMI maker's CompactFlash FAQ | 137 GB reported maximum, small capacity recommended | Startup reads the whole card structure, so stay small for boot speed |
| One in-chassis communication module, CHS addressing | 512 MB maximum | Addressing mode can cap a usable card far below retail sizes |
The second row exists because the CompactFlash standard supports two addressing modes: CHS, where the host works in cylinder-head-sector geometry, and LBA, where it addresses numbered blocks. A host built around CHS reaches only what its geometry allows, and one maker of in-chassis communication modules documents 512 MB as the largest card that works with its module in that mode. A card well under one maker's ceiling can sit above another host's.
When the manual for your model names no limit at all, take the smallest card that holds the project and its logs as the working default and time the boot.
Symptoms and what each points to
- Slower boot right after a capacity increase, same project. The card-structure read is the cause. Time it, size down, retime.
- Card not recognized, or recognized then rejected. The capacity or format sits outside the model's list. Check the model's documentation before buying anything, and follow the same care as the safe swap for a proprietary CompactFlash card.
- Panel starts but shows no project. The project did not come across with the card. The blank-CF-card boot case shows what that looks like and how to reload.
- Same card for years, slower only now. The card swap was never the variable. Note where the delay sits in the startup sequence, and check the supply before replacing hardware.
Change one thing at a time. Swap card, project and format together and the timing comparison is worthless.
Time the boot before and after
Boot time is a measurement you can take with a phone, and it is the same measurement that matters when testing startup and runtime before you buy a panel.
- Write down the card's labeled capacity, plus the size the panel's system information reports if it displays one.
- Time three boots from power-on to the operating screen and keep the middle value as the baseline.
- Note where the delay sits: before the panel's splash screen points at the startup stage; after the splash, while the project loads, points at the card and project.
- Change the card alone, with the same project restored by the documented procedure.
- Retime three boots and compare middle values. A difference of more than a couple of seconds, with nothing else changed, points at the card.
Record both timings on the panel's service sheet. The sheet turns the next swap into a comparison instead of a guess.
Example: one card swap, 33 seconds slower
A maintenance round replaces a panel's original 2 GB card with a 32 GB card of the same type, restoring the project by the panel's documented backup-and-restore path and touching nothing else. The card's structure is the only variable.
- Baseline, original card: three timed boots of 13, 15 and 14 seconds; middle value 14 seconds.
- After the swap, 32 GB card: 46, 48 and 47 seconds; middle value 47 seconds.
- Difference: 47 - 14 = 33 seconds, a 2.4 times longer wait to reach the same operating screen.
The project is byte for byte the one that booted in 14 seconds, so the delay is the larger file structure the panel reads at power-on. The decision follows directly: fit the smallest documented card, restore, and retime. The original card returns to 14 to 16 seconds; the 32 GB card goes on the shelf as a bench spare, labeled with both timings so the next person does not repeat the experiment.
The fix: size down and retime
- Put the machine in a state where the screen can be down for ten minutes, then power the panel off. Never pull a card while the panel is writing to it.
- Back up the working card by the panel's documented procedure, and keep the original card unchanged as the rollback copy. Never reformat the only working card to test a theory. A card carries more than the project file: what saves to a CF card, and when covers the recipe and log writes worth capturing.
- Choose the replacement by the documentation first: the smallest listed capacity that holds the project plus months of logs. If the panel logs to the card, size the budget from your retention numbers; what fills USB storage over months shows how quickly log files grow.
- Install the card and restore by the documented path. Copying files by hand skips whatever the panel keeps outside its project file.
- Power up and retime three boots against the baseline.
Recommendation: Size the card to the smallest capacity the panel's documentation lists, and time every boot you change. When the documentation names no maximum, fit the smallest card that holds the project and a few months of logs, and add capacity only after counting the log budget. With the card sized, the boot should land within about 2 seconds of its baseline; a slower result means the cause sits elsewhere, and the next check is the supply and the startup sequence.
Check the panel before it goes back to work
- The panel reports the card and its capacity without a media error.
- The intended project loads, and every operator screen the crew needs opens.
- Boot time sits within about 2 seconds of the baseline.
- If the panel logs to the card, the first new log entry lands after the swap.
- The card size, the baseline and the final timings are written on the panel record, and the spare card in the drawer carries a label with its capacity.
That record is the deliverable. The next capacity question, on this panel or its spare, then gets answered from numbers instead of memory.
Questions
Does a faster CompactFlash card make the panel boot faster?
Card speed ratings describe how fast a card streams a large file, and cards are sold in capacities from small bench sizes to hundreds of gigabytes with those ratings rising across the range. The documented boot delay comes from the size of the file structure the panel reads at power-on, which follows capacity. A faster card in the same capacity leaves the structure the same size, so change capacity first and keep the timing record.
Can a reformat make a large card behave like a small one?
No. Formatting erases the card and leaves its capacity, and therefore the file structure the panel reads at startup, the same size. It also wipes the project, so back the card up by the panel's documented procedure before any format. When boot time is the complaint, the fix is a physically smaller card, a documented restore, and three timed boots to confirm.
Do the same capacity limits apply to SD and microSD cards?
Check each slot's documentation separately, because panel makers set limits per model and per slot. One panel family documents a 2 GB maximum for its SD card, while the published CompactFlash guidance for another maker reports a 137 GB ceiling and a small-capacity practical recommendation. The boot mechanism is the same for any card the panel reads at power-on, so the smallest documented capacity that holds the project wins.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.