Interop.LabVIEW DLL

Where can I get a copy of the Interop.LabVIEW DLL for use with C#, or do I have to write my own?
Solved!
Go to Solution.

The project requires:
1. My vi recieving a digital input and then triggering my wpf to start a webcam running.
2. my vi then recieves a second digital input and that triggers my wpf to capture and save an image from the webcam to file or for that image to be sent directly to my vi.
3. the captured image will be compared to a reference image and if the illumination of the object is not the same as that of the reference image my vi will adjust the illumination level of the object (this process will cotinue until the illumination level of the object anf reference image are equal).
4. Once the captured image is equal to the reference image my vi will begin image processing to determine the orientation and feature recognition of the object by comparison to the reference image.
5. if the orientation and/or features of the object are incorrect my vi will send a digital signal to have the object rejected (my vi will also sound an alarm buzzer and start an LED flashing).
6. If the object passes inspection then the orientation and co ordinates of the specific features that need to be identified will be saved to file.
7. With 6 completed or the object rejected my vi will send a signal to my wpf to stop the webcam. and wait for the input signal to start
the whole process all over again.
So i will be using the DLLs that are available via the references window in visual studio 2010. but i dont know what namespaces, classes and methods are available in those DLLs so i bont know how to use them. but i looked on the internet and i think the DLLs that are available via vs2010 are to allow communication between both my wpf and vi via .net objects and/or active x objects.
Ive no idea how to use either and finding anything more than superficial documentation on using either of the above is proving difficult to find (could you point to anything useful on .net and/or active x).
I think ive covered all you wanted to know but if you require more info please let me know, and thank you for trying to help me.
Saving to file isnt a problem but the communication between my vi and c# based wpf is.

Similar Messages

How do I use "LabVIEW dll import wizard" to import NETAPI32.dll

I am trying to use the LabVIEW dll import wizard for the first time. I am not very familiar in C-coding so this might be a good help instead of configuring CallLibraryFunction nodes myself.
I want to import NETAPI.dll. I am interested in several functions in that dll, but my main priority is the funtion NetUserGetInfo(). On MSDN I have found that the header file for the mentioned function should be: lmaccess.h (include lm.h).
My problem is this:
The shared library contains 317 function(s). But no function is found and recognized in the header file. The following function(s) cannot be wrapped. If you want to import these functions, please review the warning messages next to the functions below. You will need to fix the problems before you can continue with the wizard.
The function cannot be imported into LabVIEW. This might be caused by one of the following problems:
The function is not declared in the header file but is exported in the library.
Check the header file to make sure it contains declarations of the function.
Undefined symbols can prevent the wizard from recognizing functions and parameters. To correct this problem, check the header file to determine if you must add predefined symbols. Click the Back button to return to the previous page of the wizard to add a predefined symbol (for example, "NIAPI_stdcall = __stdcall" or "NIAPIDefined = 1").
MIDL_PASS;_STDCALL_SUPPORTED;__cplusplus;
Any suggestions how I can solve my issue?

astrid wrote:
I am trying to use the LabVIEW dll import wizard for the first time. I am not very familiar in C-coding so this might be a good help instead of configuring CallLibraryFunction nodes myself.
I want to import NETAPI.dll. I am interested in several functions in that dll, but my main priority is the funtion NetUserGetInfo(). On MSDN I have found that the header file for the mentioned function should be: lmaccess.h (include lm.h).
My problem is this:
The shared library contains 317 function(s). But no function is found and recognized in the header file. The following function(s) cannot be wrapped. If you want to import these functions, please review the warning messages next to the functions below. You will need to fix the problems before you can continue with the wizard.
The function cannot be imported into LabVIEW. This might be caused by one of the following problems:
The function is not declared in the header file but is exported in the library.
Check the header file to make sure it contains declarations of the function.
Undefined symbols can prevent the wizard from recognizing functions and parameters. To correct this problem, check the header file to determine if you must add predefined symbols. Click the Back button to return to the previous page of the wizard to add a predefined symbol (for example, "NIAPI_stdcall = __stdcall" or "NIAPIDefined = 1").
MIDL_PASS;_STDCALL_SUPPORTED;__cplusplus;
Any suggestions how I can solve my issue?
Sorry I forgot the attachment, but here it is.
Attachments:
NETAPI32.doc ‏103 KB

