English

Home › Battery Management Systems (BMS)

BMS platform

Battery Management Systems (BMS)

BMS development is half of the company's focus — lithium-ion power battery modules and BMS solutions. Across the catalogue the management layer appears in three forms: protection boards with voltage thresholds in the small packs, communication BMS in the industrial systems, and monitoring options on the power batteries.

Illustration of a green circuit board with a chip

Key data — Battery Management Systems (BMS)

Protection boardsThresholds on the 14.8V polymer pack; built-in BMS/PCB in the shop 18650 packs
Communication BMSRS-485 with host software (AGV battery); CAN + RS-485 (450Ah system); CAN for PLC with SOC ≤5% (250Ah system); RS485 / CAN / RS232 (storage unit)
Monitoring optionsBluetooth phone-app readout (12.8V 200Ah LiFePO4)
IntegrationProtocols supplied for host integration on the communication models

Protection, communication and monitoring: the three tiers in service

The tiers are visible in the catalogue's own models. Protection tier: the 14.8V 10Ah polymer pack gives its board's thresholds as voltages — over-charge protection at 16.8V±0.05V and over-discharge at 12.0V±0.25V — and the shop's 18650 packs carry built-in BMS/PCB (maximum charge and discharge ≤2A, adjustable, on the 2S3P pack; a 12.6V charge voltage and 9V discharge cut-off on the 3S3P). Communication tier: the 48V 40Ah AGV battery runs RS-485 with host-computer software and the protocol supplied; the 48V 450Ah forklift system runs CAN plus RS-485 with protocol; the 48V 250Ah system provides its CAN protocol for PLC reading with SOC accuracy of ≤5%, with a BMS electrical schematic in its documentation; the 24V cold-storage battery runs RS-485 with protocol; the 51.2V storage unit offers RS485, CAN and RS232. Monitoring tier: the 12.8V 200Ah battery's Bluetooth option puts state of charge on a phone app — the right tier for a vehicle or installation with no host system to report to.

Specifying a tier is an integration decision

A standalone device needs protection and nothing else. A vehicle in a managed fleet needs communication, and the protocol choice (CAN for vehicle and machine networks, RS-485 for industrial hosts, RS232 still present on the storage unit for legacy energy systems) should follow the host, not the battery. Retrofitting communication onto a protection-tier pack is not a configuration change; it is a different build, which is why the tier belongs in the first enquiry, not the last. The enquiry facts a BMS specification needs: the pack's series and parallel arrangement; the continuous and peak discharge the board must carry, with the peak's duration; the charge current; the host interface where communication is required; and the data set the host will consume — pack voltage, current, state of charge, fault flags. With those facts, the tier decision becomes a specification rather than a preference.

Two failure patterns worth naming

Both are common, and both are specification-stage cheap to prevent. Undersized boards: a protection board chosen at the pack's continuous figure with no margin for the peak becomes the fuse the design never intended — the AGV battery pairs a 120A pulse with 40A continuous, and the 450Ah system a 600A peak with 250A continuous, so the board can be specified against both. Unowned data: a communication BMS whose host software was never scoped delivers a port, not a system — the AGV battery is the counterexample, supplied with host-computer software and protocol as part of the model, and the 250Ah system provides its protocol for the PLC that will read it.

Worked example: reading a fleet's SOC argument

A warehouse reports its AGV fleet 'losing capacity' after a year. The BMS data is where the argument is settled: the packs report state of charge over RS-485, and the fleet log shows the vehicles returning at 35% and leaving at 90% — a 55% working window, inside which the packs have not lost capacity at all; the routes grew. Without communication, the same complaint becomes battery replacements bought to fix a routing fact. The ≤5% SOC accuracy of the 250Ah system is what makes such arithmetic trustworthy on the machine side: at 250Ah, a 5% band is 12.5Ah, small against a shift's throughput, and small enough for a PLC to schedule charge windows from the battery's own report. Enquiry questions: the host system's protocol and polling model, the fault flags the fleet software will consume, and whether SOC or full telemetry is the actual requirement.

Choosing a tier by the conversation the battery must hold

The tiers on this page sort by audience. A pack whose only audience is its own protection — over-charge, over-discharge, over-current, short-circuit — needs the protection tier and nothing more; most device and polymer packs live there, on protection lines alone. A pack whose audience is a charger and a display needs the reporting tier. A pack whose audience is a fleet host needs the communicating tier — the AGV battery's RS-485 with host-computer software and protocol is the catalogue's worked example. A pack whose audience is a machine controller needs the integration tier — the forklift systems' CAN arrangements, and at the top of it the 250Ah system's CAN-for-PLC provision with ≤5% state-of-charge accuracy, where the machine schedules its own work against the battery's reports. Specifying a tier above the audience wastes money; specifying below it wastes the machine. The enquiry should name the audience first.

Protection numbers are specifications too

Where a pack's protection thresholds are given as voltages with tolerances — the 14.8V 10Ah model's over-charge and over-discharge protection voltages are the worked example — they deserve the same reading as the capacity figure. The over-charge threshold is the ceiling the charger and the board agree on; the over-discharge threshold is the floor the load must respect; the tolerances are the honesty of both. A management specification written for a custom pack should state its thresholds the same way — as voltages with tolerances, per cell or per pack, with the recovery behaviour named (auto-recovery, as on the 9V accessory's short-circuit protection, or latching) — because the protection system is the part of the battery that acts when everything else has already gone wrong, and its specification is not the place for adjectives.

Failure behaviour is a specification

A management system's most important lines are the ones describing what it does when things go wrong: the protection thresholds, the recovery behaviour after a short circuit (auto-recovery on the catalogue's accessory charger, or latching until inspected), the alarm path on a communicating tier, and the lockout behaviour a machine's PLC can command on an integration tier. Specifications that name these behaviours — with voltages, currents and timings — can be tested; specifications that describe them as features cannot. Buyers writing a management brief should use the same form the models themselves use: thresholds as numbers with tolerances, recovery as a named behaviour, reporting as a named protocol. The battery will spend almost all of its life in the normal case; it will be judged, and possibly its machine with it, on the abnormal one.

Related pages