Re: [oopic] Re: OOPic-R limits?

Those 256 bytes of internal EEPROM are available to you in the V.6
compiler. Sbyte was vaporware on the V.5 compiler and never worked.
Just define non-object variables and you will be using the variable
space RAM. If you don't need to link the memory to objects then that is
the perfect use for it.

DLC

m.lisowski wrote:

>Thank you all for valuable information. Unfortunately, my hexapod
>robot (12 servos) was already equipped with OOPic-R board when I
>started the project and I wasn't aware of object memory limitation at
>that point.
>
>I seems that external serial controller is the best solution, but
>before I will go for it I need some more information.
>
>How can I use 256 bytes of internal EEPROM memory? Is sByte variable
>implemented and working in B.2.2+ firmware? I thought about storing
>the gate sequence there to free some object memory.
>
>I have some doubts about 72 bytes of variable space. How can I
>access/use it? Maybe it is better then internal EEPROM for storing
>sequences?
>
>
>
>
>
>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:

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