12-22-2022 08:27 AM
Hello I have a problem using my Keysight 34461A. When I run my program multimeter says it's on remote mode but the program itself freezes on a intialize.vi block. I'm using labview 2018 and have correct drivers.
Is there any solution?
Solved! Go to Solution.
12-22-2022 09:11 AM
May be it takes a while to initialize? you can step inside the Initialize VI during execution to see where exactly it freezes.
12-22-2022 02:12 PM - edited 12-22-2022 02:14 PM
First thing to try is setting ID Query option to FALSE. You may have to modify your Initialize VI if the string your instrument returns isn't handled correctly.
EDIT: Of course, you should also verify your VISA resource is set correctly and physical connections are good with NI-MAX.
12-22-2022 03:14 PM
@NIquist wrote:
First thing to try is setting ID Query option to FALSE. You may have to modify your Initialize VI if the string your instrument returns isn't handled correctly.
EDIT: Of course, you should also verify your VISA resource is set correctly and physical connections are good with NI-MAX.
Just an FYI that when you disable the ID query for HP/Agilent/Keysight, it will default to a very basic set of commands that may not even work for your instrument. It depends on getting the ID to send the commands appropriate to your instrument.
12-22-2022 03:39 PM
That explains that "User Data" variable sent to the instrument I was wondering about. The Initialize VI reads the model of the instrument and enumerates it into an integer. Looks like in this case it just sets it to the simplest model in the line (the 34460A = 0) if you don't run the ID query. Interesting. Thanks for the info Bilko!
12-24-2022 04:06 AM - edited 12-24-2022 04:13 AM
One small correction: It does NOT send that User Data to the instrument. A VISA session provides a storage attribute that allows the user (here the instrument driver) to store some arbitrary information that it can later query, in order to do device specific handling. On the VISA API level this is a pointer sized integer but LabVIEW has no pointers (and the closest thing to pointers, a DVR, didn’t exist for almost another 20 years, when VISA was invented and integrated in LabVIEW).
You can think of this like a private element in a LabVIEW class and the property node is the class property accessor. All VISA property nodes don’t directly correspond to a device element but rather to an attribute of the underlaying communication interface or a VISA internal session management attribute.
12-26-2022 07:15 AM
@AdrianOstrycharczyk wrote:
Hello I have a problem using my Keysight 34461A. When I run my program multimeter says it's on remote mode but the program itself freezes on a intialize.vi block. I'm using labview 2018 and have correct drivers.
Is there any solution?
Everything said by others hear is good information HOWEVER, it fails to address one potential issue.
That DMM has a triggering subsystem. If the device is actively working on measuring almost nothing is important to the device. In fact, it will simply store most commands for later action until it is finished with its primary purpose of taking measurements. The "*RST" command will abort any active measurement.
I would suppose that you are not taking any action to abort an ongoing measurement. So, the instrument is simply too busy trying to do the important work you left it trying to finish. Like a dog you placed on a stay command, your trivial distractions don't mean anything to the well trained device.
12-27-2022 01:34 PM - edited 12-27-2022 01:36 PM
It freezes on attempting to reset and always ends on a timeout no matter how long the timeout is. I also tried using another Keysight instrument 53220a. The result was exactly the same. I'm running out of options. Is there any possibility that there's problem with my USB port?
12-28-2022 06:19 AM
How exactly are you connected? You mentioned USB. Is there a USB-GPIB adapter or, are you using a Virtual COM Port? Is the instrument configured to use the correct bus? If you are using a VCP Is the hardware driver installed?
12-28-2022 09:44 AM
I have a 34461A connected through USB and I get this for my *IDN? response:
Keysight\sTechnologies,34461A,MY53219439,A.02.14-02.40-02.14-
00.49-01-01\n
I would suggest that you close your VI and LabVIEW to make sure all VISA resources are really closed. Then open the example called Agilent 3446X Series Acquire Single.vi since it is the simplest thing to run so you avoid any confusion. Best to troubleshoot with known good examples and this works fine for me.
If it still fails the same way:
Open the RESET.VI since it not only sends a *RST, but also runs the DEFAULT.VI and then checks for errors where it may be stuck. Turn on highlighting to see which VI is the actual culprit. Then, open and debug that to see where the root cause is.
If all else fails, you can try manually resetting the instrument too (Press Shift > Run/Stop button) to clear any errors and reset to factory settings. If all that doesn't get you going, you may have a hardware issue with your USB or cabling. Obviously try the other USB ports on your PC with a known good cable.