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 / 357
356  |  358
Subject: 
RE: questions on events
Newsgroups: 
lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.nqc
Date: 
Mon, 3 Jan 2005 03:27:27 GMT
Viewed: 
12736 times
  
firmware... You can monitor multiple events, but only in
*different* tasks. In other words, (to my knowledge) you can
not "nest" event monitors. But if you use multiple tasks, this
should work OK...

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.

e.g. I have 2 different light sensor events set to watch for value
higher than 42, yellow & blue.  Let say both sensors read 45 at the
same time,  RCX returns only one event being invoked.

   Are you certain? Or is the code from one event watcher
overriding anything happening in the other? I know the
firmware doesn't "loose" events this way, but I'm not sure of
Robolab itself.

This is why I suspect the "event" in Robolab works like system call signal()
in C.   Signal() system interrupt is not stackable.  However, this question
becomes mood point if only one event monitor can take place in a single task



   Asking as someone who became terribly frustrated with both
the nature of Robolab as well as the documentation (*is*
there any?), does Robolab allow access control?
Yea... The doc for robolab is very lacking in significant details.  But
again, this may be because the initiative of Robolab is for education only,
but not industrial usage.  Perhaps you can obtain more info from Labview
documentation since Robolab's back bone is Labview.  And some of the low
level usage of Robolab needs knowledge of G code.

   I never did figure out even the simple Robolab multi-task
structures, like being able to easily kill a task
I guess this is more like killing a thread in a true multitasking
environment.

(does
Robolab allow naming of tasks? Or are you just stuck with the
task number as assigned, and how do you find out what a
task's ID number is anyway?).

I don't know if there is any.  I always create comment as synopsis  at the
top of my robolab vi file.

--
Elizabeth Mabrey @storming-robots.com



Message has 1 Reply:
  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 (...) (20 years ago, 3-Jan-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.nqc)

Message is in Reply To:
  Re: questions on events
 
(...) See previous post for the "I-don't-actually-do-Robolab" disclaimer, but, since Robolab & NQC both work on the same firmware... You can monitor multiple events, but only in *different* tasks. In other words, (to my knowledge) you can not "nest" (...) (20 years ago, 2-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

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

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