Why is LV deploying multiple instances of my vi to the cRIO

[viScience]

Here is a snipit from the Deployment Progress window when I deploy my code to a cRIO target

the vi Sump Control is set to be non-reentrant and is only called from one place in the hierarchy.

So what's up with the multiple instances???

Deploying Sump Control.vi:Instance:0
Deploying Sump Control.vi:Instance:2
Deploying Sump Control.vi:Instance:4
Deploying Sump Control.vi:Instance:3
Deploying Sump Control.vi(already deployed)

[Robbob]

Interesting. Is it a polymorphic VI? Any way you can share it so I can take a look?

[viScience]

Hi Rob,

Thanks for taking a look at this problem...  The vi is called Sump Control

[Robbob]

Nothing in that VI points to deploying it multiple times, seems perfectly normal to me except for the 2 second wait in a 250ms timed loop

One thing we can check, if you make it into an executable and then download it to target, we can FTP into the controller and see if there are actual multiple instances of this VI in the dependencies folder.

Either way, it probably isn't a huge deal.  If multiple instances are being deployed it will use a small amount of memory(check the remaining memory as it downloads to see how much) but this will most likely not make a difference.