VI Crashes when the "Run" button is pressed again

[solarfacility_user]

The whole VI can be run, but only once. The VI crashes when pressing the "Run" button again. Is this a hardware problem? Like a GPU being unable to handle the VI?

[GerdW]

Hi user,

---

@solarfacility_user wrote:

The whole VI can be run, but only once. The VI crashes when pressing the "Run" button again.

---

Unfortunately you didn't attach all those missing subVIs…

How does your VI crash?

• LabVIEW gives an error message?
• LabVIEW closes without further message?
• Windows crashes with a BSOD?
• The computer starts burning?

What happens when you start the VI using highlight execution mode the second time? Where/when does the VI "crash"?

Do those device drivers use something like ActiveX or DotNet? Any DLLs called in the device drivers?

[cordm]

My guess is that you must close a refnum at the end of the VI run.

[altenbach]

---

@solarfacility_user wrote:

The whole VI can be run, but only once. The VI crashes when pressing the "Run" button again. Is this a hardware problem? Like a GPU being unable to handle the VI?

---

This has nothing to do with the GPU. A GPU does not "handle" a VI, I don't even know what the means.

This looks like a very poorly written "one shot" VI (no toplevel loop or state machine architecture). that was last revised about 10 years ago. Do you know who wrote it?

We can't really troubleshoot without your hardware and all the missing drivers, but chances are that the driver/instrument is left in an undefined state (i.e. not properly closed) at the end of the run and next time the VI is run and tries to connect again, things go haywire.

[Bob_Schor]

While attempting to download your VI, a lot of requests were made for things from such places as the Keithley 2600 Series folder, and a bunch of files from an "Old Desktop\AUG 31 DATA DUMP DESKTOP\DESKTOP Aud 1 2017\SAFEHarvestS folder (which also had a reference to LabVIEW 2010\instr.lib\Keithley 2600 Series).

I did look at the code that you posted, which (of course) was missing "lots of stuff".  It had a Stacked Frame Sequence, with wires entering and leaving through all four edges. truly a nightmare to dissect and figure out.  Please replace this with a For Loop (with 4 "states") containing a Case Statement that handles the four cases, using Shift Registers to hold the variables.  Find the missing Libraries (Keithley, SAFEHarvestS, maybe others), and create (probably from scratch) a proper LabVIEW Project with a recognizable model (probably based on a State Machine, possibly a QMH, DQMH, CMH). 

Bob Schor  

[solarfacility_user]

LabVIEW just closes without any message whatsoever. I haven't tried running it in highlight execution mode, so I'll verify that when I get the chance. I do remember having some VI's that have the .dll extension, although I'll check which one is which.

[solarfacility_user]

I didn't make the VI, but I made a few modifications. I don't know if starting over will fix the problem.

[MichaelS78]

It will be a dll. A dll is a dll, not a vi with dll extension! Dlls which are called incorrectly sometimes cause labview to close on the second run with no warning at all. Last time I had this was when calling convention was set up incorrectly.  Also if data is the wrong size etc...

[altenbach]

LabVIEW has very little control over what goes on inside a DLL. If it was running fine before you made modifications, focus on the modifications around the dll.