How can I calling LabView DLL within LabView and pass similar Data Types?

I am trying to use an Instrument Driver, which is created in LabView6.1 as a DLL. At this point I have only LabView to test this DLL. I was wondering, is there easy way to find out what sort of Parameter or Data Type I should be using.
How can I pass the following data with in LabView:
LVRefnum as Type?
LVBoolean as Type?
TD1 (a structure) as Type?
It is funny to see that I am able to create a DLL in labview but having trouble calling it within LabView. I thought, it would be easier to test the DLL within the same environment.
Basically, I am more worried about the VISA calls that are used in the driver to communicate with instrument. Because, there is no link to �VISA32.dll� in
the header file, is that handled by the LV Run-time engine? I guess more details are needed on using the LabView DLL within LabView from National Instrument Technical Support.
Attachments:
RL5000.h ‏1 KB

A LVRefNum seems to be an unsigned long data type (32bit). You can cast it
in LV then use that as a parameter to call the DLL. (an Occurrence type
seems to be a Ulong32)
When you created the DLL what was the resulting type for the LVRefNum?
Happy Holidays
"Enrique" wrote in message
news:[email protected]..
> I see...
>
> After doing some research, it seems to me that there is no easy way to
> find out the type of data, other than looking at the header file and
> have documents like Using External Code in LabVIEW handy. The
> following information is from that document:
>
> LVBoolean is an 8-bit integer. 1 if TRUE, 0 if FALSE.
>
> LabVIEW specifies file refnums using t
he LVRefNum data type, the
> exact structure of which is private to the file manager. To pass
> references to open files into or out of a CIN, convert file refnums to
> file descriptors, and convert file descriptors to file refnums using
> the functions described in Chapter 6, Function Descriptions.
>
> I know you are creating a dll in LabVIEW, but I am pretty sure the
> information applies as well and is useful. For your dll this can be
> interpreted that, rather than passing a LVRefnum, try passing the file
> descriptor.
>
> From the header file, is can be deduced that TD1 is a cluster in
> LabVIEW.
>
> You are right in saying that "more details are needed on using the
> LabView DLL within LabView from National Instrument Technical
> Support.".
>
> Enrique

How to call a labview dll from excel-VBA?

How to call a simple Labview DLL from Excel VBA?
I have seen examples of DLL calls from VB but does it work the same way for VBA? I have 2000 excel and Labview 8.5. I created the DLL and tried to call it from VBA using the same type of code as in NI's website example(ofcourse its a bit diff with 8.5)
http://zone.ni.com/devzone/cda/tut/p/id/...
BUT it errors out when called from excel
ERROR: The object invoked has disconnected from its client

You would need to provide more details about the LabVIEW DLL, such as the prototypes of the functions (VIs) that you're trying to call, and your actual VBA code. Specifically, what object you're trying to create. You should also make sure the Run-Time Enginer is installed, as well as any required libraries such as the VISA Run-Time if you're using VISA. Have you made sure to enable the ActiveX server for the DLL?
A search yielded the following items that you may wish to peruse:
http://forums.ni.com/ni/board/message?board.id=170&message.id=261345&requireLogin=False
http://forums.ni.com/ni/board/message?board.id=170&message.id=45099&requireLogin=False
http://forums.ni.com/ni/board/message?board.id=170&message.id=299209&requireLogin=False
http://forums.ni.com/ni/board/message?board.id=170&message.id=195846&requireLogin=False

How to handle a problem of Interop.SAPbouiCOM.dll file in SAP b1 9.0 PL11

