LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

SubVI not registering inputs

Solved!
Go to solution

Just yesterday I experienced a new behavior, completely new to me. Certain subvis are not using the inputs provided to them. Specifically, I pass in a VISA COM address, a couple of booleans, and an error. The sub vi runs without those inputs. I can setup the subvi and run it on its own, but being called it exhibits that behavior. Does nyone have an idea of why this would happen? There's nothing fancy going on, just one vi calling another with locally provided inputs.

 

LabVIEW 2019 SP1

0 Kudos
Message 1 of 7
(1,201 Views)

Hi WHunter,

 


@WHunterLV wrote:

Certain subvis are not using the inputs provided to them.


Maybe the problem is with your "certain subVIs" and how you use them!?

As you forget to attach those "certain VIs" you need to check and debug them on your own!

Best regards,
GerdW


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

Wow, that's the least helpful reply I've ever seen. Thanks!

 

I will upload the vis when the pc is back up and running, I'm currently trying to repair drivers. I've also done a fair bit of troubleshooting, but again, this is a completely new one for me....after 20 years of LabVIEW. Was hoping someone with a similar experience could quickly reply.

 

BTW, you're why a lot of people don't ask for help. 

0 Kudos
Message 3 of 7
(1,188 Views)

My best guess is that in the calling VI, you've got wires running under the called VI making it look like those wires are connected to the inputs when they're really not.

 

Such a circumstance could be readily found if you set the inputs to "Required".

0 Kudos
Message 4 of 7
(1,168 Views)

Is the subvi set to be reentrant with preallocated clones?  If you start by having such a subvi's front panel open in the dev environment, then run code that calls the subvi, the inputs won't show up in the edit-time front panel you're looking at.  You would need to use debug tools and *step into* the subvi in order to get to the front panel of the run-time instance that executes.

 

Offhand, that's the only guess I've got.

 

 

-Kevin P

ALERT! LabVIEW's subscription-only policy coming to an end (finally!). Permanent license pricing remains WIP. Tread carefully.
0 Kudos
Message 5 of 7
(1,164 Views)

Thanks, I wish that were the case. The inputs are set to required!I

0 Kudos
Message 6 of 7
(1,159 Views)
Solution
Accepted by topic author WHunterLV

Thanks for the suggestions, guys. I still have no idea what was going on, but it started working again after repairing VISA and clearing MAX's settings. I am going to put a mini fridge next to the test stand and stock with ice cold beer for days like this. Happy programming!

0 Kudos
Message 7 of 7
(1,106 Views)