This Forum is Dedicated For all The Object Oriented PIC Lovers .......... The concept behind OOPic is straight forward. Use preprogrammed multitasking Objects from a library of highly optimized Objects to do all the work of interacting with the hardware. Then write small scripts in Basic, C, or Java syntax styles to control the Objects. During operation, the Objects run continuously and simultaneously in the background while the scripts run in the foreground telling the objects what to do.

Sunday, October 21, 2007

Re: [oopic] Quadrature Encoder

I realized this morning that while I mentioned the pulses per revolution, I
didn't mention the revolutions per second, so the pulses per second couldn't
be calculated.

Unfortunately, I haven't tested what the revolutions per second actually
comes out to, but I believe it would be variable depending on the speed I
have set for the motors. Unfortunately, I think that the top speed could be
as fast as 2 rps, which could mean that the pulse rate could be well over
1KHz, and even if my estimate is excessive, I would come close to the 1KHz
rate. What this might mean is that I can measure the pulses per second at a
few low speeds, and figure out a curve of speed setting vs true speed,
though I suspect it won't be linnear.

Which object(s) in what configuration would get me the maximum resolution? I
suppose if I had an oWord filling with a pulse count each second, that might
be easiest, but it appears that there are a couple of pulse counting
options.

ooPIC Tech Support wrote:
>
> What is your motor speed? The ooPIC can handle up to about a 1KHz rate
> but might get sketchy past that, especially if as you say, you have a
> lot of objects running. From the sounds of it, this encoder will soon
> outstrip the ooPIC's ability to keep up. Try it and see what kind of
> results that you get.
>
> DLC
>
> Shaggy wrote:
>> I'm using an OOPic board and have a pair of motors with quadrature
>> encoders.
>> These put out a pulse rate of 624 pulses/output shaft revolution. From
>> looking at the OOPic documentation, that looks like a pretty high pulse
>> rate
>> to be counting. I hope to return either speed or distance traveled out
>> the
>> serial port. I have all the serial port code worked out, so that all I
>> really need is a way to turn that pulse rate into something useful.
>> Either a
>> pulses per second rate would work, or a number of pulses in the last
>> second
>> (leaving the division up to the receiver and not on the OOPic). I figured
>> somebody on here would have either a suggestion or some example code I
>> could
>> use for that. This is only one piece of a larger project, and I am
>> getting a
>> bit tight on memory, but not excessively so....yet.
>
> --
> ------------------------------------------------------
> Dennis Clark ooPIC Tech Support
> www.oopic.com
> ------------------------------------------------------
>
>

--
View this message in context: http://www.nabble.com/Quadrature-Encoder-tf4663541.html#a13330954
Sent from the OOPic mailing list archive at Nabble.com.


Yahoo! Groups Links

<*> To visit your group on the web, go to:

http://groups.yahoo.com/group/oopic/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:

http://groups.yahoo.com/group/oopic/join

(Yahoo! ID required)

<*> To change settings via email:
mailto:oopic-digest@yahoogroups.com
mailto:oopic-fullfeatured@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
oopic-unsubscribe@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:

http://docs.yahoo.com/info/terms/

No comments: