??? 01/26/10 17:52 Read: times |
#172737 - Sensor Problems |
I will keep this fairly simple, and spare you a lot of unnecessary detail!
I am reading a sensor using an SiLabs F060 micro on its development board. The reed sensor is sensing the position of a piston inside a cylinder. This sensor is unfortunately only triggered for around 5-6 milliseconds according the oscilloscope trace I am reading, and is so short because the Actuator moves so damned fast! This 5-6 millisecond pulse is not being sensed by code in my program. I cannot slow this speed down due to the nature of the build. When running the cylinder by hand (not with the pressurised CO2 that normally moves it) it successfully reads this signal, and turns off an output of the micro connected to a valve that has been opened to allow CO2 into the cylinder to allow the actuator to move. Due to the size limitations on the PCB I must use, I am looking for the smallest possible way to increase the time that the signal from the sensor is present at the port pin of the F060. I could use a 555 timer, simple, would work, but far too large. Has anyone here had this problem before? Or did they decide to go with faster switching sensors. (which is an option for me, but as these are highly reliable in the environment (vibration and shock) I was hoping that their may be another solution to my problem. I have found MUCH help here before, and wait for your replies patiently, Regards, Joel |
Topic | Author | Date |
Sensor Problems | 01/01/70 00:00 | |
milliseconds? | 01/01/70 00:00 | |
I wonder too ... | 01/01/70 00:00 | |
use of interrupts | 01/01/70 00:00 | |
Remember state![]() | 01/01/70 00:00 | |
To (almost) quote Star Trek: | 01/01/70 00:00 | |
Counter | 01/01/70 00:00 | |
re-think code | 01/01/70 00:00 | |
Weeelll if you have to | 01/01/70 00:00 | |
misnamed device | 01/01/70 00:00 |