Battery BMS Telemetry for Electric Machines

Electric machine OEMs ship battery systems without continuous field visibility. The BMS tracks cell voltage, thermal events, fault codes, and charge-cycle history, but that data remains on the machine after it leaves the factory. Melqart Systems deploys a CAN-to-cloud edge gateway on each machine, delivering real-time SOC, SOH, fault streams, and thermal telemetry to the fleet platform without modifying BMS firmware.

Rows of battery cells with red and blue terminals
Battery Data Visibility Gap

The BMS leaves the factory, but its data remains on the machine.

Electric machine OEMs invest heavily in battery technology but lose visibility when machines enter service. The BMS tracks cell voltage, thermal events, charge cycle counts, fault history, and degradation curves. Without an edge connectivity layer, this data does not reach engineering teams. Warranty disputes remain unresolved because field evidence is missing. Field failures are diagnosed by replacing parts rather than reading fault logs. Battery degradation patterns that could inform the next product generation are lost. Melqart Systems extracts structured BMS telemetry from the CAN bus or RS-485 interface, normalizes it at the edge, and delivers it continuously to the fleet platform.

Electric forklift in a warehouse beside stacked panels
01

Real-time battery health streaming

Continuous SOC, SOH, cell voltage, and temperature telemetry from every machine in the field, not just when a fault occurs.

02

Fault-code transparency

BMS fault codes and error events streamed to your platform the moment they occur, with contextual operating data to support remote diagnosis.

03

Non-invasive CAN integration

Edge gateway reads from the CAN bus or RS-485 interface without firmware changes to the existing BMS, compatible across battery suppliers.

04

Fleet electrification visibility

Unified telemetry layer across your electric machine range: one data pipeline for SOC, SOH, charge cycles, and thermal events across every model.

The challenge

Where current approaches fall short

01

Warranty disputes without field evidence

Without field BMS telemetry, teams cannot distinguish genuine product failure from operator misuse or improper charging. Warranty claims are resolved by cost rather than data, and engineering teams gain no product insight from them.

02

Battery degradation goes undetected until failure

Cell voltage drift, capacity loss, and thermal anomalies develop over hundreds of cycles. Without continuous SOH monitoring from the field, degradation is invisible until it becomes a field failure or a customer complaint.

03

Mixed electric fleets lack unified telemetry

As OEMs electrify their machine range, each model may use a different BMS supplier, protocol, or data format. Without an OEM-agnostic edge layer, each product line becomes a separate, isolated telemetry problem.

Architecture

How BMS edge connectivity works

Melqart Systems connects directly to the machine's BMS interface, normalizes battery telemetry at the edge, and delivers structured data to the fleet platform over cellular connectivity without modifying BMS firmware.

  1. 01

    BMS Interface

    CAN/J1939 or RS-485/Modbus tap

  2. 02

    Edge Gateway

    Normalization, buffering, fault detection

  3. 03

    Cellular Uplink

    LTE/4G with store-and-forward

  4. 04

    Fleet Platform

    Structured telemetry via MQTT or REST

What's included

The Deployment Package

A complete BMS edge connectivity stack: interface integration, edge normalization, cellular connectivity, and fleet platform delivery, ready for serial deployment across your electric machine range.

01

BMS Protocol Integration

CAN/J1939 bus decoding and RS-485/Modbus integration for direct BMS data extraction. Compatible with major battery suppliers across mobile machine, forklift, and energy storage applications.

02

SOC & SOH Telemetry

Continuous State of Charge and State of Health streaming with configurable resolution. Cell-level voltage and temperature data normalized to a consistent schema for fleet analytics.

03

Fault Code & Event Streaming

BMS fault codes, thermal alerts, and protection events delivered to your platform in real time with contextual operating data at the moment of occurrence.

04

Edge-Buffered Cellular Connectivity

LTE/4G primary connectivity with local edge buffering for guaranteed telemetry delivery during coverage gaps, designed for mobile machines operating in remote or urban-fringe environments.

Charging connector plugged into an electric vehicle
On electric vehicles and charging infrastructure, BMS data has to leave the battery and reach the cloud.
Specifications

Technical specifications

BMS Interface Protocols

