I have a N5230A PNA. The output of the adapter characterization macro has numbers I do not recognize:
7.85E+08 -3.39E+01 -1.74E+02 1.30E-01 -1.54E+00 2 1.302579E-00 1 -1.538720E+0 02 -3.839649E+0 01 4.731741E+001
I understand the list is: stimulus, S11 real, S11 imaginary, S21 real, S21 imaginary, S22 real, S22 imaginary, but do not understand the number (for example) 2 1.3002579E-00.
Please help. Thanks.
7.85E+08 -3.39E+01 -1.74E+02 1.30E-01 -1.54E+00 2 1.302579E-00 1 -1.538720E+0 02 -3.839649E+0 01 4.731741E+001
I understand the list is: stimulus, S11 real, S11 imaginary, S21 real, S21 imaginary, S22 real, S22 imaginary, but do not understand the number (for example) 2 1.3002579E-00.
Please help. Thanks.
http://na.tm.agilent.com/pna/apps/applications.htm
Hey Jvall: you need to put on Dara's latest on the apps page too.
The attachement is the exact output. I executed the macro twice & got the same numbers both times. I'll try the latest download you've suggested. Thanks, Ken
PNA Firmware Download:
http://na.tm.agilent.com/pna/firmware/firmware.html
If you try the newest version and you still see the same problem please send me the two calsets that you are pointing to in the macro so that I can re-create the problem and find the cause. You can save your calsets as individual .cal files by creating a channel, applying the calset to it and make sure to choose the option th change the channel stimulus to match the calset stimulus. once you have the channel associated with each calset do a save as and choose .cal file format.
Send me a PM and I can give you an email address to send files to or you can attach them to a post on this topic.
Thanks.
Still experiencing the same problem after upgrading firmware to rev. A.07.50.57. I tried attaching the cal sets to this post & received error "The extension cal is not allowed". My email address is k.ballschmieder@mskennedy.com. Please let me know yours.
Thanks, Ken
or post them direcly to daras.
dara's email is dara_sariaslani@agilent.com
It turns out that the calsets used to create this S2P file were calibrations performed on 2 different ports. Technically the macro should have not allowed that, so that is a bug that I will fix in the next release of the application (but it is considered minor). However, even with the two calsets that I got from Ken I could not reproduce the malformed S2P file that he has seen in his setup, so at this point I can't tell what might have caused the numbers to come out the way they did. I will continue looking into possible explanations, but given that Ken's actual use model is not supported by the application, I am considering the matter closed unless the problem resurfaces and can be duplicated in a way that I can debug it.