ni.com is currently undergoing scheduled maintenance.

Some services may be unavailable at this time. Please contact us for help or try again later.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Open VI Reference LabVIEW NXG

Solved!
Go to solution

Hello,

Can anybody help me?

 

I always get an error when I call a VI (*.gvi) via "open VI Reference".
Is that posible in LabVIEW NXG?

 

Anmerkung 2020-03-04 142817.jpg

 

Thanks,

0 Kudos
Message 1 of 9
(4,841 Views)

Hi Muaadh7

 

Could you post your project? Is the referenced VI in the same Component as this VI?

 

Thanks,
Frank

0 Kudos
Message 2 of 9
(4,775 Views)

Hello Frank,

 

Thank you for your Reply.

 

Yes, it is.

Sorry, I couldn't upload a code.
Look at the pictures, please.

 

Anmerkung 2020-03-06 081235.jpg

………………………..

 

Anmerkung 2020-03-06 081302.jpg

 

------------------------------------

Anmerkung 2020-03-06 081904.jpg

 

Thanks,

Muaadh

 

0 Kudos
Message 3 of 9
(4,756 Views)

Hi Muaadh7, VI name "Multiply.gvi" is not enough. You must add a library name.

In this case, try "TestLib::Multiply.gvi".

 

If the VI is in Sub namespace, you can access the VI by "TestLib::Sub::Multiply.gvi".

 

Best,

Certified LabVIEW Developer
There are only two ways to tell somebody thanks: Kudos and Marked Solutions

GCentral
Message 4 of 9
(4,749 Views)

I tryed all options butt it dose'nt work.

 

Anmerkung 2020-03-06 110943.jpg

0 Kudos
Message 5 of 9
(4,738 Views)
Solution
Accepted by Muaadh7

In ordinary LV you can place a VI reference constant and drag a VI into it, there's no similar possibility in NXG?

/Y

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
Message 6 of 9
(4,723 Views)
Solution
Accepted by Muaadh7
Thank you Yamaeda.
I dragged the VI in a constant reference.
And I realized. He has a different name than is displayed in the library (TestLib) ...(I have no idea why)..See picture.
 
It works now. 🙂
 
Anmerkung 2020-03-06 142631.jpg
 
Thanks,
Muaadh
0 Kudos
Message 7 of 9
(4,709 Views)

What is the exact use case of Component reference node when we have the option of hard-coding the vi name in the input of open VI reference node?

0 Kudos
Message 8 of 9
(4,243 Views)

Uh-oh, this sounds like a recurring theme in LV NXG.  Could it be related to this topic?  And make sure to browse the topic I refer to near the bottom, also.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 9 of 9
(4,228 Views)