Subject:
|
Re: Why NQC over Robolab?
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Fri, 10 Dec 2004 21:49:26 GMT
|
Viewed:
|
1327 times
|
| |
|
|
In lugnet.robotics, John Hansen wrote:
> In lugnet.robotics, DanL08@aol.com wrote:
> > > > First, Robolab is for working with the RCX. I saw no Scout >>or microscout support.
> >
> > Not true
> > RoboLab supports the Scout, microscout and Interface B.
>
> Can you explain exactly how RoboLab support the MicroScout? I'm guessing you
> can write simple scripts that can be downloaded using the USB tower's VLL
> support. Is that right?
Robolab uses the Scout as an intermediary. Essentially, you program the Scout
to program the microScout. Using the Scout, scripts or direct commands are sent
to the MicroScout. Robolab supports the Code Pilot in the same fashion.
Although this method may seem somewhat convoluted, it works quite well.
I would guess that it is possible to do nearly the same thing in NQC?
Tom
|
|
Message has 1 Reply:
 | | Re: Why NQC over Robolab?
|
| (...) I'm having a hard time grasping the concept for some reason. In Robolab do you say "I want to write a program for the MicroScout" or do you simply have a component that can be placed into a script written for the Scout which says "send a VLL (...) (19 years ago, 10-Dec-04, to lugnet.robotics)
|
Message is in Reply To:
| | Re: Why NQC over Robolab?
|
| (...) Can you explain exactly how RoboLab support the MicroScout? I'm guessing you can write simple scripts that can be downloaded using the USB tower's VLL support. Is that right? John Hansen (19 years ago, 10-Dec-04, to lugnet.robotics)
|
7 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
|
|
|
|
