Bryan

I'm not sure if I'm missing something, but I don't believe that the code is going to work reliably or as intended, unless I'm not understanding how this SubVI is to be used. Updating combo box items/values in a subVI doesn't really make sense (unless you're passing a reference to a front panel control into it). Even then, you'd have to update the combo box items/values before the they're selected by the user - then use the user's selection to search for and return the Density/Refractive index values. I have a lot going on right now, so I'm unable to provide an example at the moment.

There are many ways to "skin that cat", but these are the routes I would probably use myself: Using a Text Ring instead of a Combo Box (The RingText.Text property outputs the string of the selected item): If you're set on using a combo box method, here would be my approach (the Text.Text property outputs the string value of the selected item):

TestStand has its place. Yes, it can be a very powerful tool, but where I work, TestStand was someone's hammer and every test solution was a nail. We have several instances where TestStand was grossly overkill, where a more lightweight test executive would have been a better fit. I could write a short novel on all the hassle we've had with our TestStand based testers and the poor planning, development and implementation of it where I work, but I will refrain. (In fact, I did, but deleted it as it went on a long rant). I'll just simply say that I've inherited those @%$#@ machines and they've been nothing but a 4-year headache and I'm slowly replacing each one with a LabVIEW-Only solution. The ones I've done so far perform much better/faster/stronger, are more robust and the operators gripe much less about them if at all. In fact a "notoriously gripey" operator said that they "absolutely loved the new tester" after I had completely reworked it to eliminate TestStand.

Sie sollten ein LabVIEW 2009-VI in LabVIEW 2019 öffnen können. Einige Abhängigkeiten werden möglicherweise nicht richtig übersetzt. Wollen Sie damit sagen, dass Sie es überhaupt nicht öffnen können - was bedeutet, dass Sie beim Versuch, es zu öffnen, eine Fehlermeldung erhalten, oder dass Sie das VI einfach nicht ausführen können (gebrochener Ausführungspfeil)?

Not everything was "free", but I did get a good deal on some things. - Expensive set of industrial environment cooling fans used in destructive environmental testing of a DoD product that still worked perfectly fine after testing was completed. Was able to get permission to take them home. They ended up as attic fans in my old house. - Expensive soldering iron for $1 at a company auction. - May possibly be getting a high horsepower server that we built for our department that was in a recent flood that will be scrapped. Only the bottom of the server tower was in the water, so the power supply would be the only thing that needs replaced. Nothing else except one of the HDs was submerged. - $200 office chair from company auction for $10.

Thank you for posting this. It's very helpful and informative. I was noticing icon font issues in LabVIEW 2020 Community Edition for Linux, so it doesn't look like NI has fixed (or knew about) the issue in LV 2020 for Linux either.

This process worked for me (though not verbatim) in order to install LabVIEW 2020 Community Edition on Zorin 16 Linux. Thank you @Yaw Mensah. The .deb package names varied slightly for me and I had to install alien on zorin and dpkg manually before starting above: sudo apt-get install alien dpkg-dev As of writing this post, I haven't messed with LabVIEW enough on Zorin to say whether everything is working 100%, but I was able to at least launch LabVIEW. I did have to go into /usr/local/natinst/LabVIEW-2020-64 and create a symbolic link to the executable to launch with using the Zorin "start menu" entry: cd /usr/local/natinst/LabVIEW-2020-64/ sudo ln -s labviewprofull labview

That's a lot of participation awards... I'm surprised an Admin hasn't chimed in yet to let us in on the new hotness.

Would you be willing to post what the solution was?

Welcome @LVmigrant! If your company isn't willing to pay for LabVIEW training, but uses LabVIEW - it sounds like a great recipe for major headaches in the future. Speaking as someone who has inherited some really bad LV code over the years, a company's up front investment in training for their employees will save them a lot in the future as far as maintenance, refactoring, and many other things. The bad code I inherited was from programmers who didn't take any training nor took the time to learn from other more seasoned programmers. This is a great community with some of the most knowledgeable LabVIEW programmers I've ever met. Even though I've been using LabVIEW on and off since 1999 - I don't hold a candle to the knowledge contained within some of the the members of this forum. That being said - many of the users in here have contributed to the LabVIEW Wiki, which has a LOT of useful information.

I was never involved with it, where I used to work I supported a software group that wrote code for an automated military application. I can't speak for other DoD contracting companies, but I know that they went through iteration after iteration of software testing, regression testing and debugging over the course of several months to a couple of years with testing "events" that would go around the clock for a couple of days at a time. My role was not with programming for that application, but I was responsible for maintenance and troubleshooting of the simulation testbed that they used to develop their software. If they found undesirable behavior from their code, I worked with them to determine whether it was actually a bug or something wrong with the testbed.

