Jordan BurgessSoftware design · Connected systems · Embedded hardwareView in archive

Multi-Vendor Power and Control Integration

Integrating power, control, and interface products from different manufacturers, then diagnosing failures that appear only when those products operate together.

Recurring integration boundary

Between devices

A representative multi-vendor system. Battery management, charging, power conversion, and DC distribution share a physical power path while supervisory control and the human-machine interface exchange commands and reported state with devices through CAN-based communication, including RV-C. The interface contract—command timing, reported state, control authority, initialization, and recovery—must align at each interface. Devices that are valid in isolation can still produce the wrong system result when those assumptions diverge.

Most of the systems I work on combine battery management, charging, power conversion, DC distribution, monitoring, supervisory control, and human-machine interfaces from different manufacturers. My role is to make those products operate as one system and then work out why they do not.

That work moves between system architecture, device configuration, CAN and RV-C traffic, reproduction of intermittent faults, and validation of firmware or configuration changes. It also requires coordinating with manufacturers, installers, customers, and internal engineering teams, since each group usually has a different view of the same failure.

The difficult problems are often not contained within any one device. They appear when two products make different assumptions about command timing, reported state, control authority, initialization, or recovery. Each device can be behaving as designed while the system still produces the wrong result.

  • Systems integration
  • CAN and RV-C
  • Protocol analysis
  • Fault reproduction
Format
Embedded systems integration
Threads
Engineering · Fieldwork

Ongoing