Track your object RAM usage, that will determine when you can't get any
more into the ooPIC. One way to deal with it is to not use any more
oByte or oWord objects than you have to, use data variables for as much
as you can. You have 86 bytes of object memory, use it wisely and be
efficient and you can get an entire robot in. I have built line
followers and mini sumos with ooPIC boards with no problems.
DLC
red71956 wrote:
> How many VCs (virtual circuits) can I be expected to reasonably run?
> Would using Userclass objects make any difference as opposed to VCs?
> I am assuming a program that uses about 60 bytes or so, leaving wiggle
> room. One VC for general motor control, one for obstruction detection,
> one for communication... how much is too much?
> Another way of asking: when would I know it is my fault (coding) and
> not a limitation?
>
> On a different but related note, anybody work up any good error-
> trapping routines?
>
>
>
>
> Yahoo! Groups Links
>
>
>
--
------------------------------------------------------
Dennis Clark ooPIC Tech Support
www.oopic.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:
No comments:
Post a Comment