LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

why does my computer restart when I push run?

When I try to run my VI on my computer it sometimes restarts, how come?

Thanks,

Brian
0 Kudos
Message 1 of 12
(3,532 Views)
Maybe you could attach the VI that is causing the problem?

Martin
0 Kudos
Message 2 of 12
(3,532 Views)
Hi Brian,

Which version of LV are you using, what is the Operating system and what kind of PC are you using?

I originally had strange problems when I installed LV7 on a Dell Dimension PC running Win-XP. I could never explain why... My solution was simple, I moved to another PC... a clone, still running Win-XP.

There was no obvious reason for the PC to crash...

Try re-installing Labview...

;O)
Message 3 of 12
(3,533 Views)
Joe,
I recently switched over the board to a Dell Lattitude. The processor is a P3, 1gighz, and I am using LabVIEW 6.1 It is kind of wierd because it only seems to happen when I put a probe ona certain wire. Can I send you the VI and tell you which wire and see if it happens to your computer?

Thanks,

Brian
0 Kudos
Message 4 of 12
(3,533 Views)
Sure..
Message 5 of 12
(3,533 Views)
Excuse me for the delay, I have run a few tests of my own on this new machine. At first, in the VI that I am sending you, the computer would restart when I put a probe on the output error of “Brians design_snap.vi”. When I pushed run, the computer would restart and sometimes would just restart and just stay on the blue Dell Screen. It seems now that when I go down about 3 sublevels from “Brians design snap.vi” this is the order:

Brians main.vi/Brians design snap.vi/IMAQ Grab Aquire.vi/IMAQ Copy.vi

On the “IMAQ Attribute.vi” there is a list that where I can select the Attribute. When I try to select a different attribute, and then press run, the computer will sometimes restart.

The reason that I am doing this in the first place is that I used to be able to get some kind of reading from my IMAQ board, this was all on another computer, well one day for some reason I kept getting an error code, and it came from the “IMAQ Attribute.vi” once in a while there woulden’t be an error in that particular Sub VI but if you pushed the debugger and watched the information it would turn into an error code after it came out of the Bundle all the way to the right in the “IMAQ Copy”, (where the “IMAQ Attribute.vi” is). Note that this was even on the old computer.

Now it is switched over to the new computer and I still get errors in the same place but now I have an extra added computer crash that is happening lots of the time. And even as I am writing this, as the computer has kept shutting down, from me trying it out, now I even properly shut down restarted the computer and I am getting this message:

An exception occurred within the external code called by a call Library Node. This may have corrumpted LabVIEw’s Memory. You should save any work to a new location and restart LabVIEW. VI “Brians main.vi” was stopped at node 0x1230 of SubVI “IMAQ Copy.vi”


The Call Library Function Node in the “IMAQ Copy.vi”, (the same VI with the “IMAQ Attribute.vi” in it that was having problems sometimes). Also, I noticed before, when the IMAQ Attribute.vi” was working, on the Boolean “Equal?” the output from the “IMAQ Attribute.vi” labeled “Get Value” that was fed into the Boolean “Equal?), was not equal to the output of the “IMAQ GetImagePixelPtr.vi” labeled “Pixel Size (Bytes)”. This was sending a False over to the Case structure containing the Call Library Function Node that I am having problems with, (listed above).

I could really use some help. I am going to re-save the IMAQ Copy off of the LabVIEW 6.1 Disk, and see if this will clear up the Call Library Function Node. I probably pushed save after it had been modified by some error and saved the error into it, (if that can be done).

Thanks…. Brian D.
0 Kudos
Message 6 of 12
(3,533 Views)
Hi Brian,

Sorry, I could not run your vi's because I do not have the Image & Vision (IMAQ) libraries installed.

JLV
Message 7 of 12
(3,533 Views)
See attachment at the bottom..

🐵
Message 8 of 12
(3,533 Views)
Brian,

I have had this same problem with other types of daq cards. What i found out is that labview for some reason could not initialize the driver correctly and would crash or I would close out labview wrong and it would not close out the driver, then when I restarted labview and hit run on My VI it would restart the computer.one thing you need to make sure of is that the port that your card is running on is free when you start your VI.It sounds to me that it is the card or that the driver is corrupt. Try reinstalling the driver for the card and see if that helps. Also I need the inside loop VI and the outside loop VI to open your application. sorry i cannot be more helpful



Joe.
"NOTHING IS EVER EASY"
0 Kudos
Message 9 of 12
(3,533 Views)
Ok, then what should I do? Should I re-post?
0 Kudos
Message 10 of 12
(3,533 Views)