Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

Calibration files for HP8753D sometimes fail to transfer when using NI supplied VIs.

I have been using the LabView driver for Agilent HP8753D Network Analyser
that I obtain from NI to transfer calibration and state files between Analyser
and PC.

The key VIs being used are: HP8753 Save/Recall Calibration.vi and HP8753
Save/Recall State.vi.

I have found that sometimes the calibration is not implemented in the Network
Analyser when copying files from PC to Analyser.

I have spoken to Agilent, and they have made 2 suggestions to this problem:
- there is a timing issue; not enough time is being allowed for transfer
before the next action is performed,
- the files are being corrupted or changed in some way in the transfer (note
that the files stored on PC ar
e NOT being corrupted)

The problem seems to be random; generally the transfer is fine, but sometimes
it fails.

Can anyone shed some light on this problem?

(link to original files in the NI download area : http://zone.ni.com/idnet97.nsf/dbdd9b9b4f791d3c8625643400733d3d/99fd4a9bfc561ba7862568ab005fbb48?OpenDocument)
0 Kudos
Message 1 of 6
(5,203 Views)
Stevaan Hall wrote:

> I have been using the LabView driver for Agilent HP8753D Network Analyser
> that I obtain from NI to transfer calibration and state files between Analyser
> and PC.
>
> The key VIs being used are: HP8753 Save/Recall Calibration.vi and HP8753
> Save/Recall State.vi.
>
> I have found that sometimes the calibration is not implemented in the Network
> Analyser when copying files from PC to Analyser.
>

I looked them over and do not see any MAJOR problems, I dont have a prog manual
but I assume that all the commands / formats are correct.
The VIs were written for the B version and sometimes there are minor changes that
may produce the results you are seeing. In the Save portion of the Cal vi it says that
the 1 path 2-port cal is for the 8753 only.
Not quite sure what that means.

Also in the save portion the file is written with a tab before and after "POINTS"
This may not be a problem but usually tabs are expanded to spaces and the number
varies by platform. Also they are writing the points with a %02d and reading with just %d.
I might save the same one 2 or three times and do a diff to see if there are any errors.

Good Luck
0 Kudos
Message 2 of 6
(5,203 Views)
"I have been using the LabView driver for Agilent HP8753ES Network Analyser
that I obtain from NI to transfer calibration and state files between Analyser
and PC.

The key VIs being used are: HP8753 Save/Recall Calibration.vi and HP8753
Save/Recall State.vi.

I have found that the state file which is furnished will work correctly
but when you create your own state file and try to read it back in
will lock up the the Network Analyser.

Can anyone shed some light on this problem?
0 Kudos
Message 3 of 6
(5,204 Views)

Hi, I have a similar problem with calibration files for HP8753D. Actually, I try to save the calibration from my Analyzer to my PC and it doesn't work. I mean, it is saved but I can not read the file.

Could you explain me, why?

0 Kudos
Message 4 of 6
(4,948 Views)
Hi Ninicocolala,

Are you using the instrument driver linked here?  I looks like it's been updated since the last posts on this thread.  If you downloaded the driver before 2005, you might want to try this one.  If you have the latest, how are you trying to read the file, and are you getting any errors?  

Regards,

Adam W
Applications Engineering
National Instruments

Message Edited by Adam W on 04-17-2007 07:01 PM

0 Kudos
Message 5 of 6
(4,911 Views)

I have recently run into the same problem, and may have a solution that I am yet to prove, although it is a possible problem in the driver anyway

When loading calibration data into the network analyser the transfer would sometimes fail.  I have not had time to re-try this out although i think i have found the problem.  In the Cal file they use the POIN; command say for example POIN201;

From the Manual :

"This command should be followed by a wait command equal to at least 2 sweep times"

The driver doesnt implement this and could be the source of the timing issue.  Will update next time I have chance to get on the analyser.

Craig

LabVIEW 2012
0 Kudos
Message 6 of 6
(4,601 Views)