Commercial Vehicle · Hydrogen
Active · 3rd year
Hydrogen Fuel Cell Vehicle Control Unit
Role: VCU software architecture, J1939 integration, system bring-up
Multi-year development of the vehicle control unit for a Class 7/8 hydrogen fuel cell truck conversion. The VCU coordinates the fuel cell control unit, a supplier-provided translation gateway, and the vehicle's traction and auxiliary systems over J1939 CAN — arbitrating power requests, managing startup and shutdown sequencing, and enforcing fault handling across three independent control domains.
Work included defining the CAN address map and message set across the network, resolving the power-request scaling and unit conventions between the vehicle model and the fuel cell's command interface, and establishing the operating mode and heartbeat requirements that govern the fuel cell interface. Software is developed in MATLAB/Simulink on the New Eagle Raptor eMBD platform.
Raptor eMBDJ1939Fuel Cell ControlsSimulinkHV Systems
Port & Terminal Equipment · EV Conversion
Commissioning support
Reach Stacker Electric Conversion
Role: Commissioning engineering, technical documentation, integration boundaries
Technical preparation and on-site commissioning support for the battery-electric conversion of a heavy container-handling reach stacker. Scope covered traction inverter commissioning procedures, battery management system precharge validation, CAN network integration across the drive and energy systems, and a clear definition of component responsibility boundaries between the integrator and the component suppliers.
The deliverable set was written so the field team could execute commissioning in sequence and capture the evidence needed to sign off each subsystem — the difference between a conversion that starts and a conversion that can be supported.
EV ConversionTraction InvertersBMS PrechargeCAN IntegrationCommissioning
Marine · Controls & Networks
Ongoing capability
Marine CAN Protocol Reverse Engineering & DBC Development
Role: Protocol analysis, database authoring, validation
Recovery of undocumented and partially documented marine CAN protocols into validated, production-usable DBC databases. Recent work includes a fully corrected 18-message database for a marine power distribution module — bit layouts verified message by message against manufacturer documentation and live bus capture — and the reverse engineering of a proprietary helm control protocol covering display intensity, switch status, and indicator command frames.
Databases are delivered in a three-file architecture — commissioning, full bench, and runtime — so the same signal definitions serve bring-up, lab validation, and the shipped controller without divergence, together with written usage documentation.
CAN / J1939NMEA 2000DBC AuthoringProtocol AnalysisKvaser / Vector
Marine · Production Programs
Career portfolio
Zeus & Axius Steer-by-Wire Propulsion
Mercury Marine · MotoTron / Brunswick — System engineering, CAN architecture, harness release
System engineering for Mercury Marine's Zeus & Axius platform, one of the first autonomous steer-by-wire marine propulsion systems, recognized with the IBEX Innovation Award. The CAN network isolation and termination strategy developed for multi-engine applications is the subject of US Patent 7,941,253.
The same programs produced 60+ production wiring harness assemblies released to manufacturing, and the licensed CAN protocol distributed to third-party marine customers through MotoTron/Brunswick.
Steer-by-WireCAN ArchitectureLV HarnessPatentIBEX Award
Industrial · Product Development
Career portfolio
Automotive-Grade Controls for Industrial Machines
McElroy Manufacturing — Director of Product Development
Led a 36-person mechatronics organization through the replacement of legacy machine controls on track-mounted pipe fusion equipment with automotive-grade hardware and model-based software development. The transformation brought requirements traceability, structured validation, and production software process to a product line that had grown up on ad-hoc PLC programming.
Implemented a secure Product Data Management system alongside it, so engineering change became traceable across the whole organization rather than living in individual engineers' folders.
Model-Based DevPLC ReplacementRugged ControlsPDMTeam Leadership