Project Summary

Note: changes to challenger will result in the below information potentially no longer applying.

Strategy should exist in 3 places during the race: chase vehicle, Raspberry Pi 3B (Driver DisplayIn-Car), and Raspberry Pi 0 (BMS Carrier). The following page in progress will outline how we rely on each and why each is important.

...

• How do we manually control the system? (Start/stop)

• What’s the most effective way we can fire queries so as to not block anything else?

• Is Python sufficiently fast for our calculations?

• Are we over-burdening the 3B Pi; if so, what’s the backup plan? For eg. what’s the power usage cost of using the infotainment Pi exclusively for strategy?

• Specific to the SOC ideas (via discussion with Avery, 3/13/21)

...

Chase Vehicle

The chase vehicle should be the primary location for strategy data monitoring during the race. It has one copy of the optimization calculations running (including relevant API calls) and a dashboard.

...

Frequency: 15 mins intervals, corresponding to telemetry

...

In-Car Pi

Note: due to the team changing to a challenger, a drivers display pi will no longer be needed. However, there will likely be a pi for telemetry still that may be capable of operating the strategy suite. The below information will likely change when electrical determines what computing resources will be necessary for the car.

There are three strategy-specific responsibilities of this Pi (as operated by telemetry’s parent script):

...