CAN 2.0A/B (J1939 application layer), RS-485 Modbus RTU, SMBus. Compatible with major battery suppliers including CATL, BYD, Pylontech, and custom OEM BMS architectures.

Battery Parameters Captured

State of Charge (SOC), State of Health (SOH), individual cell voltage, pack temperature, current, fault codes, charge cycle count, and protection event history.

Connectivity

LTE/4G primary with multi-carrier SIM for global deployments. Store-and-forward edge buffer ensures guaranteed telemetry delivery during cellular coverage gaps.

Edge Hardware

Open Linux telematics gateway built for industrial machines, available in enclosed and ruggedized variants for indoor or outdoor installation.

Telemetry Rate

Configurable from 1Hz continuous to event-triggered streaming. Burst logging at higher resolution during fault conditions or thermal events for post-incident analysis.

Integration Standards

MQTT or REST for cloud delivery. JSON or Protobuf payload formats. Compatible with time-series databases (InfluxDB, TimescaleDB) and major fleet telematics platforms.

Open Linux telematics gateway
Open Linux telematics gateway for battery-powered industrial machines.
Applications

Use cases and industries

01

Electric Crane OEMs

Remote battery diagnostics for electric mobile cranes: tracking SOH degradation across the rental fleet and generating warranty-evidenced fault logs for all field service calls.

02

Forklift Fleet Operators

SOC and SOH monitoring across large forklift depots: proactive identification of degraded packs before they cause shift disruptions, and charge cycle analytics to optimize charging schedules.

03

Electric Construction Equipment OEMs

Connectivity layer for new electric excavator and loader product lines: real-time BMS telemetry from day one, with fleet health analytics for the product engineering team.

04

Battery Energy Storage Systems

Pack-level SOC and SOH telemetry for stationary BESS deployments: real-time visibility across cell strings, thermal management monitoring, and degradation tracking against IEC 62619.

05

Warranty & After-Sales Teams

Field usage evidence for warranty claim resolution: charge cycles, thermal history, fault log context, and operating condition data at the time of the reported failure.

Results

Key outcomes

“From isolated battery data to continuous fleet health visibility, across every electric machine.”
  • Continuous SOC and SOH streaming from every electric machine in the field.
  • Real-time fault code and thermal event delivery with full operating context.
  • Non-invasive CAN/RS-485 integration: no BMS firmware changes required.
  • Multi-vendor compatibility across battery suppliers and machine models.
  • Warranty-evidenced field data for dispute resolution and product improvement.
  • Serial deployment-ready: the same edge gateway and integration stack across the full electric range.
Cover of the Battery BMS telemetry solution datasheet
Solution datasheet

Battery BMS telemetry

State of charge, state of health, fault codes and temperatures from every electric machine, read over CAN or RS-485. No BMS firmware change, subject to protocol documentation.

MS-DS-BAT-2026-58 · PDF · 6 pages · English

FAQ

Frequently asked questions

01

How do we get battery BMS data to the cloud without changing BMS firmware?

An edge gateway taps the existing BMS interface (CAN 2.0A/B with the J1939 application layer, RS-485 Modbus RTU or SMBus) and forwards the data to your fleet platform. The integration is non-invasive and requires no BMS firmware changes.

02

Which battery parameters are captured?

State of Charge (SOC), State of Health (SOH), individual cell voltage, pack temperature, current, fault codes, charge cycle count and protection event history.

03

Which battery suppliers are supported?

Major battery suppliers including CATL, BYD and Pylontech, as well as custom OEM BMS architectures.

04

Which gateway hardware is used on the machine?

An open Linux telematics gateway built for industrial machines, available in enclosed and ruggedized variants for indoor or outdoor installation. It reads the BMS on the machine and publishes the data over LTE/4G.

05

How is battery telemetry delivered to our platform?

Over MQTT or REST, as JSON or Protobuf payloads, compatible with time-series databases such as InfluxDB and TimescaleDB. A store-and-forward buffer on the gateway holds data through cellular coverage gaps.

Bring battery visibility to electric machines in the field.

Melqart Systems designs the BMS interface, edge normalization, and fleet telemetry pipeline, delivering structured battery health data from day one in the field.