accident of LabVIEW

Similar Questions

• LabVIEW closing command line

  Hi all

  I was wondering if there is a way to close the LabVIEW.exe from the command line. I came across the taskkill command as well, I found that it does not properly close the app and can eventually cause accident of LabVIEW.

  Why I want to do it is because I am developing an application that needs to run on the computer of LV 10.0. So it will check what version of LV is running, and if it's not 10.0 it should close the LabVIEW.exe and open version 10.0 of LabVIEW.exe.

  Now I know how to open LabVIEW.exe using the exec.vi system , but can someone tell me how to close LabVIEW.exe using it.

  PS: I can't use the leave LabVIEW as well because it will close my application.exe himself.

  Best regards,

  Amine31

  Hi Amine31,

  I see what you mean - I had a game and released the files that apply. I tried to build an exe file and it seems indeed close LabVIEW.exe leaving a compiled exe in the course of execution, although if you have not saved or run screws, it will jump to the top of the user... dialog boxes could help if.

  High lift the page file, you must run obviously 'abandonment application.vi'... by running in the development environment, it will end itself!

  Good luck!

  Ian

• An array of LStrHandles to the breast to call library node grave Functio Resizeing down Subvi.

  Hello

  I try to resize a table of LStrHandles in a shared library. Here the code C - attached a picture of the appellant Subvi:

  / * Call library source file * /.

  #include
  #include "extcode.h".

  / * Typedefs * /.

  typedef struct {}
  long dimSize;
  LStrHandle elt [1];
  } TD1;
  typedef TD1 * TD1Hdl;

  long strArray (TD1Hdl arg1);
  long strArray (TD1Hdl arg1)
  {
  long err = 0, count = 2;

  ERR = DSSetHandleSize (arg1 (UHandle), count + (long) sizeof * sizeof (LStrHandle));
  {if (Err)}
  printf ("ERROR: 'DSSetHandleSize()': %ld\n", err);
  return err;
  };

  (* arg1)-> dimSize = (* arg1)-> dimSize;

  return noErr;

  }

  I know there is a lot of discussion, I read some and also tried the source code provided but somehow LabVIEW crashes. I don't know if it's valuable, but when I change the next line it don't crash:

  (* arg1)-> dimSize = (* arg1)-> dimSize;

  Thanks for any help,

  Johannes

  OS: RedHat

  LV: 8.2 teacher

  To be honest I'm not entirely sure why that would break but good process is much more complicated than what you have done. The crash probably can't function of C, but the return of the function such as LabVIEW tries to display data. DSSetHandleSize() doesn't boot the zone allocations in addition it of probably garbage that LabVIEW then tries to interpret as string handles and therefore crashes.

  You should also use NumericArrayResize() where possible because it supports various complications that can be difficult to deal with cross-platform programs. NumericArrayResize() use internal DSSetHSzClr() which initializes additional memory to 0. That would avoid the accident since LabVIEW interprets handles NULL as the default value for the data type, which would here be a string empty.

  #include "extcode.h".

  #if IsOpSystem64Bit

  uPtr uQ #define

  #else

  uPtr uL #define

  #endif

  typedef struct {}

  dimSize of Int32;

  LStrHandle Elm [1];

  } TDStrArr, * TDStrArrHdl;

  MgErr MyArrayFunc (TDStrArrHdl stop)

  {

  Int32 count = 4;

  LStrHandle p;

  MgErr err = noErr;

  / * Table could be non-empty, so have all of the items there are larger than we need * /.

  for (i = (* arr)-> dimSize - 1; i > = count; i--)

  {

  p = (* arr)-> Elm [i];

  If (p)

  DSDisposeHandle (p)

  }

  (* arr)-> dimSize = i + 1;

  / * resize the table handle to get enough space * /.

  ERR = NumericArrayResize (uPtr, 1, (UHandle *) & arr, count);

  If (err)

  return err;

  / * Fill in the data as desired * /.

  for (i = 0;! err & I)< count;="">

  {

  p = (* arr)-> Elm [i];

  #if! complicated

  ERR = NumericArrayResize (uB, 1, (UHandle *) & p, 1);)

  #else

  If (p)

  {

  ERR = DSSetHSzClr (p, sizeof (int32));

  }

  on the other

  {

  p = DSNewHClr (sizeof (int32));

  If (p)

  (* arr)-> Elm [i] = p;

  on the other

  ERR = mFullErr;

  }

  #endif

  If (! err)

  ERR = LStrPrintf (p, "% ld", i);

  }

  (* arr)-> dimSize = i;

  return err;

  }

  Rolf Kalbermatter

