Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Current »

Specific to data transfer from the main car to the trailing car. See Coulomb Counting for other tasks regarding data management within the car.

Tentative Deadline:

Slack Channel: #telemetry

Related: #elec-firmware, #elec-hardware, #coulomb-counting


Points of Contact

Primary

Role

Contact Information

Main points of contact.

Meetings and updates must include all primary members.

Mitchell Langdon Ostler

Firmware Lead

Prabhav Khera

Strategy Lead

Secondary

Role

Contact Information

Secondary members must be kept updated on progress and all decisions. However, they not directly handling this task.

Nita Esfarayeni

Consult

Forest Zhou

Hardware Lead

Rodrigo Tiscareno

Strategy Lead

Yanshen Zhou

Owen Li

Battery Box Lead

Members

Role

Contact Information

This keeps track of all members and their current contributions or roles within this task.

This should be kept updated by the members each meeting.

Kostubh Agarwal

Slack Channel Manager

Kyle Chan

Lead

Eric Zhao

Ryan Lam

Jenna Kong

Katharine Laughton

Slack


Meeting Schedule

Date

Time

Itinerary

Topics to be Covered

9:00 PM - 10:00 PM

Hardware Integration

Telemetry, Coulomb Counting, BMS Current Sense

 Meeting Notes

RF implementation is complex and involves dealing with FW drivers, regulations, and interference

Was initially proposed as a simpler alternative to dealing with networking protocols, but that doesn’t seem like it’s the case

From strat, we only need accurate SOC every 5 mins for their model, possible to do over radio

What accuracy is needed?

Baseline is no live data, will be a task but not on the critical path

Critical assumption made is that we will be able to get accurate SOC calculation entirely on the vehicle, which is possible especially with OTS ICs

  • No labels