 | | 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 (...) (20 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 (...) (20 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 (...) (20 years ago, 16-Jan-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx)
|
| |
| | Re: combining LDCC and NQC style automation?
|
|
(...) If you'd rather do a little hardware work, than learn pbForth, I have a couple suggestions. 1) You could use LEDs instead of regular lights. An LED will only light, when the power is going the correct direction. So you could connect 1 LED to (...) (20 years ago, 14-Jan-05, to lugnet.robotics.rcx, lugnet.trains)
|
| |
| | Re: combining LDCC and NQC style automation?
|
|
[big snip] (...) I do have DCC in the latest pbForth, but I've sort of dropped official support for older versions of MacOS. That being said, I think the instructions are still up on the site for getting it to work. :-) Please post here if you;re (...) (20 years ago, 14-Jan-05, to lugnet.robotics.rcx, lugnet.trains)
|
| |
| | Re: combining LDCC and NQC style automation?
|
|
Christopher Masi wrote: [snip] (...) [snip] (...) I know, replying to myself, bad form. I have also discovered that pbForth has DCC worked into it. The good new here (although I have only looked at the introduction on the home page) is that Raplph (...) (20 years ago, 14-Jan-05, to lugnet.robotics.rcx, lugnet.trains)
|
| |
| | 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 (...) (20 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 (...) (20 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 (...) (20 years ago, 14-Jan-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx)
|
| |
| | Re: combining LDCC and NQC style automation?
|
|
(...) Ah, so you have dabbled with LDCC? Gave up? Not enough fun for the amount of effort? Or will you be going back to it? (...) Oh, I was just expecting to send power out the top of the motor to light the light, and have a small technic motor (...) (20 years ago, 14-Jan-05, to lugnet.robotics.rcx, lugnet.trains)
|
