Hi Taut,
probably the SVA3kX will solve all the 1015x issues, but what will be the price?
More then 2k hear in Europe, I presume.
I want to keep the value around 1,5k eur.
Just watch siglent site and the ssa3021 TG promotion finishes 12/2018,so, in few days.
I should to decide between this two models. I have some doubts about it.
Regards
Rodrigo
can someone test the latest firmware (V2.1.1.1.13)?
https://www.siglenteu.com/wp-content/uploads/dlm_uploads/2018/08/SVA1000X-Firmware-Revise-History.pdf
Is the VNA still going from 10MHz? In the release note they mentioned changes to minimum frequency:
"VNA mode: fasten the VNA sweep speed; expand the minimum span from 10M to 10 kHz"
is there any news about the same ""procedure"" that has been done on the SSA3021X even on this model? there are a lot of cool options but the prices are a bit high for a non-professional user
Is anything known about the new higher frequency VNA that was presented a while back?
is there any news about the same ""procedure"" that has been done on the SSA3021X even on this model? there are a lot of cool options but the prices are a bit high for a non-professional userWelcome to the forum.
I don’t know any reason why it will be different to SSA models however how I got the options out of SVA was a bit different.
My SSA used the standard procedure.
Hi everyone. I usually lurk here more than post, but I thought I'd share a odd behavior of my SVA1015X that's a bit confusing.
I've only recently acquired this unit, and I'm new to spectrum analyzers, so it's very possible this is user error, but I've been looking at reviews of the SSA3021 (as I haven't found too many of the SVA1015X), and those models don't seem to behave this way.
I've noticed that when the tracking generator is ON and NORMALIZE is also on, changing the CT, Start or Stop frequencies seems to cause the SA to rerun the NORMALIZE procedure, effectively cancelling out the current waveform. I am able to consistently reproduce this behavior and I am hoping someone here can clarify where I made a mistake or maybe can confirm the issue.
My setup:
.................
I guess market for lower end VNAs is not very big? If something like this would be priced so that its attractive to "average" Amateur Radio hobbyist, Siglent probably would sell orders of magnitude more....
In my opinion, it is a BUG. It should not re-normalize after you change the CF or Start/Stop frequencies. Anyway, the logical procedure sounds like to first set the CF or Start/Stop frequencies, then normalize, then insert the DUT and measure.
In my opinion, it is a BUG. It should not re-normalize after you change the CF or Start/Stop frequencies. Anyway, the logical procedure sounds like to first set the CF or Start/Stop frequencies, then normalize, then insert the DUT and measure.
It does kind of seem that way. I would expect if you change some settings that change/effect the prior normalization it would just report that it is no longer normalized.
In my opinion, it is a BUG. It should not re-normalize after you change the CF or Start/Stop frequencies. Anyway, the logical procedure sounds like to first set the CF or Start/Stop frequencies, then normalize, then insert the DUT and measure.
It does kind of seem that way. I would expect if you change some settings that change/effect the prior normalization it would just report that it is no longer normalized.This is what I'd expect too but it's currently not the case so emails have been sent to look at this behavior so to address it or have the unit warn the user.
What do other SA's do ?
Based on the appearance of the noise in the screenshots it doesn't look to me to re-run the normalise procedure. If it was the line would be completely flat as tautech mentioned.
In fact it looks to be retaining the normalised data and using it for the reduced span, as the noise in the trace looks very similar to what it was before.
However, for some reason it is moving the trace up by 20dB. It could be that this is the real bug, perhaps something to do with the 20dB reference offset. Try again without that offset perhaps?
On my Signalhound, from memory any change to the sweep params will discard the normalised data. I think the HP 8753 VNA will 'try its best' to keep the calibration if you have interpolation turned on, but I will need to confirm that.
From a user perspective, it would be great if I didn't have to toggle the normalize for small shifts in frequency or span. If I see a part of the screen I'd like to zoom into a bit, having to disconnect the DUT each time would be pretty inefficient as I search for the best CF or span. Is this how it's done with other SA's?
Here's a video I found of a review for the SSA3032X where the author changes the span to zoom in without toggling normalize. Being able to do that would be ideal, in my opinion.
https://www.youtube.com/watch?v=Fn7uaEVeOPk, at 37:00
However, for some reason it is moving the trace up by 20dB. It could be that this is the real bug, perhaps something to do with the 20dB reference offset.
I created a video of this here:
https://gfycat.com/DimEllipticalAnura