 | | Re: sub-vi begin vs end control
|
|
(...) Hi, This is a *minor* bug in RoboLab. The sub-vi diagram will have begin and end terminal labels swapped, but the program will function properly. Use the text tool to rename the terminal labels. Thought it should have been rectified in ver (...) (21 years ago, 17-Jan-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx)
|
| |
| | Re: sub-vi begin vs end control
|
|
(...) In a LabVIEW program (vi) there is a front panel and a block diagram. The front panel is the user interface and contains both controls and indicators. When you place a control/indicator on the front panel a corresponding terminal is created on (...) (21 years ago, 17-Jan-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx)
|
| |
| | RE: sub-vi begin vs end control
|
|
Hi Tom, Just for my education purpose, I'd like to understand the difference between the "begin" & "end" control boxes at the "Front Panel" window. Although they look identical, they must be different since they failed to wire to the blocks next to (...) (21 years ago, 16-Jan-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx)
|
| |
| | Re: sub-vi begin vs end control
|
|
(...) It is a leftover from LabVIEW. When you create a sub.vi, LabVIEW reuses the name of whatever is wired to the control/indicator. This behavior makes perfect sense in LabVIEW but much less so in Robolab. FWIW, the names are little more than (...) (21 years ago, 16-Jan-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx)
|
| |
| | sub-vi begin vs end control
|
|
Hi, After a sub-vi is created, there are two controls created namely begin and end. Would someone explain why they are backwards? That means, it creates an "end" control linked to the beginning of the sub-vi, while the "begin" at the end. Thank in (...) (21 years ago, 16-Jan-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx)
|
| |
| | Re: sub programs
|
|
"Elizabeth Mabrey" <emabrey@storming-robots.com> wrote in message news:200501140706.j0...ing.com... (...) Both RCX 1.0 and 2.0 use the same firmware which supports 40 total subroutines. Subroutines are dedicated to the five program slots so that (...) (21 years ago, 14-Jan-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx)
|
| |
| | RE: sub programs
|
|
Ok... I figured that out how to make sub-vi have that linked inside a vi. The question about the RCX 2.0's capability still remains unknown... --thanks (...) (21 years ago, 14-Jan-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx)
|
| |
| | sub programs
|
|
Hi I wonder if I can call a sub program (another vi) within a program. There is an icon command for inserting another vi program into a program, but it does not seem to be a usable function though. Please advise. I understand the maximum of (...) (21 years ago, 14-Jan-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx)
|
| |
| | Re: Robolab Documentation
|
|
The replacement firmware has several modes for displaying the clock. HH.MM, MM.SS and M.SS.S. The first format is the Lego standard whcih I find failry uninformative. The clock is reset to zero whenever RCX is powered up although many IDE's reset it (...) (21 years ago, 7-Jan-05, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab Documentation
|
|
(...) based on a question that I asked back on Dec 11: "I followed instructions replacing firmware.txt with the replacement file as instructed. The download went smoothly,immediately upon finishing (two beeps) the LCD screen started counting in (...) (21 years ago, 7-Jan-05, to lugnet.robotics.rcx.robolab)
|
| |
| | RE: Robolab Documentation
|
|
Although I shall not consider that as a manual, this is a very good reference book for intro to Robolab. Well, just say intro may not be fair either, as it does include some advanced concepts at the end of the book. It contains useful sample codes, (...) (21 years ago, 5-Jan-05, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab Documentation
|
|
(...) for ROBOLAB before I order it? By the way, Dick, can you say if your new firmware works with ROBOLAB 2.5.4? Jerry (21 years ago, 5-Jan-05, to lugnet.robotics.rcx.robolab)
|
| |
| | Robolab Documentation
|
|
Several recent posts have complained about the lack of Robolab documentation. "Engineering with Lego Bricks and Robolab" seems like a pretty good reference / tutorial handbook. It's available from (URL) (21 years ago, 4-Jan-05, to lugnet.robotics.rcx.robolab)
|
| |
| | RE: New invention instructions
|
|
(...) Participating the state FIRST LEGO League Tournament is a great idea. However, the challenging effect varies greatly. I guess it really depends on who holds the events. I went to one held in my state, I was completely disappointed. It turned (...) (21 years ago, 4-Jan-05, to lugnet.build, lugnet.people, lugnet.people.newbie, lugnet.people.teens, lugnet.robotics.rcx.robolab)
|
| |
| | Re: Today's Challenge
|
|
(...) Your apologizing to be a teacher is accepted ;-) However, you must not apologize to work with ROBOLAB ! Anybody who followed the development of great LEGO robots has seen that ROBOLAB allows easy programming from beginners to absolute (...) (21 years ago, 4-Jan-05, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: New invention instructions
|
|
(...) Four: -If you're between 9-14, ask teacher at school to join First Lego League. Five: -If you're not, participate in a local LUG or organization that has regular robotics challenges, etc. Calum (21 years ago, 4-Jan-05, to lugnet.build, lugnet.people, lugnet.people.newbie, lugnet.people.teens, lugnet.robotics.rcx.robolab)
|
| |
| | Re: New invention instructions
|
|
(...) three variations: ONE: a) look around you room, dig in your LEGO boxes, have a walk through the cellar or the attic b) build the facinating idea you just had. TWO: a) turn on your computer, start the web browser b) find something facinating (...) (21 years ago, 4-Jan-05, to lugnet.build, lugnet.people, lugnet.people.newbie, lugnet.people.teens, lugnet.robotics.rcx.robolab)
|
| |
| | Today's Challenge
|
|
A cry for help: I am trying to implement Ben Williamson’s Fetchbot (URL). I am happy that I have the mechanics right. The problem is that I want to emulate Ben’s code in Robolab. (Yes, there are reasons I use Robolab which include me being a teacher (...) (21 years ago, 4-Jan-05, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: questions on events
|
|
(...) This is where you use the event fork(s) that you asked about in a different message. You nest these forks to determine which event has been triggered. (...) Robolab is just a LabVIEW program. Viewed in that context, it is an amazing bit of (...) (21 years ago, 3-Jan-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.nqc)
|
| |
| | Re: questions on events
|
|
(...) Yeah, my fault. I said two things that do not have to follow. Yes, you can use one event monitor to watch more than one event... and yes, you can't nest event monitoring statements. I've not used an event watcher to monitor more than one event (...) (21 years ago, 3-Jan-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.nqc)
|
