LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Trouble using NI_MAPro.lvlib VIs inside a "Plug-in"

Hi,

      I'm trying to use NI_MAPro.lvlib."Trigger Detection for 1 Channel" inside a VI that's called by name (the "Plug-In"). If I run my application in the Development environment, it works, but as an EXE, the plug-in opens-broken. If I remove "Trigger Detection" (and all the other NA_MAPro VIs) from the plug-in, it "runs" unbroken. I've replaced the "Trigger Detection" SubVI with a CLF calling the same dll (lvanlys.dll) - and the "plug-in" runs - in other words, it doesn't seem to be a DLL problem. I've even configured "Trigger Detection" to open it's FP on load, and it opens UnBroken, though the caller (the plug-in) is broken.Smiley Mad

 

I suspect it's a lvlib issue, but am inexperienced with these things and out of ideas!

 

SINCE posting this to the worng forum, I saved Trigger Detection and two others as new-VIs, outside a lvlib, and the Plug-in is happy/working, though...

 

It would still be good to know how to solve this without having to re-create lvlib VIs,

 

Any help is appreciated.

 

Cheers!

"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
0 Kudos
Message 1 of 5
(3,804 Views)

Hi tbd,

 

Can you post a simple VI which shows this problem? And which version of LabVIEW do you use?

 

Thanks,

Michael

0 Kudos
Message 2 of 5
(3,782 Views)

Hi Michael,

      Thank you for the reply.  I'm using LV 8.5.1, but, at the moment, can't reproduce the problem when I develop a simple example project which builds an EXE that calls a plug-in.

 

So it seems to be a lvlib-related problem on my development station.  I'll recompile the example there (later) and post the project if the problem recurs.

 

Thanks/Cheers!

"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
0 Kudos
Message 3 of 5
(3,769 Views)

Hi Tbd,

I am facing similar problem. Did you find any solutin to it.

 

Regards,

Vikas

0 Kudos
Message 4 of 5
(3,408 Views)

Vikas,

 

Try going into your build spec and unchecking the "Remove unused members of project libraries" in the "Additional Exclusions" section.  If a library is used in multiple locations, this feature can sometimes create a situation where LV tries to load two libraries of the same name but with different contents.  This is generally the source of the error.

 

Hope it helps!

JasonP - CLD

0 Kudos
Message 5 of 5
(3,403 Views)