Well - Finding a CLA may be more difficult than finding a CLD. Some people may (like myself) have gone the path up to feeling qualified to take the CLA Exam, but never pulled the trigger for one reason or another (mostly $$ reasons). I never did it because - working for a company - a CLx never benefited me in any way nor did it benefit my company. They were willing to foot the bill for the exams, some of the time, but I never went through the process and let my certification expire long ago after only one renewal. You could specify CLA-Level of experience without necessarily making them have an active or expired credential. However, you'd still have to determine somehow by evaluation or by faith that they have the level of experience they claim to have. Hey! I (likely) resemble that remark!

I would start with having a CLD (recent or in the past) as being helpful, but not necessarily a requirement. Ask them if they've taken any LabVIEW courses and what they were. This should give a baseline of their expected knowledge/experience. Quiz them on what they SHOULD know having taken them. Quiz them on the commonly used LabVIEW frameworks (or commonly used in YOUR job) to get a feel for their grasp on the concepts (e.g. QDMH, DVRs, OOP, etc. LIB MR DUCKS). A courses, a degree, or CLD doesn't necessarily equal competence (but I agree, it gives more of a 'warm-n-fuzzy' feeling) - I've seen it several times in my career. Some of the most competent people I've worked with have no official degree, but lots of experience. Some people can have loads of LabVIEW experience, but never went for a CLD/CLA because the certification wasn't required for their job or field. If they can (and it's not always able to be done because of intellectual property constraints), ask them to provide sample code for you to review. I'm sure others will have more (and much better) insights than I do, since I haven't taken part in many candidate interviews for LabVIEW positions. (Although I will be here in the near future).

Is the TVI - Tester Automation Framework an open source alternative? I see you also posted the exact same text here. Is it also a LabVIEW software validation tool?

What are the functions of pins 7, 8, and 9 on the DB-15 controller? Is it possible that you have RX connected to RX and TX connected to TX on both ends? If so, you'll likely need to wire it like a crossover: DB-9 Pin 2 (Rx) to DB-15 Pin ? (Tx) DB-9 Pin 3 (Tx) to DB-15 Pin ? (Rx) DB-9 Pin 5 (GND) to DB-15 Pin ? (GND)

I'm sure others have better suggestions (e.g. a LabVIEW Toolkit or other), but in the past I worked with a system that used PDF995 virtual printer and have LabVIEW set it as the default printer and then print to it. However, It will prompt you for a filename/save location every time you print to it and I wasn't able to figure out how to change the default filename at the time nor have it print without prompting.

I'm in the exact same boat. While I'm not on the cutting edge and doing much of the cool stuff many of you in this forum do, I do entertain the idea in the back of my mind that LabVIEW may one day go away while I'm still in the working world. I'd like to think (realistic or not) that if NI ever decided to completely get rid of LabVIEW, that they would show appreciation to all of we who have made it successful in the past by making it open source.

Thanks for the info! I don't currently work at that company or with iVVivi anymore, so my question was more of a "what became of it" post than anything. While I was there, we had selected it over TestStand because of the built in HAL and simplicity in test development.

At my previous employer, we had updated a couple of our test systems to Calbay Systems' "iVVivi" software. I had spent a lot of time with it and recently got to wondering whatever happened to it. When Calbay Systems was acquired by Averna, iVVivi seemed to disappear. It makes me feel bad for those at my previous employer who are now stuck with using a test executive software for which they may no longer have support. I know that we have some Averna employees in the forum, and I'm hoping someone may be able to shed some light on what became of it - including someone who helped us with our implementation of iVVivi (though I haven't seen him on the forums in many moons).

I'm very interested in the responses to this. We're currently looking into migration of existing TestStand systems either back to pure LabVIEW or to a home-grown or other architecture. TestStand has just become too much of a pain in the butt for us that we're planning on purging it from our test systems. I miss the days of Test Executive (TestStand's predecessor). It was simple and easily customizable for LabVIEW programmers. Even "iVVivi" (created by CalBay - Now Averna??) was better than TestStand for our needs (lacking in some areas), but iVVivi wasn't open source and it seems to have disappeared from existance. It would have been nice if NI would have made the old Test Executive code open source, but I'm sure it would have hurt the sales of TestStand, (although I'm sure TestStand is doing a pretty good job of that by itself). Sorry, I didn't mean to hijack - I'll stop right now as I could easily go on a tirade about my experiences with TestStand.

Did they give a reason? I'm betting has something to do with "Microsoft CE" being a thing, and they don't want to even remotely draw any negative attention from Microshaft.

I had heard that they were entertaining the idea of supporting Discover... but even fewer people use it.

AutoIT is the first tool that comes to mind. I'm not familiar with it personally, but know some people who have used it in the past. I don't know if there are any issues using it with LabVIEW, but I know it has been used to automate control of other types of Windows applications.