Record every vehicle parameter the team needs for validation, tuning and driver analysis.
From CR26I all vehicle parameters, acquired and computed, are logged in one central location: the MoTeC M150 ECU. Frequency-critical parameters are sent over CAN at 1000 Hz, which is the M150's maximum logging rate. The Bosch DDU11 handles signal conditioning and operations the M150 does not support, then sends results over CAN to be logged, which keeps sensor-to-DDU11 speeds high while M150 logging rates stay conservative to maximise throughput.
Centralising logging forced the CAN network to be optimised and introduced a formal per-subteam datalogging parameter request system specifying desired logging rate and signal conditioning.
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.
CAN bus load 54%. From the cost report drawings and CAD: Manufacturer datasheet, MoTeC C185: Weight: 410 g; Operating voltage: 6 to 32 V DC. Source: Datasheet: CR22/Electrical/Design/MoTeC/USB Contents/Datasheets/18046 C185 Display Logger USB datasheet.pdf Quantity per car, as costed: 1
Nothing in CrimsonStorage covers these yet.