Labview crashing - running dll. motorbee

Hi, I'm a student doing my masters project.
I'm trying to run a dc motor with the driver board and software called motorway from pc-control.co.uk
The board came with some software to run it and I have the dll. and header files.
I have managed to import the files, however whenever I try and run the "set motors" vi, labview crashes for no reason and doesn't give an error code.
The files can be found here https://www.dropbox.com/sh/0nbrx0ncyfg58y0/rKMy9iMAKE
Thanks a lot for any help as I don't have much time to complete my project!
Cheers
Henry
Attachments:
mt.h ‏1 KB

Hello, can you please post your LabVIEW code so I can look at the error in order to be able to help.
Thank you

Similar Messages

Labview Crashes after DLL call

HI All,
I am working on to write a wrapper to a dll. The call to dll works fine an returns appropriate values but as soon as i close the VI the LabVIEW dev environment crashes. Any help on avoiding the same. I went through a lot of posts and tried varing the types of data being sent to the dll but still it gets crashed.
the dll function I am using is of the prototype(with C type call convention)
int functionName(Struct *cfg, UCHAR dNumber, UCHAR hTYPE)
The UCHAR varables I am passing as Unsigned 8-bit Integers.
For the structure I have made a cluster and am passing with Adapt to Type and as Handles.
The DLL executes fine and the VI stops too, but as soon as i try to close the VI the dev environment crashes. Please help.
Thanks.
Solved!
Go to Solution.

While nathand is right about possible other errors, the Struct that you fail to tell anything about is a big flag pole for something that might be going wrong. Show us the C header declaring the structure and function and attach the VI you created (please no BMP or other image! They do say a picture says more than thousend words, but in the case of a LabVIEW diagram a picture is not enough to show all aspects of a VI, especially things like how the Call Library Node is configured!)
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

LabVIEW Class crash - ntdll.dll access violation

Hi,
When I close my LV11SP1f2 I always get a warning.
It didn't bother me until a vi I wrote that uses a class with nothing out of the ordinary started crashing my LV.
The crash says that: "DAbort 0x37C03D in MemoryManager.cpp"
I sent the log files to the local support and they saw that the common issue between my logs is an access violation in ntdll.dll.
Any operation that uses the property nodes of that crazy class fails, sometimes with a crash and sometimes with a error that sends me to a bundle by name in the autocreated property node.
I rewrote the project with the class and there is no error.
Sending the crashing project to another computer gave no error.
Before I go on and investigate windbg to search for a conflicting app and finally formatting my entire computer could some1 help? Please...
I attached several logs for example.
Thanks in advance,
GoofyWires.
Attachments:
92c82e7b-fa2a-43af-b2be-a6650c031681.zip ‏2485 KB
daa462b5-9395-4e3f-8894-05a3bdb3d159.zip ‏65 KB
ea2c40ef-056d-41ed-a4c5-9cf4bc6666fc.zip ‏494 KB

I did a clean format and reinstalled LabVIEW 11.0.1f2 without adding many of the add-ons from VIPM and without installing the rest of my shortwave, yet, the crash is still here!
I was able to reproduce it on my pc:
1. I have a class that contains two children of another class which each contain another class with a class inside it.
2. I accessed the classed through property nodes.
3. I then went on and deleted a private data from the first class control, deleted its property nodes and added a new private data to that class control and added the property nodes for it.
4. I updated the vi that used the classes to stop using the deprecated property node and start working with the new one.
5. I did a "save all" and run the vi. All OK!
6. I closed LabVIEW and reopened the project and run the vi which is not broken! LabVIEW crashes!!!
I guess the complexity of the class is not the issue and it can be reproduced in a much simpler way.
Yet, since I bet the scenario caused you to raise an eye brow I'll give an example as an analogy:
File Handler class contains ASCII Read class and ASCII Write class which inherit from class ASCII.
Class ASCII parent contains class Headers while class Header contains class Data.
Thus, class ASCII Handler will use class ASCII Read/Write to give a high level simple interface while during the read/write the inner ASCII Read, for example, will add to the Header class in it the read data which will in turn be added to the array in the private data of class Data.
I'll try and reproduce it on a different pc and send the local NI support the code and way to reproduce.
I see two possibilities:
1. Something is wrong with my new Dell PC.
2. LabVIEW doesn't handle and propagate correctly changes in a class to all the vis that use it. Maybe changing the array size in a class overrides some memory since the class can't change its size.
Please let me know if this rings a bell.
Update: I coundn't reproduce the crash on my pc with a simpler case. There is something missing...
I'll try to replroduce with the complex class on a different pc and if it crashes I'll simply send my original code.

