Bendix develops braking systems and components for commercial vehicles. I worked in an engineering environment involving pneumatic systems, electronic control units (ECUs), and product validation equipment.
What I Did
My main responsibilities involved running product validation tests, developing test automation, troubleshooting test benches, analyzing test data, and investigating returned electronic control units.
Main Results
I automated seven validation tests, reducing manual operation by up to 12 hours per testing cycle. I also resolved a critical software issue that allowed validation work to finish 14 days ahead of schedule.
Technical Skills
Programming
Python, CAPL, Arduino, Vector CANoe
Hardware & Systems
Pneumatics, ECUs, CAN/LIN communications, test benches, pressure instrumentation
Analysis
Advanced Excel, data cleaning, test-result analysis, root cause analysis
Engineering Methods
Test automation, product validation, troubleshooting, technical documentation, Kaizen
Assigned Work
Product Validation
Executed and analyzed over 120 pneumatic validation cases per testing cycle, comparing system behavior with test requirements.
Configured and operated test-bench equipment, including pneumatic components, pressure instrumentation, and ECU-related hardware.
Used CANoe and CAN/LIN communications to support ECU diagnostics, software flashing, configuration, and system bring-up.
Engineering Investigations
Inspected returned ECUs using PCB examination, voltage measurements, mechanical teardowns, and vibration testing.
Investigated unexpected test results, software communication errors, and equipment behavior to identify possible causes of failure.
Documented findings and technical procedures so they could be reviewed and reused by the engineering team.
Data Analysis & Documentation
Organized and analyzed validation results using Excel, formulas, pivot tables, and data-cleaning techniques.
Developed 13 repeatable reporting workflows and supporting documentation.
Standardized test procedures and equipment configurations to make validation work more consistent.
Initiatives
01
Automating repetitive validation tests
Problem
Several validation procedures required repeated manual operations, taking engineering time and making the process more dependent on the operator.
My solution
I designed and implemented a closed-loop automation system combining Python, CAPL, CANoe, Arduino, and physical test hardware. I brought test sequences, timing, data collection, and evaluation functions together in one system.
Result
Seven tests automated and up to 12 hours of manual operation eliminated per cycle.
02
Resolving a critical test-bench software issue
Problem
A software issue was interfering with the completion of validation work.
My solution
I learned the CAPL functionality needed to investigate the issue, traced the behavior through the test code, and implemented a correction.
Result
The validation work was completed 14 days ahead of schedule.
03
Sharing technical knowledge
Problem
Technical knowledge gained from troubleshooting and testing was not always easy to pass between interns, co-ops, and other team members.
My solution
I initiated recurring sessions where team members could explain the tools they were using, discuss technical problems, and share useful solutions.
Result
Established a regular opportunity for technical knowledge-sharing and collaboration.
Results
7 tests automated
Up to 12 hours saved per testing cycle
120+ validation cases per cycle
14 days ahead of schedule on a critical validation assignment
13 repeatable reporting workflows developed
Lessons Learned
This placement taught me that effective automation involves more than writing code. Understanding the physical equipment, expected system behavior, and the people who will use the test system is just as important.
I also became more comfortable taking ownership of problems, learning unfamiliar tools independently, and explaining technical findings to other engineers.