-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Production details #2
Comments
I highly recommend you to look up some resources explaining what all of these manufacturer terms mean before just blindly ordering something from a manufacturer. The best way to learn is to put in a little effort yourself first. That will also help you deal with other issues you might face down the line! That being said, It's a simple 2 layer board, 1.5mm thickness, FR4 material likemost keyboard pcbs. Rest is up to you. |
Actually, let me reopen this b/c I think it's a fair point that I should add this info to the documentation (even if it would be obvious to most,I did notice there are a couple of people that picked this as their first project) |
Thank you so much. |
May be a stupid question because this is my first real custom, but when I search HRO-TYPE-C-31-M-12 on google, the result is an smd port, but in the picture, the port looks through hole. Which is it? |
You're right, the pictures on the main page are from the prototype PCB (v2) and are using Wuerth part-through hole, part smd usb receptacles. The latest versions (v2.1 and v3) use the smd-only connector of the type that you're referring to (HRO-TYPE-C-31-M-12 ) |
Dear dev,
I tried sending the Gerber file to my local Pcb manufacturer but they asked for the following details (they said these were missing):
Pcb Material
Pcb Layer Account
Pcb Board Thickness
Copper Thickness
Inner Copper Thickness
Soldermask Color
Silkscreen Color
Surface Finish
Panelization
Technical Border (Strip)
“Multilayer: Stack-up, Impedance Control, Via Filled Type etc.”
So sorry for being such a noob. Any help would be greatly appreciated.
Thanks so much in advance!
The text was updated successfully, but these errors were encountered: