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.

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

Main PCB: Potential collision RoboClaw 1 and C2 #169

Closed
Roger-random opened this issue Sep 12, 2019 · 1 comment
Closed

Main PCB: Potential collision RoboClaw 1 and C2 #169

Roger-random opened this issue Sep 12, 2019 · 1 comment
Assignees
Labels
Electrical Improvement Makes an improvement on an electrical property of the robot

Comments

@Roger-random
Copy link

Using mainboard Rev E.

Our five RoboClaw controllers are mounted with the tops of their electrolytic capacitors flush against the main board. On RoboClaw 2-5, they meet up with flat uninterrupted PCB. In Rev E, however, capacitor C2 is directly on the other side of RoboClaw 1's capacitors. Its soldering points can barely clear in between two capacitor cans of RoboClaw 1. And this is when trimmed back almost flush.

If someone has a large solder joint that hasn't been trimmed, doesn't notice the potential for collision, and crank the screws tight while installing their RoboClaw 1, they risk puncturing the electrolytics.

Consider moving C2 to reduce the chance for this potential problem.

@ericjunkins ericjunkins added the Electrical Improvement Makes an improvement on an electrical property of the robot label Jun 25, 2020
@ericjunkins ericjunkins self-assigned this Jun 25, 2020
@dcschooley dcschooley mentioned this issue Jul 5, 2020
64 tasks
@apollokit apollokit self-assigned this Apr 9, 2021
@apollokit
Copy link
Collaborator

Handled in #198

@Achllle Achllle closed this as completed Sep 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Electrical Improvement Makes an improvement on an electrical property of the robot
Projects
None yet
Development

No branches or pull requests

4 participants