2024-12-06 (F) Weekly Summary

I troubleshot the I₂C problem with some software tricks, like streamlining the code for the scanner and enhancing its error-reading feedback. The thing that finally worked was cleaning near all the I₂C data pins. Something conductive was touching a solder joint because I could reliably scan after the cleaning.
I₂C troubleshooting

Using some example code, I mapped the LEDs and pushbuttons connected to the IO expanders. All operators functioned as expected except for one LED and one pushbutton.
EWC_Noodle buttons and IO expander pins

One button and one LED were not working. I confirmed the LED was faulty by checking continuity, but since it was inconsequential, I removed it from the IO list. For the BACK button, I found it wasn't functioning due to a disconnected ground. After connecting it to the GND pin on the IO expander board, I could read the button reliably.
GND wire connected from D-pad buttons

I cleaned up the wires by adding mounting points and zip ties. The Arduino and prototype board were left alone since there is more soldering to do.
A little tidier

I soldered a single-channel optoisolator onto the prototyping PCB and added the necessary resistors for the RX and TX circuits. I am ready to test the MIDI sockets although I am unsure if I arranged the DIN socket wires according to an internal or external view.
Optoisolator on microcontroller board

I grabbed my MIDI output tester, which has a couple of LEDs on the side and a socket on the back. Green indicates Good wiring, and Red indicates Reversed wiring. I will test the input next and correct it as needed.
Red means reversed

The rest of the summary posts 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
Completed projects from year 6
Completed projects from year 7
Completed projects from year 8
Completed projects from year 9
Completed projects from year 10
Completed projects from year 11

Disclaimer for http://24hourengineer.blogspot.com and 24HourEngineer.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.

Comments