Hi all,
I have a problem in creating addon of SAP b1 9.0,
At start time when I build my project but it does not create a file of Interop.SAPbouiCOM.dll except that it creates the file of SAPbouiCOM.dll in Bin folder of project. And as I thing, that missing of Interop.SAPbouiCOM.dll file is causing my addon to be not registered in SAP b1 9.0 PL11.
How can I solve that problem? I edited system form (Employee master data in VS2010(VB.NET)) that form runs correctly in SAP b1 at run time, the problem is missing file of Interop.SAPbouiCOM.dll which will be associated with project1.exe in Bin folder. even if I create another new project, it can not create that file,
What is the problem?
please anyone can help me.

Hi Edy,
Thank you so much, so how can I add reference of SAPbouiCOM in my project? Because I have added those 2 references DI and UI API version 9.0 but they give errors in each line contains SAPbouiCOM..... in menu.vb.
if it's possible can you try to explain me step by step as you explained to this link http://scn.sap.com/thread/3440046
Your help is highly appreciated Edy.

How to pass Visa Resoure Name parameter to labview dll in labwindows/cvi

Hi, everyone
I build a dll from labview, the prototype is : double getchannelpower(double f, uintptr_t *VISAResourceName);
I don't know how to pass VISAResourceName to this function.How can I get the VISAResourceName of this type(uintptr_t *)?
Is it related to the paremeter ViPSession in function viOpen(ViSession sesn,ViRsrc rn,ViAccessMode am,ViUInt32 ti,ViPSession vi)?
BRs,
lotusky

1. uintptr_t *VISAResourceName in the labview dll is connected to viOpen function as input parameter internally.
2.I can call the labview dll in labview via CLF Node, when the VISAResourceName parameter is set to Numeric(32-bit int or 32-bit usigned int) OR Adapt to data(Handle by Value). And I got the value of the VISAResourceName parameter, which is 0; When I directly connect 0 to the dll, it still works. But in labwindows, when I pass 0 to the VISAResourceName parameter of the dll function, I got a FATAL RUN-TIME ERROR: The program has caused a 'General Protection' fault.
mkossmann 已写：
Could you check what exactly uintptr_t *VISAResourceName in your labview dll does.Might it be that it is connected to the labviews Dll internal ViOpen() ViSession output parameter ?. And the name VISAResourceName is misleading.
Another idea would be that Labview uses 32bit Unicode for the ResourceName. And you have to convert the C String to that Unicode first.

Why does LabView dll not work in C Thread?

Hello Everybody,
I want to use a LAbView Application as Dll in a Console Application.
There is an Example Available (DLL_Example.zip)in (Displaying the Front Panel of a LabVIEW-Built DLL Function)
When I use this Example in a Windows Console Application, it Works fine (It is important for me, to see the LV Window!)
Code example:
/* Example Start *******************************************/
int main(int argc, char* argv[])
double Y = 4;
double X = 5;
double Result = 0;
SimpleCalculator(1, Y, X, &Result);
printf("Result = %f", Result);
return 0;
/* Example Stop *******************************************/
When I use the function "SimpleCalculator" in a Thread, the LabView Window never appear, what's wrong?
Code example:
/* Example Start *******************************************/
DWORD WINAPI LVThread(LPVOID lpParameter)
double Y = 4;
double X = 5;
double Result = 0;
SimpleCalculator(1, Y, X, &Result);
printf("Result = %f", Result);
return 0;
int main(int argc, char* argv[])
DWORD ThreadID;
CreateThread(NULL,0,LVThread, NULL, 0, &ThreadID);
getchar();
return 0;
/* Example Stop *******************************************/
I'm using Microsoft Visual Studio 6.0. and LabView 7.0
Thanks for every help.

