VI Not Responding When Trying to Save

[jlaijames]

I have some VIs that are used to communicate with a Spectrum Analyzer. However, for some reason these VIs occasionally have issues where Labview will freeze and say "(Not Responding)" when I try to save the program after making certain modifications. Usually it will recover after a few minutes, but I have also seen times where it will not recover. I also have the same issue opening the VIs sometimes. These VIs include some SubVIs from the driver that I downloaded for my spectrum analyzer. However, I had to modify some of the driver VIs from the spectrum analyzer driver llb because they were missing functions that I needed. I am not sure if there is a certain procedure that needs to followed when modifying a VI from a llb file, but it seems like these llb VIs that were modified are the ones causing issues in my main VI.

I attached two of my VIs.

RSA306B Integrated Power.vi- I cannot open this VI without it freezing, but it sometimes recovers after a few minutes.

RSA306B Integrated Power 062118.vi- I went back to a previously saved version of the RSA306B Integrated Power.vi VI and began making one modification at a time before trying to save it to see where I was getting the issue. The picture below shows where the freezing issue occurs in this VI. I added another item to the enum for that driver VI "tkrsa6100 Config Spectrum Trace.vi" and when I remove the enum in the main VI and replace it with a new one with the matching number of items and then try to save the main VI, Labview stops responding. Or if I remove the "tkrsa6100 Config Spectrum Trace.vi" with the "Avg Count" connected to it, the same thing happens. However, I didn't see that issue when I updated the enum for the same "tkrsa6100 Config Spectrum Trace.vi" but with the "Trace Function" and "Average" connected to it.

[azp7]

Why dont you download the original drivers again, and try to get the functions that you need in other new VI? I mean, if you know this is where began your issue, why specifically do you need change the driver VIs from the spectrum analyzer drivers instead make a new module or a new subVI with the functions you need?

[billko]

It's always a bad idea to modify the original drivers.  Make a copy and modify that.

[jlaijames]

---

@azp7 wrote:

Why dont you download the original drivers again, and try to get the functions that you need in other new VI? I mean, if you know this is where began your issue, why specifically do you need change the driver VIs from the spectrum analyzer drivers instead make a new module or a new subVI with the functions you need?

---

I don't know for sure that these driver modifications are the issue. I have been experiencing the "Not Responding" issue for a while now and originally thought it was because this computer is slow and almost out of memory, but I copied the Labview files over to another computer and ran into the same issue. This is just the first time I was able to pinpoint a modification that was causing Labview to freeze.

---

@azp7

---

I just moved my modified drivers and downloaded the original tkrsa6100 driver again but I am still running into the same issue. But now the modification that causes the freeze is different. It now freezes if I remove the wire and the "Trace Function" enum and try to save as. I checked and the SubVIs are calling the original drivers that I just re-downloaded.

[Michael_Munroe]

You don't mention the version of LabVIEW you're using, so I assume it is the same as your VI which is 2011.  Your driver is still in LV 8.2.1.  Any VI in memory that is not the current version is loaded in development mode.  This will dramatically increase memory usage and cause issues when saving code.  I recommend using Tools -> Advanced -> Mass Compile to update the driver.

Also, your driver uses the enum to combine multiple operations into a single VI.  None of the enums in your driver are saved as a typedef.  You can't modify just one of the enums in the main VI.  If you are adding a value to the enum inside the driver vi, delete all of the constant copies in the main VI first.  After saving the driver VI, right-click the terminal and Create Constant to use the current values.