Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by hooovahh

  1. I didn't plan on git or Tools Network.  The Tools Network has a larger barrier to entry than I want to mess with for something like this.  And I've been lazy and just never done anything with Git.  The source is all there when you install it, the only thing missing is the VIPM config, and a Pre-Build VI.

    I use Remove Duplicates From Array probably the most, and also I think I use Foreign Key sort quite a bit.

  2. Your file doesn't exist, or you typed it wrong.  I just did a test where I made a batch file with ping localhost as the only thing in the file then did the same thing you did and it worked.  I'd suggest putting an output on your error, and Standard Error to see if it returns anything like file not found.  Also you may want to test small with a batch file like dir or ping.

  3. I had this discussion with a good friend of mine who is a senior developer in a texted based language.  He has 15 years of experience in real world development, has probably 10 developers under him, and he keeps up with all the latest in the tech and software development world.  He mentioned to me a few times that in his experience he sees the projects that have many many layers of abstraction, and code hiding behind code, only to find that debugging them is difficult.  And even searching for what a function is actually doing leads down many holes of things calling things.  Where the intermediate developers make a program that is straight forward, and does what it needs to. 

    His conclusion is that his years of experience of seeing when things work well and when they don't, help guide him how complex or how simple a set of code needs to be.  And when he talks about OO he very much is open to the idea that he just doesn't fully get it, but all of his experiences are summarized with "It looks great and it sounds like it solves my problems, but then in practice it falls apart" and I followed it up with a reply I've heard and that was "Well maybe you just don't fully grasp the right way to use it."  And his reply was "That's what OO experts tell me."

    When it comes to LabVIEW I feel like I have a good mix of OO and non-OO code.  Having no classes in a large project is probably a bad sign.  And having all clusters be a class, is also probably a bad sign.  Hardware abstraction, and plugin architectures is a couple places that OO just fits in really well in my mind.  Reuse code in general also works well.  Everywhere else I'm not apposed to it, but I can see some draw backs.

    • Like 2
  4. Oh for pete's sake!  I guess AppData is probably a more appropriate place to store this stuff.  The source is actually here on LAVA.  It is the full installer that I hosted somewhere else because I didn't want to store a large single EXE on LAVA, but the source seemed appropriate enough to host here.  Work hasn't pushed Windows 10 on me for my main development machine yet so I haven't tried this in that OS.

  5. No you can't do what you are asking.  There are a few things you might want to know, but none will totally fix your situation.

    Starting in LabVIEW 2017 there is a forward compatible runtime engine.  Meaning binaries build in LabVIEW 2017 can be ran in the 2018 or newer runtime engine.  When you build a EXE there is an option to force it to run in that one version of LabVIEW, or the newest one installed.  Then if you wanted to run a new version all you'd need to do is install the new RTE and it would run in that.  Obviously that is a relatively new feature and not going to be useful for you now.

    Also there is the fact that LabVIEW 2009 while not official supported in Windows 10 will most likely run just fine.  I've installed LabVIEW 7.1 in Windows 7 and had no issues, other than tracking down old drivers to support it.  So you might be able to convince your IT team that the 2009 RTE should be used.  Without the source that really is the only way to run that EXE.  The binary is compiled for that RTE and can't be recompiled for another target or platform unless you have the source.

    • Thanks 1
  6. 18 hours ago, desidude said:

    4) Recertification by points:  This is a no-brainer with a catch. I used to be involved in the community but I realized too late that for certify-by-points you also have to send emails to certification at ni dot com so that they record every event (quite ridiculous, because all events were at NI locations and sponsored by NI, including user-group meetings where they make you put your name and sign.) I had done LabVIEW presentations at local user-groups to advanced as well as new-to-labview groups,  NIweek, and local colleges/universities as a part of industry involvement in their curriculum. I realized too late that ALL of this was essentially wasted because even though I certainly had more participation points than needed, I just didn't keep a track of them and sent to NI to record!  *Poof* its all gone.

    So most of my interactions with NI in that capacity are documented somewhere.  If I presented at NI Week, it is available online.  If I attended NI Week then I have expense reports on it (and I know I attended), if I present at a user group I post my slides after the presentation, if I participate in a beta I'll remember, or even have the beta VM still on my computer.  So what I did was when my certification was about a year from expiring I just started adding up all the events and presentations I did.  Once I reached 50 points I sent an email to NI saying what I did and when and how I was up to 50.  They emailed back within a couple days saying I was then certified for another 4 years.  The one thing you might have a hard time with is remembering what user groups you attended if you aren't always a regular.

  7. 7 hours ago, Aristos Queue said:

    You people are so laid back and forgiving. I’m an editor on multiple wikis across cyberspace, and none of the others are anything less than draconian. Capitalization whatever?! 🙂

    Maybe it has something to do with the fact that we have a more graphical mindset and don't care as much as long as we can convey a thought.  Maybe because we are primarily engineers?  Or this is a wiki with a relatively small support base?  In any case thank you for your wiki contributions.

    • Like 1
  8. All very good points and good concerns.  Personally I would capitalize Boolean, but I may forget occasionally.  I would also prefer subVI as I've gotten used to the NI standard.  I can see the confusion with LabVIEW and G, and often I go back to what the community at large uses.  If I say "My programming language of choice is G" some may confuse this with GCode, or something else.  If I say LabVIEW I think that conveys what I mean to the general public more.  For this reason I default to "LabVIEW" but at times will say G.  Public opinion may change, and that may mean updating the wiki.  And if there are specifics I'd prefer separate pages for 20xx and NXG, but whatever.

    One thing you might not be aware of is that there is a place for page specific discussions on the Wiki Talk Page.  You could make an edit, but leave a comment asking for direction or leave it open to preference.

    That being said I think the opinion of most moderators on the Wiki is more that getting something which is non-perfect, is better than having nothing.  I'd encourage others to make pages and fill in what they can, even if they are unsure of how to handle some of these differences.  Things can always be cleaned up and refined later.

    • Like 1
  9. Not really.  I mean it might be possible but an easier way to handle this would be to setup your VI to run on open, and then just ask your users to double click on the VI from a shortcut somewhere like the desktop.  Then it will open that VI in LabVIEW (because that's what happens when you double click a VI file) and on open it will start running it.  You can even configure the VI to quit LabVIEW when the VI stops running or the user closes the window.  Then they wouldn't even know it is running in the IDE.

    This does however go against some standard programming practices and the better answer would involve still turning the code into an application, and figuring out what features you are trying to use that isn't available in the run-time engine.  And try to code around them.

  10. The linked article specifically states that it is for Windows and has you go through the process of creating drivers and installing them in Windows so that process isn't possible on RT.  Also NI sells PCI and USB based FPGA's that can be programmed with LabVIEW, but I assume you went with a custom chip for a reason.

  • Create New...

Important Information

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