Quote:
|
Originally Posted by duane
We are going to be using three encoders, two for position control (on the drive wheels) and one for speed control. We expect the motor that we need speed control on to be going a max of about 2500 RPM. We are using the 63K encoders that should handle this speed, but I'm concerned about the interrupt speed on the processor.
Are we going to overwhelm the processor? If the processor is at 10MHz, 2000RPM with a 64 PPR encoder is a little over 2100 interrupts per second. That doesn't seem to bad, but we don't have first handle knowledge like some others.
Add in some positioning encoders, and is this going to work?
Thanks for the advice.
...Duane
|
Why do you need 64 PPR encoders on the shooting wheel? Just use a disk with a couple of holes drilled in it and a break-beam detector.
Oh and by the way, the controller will handle a few thousand pulses per second in quadrature; that should be much higher without quadrature, as you just have to increment a counter. And I think the proccessor is running at 40MHz, not 10MHz.
Just my 2 cents...
__________________
CMUCam not working? Tracks sporadically? Try this instead:
http://www.falconir.com!
PM me for more information if you are interested (it's open source!).
Want the FIRST Email blasts? See here:
http://www.chiefdelphi.com/forums/sh...ad.php?t=50809
"The harder the conflict, the more glorious the triumph. What we obtain too cheaply, we esteem too lightly; it is dearness only that gives everything its value."
-- Thomas Paine
If it's falling apart it's a mechanical problem. If it's spewing smoke it's a electrical problem.
If it's rampaging around destroying things it's a programming problem.
"All technology is run on 'Magic Smoke' contained within the device. As everyone knows, whenever the magic smoke is released, the device ceases to function."
-- Anonymous
I currently speak: English, some German, Verilog, x86 and 8051 Assembler, C, C++, VB, VB.NET, ASP, PHP, HTML, UNIX and SQL 