bobby wrote:
Hello Everybody,
I want to use a LAbView Application as Dll in a Console Application.
There is an Example Available (DLL_Example.zip)in (Displaying the Front Panel of a LabVIEW-Built DLL Function)
When I use this Example in a Windows Console Application, it Works fine (It is important for me, to see the LV Window!)
Code example:
/* Example Start *******************************************/
int main(int argc, char* argv[])
double Y = 4;
double X = 5;
double Result = 0;
SimpleCalculator(1, Y, X, &Result);
printf("Result = %f", Result);
return 0;
/* Example Stop *******************************************/
When I use the function "SimpleCalculator" in a Thread, the LabView Window never appear, what's wrong?
Code example:
/* Example Start *******************************************/
DWORD WINAPI LVThread(LPVOID lpParameter)
double Y = 4;
double X = 5;
double Result = 0;
SimpleCalculator(1, Y, X, &Result);
printf("Result = %f", Result);
return 0;
int main(int argc, char* argv[])
DWORD ThreadID;
CreateThread(NULL,0,LVThread, NULL, 0, &ThreadID);
getchar();
return 0;
/* Example Stop *******************************************/
I'm using Microsoft Visual Studio 6.0. and LabView 7.0
Thanks for every help.
Check out luciangeeks's explanation elsewhere on this forum in several threads about the message loop needing to be pumped by the intial thread starting up the LabVIEW runtime system. In Windows console applications the hidden startup code linked in from the C runtime library to intialize the environment before passing control to the console applications main function also contains a message loop, polling the Windows message queue to among other things translate those messages into keychars so that the C runtime library function getchar() and friends can work as expected. It also makes the console application look responsive to the Windows system so that Windows doesn't think it would need to shutdown the application. LabVIEW DLLs really running as GUI components can't work without an active message loop making sure those system messages are retrieved and distributed to the according (usually hidden) VI windows. However the setup in Windows makes it such that a DLL sort of inherits the message loop of the thread which first entered that DLL. If that thread does not have a message loop, LabVIEW windows simply can't work properly and this means that the LabVIEW code is not managed properly and therefore won't run.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Interop.sapbobscom.dll compatibility

I'm having a compatibility issue, I think, with the patch-level of my interop.sapbobscom.dll that is installed with my addon compared to the patch level that is installed at my customer's location. I'm developing on SP00 PL49, but the customer is at 48. (They are getting a "server threw an exception" error at random places in the code that seem to be related to recordset.doquery.)
I want to create an installer for my addon that will contain the appropriate interop dlls but I want to make sure that I'm giving them the right ones. How do I tell what patch level the interops were created for? The SAPBOBSCOM.DLL object in C:\Program Files\SAP\SAP Business One\DI API\2007 has a special build description property in the version tab that lists the PL, but the interop file does not contain that property. I have different addons created for different customers all at different levels, so finding the right version of the interop files is quite challenging without any real identifying numbers.
Thanks!

Hello John
Basically the interop dlls are just containg the functions, as library but the business logic is coded in observer.dll which is downloaded to %TEMP%SM_OBS_DLL. By this logic the SAP B1 DI API can support the compatibilty between patch levels.
You cannot determine the interop versions, because only the major version number is stored there.
So in your case the Business Logic of PL 48 not knows the logic of PL49 if i understand you problem well.
When i had problems with recordset queries i was able to dicover 2 reasons
- cleaning up the %TEMP%SM_OBS_DLL was solving the problems
- on huge databases the transactions was generated this kind of errors.
I hope i has able to help you.
Regards
János

Problems in using Labview DLL with TestStand!

Hi,
I tried to put the VI's to create a TCP/IP Connection, read/write Data to it and close it inside a LabVIEW DLL and use these functions with TestStand.
The problem is to get access to the ConnectionID generated as TCP Network Refnum in LabVIEW.
I don't know how to specify the prototype entry for this Refnum in LabVIEW and how to read it with TestStand.
Another try to pass an ActiveXReference of SequenceContext and use the SetValIDispatch method to set a local variable (Type: ActiveXReference) to the returned ConnectionID of the TCPOpen.VI wasn't successful too.
It seems to me that the connectionID isn't a normal ActiveXReference.
Regards,
Sunny

Hi Sunny -
You should treat this parameter as a pointer to an int when calling the DLL from TestStand (or any language like C or C++). Note that you can't do anything with the value outside of LabVIEW since it only has meaning inside of LabVIEW. You can only pass it around for use in other VIs you call from TestStand.
Hope this helps....
Kyle G.
National Instruments
Kyle Gupton
LabVIEW R&D
National Instruments

Version incompatibility issue with Interop.SAPbobsCOM.dll in SBO 2004

