Siglent SNA5000A two and four port VNA's

[KungFuJosh]

Do you have an example file I could try?

You got PM

Knud

What are you trying to do exactly? The CSA file you saved is a full "state" file. It saves everything about the live state of the SNA. That means if the sweep is active or on hold, that will be saved/loaded also. You can view it in an XML editor. I assume this state is part of the problem:

Code: [Select]

        <Sweep>
          <SweepPoint>2000</SweepPoint>
          <SweepDelay>0</SweepDelay>
          <SweepTime>1.8217300000000001</SweepTime>
          <PointExWaitTime>0</PointExWaitTime>
          <SweepAuto>1</SweepAuto>
          <SweepMode>0</SweepMode>
          <SweepType>0</SweepType>
If for some reason, you need to save the whole state, then set the trigger how you want it first.

If you're just trying to load a trace, then you shouldn't save the full state. If you click the save button, click File Type, and it will give you the options for:

Code: [Select]

State and Cal
State
Cal Data
Trace s1p
Trace s2p
Thanks,
Josh

[knudch]

I am fully aware of that locking the trace before saving the state would solve the problem

But rather inconveniened to discover that when you have made the measurement

I think it is a "bommer" in the firmware that it is not possible  to load a measurement without immediately to get overwritten

Knud 

[KungFuJosh]

I am fully aware of that locking the trace before saving the state would solve the problem

But rather inconveniened to discover that when you have made the measurement

I think it is a "bommer" in the firmware that it is not possible  to load a measurement without immediately to get overwritten

That's illogical. You're saving the whole state of the machine in that file option. Why wouldn't it save the sweep state? It would be a problem if it didn't.

For example, I use different saved states as presets for different reasons. 8.5GHz SA, or Cable Testing with 3 panels open how I want, DTF, etc. I load a state, and save a ton of time. Especially if the cal set was saved with it when appropriate. If I don't want it to start with an active sweep, then that's how I'll save the csa file.

What are you trying to do? It sounds from your description that you were interested in loading a trace. So you should only save the trace data. Choose the options Trace s1p and/or Trace s2p to save your trace data without it causing problems.

If you're not only trying to load a trace, what is it exactly you want to do?

Thanks,
Josh

[knudch]

The problem is I discover that difference (state/trace) afterwards and it is rather unconvienent that I now need to repeat the measurement just because of this behavior.

Knud

[KungFuJosh]

The problem is I discover that difference (state/trace) afterwards and it is rather unconvienent that I now need to repeat the measurement just because of this behavior.

So, you're still getting used to how the SNA works then? The behavior is normal; I don't know what else to tell you on that one.

You still haven't specified what it is that you want to save or load. If you want it to save the state, it will do that. The state includes the sweep and trigger settings.

Maybe you want to add a feature request where it can do a custom save state, and specify what to include?

[knudch]

I did only want to save the trace content for later analyze...
Apparently I should not have chosen to save state.

But as done...

And yes it would be nice to have the possibility to load trace data within a .csa file without getting it overwritten immediately.

I don't see the benefits of storing the trace data together with the state when trace data is overwritten when the whole state file loaded.

Think if the results are very valuable and difficult to reproduce.

 Knud

[KungFuJosh]

Submit a feature request if you want. However, trace data is trace data, and they have separate save options specifically for that already. Save whichever port you want separately and load just the trace data. That's the easiest thing to do without any headaches.

[knudch]

I am fully aware of that now....

But I need to repeat the measurement and that is no so easy....
Very inconvenient
Knud

[KungFuJosh]

Yes, I feel the learning curve pains as well with new toys.

I was very happy though when I figured out the Preset system. That makes it much easier to repeat things. For example, whatever your test is, you can set it up and save the State + Cal settings, then recall the Preset to rerun your test again.

I do that a lot for different functions rather than setting each thing manually, and then running through calibration again. That all gets tedious. I think I did a bunch of my cable tests that way initially. 

[tautech]

I did only want to save the trace content for later analyze...
Apparently I should not have chosen to save state.

But as done...

And yes it would be nice to have the possibility to load trace data within a .csa file without getting it overwritten immediately.
...................

 Knud

You have options how to save just the trace data.
Slow the Sweep and set Trigger to Single.
Then save the Trace data CSV file for later analysis.

[hendorog]

I am fully aware of that locking the trace before saving the state would solve the problem

But rather inconveniened to discover that when you have made the measurement

I think it is a "bommer" in the firmware that it is not possible  to load a measurement without immediately to get overwritten

Knud

Attached is a python script which will extract the touchstone files from a saved .csa state file. You can then load those into the SNA as a user trace.
No SNA here to test this on at the moment, but it worked on a .csa I had.

Github repo here:
https://github.com/hendorog/siglent-utils

Let me know if you want it as an executable application and I'll setup a runner on github to build it.

[knudch]

Does not work as all settings (including sweep/single) are stored within the state and is loaded...so any settings you make before loading is overwritten

Knud

You have options how to save just the trace data.
Slow the Sweep and set Trigger to Single.
Then save the Trace data CSV file for later analysis.

[knudch]

I am fully aware of that locking the trace before saving the state would solve the problem

But rather inconveniened to discover that when you have made the measurement

I think it is a "bommer" in the firmware that it is not possible  to load a measurement without immediately to get overwritten

