Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers

[tautech]

Exactly that.

And again, you can't really go wrong with activating the additional options with the keygen. But increasing the bandwidth can mean that the bandwidth increases, but that this is not a calibrated function anymore because of missing calibration by the factory.

Maybe Tautech knows more.

Only what study of the X-R range datasheet tells me. 

[Zenith]

The first thing everyone seems to do is "expand" the bandwidth.
Question:
Is this really necessary, if I buy a model with say 2.1Ghz now, am I "missing out" on anything if I don't upgrade it to X.XGhz?

Increasing the bandwidth of my scope and AWG made them vastly more useful.

For the 2.1GHz spectrum analyser,  1GHz would probably be enough for anything I've done so far. Increasing ihe bandwidth to 3.2 GHz was a bit of harmless fun.

[Bicurico]

A bandwidth increase is always a win.

At worst case, you can look at more harmonics. So definitely useful.

And it does not mean that the calibrated range is suddenly uncalibrated, since the limitation was just by software.

[EE-digger]

Kudos to those who ventured out on 100 man years of work to get the "upgrades" figured out. 

What I am worried about is the loss of any factory cal that makes a unit meet all specs at 3.2 / highest GHz.  On the send side this could include things like leveling vs frequency for the VNA or for the TG.  On the receive side it might include compensation by frequency segment, control of supply voltage or offsets, etc.  I have a good cal kit and am not so worried about results to a reference plane.  I suppose successful SOLT cal is a fair indication that all else is pretty good.

Has anyone compared the SVA1032X you "created" to a genuine one?  Were VNA specs like directivity, frequency range still met?  I read one post with concerns about his SOLT result but I think it may have been an interpretation issue.  Are your SOLT cals good and repeatable?

Thanks.

-- edited for brevity --

[EE-digger]

The first thing everyone seems to do is "expand" the bandwidth.
Question:
Is this really necessary, if I buy a model with say 2.1Ghz now, am I "missing out" on anything if I don't upgrade it to X.XGhz?

Increasing the bandwidth of my scope and AWG made them vastly more useful.

For the 2.1GHz spectrum analyser,  1GHz would probably be enough for anything I've done so far. Increasing ihe bandwidth to 3.2 GHz was a bit of harmless fun.

Of course it all depends on your needs but just picking up the 2.4GHz band opens up wide possibilities to work with Wifi, Bluetooth, all the other protocols that are popular for comms, home control remote control, etc.  Small antennas, filters and layouts for that band are possible.

[xugmu]

No, it can't.
The data stream is much too high.
You need a propper TV field meter to be able to do that.
Let me know if you want some suggestions on capable TV field meters and/or other options.

An OFDM carrier occupies only 1K. Would the SSA3000 be able to isolate it from the rest of the carriers and represent it in a constellation?

Best regards

[videobruce]

When it comes to VNA's the calibration is everything.  Its not cheap to make a good OSL with a known and true 42dB return loss into the GHz.  There are books just on the calibration process alone.  This one is in my amazon wish list 
I picked up this OSL, very good quality but not too bad a price for a home lab https://rftestparts.com/
I would really like one with female ends as well.

Can this be used as a RLB??

[tautech]

When it comes to VNA's the calibration is everything.  Its not cheap to make a good OSL with a known and true 42dB return loss into the GHz.  There are books just on the calibration process alone.  This one is in my amazon wish list 
I picked up this OSL, very good quality but not too bad a price for a home lab https://rftestparts.com/
I would really like one with female ends as well.

Can this be used as a RLB??

No.
OSL Cal kits are only used with VNA's. Each port is Open, Short or Load and only configured in a tee for convenience. They share just the 1 common connection, the shell.

[videobruce]

Ok, thanks. I guess that is off my short list for another RLB.
Unfortunately what I choose many years ago for my SA was not the one Siglent offered since for some reason or another I never knew they offered one. 
To make matters worse, I paid $200 over what Siglent is selling theirs now, but at least, it is US made. 

My SA is the original 'X' version. Maybe it wasn't offered in 2017?? 

https://www.tequipment.net/Siglent/RB3X25/Spectrum-Analyzer-Kits/

[videobruce]

