maybe try to show the code you have written.. maybe its just software... as wirh interrupts you must clear some flags before exiting the interupt routine or the interrupt will just go loop forever.. "Dan Price" wrote in message news:4800c2c60609141458g46821400yfb249b309e1b5b82@mail.gmail.com... > >jtroxas wrote: >>put eather a software delay or a hardware delay by using a timing >>capacitor >>in parallel and a pullup resistor when querying for input on the interrupt >>1 >>millisecond is good enough delay.. If you go with the hardware solution >>you >>will need a an input pin assigned to the button that is schmitdt triggered >>as the rising time for the button pulse is greatly reduced.. >>the button may be springing... and producing unwanred pulses... > > Thanks for the response. The first thing I thought of was button > "bounce" so I tried a software delay and tried activating the built in > pull-ups in the mcu to no avail. I was going to go with a hardware > solution but the thing is that if I physically remove the button from > my breadboard the problem still persists. This suggests to me that > the button itself is not the problem. Is there some other way I could > be getting bounce-like intereference or some kind of cross-talk > simply by turning ANSEL off? > -- > http://www.piclist.com PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist > -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist