2018-05-20 (Su) ModuKey

A Teensy-LC was purchased and header pins were soldered so it could plug into the keyboard socket. Once installed, an I2C scanner sketch was installed. There were a couple options, even one right on Arduino.cc which worked well. Neither of them showed any activity on the data lines.

Testing a serial scanner

In order to test the boards systematically, a new controller board was populated with pull-up resistors and headers. This was not connected to any of the other PCBs. One of the breakout boards for an MSP23017 chip was connected to the new controller with jumper-wires. The scanner was able to detect this board without a problem.

Testing a module known to work

This proved that the new Teensy-LC boards were working properly and the board that the controller was mounted in was functional. A continuity tester was used on the keyholder boards and it showed that the data lines were both connected to ground. Schematics for the 4x4 board revealed that half of the connectors along one edge were all messed up and that was causing the data lines to be grounded. This would have to be revised in the next iteration of boards. In the meantime, jumpers to the 2x4 board were shuffled so communication could be established between the keyholder boards. The second half of the keyboard will have to be changed as well before it can be programmed.

Getting feedback from the 4x4 board and 2x4 board

The rest of the posts for this project have been arranged by date.

First time here?

Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5

Disclaimer for http://24hourengineer.blogspot.com/

This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.

All information in this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property or similar, is the responsibility of those involved in the replication.

All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by  Brian McEvoy, cannot be used to claim property or assets.

Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.

This blog, including pictures and text, is copyright to Brian McEvoy.