Quote:
|
Originally Posted by Damian Manda
Yes, we have been having problems too.
We have set up our system with the proper code running on both the EDU and Full-Size RC, the beacons wired correctly and the detectors hooked to the correct pins. We know that the beacon is emitting infrared, since we can detect it with a learning remote. When the bacon is off, the remote says "No Infrared Detected." We need to figure out if the beacons are somehow emitting the wrong waveforms/frequencies, or if our detectors are just faulty (we have tried more than one). We have hooked the sensors to various inputs, and even wired it to an LED, to no avail. Is there any way to do this without an oscilloscope or other expensive instrument that we do not have? We have everyone that knows anything about the code and infrared stumped, even the engineers. Any hints on other things to test or try?
--Damian Manda
|
We were fortunate to have not only one but two o-scopes lying around to see the waveforms for both the beacon and detectors. They both are exactly right. Type-1 Beacon causes the detector to go low for 1 ms, Type-2 for 2 ms.
We tryed with the tracking code and traced the problem all the way back to the digital inputs. Tonight I'm going to have a looksey to figure out what may cause the digital inputs to not work. (Note: if you hook up the detector this should keep the signal set to high as long as it doesn't see the beacon).
EDIT: Hmmm.... Maybe I'm wrong and that's why we are having trouble. Looking at the schematics and everything and maybe the input is 1 when the signal goes low. Test for tommorow I suppose.