Agilent ENA s3p file

[jjp377]

In the manual [DATA] is optional, so it is not included above for the last command

For sp4

modify the last part of the 2nd command to S4P 1,2,3,4

and change extension to s4p

[aap348]

I think I am in a similar situation as you at the moment.  I am trying to get the data out as .s1p from the ENA to my computer via labview.  I would like to take it off as a text file.  The problem I am running into is even if I name it and store it on the computer, I cannot get it to transfer via touchstone format (.s1p) to my computer.  

Do you know the command to get it to transfer what is saved?  How did you get arround this issue?  Did you save the data to your computer?

If you could send me an example of the code you used, that would be very helpful

Best,

Adrian

[NIYiran]

Hi Adrian,

Plasmaphase mentioned using the Agilent ENA Series.lvlib:File Transfer From a Storage Device.vi to grab the file from the Network Analyzer and store it to a local file. However I would highly recommend opening up a new forum thread if that does not work, since this this topic is from several years previous, and it's unlikely that the original posters are still monitoring the thread. 

[aap348]

Hi Yiran,

So I finally got the program to work where I am taking the measurement, labeling the file (i am able to find the file on the ENA computer), writing the memory transfer function but once I get there, there seems to be a problem with the timing.

I tried the Binblock function that someone previously mentioned however I cannot get it to work.  I keep getting the same error1073807339 function which seems to indicate that the entire file could not be written.  It seems to be timing out.  

What is the best way to get the data in the .s1p file out of the computer and into labview so that I can then save by formatting the string into an ascii file?

Does there need to be a delay to get all the data out?  How do I put in the delay?

Thank you!

[NIYiran]

Hi Adrian,

We have several functions in the Timing palette available to delay execution: Wait (ms), Wait Until Next ms Multiple, and Time Delay Express VI. You can configure any of those functions to delay for a set amount of time. However I am unsure as to whether or not a delay would actualliy benefit your application. 

Generally speaking however, VISA timeouts occur when the instrument is not sending any data back which can be due to incorrect command, broken cable, broken device, or even just miscnofigured port settings. I also noticed that the VISA commands you are passing in are different from the VISA commands that earlier posts in this thread recommended. That may be another issue with your application.

Moving forward, so long as you are passing VISA commands directly to your Agilent device, there may be more resources available by contacting Agilent or their communities. I would recommend looking through our Instrument Driver Network (www.ni.com/idnet) to see if your instrument has a higher-level instrument driver API available in LabVIEW. Finally, I would highly recommend opening up a new thread if you have further configuration questions to increase visibility in case other users have further input. It would also allow the solution-found mark to be more useful for others who may have similar problems.