Integrated lithium battery energy storage solutions

Communication Protocol|ICD engineering

From interface definition to anomaly recovery — make the system truly interoperate

Protocol customization covers physical interfaces, message semantics, timing, exception recovery and version compatibility across BMS, PCS, EMS, fire, metering and customer SCADA.

Sample message Demo data
Signal
MaxChargePower
ID
0x18FF50E5
Value
320.5 kW
Quality
GOOD
  • Endpoints & roles

    Endpoints & roles

    Ownership, authority and control priority.

  • Signal dictionary

    Unified signal dictionary

    Names, units, scale and quality flags.

  • CAN / link / handshake

    State & command handshake

    Observable, controllable, verifiable.

  • Heartbeat & recovery

    Anomaly recovery & joint verification

    Defined degrade paths and staged prove-out.

Device boundaries & role map

Role band plus control-priority ladder — one ICD owns who may override whom Demo data

  • BMS Limits · contactors · 0x1xxx
  • PCS Power · grid codes · 0x2xxx
  • EMS Schedule · setpoints
  • HVAC Thermal aux links
  • Fire Dry contact + CAN
  • Meter Energy / PQ tags
  • Gateway Protocol bridge
  • Tool Service · audited

Line legend

  • CAN FD Control / high rate
  • RS485 Aux / meter
  • Ethernet Northbound
  • Hardwire E-stop / HVIL

Control authority & priority

AuthorityPriorityMay override
Safety / E-stopP0 · highestAll power & contactor paths
BMS protectionP1 · highSOP clamps · local trip
EMS scheduleP2 · mediumP/Q setpoints within band
Field toolP3 · lowEngineer mode · audited

Layered communication architecture

Physical → link → application → channel mapping — media changes must not rewrite semantics

  1. Physical Connectors, cable class, isolation
    • M12 / Phoenix
    • Shield & drain
    • Galvanic isolation
  2. Link Frames, addressing, media access
    • CAN FD · Modbus
    • IEC 61850 option
    • VLAN / baud / term
  3. Application Signals, units, quality
    • Endian fixed
    • Scale / offset / enum
    • Severity flags
  4. Channel map Example bindings
    • BMS↔PCS CAN FD
    • EMS Modbus TCP
    • Fire dry+CAN

End-to-end trace

Signal end-to-end traceability — eight steps

From connector pin to system action and event log · demo fields Demo data

  1. Physical port M12 pin · shield bond
  2. Channel CAN FD ID / Modbus addr
  3. Frame Byte / bit layout
  4. Parse Type · scale · unit
  5. Semantics Named control point
  6. Handshake State · command pair
  7. System action PCS / contactor / EMS
  8. Event log Stamp · quality · severity

Unified signal dictionary

Master table plus CAN FD message sidebar · demo Demo data

SignalSrc→DstTypeUnit / scaleRateQualitySeverity
PackV_AvgBMS→EMSUINT160.1 V100 msGOODInfo
PackI_HallBMS→PCSINT160.1 A20 msGOODInfo
SOP_ChargeBMS→EMSUINT160.1 kW200 msGOODWarn
PCS_P_CmdEMS→PCSINT160.1 kW100 msGOODInfo
FaultWord_BMSBMS→EMSBITFIELD—50 msSTALEWarn
EStop_FbSafety→AllBOOL—Hard+CANGOODCrit

State & command handshake matrix

Who may start, stop, clear faults or override — encoded in one matrix Demo data

BMS statePCSEMS commandACKResult
OFFOFFStartSelfCheckYesEnter SELF-CHECK
STANDBYSTANDBYPrechargeYesPRECHARGE
READYREADYChargeYesCHARGE
FAULTANYPowerOnNoForbidden
READYDERATEDischargeCond.SOP clamp
ESTOPTRIPResetCond.Role + audit

Forbidden transitions

  • FAULT → PowerOn without clear
  • ESTOP → RUN without latch reset
  • Dual writers on same setpoint
  • Allowed
  • Conditional
  • Forbidden

