Strange problem of calling library function node in labview 2010 and 2011
one year ago,I develop a program to usb device data and it works well,in labview 8.6 or 2009(win xp).Recently, When I test
the program in labview 2010 and labview 2011(win xp).,the program always crash immediately.I check the program and find main
problem is in call library function node. In my program,I use labview 2009 library for the USBExpress driver for
Silicon Labs USB MCU's from:https://decibel.ni.com/content/docs/DOC-9522,for example, 2 functions SI_OPEN and SI_READ
can not work well.
the header definition of SI_OPEN and SI_READ is:
SI_STATUS WINAPI SI_Open(
DWORD dwDevice,
HANDLE* cyHandle
SI_STATUS WINAPI SI_Read(
HANDLE cyHandle,
LPVOID lpBuffer,
DWORD dwBytesToRead,
LPDWORD lpdwBytesReturned,
OVERLAPPED* o = NULL
the SI_STATUS is equivalent to int type.
orignally, for HANDLE * in SI_Open, the parameter type in call library function node is numeric, data format is unsigned 32 bit integer ,and pass pointer to value.
for HANDLE in SI_Read, the parameter type in call library function node is numeric, data format is unsigned 32 bit integer ,and pass value.The program works well in labview 8.6&2009,however,crash in labview 2010 &2011.
later,I debug the program, for HANDLE *, I choose parameter type in call library function node as adapt to type, data format is point to Handles.for HANDLE, I choose parameter type in call library function node as adapt to type, data format is Handles by Value.Crash not happend in labview 2010&2011,however,it cannot read any data from from USB device correctly as before.I can not find the reason.
Dear friends,I need your help to answer the problem. Thank you.
Based on the help page it looks like it should execute asynchronously.
The thing in the description that leads me to believe they execute asynchronously is that you can configure the library to run as a multi-threaded operation.
Please take a look here to see the difference between synchronous and asynchronous execution.
Since the code even has the ability to be multi-threaded, you can consider it as running in parallel to your other code.
Any data returned is passed to the thread that called that function.
Cory K
Similar Messages
-
Is a call library function node in LabView 8.6 synchronous or asynchronous?
I tried setting a sub-VI with a call library function node in it to "subroutine" execution status. The error list indicated that the Call Library Function node in the block diagram was an asynchronous node. The LabView on-line help content indicates
"...CINs and shared libraries execute synchronously, so LabVIEW cannot use the execution thread used by these objects for any other tasks. "
Does anyone know for sure what the status of a Call Library Function is? Does it depend upon the specific code in the DLL being called?
Thanks,
Mike H.Based on the help page it looks like it should execute asynchronously.
The thing in the description that leads me to believe they execute asynchronously is that you can configure the library to run as a multi-threaded operation.
Please take a look here to see the difference between synchronous and asynchronous execution.
Since the code even has the ability to be multi-threaded, you can consider it as running in parallel to your other code.
Any data returned is passed to the thread that called that function.
Cory K -
How to use structure pointer with « Call Library Function node » in LabVIEW
I use GetTimeZoneInformation from kernel32.dll. It definition is :
DWORD GetTimeZoneInformation( LPTIME_ZONE_INFORMATION lpTimeZoneInformation );
Where
lpTimeZoneInformation
[out] Pointer to a TIME_ZONE_INFORMATION structure to receive the current time-zone parameters.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sysinfo/base/gettimezoneinformation...
I don't know how to set this parameter with my cluster based on the TIME_ZONE_INFORMATION structure.
Your help will be appreciate
Thanks
INKSPECINKSPEC wrote:
I use GetTimeZoneInformation from kernel32.dll. It definition is :
DWORD GetTimeZoneInformation( LPTIME_ZONE_INFORMATION lpTimeZoneInformation );
Where
lpTimeZoneInformation
[out] Pointer to a TIME_ZONE_INFORMATION structure to receive the current time-zone parameters.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sysinfo/base/gettimezoneinformation...
I don't know how to set this parameter with my cluster based on the TIME_ZONE_INFORMATION structure.
Your help will be appreciate
Thanks
INKSPEC
If creating a wrapper DLL which does the conversion for you is not an option (I think it won't since that would require C programming and if you knew C programming you wouldn't ask this here) then you will have to create a byte array of appropriate length and just configure the Call Library Node to pass this array as an Array of unsigned bytes and as C pointer.
On return you will have to copy out the interesting data at the right position.
First the length of this structure would be:
typedef struct _TIME_ZONE_INFORMATION {
LONG Bias; 4
WCHAR StandardName[32]; 32 * 2
SYSTEMTIME StandardDate; 8 * 2
LONG StandardBias; 4
WCHAR DaylightName[32]; 32 * 2
SYSTEMTIME DaylightDate; 8 * 2
LONG DaylightBias; 4
} TIME_ZONE_INFORMATION
Total 172 bytes
Now the fun part will be to actually get out the information. There are a number of difficulties.
First the strings are 16 bit Unicode so if you are interested in them you will have to call a different Windows API function WideCharToMultiByte function to convert the 16bit Unicode string into an ASCII string. For this part there has been a post here:
http://forums.ni.com/ni/board/message?board.id=170&message.id=123821&requireLogin=False
For the LONG values you would pick 4 bytes at the appropriate offset from the array through the Array Subset function and then typecast it into an int32 and pass that through the Swap Bytes and Swap Words functions to reverse the LabVIEW Big Endian byte swapping in the Typecast function.
The SYSTEMTIME is a structure with eight 2 byte integers so it would be best to use Array Subset again to extract 16 bytes at the correct offset, typecast this into a cluster with eight int16 numerics and pass it through Swap Bytes too.
You see accessing such API functions in LabVIEW directly can get easily quite a mess and that is the reason why creating a wrapper DLL to convert properly between LabVIEW datatypes and C datatypes gets soon the easier solution if you need to interface with more than one or two functions taking such complicated data structures.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions -
Window doesn't close wheh Call Library Function Node set to Run in Any Thread
This is a problem regarding Call Library Function Nodes running in the UI thread or any thread.
I have a camera which has its own API supplied as a dll. I have created a set of VI wrappers which each call a function in the dll through a Call Library Function Node.
Initially each CLFN was set to 'Run in the UI thread' (the default).
To start the camera streaming images I call (through a CLFN)
ICubeSDK_Start(int CamIndex, Hwnd, ImgHandle, bool Preview, bool callback);
If Preview = True then the image is displayed in a preview window.
If ImgHandle = NULL a default preview window
is used.
In the CLFN definition I define:
ImgHandle as a U32
Preview as a I32
To stop the camera streaming images I call
ICubeSDK_Stop(int CamIndex)
In the actual implementation I set ImgHandle = 0 (NULL) and Preview = 1 (true).
This all works fine, and a preview window is opened and images displayed. When I call ICubeSDK_Stop the preview window is closed.
However, I would prefer to set the CLFN to 'Run in any thread' because
a) when run in the UI thread the preview window randomly gets sent to the back when I switch focus between open VI windows (presumably because it is in the same thread as the VIs)
b) I don't want to put unnecessary stuff in the UI thread
c) my (naive?) understanding is that it is safer to run in any thread
So I have set all CLFNs to 'Run in any thread'
When I do this the preview window opens OK, and behaves like any other non LabVIEW controlled window in terms of focus. But when I call ICubeSDK_Stop() the preview window does not get closed properly, it just shows a blank image. I can't close it manually, there is no X in the corner and no option to close it from the taskbar. To get rid of it I have to close the LabVIEW project it is spawned from, which often results in a crash. It does appear as a separate item in task manager but if I 'end process' it, LabVIEW closes (and often crashes) as well.
If I change only the CLFNs that call the Start and Stop functions back to 'Run in the UI thread' then it all works fine again, except that the preview window gets sent to the back randomly as before.
So, what do I have to do to get the preview window to close properly if I set the CLFN to 'Run in any thread'.
Alternatively, is there a way to close the window programmatically (ie force it to close) after I have called ICube_Stop.
Thanks
DAveHi Dave,
The "Run In UI Thread" switches from the thread the VIs currently executing in to the user interface thread. If you select "Run in Any Thread", the Call Library Function Node continues in the currently executing thread. By default, all Call Library Function Nodes run in the User Interface thread.
Before you configure the Call Library Function Node to run in any thread, you have to make sure that the code is thread safe. Code is thread safe when it does not store any global data (e.g. global variables, files on disks, etc.), does not access any hardware, does not make calls to any functions, libraries or drivers that are not thread safe.
Unfortunately, since you said that your DLL accesses hardware, it is not recommended to use "Run in Any Thread." This is probably why you are seeing the crash.
If your preview window gets sent to the back you can programmatically bring it forward. Here is an example of how this can be done: http://decibel.ni.com/content/docs/DOC-4551
If you want to completely close the window down you can do so as described in this link: http://digital.ni.com/public.nsf/allkb/81E9C1441900FFCE8625748F0055DBB0?OpenDocument
I also thought you might find this useful: http://zone.ni.com/devzone/cda/tut/p/id/3009
I hope this helps.
Regards,
Mahdieh G
Applications Engineer
National Instruments UK&Ireland -
VI analyzer: Wire under object test fails with Call Library Function Nodes
Hi,
If I wire a Call Library Function Node with an ErrorIn and an ErrorOut, the VI Analyzer Test "Wire under Object" fails always with two occurrences per Call Library Function Node.
A double click to the occurrence highlights the error lines connected with the call... node.
The test does not fail, if the error lines are not connected.
Thanks!
H
Solved!
Go to Solution.This became a problem when Call Library Nodes got error terminals (and optional path terminals) in LabVIEW 8.20. I should be able to get a fix in to VI Analyzer Toolkit 2010.
Thanks for taking the time to report the bug.
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman -
Help to make opencv's dll and LabVIEW's Call Library function node understanding each others
Hi, i have a little problem trying to use a C++ opencv's dll in labview. I wrote a really simple and stupid dll just to try to understand how it works the call library function node. Here the header code:
#ifdef GENERICDLL_EXPORTS
#define GENERICDLL_API __declspec(dllexport)
#else
#define GENERICDLL_API __declspec(dllimport)
#endif
#include "stdafx.h"
#include <opencv2/core/core.hpp>
#include <opencv2/highgui/highgui.hpp>
#include <iostream>
#include <string.h>
#include <stdio.h>
#include <opencv/cv.h>
#include <opencv/highgui.h>
// Questa classe è esportata da Generic DLL.dll
class GENERICDLL_API CGenericDLL {
public:
int Summ(int a, int b);
int Sott(int a, int b);
int opencv(int a);
// TODO: aggiungere qui i metodi.
and here the .cpp:
// Generic DLL.cpp: definisce le funzioni esportate per l'applicazione DLL.
#include "stdafx.h"
#include "Generic DLL.h"
#include <opencv2/core/core.hpp>
#include <opencv2/highgui/highgui.hpp>
#include <iostream>
#include <string.h>
#include <stdio.h>
#include <opencv/cv.h>
#include <opencv/highgui.h>
using namespace cv;
using namespace std;
// Esempio di variabile esportata
GENERICDLL_API int nGenericDLL=0;
// Funzioni esportate.
GENERICDLL_API int Summ(int a, int b)
return a+b;
GENERICDLL_API int Sott(int a, int b)
return a - b;
GENERICDLL_API int opencv(int a)
const string ind = "C:\\Users\\sviluppo\\Desktop\\Tuli.bmp";
const string ind_2 = "C:\\Users\\sviluppo\\Desktop\\Tuli_Gray.bmp";
//Mat image;
return 5;
i can call all the three simple functions in labview with this easy code. No problem at all. If i uncomment the line "Mat image;" the call library function node doesn't work and i receive the error:
"The library specified for this node cannot be found or cannot be loaded. Right-click the Call Library Function node and select Configure, then choose the correct library name or path."
I think that is a problem of dependencies between opencv libraries but i dont know how to manage this. Any ideas?
Thank you for yours time,
Francesco.Hello Francesco,
I'm having exactly the same problem as you. I created a DLL that I can easily access from LabView. If I add one line and include "imgproc.hpp" (the only one I need), then LV gives me the same error you had. I read the thread Loura linked to, but I don't see how people actually take care of the dependecies (Klemen's examples did not work for me for the same reason, even though I recompiled the .cpp). Could you explain in detail what you did to make it work?
Thanks -
I have created a simplee application that controls a piece of equipment with all control via a supplied dll. Hence, there are a number of Call Library Function Nodes within the code and a modicum of other LabVIEW code. Everything works fine as a LabVIEW application, but when converted to an executable, although the application runs and functions, as soon as any Call Library Function Node is executed, calling from the dll, I get the C++ debug error in the attachment.
Is this something that I can solve from within LabVIEW, or is the problem likely buried in the dll?
Damian
Attachments:
CLFN error.JPG 22 KBHi Wise,
Try building an executable from a very simple VI that makes one call to the dll. Have you also try using the Call Library Function node on other simple dlls that you know will work?
Regards,
Stanley Hu
National Instruments
Applications Engineering
http://www.ni.com/support -
Call Library Function Node.vi using problem
Hi,
我用Labwindows 编了个读文件的程序然后生成动态库, 然后在LabVIEW里调用该动态库(Call Library Function Node), 即向该动态库传递文件名及路径和某一字符串,然后该动态库打开相应路径文件从中读出并返回三个参数值,可是每次的返回值总显示打开文件失败, 该函数在Labwindow里没有问题. 在LabVIEW里如何调试来确定传到动态库的参数格式是没有问题的呢?任何的指点迷津,不胜感激!
Frank,xiejiezhou wrote:
Thank Georges and Rolf Kalbermatter,
I changed the runtime support with " Full Runtime Engine" instead of " LabVIEW Real-Time Only" before, it's work now, but the output parameters returned are irregular incorrect characters. My funciton prototype is:
DLLEXPORT long CollectParameter(char *NomFile, char *szNomParagraph, char *Command[], char *Type[], char *Value[])
so how to configure the type in LabVIEW respectively? I tried every types, just "c String Pointer" is ok, but returned value irregular & incorrect.
As Geogre's suggestion, i should add my code as below function generated by LabVIEW, is it?
ong CollectLabel(char szNomFile[], char szNomParagraph[], char Command[], char Type[], char Value[])
/* Insert code here */
Frank
The char *Command[], char *Type[], char *Value[] parameters are parameters that you can not create with LabVIEW. This are arrays of strings and and LabVIEW has a completely different idea about how to place strings and arrays in memory than what is used in C.
And while LabVIEW supports translation of the top level type to C compatible pointers it does not have any option to let you configure it to translate embedded elements in parameters (the strings in the array) to be translated too.
But to be honest what you seem want to do is read in a file, do some parsing and then return parameters taken out of that file. Doing that all in LabVIEW would be SOOOOOOOOOOOO much easier.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions -
Problem in call library function
Hi,
I encountered some problems when using call library function node.
After i select the path in configuration of call library function node, an error message is shown as 1st attachment.
After i tick and the specified path on diagram, link the path name to the node, and run the program. Another error message is shown as 2nd attachment.
Is my dll file got problem? Or i have done a wrong setting?
Here i have attached my dll file.
The dll file is built by Microsoft Visual Studio 2008.
Please kindly advise.
Thank you.
Attachments:
picture1.JPG 14 KB
picture2.JPG 17 KB
CodeUtil.zip 152 KBTanTan wrote:
Hi,
Is my dll file got problem? Or i have done a wrong setting?
It seems to be compiled for WinCE. Assumed that you have Win2000/XP/Vista/7. Check your MSVC build settings.
Andrey. -
Call a special function in the dll using Call Library Function Node????
Dear all,
I am calling a special function in the dll using call library function node. There is a input parameter that it is a enum type in this function. I don't know how to deal this parameter for calling this function.Has anybody solved this problem?Please advise!
I am appreciated of you anytime.Most of the times an enum is just a U8/U16/U32, internally so probably you can call it with just a U8/U16/U32 or something. For the correct value you have to look at the definition.
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be! -
Dear all
I try to interface my spectrometer (NIRquest from ocean optics) using labview on my 64 bits cumputer using windows 7.
I have absolutely no problem to run the spectrometer with the program dedicated to the spectrometer (called Spetrasuite).
I've installed "OmniDriverSPAM-1.66-win64-development-installer.exe" and everything went right.
When I select a VI in LabView (e.g."wrapper_create.vi") from the wrapper.llb, LabView returns an error :
"Call Library Function Node 'Wrapper.Create': Library not found or failed to load."
I chek the call library function, but everyting seems to be right :
I use LabView 8.6.1 and my others *.vi are running perfectly...
Do you have any idea from where does the problem comes ?
Thank you very muchHello Flanguy,
In addition to smercurio_fc's feedback I can confirm that LabVIEW 8.6.1 doesn't exist in 64-bit version.
Officially, LabVIEW 8.6.1 doesn't support Windows 7 either.
The minimal version of LabVIEW you would need to both support Windows 7 and exist in 64-bit version is LabVIEW 2009 64-bit or any 64-bit versions which are more recent.
In the two links (1 & 2) you can find more background information.
Kind Regards,
Wouter
National Instruments Belgium -
Call Library Function Node: library not found or failed to load
Hello,
I had a VI that could not find some of the dll functions it needed. It works on one machine and not on another. So foolishly I copied the dll in question from the working machine and pasted it over the one on the non-working machine.
Now all my math functions are broken on the machine I copied the dll too. The error is "Call Library Function Node: library not found or failed to load"
And if I try to relink in the VI I get "Error loading C:\National Instruments\LabVIEW 8.2\resource\lvanlys.dll" A dynamic link library (DLL) initialization routine failed."
I tried a repair labview and that did not help.
I tried uninstall and reinstall labview and that did not help!
Please help me fix this!
Version 8.2
dll: C:\National Instruments\LabVIEW 8.2\resource\lvanlys.dll
JimWhat library did you first copy?
Also lvanlys.dll depends on the Intel Math Kernel Library that gets installed in a different location "C:\Program Files\National Instruments\Shared\MKL".
This Intel Math Kernel Library again depends on the Visual C runtime libraries. Most likely you replaced one of those runtime libraries somehow and now the Math Kernel Library (MKL) fails to initialize which causes thelvanlys.dll to fail its load.
Without a good view on your system and what other NI software you have installed it is very hard to recommend a good way of proceeding. There are various versions of the MKL used by various versions of NI products and just deleting the entire MKL folder might get you into trouble with other NI tools.
Deinstalling everything from NI, deleting the entire National Instruments folder and then reinstalling what you need would be the most safe proceeding.
And next time don't just copy some Visual C runtime libraries between machines. Their dependencies are complicated at the least and simply not graspable by us mere mortals. Use the according C runtime installer for the version you need as that installer will take care of installing the right versions of C runtime components and registering everything proberly so you do not usually run into problems with other applications using different versions of the C runtime.
Message Edited by rolfk on 03-01-2010 10:26 AM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions -
Call Library Function Node produces error in Windows 7
Hi,
I've created a simple program using LabVIEW 8.5 that uses calls in winscard.dll to read and write to a Smart Card. I use Call Library Function Node to call functions in C:\Windows\System32\winscard.dll. This program works without a problem in Windows XP both within LabVIEW 8.5 and once it is compiled. I am also able to get this program to run without a problem when I run it in LabVIEW 2011 on a Windows 7 machine. However, when I run the program compiled with LabVIEW 8.5 on Windows 7, the first call I make to a function in the DLL returns Windows System Error 2 (file not found). Subsequent calls to other DLL functions return errors about invalid handles, which makes sense.
Can I compile the project in LabVIEW 2011 and save it back to a LabVIEW 8.5 compatible project file?
Thanks,
Jason MazzottaBannu wrote:
Hi All,
I am also having the similar issue. I have a VI, developed in LV2010 on Windows XP machine with a dll call using "Call Library Function Node".
It is working fine in all WindowsXP machines but not in Window7 PCs.
Getting Error when i tried to open in Windows7 machine:
Error loading "DLL path....". Invalid access to memory location.
Please let me know how to make this working on both machines [XP and Win7].
Thanks,
Soumya
Way to little information to say anything useful about it. Attach your VI, explain what it should do, explain what the DLL is you try to call! You don't call your mechanicien saying your car doesn't start and expect him to diagnose the problem over the phone either with that much information.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions -
LabVIEW PDA reports COREDLL.DLL error when using Call Library Function Node
I'm trying to build a LV PDA app that calls an external DLL file built using embedded visual C. When configuring the Call Library Function node I select the stub DLL, configure the I/O parameters and select OK. When the configuration dialog closes I get the following error:
LabVIEW: LabVIEW.exe - Unable to Locate Component
This application has failed to start because COREDLL.DLL was not found. Re-installing the application may fix this problem.
I do not get this error when using the configuration dialog in the example VIs.
Any suggestions as to the cause and/or the solution?
Thanks,
RyanHello -
When you create a PDA VI that calls a DLL, you must include the .c or .lib file that corresponds to the DLL. Take a look at these documents:
LabVIEW PDA Module Build Errors with VIs that Call DLLs
Why Do I Receive Errors When Calling a C++ DLL from a Call Library Node Using the LabVIEW PDA Module...
How To Call External Code in LabVIEW PDA for Palm OS
H
ow To Call External Code in LabVIEW PDA for Pocket PC
Hope this helps!
S Vences
Applications Engineer
National Instruments -
When using a call library function node and program is exited, I get a "has encountered a problem and needs to close" error having to do with ntdll. It doesn't stop the program from running correctly, but it is annoying. Any ideas?
Solved!
Go to Solution.Sorry about the missing information. This is my first post. I am using Labview 2010 on Windows XP SP3. I am including a stripped down version of my application that will produce the same error along with the project file. This only happens when the application is built into an executable. It will also occur if the application is closed before FindWindowA is called. I'm also including a file containing the error that comes up. I appreciate all the help.
As to why I'm doing this myself? Ignorance would be the best explanation. A machine supplier gave me a VB program to communicate with his application. I used the same functions in Labview to do the communication and it worked great. I thought that was pretty cool.
Attachments:
FindWindowA Test.vi 25 KB
FindWindowA Test.lvproj 7 KB
FindWindowA Error.JPG 28 KB
Maybe you are looking for
-
When I try to set up my wife's Cloud account after upgrading to Mountain Lion, I click on the "send verification email" box, but the email never arrives. Her iPad and iPhone already seem to sync up in the Cloud, but no storage is being used. Any sugg
-
Recently something strange started happening ... When I select multiple images there used to be a white line around everyone selected and a bolder white line around what I call the primary ... Ok, so now, when I select multiple, eg 100, images and tr
-
sap guru's:- we have only copied g/l accounts from one company code to another company code for this situation what is useing the method, what is the t-code,plz,,, give the clarrification for this dount.
-
Where has the date gone from iMovie 11 events?
In iMovie 08 the date of the event is shown in the Event Library pane, in small text underneath the name of the event. But in iMovie 11 the date isn't shown. Is there a way to show it like in iMovie 08? This is a real pain. I've just imported a years
-
When i last worked at my project I accidentally quit the program (not a force quit). I think it happened during a background transcoding, but I'm not sure. All I know is that the shutdown of FCPX tok long time. Now when I try to open it, it stops at