• LabVIEW 2009 accident while trying to go to the dialog box properties of the VI

  Hello

  I can't go into the properties of the VI... It hangs for a few seconds and then every moment of the accident. I use 9.0f3 Version of LabVIEW.

  Any that have fallen on this?

  I guess I'll have to reinstall LabVIEW!

  Thank you!

  Vincent

  
  

• LabVIEW FPGA SPI accident - SPI OR IP address for example - R series OR

  Hello

  I am trying to run the series R - sample project NI SPI FPGA Simulation.lvproj that comes with the SPI IP OR on a real FlexRIO FPGA SMU-7976R target with an attached digital adaptation NI 6581 B Module. The example is for a PCIe-7841R but I wore during my target FPGA, follow these steps and made additional changes to try to make it work with my set-up. I learned that FlexRIO FAMs CLIPs do not work with nodes in office had so I know I can't simulate the project originally planned so I will try to use FPGA to e/s node host side (open FPGA vi reference) to implement the actual hardware.

  My first question concerns my configuration of the adapter module e/s and selection. I added the IO Module (NI 6581 B: NI 6581 B channel) for my project and selected the channels as shown in the table below. I have a real physical hardware connection as described below using two NI SHC68-C68-D4 cables and a break-out Board.

  

  I changed the names as well:

  

  I selected these DIO channels because I wanted the DDCA connector to be the master and the DDCB connector to be the slave. In addition, in this CLIP every eight channels of i/o has a write enable signal. I have not used the Port configuration because I needed 4 available DIO channels and I saw DIO0-3. Is my logic of selection of channel vs correct Port here?

  Following the same strategy that examples FlexRIO/NI6581B, I changed the FPGA.vi to include initialization outside of timed loops:

  

  And in the Host.vi I have a node reference FPGA and wired loops of feedback accordingly:

  

  When I compile the FPGA and try to run Host.vi LabVIEW inevitably crashes with Crash Reporter below and must restart:

  

  Does anyone know what I'm doing wrong here? My guess is that it has something to do with the CLIP/IOModule. Any help is appreciated.

  Thank you

  Scott

  Hi Scott,.

  I suspect that the problem might be related to the fact that your node open FPGA VI reference is in the while loop and trying to open a new FPGA reference at each iteration.
  If you move outside of the while loop, it does not solve the crash?

  On channel vs port question, your logic seems reasonable to me, but I recommend to try it since this feature could depend on device.

• LabVIEW 2009 sp1 not having replied to the questionnaire / accident

  Hello

  I seem to have developed a problem with LabVIEW, in which case it freezes at a random point during execution. It is not a matter of a VI gel, rather LabVIEW itself stops working and has closed by the Task Manager. What I have running at the moment is a VI host that sends and receives data over a TCP connection to a target in real time on a PXI system. The real-time application continues to operate after the crash. The host system is also running control of 3D image showing some basic graphics. The entire system is controlled at a higher level by a program crushed in c# via a TCP connection, but can work alone. When you run stand alone the problem will not occur.

  The communication between LabVIEW and c# works very well, but at a random time during the operation, LabVIEW freezes while c# continues to work. This does not appear to correspond to a particular action by the c# program. I guess my question is, is there any likely culprit by which LabVIEW can be crushed by an exernal program where the only communication is via TCP, which seems to work very well and where it does not seem to be excessive memory or CPU usage?

  See you soon.

  Fixed a problem with an update of the graphics card driver.

