LED video wall shows black: test patterns and screen config

What each symptom points to

A fully dark wall narrows fast once you read the symptoms against each other:

• Every tile dark, every receiving card powered, and the source reports a connected display. The cable and the sending box input are good. The fault sits in the box's output state or in the tile configuration.
• Built-in test pattern dark on every tile. The fault is past the input stage, in the screen configuration or the data path.
• One block of tiles dark while the rest plays normally. That block's data run, its receiving card or its power supply.
• A torn or scrambled picture instead of black. A configuration file written for tiles with a different pixel count or scan mode.
• The source detects no display at all. Source cable or source output format, before anything else.

Power the cabinet down before you open it for any of these checks; the supplies inside are wired to mains.

Match the source to the controller's fixed input

Compact standalone sending boxes of the kind used on shop-floor walls take one fixed input resolution, and on this class of box that input is 1920 x 1080. It is the only input the box takes, so set the laptop or player output to exactly that before you blame anything downstream.

A source that reports a connected display at that resolution has read the sending box's EDID, the VESA data structure a source reads when it plugs in to learn which formats the display accepts. The handshake reaching that point clears the source cable and the box's input stage, so the next checks move to the output side. Resolution mismatches garble other screen feeds the same way; why a 4K portrait signage player shows a quarter of the layout is the same fault on the player side.

Clear blackout, then send a test pattern

Sending boxes carry a blackout function that blanks the output while every indicator on the box looks healthy, which is why it imitates a dead wall so well. Open the management software on a laptop, connect to the sending box, and switch blackout off.

Then send the built-in test pattern. The pattern is generated inside the box, after the input stage, so it needs no source at all. Two outcomes tell you where you stand:

• A pattern on the wall. The box, the data runs and every receiving card are good. The fault is in your source, and the wall needs no further work.
• A dark wall under a test pattern. The input stage is cleared. Two suspects remain: the screen configuration and the data path, and on a wall where every card shows power, the configuration comes first.

Example: reading a P2.5 tile sticker as 128 x 64 pixels

The tile maker is unreachable and you need the numbers the screen configuration asks for. They are printed on the tile.

Inputs, and where each comes from:

• The sticker on the back of a tile, which carries a pitch code and a pixel count. The tile in this example reads P2.5 and 128 x 64, with the rest of the string coding the lamp package and the scan mode.
• A tape measure, for the field check.
• The screen configuration page of the controller management software, where the per-tile pixel size is entered.

The rule: pixel pitch times pixel count gives the tile's face size, and the pixel count is what the screen configuration must declare for every tile the port feeds.

The arithmetic: 128 px x 2.5 mm/px = 320 mm. 64 px x 2.5 mm/px = 160 mm. Check it in the field the other way round: a tile face that measures 320 mm, divided by the 128 pixels in the string, gives 320 mm / 128 px = 2.5 mm/px, and the sticker is confirmed.

Result: every tile shows 128 x 64 pixels on a 320 x 160 mm face.

Decision: the screen configuration must declare 128 wide by 64 high per tile, together with the scan mode coded in the string. A file declaring any other per-tile pixel count was written for a different tile, and a wall running it stays dark, pitch match or no pitch match.

Load the tile maker's screen configuration file

The fix for a wall that powers up and holds dark is the tile manufacturer's screen configuration file, an RCFGX file in this controller family. The file carries the tile's driver settings, decode mode and scan arrangement, and the management software sends it down the data chain to every receiving card. With no file loaded, or a file for another tile, the cards power up and hold dark: the exact symptom in front of you.

Find the file in this order:

• Read the full sticker string from the back of a tile. The maker's support wants the whole string: pitch, pixel count, lamp code, scan code.
• Check the spare tile boxes. The shipping label carries the maker's name, which is how most walls give up their manufacturer years after installation.
• Ask the integrator or electrical contractor who hung the wall for the commissioning file.
• Send the sticker string to the tile maker and ask for the screen configuration file for that exact model.

The management software's automatic tile setup builds a file from its library of common tiles. When your tile is in the library it works; when it is not, the wall stays dark. Treat what the wizard produces as a fallback and check its per-tile numbers against the sticker before you load it.

Work from the sending box outward

The order that finds the fault with the least dismantling:

1. Set the source output to the controller's fixed input, 1920 x 1080 on this class of box.
2. Plug the source in and confirm it reports a connected display. If it does, the source cable and the input stage are good.
3. Switch blackout off in the management software.
4. Send the built-in test pattern.
5. Pattern dark on every tile: get the tile maker's RCFGX file, using the sticker string, and load it to the receiving cards.
6. Only after a correct file fails, reseat both ends of every data run. A wall fed by eight runs from one box does not lose all eight at the same time, so a fully dark wall with powered cards points at configuration, not cabling. A cable certifier settles a single suspect run.

Recommendation: when every tile is dark and every receiving card shows power, set the source to the controller's fixed input, clear blackout, and send a test pattern. If the pattern stays dark, order the tile maker's screen configuration file with the full sticker string from a tile label and load it before you touch the data cabling. Data runs do not all fail at once; one missing tile file explains the whole symptom.

Keep the floor covered while the wall is down

Chasing the file can take days, and an unread status board undoes the reason the wall went up. While you wait on the manufacturer, put the status content on a small panel-mount screen near the line; our shop-floor screens in the panel-mount range play their content offline from a card, with no subscription. When the wall is back, drive it from an Android signage player and the content side stays as simple as the repair.

Questions