Keysight 34908a w/ Command Expert vi just stops working

[Jim12345678]

I've written a program to work with a KeySight 34908a using a KeySight sub vi generated using the Keysight command expert.  The call to the Keysight unit is below.

The code just loops at a user defined period, reads the Keysight and plots and saves the data.  It work fine for hours and hours, but then it fails to read the Keysight unit.  I've run the test three times and it always fails after the same number of reads (2739).  If I stop the code and restart it.  It works fine again.  I doubt it has anything to do with the larger program.  I use the same code with other hardware and just change the function to read the values as needed for whatever hardware I'm using (i.e. the only difference is the "read voltage" case in the picture above). Any ideas?  The Keysight is connected via the USB, but I've turned off the power saving "feature".  This is running LabVIEW 12, 32 bit on windows 7

[Dennis_Knutson]

You've got some very questionable code there with all of the locals and the stacked sequence structure. Neither should be used. What is this 'command expert' and why aren't you using the NI driver? Why is the address unwired?

[Jim12345678]

Command expert is some Keysight program that generates the LabVIEW module.  It was created by their software as shown.  I prefer to use locals and sequences - given the power of today's computers the inefficences they bring about are of no concern to me.

[Dennis_Knutson]

You aren't concerned about race conditions or hard to read code, then.

Try using the supported driver instead of Keysight's. I would not trust that. You would obviously need to show that subVI if you want help debugging their code.

[RTSLVU]

---

@Dennis_Knutson wrote:
You aren't concerned about race conditions or hard to read code, then.

Try using the supported driver instead of Keysight's. I would not trust that. You would obviously need to show that subVI if you want help debugging their code.

---

Dennis is correct on all points here.

The 34980A is not that much different than the 34970A that we used extensively in our lab.

I have found that Keysite has hosed most of the software that Agilent already hosed after Carly sold them off from HP

I do not even bother to install any software that comes from Keysight anymore.

Download the LabVIEW driver and use it, forget about the so called "Command Expert".

Search the forums for examples using the 34970A, they are more popular and programming them is pretty much identical to a 34980A

[Jim12345678 · Accepted solution]

After exchanging emails and phone calls with Keysight, I was told that the LabVIEW add on for Command Expert version 1.4 has a memory leak and to rebuild the code using version 1.5.  After doing so, the problem has disappeared.

[Dennis_Knutson]

Glad it's working but if you had used Help> Find Instrument Drivers initially like most users, you would have been up and running a while ago.