Hi,
I have encountered an incompatibility issue in DI API 2004 across different patch level-versions. Originally, I developed an application in SBO 2004 pl4 environment. Now, some of the customers who were installing the application, notified me that the application has a login problem. It turned out that the CompanyClass.connect() method returns an error message "object reference not set to an instance of an object", when the DI API version installed in the production environment is higher (in this case, pl7) than the DI API version which was used in the development environment.
I figured out that the problem can be fixed by replacing the Interop.SAPbobsCOM.dll file in the application directory by a newer version that reflects the DI API that is installed in the system. However, it seems a rather lousy workaround, if the customer needs to manually replace the dll. Maybe the installer could be customized to "sniff" the correct DI API level, but this too would be a pretty kludgy solution.
Does anyone know a better solution to this problem ?
Regards,
Henry

normally this is not a problem as long as they don't change the signatures on the DI-API (which they said they wouldn't) but it appears in P5 they changed that signature... we noticed some enums that got added and a few minor changes.

(Un)Managed Wrapper calling LabView-Dll

Hello,
I am focused with a strange behaviour which i could not explain.
I had to extend the NI272x in my C++ unmanaged environment for a StepType http://sine.ni.com/cs/app/doc/p/id/cs-11443/lang/de/pdf/yes/pdf that descripes a functional testsystem.
Unfortuanately NI provieds no C Api for this devices. But LabView drivers were available. So i made LabView Wrapper
to consume it. This is worked fine.
A current extension development is done in C#. It loads the old unmanaged StepType-Dll during runtime. If the LabView Dll is
used. I am not able to load the DLL with C# via SDK LoadLibrary to memory.
To understand whats going on i have provied a small project that descripes the task.
Regards
Juergen
=s=i=g=n=a=t=u=r=e= Click on the Star and see what happens :-) =s=i=g=n=a=t=u=r=e=
Solved!
Go to Solution.
Attachments:
TestProject.zip ‏129 KB

I believe the problem is that the dll you are loading has dependent dlls. The normal behavior of LoadLibrary does NOT automatically look for dependent dlls in the same directory as the dll you are loading. You should use LoadLibraryEx with the LOAD_WITH_ALTERED_SEARCH_PATH option instead (This is what teststand uses when loading dlls with the c++ adapter). See Microsoft's help info on MSDN for more details about LoadLibraryEx and LOAD_WITH_ALTERED_SEARCH_PATH.
Hope this helps,
-Doug

Where do i find Interop.WMEncoderLib.dll in system?

RegSvr32
[Content]
The module "Interop.WMEncoderLib.dll" failed to load.
Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files.
The specified module could not be found.
above error is throw once i try to register dll as administrator

I am not sure where it would be located. You can do a system search for the dll file. I just wanted to make sure that you knew that Windows Media Encoder 9 is not supported anymore and was never really meant for OS`s past Win XP i believe. The
Microsoft Expression Encoder 4 has pretty much replaced it from what i have read.
I think i saw something about it having a 10 minute recording limit on one of the newer versions and i don`t know which it was but, you can download version 2 and 3 still too. Maybe they have the limit, maybe they don`t, i don`t know. Version 3 is
the last one supported on Win7 from the details in the download pages.
Microsoft Expression Encoder 3
Just thought i would mention it. 8)
If you say it can`t be done then i`ll try it

Using PostLVUserEvent function from Labview.dll

I am trying to use the PostLVuserEvent function from the labview.dll and corresponding extcode.h file. I have made my own dll using CVI that uses this function. I then use Labview to call my dll. My dll compiles fine. No issues, no errors. LabView can call my dll function containing the PostLVUserEvent function with no errors. However, the event number LabView passes my dll is not the same event number I receive so no LabView event is triggered.
Has anyone had this issue?
We are trying to solve it from the LabView side and the CVI side but cannot seem to get it to work. The examplesI have found here were compiled using C++ and those seem to work. I do not know why when I compile my program in C, it creates the dll but does not work. If I had to guess, i think it's an issue with pointers vs non-pointers. When the LAbview program selects my function from the dll, it shows the argument PostLVUserEvent as a pointer when in my dll, it is not a pointer PostLVUserEvent....
Any ideas?
Thanks in advance.