LabVIEW crashes with ntdll.dll!7C911e58 as the error in debugger.

I am running a streaming video application (VLC) in LabVIEW as an activeX control. There are 6 separate containers with different streams in each.
Labview Crashes citing ntdll.dll!7C911e58 as the error in debugger when I try to run the VI.
As well, every 4th attempt to run the VI results in the BSOD.
Does anyone know what I can do to try and fix this serious error?
Regards,
Sean

Which version of LabVIEW do you have? There wasn't a LabVIEW 7.2. Did you mean 7.1.1?
Did you get an error log generated? That would be useful in diagnosing the problem. This KB reviews its location:
http://digital.ni.com/public.nsf/allkb/54E361E3FF477EC186256C320068184F?OpenDocument
Trey B
Applications Engineering
National Instruments

Why does LabView crash when unloading my DLL (reentrant calls)?

I have written a DLL in Borland Delphi using multiple threads that exports several functions (stdcall). I am using LabVIEW 6i on a WinXP machine. All functions in the DLL work as expected and return correct values. Everything works fine if I set all Call Library Function Nodes to 'UI-Thread', but as soon as I set one Function Node to 'Reentrant', LabView crashes when I close the VI after it has been executed. I assume the error is caused by the DLL unloading mechanism of LabView. Other C++/Delphi programs using the DLL reentrantly work fine, this only occurs in LabView. In which thread does LabView call FreeLibrary/DLL_PROCESS_DETACH? Has anyone experienced similar problems?

