[HELP] Agilent 53220A Counter Timer Will Not Initialise Using NI VI's!

[ChristopherPovey]

I am running National Instruments 2012 Development Suite.

I have hooked up an Agilent 53220A to a PXI chassis via USB and MAX can see it.

If I use the D:\Program Files (x86)\National Instruments\LabVIEW 2012\instr.lib\Agilent 532XX Series\Public\Initialize.vi library to initialise it, it takes ages before finally timing out.  I opened all the VI and issued the commands manually using the Measurement and Automation Explorer as follows:

*IDN?\n = Returned the details of the Counter Timer.

*RST\n = Returned no errors.

*ESE 60;\n = Returned no errors.

*SRE 48;\n = Returned no errors.

*CLS;\n = Returned no errors.

: SYST:ERR?\n = The subsequent read then times out!   (delete space between ":" and "S")...

If I repeat the above but skip the "*SRE 48;" command it then works.

Any ideas why my Agilent 53220A Counter Timer does not like the "*SRE 48;" command?

Thanks.

[ChristopherPovey]

---

@ChristopherPovey wrote:

I am running National Instruments 2012 Development Suite.

I have hooked up an Agilent 53220A to a PXI chassis via USB and MAX can see it.

If I use the D:\Program Files (x86)\National Instruments\LabVIEW 2012\instr.lib\Agilent 532XX Series\Public\Initialize.vi library to initialise it, it takes ages before finally timing out.  I opened all the VI and issued the commands manually using the Measurement and Automation Explorer as follows:

*IDN?\n = Returned the details of the Counter Timer.

*RST\n = Returned no errors.

*ESE 60;\n = Returned no errors.

*SRE 48;\n = Returned no errors.

*CLS;\n = Returned no errors.

: SYST:ERR?\n = The subsequent read then times out!   (delete space between ":" and "S")...

If I repeat the above but skip the "*SRE 48;" command it then works.

Any ideas why my Agilent 53220A Counter Timer does not like the "*SRE 48;" command?

Thanks.

---

I have confirmed this morning that I have installed the drivers and library for LabVIEW 2012 version from the NI website.

Any ideas anyone?

Thanks.

[Dennis_Knutson]

Since you have the same problem in MAX, I don't believe it is a LabVIEW issue. I would check the manual and with Keysight about the command and whether there is a difference between usb and gpib versions of the instrument.

[ChristopherPovey]

---

@Dennis_Knutson wrote:
Since you have the same problem in MAX, I don't believe it is a LabVIEW issue. I would check the manual and with Keysight about the command and whether there is a difference between usb and gpib versions of the instrument.

---

According to the User Guide and Programming Reference manual the command is Service Request Enable Register. "48" is defined as the following bits:

Bit 4 - Message Available

Bit 5 - Standard Event Summary

I will try sending "*SRE 16;" and "*SRE 32;" and see which "bit" it is having an issue with...

[ChristopherPovey]

---

@ChristopherPovey wrote:

---

@Dennis_Knutson wrote:
Since you have the same problem in MAX, I don't believe it is a LabVIEW issue. I would check the manual and with Keysight about the command and whether there is a difference between usb and gpib versions of the instrument.

---

According to the User Guide and Programming Reference manual the command is Service Request Enable Register. "48" is defined as the following bits:

Bit 4 - Message Available

Bit 5 - Standard Event Summary

I will try sending "*SRE 16;" and "*SRE 32;" and see which "bit" it is having an issue with...

---

I have tried some experiments and it seems to be taking exception to the "*SRE 16;" command. If I change the LabVIEW code to use "*SRE 32;" instead of "*SRE 48;" then the devices initialises without error. However the Message Available state probably impacts the other functions. So not enabling this bit might not be an option!