A panel the PC recognizes on USB after a firmware update, with a dark screen and a greyed-out transfer button, is usually stalling partway through startup because the 24 V DC supply cannot carry the full boot load. Measure the terminals during power-up, compare the supply's current rating with the panel nameplate, and fix the supply before you retry the update or the transfer.
A firmware update that ends with a panel the PC can see but cannot talk to is usually not a firmware fault. The update finished, the panel rebooted, and the reboot stalled partway because the 24 V DC supply cannot carry the panel's full startup load. That is why the PC still recognizes the panel on USB while the screen stays dark, the transfer button stays greyed out, and Ethernet discovery finds nothing. USB enumeration runs on a few watts. The display and the network port cost far more. Check the supply before you touch the panel again. Repeating a firmware write on a brown-out supply is how a wiring job turns into a boot-loader repair.
What each symptom points to
Work down the rows until you find yours, and take the check in the last column.
| Symptom | What it points to | Next check |
|---|---|---|
| PC recognizes the panel on USB, screen dark | Boot reached the USB stage and stalled; the cheap circuits are up, the expensive ones are not | Measure the panel's power terminals during power-up |
| Transfer button greyed out | No ready panel answered the software, so the software keeps the button disabled | Watch a complete boot before reopening the software |
| Ethernet discovery finds nothing | The network stack loads late in boot and never came up | Same terminal measurement; discovery returns once the screen works |
| Holding the corner of the screen for 3 seconds does nothing | The touch handler lives in software that never finished loading | Stop repeating the gesture; it cannot run until boot completes |
| Power LED lit, second LED red or flashing, screen dark | Power is present and startup has faulted | Use the manufacturer's documented recovery procedure |
| Screen dark only after the panel sits idle | Idle screen-blank setting, the same idea a PC uses | Check the display timeout once the panel is up |
The first row is the one that matters here. The next two rows are its consequences on the software side.
Why the PC still sees a panel with a dark screen
The USB device stage is one of the first circuits up and among the cheapest to run. The USB 2.0 standard allows a connected device up to 500 mA at 5 V, which is 2.5 W, and a panel needs little more than that to complete enumeration. The display and its backlight are the biggest load on the DC rail. The Ethernet port and the network stack come up last. When the supply is undersized or aged, its output collapses the moment the big loads switch in, and the late-loading stages drop out. What is left is a panel that enumerates and a screen that never lights.
The update is when the margin ran out; the supply is the part that failed. A unit can also read a healthy voltage with no load and collapse under it, so measure with the panel connected and booting. The same power arithmetic explains an HMI that goes blank and freezes during a shift. Undersized power can also resurface later as an intermittent PLC communication timeout once the panel is running.
Check the supply before you retry anything
Work down the checks in order and stop when one names a fault.
- Read the panel nameplate. It prints the supply voltage and the current the panel draws, for example 24 V DC at 1.0 A. The installation manual repeats it.
- Compare the supply label. The output voltage must match the nameplate and the current rating must meet or beat it. A 12 V unit cannot boot the panel; a 48 V unit can damage it.
- Measure during power-up. Set a meter to DC volts across the panel's power terminals and watch a full boot. IEC 61131-2, the standard for industrial control equipment supplies, rates a nominal 24 V DC supply between 20.4 V and 28.8 V at the terminals. A reading that dips below 20.4 V during startup names the supply. A reading that holds inside the band with the screen dark moves the fault to the panel.
- Check for shared loads. Valves, contactors and lamps on the same rail pull the terminal voltage down when they switch; a DC rail shared with solenoid coils is a classic cause of a panel that runs until something else switches on.
- Check the wire size and run length. Copper losses eat into the 20.4 V floor. The example below shows when they matter and when they are noise.
Example: is the supply big enough?
Example: The nameplate reads 24 V DC, 1.0 A, so the panel can draw up to 24 W (24 V × 1.0 A). The installed supply is rated at 0.5 A, which is 12 W. Startup then goes like this:
- The logic and the USB stage come up first at a few watts, and the PC's enumeration succeeds.
- The backlight and the Ethernet PHY switch in, and the load heads toward 24 W against a 12 W supply.
- The supply hits its limit, the terminal voltage falls below the 20.4 V floor, and every stage that loads late drops out.
The result is the exact symptom set: a PC that sees the panel and a screen that never lights. The arithmetic says capacity is the fault, because 12 W / 24 W = 0.5, half the required power. A replacement rated for 1.5 A, which is 36 W, carries the nameplate with 50% headroom for startup peaks.
Wiring on the same panel: 22 AWG copper is about 0.016 Ω per ft, so a 10 ft run counts both conductors, 20 ft of copper, and loses about 0.32 V at 1.0 A (20 ft × 0.016 Ω × 1.0 A = 0.32 V). That is trivial next to the 3.6 V between 24.0 V and the 20.4 V floor. A 100 ft run loses about 3.2 V and leaves 20.8 V at the terminals, close enough to the floor that one shared load switching on pushes the panel under it. Short runs on ordinary control wire are noise; long runs need a larger wire size.
The fix
- Lock the panel out. Open the disconnect and verify zero volts at the supply output before rewiring. The input side of the supply is line voltage.
- Install the corrected supply. Voltage matches the nameplate, current rating meets or beats it with headroom for startup, mounted and fused per the supply's own manual.
- Rewire the power pair. Polarity and terminal tightness as the panel manual prints them, routed away from motor and coil wiring.
- Apply power and watch the whole boot. The screen lights first, and Ethernet discovery returns only after the panel finishes starting.
- Run the transfer. Open the programming software, confirm the panel is discovered, transfer the project, and leave the panel powered through the entire write.
- Power-cycle once and confirm. The project should come up on its own, and the panel should answer discovery on every repeat of the cycle.
You are done when the screen lights on every start, discovery answers every time, and a transfer completes without the panel dropping off. If a transfer still fails with a healthy supply and a fully booted panel, that fault has its own article: a project restore that fails after reboot.
Recommendation: Before you retry the firmware update or the project transfer, measure the DC terminals at the panel while it boots and compare the supply's current rating with the nameplate. Replace the supply if the rating sits under the nameplate or the terminal voltage dips below 20.4 V during startup. Retry the write only after the screen lights on its own; a panel that enumerates on USB with a dark screen is asking for power, not for another update.
If the supply passes and the screen stays dark
If the terminal voltage holds inside the band through a full boot and the screen is still dark, work this list.
- Read the status LEDs. A lit power LED with a red or flashing status LED and a dark screen is a startup fault. Use the manufacturer's documented recovery procedure for the exact model. One documented procedure requires the USB stick in FAT32 format and USB 2.0 or lower; your panel manual prints the requirements for your model.
- Stop if recovery fails. A recovery tool that cannot load the firmware points to a corrupted boot loader or flash, and that panel is a manufacturer service case.
- Check the backlight path. If the panel reports a backlight error after power up, work that checklist before anything else.
- Check the blank timer. A screen that goes dark after the panel sits idle and returns after a power cycle is a display timeout setting, changed in the panel's settings menu once it boots.
Keep firmware writes off the panel until the power question is settled. That is what protects the boot loader.
Questions
Where exactly should I measure the supply voltage?
At the panel's own power terminals, with the panel connected and booting, not at the supply's output with the load disconnected. A supply can read a healthy 24 V unloaded and collapse when the display stage switches in. Set the meter to DC volts across the terminals and watch the reading through the first minute of startup; a dip below 20.4 V names the supply.
How much headroom should the replacement supply have?
Rate it at or above the nameplate current and add margin for startup peaks: 1.5 A against the 1.0 A nameplate in the example is 50%. If the same supply feeds a second small load such as a stack light, add that load's nameplate current before you size the margin. A nominal 24 V DC unit is correct; 20.4 to 28.8 V at the terminals is the accepted band.
Why did Ethernet discovery work before the update?
A supply with no headroom can finish one boot and stall the next, because boot order and load timing decide where it stops. The update rebooted the panel into a boot it could no longer complete, and the network stack loads late, so discovery was the part that dropped. Measure the terminals with the panel booting before you blame the firmware.
Does rebooting fix the problem permanently?
A reboot clears a brown-out until the next heavy load switches in. With a supply that has no headroom, the panel boots once and then stalls again on the next power-up or when another device on the rail pulls current. Use one reboot as a test. If the fault returns, measure the terminal voltage during startup and size the supply from the nameplate.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.