I see there is a F/W update for the 'X' version which I didn't expect, especially after this amount of time since it was introduced (2016). My current version is v1.3.9.7.
I also see a 'KeyGen' script. I haven't kept up with this really long thread, as I'm always nervous 'flashing' F/W (knock on wood. I've never 'bricked' any device yet (knock on wood). Any issue at this late date to flash this 1.3.9.10? I assume I can skip .9 ?

[trackersoft]

I just received my SSA3015X Plus from Saelig and the cal cert says first time use was 9-2-2019 and next cal is due 9-2-2020 which means cal has expired. Is this right to get a new one with expired cal cert?

[tautech]

Ok, thanks. I guess that is off my short list for another RLB.
Unfortunately what I choose many years ago for my SA was not the one Siglent offered since for some reason or another I never knew they offered one. 
To make matters worse, I paid $200 over what Siglent is selling theirs now, but at least, it is US made. 

My SA is the original 'X' version. Maybe it wasn't offered in 2017?? 

It was and I got one when I got my first SSA3032X.....probably 2018 ?
https://siglentna.com/product/rb3x25/

You could buy the RLB by itself or including an option license.

[tautech]

I see there is a F/W update for the 'X' version which I didn't expect, especially after this amount of time since it was introduced (2016). My current version is v1.3.9.7.

You are actually a few versions behind and there are update steps required to get to the latest.

They are described in a PDF that comes in the FW package so a quick study up will reveal the steps needed.
You can find everything you need here:
https://int.siglent.com/download/firmwares/?ProId=29

[trackersoft]

I just received my SSA3015X Plus from Saelig and the cal cert says first time use was 9-2-2019 and next cal is due 9-2-2020 which means cal has expired. Is this right to get a new one with expired cal cert?

Just talked to Saelig and the Cal had expired in December 2023 -- they did an RMA and are shipping me a new unit. Great company to work with.

[videobruce]

You are actually a few versions behind and there are update steps required to get to the latest.
They are described in a PDF that comes in the FW package so a quick study up will reveal the steps needed.
You can find everything you need here:
https://int.siglent.com/download/firmwares/?ProId=29

There is only a version 1.3.9.8 after 1.3.9.7 that I'm running and before the current 1.3.9.10 issued 2/25/24. Unless I missed a v1.3.9.9 which I didn't see on that page you linked. 

[tautech]

You are actually a few versions behind and there are update steps required to get to the latest.
They are described in a PDF that comes in the FW package so a quick study up will reveal the steps needed.
You can find everything you need here:
https://int.siglent.com/download/firmwares/?ProId=29

There is only a version 1.3.9.8 after 1.3.9.7 that I'm running and before the current 1.3.9.10 issued 2/25/24. Unless I missed a v1.3.9.9 which I didn't see on that page you linked. 

V2.1.1.4 is the latest SSA3000X version.
Study the upgrade steps required. 

[videobruce]

Sorry, too many numbers. I missed the v2xxx part, I was only looking at the last digit(s).   

Well, those v2 won't work with the non Plus version which I have. I see the size of the v2 file is 4x larger than the v1. 

[tautech]

Sorry, too many numbers. I missed the v2xxx part, I was only looking at the last digit(s).   

Well, those v2 won't work with the non Plus version which I have. I see the size of the v2 file is 4x larger than the v1. 

Did you try ?

Yes the version info seems contradictory. 

[videobruce]

"Seems"?? Dangerous would be more like it.  Just like the warning in the OP (in red);

It is old mistake when these both models, X and Xplus are mixed here in same thread. If later Siglent produce different different models where HW etc is very different, even if model number is nearly same etc. It is best to keep both tightly in totally separate threads for avoid confusion and mess what can also see here in this thread many places.

The size of the file for V1 is 7MB
The size of the file for V2 is 30MB
That in itself should raise red flags. I've seen F/W file sizes vary by size, but surely not like this. If nothing else, I would be concerned about memory space available from one to the other model.

the last update for V1 is dated 1-21-24,
the last update for V2 is dated 7-3-23

This warning is in this v2 firmware;

If your analyzer has an earlier version（V1.x.x.x）, it can not upgrade to” V2.x.x.x” version and
the “V2.x.x.x” version also can not downgrade to the earlier version

[videobruce]

I'm ok for someone else tiring it.   

FYI, below is a list of the F/W versions for the X (original) model based on the V1 series from 2016

[Bicurico]

The are two HW revisional of the SSA3000X series.

The original uses the v1.x FW.

The new revision shares the same HW platform as the SSA plus and SVA models. I am still interested to find out if some cross flashing is possible.

The old HW was discontinued because it does not make much sense to buy the non plus model. It is kept because some companies might consider it, I guess.

[videobruce]

Anything to confuse matters worse. 
Is my assumption about the file sizes correct regarding the larger file HW version would require more system memory to handle that extra data?

[dibro]

The firmware update instructions pdf states:
2. If your analyzer has an earlier version（V1.x.x.x）, it can not upgrade to” V2.x.x.x” version and
the “V2.x.x.x” version also can not downgrade to the earlier version
So I guess "SSA3000X_Firmware_V1.3.9.10 (Release Date 02.05.24 )" is the save way to go.

[Bicurico]

The v2.x FW is for a completely different HW platform!

There is no issue with the increased filesize of the FW - the new HW platform has simply a bigger flash. No problem with that!

In other words this means:

1) The original SSA3000X hardware platform has been discontinued.
2) The new SSA3000X hardware platform is compatible with the SSA-P/SSA-R/SVA hardware and shares the same FW base, which uses the same main application. This makes sense, because it reduces manufacturing cost.
3) It does not make much sense to buy the SSA3000X, since you can get for little more money the Plus version. I think the SSA3000X is kept to just complete the portfolio and to be competitive on the cheapest end.

I haven't tried, but I would expect that the device with v1.x FW would not accept the v2.x FW and vice-versa.

[hfleming]

The v2.x FW is for a completely different HW platform!

There is no issue with the increased filesize of the FW - the new HW platform has simply a bigger flash. No problem with that!

In other words this means:

1) The original SSA3000X hardware platform has been discontinued.
2) The new SSA3000X hardware platform is compatible with the SSA-P/SSA-R/SVA hardware and shares the same FW base, which uses the same main application. This makes sense, because it reduces manufacturing cost.
3) It does not make much sense to buy the SSA3000X, since you can get for little more money the Plus version. I think the SSA3000X is kept to just complete the portfolio and to be competitive on the cheapest end.

I haven't tried, but I would expect that the device with v1.x FW would not accept the v2.x FW and vice-versa.

Yep, I bought my SSA3021X in 2019, and it can only upgraded with v1.x FW. It does not accept v2.x FW.