• The last time that you have run LabVIEW, an error internal or the accident occurred in fpsane.cpp, line 444. WHY?

  I get this error everytime I open 10 LabVIEW. Everything seems to work fine whenever I use it, but for some reason, LabVIEW not close properly and linger in the background. I still see the icon in the task bar and I would sometimes close with the the Task Manager for re - use LabVIEW. There, someone knows how to fix this?

  Attachment:

  

  Thanks Hinz,

  I think I was able to solve this problem myself using "LVdebugKeys". I managed to isolate the offending using debugging VI and it came out that an old "write Test data to file vi." work well with LV2010. I replaced this vi and it gives me is no longer the mistake.

  Thank you for your help.

• LabVIEW crashes when opening the project

  Hey guys,.

  I'm running into an interesting issue where LabVIEW crashes when you open a project. This is the second time I encountered this problem on the same project. To get around it the first time, I simply deleted and remade my project, but since it happened again, I need to find a way to debug it. The symptom is that LabVIEW will crash at the opening of the project (sometimes I can see the screen "loading the vi") with no indication that the accident occurred. It does not even launch the reporter of the error, the process just dies. Anyone know how I can go about debugging it?

  xkenneth86,

  What version of LabVIEW? Have you had previous versions of LabVIEW on your computer? You can attach a screenshot of the accident?

• LabVIEW 13.0f2 crashes when text cut of some free labels on the block diagram

  While reviewing the documentation of a VI, I faced a LabVIEW crash. I can reproduce it in LabVIEW 13.0f2 with the following code.  Can anyone confirm that the content 'def' Cup free label and trying to stick to the free label with "ghi" produce error 0xBC0BF185?

  I can't reproduce this problem by any other cut and paste between the free labels on the left side of the BD.  The accident occurred only when 'def' cutting and trying to stick to the "ghi".

  

  Hi all

  I looked into this, and it is more general than just the madness in the label. I dropped the CAR 442743 for this behavior. It's an accident that can occur when cut and paste text between the free labels in 2013 of LabVIEW with the disabled automatic tool. This is related to the CAR 408955 (deadlock occurs when deleting a comment with the automatic tool off) that has been corrected in the Patch of f1 2013 LabVIEW. This case was not covered by that fix and will be fixed in a later version.

  Thank you

  Jeff Peacock

  Product Support Engineer | LabVIEW R & D | National Instruments

• GPIB crashing when running labview

  I'm under labview 8.6 on windows 7 with a GPIB-USB-HS which is connected to a HP 34401 multimeter. This configuration is used to register the pressure readings. Recently I had an issue where labview will suddenly freeze and stop taking the pressure values. This accident occurs randomly and without warning. It may be triggered by pressure changes very quickly, but I'm not sure. Initially, I assumed from the computer, the drivers or the multimeter, but I have since excluded these sources. Now my only conclusion is that the GPIB has failed somehow. Is there anyway I can diagnosis the GPIB or fix this problem?

  Looks like our problem was that we had a bad connection with our cable gpib, labview to expire causing waiting to talk to the instrument, it was connected to. We exchanged the bad cable and no more crashing.  Thank you!