Time & data-quality engineering

Four cards — trigger, quality policy, time sync, reliability

Trigger mechanism

Cyclic
Per ICD rate
Event
On change / edge
Polled
Master request
Burst
Fault dump demo

Quality codes & policy

GOOD
Within rate window
STALE
Hold last · alarm
INVALID
Parse / logic fail
OOR
Outside ICD limits

Time sync

Clock
NTP / PTP demo
Seq ID
Monotonic / link
Stamp
Source + gateway
Order
Cmd before confirm

Message reliability

CRC
Frame / PDU
Rolling cnt
Replay detect
Heartbeat
500 ms · 3 miss
Auth tier
Write gated

Deterministic anomaly behavior

Anomaly communication — defined degrade, alarm and recovery

Lost links and conflicts never become ad-hoc operator guesses Demo data

AnomalyDetectDegrade / safe actionAlarm & recovery
Link timeout3× · 500 msHold last → safe stopRe-handshake + audit
Heartbeat lossWatchdogPCS stop · EMS alarmManual clear gated
Command conflictDual writersReject · keep priorRole arbitration
Version mismatchICD hash failRead-only · block controlAlign ICD + retest

Alarm & fault mapping

Source codes map to severity, PCS action and EMS/HMI text Demo data

Mapping table

SourceCodeSeverityPCS actionEMS / HMI
BMSA1001CRITTrip DCOpen contactors
BMSA2104WARNDerateSOP clamp banner
PCSP0302CRITGrid disconnectIsland inhibit
PCSP1108INFOLog onlyComm retry
EMSE0501WARNHold P/QSchedule freeze

Cause → Effect

CauseEffect
CAN timeoutDerate → stop
E-stop hardwireImmediate trip
ICD hash failRead-only mode
Dual setpointReject write

Gateway / translation boundary

Five stages — no silent unit change; ICD owns scale

  1. Source dictionary CAN FD · PackV 0.1 V
  2. Internal model Named SI · quality
  3. Target dictionary Modbus reg · scale
  4. Transform rules Endian · factor · clamp
  5. Reject / unknown Drop · log · alarm

Security & access control

Seven controls on the write and update path

  • Whitelist Allowed peers only
  • Roles RO / Op / Eng
  • Signing Param packages
  • Secure update Signed FW / ICD
  • Segmentation VLAN / zone
  • Audit Cmd · config log
  • Local safety Hardwire wins

Version compatibility & change control

Compatibility matrix plus six-step change flow Demo data

Compatibility matrix

ComponentRevCompatible withNotes
ICD-COMMv2.7BMS 3.1 · PCS 2.4 · EMS 2.0Baseline
BMS dict3.1ICD v2.7Additive only
PCS map2.4ICD v2.6+Reg map frozen
EMS tags2.0ICD v2.7TLS northbound

Change flow

  1. Change request Delta vs ICD ID
  2. Impact analysis Consumers · rollback
  3. Document update Dict · matrix · diagrams
  4. Implement FW / gateway maps
  5. Verify Sim · unit · integration
  6. Release Rev bump · package
Protocol simulator and integration lab
Cabinet / lab context (demo)

Verification ladder & message fragments

Seven stages with case counts / pass rates · plus message log · not a CTA Demo data · not CTA

  • ICD verify 42 · 100%
  • Simulation 128 · 98%
  • Unit 64 · 97%
  • Integration 36 · 94%
  • HIL 24 · 92%
  • FAT 18 · 100%
  • Field — · Planned

Message log fragment

TimeIDSignalValueQ
12:01:03.1200x18FF50E5MaxChargePower320.5G
12:01:03.1400x18FF51E5PackI_Hall-180.2G
12:01:03.2000x18FF10E5FaultWord0x0000G
12:01:04.010—HB_PCSOKG
12:01:04.5200x18FF50E5MaxChargePower318.0S