ECM/Engine Electronics Assembly

Subteam: ElectricalSubsystem: BSPDAssembly: ECM/Engine Electronics AssemblyCars: CR22, CR25

Purpose

Assembly line covering the ECU, datalogger and engine electronics.

Function

Groups the M150, the dash, the sensors that feed them and the BSPD. Design Philosophies and Processes: Inherited from the BSPD subsystem design process: 1. Establish the rules requirement and the thresholds from real vehicle data (brake pressure at which hard braking is unambiguous, throttle position of 10%). 2. Schematic capture in Altium, split into the main connector, reset subcircuit, signal loss subcircuit, simultaneous brake and throttle subcircuit, and the fault and latching subcircuit. 3. Lay out the board, push to MCAD, design the case. 4. Manufacture and bench test each subcircuit. 5. Validate on the car by observing PDM outputs: output 1 (ignition), output 11 (injectors), output 5 (fuel pump) all drop for the fault duration.

Reoccuring issues

None recorded. This part has no entry in Knowledge_Transfer/Issue Logging/Fault Vault.xlsx, in either Issue Log.xlsx, in CR22/Issue Tracking/Shakedown 7-15-23.xlsx, or in any design review issue list found in CrimsonStorage or Box.

Still to document

Nothing in CrimsonStorage covers these yet.

Design Process — How it is designed and deemed effective at its purpose and function
Design Constraints — What held back the design whether it be location, time, materials etc
Analysis — How you get quantitative, predictive information on the part
Manufacturing Process — How it is assembled in detail from start to finish
Full Material List — Everything used to build this part (Best if actual numbers are used to show how it evolves year to year)
Improvements — Improvements for this generation
Properties — Size, weight, mass, charge, thermal properties, anything else relevant