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, August 6, 2008

Re: [oopic] Re: instructions per second

If you had been keeping up with this group all along, you'd know that
I'm well aware of the OOPic's script code execution speed. And
again, you've eliminated context by changing the thread subject (it
was "storing data to oopic").


The original context (written by another member):

"The incoming (serial) buffer is 4 bytes.

As Dennis said, the OOPic can't keep up with a GPS under any
condition or, as I might have said, it is darn difficult and it is
about the ONLY thing the OOPic can be doing.

Let's say the OOPic executes about 1000 instructions per second
(although there are certainly examples where it only executes about
400). Four incoming chars takes about 13 mS so the buffer is full
(if starting from empty) in somewhere around 13 (or 5!) lines of
code. That is the buffer will be completely full - starting from
empty."


Most GPS receivers send data at 4800 bps, which is 480 characters per second.

The OOPic "average lines of source code executed per second" figure
is LESS than 480.

The OOPic can't execute "13 lines of code" in 13 ms (more like 37
ms), hence my comment. And 4 characters at 4800 bps would take about
8.3 ms by my reckoning, so keeping up with a GPS is just that much
more impossible.


At 09:01 PM 8/5/2008, scottmsavage wrote:
> > > rtstofer wrote:
> > > Let's say the OOPic executes about 1000 instructions per second...
>
> > Andrew Porrett <slicerwizard@...> wrote:
> > I'd like to see an example that executes anywhere near 1000 user
> > source code lines per second.
> > ...Andy
>
>
>Andy,
>
>"instructions per second" and "user source code lines per second" are
>two different things and cannot be compared. Its the old Apples and
>Oranges thing.
>
>"instructions per second" relate to the number of instructions the
>processor can handle each second.
>
>"user source code lines per second" relate to an average based on
>coding style.
>
>For instance:
>
> a=1
>
>compiles into 3 instructions.
>
> a=abs((a*2+9)/2)
>
>compiles into 12 instructions.
>
> If (a=1) then a=abs((a*2+9)/2)
>
>compiles into 20 instructions.
>
>The details of how fast the 8-bit ooPIC interpreter chips operate can
>be found on the following page which does a comparison to the Basic
>Stamp which also publishes speed in "Instructions per second":
>
>http://www.oopic.com/vsbs.htm
>
>Scott Savage

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

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: