Cabinet Configuration File Import & Brightness Adjustment: A Practical Guide for LED Engineers
Using the NovaStar control system as our example, this guide covers when and how to import cabinet configuration (rcfg) files, and how manual and automatic brightness adjustment work — essential skills for commissioning and maintaining any COB LED display project.
- A field story: why "plug it in and it works" is a myth
- What is a cabinet configuration file — and when must you import one?
- Importing a cabinet config file: the standard workflow
- Brightness adjustment: the manual approach
- Brightness adjustment: the automatic approach
- Why this matters even more for COB LED displays
- Key takeaways + FAQ
1. A Field Story: Why "Plug It In and It Works" Is a Myth
Almost every LED engineer has lived through this moment: the cabinets are stacked, every Ethernet cable is seated, the sending card is detected — and yet the screen lights up as a mosaic of garbled tiles. Some cabinets show content, others stay black, and the image is offset in ways that make no sense. After an hour of troubleshooting, the root cause turns out to be simple: the replacement receiving card was never loaded with the correct cabinet configuration file.
An LED display is not a television. Every receiving card must be told exactly what it is driving: the module resolution, the scan mode, where each RGB data group starts. All of that lives inside the cabinet configuration file. Mastering these routine control-system operations — config file import and brightness adjustment — is what separates a cable installer from a commissioning engineer.
2. What Is a Cabinet Configuration File — and When Must You Import One?
2.1 The rcfg file in one sentence
The cabinet configuration file (commonly a .rcfg file) is the receiving card's ID card and blueprint combined. It stores the module resolution, scan mode, driver IC type, RGB data group mapping, and OE polarity. Only after the sending card delivers this file does the receiving card know how to drive every module inside its cabinet.
2.2 Four scenarios where import is mandatory
① First power-on of a new screen
After mechanical installation, the manufacturer's rcfg file must be imported and sent to the cards before the wall can display anything correctly.
② Replacing a receiving card
A new or repaired card ships blank or with mismatched parameters. It needs the correct configuration sent and saved before it will behave.
③ Swapping or servicing cabinets
When a spare cabinet joins the wall — especially from a different production batch — its matching config file must be imported.
④ Firmware or hardware changes
After a receiving card firmware upgrade, a rewiring change, or a driver IC revision, the updated configuration must be pushed out again.
3. Importing a Cabinet Config File: The Standard Workflow
The steps below follow NovaLCT, the most common software path in today's LED display control systems:
- Connect the hardware: Link your PC to the sending card over Ethernet and confirm the sending and receiving cards are detected.
- Log in to the software: Open NovaLCT and sign in (default credentials are typically admin or 666).
- Open screen configuration: Navigate to the "Screen Configuration" or "Cabinet Configuration" section.
- Load the config file: Click "Load/Import" and select the .rcfg file supplied by the cabinet manufacturer.
- Send to the receiving cards: Verify the parameters, then send the configuration to the selected cabinets or the entire wall.
- Save to hardware: Execute "Save to Hardware" so the configuration survives power cycles.
- Verify the picture: Run test patterns (solid colors, diagonals, grids) and check for color shifts, offsets, or dead tiles.
4. Brightness Adjustment: The Manual Approach
Manual adjustment is the workhorse during commissioning: in NovaLCT's brightness panel you drag a slider or enter a value (typically 0–255 or 0–100%) and the wall responds in real time.
4.1 Where manual adjustment earns its keep
Baseline setting at handover
Before delivery, set a brightness baseline that suits the environment — meeting room, showroom, or outdoor advertising site.
Preparing for calibration
Before point-by-point calibration, brightness and color temperature are set to a uniform reference so the calibration data is accurate.
Low-brightness optimization
Indoor COB LED displays often run at 100–300 nits. Pulling brightness down manually, together with low-grayscale tuning, prevents color cast at dark levels.
Live-event firefighting
When a client on site says "a bit dimmer, please," the manual slider is the fastest answer you have.
5. Brightness Adjustment: The Automatic Approach
Automatic adjustment lets the screen respond to its environment without human supervision. There are two common implementations:
5.1 Ambient light sensor adjustment
A photocell mounted on the display feeds real-time ambient light readings to the control system, which follows a preset brightness curve: ramping up under harsh daylight for legibility, and dimming at night to avoid glare and light pollution. This is standard practice for outdoor LED displays.
5.2 Scheduled (time-based) adjustment
No sensor required — you define a timetable in the software. For example: 7:00–18:00 at 80%, 18:00–23:00 at 40%, and 15% after 23:00. This suits sites with predictable lighting conditions or where installing a sensor is impractical.
6. Why This Matters Even More for COB LED Displays
COB (Chip on Board) packaging bonds LED dies directly onto the substrate, delivering ultra-fine pixel pitches and excellent protection — which is why it dominates premium indoor display. But small pitch and high cabinet counts raise the bar for control-system discipline:
Stricter configuration management: A P1.2 COB video wall easily spans a hundred cabinets. On a high-density image, a single cabinet with a mismatched rcfg file is impossible to miss. A disciplined "import → send → save → verify" routine is what gets a project lit up right the first time.
Low-brightness quality defines the experience: COB walls live in meeting rooms and control centers, running at low brightness for years. The manual brightness baseline — paired with gamma and low-grayscale tuning — directly shapes grayscale smoothness, while the automatic brightness policy determines energy consumption and LED lifespan.
7. Key Takeaways
| Topic | What to Remember | One-Line Rule |
|---|---|---|
| Cabinet config file (rcfg) | Stores module resolution, scan mode, and data mapping — the receiving card's blueprint | New card in, config in — then save to hardware |
| When to import | First power-on, card replacement, cabinet swap, firmware upgrade | Hardware changes mean re-sending the config |
| Import workflow | Connect & log in → screen config → load rcfg → send → save → verify | Six steps; verify small before saving wall-wide |
| Manual brightness | Real-time slider or value input for baselines and quick fixes | Brighter isn't better — 30%–60% for indoor daily use |
| Automatic brightness | Light sensor follows ambient conditions; schedules follow the clock | Sensors for outdoors, schedules for predictable sites |
| COB specifics | More cabinets, finer pitch — config discipline and low-brightness tuning matter more | High density magnifies every parameter error |
FAQ
Q1: The picture is still garbled after importing the config file. What now?
First confirm the rcfg file matches the module model and batch. Then check that the Ethernet cabling order matches the cabinet layout in the software. Finally, make sure you saved to hardware and power-cycled the screen.
Q2: What happens if I forget to save to hardware?
The configuration lives only in the receiving card's runtime memory. After a power cycle it is lost, and the screen reverts to its previous state — or no configuration at all. You'll need to re-send and save again.
Q3: What brightness level is recommended for an indoor COB LED display?
Meeting rooms and control centers typically run at 100–300 nits (roughly 20%–40% of full range), tuned to ambient light and viewing comfort — with low-grayscale optimization to prevent color cast.
Q4: Can sensor-based and scheduled modes work together?
Yes. A common setup uses the light sensor as the primary input with the time schedule as a fallback, so brightness stays reasonable even if the sensor fails or reports bad data.
Q5: Where do I get the rcfg file?
From your cabinet or module manufacturer — it is generated for that specific hardware batch and shipped with the goods. Never reuse a config file from another project; request the batch-matched file from your supplier.
Planning a COB LED Display Project?
We support the full workflow — from cabinet configuration and point-by-point calibration to brightness strategy. Ask us for the spec sheet and a configuration management plan.
Get a Technical ProposalDisclaimer: This article is adapted from Chapter 5, "Common Control System Software & Hardware Operations," of the NovaStar NCE certification textbook "LED Display Application — Beginner Level," rewritten for technical discussion and learning purposes only. Textbook copyright belongs to the original publisher; NovaLCT and NovaStar are trademarks of NovaStar Tech Co., Ltd.
