@hsgw Would you be able to take a look if the PCB looks OK? I copied the USB-C schematic from the Discipline project, so that should be good. Thanks!

Hi,
I can't find schematic symbol of USB connector.
Can you include files in /pcb?
And, what kind of license is it?

I know there is through hole type-c connector and it's not difficult to soldering too much.
If you don't mind, I can replace it and rerouting.

Thanks

@hsgw Hey, I did include the schematic symbol in pcb/plaid.lib and the footprint in pcb/plaid_silk.pretty/USB_C_GCT_USB4085.kicad_mod. The source of these files is the coseyfannitutti/discipline repo before the license was changed to the more restrictive one. The Discipline board itself is licensed under GNU GPL, but I'm not entirely sure if that applies to the schematic symbol/footprint.

I just updated the PR, looks like I had the associations and the library path wrong. Can you please test again?

The connector I used is a through-hole one - see the DigiKey link in the PR description. It is indeed pretty easy to solder; I built one Discipline v1 with it.

Just out of curiosity, which connector did you have in mind?

I just opened an issue in the Discipline repo to find out what's the origin/license of the USB-C connector schematic symbol/footprint: coseyfannitutti/discipline#34

OK! I can see type-c symbol on schematic.

symbol and footprint

If we can't use them, I can make our own library.

Pinged Bryan from CFTKB by e-mail and received the following response:

The USB4085-GF-A footprint that I use is a modified version of the one that was in ai03's USB Type-C library. The symbol I just made myself because at the time his library didn't include one, and I wanted to be sure that the pins would be assigned correctly.

It is absolutely fine for you to use them for Plaid.

I've also received prototype USB-C Plaid PCBs from JLCPCB today, will try to build one to confirm it's working correctly.

Thanks!

I've thought a lot about ensuring that it works correctly.
I'd have to actually make it myself to warrant it.
So I wouldn't like to merge pcb design from others.
I would appreciate it if you could folk this repository and publish with your own responsibility.

I am really sorry and very grateful for your contribute.

I completely understand that. I wouldn't expect you to merge it just like that. I also want to ensure the PCB works correctly. I'm currently having PCBs made and will build one when the next revision arrives. (I should have perhaps opened the PR only after testing, but I was also looking for possible feedback.)

Once I confirm that the PCB works correctly, would you perhaps be open to merging my contribution into a separate branch (usb-c?) and linking to it from the README?

Ladies and gentlemen, it's alive! 😊 The second revision works correctly (don't even ask about the first revision... 😉). Latest revision has been pushed to my fork.

usb 1-1.5.6: new low-speed USB device number 119 using ehci-pci
usb 1-1.5.6: New USB device found, idVendor=16c0, idProduct=27db, bcdDevice= 0.02
usb 1-1.5.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1.5.6: Product: Plaid
usb 1-1.5.6: Manufacturer: dm9records
usb 1-1.5.6: SerialNumber: 0
input: dm9records Plaid as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.6/1-1.5.6:1.0/0003:16C0:27DB.00D5/input/input396
hid-generic 0003:16C0:27DB.00D5: input,hidraw6: USB HID v1.01 Keyboard [dm9records Plaid] on usb-0000:00:1a.0-1.5.6/input0
input: dm9records Plaid Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.6/1-1.5.6:1.1/0003:16C0:27DB.00D6/input/input397
input: dm9records Plaid System Control as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.6/1-1.5.6:1.1/0003:16C0:27DB.00D6/input/input398
input: dm9records Plaid Consumer Control as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.6/1-1.5.6:1.1/0003:16C0:27DB.00D6/input/input399
hid-generic 0003:16C0:27DB.00D6: input,hidraw7: USB HID v1.01 Mouse [dm9records Plaid] on usb-0000:00:1a.0-1.5.6/input1

Thanks so much!
I would like to make new branch soon.

slightly off topic, any chance to add a kailh hotswap branch?

@fi0 I guess that wouldn't be too difficult - all the switch footprints would need to be replaced and re-routed. I have loads of Kailh sockets, so might have a go at it soon.