LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Missing A Sub VI

I see I have 19.0.0.49152-0+f0 installed here. I'll try adding the patch to confirm that it fixes/d the issue, but I confess to not being too worried either way for my Express Node Build XY Array 😉

 


GCentral
0 Kudos
Message 21 of 29
(2,088 Views)

My LV 2019 has the f2 patch.  Both done through NIPM.   (mine gives the broken subVI)  I had not tried to use this express VI before I started trying to help in this thread.

0 Kudos
Message 22 of 29
(2,086 Views)

My f2 update didn't fix this for me. Oh well.


GCentral
0 Kudos
Message 23 of 29
(2,070 Views)

@cbutcher wrote:

I guess the question becomes... Hey Bob, how did you install LabVIEW? We all did it wrong 😞 😉


Well, yes and no.  Probably all experienced LabVIEW Users (including myself) "did it wrong", and the only people who did it right are newbies who've never before used LabVIEW.

 

It's a very sad story.  Until about a month ago, I had not been able to install LabVIEW 2019 "on top of" my previous LabVIEW installations (LabVIEW 2016, 2017, and 2018, all peacefully co-existing).  I tried multiple times (>5), starting from a complete NI Software "uninstall", then installation of LabVIEW 2016, 2017, 2018, and 2019.  Just couldn't get 2019 to install properly.  At one point, I started looking at NI Services at each step (documenting everything -- NI got several 8-12 page reports from me), and found that at some point, the NI Service Locator Service (does anyone remember William Safire's "Squad Squad"?) disappeared.  This means "No LabVIEW Examples", as the Example Finder depends on this Service.

 

A very helpful and friendly NI Applications Engineer handling my Service Request took this problem (and my documents) to R&D, who came up with a ridiculous suggestion:  instead of doing what we "Old Hands" knew was the proper way to install multiple versions, starting with the oldest and doing successively newer ones, they said "First install LabVIEW 2019, no Toolkits or Modules, no Drivers.  Repeat with LabVIEW 2018 (only), then LabVIEW 2017, then LabVIEW 2016, rebooting after every step.  Step 2 is to install the Toolkits and Modules, again in reverse chronological order.  Finally, install the 2019 Drivers."

 

Well, this worked.  Of course, I didn't believe it, so I did it again, very carefully, in the "correct" (chronological) order, and it blew up in my face.

 

As it happens, today I did (part of) another installation (so far I've just done the LabVIEW steps, and just did 2019, 2018, and 2016), and verified that the Ex XY Graph works just fine.  I even made a little For loop with two random number generators in it, ran it with N = 1000, and got Modern Art!

 

Modern Art 2019 (BS)Modern Art 2019 (BS)

Some observations and suspicions:

  • This is the third version of NIPM that I've obtained from the NIPM Download site.  The original one was NIPM 19.0.  About a month ago, when I finally "saw the light" and was able to build a multi-version LabVIEW installation that included LabVIEW 2019, it was NIPM 19.5.  This was still buggy, especially when it came to Activation (seems that it didn't "see" earlier activations, and didn't know that if you install Full or Professional, you should not have Base or Student automatically selected).  Today, the download gave me NIPM 19.5.1, and Activation was just what you'd expect (it even remembered the License number that it requires in the initial steps, and "fills it in" during the final Activation step).  This is real progress, as I found NIPM to be something of a mess previously.
  • It was explained to me that the "reverse-chronological-order" works, in this case, because each version of LabVIEW now installs in a Version-specific folder, and the Toolkits and Modules either are "version-specific" or (now) "backwards-compatible".  Also, the Drivers are supposed to be good for a 4-5 year "backwards" span.
  • Of course, until they fix NIPM (which, perhaps, they've done -- it certainly seems better now), those of us who already have older versions of LabVIEW can't go "back to the Future" to install LabVIEW 2020 before we install LabVIEW 2019.  It used to be that the Royal Pain was installing older versions of LabVIEW -- now, it seems to be "installing the current/latest version", but only if you are an experienced user!
  • It would not surprise me if NI is working really hard to fix this (and, as I said, may have succeeded, but I don't really want to be a guinea pig again ...).

Bob Schor

Message 24 of 29
(2,047 Views)

@crossrulz wrote:

It works just fine for me.  I just did a normal install.  At least, I don't think I used any magic sauce.  Did you install the latest patch through NIPM?  I have the f2 patch installed.  It does not appear to be available through a simple download and install.

It works just fine for me too. I did a manual download and install of LabVIEW 2019 f2. It is available as an offline installer without drivers from the official LabVIEW download page.

OfflineInstallerLabVIEW

Message 25 of 29
(2,024 Views)

@Bob_Schor wrote:

A very helpful and friendly NI Applications Engineer handling my Service Request took this problem (and my documents) to R&D, who came up with a ridiculous suggestion:  instead of doing what we "Old Hands" knew was the proper way to install multiple versions, starting with the oldest and doing successively newer ones, they said "First install LabVIEW 2019, no Toolkits or Modules, no Drivers.  Repeat with LabVIEW 2018 (only), then LabVIEW 2017, then LabVIEW 2016, rebooting after every step.  Step 2 is to install the Toolkits and Modules, again in reverse chronological order.  Finally, install the 2019 Drivers."


When I recently did my formatting of my work computer and went through reinstalling everything, I installed LabVIEW 2016, 8.2.1, and 2019 in that order and with their respective toolkits.  I then installed the 2019 drivers.  I haven't had any problems yet.  My observation was that I would always get an installation error if I tried to install drivers at the same time I installed LabVIEW 2019 (the "LabVIEW 2019 with drivers" download).  But installing the drivers later worked perfectly.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
Message 26 of 29
(2,009 Views)

Bravo, Crossrulz!  Your method that involves "Reality", installing LabVIEW Versions in the order released, rather than "Most recent first", but fixes what is (probably) a bug in the Installation Process, should be something that NI can find and fix.

 

Bob Schor

0 Kudos
Message 27 of 29
(1,993 Views)

Just another data point: For me it was broken in 19.0, upgraded to f2 via NIPM, rebooted, still broken. Is there a BUG#?

(Never use that express vi myself).

0 Kudos
Message 28 of 29
(1,980 Views)

I believe there is an easy way to solve this problem.  Simply just open the xy graph example file: Lissajous with Express VIs.vi.  In the block diagram window, copy the Build XY graph icon and paste to your working window. Replace the icon with the new one. It works

0 Kudos
Message 29 of 29
(1,619 Views)