| |
> > 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.
|
|
| |
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?
John Hansen
|
|
| |
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
|
|
| |
In lugnet.robotics, Thomas Johnson wrote:
> 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?
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 command to the MicroScout" or "send a VLL command to the Code
Pilot"?
If the latter then NQC already supports the MicroScout and the Code Pilot for
both the Scout and the Spybot targets (and via custom NQC headers files the
RCX).
Does Robolab support the Spybot? If not, why not?
John Hansen
|
|
| |
In lugnet.robotics, John Hansen wrote:
> In lugnet.robotics, Thomas Johnson wrote:
> > 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?
>
> 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 command to the MicroScout" or "send a VLL command to the Code
> Pilot"?
>
> If the latter then NQC already supports the MicroScout and the Code Pilot for
> both the Scout and the Spybot targets (and via custom NQC headers files the
> RCX).
It is the latter.
>
> Does Robolab support the Spybot? If not, why not?
I've never messed w/a spybot so I can't give a definitive answer but if the
spybot is controlled via VLL, then it should be supported.
Tom
|
|
| |
In lugnet.robotics, Thomas Johnson wrote:
> In lugnet.robotics, John Hansen wrote:
> > If the latter then NQC already supports the MicroScout and the Code Pilot for
> > both the Scout and the Spybot targets (and via custom NQC headers files the
> > RCX).
>
> It is the latter.
Then I would like to announce that NQC supports the MicroScout and CodePilot
bricks. It has had this support for several years.
> > Does Robolab support the Spybot? If not, why not?
>
> I've never messed w/a spybot so I can't give a definitive answer but if the
> spybot is controlled via VLL, then it should be supported.
The Spybot is a fully programmable lego brick like the RCX and Scout. Like the
Scout its firmware is in ROM. It has about 4K available for user programs (only
one program slot). It doesn't have a datalog, but it has a large EEPROM area
for storing data. It has very powerful IR features for communicating with other
Spybots (as well as Scout and RCX bricks). It has VLL output capability. It is
the least expensive programmable brick available, but it is also the least
flexible with respect to its outputs and inputs (sensors and motors are all
built-in).
To say that Robolab has support for the Spybot would require that a user could
write a program in Robolab targeted for the Spybot, with blocks that
specifically represented its capabilities for finding and tracking the position
of other Spybots, defining and using LED animations, defining and using sound
effects, EEPROM reading/writing, etc...
NQC has a Spybot API which provides a programmer with direct access to all the
Spybot capabilities, from those it has in common with the RCX2 firmware to those
that are unique to the Spybot firmware.
John Hansen
http://bricxcc.sourceforge.net/nqc/
|
|
| |
In lugnet.robotics, John Hansen wrote:
> In lugnet.robotics, Thomas Johnson wrote:
> > In lugnet.robotics, John Hansen wrote:
> > > If the latter then NQC already supports the MicroScout and the Code Pilot for
> > > both the Scout and the Spybot targets (and via custom NQC headers files the
> > > RCX).
> >
> > It is the latter.
>
> Then I would like to announce that NQC supports the MicroScout and CodePilot
> bricks. It has had this support for several years.
I suspected as much.
>
> > > Does Robolab support the Spybot? If not, why not?
> >
> > I've never messed w/a spybot so I can't give a definitive answer but if the
> > spybot is controlled via VLL, then it should be supported.
>
> The Spybot is a fully programmable lego brick like the RCX and Scout. Like the
> Scout its firmware is in ROM. It has about 4K available for user programs (only
> one program slot). It doesn't have a datalog, but it has a large EEPROM area
> for storing data. It has very powerful IR features for communicating with other
> Spybots (as well as Scout and RCX bricks). It has VLL output capability. It is
> the least expensive programmable brick available, but it is also the least
> flexible with respect to its outputs and inputs (sensors and motors are all
> built-in).
Well crud. Now I'm going to have to go out and get one of those things.
>
> To say that Robolab has support for the Spybot would require that a user could
> write a program in Robolab targeted for the Spybot, with blocks that
> specifically represented its capabilities for finding and tracking the position
> of other Spybots, defining and using LED animations, defining and using sound
> effects, EEPROM reading/writing, etc...
Suffice to say, Robolab does not currently support the Spybot. Sounds like an
interesting project though....
Tom
|
|
|
