The sensors wired directly to the ECU.
Every sensor relevant to engine control goes to the M150 directly. The CR22 goal was to make sure as much engine-relevant data as possible was wired to the ECU.
No part-specific design process is documented. The Custom Electronics subsystem design process applies: 1. Collect the sensor list from every subteam, agree location and type with the designer who needs the data. 2. Split sensors between ECU and dash based on which parameters are engine-critical. 3. Size the charging system and validate it. A custom current measurement board (50 A bidirectional sensing chip, inline on the rectifier-to-PDM wire) measured what the rectifier actually puts back. 4. Build the datalogging parameter list with rates, then check CAN bus load. 5. Validate on a mock endurance: average battery voltage 13.4 V, minimum 12.1 V excluding cranking on CR26I.
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.
Nothing in CrimsonStorage covers these yet.