Battery Communication Loss vs Loss of UPS Backup Power

Highidea offers online UPS configurations with built-in and external LiFePO4 storage. Separating these layers helps you specify the right host, battery and monitoring arrangement for the service you need to protect.

Draw three paths, not one “battery connection”

The data path carries measurements and status. A displayed charge percentage may be an old value after updates stop. Record its age and validity, rather than treating the last number as a current measurement.

The permission path determines whether charging or discharging is allowed. Depending on the architecture, it may use electrical signals, digital messages or internal controls. A communication fault can affect this permission even while the physical battery connection remains intact.

The power path carries energy. Its availability also depends on protection devices, switching and the host's operating state. Valid data alone cannot establish that this path can support the intended load.

Victron's BMS design guide illustrates separate control signals and physical disconnection arrangements for its own products. It is useful architectural background, not a response specification for another manufacturer's UPS.

Classify the observation before deciding the response

Unknown fields should remain unknown. A receiver can lose contact with the monitoring card while the card still communicates with the UPS; that is a different boundary from a host losing contact with its battery.

Two planning examples

In a hypothetical mains-powered rack, the dashboard freezes while the host continues supplying the load. The immediate observation supports a visibility problem. It does not establish how the battery will behave at the next outage. Keep the load protected and use the approved support route to resolve that uncertainty.

In a hypothetical integrated system, loss of a required battery message causes discharge permission to be withdrawn. The energy connection might remain physically present, but backup is unavailable under that control state. The correct response follows the agreed host/BMS behavior, not an assumption that a connected cable guarantees service.

Neither example is a Highidea test result. Do not unplug battery communications on a live system to discover which case applies.

Put the behavior into the configuration request

Ask the host and battery suppliers to answer one shared record:

• Which link is supervised, and how is stale or missing information indicated?
• What happens separately to charging, discharging and output when that link fails?
• Which observations remain trustworthy, and through which approved interface?
• Who receives the alarm, protects the service and authorizes recovery?
• What conditions must be satisfied before the system returns to normal operation?

For abnormal heat, swelling, smoke or odor, prioritize the site's emergency procedure and safe separation; do not approach equipment for better readings.

Select the complete battery route

Our ET1-3KR provides a rack-mounted online route with built-in LiFePO4 storage. External-storage projects additionally need the exact host/battery/interface combination. Send Highidea the equipment identities, load, required backup task and integration diagram so the configuration discussion covers data and power together.

Technical references

• Victron: BMS signals and system design, §3.2.
• RFC 1628: UPS battery, output-source and communication-alarm objects. These are protocol definitions; available objects depend on the installed equipment.