Can a call to a DLL be aborted?

Hi all,
I've got a rather huge project stat starts to cause bad problems now communicating with an USB device. There's a home-made DLL that calls some chip-specific DLL functions. From time to time a call that finally should simply close the handle to that device takes far too long, from seconds to hours. It will finally return and everything is done, but I cant affort to wait more than some few seconds.
Now my Q is, is there any way to abort a call to that DLL whenever it takes more than a specified period? I thought of dynamically call a VI that calls the DLL, but I am not sure if this would really help, as LV is really lazy when it hangs in the DLL call _now_! The system monitor shows no CPU usage (~1%) and does not show LV hanging, but LV does react to any clicks with long delayes, if at all. Would not like to set that up just to find out that it could not have worked.
Any C programme here that has an idea to change the home-made dll?
Greetings from Germany!
Uwe

After re-thinking the whole thing, I conclude this is impossibel, at least in the way I asked for.
To abort a process, it must be a separate process. As LabVIEW itself is a single process, I would have to bring this DLL-stuff into another process, which could just be another LV runtime engine. This might work in the devellopment system, but no way when compiling the main app into an exe itself. OR I had to use an older runtime engine.
AND, I would need to create a LabVIEW daemon that accepts the jobs with the DLL as it needs to stay in memory when being active.
AND I'd need a whole bunch of communication between both processes, exchanging different data like handles, errors, commands and communication packets.
Conclusion: I will not try going this way unless someone proofs me wrong.
Greetings from Germany!
Uwe

Similar Messages

Can LabVIEW call a DLL built with VS(2005) C++ with /CLR and Without an Entry Point

My project requires me to convert a C++ program to a DLL and having it called by LabVIEW. Due to the complexity of this C++ program (converted from fortran using f2c -C++ option), it cannot be compiled without using /clr option. I did build the application standalone (/clr), and it functioned fine. When I build it into DLL using VS2005, I was forced to use No Entry point option and without using DllMain in the C++ code. Eventually the DLL was built without error. But after I call it from LabVIEW, I was not getting calculated results as expected. I added a testing function to the C++ code of the DLL and just try to modify a parameter, it will not, but only return the input numbers. I was passing data by pointer and not by value, so I expect this parameter output be modified. I suspect that the DLL didnt get executed at all as it has no entry point specified.
Am I on the right track to approach this task, or I am heading to totally wrong direction here? I believe due to the fact that my C++ was from f2c and use vsf2c.lib and so on, the code is managed code, so that a regular DLL cannot be built from it with an entry point. How can LabVIEW call such a DLL? Am I right on that? I really need your advice here for a right approach to this problem and possible implementation "watch outs"...Thanks!
Bryan

