My finger rods took a blow when they fell, and three broke. I will consider stronger resin when I get closer to a final build. I continued wiring my electronics like the infrared aerial with the transmitter and receiver, plus I had three auxiliary inputs from the DIP switch package.
Many terminated wires
While cleaning my printer, I spilled a lot of resin into a dirty plastic tray. Since I couldn't save any of it, I used my ultraviolet laser pointer and saw what happens when you hit uncured printer fluid with coherent UV light.
I took my old code, which only ran the display, and worked it into my new code that supervised inputs. I found out that the wireless controller wouldn't work as a wired keyboard or mouse, but it may still work as a Bluetooth device.
Before the false positives
I started testing the IR aerial, and I managed to get the noise under control by slowing my scan rate, but the LEDs weren't activating. I checked the lights with my phone camera and a camcorder with no infrared filter.
Not getting any IR from the LEDs
I got my LEDs working after I discovered I was activating the wrong lights. This was a relief since I was worried I burned out the components. The bad news was that I saw lots of noise on the receiver, but I proved that I could use my IR camera as a jammer at close range.
The LEDs are working
Reading values on a serial monitor wasn't intuitive enough to figure out if I was getting noise, witnessing a wave, or misidentifying valuable feedback. I switched to viewing the IR signal strength on the screen as a line or bar graph. The best I could do was figure out that the IR spotlight on my camera would make the whole unit act like a proximity sensor.
Tame signal
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.
While cleaning my printer, I spilled a lot of resin into a dirty plastic tray. Since I couldn't save any of it, I used my ultraviolet laser pointer and saw what happens when you hit uncured printer fluid with coherent UV light.
Spilled resin against UV laser
I took my old code, which only ran the display, and worked it into my new code that supervised inputs. I found out that the wireless controller wouldn't work as a wired keyboard or mouse, but it may still work as a Bluetooth device.
I started testing the IR aerial, and I managed to get the noise under control by slowing my scan rate, but the LEDs weren't activating. I checked the lights with my phone camera and a camcorder with no infrared filter.
I got my LEDs working after I discovered I was activating the wrong lights. This was a relief since I was worried I burned out the components. The bad news was that I saw lots of noise on the receiver, but I proved that I could use my IR camera as a jammer at close range.
Reading values on a serial monitor wasn't intuitive enough to figure out if I was getting noise, witnessing a wave, or misidentifying valuable feedback. I switched to viewing the IR signal strength on the screen as a line or bar graph. The best I could do was figure out that the IR spotlight on my camera would make the whole unit act like a proximity sensor.
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.
Comments
Post a Comment