Labview freezes when VI runs, must restart PC

[johnsold]

Ian,

You did not fix the Use Default if Unwired tunnels.

I tried to do some clean up on your code so it is more readable.  Except for the display indicators all the code in cases 1, 2, and 3 is identical.  You should create subVIs so that you do not need to duplicate code.  A sub VI for each of the three frames in the sequence structures is probably appropriate.  Use data flow to establish dependencies between the subVIs and you do not need the sequence structures at all.

It is not clear what you are trying to do with the data outside the while loop, but I am almost certain there are easier ways to do it.  Insert into Array can lead to memory allocation problems.  It is better to use Build Path than to do string manipulations and String to Path. You may be able to use Write to Spreadsheet File.vi directly rather than formatting a string and writing to text file.  

Since I did not have your subVIs, you may get som ewarnigns or errors about different paths when you open the modified VI.

Lynn

[Ben]

If the instrument are GPIB, then make sure you have the updated VISA drivers etc. I have seen an old VISA driver lock-up an applciaton.

Ben

[IanMcD]

Thanks for the suggestions. I'm using VISA / Serial for everything, I do have the latest (5.1.1)...should I also download the GPIB drivers too?

How can I go about monitoring the memory allocation better?

[Ben]

---

@IanMcD wrote:

Thanks for the suggestions. I'm using VISA / Serial for everything, I do have the latest (5.1.1)...should I also download the GPIB drivers too?

How can I go about monitoring the memory allocation better?

---

To rule out the GPIB driver yes.

THe Windows Task manager perfomance tab will show you memory usage.

Ben

[IanMcD]

Update:

   I changed over to an old laptop, installed the necessary drivers, etc. and plugged in all the cables. After just a bit of tweaking...the program ran...well! I ran it a few times over the course of an hr or two to check and had no freezing.

   This leads me to belive that it has something to do with the pc I was running it on. (Despite it having 4x the RAM and a much better processor, etc.)

   My friend then suggested that maybe the old laptop is 32-bit while the pc that wasn't working may be 64-bit. I will check this tomorrow.

   I also plan on switching the pc's and trying a new one to see if that works just the same. Will update when I figure it out. Thanks

Ian

[RobCole]

---

@IanMcD wrote:

   I changed over to an old laptop, installed the necessary drivers, etc. and plugged in all the cables. After just a bit of tweaking...the program ran...well! I ran it a few times over the course of an hr or two to check and had no freezing.

---

I would open MAX and look at the software to see if they are running the same versions of all drivers. Even something as subtle as a minor fix or service pack could make the difference. Make the PC drivers match those of the laptop and see if that fixes the problem.

Also, make sure your graphics drivers are all up to date. I have had that stop a graphics intensive program (LabVIEW) once before.

     Rob