2022-02-25 (F) Weekly Summary

My laser doesn't always cut through plywood, but I made some ugly holes, and I could test my footprints and confirm that everything fit. A coworker suggested that wood density varies between batches, and I may have better luck later.
Good test fitting

Instead of suffering through another day of laser woes, I bought some plastic boxes and adapted my drawings to fit. The person who requested this project worked in a machine shop and offered to cut them.
Layouts and plastic boxes

I got to work on the electronic and soldered pins to everything. I decided on breakout boards for the controllers, ensured I had a place to land everything, and included a tactile button for testing.
Everything soldered with header pins

The first bit of electronics I focused on was the light ring. The majority of the work was establishing the program to work with my inexpensive controllers, the MH-Tiny boards I had in surplus.
Working light rings

Next, I went to the distance sensor and wrote a configurable beam. I looked at the nearest distance, and whenever something came closer, it would trigger the onboard LED.
My hand causes the light to turn on

When I worked on the LCD screen, I realized that I should have started there. The cheap controllers don't support serial feedback, so I couldn't tell what was happening there, but I could have been displaying data all along.
LCD working with poor contrast

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

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