See my recent post - 37874. The only thing it requires is a little
bit of looking through the compiled code and an oRAM object (3 bytes
of object space).
--- In oopic@yahoogroups.com, "rtstofer" <rstofer@...> wrote:
>
> --- In oopic@yahoogroups.com, gary@ wrote:
> >
> >
> >
> > About a month or so ago you tried to help me with event
> > >programming. I eventually gave up and used To Do Loops figuring
I was
> > >just too dumb to figure it out.
> > > I have another situation that requires Event programming. I
took
> > >the code below from the manual. I changed it so I could see leds
in
> > >different parts of the program but I did not change the event
part.
> > > I would expect the code below to delay 5 seconds turn on the
> > >green led, go to the event subroutine, turn on the red led wait
1
> > >second and turn it off. From there blink the red led every 1
second.
> > > What happens is there is a delay of 5 seconds the green led
comes
> > >on and goes out after a second or so then delays 5 seconds and
comes
> > >back on. Like it is rebooting. This time I have nothing
connected to
> > >the board.
> > > I tried the virtual circuit in chapter 7. That works as
expected.
> > >Could I get you to run this code and see if it works correctly
> > >please? another question that might be related. Pin 21 is
supposed to
> > >be 5 volt pwr I get 6.49 volts. Is that correct?
> > >
> > >c 1.1 + board v 6.1.1 compiler
> > >
> > >Dim BLINK As New oEvent
> > >Dim WIRE As New oWire
> > >Dim led7 As New oLED
> > >Dim led5 As New oLED
> > >
> > >Sub Main()
> > > ooPIC.Delay = 5000
> > > led5.IOLine = 5
> > > led5.TurnOn
> > > led7.IOLine = 7
> > > WIRE.Input.Link(ooPIC.Hz1)
> > > WIRE.Output.Link(BLINK.Operate)
> > > WIRE.Operate = cvTrue
> > >End Sub
> > >
> > >Sub BLINK_Code()
> > > led7.TurnOn
> > > ooPIC.Delay =1000
> > > led7.TurnOff
> > >End Sub
> > >
> > >
> >
> > Hello
> >
> > I have the same problem, I have 5 ooPIC-R boards all purchased
> within the last 3 weeks for a project I m working on, has anyone
found
> a work around for the v6 compiler problem? Do we have any further
> estimates of when this will be fixed?
> >
> > I have also observed the following the system continues to loop
> through the main sub even when a Do..Loop is included in the Sub,
also
> just linking the event, when executed corrupts memory locations of
> other variables in the system, but it appears virtual circuits are
not
> affected.
> >
> > This is a time sensative project, any assistance would be
appreciated.
> >
> > Thanks
> > Rusty
> >
>
> Just my personal opinion but I wouldn't hold my breathe on the
> compiler (firmware?) upgrade. So far, we don't even have a promise
of
> a 'maybe'.
>
> If I had a project that HAD to be done, no matter what, I would buy
> these controller kits http://www.junun.org/MarkIII/Info.jsp?item=28
at
> $49. The 40 pin header is presumed to be compatible with the pinout
> of the OOPic S board although I haven't personally checked it.
There
> is a nice stackable prototype board and sensor board.
>
> Now, armed with boards with older firmware, I would use V5 of the
> IDE/compiler because it has well understood warts. V6 clearly
doesn't
> work (with C.1.1 firmware) and, if I had to get the work done, I
want
> something that will accomplish the goal. V6 events with B.2.2+
> firmware do seem to work. At least they did for me.
>
> A couple of messages back, Dennis gave the link to the older V5
> documentation. I would use that and skip all the 'gee whiz'
features
> of V6.
>
> So, that's my opinion... Others may disagree...
>
> 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