To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.roboticsOpen lugnet.robotics in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / 23135
23134  |  23136
Subject: 
Re: Why NQC over Robolab?
Newsgroups: 
lugnet.robotics
Date: 
Thu, 9 Dec 2004 21:52:31 GMT
Viewed: 
1234 times
  
This is a "free" way to get the full version Robolab but it requires you own
the student edition of LabVIEW....


Here's a link to the "Robolab for LavVIEW" that Tom was talking about:

http://www.ceeo.tufts.edu/robolabatceeo/college/robolabforlabview/RLforLabview2521.zip


Oops.  Thanks for the correct link, John.


Robolab reportedly has a number of problems with features that don't quite work
reliably (http://news.lugnet.com/robotics/rcx/robolab/?n=294,
http://news.lugnet.com/robotics/rcx/robolab/?n=297)

This issue has always plagued Robolab.  Features have been added w/o thoroughly
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 someone w/knowledge of LabVIEW to fix
bugs.  Unfortunately, a mechanism does not readily exist to report bugs and
fixes.

Robolab can actually run programs on the host PC (for the Control Lab
interface).  You can't do that with NQC.

Robolab can also run the RCX and the Scout in direct mode.  Direct mode lets you
use the camera and microphone as sensors which opens all sorts of possibilities.


It is conceivable that a Control Lab target could be added to NQC which would
let you compile an NQC program into a JavaScript that would use a COM automation
object to talk to the Control Lab.  I'm mildly interested in investigating such
a scheme.  Alternatively, an IDE like BricxCC could be modified to have a
separate Control Lab feature of some sort.  I'm not sure how many people are
interested in such a thing.

Seeing as most folks here seem to use text basted languages, I would love to see such a thing.  The creativity w/3 inputs and outputs has been astounding.   Imagine what would be built given easy access to the control lab's 8 inputs and 8 outputs!



Message is in Reply To:
  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 (...) (20 years ago, 9-Dec-04, to lugnet.robotics)

12 Messages in This Thread:





Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR