Monitoring Every Cell Without Wiring Every Cell

Per-cell battery monitoring is the measurement of each individual cell or jar in a battery string, rather than only the voltage across the whole string. For a large DC plant - a 110 VDC bank of twenty cells backing up signals, switches, or protection equipment - it is the only reliable way to find the one weak cell before it takes the whole string down with it.

The obstacle has never been the idea. It has been the wiring. This article explains why per-cell monitoring matters, why the traditional wired approach stalls at scale, how wireless cell sensors change the economics, and how to get the resulting data into whatever analytics platform you already run. It is written for engineers responsible for battery-backed systems at remote sites, particularly in rail, utility, and transit environments.

Why Doesn't String Voltage Tell You Enough?

String voltage is the total voltage across a series of cells. It is easy to measure, cheap to monitor, and genuinely useful: it shows whether the bank is charging, floating normally, or discharging during an outage. For many small sites it is the right starting point, as covered in our battery monitoring best practices.

Its limitation is arithmetic. In a twenty-cell string, one cell drifting badly low changes the total by only a small fraction. The string looks healthy while one cell is failing - and in a series string, the weakest cell determines how long the whole bank lasts under load.

That failure mode shows up in exactly the places where it hurts most:

• Cold climates, where reduced capacity exposes weak cells during the winter events that most need battery backup.
• Long-float applications, where banks sit fully charged for months and degradation is invisible until the first real discharge.
• High-consequence loads such as switch machines, signals, and protection relays, where a bank that fails early fails safety-critical equipment.

Per-cell data turns an invisible weak cell into a visible trend weeks or months before the discharge that would have exposed it.

Why Does Wired Per-Cell Monitoring Stall at Scale?

The traditional approach measures each cell through a wired connection back to a monitoring device, often through an individual isolated voltage converter per cell so that high string voltages do not reach the monitoring electronics directly.

On one bank, that is manageable. Across a railroad or utility territory it becomes the reason projects never get approved:

Wayside cabinets and substation control houses are often already dense with voltage transducers and protection wiring. Adding twenty converters and twenty conductor runs per bank is frequently where a per-cell project dies - not on cost of hardware, but on the labor and space to install it.

How Does Wireless Cell Monitoring Work?

A wireless battery sensor mounts on an individual cell, draws its operating power from that cell, measures cell voltage, and transmits the reading over a low-power radio link to a collector at the site. The battery voltage monitor family covers this per-cell role.

The architecture has three layers:

1. Cell sensors, one per cell or jar, reporting voltage periodically.
2. A site collection point that receives all the sensor transmissions and presents them as one coherent data set. Depending on the configuration, this is either a gateway alongside an RTU or a function of the RTU itself.
3. The northbound interface that delivers the collected data to wherever it is analyzed.

Low-power wide-area radio technologies are well suited to the job, because cell sensors transmit small readings infrequently and must not drain the cells they measure. When evaluating a wireless approach, confirm three things with the manufacturer up front: whether the collector function is built into the RTU or requires a separate gateway, whether the system can work with a standard third-party gateway if you already run one, and whether any firmware change is needed for your chosen configuration. The answers shape the bill of materials more than the sensor count does.

How Do You Get Cell Data Into an Existing Analytics Platform?

Many organizations that need per-cell data already have somewhere they want it to go: an in-house predictive maintenance system, a system integrator's analytics platform, or an enterprise data historian. The monitoring hardware should serve that platform rather than compete with it.

Practical integration paths:

• IP-to-IP delivery from the site collector to the analytics platform, polled or pushed.
• Receive-and-forward from a gateway, where the analytics platform runs a listener for the forwarded data.
• SNMP, where readings and threshold alarms are delivered as SNMP traps and polled values to any standard manager.
• Modbus, where the collection point exposes values as registers for platforms that already speak Modbus.

The principle is to specify the smallest head end that does the job. If an integrator's platform will do the analysis and presentation, there is no reason to buy a separate monitoring master just to relay data. Most monitoring hardware is managed by third-party systems routinely, and a per-cell deployment should be no different.

Where the same site also has chargers with automatic battery testing, or legacy equipment reporting over contact closures, a single RTU at the site can consolidate those alongside the cell data, so the analytics platform sees one feed per site rather than several.

What Does Per-Cell Data Make Possible?

The payoff of per-cell monitoring is not a new alarm. It is a shift from reactive to predictive maintenance.

• Cell-level trending shows which specific jar is drifting, so replacement targets the failing cell rather than the whole string.
• Discharge profiling during outages or tests reveals which cells sag first under load.
• Fleet comparison across many sites shows whether a problem is local or systemic to a battery model, age cohort, or climate.
• Replacement planning becomes a budget exercise instead of an emergency purchase.
• Environmental correlation with cabinet temperature monitoring shows how heat and cold are aging each bank.

Industries with large installed bases of battery-backed field equipment often talk about predictive maintenance far more than they practice it, largely because the data never existed at the cell level. Removing the wiring barrier is what makes the data practical to collect.

How Should You Scope a Pilot?

A pilot answers the questions no brochure can: radio coverage inside your cabinets, how the collector presents data to your platform, and what the real per-bank cost looks like.

1. Pick two or three representative banks, ideally including one in your harshest climate.
2. Document the bank topology: string voltage, cell or jar count, and whether a site has more than one bank - for example a 110 VDC bank for switches plus a 12 VDC bank for other equipment.
3. Settle the collector architecture before ordering: built-in versus separate gateway, and the northbound handoff.
4. Get a per-bank frame of reference. Integrators especially need a per-bank cost to quote their own customers, so ask for pricing structured that way.
5. Run through at least one discharge event before judging the data.

FAQ: Wireless Per-Cell Battery Monitoring

Why monitor individual cells instead of string voltage?

Because one weak cell changes a long string's total voltage only slightly, while determining how long the whole bank lasts under load. Per-cell data exposes the weak cell before a discharge does.

Do wireless cell sensors need their own power?

Typically not. They draw a small amount of power from the cell they measure, which is why low-power radio technologies suit the application.

Is a separate gateway required?

It depends on the configuration. The collection function may be built into the RTU or provided by a gateway alongside it. Confirm this, and compatibility with any third-party gateway you already run, before ordering.

Can the data go to our own analytics software rather than a vendor platform?

Yes. Data can be delivered IP-to-IP, through a gateway's forward path, over SNMP, or as Modbus registers, so an existing analytics platform can do the analysis without an extra head end.

Is per-cell monitoring worth it for small 12 V banks?

Often not. String voltage monitoring is usually sufficient for small banks. Per-cell monitoring earns its cost on larger, higher-voltage strings backing critical loads.

What should a pilot measure?

Radio coverage inside the actual cabinets, how data arrives at your platform, real per-bank cost, and cell behavior through at least one discharge event.

Get A Free Consultation

If per-cell battery monitoring has stalled on the wiring rather than the value, a wireless approach can make it practical across a fleet of cabinets. DPS Telecom can help you scope the collector architecture, match the northbound interface to the platform you already use, and provide per-bank pricing you can plan around. Get a Free Consultation, or call 1-800-693-0351 or email sales@dpstele.com.

Andrew Erickson

Andrew Erickson is an Application Engineer at DPS Telecom, a manufacturer of semi-custom remote alarm monitoring systems based in Fresno, California. Andrew brings more than 19 years of experience building site monitoring solutions, developing intuitive user interfaces and documentation, and opt...