Hi...Finally I was able to compile my code with an entry point defined and without using /clr. I can also call this DLL from LV and got back a variable from a little test function added to the DLL. But the function that was used for my main application in the DLL crashed LV and I got a pop up box from Microsoft Visual C++ Runtime Library: Runtime Error! "This application has requested the Runtime to terminate it in an unusual way, please contact the application's support team for more information". In Visual Studio I also got the following message: (I eliminated most of the "No symbols loaded" messages that are not errors but just info.) I would apprciate if someone can take to look with your more "experienced eyes", many thanks! Bryan.
'LabVIEW.exe': Loaded 'C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll', No symbols loaded.
'LabVIEW.exe': Loaded 'C:\WINDOWS\system32\xpsp2res.dll', Binary was not built with debug information.
'LabVIEW.exe': Loaded 'C:\Program Files\National Instruments\Shared\nicont.dll', Binary was not built with debug information.
'LabVIEW.exe': Loaded 'C:\Program Files\National Instruments\Shared\NICONTDT.dll', Binary was not built with debug information.
'LabVIEW.exe': Loaded 'C:\Program Files\National Instruments\LabVIEW 8.5\resource\nitaglv.dll', No symbols loaded.
'LabVIEW.exe': Loaded 'C:\WINDOWS\system32\lkbrow.dll', No symbols loaded.
'LabVIEW.exe': Loaded 'C:\WINDOWS\system32\lkrealt.dll', No symbols loaded.
'LabVIEW.exe': Loaded 'C:\Program Files\National Instruments\LabVIEW 8.5\resource\Framework\Providers\lvdaq.mxx', No symbols loaded.
'LabVIEW.exe': Loaded 'C:\Program Files\National Instruments\LabVIEW 8.5\resource\Framework\Providers\lvdesktop.mxx', No symbols loaded.
'LabVIEW.exe': Loaded 'C:\Program Files\National Instruments\LabVIEW 8.5\resource\Framework\Providers\lvfp.mxx', No symbols loaded.
'LabVIEW.exe': Loaded 'C:\WINDOWS\system32\mfc71.dll', No symbols loaded.
'LabVIEW.exe': Loaded 'C:\WINDOWS\system32\MFC71ENU.DLL', Binary was not built with debug information.
'LabVIEW.exe': Loaded 'C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\FieldPoint\SubVIs\FPLVMgr.dll', Binary was not built with debug information.
'LabVIEW.exe': Loaded 'C:\Program Files\National Instruments\LabVIEW 8.5\resource\Framework\Providers\lvfprt.mxx', No symbols loaded.
'LabVIEW.exe': Loaded 'C:\Program Files\National Instruments\LabVIEW 8.5\resource\Framework\Providers\LvProjectProxy.mxx', No symbols loaded.
'LabVIEW.exe': Loaded 'C:\Program Files\National Instruments\LabVIEW 8.5\resource\Framework\Providers\LvRealTimeCoreProvider.mxx', No symbols loaded.
'LabVIEW.exe': Loaded 'C:\Program Files\National Instruments\LabVIEW 8.5\resource\Framework\Providers\MVEProvider.mxx', No symbols loaded.
'LabVIEW.exe': Loaded 'C:\Program Files\National Instruments\LabVIEW 8.5\QtCore4.dll', Binary was not built with debug information.
'LabVIEW.exe': Loaded 'C:\Program Files\National Instruments\LabVIEW 8.5\QtXml4.dll', Binary was not built with debug information.
'LabVIEW.exe': Loaded 'C:\Program Files\National Instruments\LabVIEW 8.5\QtGui4.dll', Binary was not built with debug information.
'LabVIEW.exe': Loaded 'C:\Program Files\National Instruments\LabVIEW 8.5\resource\Framework\Providers\mxLvProvider.mxx', No symbols loaded.
'LabVIEW.exe': Loaded 'C:\Program Files\National Instruments\LabVIEW 8.5\resource\Framework\Providers\nimxlcpp.mxx', No symbols loaded.
'LabVIEW.exe': Loaded 'C:\WINDOWS\system32\nimxlc.dll', No symbols loaded.
'LabVIEW.exe': Loaded 'C:\Program Files\National Instruments\LabVIEW 8.5\resource\Framework\Providers\variable.mxx', No symbols loaded.
'LabVIEW.exe': Loaded 'C:\Program Files\National Instruments\LabVIEW 8.5\resource\Framework\lvMax.dll', No symbols loaded.
'LabVIEW.exe': Loaded 'C:\Program Files\National Instruments\MAX\UI Providers\FieldPoint71.dll', No symbols loaded.
'LabVIEW.exe': Loaded 'C:\Program Files\National Instruments\LabVIEW 8.5\resource\MathScriptParser.dll', Binary was not built with debug information.
'LabVIEW.exe': Loaded 'Z:\bli\development\projects\galfitDLL\Debug\galfitDLL.dll', Symbols loaded.
'LabVIEW.exe': Loaded 'C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6b128700\msvcr80.dll', No symbols loaded.
'LabVIEW.exe': Loaded 'C:\Program Files\National Instruments\LabVIEW 8.5\resource\mesa.dll', No symbols loaded.
'LabVIEW.exe': Loaded 'C:\WINDOWS\system32\mscms.dll', No symbols loaded.
'LabVIEW.exe': Loaded 'C:\WINDOWS\system32\icm32.dll', No symbols loaded.
The thread 'Win32 Thread' (0xf94) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x90c) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0xfd0) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0x284) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0xdac) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0xa98) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0x528) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0x614) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0xa5c) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0xebc) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0x5cc) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0x700) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0xcf0) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0xc7c) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0x4c8) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0xa4) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0x52c) has exited with code 3 (0x3).
The program '[804] LabVIEW.exe: Native' has exited with code 3 (0x3).

Can Ora_ffi call ActiveX DLL function???

Hi, Can I call an ActiveX DLL function using ora_ffi or by any other means? Ora_ffi documentation says that it can call C dll functions.Can I call VB dll functions from forms PL/SQL.

Hi, I don't have any experience in calling DLLs, but you may want to give this a try.
report zrich_0001.
data: path type string.
path = 'C:WINDOWS<the_file_Name>.dll'.
call method cl_gui_frontend_services=>execute
 exporting
 application = path
