All LabVIEW retirees! Would you please post the most amazing LabVIEW code you've ever written ?

[crossrulz]

---

@BuddyHaun wrote:

If you ever have the pleasure of working a lot with serial instrumentation I found this vi that I wrote long ago to be indispensable. It closes all open com ports without getting out of LabVIEW.  Not that I am retired yet.

---

Interesting.  It looks like it will close all VISA sessions, not necessarily just the COM ports.  Nice hidden gem in there as well.  I might have to play with this in my next project.

[JÞB]

---

@crossrulz wrote:

---

@BuddyHaun wrote:

If you ever have the pleasure of working a lot with serial instrumentation I found this vi that I wrote long ago to be indispensable. It closes all open com ports without getting out of LabVIEW.  Not that I am retired yet.

---

Interesting.  It looks like it will close all VISA sessions, not necessarily just the COM ports.  Nice hidden gem in there as well.  I might have to play with this in my next project.

---

There is a LabVIEW.ini Key to do that!  So, a private method probably already exists.  Tim why don't you ask on another board?

[Kevin_Price]

As a public service FYI:

This will only identify VISA sessions that are part of the same execution context.  A colleague tried it out from the dev environment while an EXE was holding a particular COM port open and the EXE's session wasn't in the VISA array.  Which is how it *should* work -- there's a good reason for it *not* to be included.   So this isn't a complaint, just an FYI.

-Kevin P

[Hooovahh]

---

@GRCK5000 wrote:

Let's see your top notch LabVIEW code.

---

Listen if this is some kind of interview then I'm going to want to see the job offer first.

I do have a reuse library I organized and maintained pretty well at my previous job.  I've posted this on Linkedin and LAVA in the past.  I have since made some improvements in automating its generation.

I also have some more elaborate high level software documentation that I'm proud of, but I haven't got permission to post yet.  And the documentation for a cool software thing, isn't really all that impressive if you don't also have the cool software.  But it might look good on a Linkedin accomplishments page.

[GRCK5000]

@Hooovahh Haha... But I have used your library before. Great documentation, very easy to understand.  Man, you definitely deserve a huge trophy. lol

[Hooovahh]

Turns out I did post part of the documentation of this large project here.