Eaton XV HMI — Not Detected & Bootloader Mode

Eaton · intermediate · 25 min

An Eaton XV HMI/PLC that won't be found by GALILEO or XSOFT-CODESYS is usually a subnet or cable problem — or the device sitting in bootloader mode. Learn to get on the right subnet, recover from bootloader, and reload the application.

ℹ️ An Eaton XV panel is programmed and visualised over one Ethernet port — GALILEO for the HMI and XSOFT-CODESYS for the PLC. If it isn't detected, get your PC on the device's subnet first; if it's stuck in bootloader mode, recover it and reload the app.

One port, two tools

Eaton XV series devices (XV100, XV300…) are combined HMI/PLC units. The Ethernet interface is used both for engineering the 'GALILEO' visualization and for programming the PLC with 'XSOFT-CODESYS'. So a connection problem blocks both — fix the link once and both tools can reach the device.

If the device isn't detected

Work the basics in order:

1. Cable/port — if connecting over USB, try a different USB cable/port; a charge-only or flaky cable is a common cause.
2. Subnet — over Ethernet, set your PC to the same subnet as the device's default IP (often 192.168.1.10 or 192.168.0.1). A PC on a different subnet simply won't see the panel.
3. Address/port in the tool — select the correct IP (or COM port) in GALILEO / XSOFT-CODESYS.

Recovering from bootloader mode

If the device is sitting in bootloader mode (firmware not running the application), use the Eaton Bootloader Tool — it automatically detects the XV device in bootloader mode, or you can select the COM port or IP address manually. Once connected:

• Restore the firmware if needed.
• If the firmware is restored but the application is missing, use XSOFT-CODESYS or Galileo to download the application project back to the device.
• If it stays stuck in bootloader mode despite recovery, that indicates a possible hardware failure — contact Eaton support.

Step-by-step

1. Not detected over USB? Swap the cable/port.
2. Not detected over Ethernet? Put your PC on the device's subnet (e.g. 192.168.1.x for a 192.168.1.10 device) and select the right IP in the tool.
3. In bootloader mode? Use the Eaton Bootloader Tool (auto-detect, or set COM/IP) to recover the firmware.
4. App missing after recovery? Download the project via XSOFT-CODESYS (PLC) / GALILEO (HMI).
5. Still stuck in bootloader? Treat as hardware — contact Eaton support.

Never do this

Don't keep re-flashing a panel that returns to bootloader mode after a good recovery — Eaton's own guidance is that persistent bootloader mode points to a hardware failure. Confirm the subnet/cable first, do one clean recovery, and if it won't hold, escalate rather than repeatedly re-flashing.