call by reference and VBAI user interface

[gsajja]

hello,

         I'm trying to build a table ( recipe_array_mod.vi), in which using the up and down key will enable the cursor to navigate through the table and load the corresponding data into indicators and I also got add a new recipe information along with load data button. I got to the point where my VI for recipe_array_mod.vi is working fine, however in order for this code to work on the VBAI custom user interface withour throwing exceptions for any dependencies, I started to look into call by reference method using VI server. I'm new to labview environment and  reading about calling VI by reference , type specifier VI refnum shows connector type information. But I dont see any connector information when I use this method. Do I need to have a full development version of labview to exploit this method?

Please look into this issue and provide me some feedbacks and code corrections to be able to use with VBAI custom UI.

thanks,

[Brad]

Hello,

Using these VIs with the Custom UI in VBAI will hang VBAI because they use loops that don't ever end. You're close, but you should make sure the loops only execute once and use the value of the shift register to keep track of previous values. Why don't you email your contact information to vbai.support@gmail.com and we can discuss this over the phone because I think that would be more efficient. Reply to this thread after sending your contact info so I will get a notification and can check the email box.  I'll post the solution we use on this thread, but I wanted to get more info first since there are several ways you could address this.

Thanks,

Brad

[gsajja]

Brad-

       I emailed my contact information.

thanks,

[Brad · Accepted solution]

Here's an updated example. It makes the nice UI that you want the main VI and it dynamically calls the subVIs that do the work with File IO and have dependencies using VI server (which are primitive VIs so they aren't counted as dependencies). You need to update the path to your sub VI in the main VI and you need to make sure to close the VI Ref in the Cleanup state of your inspection (comments in the code of the main VI explain this).

Hope this helps,

Brad

[gsajja]

Brad-

            It looks good, could you please forward me your contact info to my email address. If in case i have question I can contact you?

thanks.

[Brad]

I thought of something that might work better for you. I noticed it takes awhile to load the subVI when you press the button the first time. You could load the subVI into memory using a Run LabVIEW step in the Setup state of the inspection and pass False to the VI so it doesn't actually do the File IO. Then in the Custom UI open the VI ref by name (i.e. use a string with just the name of the VI instead of a path to the VI). This will use the VI that's already in memory so it won't take so long to load the first time.

You will still need to clean up the ref in the cleanup state using a Custom UI step and setting the close to True.

Hope that helps,

Brad