I have never run into this situation myself, but I do know that calling a multi-threaded DLL or CIN from LabVIEW does depend upon the following criteria:
If your CIN/DLL doesn't have any global data storage (global variables, files on disk, etc.), AND it doesn't access any hardware (register-level programming) AND it doesn't call any functions/DLLs/Drivers that are thread-unsafe.
OR
Your CIN/DLL protects (with semaphores or mutex's) access to those global resources.
OR
Your DLL is only called from one, non-reentrant VI
OR
Your CIN is only called from one, non-reentrant VI AND you don't access any global resources from CINInit, CINAbort, CINDispose, etc. procedures.
Hopefully this information can help you out in some way.
J.R. Allen

Why does LabView crash when I run it in parallel with a temp/ RH logging probe?

I am running LabView 6.1 on windows 95. Up till now I have had no problems. However, we recently acquired a Temperature / Humidity probe which plugs into the Com1 port of the computer and logs the data using it's own software. Since then, when the two programs are used together, eventually LabView crashes with the following error message: Failure, 'image.cpp, line 5793.
Can you tell me why this occurs and what the solution is?

Taking a shot at this. It could be because the two programs are trying to access the same type of logging program(excel??). Only one link can be active at a time or they crash. Try running it without saving the data and see if it crashes.

LabVIEW crashes when you run a VI that contains a mixed signal graph with a multi-plot cursor.

Hello, LV 8.2.1 notes indicates the following bug fix:
43SAIR2A Fixed an issue where LabVIEW crashes when you run a VI that contains a mixed signal graph with a multi-plot cursor.
I am running this version, and still have this behavior. Is there anything I may be missing, and/or certain circumstances that may still be causing this?
thanks in advance,
Darren

Darren:
I looked at the CAR ID that you mentioned and the issue has been resolved in LabVIEW 8.2.1. To verify something similar, I ran the attached VI and things worked just fine. Please feel free to send me the steps to follow to reproduce the issue you are running into in 8.2.1.
Regards,
Rudi N.
Attachments:
MixedGraphs.vi ‏15 KB

LabVIEW crashing when running NI-DSP VI on Windows XP

I am in the process of upgrading a software application from LabVIEW 3.1 on Windows 3.11 to LabVIEW 7.0 on Windows XP with NI-DAQ 7.2. The hardware has been replaced, the relevant hardware change here is from the AT-DSP2200 to the NI-4551.
The source code uses the NI-DSP libraries to control the DSP2200. I can't find any equivalent in the new LabVIEW (and have assumed that there is none, this is all covered in the MAXX now). The source code has been convereted to LabVIEW 7.
When the source code is opened on the Windows XP machine LabVIEW crashes. I've traced to cause of this crash to the NI-DSP code. Whenever I try to open any VI that contains the DSP code it crashes LabVIEW. I think the problem is the CNI call
inside the DSP library. When I try opening the source code on a computer that doesn't have the NI-4551 installed there are no problems.
What is the upgrade from NI-DSP to? Is there a direct mapping of NI-DSP functions to equivalent NI-DAQ ones? How is it that having the hardware plugged in causes a crash even though it shouldn't be accesssed until I run the VI?
Any help would be appreciated.
Thanks.

Hello EborLance,
The NI-4551 can use either NI-DAQ or NI-DSA as the driver. If you only have NI-DAQ installed, any program that uses the NI-DSA functions may be crashing.
There is no direct mapping of NI-DAQ functions to NI-DSA functions but you can download and install the NI-DSA driver from the website. Current DSA Drivers
Once you have installed the NI-DSA driver, you should see the functionality you were previously used to and your program should run.
Thanks,
C. Flip
National Instruments

LabVIEW Application Builder Crash : ntdll.dll faulting module

Hello guys,
I'm currently experiencing problems while building my project (LV2012 (32 bits) , Windows 7). At the very end of application build, LabVIEW crashes with no explanation (Screenshot in french, sorry)
Windows error logging follows :
Event 1000 Application Error
Faulting application name LabVIEW.exe, version : 12.0.0.4024, time stamp : 0x4fea600e
Faulting module name : ntdll.dll, version : 6.1.7601.17725, time stamp : 0x4ec49b8f
Exception code : 0xc0000374
Fault offset : 0x000ce6c3
Faulting process id : 0x16fc
Faulting application start time : 0x01cda5350f41f87c
Faulting application path : C:\Program Files (x86)\National Instruments\LabVIEW 2012\LabVIEW.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id : 8e5b1344-1128-11e2-97d8-c0f8dae81bad
I had the same problem on LabVIEW 2011. I tried to build my application with another computer (also LV2012 32 bits and Windows 7 64 bits) and I do not have any error.
What is wrong with my computer?
For french people, topic in french
Thank you for your help,
Regards,
Quentin
Solved!
Go to Solution.

Solution found :
-Uninstall all NI products
-Clear registry keys related to LabVIEW
-Delete National Instruments directory into Application Data
-Reinstall LabVIEW

LabVIEW Crashes while closing the VI

Hi all,
I am experiencing a labVIEW crash everytime I close my VI after running it. what the VI is doing is, it communicates with an opal kelly board through the okFrontPanel.dll and reads some data from it and displays it in the front panel. The vi runs fine and I get the results as well. But after stopping the vi, when i try to close the vi, labVIEW crashes.
Has anyone faced such an issue? I would appreciate if anyone can help me fix this issue.
Thanks and regards,
Nitz
(P.S: I am not able to upload the code due to restrictions and also its a quite lengthy code to create a sample vi to replicate the scenario)
Solved!
Go to Solution.

A crash is usually an indication that something inside the DLL is touching an area of memory which it shouldn't be touching. The fact that the VI runs fine is incidental. It seems that in this case the DLL touches something which is only affected when LV needs it when closing the VI. I think the only thing you can do about it on the LV side is make sure you allocate large enough buffers for variable length parameters the DLL uses. I'm assuming you don't have access to the source code of the DLL?
Try to take over the world!

Internal error or labview crash in 7.1ver thread.cpp(2842) whats reasons and how to fix it

Hi
Everybody ,
I am working with pci-6723 and labview 7.1 yesterday when iwas testing , the programme was running , suddenly the power has gone , since i have not connected my system to UPS system got shutdown , and when i booted pc its higlighted this error , now to what extent this problem affects to my software, and how to fix it.
"Internal error or labview crash in 7.1ver thread.cpp(2842) whats reasons and how to fix it"
Thanks in advance
Rajesh

Hello Rajesh,
Do you get this error frequently or you got it only once after the power shutdown? Are you making a call to a DLL in multithreaded environment? Try mass compiling the VI by going to Tools->Advanced->Mass Compile. Also please follow the suggestions provided in this knowledge base entry regarding thread.cpp and see if that will fix the problem:
http://digital.ni.com/public.nsf/websearch/01B186B5CEB1D07786256747000F4319?OpenDocument
If you continue to have this error, is there any way you can send me a pared-down example demonstrating what your program does, so I can at least investigate to see if I can narrow down the cause of the thread.cpp failure?
Thanks and good luck!
Shakhina P.
National Instruments

LabVIEW crashes in calling dynamically linked libraries

I am using LabVIEW 7.1 for Linux.
I am interested in writing wrappers around Intel's OpenCV library. The Intel's OpenCV library contains image processing functions. I want to use LabVIEW in order to provide a "glue" for the OpenCV functions.
Using C, I wrote up edge.c which will display a OpenCV HighGUI (basically a GUI window) and wait for an event from the keyboard before closing. It is a very simple program. It compiles and executes correctly.
Using a Makefile, I created the Linux shared library .so file around it. A Linux .so shared library is the Linux's equivalent to the Window's DLL. I named the file edge.so .
When I use LabVIEW's Call Library Function Node, LabVIEW crashed. It just shut LabVIEW down automatically. It did not even display an error message which surprised me.
From the results of this forum message, I decided to write up a C wrapper around the .so file.
I wrote up the following code:
#include <stdio.h>
#include <stdlib.h>
#include <dlfcn.h>
int main()
   void *libhandle;
   int (*edge_func)();
   libhandle = dlopen("/home/elliot/opencv_code/edge_code/edge.so", RTLD_LAZY);
   edge_func = dlsym(libhandle, "main");
   (*edge_func)();
   dlclose(libhandle);
   return 0;
When I compiled and executed the code, it worked fine.
Since I want it to run in LabVIEW, I used LabVIEW's Code Interface Node.
I created a CIN and I have it auto create a C file.
I wrote the following code using the CIN:
#include "extcode.h"
#include <stdio.h>
#include <stdlib.h>
#include <dlfcn.h>
MgErr CINRun(float64 *Numeric);
MgErr CINRun(float64 *Numeric)
   /* Insert code here */
   void *libhandle;
   int (*edge_func)();
   libhandle = dlopen("/home/elliot/opencv_code/edge_code/edge.so", RTLD_LAZY);
   edge_func = dlsym(libhandle, "main");
   (*edge_func)();
   dlclose(libhandle);
   return noErr;
When I ran lvmkmf which is the LabVIEW function to create the necessary files, it created the necessary files and the makefile. I ran the makefile and it created the lsb file that is needed.
I used the CIN to call the lsb file. I ran the vi and again, LabVIEW crashed by closing the LabVIEW window without displaying any messages.
If anyone can help me, that will be great! I have no idea how LabVIEW is crashing without displaying any messages. I would assume when I used lvmkmf and the makefile to create the necessary files that it would catch any errors that it did not like. Did LabVIEW crashed because it did not like the call to display a GUI window?

From doing ldd edge.so, the dependencies (at least on the Linux box at work) are:
        libcxcore.so.0 => /usr/local/lib/libcxcore.so.0 (0x40020000)
        libcv.so.0 => /usr/local/lib/libcv.so.0 (0x40117000)
        libhighgui.so.0 => /usr/local/lib/libhighgui.so.0 (0x401ce000)
        libcvaux.so.0 => /usr/local/lib/libcvaux.so.0 (0x401eb000)
        libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x40250000)
        libm.so.6 => /lib/tls/libm.so.6 (0x40304000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x40326000)
        libc.so.6 => /lib/tls/libc.so.6 (0x42000000)
        libdl.so.2 => /lib/libdl.so.2 (0x4032e000)
        libpthread.so.0 => /lib/tls/libpthread.so.0 (0x40331000)
        libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0x4033e000)
        libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0x40593000)
        libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x40601000)
        libpangoxft-1.0.so.0 => /usr/lib/libpangoxft-1.0.so.0 (0x4061a000)
        libpangox-1.0.so.0 => /usr/lib/libpangox-1.0.so.0 (0x4063b000)
        libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x40648000)
        libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0x4067b000)
        libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x4068f000)
        libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x406c4000)
        libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x406c8000)
        libpng12.so.0 => /usr/lib/libpng12.so.0 (0x40732000)
        libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x40755000)
        libz.so.1 => /usr/lib/libz.so.1 (0x40773000)
        libtiff.so.3 => /usr/lib/libtiff.so.3 (0x40782000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
        libXrandr.so.2 => /usr/X11R6/lib/libXrandr.so.2 (0x407c3000)
        libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x407c7000)
        libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x407cf000)
        libXft.so.2 => /usr/X11R6/lib/libXft.so.2 (0x407dd000)
        libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0x407f0000)
        libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x407f8000)
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x4081d000)
        libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x408fc000)
        libexpat.so.0 => /usr/lib/libexpat.so.0 (0x4094d000)

