Jump to content

BrokenArrow

Members
  • Posts

    257
  • Joined

  • Last visited

Posts posted by BrokenArrow

  1. QUOTE (rolfk @ Dec 19 2008, 04:44 AM)

    It could be compiled probably but I would hazard this to be a very time consuming job with little benefit as every driver release or even bug fix will change that again.

    I agree completely. As long as the data exists, and can be found, then I'm happy. It just seems to me that some of the knowledge base is a bit "tribal".

  2. Does NI keep a List of everything that ships with LabVIEW, and where to find it?. By "everything", I mean every VI, Function, and every possible Property and Invoke Node. I know, it would be voluminous, but the data exists somewhere.

    Didn't they used to ship reference books with version 6? What happened to that idea?

  3. QUOTE (vugie @ Dec 15 2008, 05:55 AM)

    There are "Get Property" and "Sete Property" private methods in Generic class. They looks like they set/get properties via property index and using variant type. But you have to know these indices. First several thousands (from 0) does not work for simple digital control :)

    Maybe any of our "rusty nailers" knows sth more?

    Sounds like a great hidden implentation method. ;) I wonder if that works anything like setting the properties of similar decorations? Just guess at which one it might be until... Viola! Then you delete that and add a few more, and.... :throwpc:

  4. QUOTE (mindmoody @ Dec 14 2008, 11:24 AM)

    Hello everyone... again.. i'm back with a new things to solve.. BrokenArrow, i've decide to make my own interface board and this will reduce my project cost right? so right now i've done with the MAX232 circuit. The things in my mind is;

    1. Which microcontroller should i used for this interface? and could anyone give me some advice and recommendation about this?

    Thank you a lots,

    Mindmoody :headbang:

    Stop Dude! There's no WAY you can make your own board for the cost of buying one or two. It sounds like you just need a few Digital Outs - maybe relay, and an Analog In. If you pay yourself a dollar an hour and use the cheapest parts you can find and get a cheap PCB made with no solder mask and silkscreen, you might break even. Now, if you're doing this as a learning exercise, then fine*, but your statement about it reducing cost is off base.

    * I'd recommend the PIC16F876, but LAVA isn't really the forum for that type of thing, insofar as how to make the board, wire it up, etc.

  5. I like orko's two questions ....

    QUOTE (orko @ Dec 3 2008, 02:22 AM)

    The two questions I like to ask myself are, "Does this subVI serve a defined purpose?" and "Will I be using this subVI anywhere else?". If either of the answers is "no", then it may be time to lay the design on the table again and rethink how things are organized.

    but the first can almost always be answered "yes". Such as: "The sub-vi saves space on the wiring diagram", or, "the sub-vi makes the code more modular". I don't think these are necessarily bad reasons to make a sub-vi. A good example of the proper use of a one-off sub-vi would be in the "organization" of multiple Property Nodes for GUI manipulation (wiring in references). Other examples which I use a lot would be in large string concatenations, multiple Select or min/max functions, obtain multiple notifiers, etc. Admittedly, these are "space savers" and not true modular coding techniques (and not true encapsulation), but a one-screen wiring diagram is important to me.

  6. QUOTE (Aristos Queue @ Dec 8 2008, 08:41 PM)

    There is no cluster view of LabVIEW classes -- the data is private and there is no way to get access to it (including FP access) other than through interfaces the programmer exposes (FP access can be exposed through an XControl if the programmer chooses).

    You may have inherited code written with one of the GOOP toolkits, perhaps?

    I bet you're right The originator of the code was a hardcore C++ programmer. It wouldn't surprise me if he used 3rd party OO. I have a good idea... I'll ask him. Sounds radical, I know.

  7. QUOTE (Michael_Aivaliotis @ Dec 9 2008, 03:49 AM)

    ...used to be a hansom man ...

    :laugh: :laugh:

    Anyway, I'm glad to help, but I'm wondering if the Community would be up for a simplification of the categories. Combining a few. Renaming a few. Among other things, maybe putting the General category down under the other categories so it forces users to consider all the options. This way, the "system" has more of a chance to take care of itself, at least that's the idea.

  8. Along these same lines, how come in my OOP code, my class data is a cube, but on some other code I have inherited, it's a cluster showing the class data? How do I get that later thing?

    QUOTE (Aristos Queue @ Sep 9 2008, 05:44 PM)

    ...If you want to insert the block diagram constant into the Functions palette, you can create a VI that has nothing except the constant on its diagram and then add it to the palette as a Merge VI.

    I think you are referring to Place VI Contents. What used to be called Merge is now the deal when you're sopposed to be able to merge two VI's, which is great demo at shows.

  9. IMO, the category "LabVIEW Development Environment" is mis-used a bit. This is a category for questions about the Environment, however it looks like users may be reading to much into the word "Development". Just a quick scan of the latest posts - I'd say at least 50% of them don't belong in there, but could be interprested as belonging there.

    Can I suggest that we rename that category? How about dropping the word "Development"?. Or maybe call it Options and Settings. Or Settings, Options, and Tricks. Something along those lines.

    I dunno. Just a thought. :lightbulb:

  10. QUOTE (TobyD @ Nov 25 2008, 10:59 AM)

    The only way I know to do it is with an intermediate version like you suggest. If it's small I'm sure someone here can upsave it and send it back to you or I think NI will usually hook you up with a trial license of the intermediate version of LabVIEW if you need it for the upsave.

    Good idea, the trial license. I've also been thinking of picking up an old version on eBay. The 6.1 usually goes for cheap.

    This is a great community here and I know someone would upsave for me, but I don't want to give people my busy work, but more importantly, I wanted to know a good solution going forward. I could conceivably have hundreds of these to convert.

    Thanks! :thumbup:

    edit: Toby, your member info says you've been on LabVIEW since 2007? I'd like to nominate you for "Fastest LAVA Ever".

  11. QUOTE (TobyD @ Nov 25 2008, 11:14 AM)

    My point here was just to demonstrate the while loop. I kept his original code unchanged (other than running the diagram cleanup tool on it). That said, the VISA driver used to require a VISA Open at the beginning of a program. It was later changed so that the driver would automatically open a VISA reference if it needs one. So, it is not even necessary to have it in there at all - although it is probably still a good practice from a readability point of view.

    10-4 thanks Toby. And I knew it wasn't your code snippet. I replied to your post simply because it contained the picture. :)

  12. I am disappointed that NI decided to stop opening version 5 files as of 8.5 (I think it was 8.5 when they did that). Version 5.1 is a hugely popular version.

    Anyhooo. How do you "upsave" to 8.5? Lets assume you don't own / have access to an earlier version. The obvious answer is to acquire an old version of 6.x through 8.2 and open the 5.1 VI, save, as the current version, then open in 8.5, but I'm wondering if I'm missing something obvious.

    Thanks! :)

  13. QUOTE (Jim Kring @ Nov 18 2008, 02:21 AM)

    When did this turn into a negotiation? :unsure:

    Don't take my stab at humor the wrong way. I was trying to point out how absurd NOT owning that book is, for the price Amazon is charging ($53 with free shipping). I actually have your older version. It'll be on eBay when my Ed.3 arrives, complete with coffee and beer stains! :beer:

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.