exceptions
 cntl_error = 1
 error_no_gui = 2
 bad_parameter = 3
 file_not_found = 4
 path_not_found = 5
 file_extension_unknown = 6
 error_execute_failed = 7
 others = 8.
Regards
Rich Heilman

How can i call a DLL file from labview?

Iam using a sensoray 2601 module.It is given as DLL file(S2600.DLL).How can i call this function from LabVIEW?
Please Mark the solution as accepted if your problem is solved and donate kudoes

As far as I can tell problems might occur with the call library function node if the the DLL from visual basic is actually an ActiveX dll if that is the case it seems calling the dll by using the Invoke node is the way to go.
Have a look at this
/sletten

Can I call a function from a dll in LabVIEW that returns:double*string and int.?

I have a function from a dll that return a double* string and an integer. How can I call this function from LabVIEW? There is a possibility to work in LabVIEW with a double* string?

pcbv wrote:
> Hello all, The header of the function is:
>
> "HRESULT WRAPIEnumerateDevices(WRAPI_NDIS_DEVICE **ppDeviceList, long *plItems);"
>
> where WRAPI_NDIS_DEVICE have this form:
>
> typedef struct WRAPI_NDIS_DEVICE { 
> WCHAR *pDeviceName; 
> WCHAR *pDeviceDescription; }
> WRAPI_NDIS_DEVICE; 
>
> The function is from WRAPI.dll, used for communication with wireless card.
> For my application I need to call in LabVIEW this function.
Two difficulties I can see with this.
First the application seems to allocate the array of references
internally and return a pointer to that array. In that case there must
be another function which then deallocates that array again.
Then you would need to setup the function call to have a pointer to an
int32 number for the deviceList parameter and another pointer to int32
one for the plItems parameter.
Then create another function in your DLL similar to this:
HRESULT WRAPIEnumExtractDevice(WRAPI_NDIS_DEVICE *lpDeviceList, long i,
CHAR lpszDeviceName, LONG lenDeviceName,
CHAR lpszDeviceDesc, LONG lenDeviceDesc)
if (!lpDeviceList)
return ERROR_INV_PARAMETER;
if (lpDeviceList[i].pDeviceName)
WideCharToMultiByte(CP_ACP, 0,
pDeviceList[i].pDeviceName, -1,
lpszDeviceName, lenDeviceName,
NULL, NULL);
if (lpDeviceList[i].pDeviceName)
WideCharToMultiByte(CP_ACP, 0,
pDeviceList[i].pDeviceDescription, -1,
lpszDeviceDesc, lenDeviceDesc,
NULL, NULL);
return NO_ERROR;
Pass the int32 you got from the first parameter of the previous call as
a simple int32 passed by value to this function (and make sure you don't
call this function with a higher index than (plItems - 1) returned from
the first function.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

How can i avoid a pop-up window when calling the avi.dll?

Ok, here another try!
My problem is as followed:
My program calls the avi.dll to initialize, write into and close an
avi-file.
Now, when initializing it, a pop-up window is shown so you can choose the
codec to use.
My question is, can I pre-define the codec, so the pop-up window won't show
up?
The program is meant to write several files, some starting without the user
having to control them, so the pop-up window really isn't helping.
Any ideas?
I attached the avi.dll in case you need it to look at the problem.
Also helpful would be, if someone could tell me, how I can take a closer
look at the structure of the dll. Is there a program I can do that with?
Thanx!
regar
ds,
Martin

Hello Martin,
I have used this DLL before and wasn't asked to choose a codec. Maybe if you use all three functions (init, write, close), it works without problems. Here's a example that uses IMAQ hardware to acquire an 8-bit image at 30fps and writes each image to an avi file.
There are utilities to examine dlls (see what functions are exported and what the dependencies are, but you can't see source code since it is compiles.) Check out QuickView or DependencyWalker.
Attachments:
avigrab.zip ‏66 KB

Can LabVIEW call a function from a .sys file or is LabVIEW limited to dll access?

My vendor has sent me a .sys file with functions accessing their hardware. Can i call these function from labview directly or do I have to wrapper the .sys with a dll?

Well a sys file is a kernel device driver. LabVIEW does not have any direct way of accessing such a driver. The way kernel drivers are accessed is usually through a DLL which makes calls to WinAPI functions such as CreateFile(), ReadFile(), WriteFile(), CloseHandle() and DeviceIORequest(). Since these WinAPI calls are basically just DLL calls too, you could theoretically use the Call Library Node to call them and access the kernel device driver in such a way.
However for any kernel device driver with more than one or two device driver calls, it will certainly be easier in terms of development, debugging and maintenance of the code, to write actually a dedicated DLL in C/C++ for this device driver and access that DLL from LabVIEW, especially if you consider the LabVIEW datatype limitations when designing the DLL interface (Basically this same DLL can then be called from any other Windows development environment, be it Visual Basic (similar datatype limitation as LabVIEW), Delphi, (Visual) C, LabVIEW or also various scripting environments like Python and Lua.
Some of the necessary WindAPI calls are rather involved and pose quite a bit of trouble to get the parameter data right in LabVIEw.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Can we call DLL method in jave code

hi,
can we call DLL file method in java Code or program.

See
http://forum.java.sun.com/thread.jsp?forum=52&thread=179765

What are analogous shared libraries that can be called using a call library function to user32.dll and lvtoolbox.dll when using Linux and Mac?

I am wondering if anyone is familiar with how to get similar information with a LV program using a Linux shared library as well as the corrolate Mac library to the Windows user32.dll and lvtoolbox.dll. I specifically am trying to get system metrics such as screen resolution information and cursor information as well as being able to set mouse position. I am trying to convert a LV Windows program to these other operating systems and I am unfamiliar with these platforms.
Thanks for your time - I really appreciate it.

There is no simple answer to that. On Linux you will likely have to call into X Server, which would be a pain to do, due to various versions and implementations of that. On the Mac there would be the difficulty that you can't call into the native ObjectiveC API but would need to find a Carbon API or something like that to do what you want.
If you seriously want to do something like this for multiplatform, you should bite the bullet and start coding an intermediate shared library in C. This library would export a LabVIEW friendly C API and access whatever system API you need to have for the particular functions. But multiplatform programming on this level is a pain in the ass, no matter what.
Message Edited by rolfk on 04-21-2010 08:26 AM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Can cobra call win dll?

I know jni is for calling the window dll but i heard that cobra also can do that. Is it correct?

Cobras are snakes.
CORBA is one mechanism for calling services on a different process. You can use it to communicate between a Java process and a native one, or anything else.
A windows DLL is not a process, but you could write a COBRA enabled process that called the functions you wanted in the DLL.
But I found it easier to use JNI when I last tried.
Pete

Can a VI compiled in dll be called in LV?

Hello,
I have some dll´s, which use some common VIs. This means, each time when I compile a dll, the VI will be compiled within the dll. What habbens, if I compile the same VI in another dll, and call the dlls in the same time. Will be there a collision, that the VI is already loaded , by calling the second dll?
regards
Mitulatbati

Maybe I did not understand the question correctly...
If you have a vi that is compiled into a dll and then from another vi (main) you call both the original VI and the dll, it should not collide as you would be calling different objects.
Have you tried it and having problems?

HT201210 After downloading latest version of iTunes it will not open. This error message is displayed; The program can't star because MSVCR80.dll is missing from your computer. Try reinstalling the program to fix this problem. Then a second error box

After iTunes requested that I download latest version on PC it now will not open. 2 error messages appear. first: The program can't start because MSVCR80.dll is missing from your computer. Try reinstalling the program to fix this problem. second: iTunes was not installed correctly please reinstall iTunes. Error 7 (Windows error 126). I have tried reinstalling a number of times and restarting computer but no luck.

This happened to me today as well post installing the latest version of itunes. I did a search on google for the error and came across a recommendation to :
Note: Start Windows in Safe Mode to complete any of the following steps if you're unable to access Windows normally due to the msvcr80.dll error.
If, and only if, you're receiving the msvcr80.dll is missing error when you open Apple iTunes, do the following: (skip this step if your msvcr80.dll error is occurring with a different program)
Uninstall from Windows the following five programs in this order: iTunes, Apple Software Update, Apple Mobile Device Support, Bonjour, and finally Apple Application Support. If you have iCloud, remove it as well.
Uninstalling these programs in Windows is done from an applet in Control Panel called Programs & Features (in Windows 8, 7, or Vista) or Add or Remove Programs (in Windows XP).
Note: Songs and playlists in iTunes will not be removed when you uninstall the iTunes program or any of the other, already-mentioned Apple programs. If you'd still like to back them up, they're usually located in the My Music folder in Windows.
Download the latest version of iTunes from Appleand note the location you're saving it to so you can find it once it's done.
Run the iTunes installation as an administrator. If you're not sure how to do that, see How Do I Open an Elevated Command Prompt? for help. That procedure shows you how to open the Command Prompt program as an administrator, but the steps are essentially the same for anything, including the iTunes installation package you just downloaded.
A general overview of removing and reinstalling iTunes can also be found here on Apple's site but the above procedure seems to work better in this particular situation.

Can I call .m files from a LabVIEW executable without the full development version of matlab installed?

I have an executable that I am trying to build (and distribute). Right now, it has Matlab script nodes that call some matlab .m scripts that someone else wrote. The target PC will not have the full development version of Matlab installed. Would that work? I have tried to compile the .m scripts into a DLL, but I can't import that to LabVIEW because of the special Matlab types (*mxArrays). I have also tried to write a wrapper around that DLL, but with no success. So now I'm wondering if I can either call the Matlab .m scripts directly from a Matlab Script node OR if I can call my Matlab DLL from within a script node. OR any other idea someone might have...
Thanks a lot!
-Matt Bradley
************ kudos always appreciated, but only when deserved **************************

Simon,
I looked at MathScript and am considering using it, but one thing that is not clear to me is if I will be able to use my .m files like I can with Matlab. I call the same Matlab script repeatedly and it keeps track of some information in global variables (for example, the number of consecutive detections). Can I do that entirely within mathscript or would I have to reload all of the info each time -- if I had to do that, it would mean substantial changes to the .m files ... and that's not an option.
-Matt
-Matt Bradley
************ kudos always appreciated, but only when deserved **************************

How to auto-recognize the function parameters called from a DLL built by VC6.0

Hi,
I use Teststand 3.5 with C/C++ Adapter, and the DLL is built by VC6.0.
While I specify module for an action, the parameters of a function called from the DLL are not recognized.
Since I have the DLL source, I know I can select the source file and verify prototype in the "Source Code" Tab.
Under the way, almost parameters can be recognized, but some parameters, e.g. HANDLE or I definded, can not ( shows error message "The function definition cannot be found in the source file...").
How to recognise these parameters?
Thanks.

The problem isn't that TestStand doesn't have enough native types. A handle can be represented in a TestStand numeric variable just fine. Instead, the issue is that when you select Verify Prototype, TestStand doesn't fully pre process your headers and compile your code to determine the types. To do so would require TestStand not only to be a full C/C++ compiler but it would also have to be able to read your compiler's projects and settings to resolve include paths, macros, etc.
Since TestStand is not a C/C++ compiler, it just looks for the standard basic data types plus a few more that are common in test code. Other data types will not be automatically recognized even if they can be mapped to TestStand types.
Another option it to create a type library for your dll so that TestStand can automatically read the data type information from it. However, I don't know if that works for struct parameters and I looked for the document on devzone that explains how to do that in VC++ and it has been moved or deleted
Maybe an AE would know of a link to a current document that describes how to do this?

Can't start because msvcr80.dll is missing

I downloaded the update for itunes 11.1.4 this morning and got the message " service'apple mobile device'(apple mobile device) failed to start. Verify that you have sufficient privileges to start system services.
I tried retry and ignore, but the message kept coming back. I then used abort.
The installation was completed successfully or so the pop up said, when it finished i tried to open itunes and got the message"The program can't start because MSVCr80.dll is missing from your compuiter. Try reinstalling the program to fix this prlblem.
I have reinstalled 4 times and get the same problems.
Now I can't use Itunes and have no way to change my ipods video files.
Please some one help!!

Go to Control Panel > Add or Remove Programs (Win XP) or Programs and Features (later)
Remove all of these items in the following order:
iTunes
Apple Software Update
Apple Mobile Device Support (if this won't uninstall move on to the next item)
Bonjour
Apple Application Support
Reboot, download iTunes, then reinstall, either using an account with administrative rights, or right-clicking the downloaded installer and selecting Run as Administrator.
The uninstall and reinstall process will preserve your iTunes library and settings, but ideally you would back up the library and your other important personal documents and data on a regular basis. See this user tip for a suggested technique.
Please note:
Some users may need to follow all the steps in whichever of the following support documents applies to their system. These include some additional manual file and folder deletions not mentioned above.
HT1925: Removing and Reinstalling iTunes for Windows XP
HT1923: Removing and reinstalling iTunes for Windows Vista, Windows 7, or Windows 8
tt2

Can a call to a DLL be aborted?

Similar Messages

Maybe you are looking for