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.

Thursday, July 17, 2008

[oopic] Re: Help with OO code

OK but just on that - does it matter what the value is? ie does a
larger/smaller/type of capicitor's discharge rate ( say, if I don't
have the right one) matter too much? I've read so much where the advice
seems really abtirary! And does the type matter eg electrolytic etc..
Mike M.
--- In oopic@yahoogroups.com, "rtstofer" <rstofer@...> wrote:
>
> --- In oopic@yahoogroups.com, "Mike Martin" <xaviour2me@> wrote:
> >
> > That works! Thanks Richard. I think I understand it a little better
> > now. I hadn't taken the data width into consideration (if that's
the
> > correct term?)It's a lot more jittery than it is with procedural
code
> > for some reason. With the OO it hunts a lot too but I think there's
a
> > solution to that that I read about earlier. Many thanks.
> > Mike M.
>
> Try hanging a 1 ufd capacitor between the A/D input and ground. On
> the scope I didn't see any jitter. It looked pretty solid.
>
> 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: