LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW CLI - RunVI operation failed.

Solved!
Go to solution

Hi,

 

Can anybody please help with this error? I tried all the possible options but could not fix the issue.

 

HShetty_0-1591305159317.png

 

0 Kudos
Message 1 of 9
(2,660 Views)

Did the VI have the predefined connector pane interface as specified here?

 
0 Kudos
Message 2 of 9
(2,619 Views)

Yes. You can see in the vi connector  pane(in the attached screenshot). Followed the same format recommended by NI. 


thank you

 Adarsh

0 Kudos
Message 3 of 9
(2,612 Views)
Solution
Accepted by HShetty

I found this KB which seems support my suspicion of connpane pattern mismatch. The color icons on your connpane seem to be correct but did you check the exact data types? The input should be 1D array of string and the outputs are I32 and string.

Message 4 of 9
(2,603 Views)

My bad. I had referred the KB earlier but, I did not notice the 1D array of string, I overlooked it as string input. 

 

Thank you for pointing out the issue. It's really helpful, I appreciate it.

 

Thank you

0 Kudos
Message 5 of 9
(2,574 Views)

Hi, 

Did you fix this issue? I am running into the exact same problem but the solution posted here does nothing for me. 

My setup looks like this. The entire program is just a one bottom dialog that echos some messages. Does the RunVI interface have to be part of program flow or can we just setup the connector pane and forget about it? I'm new to LabVIEW. 

Thank you.

Screenshot 2025-07-04 165925.png

Screenshot 2025-07-04 165906.png

Screenshot 2025-07-04 165847.png

  

Screenshot 2025-07-04 142101.png

0 Kudos
Message 6 of 9
(64 Views)

Hi Jack,

 


@Jackdabot wrote:

My setup looks like this. The entire program is just a one bottom dialog that echos some messages. Does the RunVI interface have to be part of program flow or can we just setup the connector pane and forget about it?  


How do you call that subVI?

That would be the more interesting part of your code…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 7 of 9
(60 Views)

"output" is a control when it should be an indicator

 

0 Kudos
Message 8 of 9
(36 Views)

@Jackdabot wrote:

My setup looks like this. The entire program is just a one bottom dialog that echos some messages. Does the RunVI interface have to be part of program flow or can we just setup the connector pane and forget about it? I'm new to LabVIEW. 

Screenshot 2025-07-04 142101.png


 

If you are new to LabVIEW, you should start with some basic tutorials. You might also clarify some of your unusual terminologies ((What is a "Run VI interface"? What do you mean by "part of program flow"? "forget about what, exactly"?)

 

Since you have connectors assigned, this is designed to be used as a subVI, but you can also run it directly without using a caller. In that case, you should not call it "an entire program". if you are running this as toplevel, the connector pane assignment is irrelevant..

 

Controls are inputs to the subVI and indicators are outputs from the subVI (and as has been mentioned, your output is a control, not an indicator. You can easily change that by "right-clicking...change to indicator")

 

You have nothing wired up, thus your indicators will never output anything interesting based on input.

 

Typically you would be much more specific help if you would attach your subVI. Truncated pictures almost never tell the full story.

0 Kudos
Message 9 of 9
(14 Views)