• accident LV2013?

  
  

  Hi ouadji,

  We are already aware of this CAR (there is another CAR # for what it 408955). Crash occurs when you do not use the autotool and you change comments. For now the workaround is to use the automatic tool for editing comments, we are investigating the incident. The accident occurred only in 2013 of LabVIEW.

  Thanks for pointing

  Kind regards

  Jeff Peacock

  Product Support Engineer | LabVIEW R & D | National Instruments

• Legend bug XYGraph slider blocks instantly LabView 2012

  Hello!

  I'm just facing a very annoying bug.

  Please find my attached VI example, I would like to know the weather, you can confirm the bug? Run the VI if you want to see a curve (in fact the bug appears even if you put all the data on the chart, if you do, all the same) and after that try to click the cursor vertical scroll bar legend to scroll upwards or downwards to see the cursor names.

  It instantly blocks my full version of LabVIEW 2012 Edition: 12.0.1f2 (32 bit). This XYGraph is still blocking LabView... I can't continue with my project, now I will just try to work around the error, I'll try to remove the sliders and then add them again...

  In any case, a very strange and very annoying behavior...

  Anyone could repeat the same bug?

  Thanks for the support!

  The reason for the accident seems to be duplication of the cursor "Gas_inject." There are four times. Using the property node 'CursorList' to remove these duplicates made the VI DO NOT crash when you move the vertical scroll bar of the legend of cursor.

  To simplify:

  Read the CursorList first, remove any duplicated the table manually in the indicator (right-click on the element > data operations > Delete Element). The change to a control, change the property node to write and run the VI once.

  Norbert

• LabVIEW FPGA: An internal software error in the LabVIEW FPGA Module has Unknown

  Sir/Madam,

  Note Labview 2012 SP1 installed about 2 weeks ago.,.

  Accident occurred during the compilation of an fpga vi who worked satisfactorally in the past.

  When I restarted and went to the message recomplile "LabVIEW FPGA: an internal software error in the LabVIEW FPGA Module" see attached picture of popup.

  I reinstalled Labview in its entirety and backed out the changes I made to the vi but still get the same message.

  Thanks in advance

  Daryl

  It turns out that the question was in the VI and not of LabView FPGA module as the message may indicate. I created a vacuum vi, cut and pasted items in this from the vi error and recompiled and it ran very well.

  Somehow the vi has been corrupted internally.

  Thank you it's fixed.

• Open TDMS causes an immediate forced closure of labview

  Hello world

  I have just started using TDMS (and labview actually) for the first time. I managed to save data in the TDMS format that can be displayed in Excel using the importer. However if I try to open it in a vi using the TDMSopen, labview and then closes immediately. Next time I start, it offers to retrieve for me and I'm back where I started. I'm doing it just to convert the data and binary (to read by Igor Pro) Igor Wave format. By the way, if I try to use the built in Igor Pro TDMS charger it fails also, citing error DIAdem-6204... but it is perhaps a matter for Igor forums.

  Thanks for any help. I spent ages of programming to save data in this format, and it would do the job very well if he could load in Igor Pro or same LabView. I connect two groups of data. I'm streaming to the TDMS file as I write it and then defragment it when I am done with it.

  I have attached a piture of my very simple vi - you give a folder and it should load all files TDMS one by one and save them as files binary Igor. It makes no difference if I get rid of the function of the IBW.

  

  Thanks for any help

  Niall

  Hi Niall,

  Thank you for reporting this issue. There is no execuse for the crash, there defenitely a bug.

  But the TDMS file is OK and the way that you play the TDMS file is not very good, and you have a little workaround.

  

  The problem is, the group 'Data' has 6 channels in, and 2 of them are the channel of timestamp data type. When he you a 2D double data type of "TDMS read" wiring, then read covert TDMS all channels of data to double but timestamp channels cannot be converted, I suspect that's where the accident occurred.

  You can use this way, as shown in the image, below you can wire a 1 d string array as the names of input to TDMS Read channels, contains only the data type double channels and play them all

  set:

  

• Creation of Data Type when the script crashes LabVIEW

  When you use the script (LV2010) if I call the Create method of Data Type (available appeal node when a reference to the BD is cable), if I have all but 1 up to the wiring on 'style' terminal, LabVIEW, it blocks. LabVIEW then restarts with an error message saying that "the last time that you have run LabVIEW internal error or accident took place in lvmain.cpp, line 1756. If I have wiring 1 However, it creates a constant fine.

  I see in the context-sensitive help that it always creates a control at the start, but it seems that I can't get it to create a constant. So, okay, I decided to go around, create the constant, take the new object refnum he returned and there to change the constant in one control... but I can't get this work. Can someone point me in the right direction? Here is the code and the screenshot; This is a quick drop plugin.

  It is intended to run on a cluster that is perceived as an icon if you want to test, you need to create that.

  I presented the 'style' value, 0 if if you don't want to plant LabVIEW, set it up to 1.

  

  No time for an in-depth exploration now.  Create from Datatype killed my LV10.  What I was able to do after creating a constant of cluster, the consultation as an icon and select it.  (1) with the scripts, create a new VI and stick that the constant to figure (2) mount the pasted objected to the ClusterConstant and the change of control.

  I think I know where you're going, should be interesting.