??? 11/13/09 17:46 Modified: 11/13/09 17:48 Read: times |
#170764 - Some hints Responding to: ???'s previous message |
As previously noted, you can tie your interrupt pin to a high level state and make sure that irregularity does not follow. Make sure the CPU is not constantly being reset via the /RST pin. Make sure your clock source is stable. Make sure you do not have multiple interrupts going on at the same time and this one has a low priority. The interrupt pin should have an internal pull-up resistor (no worries there). Another tid bit is that if you trigger in the nanosecond regime your CPU may not be fast enough to poll the interrupt port to cause an interrupt. That is the CPU side, more likely you might find your comparator to be at fault because you stated that even when the IR portion is not active it still triggers. Which means your comparator is not working as you intended. |
Topic | Author | Date |
interrupt trouble | 01/01/70 00:00 | |
Much more info needed | 01/01/70 00:00 | |
more info | 01/01/70 00:00 | |
Have you looked at all signals? | 01/01/70 00:00 | |
yet more info | 01/01/70 00:00 | |
Some hints | 01/01/70 00:00 | |
No | 01/01/70 00:00 | |
Doesn't the '324 have an OC output? | 01/01/70 00:00 | |
Very good | 01/01/70 00:00 | |
Debugging time! | 01/01/70 00:00 | |
no oscilloscope :( | 01/01/70 00:00 | |
then try 'selective grounding' | 01/01/70 00:00 | |
This might be the reason | 01/01/70 00:00 | |
Dangerous approach! | 01/01/70 00:00 | |
Correct | 01/01/70 00:00 | |
hysteresis? | 01/01/70 00:00 | |
aka positive feedback | 01/01/70 00:00 | |
Dead gap![]() | 01/01/70 00:00 |