LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Including Prototype Information in a LabView 7 created DLL

How do you create a DLL from a LabView 7 vi that has the function parameter prototype information included. I'm calling the DLL from TestStand and have written other DLL's using LabWindows/CVI that have this info along with linking in the help file.
0 Kudos
Message 1 of 4
(2,803 Views)
Hello ToodK,

Thank you for contacting National Instruments. Please take a look at the attached KnowledgeBase links:

http://digital.ni.com/public.nsf/websearch/99AC2473C836CF0686256A49004425B7?OpenDocument

http://digital.ni.com/public.nsf/websearch/DBCE27265FFB554986256C9400026FE8?OpenDocument

http://digital.ni.com/public.nsf/websearch/BCB57B5F7E0D292486256BFA005DAD92?OpenDocument

I hope this helps!

Liz Fausak
National Instruments
0 Kudos
Message 2 of 4
(2,800 Views)
Have there been any improvements to this since LabView 8.2 ?
 
It may not be a mainstraem practice, but I also want to avoid shipping labview code with my test systems.
I'd like to put LV tests into a DLL and have TestStand import the parameter types and list..
 
Will NI be making this a development task for future versions?
 
 
0 Kudos
Message 3 of 4
(2,644 Views)
I'm not sure what you mean. It's always been possible to deploy TestStand without having the LabVIEW development system installed. If you deploy VIs, you can specify the ActiveX server of the operator interface instead of LabVIEW. And if you want to create a LabVIEW DLL, then TestStand can call it. I don't know if later versions of LabVIEW (i'm only using 7.x) create a type library in all cases, but you can manually specify the parameters during the development of your TestStand sequence. I make it somewhat simple to call a LabVIEW DLL in my sequences. The only parameter my DLLs have is a TestStand sequence context. In the DLL, I use this to get references to local variables or step fields and read/write to those. It complicates the LabVIEW code a bit though, and you can't debug the VI outside of TestStand.
0 Kudos
Message 4 of 4
(2,637 Views)