LabVIEW crashed while loading Sensor Mapping Express VI

Dear all,
I've just installed LV8.6 evaluation with all the toolkits available in the DVD. I have two problems now, one major and one minor:
1. Whenever I tried to use the Sensor Mapping Express VI, LabVIEW crashed with the pop-up window saying that "LabVIEW 8.6 Development System has stopped working". When I expanded Window's error pop-up, the message as can be found below. The same error occurs whenever I tried to load the sensor mapping demo I downloaded from the Developer Zone. I'm using Dell Inspiron 640m, by the way. When I tried with another Dell laptop (Dell Vostro), everything was alright.What I've done so far is to uninstall all NI's softwares inside this laptop, defrag, clean the registry and then reinstall LV 8.6 again but to no avail.
Error message:
Problem signature:
Problem Event Name:    APPCRASH
Application Name:    LabVIEW.exe
Application Version:    8.6.0.4001
Application Timestamp:    4862fd60
Fault Module Name:    ig4dev32.dll
Fault Module Version:    7.14.10.1147
Fault Module Timestamp:    457ef11c
Exception Code:    c0000005
Exception Offset:    000063b2
OS Version:    6.0.6001.2.1.0.768.2
Locale ID:    17417
Additional Information 1:    da97
Additional Information 2:    7a880e72b9f1636f81b04947e06e5c6a
Additional Information 3:    09b4
Additional Information 4:    56e138085db0c350e7bf46ba31a7691f
My computer specs are:
OS: Windows Vista Home Basic
RAM: 1.5 Gb
Harddisk: 10Gb free (after LV is installed)
Processor speed: 1.6 GHz Dual Core
Anti Virus: Kaspersky Internet Security
2. This is minor but still an annoyance. Whenever I tried to load my newly installed LabVIEW 8.6, it takes about 10-15 minutes before I got the Getting Started window. This includes the 5 minutes waiting period before I got the window stating how many days left for evaluation. This wasn't the case when I used LabVIEW 8.5.1 (even when every toolkits and modules are installed). Why so long?
I've asked the local NI engineers but they are also clueless.