Hello Blue
Take a look to this one, it was created on C, I think the .c and the .h files will give a good idea, how the function should be implemented. It is important when calling the dll on LabVIEW, to use the std calling convention and run it on the UI thread.
Regards
Mart G
Attachments:
LabView EventTest.zip ‏1041 KB

Calling LabView DLLs from C/C++

Hi!
Is it possible to call functions in the LabView DLLs directly from
C/C++?
Functions like InvChiSquare in lvanlys.dll has "Adapt to Type" void *
parameters. How do I specify those parameters from C/C++?
I have tried to use the "Build Shared Library" function in LabView to
make a wrapper dll of the "Inv Chi Square Distrubution" vi, but when I
call this function in the dll from C/C++ the function never returns.
Other functions in the same dll that does not use functions in the
lvanalys.dll are working ok.
Regards
Hans Forssell

There are 2 great places to get infomraiton on passing data to dlls, and the data types used. First would be this manual. Using External Code in LabVIEW
The second is the dll examples that ship with LabVIEW 7.0. Go to LabVIEW 7.0\examples\dll\data passing\Call Native Code.vi

Can't step into CVI step that calls LabVIEW DLL?

Windows 2000 SP1
TestStand 2.01f
LabWindows CVI 6.0
LabVIEW 6.1 Runtime
We have a framework based on TestStand and CVI. A customer has supplied us
with a DLL written in LabVIEW 6.1 and packaged with the Application Builder
that we need to call from a CVI test library DLL. They say they can't
supply us with a non-LabVIEW implementation. We installed the LabVIEW 6.1
run-time. We added code to the CVI test library to dynamically load and
unload the LabVIEW DLL using LoadLibrary and FreeLibrary. LoadLibrary is
called in a function in the MainSequence Startup step group, FreeLibrary is
called in a function in the MainSequence Cleanup step group.
Things run as expected when the CVI DLL is built as Release or Debug and the
CVI
adapter is configured to run in-process.
However, if we try to debug CVI DLL by building it as Debug and configuring
the CVI adapter to run in an external instance of CVI, things hang the first
time we try to step into, or run, a CVI test library step that calls one of
the functions in the LabVIEW DLL. On the Applications tab in Task Manager,
the item named LabVIEW is marked as 'Not Responding'. The only way to
recover is to kill the LabVIEW process, which takes down CVI and TestStand
with it. If none of the LabVIEW DLL functions are called, no problems are
seen (no hang).
I assume the problem has something to do with the library getting mapped to
the wrong process space (TestStand v. the external CVI instance). Is there
any way to solve this problem? Any ideas or suggestions would be
appreciated.
Joe

> Out of curiousity, what happens if you attempt to debug your DLL from
> CVI? For example, configure TestStand to run its steps 'inProcess'...
> but then close the TestStand application and in CVI, configure it so
> that the Specified External Process dialog points to TestStand's
> SeqEdit.exe (CVI launches TestStand when debugging the project). Once
> TestStand is running, run your test and set your break points as
> usual, you should be able to step into the CVI code if nothing else.
> If not, I would be interested in hearing what problems you encounter.
When 'debugging' SeqEdit from CVI, we experienced no lock up.
Thanks for this suggestion. Debugging from CVI is a workaround for now,
though not highly desirable as it is reverse from normal debug proc
edure
(user can't step into CVI from TestStand). Still would like to know if
'normal' debugging of this problem is possible.
> The nice thing about debugging directly from Labwindows/CVI while
> TestStand runs 'inprocess' is that you can avoid some library linking
> errors, which may be the source of the troubles you are seeing.
The problem appears to be general to LabVIEW DLLs called from an external
instance of CVI under TestStand. We were able to reproduce the problem with
a simple LabVIEW VI compiled to a DLL, then called from a simple CVI DLL
under TestStand. We will package up some sample code and submit it to NI
tonight or tomorrow.
Thanks for you help.
Joe

Interop.LabVIEW DLL

Similar Messages

Maybe you are looking for