TSOP4856 IR receiver replaced the TSAL6100 IR diode to try to filter some of the noise. Since the receiver used a side-looking package the same mounting technique used to house a 5mm LED wouldn't work. Hot glue was used to hold the receiver in place. As seen in the second picture the new receiver used three wires unlike the previous component which used two.
The TSOP4856 receiver kept the output pin high and lowered it when IR pulses were detected. This eliminated the need for pull-up resistors and also kept the controller informed while the component was connected. If the signal went low for too long, half of a second, the controller would assume the receiver was not giving usable input. Additionally the receiver was programmed to deliver pulses so a constant light source would not cause the device to constantly output a signal that it was receiving. In security systems this could indicate tampering
Code was written to oscillate the emitter pin and monitor the controller's receiving pin. When the signals matched (pin states were actually opposite since the receiver output a LOW state when it saw IR light) an output went high. This ensured that noise would not be read as a false positive and there would be no output when no reflection was seen. A fixed number of corresponding reads were necessary to trigger the output.
Code was not completed. Consistent reads were not happening so another day should be taken to ensure good reads are happening. As a homemade infrared proximity sensor this should be its own project.
Downloadable Files:
The rest of the posts for this project have been arranged by date.
First time here?
Completed projects from year 1.
Completed projects from year 2.
New receiver from side
New receiver from back
The TSOP4856 receiver kept the output pin high and lowered it when IR pulses were detected. This eliminated the need for pull-up resistors and also kept the controller informed while the component was connected. If the signal went low for too long, half of a second, the controller would assume the receiver was not giving usable input. Additionally the receiver was programmed to deliver pulses so a constant light source would not cause the device to constantly output a signal that it was receiving. In security systems this could indicate tampering
Code was written to oscillate the emitter pin and monitor the controller's receiving pin. When the signals matched (pin states were actually opposite since the receiver output a LOW state when it saw IR light) an output went high. This ensured that noise would not be read as a false positive and there would be no output when no reflection was seen. A fixed number of corresponding reads were necessary to trigger the output.
Test circuit
Video demonstration of proximity sensor
Code was not completed. Consistent reads were not happening so another day should be taken to ensure good reads are happening. As a homemade infrared proximity sensor this should be its own project.
Downloadable Files:
- Common OpenSCAD files
- Servo footprints for OpenSCAD.
- Arduino Code for wired keyboard
- Spreadsheet for chords.
- Wrist mount
- Terminal board
- Input voltage
- USB
- Make base for keyboard
- Spacers
- Magnet mounts
- Integrate:
- Enclosure for each controller
- Potentiometer access
- Activation switch
- Debug
- Test
- Refine
- Repeat
- Write instructions
- Compress and link to all files
- OpenSCAD files
- STL models
- Arduino code
- Make diagram with every part labeled
- Schematic for servo controller
The rest of the posts for this project have been arranged by date.
First time here?
Completed projects from year 1.
Completed projects from year 2.
Disclaimer for http://24hourengineer.blogspot.com/
This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.
All
information in this blog, or linked by this blog, are 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 claim property or assets based on their post.
This blog, including pictures and text, is copyright to Brian McEvoy.
2015-10-06 (Tu)
Comments
Post a Comment