Hi Lan,
Thanks for your post and I hope your well today.
1) You specs seem okay.
Minimum
Recommended
Processor
Pentium III/Celeron 866 MHz or equivalent
Pentium 4/M or equivalent
RAM
256 MB
1 GB
Screen Resolution
1024 x 768 pixels
1024 x 768 pixels
Operating System
Windows Vista/XP/2000
Windows Vista/XP
Disk Space
1.6 GB
1.6 GB (Note -- Includes default drivers from NI Device Drivers CD)
There has been some record of issues with the Sensor Mapping Express VI.
Does it crash when you place it down on the block diagram? Or when you click to move it? Or when you run it? Does this happen when you load a model into it?
However, as it seems to be an instance of your Dell Inspiron 640m, Im not sure what we can suggest - except to ask how the specs compare between the two machines?
Some advice for Dells,
#) So that LabVIEW can function properly with the video hardware, it is
occasionally necessary to reduce the video acceleration. You can do
this on Windows 2000 by right clicking on your desktop » Properties » Settings » Advanced » Troubleshooting.
Start with the second setting from the right, "Disable bitmap and
cursor acceleration.", and work your way left if the problem persists.
#) Number of other issues with versions of Dell video drivers.. upgrade?
2) If this is a new installation that is slow then you may be having issues with specs, however there are a few things to try:
a) Defrag Drive
b) VLM licensing? If so, there is a timeout of a view minutes... is your version licensed currently?
c) Clean your registry
d) Check LabVIEW ini file to make sure the tasks are all necessary and the paths are local.
e) Repair LabVIEW finally
Hope this helps make some progress,
Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help!

Labview crashing when building application (exe)

Hi,
I am trying to build an application from a simple labview (2011) vi. All the vi does is sets (boolean = TRUE) a line on the digital output card (NI 9472) when I start running the vi. The program works fine after I have coded it. But when I try to build an exe file (application) of that project, then labview crashes in the build process. Is this a known issue? please help. I am attaching my vi alongwith this email
Thanks
Solved!
Go to Solution.
Attachments:
relayProject.lvproj ‏34 KB
relay.vi ‏21 KB

I'm sorry to hear that gascars. I have downloaded your project and VI and have succesfully built an executable in both LabVIEW 2011 and LabVIEW 2012. Can you please send me a screenshot of the error you are receiving? Also, can you make a simple VI that just adds two numbers and see if that can be made into an .exe.
Thanks
Chris
Chris
National Instruments
Applications Engineer

Labview crashes when selecting simulate signal

Each time labview 8.6 crashes after I selected the simulate signal function. I get an error message about ivanlyss.dll. The message is in Dutch and it's hard for me to translate but there seems to be a problem initializing the dll file.
I asked a collegue to send me a vi containing simulate signal and the same thing happened: labview crashed.

Hi Stefan,
I can't post a vi with the simalute signal since labview always crashes as soon as I select this function. I guess you are right and the best thing I can do is reinstall labview.
Ronald

Labview crashing - running dll. motorbee

Similar Messages

Maybe you are looking for