View Single Post
  #2   Spotlight this post!  
Unread 13-02-2005, 15:41
Kevin Watson's Avatar
Kevin Watson Kevin Watson is offline
La Caņada High School
FRC #2429
Team Role: Mentor
 
Join Date: Jan 2002
Rookie Year: 2001
Location: La Caņada, California
Posts: 1,335
Kevin Watson has a reputation beyond reputeKevin Watson has a reputation beyond reputeKevin Watson has a reputation beyond reputeKevin Watson has a reputation beyond reputeKevin Watson has a reputation beyond reputeKevin Watson has a reputation beyond reputeKevin Watson has a reputation beyond reputeKevin Watson has a reputation beyond reputeKevin Watson has a reputation beyond reputeKevin Watson has a reputation beyond reputeKevin Watson has a reputation beyond repute
Re: Processing pre-set Interrupts

Quote:
Originally Posted by Tom Bottiglieri
I am having troubles with my encoder. It is a 128 ppr encoder, and at close to maximum shaft RPM, I start to get bad readings from it. I figured this was from the RC trying to process too many interrupts per second, so I know I need decrease the ppr of the encoder.

The way I thought I could do this was by including a true/false check statement in the InterruptHandlerLow() function that would only call the Encoder Handler Function every other time that interrput happened. I tried doing this with if's and switch statements, but neither worked. I still got 128 ticks per revolution.

Heres a sample of the code I am using.
Code:
unsigned char loops=0;
 
void InterruptHandlerLow() 
{ 
if(loops==0)
{ 
if (INTCON3bits.INT2IF && INTCON3bits.INT2IE) // left encoder interrupt?
		{ 
			INTCON3bits.INT2IF = 0; // clear the interrupt flag [91]
			Left_Encoder_Int_Handler(); // call the left encoder interrupt handler (in encoder.c)
		}
loops=1;
}
else loops=0;
}
Any ideas?
Check the magical Encoder FAQ for a possible answer.

-Kevin
__________________
Kevin Watson
Engineer at stealth-mode startup
http://kevin.org