Open Issues Need Help
View All on GitHub improvement good first issue VC firmware
nvm: Statically assert nvm struct sizes 8 months ago
improvement good first issue firmware
Investigate BMSB current scaling 10 months ago
good first issue BMSB firmware
Yamcan manifest generation silently fails (and incorrectly) when multiple signals match the provided pattern 10 months ago
good first issue YAMCAN
Add mode change requirements 10 months ago
good first issue new feature VC firmware
Add gear change requirements 10 months ago
good first issue new feature VC firmware
Add support in workers and vcs to transmit stack bytes left about 1 year ago
good first issue new feature BMSW VC firmware
Axle speeds about 1 year ago
good first issue
Investigate integrating uv binary as a buck2 dependency about 1 year ago
good first issue new feature BUILD-INFRA
Bringup brake temp about 1 year ago
good first issue new feature VC
Flag for MC Fault about 1 year ago
good first issue
Missing bmsb mcu temp in yamcan about 1 year ago
improvement good first issue help wanted BMSB
Output Calculated Pack Voltage from Worker Segment Voltages about 1 year ago
good first issue BMSB
good first issue new feature YAMCAN VC
Slip Ratio about 1 year ago
good first issue
PDU HSD Fault about 1 year ago
good first issue
IMU g's about 1 year ago
AI Summary: This issue requires receiving IMU acceleration data (lateral, longitudinal, vertical) from address 0x470 on the VCFRONT. The received m/s² values must be converted to g's by dividing by 9.81, and the resulting g-forces should be exposed as new signals (e.g., VCFRONT_longitudinal, VCFRONT_vertical) with specified min/max/unit/resolution. The implementation will reside in a newly created `math.c` file within `VC/front/src`.
Complexity:
2/5
good first issue
Brake Bias about 1 year ago
good first issue