-
Notifications
You must be signed in to change notification settings - Fork 10
Meeting Notes (2020 09 01)
Alex McLain edited this page Sep 7, 2020
·
1 revision
-
We're almost happy with the PCB design we have.
- We need to look into the solder paste stencil options. We probably want it for the LED matrix drivers; they have soldered thermal pads.
- Can we get a stencil for just the area around the ICs? Does that save on cost at all?
-
When we send the PCB off to manufacturing we should package it as a GitHub release.
-
What do we get?
- JLCPCB makes us a raw circuit board.
- We buy the components (Digikey, etc.) and populate the boards ourselves.
-
Plate or PCB-mount keys?
- We have holes in the PCB for PCB-mounted switches. Not going to have a switch plate for the dev board.
- The plastic legs can be snipped off if you want to use them as plate-mounted later.
- Need to buy keys + key caps.
- NovelKeys
- We have holes in the PCB for PCB-mounted switches. Not going to have a switch plate for the dev board.
-
We want to spec reputable parts and suppliers on the BOM to ensure quality and availability.
- The hardware will officially support the parts we specify.
- Folks can decline to opt in to our bulk orders if they want to make their own substitutions and waive official support.
-
PRUs (for matrix scanning)
- The PocketBeagle doesn't expose enough pins for our key matrix.
- We need to use the BeagleBone Black or BeagleBone Black Wireless.
-
Engine
tests- We need to test that after unregistering a paintable function it gets called at most once after unregistration.
-
We're going to need the key binding feature (#105) if we're building a 68 key keyboard so that we can make our own individual trade-offs for which keys we want to be able to use.
-
Brainstorming how the Xebow repo gets used for various keyboard implementations
- Git submodule style or a "git overlay". Xebow is base code and the implementation is overlaid on top of that.
- Xebow is a base library and it can be passed implementation details (i.e. layout) from an implementation.
- Plugin system?
-
We should push the translation from keyboard units ("U") to pixels further down the view layer (to HTML/CSS). Right now the conversion is happening in the LiveView genserver.