2021-05-28 (F) Weekly Summary

At long last, I found the problem with the infrared noise. I assumed that the black resin wouldn't let any light through, but it allowed IR to pass, albeit attenuated. The picture below is an infrared flashlight below a 6mm thick printed piece. Now, I'll have to change the infrared aerial design.
IR can penetrate printer resin

I thought about a complicated aerial that used M2 bolt cross members and foil-shielded LED nodes, but I decided to replace the bare IR receiver with the shielded version. Remodeling shouldn't increase the size dramatically. In this revision more the receiver will be exposed.
IR aerial with a larger receiver socket

I  installed the IR receiver smoothly and added five wires. This time, I learned from the previous experience, and the wiring was tidier, and the conductors coming out felt more secure.
IR aerial with a shielded receiver

I broke three of my finger rods when I dropped the unit, so I printed replacements and wired them up. This time, I took extra care to cut copper tape strips that wouldn't create any seam-lines on the bottom of the finger rod because it should contact the Velostat uniformly.
Four finger rods, hot off the press

I decided to add my updated aerial to the project rather than replacing the old one. This way, I can compare between the old and new. Since I'm still figuring out this arrangement, it seems like the most logical approach.
Two IR aerials installed

I did some program updates, but that uncovered problems with the hardware. I forgot to add pull-down resistors on the finger rods, and the other issue is that I get readings from a pressure sensor when I try to read my infrared receiver.
Debugging hardware and software

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

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.