mouse

I'm not sure how "open" I consider a pdf of the schematics (no sign of PCB layouts), compiled hex files and I'm unsure where the mechanical 3D files are. [0] When I think of open hardware I imagine Kicad/Altium files of the electronics (not gerbers), access to the C, C++ or Rust firmware and the STEP files at least or other source modifiable files so they're 3D printable if I was so inclined to modify all three. [0] https://github.com/ploopyco/mouse

You can order a ploopy[0] kit or modify their source[1]. I think a few users on r/trackballs[2] might have gotten QMK to work with it. [0] https://www.ploopy.co/ [1] https://github.com/ploopyco/mouse [2] https://www.reddit.com/r/Trackballs/comments/dk4ha7/ploopy_v...

Another gem at (https://github.com/ploopyco/mouse/blob/master/firmware/SROM_...) // This is the firmware that is uploaded to the PMW3360 each time the mouse starts up. // Don't mess with this. Just...just trust me. Don't do it.

It could be this, mentioned in the schematic: “Spark Gaps - Case: Since the case has gaps in it we expect [electrostatic discharge] to worm it’s way in via creepage and perhaps other ways. To protect the board from this eventuality, we place spark gaps along the edges.” https://github.com/ploopyco/mouse/blob/master/hardware/Elect... So technically a via fence, but not quite as sophisticated.

From the code repo (https://github.com/ploopyco/mouse/blob/master/firmware/produ...): // Startup delay. This sometimes prevents a USB handshake lockup. delay(1000);