 | | 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 (...) (20 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 (...) (20 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 (...) (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)
|
| |
| | Re: combining LDCC and NQC style automation?
|
|
(...) [snip] (...) [snip] (...) Sorry, I should have thought of that when crossposting to .robotics.rcx (URL) picture has a good view of the headlight and the trolley poles. The trolley poles are the long things on the roof that pick up the power (...) (20 years ago, 14-Jan-05, to lugnet.robotics.rcx, lugnet.trains)
|
| |
| | Re: combining LDCC and NQC style automation?
|
|
Chris, Thanks for asking these questions. I think this has been discussed before, but it is always good to rehash this at least for the .trainheads! I think that remote train operation and LDCC etc is very exciting but perhaps only for the strong (...) (20 years ago, 13-Jan-05, to lugnet.robotics.rcx, lugnet.trains)
|
| |
| | Re: combining LDCC and NQC style automation?
|
|
(...) Chris, I'm not up on my trolly design. Can you explain or show pictures of the "lights" and "trolly poles" You can not use NQC and LDCC. It's like running two operating systems on your PC. Only one works at a time. Steve (20 years ago, 13-Jan-05, to lugnet.robotics.rcx, lugnet.trains)
|
| |
| | combining LDCC and NQC style automation?
|
|
OK, so I made a trolley go back and forth using NQC and my RCX. My wife's response to this was, "I that why you wanted a Mindstorms set?" Her tone implied that while whe thought it was cool, she also thought that I had just reached a new level of (...) (20 years ago, 13-Jan-05, to lugnet.robotics.rcx, lugnet.trains)
|
| |
| | Re: New NQC API for RCX-Spybot or RCX-RC communication
|
|
(...) I forgot to include a few #defines: #define SERIAL_PACKET_RC 0 // default #define SERIAL_PACKET_SPYBOT 0 #define SERIAL_COMM_RC 7 // 4800/76KHZ/25% #define SERIAL_COMM_SPYBOT 7 // was SERIAL_COMM_4800 + SERIAL_COMM_76KHZ The RC function, by (...) (20 years ago, 12-Jan-05, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
| |
| | Re: RCX seems outputs different power levels
|
|
(...) snip (...) Well first thing I'd do is try it without ganging the outputs - that's really only required if you're going to be drawing a large current, and it doesn't sound like your trolley does that. ROSCO (20 years ago, 12-Jan-05, to lugnet.trains, lugnet.robotics.rcx)
|
| |
| | RCX seems outputs different power levels
|
|
Last night I decided to redesign my point to point trolley program. I decided to connect the three RCX outputs in parallel (as suggested by some of LDCC documentation). I also decided to use one of sensor inputs to set the power setting. When I (...) (20 years ago, 12-Jan-05, to lugnet.trains, lugnet.robotics.rcx)
|
| |
| | New NQC API for RCX-Spybot or RCX-RC communication
|
|
Recently I happened across the MindScript headers for the RCX in the SDK and saw some interesting macros for RCX communication. I decided to port them to NQC and possibly add them to the official built-in NQC API. I would be extremely grateful if (...) (20 years ago, 12-Jan-05, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
