2018-10-24 (W) ModuKey

Getting data from the IO expander proved too difficult for last evening so it was abandoned for the day and the problem was allowed to ripen. During the next day, it occurred to me that it was impossible for me to hold the IC tightly during normal operation even though that allowed communication but it would be possible to use the tension of the PCB against the wood to hold the IC in place. Screws were tightened, and the IC was pressed between the wood and PCB.

Using the PCB to hold the IC tightly

Pressure from the boards and the tweaked solder joints lead to a steady connection which could be read by the I2C scanner program. The program was slightly modified from the Arduino Playground version so it would scan fewer addresses and run more frequently.

I2C scanner picking up 0x20, the errant board

ModuKey on GitHub

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 on 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.


2018-10-26

Comments