 | | Re: Why NQC over Robolab?
|
|
(...) Oops. Thanks for the correct link, John. (...) debugging the existing ones. That said, version 2.5.4 is excellent. The event bugs have been fixed as well as a ton of others. Also, more (not all) of the underlying code is unlocked. This allows (...) (22 years ago, 9-Dec-04, to lugnet.robotics)
|
| |
 | | 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: brickOS port to FreeBSD
|
|
(...) I think the latest official gcc-binaries for brickOS are still 2.95.x. However, I have binutils-2.15 and gcc-3.4.0 running under linux and had only minor problems. Make sure you compile gcc without the stdc++ libraries or just ignore the (...) (22 years ago, 9-Dec-04, to lugnet.robotics.rcx.legos)
|
| |
 | | Re: Wire communication
|
|
(...) I think all you really need to do is switch the motor port between "float" and "brake". That's the same as opening and closing a touch sensor. I've used that for simple signals, and it seems to work fine, but I haven't tried more complex (...) (22 years ago, 9-Dec-04, to lugnet.robotics.rcx.legos)
|
| |
 | | 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)
|
| |
 | | Wire communication
|
|
Hello, I am currently trying to implement a communication protocol between two bricks using just one of the copper wire given with the brick. The protocol is based on manchester encoding, using a well-timed alternation of up and low signals. My (...) (22 years ago, 9-Dec-04, to lugnet.robotics.rcx.legos)
|
| |
 | | Re: input used as output
|
|
well I've decided to go with 2 RCX's anyway. Later I may switch to a non-lego controller ala handyboard, brainstem, etc. Anyway, for the record, the current is also pulsed in order to get the reading from the photoreceptor. I still suspect I could (...) (22 years ago, 9-Dec-04, to lugnet.robotics)
|
| |
 | | Re: Why NQC over Robolab?
|
|
(...) The only version I can find is here: (URL) This version is crippled and makes Robolab seem extremely limited. I seem to remember a more complete demo of version 1.5 but I can't find it. Another option is "Robolab for LabVIEW" found here: (URL) (...) (22 years ago, 9-Dec-04, to lugnet.robotics, FTX)
|
| |
 | | Re: Why NQC over Robolab?
|
|
What is the limitations of the demo version? It´s possible to get it downloaded somewhere? Patrick Levy "Michael Obenland" <obenland@t-online.de> escreveu na mensagem news:I8Ev9K.1DCJ@lugnet.com... (...) you (...) support. (...) Robolab (...) like (...) (22 years ago, 8-Dec-04, to lugnet.robotics)
|
| |
 | | Re: What does RCX stand for?
|
|
(...) Me, too. So, I did a search and found it here: (URL) Entering the buzzword "RCX" - out came "robotic command explorer", unless TLC intended it otherwise. C S Soh (22 years ago, 9-Dec-04, to lugnet.robotics.rcx, FTX)
|
| |
 | | RE: What does RCX stand for?
|
|
I think it stands for Robotics Command eXplorer. (22 years ago, 9-Dec-04, to lugnet.robotics.rcx)
|
| |
 | | Re: Why NQC over Robolab?
|
|
(...) Robolab is an example of an IDE as well. Tom (22 years ago, 9-Dec-04, to lugnet.robotics)
|
| |
 | | Re: What does RCX stand for?
|
|
(...) good question. i've wondered about this myself from time to time. ondrew (22 years ago, 9-Dec-04, to lugnet.robotics.rcx)
|
| |
 | | Re: Why NQC over Robolab?
|
|
(...) 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 (...) (22 years ago, 8-Dec-04, to lugnet.robotics)
|
| |
 | | Re: The Great Ball Contraption (was Re: Rolling ball clock revisited)
|
|
(...) One thing Steve forgot - think constant noise. Constant, *constant* noise. But it is a lot of fun... (22 years ago, 8-Dec-04, to lugnet.technic, lugnet.robotics)
|
| |
 | | Ultimate ROBOLAB
|
|
Finally, there it is: We now have Ultimate ROBOLAB ready for beta-testing. Ultimate ROBOLAB is an extension to ROBOLAB that allows you to graphically write your own RCX firmware. Find an introduction at (URL) ROBOLAB254 If you are interested, please (...) (22 years ago, 8-Dec-04, to lugnet.robotics)
|
| |
 | | 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 (...) (22 years ago, 8-Dec-04, to lugnet.robotics)
|