-
Notifications
You must be signed in to change notification settings - Fork 452
HexadeciPad #509
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
base: main
Are you sure you want to change the base?
HexadeciPad #509
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Umm, you final image should have everything combine, it should have case, pcb, and components like this https://github.com/hackclub/hackpad/tree/main/hackpads/Duccs%20Fidget%20Toy |
|
sorry for the late-ish reply. i will try to get that done within the next 4 hours |
|
Deployment failed with the following error: |
|
@GaoYeGithub I have fixed my render |
qcoral
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hey - awesome job, but your keyswitch schematic might be messed up - i think it's a ground connection? not sure
I think I have fixed that now. i completely forgot to connect my keys to ground |
return-misaPuding
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
schematic is fixed and all keys are properly connected, LGTM! (my PR is #634 , but i´m pretty sure dari will see this soon anyway)
|
also, your firmware is very cool! i haven´t seen anyone implement alttabbing with a rotary encoder yet |
|
images of the pcb and the schematic are outdated, but I have re-routed everything and it should be connected to ground now |
return-misaPuding
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PCB is routed correctly with the switches grounded, however, DRC outputs 1 error:

your mounting hole courtyard overlaps the switch footprint. the courtyard is bigger than the hole because it also shows clearance for the screw head, so if you try to screw it in, it will definitely mess with that "random key". i´m not sure if a MH is actually needed here - most hackpads were mounted by the keyboard plate (that´s between the switches and the keycaps), so maybe its fine to just remove the hole or not screw anything in it?
I just won't screw anything into it. I really do not want to have to commit again because I was using cli on Ubuntu because of one of the hackpads having a special character. |
|
should be good if you don´t screw it |
M0HID
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please can you remove the 50 libraries from your pr
Delete pcb libraries
Done! |
Taran-the-Idiot
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hihi, can you remove all the files here please?
https://github.com/pakkid/hackpad/tree/main/hackpads/HexadeciPad/pcb/packages3D
thank you
|
@pakkid is attempting to deploy a commit to the Hack Club Team on Vercel. A member of the Team first needs to authorize it. |
i have removed files now |
Taran-the-Idiot
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
before I approve this I just want to confirm with you if you are okay with hand soldering the io expander. rn you would not get enough grant money to pcba it. It would not be that hard to remove the io expander though. you should have enough pins to do it normally without the expander.

Ready to submit your project? Nice job! Hopefully you've read the submission guidelines. If not, make sure to read them first.
Check off the following to let the reviewers know you've done everything:
If you're unsure about the format, make sure to check out this example and follow the format there.
If this PR isn't a submission, that's okay too! Please remove the above boxes and explain what the pull request is for! If there's anything about this PR template that seems confusing, send a message in #hackpad in slack!