Subject:
|
Re: Why NQC over Robolab?
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Wed, 8 Dec 2004 22:33:40 GMT
|
Viewed:
|
1018 times
|
| |
|
|
In lugnet.robotics, Michael Obenland wrote:
> Hi,
>
> > Specifically, with regard to the RCX, Scout, and microScout, what can you
> > do in NQC that you cannot do in Robolab?
>
> Actually, I've only played with the Robolab demo version.
>
> First, Robolab is for working with the RCX. I saw no Scout or microscout support.
I'm actually quite familiar w/Robolab--it is NQC that I don't know much about.
Robolab (2.5.x) supports The RCX, Scout, microscout, and the Control Lab
Interface. It also supports the LEGO cam. I believe the demo is of a much
earlier and buggy version.
>
> The target of Robolab is the use in education, for example at schools. Robolab
> is related to Mathlab and the "programming" works in a visual way by the
> combination of logial and functional blocks. In a way, it is something like
> the programming env. you get with your rcx box but goes much deeper.
Robolab is based on LabVIEW, a programing environment targeted at scientists and
engineers. The language of LabVIEW is known as "G" and is no more or less
"real" than text based languages. Programs are drawn rather than typed but the
results are the same.
> real money for Robolab and with real money I could buy real bricks instead...
Very True!
Thanks for your input.
Tom
|
|
Message is in Reply To:
 | | Re: Why NQC over Robolab?
|
| Hi, (...) Actually, I've only played with the Robolab demo version. First, Robolab is for working with the RCX. I saw no Scout or microscout support. The target of Robolab is the use in education, for example at schools. Robolab is related to (...) (20 years ago, 8-Dec-04, to lugnet.robotics)
|
12 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
