Subject:
|
Re: Lab View
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Sat, 19 Jun 1999 13:20:31 GMT
|
Original-From:
|
DanL08@*spamless*aol.com
|
Viewed:
|
1103 times
|
| |
|
|
In a message dated 6/18/99 8:07:18 PM Eastern Daylight Time, robkc@home.com
writes:
<< As far as I can tell Robolab is really a slightly trimmed version of
Labview,
with the bulk of the standard Labview VIs removed.
More important however, is the fact that since the RCX is a remote device,
you
don't really make use of it in the same way. That is, you build VIs which
the
Robolab based application interprets into byte code that it downloads into
the
RCX, as opposed to running locally. Once the byte code is downloaded into the
RCX, the robolab application stops running (& you can continue editing the
VI). There is very little, if no, interaction with your PC or Mac.
I would suspect that the Robolan VIs could be run under Labview, since my
suspicion is that the VI itself does the downloading , however I am not 100%
on that.
If you are interested in a direct PC connection to Lego equipment you might
want to consider getting a Lego controller instead, which has a serial
interface to a number of IO ports. You can then use a free extension to
Robolab (you still need it or a version of Labview). called Lego Engineer,
which uses Labview/Robolab to drive the Lego IO in "real time". >>
The one point which you may have forgotten is that in the "Extras" folder
there are VIs that allow direct control over the RCX. There are also a bunch
of other goodies in there as well. It really adds to the level of
programming using RoboLab.
DAN
--
Did you check the web site first?: http://www.crynwr.com/lego-robotics
|
|
1 Message in This Thread:
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
Active threads in Robotics
|
|
|
|
|
|
