 | | Re: Why NQC over Robolab?
|
|
(...) 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 (...) (20 years ago, 10-Dec-04, to lugnet.robotics)
|
| |
| | 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 (...) (20 years ago, 10-Dec-04, to lugnet.robotics)
|
| |
| | Re: Why NQC over Robolab?
|
|
(...) It is the latter. (...) 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 (20 years ago, 11-Dec-04, to lugnet.robotics)
|
| |
| | Re: Why NQC over Robolab?
|
|
(...) Then I would like to announce that NQC supports the MicroScout and CodePilot bricks. It has had this support for several years. (...) The Spybot is a fully programmable lego brick like the RCX and Scout. Like the Scout its firmware is in ROM. (...) (20 years ago, 12-Dec-04, to lugnet.robotics)
|
| |
| | Re: Why NQC over Robolab?
|
|
(...) I suspected as much. (...) Well crud. Now I'm going to have to go out and get one of those things. (...) Suffice to say, Robolab does not currently support the Spybot. Sounds like an interesting project though.... Tom (20 years ago, 13-Dec-04, to lugnet.robotics)
|
