>
> I went to the website www.oopic.com to have a better understanding of
> what it does. Is there anyone who could explain what they were saying
> in laymans term (see bottom paragraph)? This is my first time using
> the Oopic microcontroller. I would really appreciate any kind of help
> anyone is willing to give. Thank you =]
>
I almost always learn by doing. To that end, there are a lot of
examples in the downloaded IDE directory structure.
First, virtual circuits: these are the reason for the OOPic and while
a somewhat advanced concept, they are the means for getting speed out
of an OOPic.
Suppose you wanted to watch an input and do some processing when it
went to a specific state. You COULD write a loop to do the sample and
conditionally process and this is what you would do in a non-OO
processor. In the case of the OOPic, you define the input with an
oDIO1, connect it to an oEvent object and write the event code. From
your point of view, there is no loop and the event code gets executed
by 'magic'.
Next, objects: by predefining certain objects like oServo, you are
spared having to figure out how to generate a pulse of about 1.0 to
2.0 mS wide, repeating every 20 mS or so. All you do is pick an
IOLine for the output, set the adjust property to certer the servo,
set the operate property to start it up and, finally, every time you
set the value property, the servo position changes. Magic...
The idea is abstraction: you don't need to know how each object
performs its' function, you just need to set the properties and use
the various methods that may be provided.
The OOPic is the absolute fastest way to prototype a gadget. To the
extent that objects are defined that will lead to a solution, you
won't find a better approach.
The downside is that some operations are clubby with no improvement in
sight. Serial IO is one operation that can be done much better in a
more conventional processor. I2C and SPI are others that can be
improved. The size of object memory is another limitation.
There are always tradeoffs. The OOPic is very fast for prototyping
but there are some blazing fast microcontrollers available if
development time is not an issue.
As you work with the OOPic, post your questions here. It is also
useful to post your successes.
Final thought: once you get past the startup portion of the learning
curve, begin to think in terms of virtual circuits. Executing lines
of code is not all that fast on the OOPic so you really want to move
away from long execution loops.
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:
No comments:
Post a Comment