To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.rcx.robolabOpen lugnet.robotics.rcx.robolab in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / RCX / ROBOLAB / 362
361  |  363
Subject: 
Re: questions on events
Newsgroups: 
lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.nqc
Followup-To: 
lugnet.robotics.rcx.robolab
Date: 
Mon, 3 Jan 2005 22:08:26 GMT
Viewed: 
12192 times
  
In lugnet.robotics.rcx.robolab, Brian Davis wrote:
In lugnet.robotics.rcx.robolab, Elizabeth Mabrey wrote:

firmware... You can monitor multiple events, but only in
*different* tasks. In other words, (to my knowledge) you can
not "nest" event monitors.

Hmm..., notice that the start monitoring icon allows to
watch for multiple events within the same task.  If each
task can only monitor a single event, that feature being
there does not quite make sense.

   Yeah, my fault. I said two things that do not have to follow. Yes, you can
use one event monitor to watch more than one event... and yes, you can't nest
event monitoring statements. I've not used an event watcher to monitor more than
one event previously.

....if only one event monitor can take place in
a single task

   Then you use one monitor to watch for multiple events. The trick is
determining which event(s) fired to trip you into the event handling branch. In
NQC there's a command to interrogate the firmware to determine which event(s)
have fired after the fact - the question now becomes, where in Robolab does such
a command exist?

This is where you use the event fork(s) that you asked about in a different message.   You nest these forks to determine which event has been triggered.


I always create comment as synopsis  at the
top of my robolab vi file.

   Sigh. I wish I had the time to understand Robolab better. Seems like a
wonderful language (especially for my 7-year-old) but the enviroment really put
me off when I started in with it.

Robolab is just a LabVIEW program. Viewed in that context, it is an amazing bit
of coding.  I'm a G programmer myself and am very impressed w/what the folks at
Tufts did.

However, if you lack that context, I imagine that Robolab is tremendously
frustrating.  The environment is loaded w/LabVIEW artifacts that must just seem
weird, the documentation is pitiful at best, I've yet to find a decent tutorial,
and previous versions were quite buggy.

That said, I've had great success w/Robolab and find it to be a very intuitive
way to program.


Tom



Message is in Reply To:
  Re: questions on events
 
(...) Yeah, my fault. I said two things that do not have to follow. Yes, you can use one event monitor to watch more than one event... and yes, you can't nest event monitoring statements. I've not used an event watcher to monitor more than one event (...) (19 years ago, 3-Jan-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.nqc)

5 Messages in This Thread:

Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR