2021-05-14 (F) Weekly Summary

I installed the infrared components into the printed stand and powered everything. I connected them with test leads on a breadboard with an onboard power supply. When I tried to test them, I think I burned out some of the LEDs, but I got a reaction when I powered an LED from a battery.
IR unit set up for testing

I fixed all the known issues in my aerial model. There were a few problems, like the spacing between LEDs was narrower than my finger distance, and I added the infrared receiver socket.
Newest IR aerial

The last time I tested my IR sensing apparatus, I burned up a couple of LEDs and still wasn't sure about the viability of the design. In preparation for my next test, I wrote a function to flicker the LED and check for reflection.
Automatic IR algorithm

I messed up the infrared receiver dimensions, so it refused to fit into its socket. My printer needed some maintenance, so it took an entire day to make a model change, but the result was excellent, and the part fit.
Proper fitting for infrared sensor

I wired the aerial with 26-gauge conductors and added lengths of shrink tube. The tube down the middle kept my work neat, but I think I need a square hole at the bottom so the wires exit easier.
Wired IR aerial

I added a section of prototyping PCB called stripboard so I could add a battery and some switches. One switch disconnects the power, and the other three should help me debug code later. One trick I learned when dealing with HIDs is to add a cutoff so it cannot make the computer unresponsive.
Battery operated and accessory switched

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.