Concept to be verified for Main VI and Sub VI

[TanTan]

Hi,

I am designing a testing software sequencer currently. Due to some constraints, I am not able to mix the sequencer software (Main VI) and my test code (Sub VI) together in a executive file. I have to seperate them out. 

Main VI >> (.exe) file

Sub VI >> (.vi) file

Here is my concept, hope some one can point me out if there is any mistake:

1. Build the Main VI into an executive file (exe).

2. Above executive file will call the sub VI in local disk drive in PC through the function of "call vi referece"

3. Repeat the step 2 for rest of sub VI.

My question here, if above software flow is deployed in a new setup PC. What kind of installation package is needed there? I know item No.1 above able to be resolved by the labview runtime engine. How about the item No.2? Does labview runtime engine able to support? Or I have to install the labview development system? In that case I will be in trouble for the licensing situation.

Thanks.

[Ranjeet_Singh]

Hi friend,

                              1. Call the subVI dynamically.

                              2. When you build the package including your main VI and include your subVI dynamically than labview will    

                                  generate some additional file to call and support these files.

                              3. So i suggess you to create one folder for subVI then only create the package.

                              4. You dont need labview on other PC for this. Dont worry.

In my case when i was calling 3 files dynamically then total 92 files were created by labview after building packager & this works fine.

Let me know if any problem.

[TanTan]

Hi Ranjeet,

Thanks for your reply. May I know what is the file format for your 3 & 92 files? (.exe) / (.vi)?

[Ranjeet_Singh]

My 3 dynamically file was  .vi extension obviously

And other files are in .vi & .ctl files 

[Yamaeda]

---

@TanTan wrote:

My question here, if above software flow is deployed in a new setup PC. What kind of installation package is needed there? I know item No.1 above able to be resolved by the labview runtime engine. How about the item No.2? Does labview runtime engine able to support? Or I have to install the labview development system? In that case I will be in trouble for the licensing situation.

Thanks.

---

Ordinary LV runtime supports this, but if you want to make an installation of it all you'll need to make sure to add the vi's to the project as it wont be automatically linked.

/Y

[Norbert_B]

I am surprised how often people try to re-write NI TestStand on their own....

Norbert