Mystery ERROR 53

[CoastalMaineBird]

LV2018 SP1, LVRT 2018

Have a procedure which loads "addons" in LVRT.  

The "Addon" is a PPL, compiled for RT, and placed in a specific folder.

The main RT code can load it and execute it on demand.

The VI shown calls GET EXPORTED FILE PATH to obtain a legal path to a VI within the PPL.

This worked fine in LV2013.  But now on LV2018, I have this mystery error 53 which shows up:

Trying to explain the error, I get "Manager Call not supported" . WHAT manager? 

If NI is TRYING to be obscure and cryptic, they're doing a good job!

The error is on the OPEN VI REFERENCE, which is a legit RT operation (AFAIK).

If I remove the VI TYPE REF from the OPEN VI REF operation, the result is the same.

If I change the FLAGS to 000, 0040, 0100, or 0140, the result is the same.

The PPL Path is known valid - the LIST operation works to show the PPL contents.

The qualified name is known valid - the 2nd item in the list has been copied to the control before running.

Any ideas ?

[aptivo]

Are the PPL and the main RT saved and compiled with the same LabVIEW version?

[CoastalMaineBird]

---

@aptivo wrote:

Are the PPL and the main RT saved and compiled with the same LabVIEW version?

Yes.

[aptivo]

Can you include one ppl for testing inside your project and call the vi via a static vi reference function as shown in the image?

[CoastalMaineBird]

I can't actually RUN it like your diagram, as there is a ton of stuff to be set up.

But the OPEN REFERENCE works OK like that.

One difference is that the static REF I use is to the PPL on the HOST machine, whereas the real world wants to load the copy on the RT machine.

But that should cause a FILE NOT FOUND error if there's a problem.

I get FILE NOT FOUND if I fudge the path a little bit, just as I would expect.

Only if the path is 100% correct, do I get the error 53

[Ben]

I don't use PPLs

Spoiler

I have read too many posts of people having trouble with them and besides most of my projects require I start from scratch and do not re-use code

SO I can only ask;

There is an option "adapt to memory allocation changes" that may be useful since you are running in RT.

There is an option to use old file layouts in builds but not sure if it available in PPLs.

Ben

[aptivo]

Have you selected the "Callers adapt at run time to Exported VI connector pane" option for the ppl build?

[CoastalMaineBird]

Sorry, I missed this message until right now.

There is an option "adapt to memory allocation changes" that may be useful since you are running in RT.

The CONNECTOR PANE STATE property panel has such an option (it seems new to me) and it was OFF.

If I turn it ON and rebuild the PPL, nothing changes.

There is an option to use old file layouts in builds but not sure if it available in PPLs.

I can't see that making a difference - I am building all the software in LV2018SP1, there should be no compatibility issues along those lines.