Subject:
|
Re: Thoughts & Issues w/ Vision Command
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Wed, 23 Aug 2000 20:03:43 GMT
|
Original-From:
|
The Gaff <the_gaff@hotmail.com#nospam#>
|
Viewed:
|
771 times
|
| |
|
|
> > Hopefully these are limitations because I have overlooked features • already
> > in the VC software or I am just not creative enough at this hour (it's
> > almost 3:30am here).
>
> I couldn't find any way to use the onboard sensors or interact with
> programs that might already be on the RCX. They seem to have
> completely left that out.
It's my understanding that when Vision Command detects motion (or color -
however you have it set), it sends a Message to the RCX. The Message is the
number of the onscreen Vision Command Region that was triggered. Vision
Command also sends "in range" messages to the RCX every five seconds; if no
response is received, the Vision Command "program" terminates.
So, what you must do is write your program to respond to messages
(corresponding to screen regions in the mask you've selected) as well as
sensor input, and download this program into any RCX program slot except
five. Once Vision Command has started up, you must switch the RCX from
program five to your program. This must be accomplished between "in range"
messages to prevent Vision Command from terminating.
[Thanks to Mindstorms host Envcons for the info!]
Issac.
|
|
Message has 1 Reply:
Message is in Reply To:
 | | Re: Thoughts & Issues w/ Vision Command
|
| (...) I was really impressed by the software at first too, but as I played with it, the next natural thing I wanted to do was start building smarter robots that could use the on board sensors. I couldn't find any way to use the onboard sensors or (...) (24 years ago, 23-Aug-00, to lugnet.robotics)
|
3 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
|
|
|
|