Knud

Attached is a python script which will extract the touchstone files from a saved .csa state file. You can then load those into the SNA as a user trace.
No SNA here to test this on at the moment, but it worked on a .csa I had.

Github repo here:
https://github.com/hendorog/siglent-utils

Let me know if you want it as an executable application and I'll setup a runner on github to build it.

I will try it out and report....I made a quick look into the csa file if something like this was possible...but did not spend enough time

Done !
Works perfect !

python script is ok....Linux machines here

Thanks
Knud

[tautech]

Does not work as all settings (including sweep/single) are stored within the state and is loaded...so any settings you make before loading is overwritten

Knud

You have options how to save just the trace data.
Slow the Sweep and set Trigger to Single.
Then save the Trace data CSV file for later analysis.

How so ? 

One would normally adjust all settings before any test, then with a Single sweep capture the response and save the data to a CSV file.
You were planning to analyze later right ?

[knudch]

Does not work as all settings (including sweep/single) are stored within the state and is loaded...so any settings you make before loading is overwritten

Knud

You have options how to save just the trace data.
Slow the Sweep and set Trigger to Single.
Then save the Trace data CSV file for later analysis.

How so ? 

One would normally adjust all settings before any test, then with a Single sweep capture the response and save the data to a CSV file.
You were planning to analyze later right ?

Yes and I was not aware of this "feature behavior" before making the measurements.....now  I know 

Knud

[tautech]

New firmware for SNA5000A models except SNA5022A&SNA5032A

V1.0.0.2.16
https://siglent.oss-cn-shenzhen.aliyuncs.com/English_content/Firmware/Vector%20Network%20Analyzer/SNA5000A%20Firmware_V1.0.0.2.16_EN.zip
~85MB

Release Notes
Features and Enhancements:
1. Added GCX measurement mode.
2. Added harmonic analysis measurement function in SA measurement mode.
3. Added full-channel calibration function.
4. Added calibration information display function.
5. Added power compensation function for fixture simulation.
6. Added ECal (Electronic Calibration) characterization function.
7. Added Compression Point Search / Saturation Point Search / Normal Operating Point Search functions.
8. Added Preferences settings.
9. Mixer Measurement Mode: Now supports dual LO (Local Oscillator) function.
10. TDR Measurement Mode: Now supports extended port function.
11. GC Measurement Mode: Now supports extended port function.
12. AFR (Automatic Fixture Removal): Now supports time domain trace display.
13. Minimum Sweep Points: Now supports a minimum setting of 1 point.
14. File Manager: Added support for "Favorites" and "History" functions.
15. Power Meter: Added support for IP connection.
16. Power Meter Reading: Default frequency changed to 50MHz.
17. Switch Matrix: Added support for characterization and de-embedding functions.

Bug Fixes:
1. Fixed the issue where single-ended measurements (e.g., Sss11) would not sweep under balanced measurement mode.
2. Fixed the issue where smoothing results were abnormal under the Phase format.
3. Fixed the issue where traces might appear abnormal after executing a calibration data overwrite.
4. Fixed the issue where the power calibration progress bar might display incorrectly.
5. Fixed the issue where trace data became abnormal after recalling CSV files saved from Power Sweeps or CW Sweeps.
6. Fixed the issue where the sweep would hang when the external trigger signal frequency was high in "Point Trigger" mode.
7. Fixed the issue where the log display time might be incorrect.
8. Fixed abnormal UI control behavior in the SA measurement mode configuration dialog.
9. Fixed the issue where eye diagram data might be abnormal after modifying the rise time in TDR measurement mode.

[KungFuJosh]

Nice!

There is also one for SNA5022A & SNA5032A: https://siglent.oss-cn-shenzhen.aliyuncs.com/English_content/Firmware/Vector%20Network%20Analyzer/SNA5022A%26SNA5032A_V1.0.0.2.16_EN.zip

[hendorog]

There are some nice features in those release notes.

Great to see.

[KungFuJosh]

There are some nice features in those release notes.

Great to see.

Hopefully Rob will give back your SNA so you can test them out.

[tautech]

There are some nice features in those release notes.

Great to see.

Hopefully Rob will give back your SNA so you can test them out.

Thought I might lend it to him again next week but hendorog the jet setter is off to see the Wizard of Oz all next week.
He'll just have to wait ! 

[Cosimo_1]

Hi! Does anyone know if there's a way (using a software option) for the SNA5014A VNA to generate true-differential and common-mode stimulus signals?

[tv84]

Hi! Does anyone know if there's a way (using a software option) for the SNA5014A VNA to generate true-differential and common-mode stimulus signals?

No.

From Keysight:

"A SNA5014A does not have, as far as the published specs/manuals show, a dual-source true-mode stimulus capability — the kind Keysight offers on its dual-source 4-port PNA/PNA-X analyzers, where two internal sources are controlled simultaneously and corrected for phase/amplitude mismatch so a genuine 0° (common) or 180° (differential) signal is physically applied at the DUT reference plane. That requires a VNA architecture with two independent, phase-coherent sources (one per side of the differential pair) plus a calibration/correction application — Siglent's SNA5000A/5014A series, based on its documented architecture and options list, is built around a single sweeping source switched between ports, not simultaneous dual sources."