LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Missing A Sub VI


@altenbach wrote:

To wire two arrays (one for x, one for y) to an xy graph, all you need is wire the two arrays to "RE/IM to complex" (or similar) and wire the resulting complex array to the terminal of the xy graph and the rest will fall into place.


The easiest solution I found was to just use the bundle function. If someone else is having this issue create your x and y arrays in the front panel. Then create the xy graph from controls/modern/graph/XY graph then go into your block diagram and select "cluster class and variant"/bundle then on the left side connect your x array to the top of the bundle and your y away to the bottom. Then connect the right side of the bundle to your graph and you're done. Here's an example

 

xy graph.png

 

To put two lines on the same graph you can use the build array function which is located in Programming/Array/Build Array

Here's an example 

two lines.png

Message 11 of 29
(2,565 Views)

Hi ben,

 

as is explained in the context help of the XYGraph…

 

Even easier as suggested by Christian:

check.png

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 12 of 29
(2,559 Views)

@Bob_Schor wrote:

As a "Reality Check", I also tried dropping an Express Graph (ooh, I really dislike Express VIs) on my Windows 10 (x64)/LabVIEW 2019.0f2 (32-bit) system.  Block Diagram looks fine to me (see below for Snippet).Ex XY GraphEx XY Graph

Bob Schor


Just in case you are not familiar with LabVIEW snippets (the above, and its attached version, were clearly identified as such), this is a "feature" NI introduced 5-6 years ago in the Edit menu that allows you to save a VI as a PNG, and saves enough additional information that if you drag and drop this PNG onto a Block Diagram, it automagically becomes a VI.

 

I no longer have the original VI, but I dragged and dropped the attachment "2019 Express Graph.png" onto a blank LabVIEW 2019 Block Diagram and am attaching the saved VI.

 

Bob Schor

 

0 Kudos
Message 13 of 29
(2,545 Views)

Just to be clear, the "build xy graph" express VI is not recommended here, because you have two arrays, not two dynamic data sets. Converting arrays first to dynamic data, the piping them through a NOOP express VI makes me cringe. Most likely it was originally there because whoever wrote the program did not know what they were doing.

 

(This express VI has one optional feature to "retain data between calls" so it can act more like an xy chart if you set that option, but eventually you'll run out of memory if you use it incorrectly this way)

0 Kudos
Message 14 of 29
(2,540 Views)

I do believe there is something wrong with benm92's LV 2019 installation as well as mine.  Is that  EX XY Graph in the Graphs palette of the Front Panel a Merge VI?

 

When I open Bob's VI in 2019, it looks good.  When I go to the front panel, right click, Graphs, EX XY Graph and drop it on the front panel, the VI breaks and looks like this.

0 Kudos
Message 15 of 29
(2,532 Views)

@RavensFan wrote:

Is that  EX XY Graph in the Graphs palette of the Front Panel a Merge VI?


Essentially, yes.  You can put a VI on the controls palette and it will drop the contents (aka to the seasoned individuals as a Merge VI).


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
0 Kudos
Message 16 of 29
(2,538 Views)

Hi,

 

for me the same problem:

check.png

The error message is what I got for double-clicking the (missing) ExpressVI.

(But well, I noticed this problem only because of this thread…)

 

Addition: This is found in the vi.lib:

check.png

So apparently the ExpressVI functions are present…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 17 of 29
(2,522 Views)

Well, I have exactly the same symptoms and experience as GerdW with this - despite using LabVIEW 2019 nearly every day since NI Week, this is the first time I've seen this 🙂

 

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

 


GCentral
0 Kudos
Message 18 of 29
(2,515 Views)

Hi cbutcher,

 

maybe Bob did install LV2019 more often than we did?

(I needed 2 or 3 setup starts until it became usable, even though I used the installer from the USB media I ordered from NI 😞 )

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 19 of 29
(2,513 Views)

@cbutcher wrote:

Well, I have exactly the same symptoms and experience as GerdW with this - despite using LabVIEW 2019 nearly every day since NI Week, this is the first time I've seen this 🙂

 

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

 


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.


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
0 Kudos
Message 20 of 29
(2,502 Views)