LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Don't use the "in place element" structure?


@Maddy07 wrote:

Does anyone has tested using subVsI in IPE? NI needs to give some recommendations on that.  I know using subVIs in IPE voids the idea of IPE as subVI's will create copies of data - still I am curious because it gave me a lot of trouble.


I can recommend you to not use IPE within IPE on the same data, as that will cause a deadlock. 🙂

Sub VIs work well, but if they're time consuming it can cause problems if you want to access the data from other parts of the program at the same time.

Sub VI's don't copy data, unless you write them poorly. 🙂

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 11 of 13
(829 Views)

Actually the problem was related to use of the special character 'µ' at the sub VI's file name. The complete code runs well in run time, but the moment it is deployed in cRIO (of course Linux),the deployment couldn't run, broke and no error information shows up- though log error has some details (but nothing related to actual issue). Hence, actually it is not related to IPE at all, it's just that sub VI was a part of IPE. 

Apologies for late response, thanks for your feedback. 

0 Kudos
Message 12 of 13
(782 Views)

Actually the problem was related to the use of special character 'µ' at the sub VI's file name. The complete code runs well in run time, but the moment it is deployed in cRIO (of course Linux),the deployment couldn't run, broke and no error information shows up- though log error has some details (but nothing related to actual issue). Hence, actually it is not related to IPE at all, it's just that sub VI was a part of IPE. 

Apologies for late response, thanks for your feedback. 

0 Kudos
Message 13 of 13
(781 Views)