 | | Re: Why NQC over Robolab?
|
|
(...) Sounds great. But I run the nqc compiler on Linux and have no COM... (...) Sometimes I dream of a BricxCC written in Java, running on Win, Linux or OSX with Control Lab and all kind of features... something like an Bricklipse... (...) Well... (...) (22 years ago, 9-Dec-04, to lugnet.robotics)
|
| |
 | | Re: Why NQC over Robolab?
|
|
(...) Not true RoboLab supports the Scout, microscout and Interface B. (22 years ago, 9-Dec-04, to lugnet.robotics)
|
| |
 | | Re: Why NQC over Robolab?
|
|
(...) Here's a link to the "Robolab for LavVIEW" that Tom was talking about: (URL) is a ~50 MB download. This is version 2.5.2. You can download the patch (4 MB) to 2.5.3 here: (URL) tufts.edu site says that "Robolab for LabVIEW" has only been (...) (22 years ago, 9-Dec-04, to lugnet.robotics)
|
| |
 | | Re: The Great Ball Contraption (was Re: Rolling ball clock revisited)
|
|
(...) There will be a minimum throuhgput to solve that. Right now, we're testing with 1 ball/second. So, the very first module will be regulated to run somewhere just below that speed. As long as everyone else can meet the minimum, there will be no (...) (22 years ago, 9-Dec-04, to lugnet.technic, lugnet.robotics)
|
| |
 | | Re: The Great Ball Contraption (was Re: Rolling ball clock revisited)
|
|
(...) Looks fun ;o) One of my goals when building Bob's clock was to get my feet wet in ball moving... One foreseeable issue: if an upstream unit has more throughput than a downstream one, we shall get ball overflows! Philo (22 years ago, 9-Dec-04, to lugnet.technic, lugnet.robotics)
|