LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Keysight Waveform generator 33521B hangs up

Solved!
Go to solution
Solution
Accepted by topic author hasse

Thank you Ben,

the removing of Close.vi solved the problem!

The reason for me to modify the Initialize was to read out the IDN. I don't know why NI doesn't include this in their Initialize VI:s.

0 Kudos
Message 11 of 16
(1,228 Views)

 


@hasse wrote:

The reason for me to modify the Initialize was to read out the IDN. I don't know why NI doesn't include this in their Initialize VI:s.


 

They do.  If you look at the inputs to Initialize one is ID Query, which makes sure you are communicating with the expected model of instrument.  It does not supply a return string, but rather gives an error if it fails.initialize.png

 

If you want that string, don't modify the driver VIs.  Make a copy, modify and save it as "Whatever_modified.vi".  Trust me that will save you headaches later.  (You might move to a different PC or share code with a colleague and download the driver only to find that it doesn't work for an unknown reason.  I have inheritted code like that from a summer student, not fun to guess at what they modified.)

 

Glad you solved the problem.  Post more code if you need help!

 

Craig 

0 Kudos
Message 12 of 16
(1,216 Views)
Solution
Accepted by topic author hasse

I am updating this post with another solution just for reference.

The other solution with removing Close.vi helped a bit but it was still hanging up from time to time.

What really helped solving this was to install the Keysight IO libraries (found that proposal on another website).

After that I have had no more issues.

Here is a link to the IO libraries:

https://www.keysight.com/main/software.jspx?cc=US&lc=eng&ckey=1184883&nid=-33330.977662&id=1184883

Message 13 of 16
(1,197 Views)

A similar problem with a Keysight 34461A Digital Multimeter that only worked after single stepping down every sub-VI after turning on the equipment. After doing the single stepping, I could use the equipment normally. After installing the IO libraries works without issues from the beginning. Thanks! 

0 Kudos
Message 14 of 16
(622 Views)

Hi all
This problem still occur with LV2023, the Keysight33510B run with that driver very well, but only on (local)Ethernet, but it crashes on USB after Init-->SetupAnySignals-->ClearBuffer ---> Close  ... so far all without any error..., and the i make an Init again, then it crashes between write *IDN? and reading the query string (query string length is ~60 bytes, so the preset 256 byte is sufficient.
When i add delays before  and also right after the *IDN? of about 400ms, then it looks "more stable". But i hate unpredictable waits in the code, so i use the device again on LAN cable although i know that on USB the whole system would work a bit faster. The same code runs fine without extra delays with the same Keysight33510B on USB on a same PC under LV2017 Win10LTSB, but with LV2023 on Win10LTSC, USB communication is not usable. The device must run in a production testing environment with 24/7/365 runtime.  

0 Kudos
Message 15 of 16
(19 Views)