Embedded systems
Industrial automation
Battery systems and manufacturing automation
3ME Technology
Project outcome
2 months to 3 days
A connected test and automation system that moved battery manufacturing from a slow, specialist-led process to a repeatable production workflow.
Where SSH Tech sat in the system
Signal path
3/6 layers built at SSH Tech
L1
Machine
Battery packs, fixtures and the manufacturing line.
Existing
L2
Sensing
Cell, current and thermal signals brought into the test path.
Integrated
L3
Embedded
BMS firmware, CAN messaging and deterministic device states.
Built at SSH Tech
L4
Compute
Test sequencing, run logging and operator controls.
Built at SSH Tech
L5
Decision
Recorded thresholds and repeatable pass or fail logic.
Built at SSH Tech
L6
Actuation
Fixture control and production release signals.
Integrated
Discipline load
Mechanical
Electrical
Embedded
Software
Operations
The system problem
Challenge
Battery-management hardware needed to be configured, exercised and verified across a growing product line. The existing process depended on manual intervention, fragmented tooling and long feedback loops between engineering and production.
Our responsibility
SSH Tech owned the technical path from the battery-management interface through to operator tooling: understanding the electrical and CAN behaviours, designing the test sequence, implementing embedded and desktop software, and making the workflow usable on the manufacturing floor.
How we worked
- Mapped the production sequence, device states and failure conditions before selecting the automation boundary.
- Built deterministic test routines around the BMS and CAN interfaces so results could be reproduced and diagnosed.
- Connected low-level device communication to operator-facing controls, logs and pass/fail evidence.
- Iterated with manufacturing users so the tooling matched the actual assembly and commissioning workflow.
Delivery path
Hardest risk first.
Phase 1
Instrument the battery system
Created reliable access to the BMS state and the signals needed to configure and validate each unit.
- Embedded C++ interfaces for device communication
- CAN message handling and state verification
- Repeatable setup and diagnostic routines
Phase 2
Turn engineering steps into a workflow
Converted specialist knowledge into sequenced tooling that guided operators through setup, test and exception handling.
- Automated test orchestration
- Operator feedback and actionable failure states
- Structured test records for traceability
Phase 3
Harden it for manufacturing
Refined the system around real production constraints so it could support throughput rather than remain a lab prototype.
- Production-floor validation
- Recovery paths for incomplete or failed runs
- Handover of maintainable tools and technical knowledge
What changed in the operation
2 months → 3 days
Manufacturing cycle
The end-to-end cycle was reduced from roughly two months to three days.
AU$4M+
Sales supported
The embedded work supported more than AU$4M in product sales.
Technical stack
Embedded C++
CAN
BMS interfaces
Test automation
Operator tooling
Capabilities applied
System integration
Manufacturing tooling
Embedded software
Verification
Next project
Control-system reverse engineering
A contract-defining prototype