To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.rcx.robolabOpen lugnet.robotics.rcx.robolab in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / RCX / ROBOLAB / 32
31  |  33
Subject: 
RE: Making Robolab more open
Newsgroups: 
lugnet.robotics.rcx.robolab
Date: 
Mon, 20 Mar 2000 13:45:27 GMT
Viewed: 
5416 times
  
That's an interesting idea.  I don't have a copy of RoboLab (yet), but I do
use LabView 5.1

Some questions:  Does RoboLab use the standard firmware?  Can you open the
RoboLab VI's to get into the sub VI's?  Can you install the RoboLab VI's
into a LabView VI?  Can you create and save modified Robolab VI's to use in
other RoboLab VI's?

Some of what you're describing is not even available to LabView users (as
far as I know).  The "autowire" function, the constantly wired constant
inputs.  I have to think it is unlikely that National Instruments will
release the source code to RoboLab, so modifications like you are
describing would have to take place within the "stock" product.

Jeff

jeffrey.hazen@northmill.net

-----Original Message-----
From: Richard Hamilton [SMTP:rhamilton@wis.twc.com]
Sent: Sunday, March 19, 2000 10:07 PM
To: lugnet.robotics.rcx.robolab@lugnet.com
Subject: Making Robolab more open

The power of software is sometimes greater than what it's creators/progr
ammers
envisioned. One way to help create this phenomena is to make the software
extensible and extendable by others. Netscape did this by releasing their
source code, and the alternative RCX languages also have this attribute by
being modified in the public domain.

Robolab is a clever adaptation of Labview, yet it is not easily modifiable
by
people who have access to Labview. Would it be possible/feasible to have
instructions on how to modify Robolab using Labview 5.1? Yes, I know the
support nightmare this might cause! I too am in the software support
business,
but the risk is manageable and the potential is open ended.

Some user contributed additions that could result from this might be:

Support of home brew sensors
Additional programming structures (Triple forks, division with remainders,
etc.)
Code to perform an "auto wire" function (automatically wiring blocks that
are
spatially aligned)
Syntax checkers
Subroutines in other languages
Templates for typical icon usage (like all motor commands would always have
a
port and power level wired in so they can be easily changed rather than
created
from the menus)

What are your thoughts?



Message has 1 Reply:
  Re: Making Robolab more open
 
According to Dr. Chris Rogers at Tufts, Labview 6.0 will have an autowire function, and Robolab 2.5 will be written with Labview 6.0 when it is GA. That is better than what I hoped for. I was proposing was getting instructions on how to modify (...) (25 years ago, 21-Mar-00, to lugnet.robotics.rcx.robolab)

3 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