Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Battery Monitoring Board Re-design #80

Open
davidlenfesty opened this issue Sep 28, 2019 · 4 comments
Open

Battery Monitoring Board Re-design #80

davidlenfesty opened this issue Sep 28, 2019 · 4 comments
Assignees
@KH1534143 @farow550
Labels
redesign

Comments

@davidlenfesty
Copy link
Contributor

davidlenfesty commented Sep 28, 2019 •
edited
Loading

Add another channel to the battery monitoring board, in order to support 5 batteries for the new robot design.

As well, board outline should be modified to fit better into new robot design.
@mothmanu mothmanu self-assigned this Oct 5, 2019
@davidlenfesty
Copy link
Contributor Author

As well, implement recommended improvements from Moira.

@davidlenfesty davidlenfesty assigned ahlee1 and shuyangzhang1 and unassigned ahlee1 Oct 26, 2019
@davidlenfesty
Copy link
Contributor Author

Some more possible improvements:

  • Latching Killswitch Connector
  • Attach GPIO to killswitch signal to output over CAN

@KH1534143
Copy link
Contributor

Is there any requirement for the board dimension?

@davidlenfesty
Copy link
Contributor Author

No, however ideally it should only get bigger linearly. (i.e. 1.2x it's current dimensions).

Also some more comments on the improvements:

  • The latching connector is not necessary, but if you can find a connector that is compatible with the standard headers but still accepts a latched connector that would be ideal.
  • I'd say adding the GPIO to the killswitch is mandatory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@KH1534143 KH1534143

@farow550 farow550

Labels
redesign
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@davidlenfesty @KH1534143 @ahlee1 @shuyangzhang1 @farow550 @mothmanu