Powertrain Mockup
Things in the mockup
Boards going in to powertrain mockup:
Pedal
Center console
power select
front power distribution
MCI
DCDC
Other components in mockup:
firmware mock of BMS carrier and potentially other things
power supply to simulate main pack
power supply to simulate aux pack
e-load to pull output from PD
motor controllers and motors
Firmware TODO before mockup
Note: “mockup ready” means we can just flash the project, and assuming all other boards in the mockup are connected, it’ll just work ™
Pedal board
Flash
smoke_ads1015
, ensure readings can be gotten for both brake and throttle channelRun calibration with
make test PROJECT=pedal_board TEST=pedal_calib
and follow minicom instructions for calibration. Also mark the potentiometers to make it clear which way is “pressed” vs “not pressed”Flash
pedal_board
and make sure proper CAN messages get sentCenter console
Make sure buttons and LEDs work, could write a smoke test or just babydriver it
validate by flashing project and hoping for the best (and fixing any clearly broken things)
figure out what CAN responses need to be mocked and write a mock or comment out things that won’t work in the mockup, generally just get the project mockup ready
Power select
Check thermistor readings and re-work the temperature checking logic if necessary (from old power select project)
Write up new requirements for power select
Completely revamp old project to take into consideration new requirements
Get the project mockup ready by commenting out unnecessary things (depends on what bits of hardware aren’t being used)
Front power distro
Sort out
smoke_bts7200
after refactor (check Selina’s onsite notes from Oct. 25)Ensure we set the config to only enable / check the relevant channels (hardware dependent) (channel 3 and 7 from
smoke_bts7200
)MCI will be powered off front power for this mockup but not for actual car. Figure out if anything needs to be changed to allow for this, and if so make the changes
Get the project mockup ready by commenting out unnecessary things
MCI
If configuration software is available, configure the motor controllers (probably won’t be doable by mockup)
figure out MCP2515 communication with new motor controllers (if necessary, don’t include status messages, just bus current / voltage and velocity measurements). Assume sending speed commands will just work.
Get the project mockup ready (this probably just means mocking pre-charge since it probably doesn’t work in hardware)