Code was written to test the new configuration which features a TSAL6100 emitter, TSOP4856 receiver and an RGB LED. Color functions for the LED worked well. Three pins, 9, 10 and 11, which were all capable of supplying a PWM sign, were used for the LED pins. Applying different intensities proved the PWM signal worked well and the LED was hooked up correctly. Each color may not be hooked to the correct pin but that change can be done in software.
Code which tested the proximity switch didn’t function properly. After trying different variables and seeing unreliable results the problem was suspected to be unfiltered power on the part of the receiver or the unregulated emitter. Limiting and filtering components will be added as necessary.
Values for the receiver were based on Miles Tag receivers.
Downloadable Files:
To do:
Code which tested the proximity switch didn’t function properly. After trying different variables and seeing unreliable results the problem was suspected to be unfiltered power on the part of the receiver or the unregulated emitter. Limiting and filtering components will be added as necessary.
- 1KΩ resistor in line with the emitter.
- 100Ω resistor in line with the power for the receiver
- 10µF capacitor from the Vcc to Gnd for the receiver
Values for the receiver were based on Miles Tag receivers.
Success with RGB light
Downloadable Files:
To do:
- Wrist mount
- Make base for keyboard
- Spacers
- Magnet mounts
- 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 f
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-15 (Th)
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 f
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-15 (Th)
Comments
Post a Comment