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.

Wednesday, April 2, 2008

[oopic] Re: reading a high speed D-wave pulse from a compass

--- In oopic@yahoogroups.com, Jerry Baccari <jerry_baccari@...> wrote:
>
> I mis-stated the frequency of the pulse. It is
> actually 50khz. Does this bring it back into the realm
> of the OOPIC?

Sure, the OOPic can count the pulses at that rate. The problem is to
know when to start and stop counting. Looking at the scope images
you sent me off-line, it appears that there is a wide front porch
pulse followed by the pulses to count.

The dickens will be in detecting that front porch. Measuring pulse
widths isn't a strong point for the OOPic. You not only need to
detect the front porch, you need to zero the counter. Actually, I
guess you need to grab the previous reading at this time as well.

With a regular PIC, you could time the width of each pulse looking
for a pulse above a certain width. This would be used to reset the
counter. Subsequent pulses would increment the counter.

Richard

------------------------------------

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: