Using ModelSupport2.dll in LabView without TestStand

I would like to use the ModelSupport2.dll purely in a LabVIEW environment as either by a "Call Library Function Node" or "Active X" or ".NET" without using TestStand.
In particular I would utilize the the "DisplayPassBanner" and "DisplayFailBanner" functions. I want the banner pop-up's so I can provide a consistency between applications that don't use TestStand and those that do.
The DLL call requires a numeric input "context" which I am not sure what it needs for a reference number.
In teststand it is passed an "Object", "CVI Active X Automation Handle", "By Value" from the "ThisContext"
How replicate this or create equivalent in LabVIEW
Any suggestions appreciated
A

A,
if you are looking into the sources of ModelSupport2.dll (the sources are included as LabWindows/CVI project and the needed C files), you will see that the display banner functions do access the object referenced by the parameter 'context'. The context is a reference to the dataset of a running TestStand execution when called from the TestStand process model.
So it will not be possible to use those functions if you are not going to use TestStand/running an actual sequence.
There are, however, two ways you can go for:
a) Design a LV VI dialog such way that it looks like one of the banner and call it as a subVI.
b) Use the LabWindows/CVI sources of ModelSupport2.dll to copy the banner dialogs into a new CVI project (from modelpanels.uir) and create similar functions into a custom written dll which do not require the ActiveX handle 'context' to be passed.....
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Similar Messages

Build a DLL in LabVIEW & Use the DLL in LabVIEW

I am trying to build a DLL for the simple vi with LabVIEW and want to use the DLL in LabVIEW. is it impossible?
I wrote a vi and it have 2 terminals. one is the input for numeric dbl data type and one another is the output for numeric dbl 1D array data type.
It was built with the Application builder for LabVIEW 8.0 and DLL was created successfully.
I want to use this DLL in new vi with LabVIEW.
Call library function used. I wrote a new vi to use that DLL.
In config dialog I config each parameter for dll and connected terminals. but it doesn't work
pleas refer to the attatched file and let me know what I missed.
Attachments:
Array1D.zip ‏60 KB

At first I kept scratching my head wondering why someone would want to do this. Create a DLL in LabVIEW to call it from LabVIEW. Seems redundant. But, perhaps it's an exercise or perhaps it's for testing the DLL...
In any event, calling the DLL worked for me in 8.2. How are you configuring your Call LIbrary Function node? I have it set up as follows:
return type: void
iteration: Numeric, Signed 32-bit Integer, pass by value
array1D2: array type, Signed 32-bit Integer, 1 dimension, "Array Data Pointer" format
len: Numeric, Signed 32-bit Integer, pass by value
Then I called the DLL like this:
Message Edited by smercurio_fc on 03-16-2007 12:57 PM
Attachments:
Example_BD.png ‏2 KB

How to use matlab code in Labview without having MATLAB software. I tried to convert .m files into .dll files. But i could not do. Please help me out..

Please help me out...
Solved!
Go to Solution.

bombay wrote:
Yes. It can be done. But Math script can not evaluate all functions in .m files (There are some exceptions).
And those can perhaps easily be ported to LabVIEW/MathScript?
It is not sufficient to disregard running your Matlab code in LabVIEW based on a few exceptions without first thoroughly evaluating the impact they have.
If you want to stick with Matlab in your implementation, then there are other avenues than hypotethizing about the limited portability issues of using MathScript in your project?
Br,
/Roger

Use a wrapper to build a C++ Dll that calls a C++ .lib and Use the Dll is LabView

Hi All,
I need to access some functions in a C++ .lib within LabView, but has no source code for the library. Can I build a Dll in Visual C++ that calls this library, then have LabView calls the Dll? If so, how different is building this Dll compared to building a Dll from a .cpp file? I am new to C++, could some one suggest how to use the .lib in Visual C++ 6.0 studio to build the Dll?
Thanks for your help.
Bryan

BryanL wrote:
Hi Rolf, thanks for the info. I will try to build a vi to call that function. For a more immediate need, I can use a downloaded vi that calls SetActiveWindow function, then use its output windowshandle to find the window name with a lvwuser32.dll function. The problem is this find window name function vi requires a windows reference input, which does not take the window handle output from the SetActiveWindow vi. How do i convert the window handle into a reference number? Thanks again.
Don't try to write a VI to call that function. That function requires a callback function pointer, something that is more or less impossible (well you can get it done but it is not worth the trouble) to create in LabVIEW. You will need an external DLL that does the enumeration and returns an array of strings to LabVIEW.
The lvwuser32.dll also just uses window handles. Look inside those VIs and you should see that those window references are typecasted into uint32 and then passed to the Call Library Node if I remember correctly. You definitely should be able to typecast the (probably uint32) you get from your other function into the window reference that that VI takes. The window reference of the lvutil library is just a nice trick to make it refnum like so that you can not inadvertly wire something else to it (and confuse/crash Windows).
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Communicate using libusb0.dll

Hello,
I have to develop an application in LabVIEW witch manage the MOWAY robot. I communicate with a RC USB Key so i have to handle with the libusb0.dll. My problem is the "usb_device *dev" used to open every function of the Dll and this type is define by :
struct usb_device
struct usb_device *next, *prev;
char filename[LIBUSB_PATH_MAX];
struct usb_bus *bus;
struct usb_device_descriptor descriptor;
struct usb_config_descriptor *config;
void *dev; /* Darwin support */
unsigned char devnum;
unsigned char num_children;
struct usb_device **children;
As you see this type is not retranscriptible in LabVIEW.
So i tried to wrap this Dll in C but it was not really a success.
If you have any idea, how to use this Dll in LabVIEW, i will be glad to hear it.
Thanks for your time.

Hello,
Thank you for yours answers.
I tried the link you send me JérémiC so i finally get that :
#include "stdafx.h"
#include "usb.h"
#include <windows.h>
#ifdef _MANAGED
#pragma managed(push, off)
#endif
#define LIBUSB_DLL_NAME "libusb0.dll"
typedef usb_dev_handle * (*usb_open_t)(struct usb_device *dev);
static usb_open_t _usb_open = NULL;
typedef struct usb_bus * (*usb_get_busses_t)(void);
static usb_get_busses_t _usb_get_busses = NULL;
#define MY_VID 0x04D8
#define MY_PID 0x0014
extern "C" __declspec(dllexport)usb_dev_handle *open_dev(void);
BOOL APIENTRY DllMain (HMODULE hModule,
DWORD ul_reason_for_call,
LPVOID lpReserved
HINSTANCE libusb_dll = LoadLibrary(LIBUSB_DLL_NAME);
if (!libusb_dll)
return FALSE;
_usb_open = (usb_open_t)
GetProcAddress(libusb_dll, "usb_open");
_usb_get_busses = (usb_get_busses_t)
GetProcAddress(libusb_dll, "usb_get_busses");
return TRUE;
usb_dev_handle *open_dev(void)
struct usb_bus *bus;
struct usb_device *dev;
for (bus = usb_get_busses(); bus; bus = bus->next)
for (dev = bus->devices; dev; dev = dev->next)
if (dev->descriptor.idVendor == MY_VID
&& dev->descriptor.idProduct == MY_PID)
return usb_open(dev);
return NULL;
#ifdef _MANAGED
#pragma managed(pop)
#endif
But i still have this error :"IntelliSense: argument of type "const char *" is incompatible with parameter of type "LPCWSTR""
I know that it's no longer a LabVIEW problem but i really need a solution to this program.
2 IntelliSense: argument of type "const char *" is incompatible with parameter of type "LPCWSTR"

TestStand LabVIEW OI and modelsupport2.dll

I'm trying to understand how to do some customization of the LabVIEW version of the TestStand (3.5) Operator Interface. I need the default OI to change in several areas. One in particular is that a teamate company (dictating the look and feel) wants us to have a Data Entry dialog. They say that it's part of the TestStand Sequential Process Model and it's contained in ModelSupport2.dll, and that it contains its own GUI that is used by the process models.
I hope to develop tests in LV8. As a first step, I'm trying to understand how (and when) to call the functions within the modelsupport2.dll. I there any documentation on the functions within (other than the .h)? Can someone walk me through an example where a sequence file (or is the call made from LabVIEW?) displays some dialog that is supposedly in modelsupport2.dll?

There's several dialogs in modelsupport2. There's the serial number dialogs for the sequential model, parallel model, and batch model. The only other dialogs are for the report file options and model options. The last two are what you get when select Configure>Report Options and Configure Model Options. The serial number dialogs are called in the process model like the other company said and I don't know of any test sequence or OI that would call them directly. If you want to override them and use your own serial number dialog, then you can put own callback in a sequence.

Get "Creation Script" of the existing table ( in SQL database) using C# and without using SMO dlls

Hi All,
I need to get the "Creation Script" of the existing table using c# and without using SMO dlls (is it possible? I don't know).
I.e. In SQL Management Studio -> right click on any table -> Script table as -> Create To - > open in the new query editor window. This will give you the schema of the table with the constraints of the table.
For E.g. In Northwind database, for the table "Categories", I would like to get it as show below
USE [Northwind]
GO
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE TABLE [dbo].[Categories](
   [CategoryID] [int] IDENTITY(1,1) NOT NULL,
   [CategoryName] [nvarchar](15) NOT NULL,
   [Description] [ntext] NULL,
   [Picture] [image] NULL,
CONSTRAINT [PK_Categories] PRIMARY KEY CLUSTERED
   [CategoryID] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]
GO
I would like to get the same schema using c#. Please help.
Thanks & Regards,
Kalai.

SMO is the easiest way to get this. This is what Management Studio uses. If you can't use SMO, get a Profiler trace of the queries that SMO executes when generating the script and execute the same using ADO.NET.
Regards,
Farooq Mahmud
Support Escalation Engineer
• Microsoft Health Solutions Group

How do I use the a command from a .dll with labview?

I want to use for example the M8784Open() command to control an M8784
photon counter. I know how to place a call library function node
but don't know where to go there. The user manual for the photon
counter has the following explanation of the M8784Open() command but I
don't know how to use their advice in labview!
7-3-1 M8784Open( )
Declaration HANDLE M8784Open( BYTE Board );
Parameter
BYTE Board
Specify the board to be used: M8784_MASTER or M8784_SLAVE. Specify both
when making 2-channel measurements simultaneously. It is not possible
to specify M8784_SLAVE only.
Return value A handle for the M8784 is returned when the function has succeeded..
INVALID_HANDLE_VALUE is returned if the function has failed..
Explanation Calls a handle to allow the M8784API.dll to use the M8784.sys driver.
Hereafter, specify this API’s return value (handle) when using other APIs.
When quitting M8784 operation, call up M8784Close( ) to cancel the driver.

You need to find out the equivalent number of the parameter. Somewhere in your documentation, or inside a file (for example, a header .h file in C/C++) you will find the definitions of each parameter.
For example, M8784_MASTER may have the value 1 and M8784_SLAVE the value of 2. You already know that it is a BYTE, so it will be a number of type U8 in LabVIEW. You need to find the exact values.
Probably, by value "A" it means the hex number "A", which is 10 in decimal. You need to find that in your documentation.
You also need to find the type HANDLE. It can be a BYTE, etc. Once you know that, find the value of INVALID_HANDLE_VALUE, so you can test for the error.
Most of this information can be found in the document Using External Code in LabVIEW. Check your help file, or check this link.
Regards;
Enrique
Message Edited by Enrique on 09-29-2005 10:36 AM
www.vartortech.com

How do I use a dll and C++ code to create a labview driver

I have a dll and some .net code to read temperature from a USB HID device I purchased from the website below. In addition some other people have posted their methods/codes of reading the temperatures. I am trying to convert this into a Labview VI but I am very lost.
http://www.no-feature.com/2008/01/taking-advantage-of-your-temper-device.html
It seems I can use the call function to see the functions in the DLL but I cannot use them to actually do anything. I have used serial communcation in labview before but never USB so I feel like I am in a little over my head and would really appreaciate some guidance.

This is not quite easy But to find out how try to reverse engineer this code http://pc8-termo.fis.ucm.es/~josechu/mitemper.zip
Before starting on the job I would recommend doing some testing to see if the code work with your device. I can help if you promise to post the tested code here in this forum. It doable in Labview. It just requires some bit manipulation. Also the unit drive must be installed
To establish a communication link with the device, the settings can be extracted from function SetupCommPort in MITEMPer.c, which are:
9600bps, 8 bits, no parity bit and one stop bit with DTR and RTS enabled.
To initialize the device, the function is init in functions.c. The sequence is:
Calling the Start_IIC function, which in turn calls the SetDataLine and SetClockLine passing 1 as parameters for both, and then calling those two functions again with 0 as parameters.
SetDataLine function sets the RTS line if the passed parameter is 1 or clears the RTS if the passed parameter is 0.
Similarly, the SetClockLine function sets the DTR line if the passed parameter is 1 or clears the DTR line if the passed parameter is 0.
In other words to to initializes the device, we first have to set the RTS, set the DTR, then clear RTS and clear DTR.
So to some part that involves a technique that is often referred to as bit banging. There are 3 groups of 8 bits (one byte) that need to be transferred. Which are, first group 10011110, second group 00000001, third group 01100000.
Then stop the IIC (look in the respective function on what have to be done here).
Start the IIC again.
Transfer another 3 groups of 8 bits.
Stop the IIC.
The sequence of transferring the group can be obtained from the function Transmit in functions.c:
The transmission is done through the DTR and RTS line only. Not through the usual TX data line.
If the data is 1 set the RTS or if the data is 0 clear the RTS.
Then the tick (clock), set the DTR followed by clearing the DTR.
Loop to the next data bit for 8 times.
After 8 bits, set the RTS line and set the DTR line.
Then read the CTS line for acknowledgement (inverted).
Closed by clearing the DTR.
You can follow the C code and find the necessary sequences and data that you need to talk to the device and obtained a reading.
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

How to use a C# dll in Labview?

How can I use a C# dll in Labview 8.2? With the "Import Shared Library" Wizzard I need the header file which I don't have. Is there another way
to use such .dll to import the functions created in C#?
Thanks in advance
Norick

Norick,
afaik there is no tool which provides you the possibility to create something like an instrument driver for .NET assemblies.
Maybe we should take a look into terminology:
- Instrument driver: This is a set of functionality, which provides the user with an easy to use API for a special instrument. Very often, the driver itself is written in C/C++ and provided as a DLL.
- "Import Shared Library" Wizard: This wizard enables the user to create an own API for any C/C++ DLL (or compatible) for LabVIEW. This wizard requires the information on all exported functions; this info is contained in the header file. The result of the wizard is a set of VIs containing one Call Library Function Node each for each exported function.
- .NET assembly (extension .exe OR .dll): This can be compared to ActiveX. So the way to program with .NET is similar to ActiveX. Maybe you want to take a look into the examples of LabVIEW regarding .NET...
- Global Assembly Cache (GAC): All assemblies contained here are registered in the system. Every application can easily work with assemblies contained here.
- Private assemblies: This would be the way to work with .NET assemblies which are built on your own. You have to select the .DLL-file itself and make sure that the file can always be found in the same (relative)folder of your application.
hope this helps,
NorbertMessage Edited by Norbert B on 02-21-2007 02:16 AM
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

How to use dll in Labview ?

I compile this code to dll file with VC++2010 filename is test_dll.dll .
#include "stdafx.h"
#include <iostream>
#include <Windows.h>
using namespace std;
int main(int a){
cout << "Test dll...............\n";
return a;
After that, I put Call Library Function node in editor and double click Call Library Function node. I browse test_dll.dll into Library name or path and set function prototype to int32_t main(int32_t a); but it show error Call Library Function Node 'test_dll.dll:main':function not found in libraly. How to use dll in Labview ? And I have more question is what is differrent from Tools -> Import -> Shared Library(.dll) and use Call Library Function node.
Solved!
Go to Solution.

The issue you are having is that LabVIEW is not capable of using C++ DLLs directly. It only handles C DLLs. This does not mean that if you you cannot use the DLL if it's compiled with the C++ compiler as opposed to the C compiler. Rather, it means that you must take extra steps in order to use it from LabVIEW. The primary issue is that of name mangling or adornment. This is discussed here: http://zone.ni.com/devzone/cda/tut/p/id/4877. Basically you need to prepend extern "C" in front of your prototypes in your header files. I would also suggest reviewing this article: https://decibel.ni.com/content/docs/DOC-14564.

How to use matlab compiled DLL in Labview ?

I have LV 8.5, and am unable to use a matlab compiled DLL in my LV code. I have tried the 'import' command, but it does not list any functions. However, it does not show any errors during its execution. The existing solutions/responses to this question do not work either. I would also like to know of a way to deal with mxArray datatype. What is its equivalent in C (or any other high-level language) ? How do I retrieve an array that is returned from the matlab dll ?

I'm assuming you have either Matlab installed or at the very least the Matlab Runtime, otherwise the DLL won't work. The "import" command relies on having a header file. Do you have one? You also need to make sure the DLL has been compiled so that it's compatible with LabVIEW. The most likely problem is name mangling, which also occurs when you try to compile a DLL written in C++. See this post, which contains links to useful posts.
The mxArray datatype is a special datatype which is actually a structure. It's complicated. Your best bet is to create a C DLL that acts as an intermediary between the Matlab DLL and LabVIEW. If you are able to, you can, instead, simply call the Matlab code directly using the Matlab script node.

Creating a DLL in LabVIEW containing a function using pointer to pointer

Hi!
I´m facing the problem to create a DLL from LabVIEW containing the following C-function:
functionF(structS** arrayA) ,
where:
structS is a struct of various data-types (e.g. int)
arrayA is an C-array of structS
How can this be done? Any ideas?
Thank you in advance for your support

This cannot be done in LabVIEW. LV doesn't have the data type "Pointer" as C has.
The only workaround I can think of is to use an array of strings in LV and in the interface define the parameter as "by reference". In LV you have to typecast the wire with the string to a cluster withthe layout of structS.
As far as I know an array of strings is represented as an array of pointer to strings. This is because strings are variable in length and therefore LV uses this method storing the pointers to the strings in the array and not the elements as usual.
You have to read the document about memory and data types of LabVIEW. In elder versions this was in the LabVIEW Bookshelf but I haven't found it in short in the newer version.
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

Using a cygwin DLL in LabVIEW 7.0

Hallöchen!
I try to use a function from a cygwin DLL in a LabVIEW 7.0 VI. So
I wrote
void funcName(double values[], long number_values)
for (int i=0; i < number_values; i++) values[i] /= 2.0;
to the file test.cc and said (cygwin gcc 3.3.1)
gcc -c test.cc
gcc -shared -o hall.dll test.o
Then I included it as a shared DLL in LabVIEW, added the correct
parameter sequence and return value. The name of the function was
a little bit different (Z8funcNamePdl).
But: LabVIEW crashes every single time. Not matter what I say about
calling convention or reentrance. As soon as the "configure" window
is closed, *all* LabVIEW windows are closed.
What am I doing wrong?
Thank you!
Tschö,
Torsten.
Torsten Bronger, aquisgrana, europa
vetus

Hallöchen!
LarsRoe writes:
> [...] LabVIEW arrays have a different structure than the
> traditional C arrays. As a quick test, try passing in a single
> DBL value by pointer for the first argument, and 1 for the second
> argument.
Even a "void Test()" lets LabVIEW crash. I now say
extern "C" {
void Test();
void Test() {
return;
> The prototype in your C function needs to match the prototype you
> get from the "Create C File..." Dialog.
Granted, but quoting the gcc manual: "Good compilers never crash."
I didn't *start* the VI after all.
Tschö,
Torsten.
Torsten Bronger, aquisgrana, europa vetus

Using axbridge.dll without going through the JRE installation process

I've searched the web and this forum for this specific problem, and have found related items, but nothing that quite answers the question.
I have an application that uses the JRE's axbridge.dll to access a DLL created from a Java bean. I used the packager to create a DLL named MyBean.dll.
When I go through the full JRE install, everything works great. That is to say, when I execute Sun's JRE installation program and go through the normal install process, I can access the bean through MyBean.dll without any problems.
I am accessing MyBean.dll from a Visual Basic 6.0 application. Converting to VB .Net is NOT an option at this time. The VB app uses MyBean.dll for a critical part of the application.
It is my understanding that it is not strictly necessary to go through the full JRE installation process. Simply deploying the JRE by copying its directory (and all subdirectories) to your application's directory structure should be sufficient. This would be HIGHLY desirable for my application. In fact, if I can't do this, it may be a show-stopper.
When I install my application in this way (i.e, by simply copying the JRE instead of "installing" it) it doesn't work at all. I immediately get an error saying that the executable "has encountered a problem and needs to close. We are sorry for the inconvenience" and a dialog is displayed offering to send the problem information to Microsoft.
The details indicate clearly that the problem occurs in the axbridge.dll, version 1.4.2.60.
1. Any ideas on how to get the axbridge.dll to work without going through the full JRE install?
2. Are there any alternatives to using the axbridge.dll to get my VB app to be able to use the Java? Remember, it is VB that must call the Java, NOT the other way around.
3. Is JNI an alternative? If so, can I use JNI to get VB to use Java, or do I have to write the DLL's in C++?
Any help you can give would be VERY MUCH appreciated.

I'm also on a JRE installation problem with the bridge.
Here is a regmon extract on excel using a dll that uses a java-packaged dll from the bridge:
5229 5.69504923 EXCEL.EXE:2364 QueryValue HKCR\CLSID\{9DD49FCD-BB61-414E-88C8-E6F5B35AEDCB}\InprocServer32\(Default) SUCCESS "C:\win32app\Specific\jre1.5.0_05\bin\axbridge.dll" << The axbridge dll in a specific location
5271 5.70646800 EXCEL.EXE:2364 QueryValue HKLM\SOFTWARE\JavaSoft\Java Plug-in\1.5.0_05\JavaHome SUCCESS "C:\Program Files\Java\jre1.5.0_05" << an installed JRE 1.5.0
This is confirmed with process explorer : excel is using "C:\Program Files\Java\jre1.5.0_05\lib\rt.jar" and not "C:\win32app\Specific\jre1.5.0_05\lib\rt.jar"
In other word, the axbridge check for its installation location in the registry to know where to start.
Even if all your components have been updated in the registry as suggested here : http://forum.java.sun.com/thread.jspa?forumID=40&threadID=559704
JRE Bug or feature?
Anyway the registry is evil.

Using ModelSupport2.dll in LabView without TestStand

Similar Messages

Maybe you are looking for