Command Classic/PCB: Difference between revisions
Jump to navigation
Jump to search
(Created) |
|||
Line 14: | Line 14: | ||
==Compact== | ==Compact== | ||
* Current goal is to use [https://kbdfans.com/products/tofu60-2-0 TOFU60 2.0] cases (though this should not affect the PCB design | [[File:CCC_JIS_4_Proposal.png|420px|thumb|link=http://www.keyboard-layout-editor.com/#/gists/8f4a6e56635f8cf65ce4e7d5bbd3d910|Proposed 4th build (JIS).]] | ||
[[File:CCC_K_4_Proposal.png|420px|thumb|link=http://www.keyboard-layout-editor.com/#/gists/57535e14bb06284e849c844109c52f55|Proposed 4th build (Korean).]] | |||
* Current goal is to use [https://kbdfans.com/products/tofu60-2-0 TOFU60 2.0] cases (though this should not affect the PCB design) | |||
* One PCB for all national layouts, or separate ones? |
Latest revision as of 04:38, 21 June 2023
PCBs for the Command Classic do not yet exist. This page tracks efforts to design and produce some.
Common Goals
- The PCB should not be used for structural support (gasket mount, etc). It should be usable in any cases that rely on a connection between the switch plate and the case.
- Use Unified Daughterboard C Series to avoid dependency on specific cases
- New C4 design uses Pico-EZmate connectors instead of JST SH
- Consider using JST SH for now because vendor stock is still mostly pre-C4
Standard
TBD
Compact
- Current goal is to use TOFU60 2.0 cases (though this should not affect the PCB design)
- One PCB for all national layouts, or separate ones?