Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers

[Sully]

I have a new SSA3021X_PLUS with V3.2.2.5.1R1.  Following electr_peter post 1619 I have made it to step IV) "Update with Siglent stock firmware for SVA1032X 3.2.2.4.0 (cross-flash SSA -> SVA).

Should I proceed with installing SVA1000X FW 3.2.2.4.0 firmware from USB as the instruction lays out (will it accept the former FW) or install the SVA version my SSA has, but the SVA version: SVA1000X_V3.2.2.5.1R1.ADS?

I understand an 8GB max USB is required.  I am in search for one to do the upgrade.

THANK YOU to all who have contributed to this effort.  I have been reading and trying to compile what the latest upgrade methods were and kept going back to electr_peter's post and went from there.  Again, thank you all!

[Sully]

Added... I was not familiar with the vi editor (I have worked with Nano), so I went through the recommended link and brushed up on it.  I double checked my vi editing was correct.  I entered the static id 11403 correctly:

2) edit /usr/bin/siglent/config/NSP_config_upgrade_info.xml to change ProductID:
replace
   <upgrade_static_id>11411</upgrade_static_id>
with
   <upgrade_static_id>11403</upgrade_static_id>

[DL4JY]

When I upgraded, I copied the file(s) to the USB-stick (make R/W before) and edited them on the Windows PC with notepad++ (careful, some PC-Editors modify the files when saving). Finally I copied the file back to the Siglent.

With that I avoided VI - which I never liked.

[Sully]

There aren't too many to modify, anymore though and I'd be using NP++ for more than taking my notes.

Any experience converting/working with the newer SSA to SVA units with 3.2.2.5 + FW?

Thanks!
Sully

[EmBlocks]

@tautech Thanks for the info.

In those links are not explained why the internal limit files show the limits completely wrong (or what I'm doing wrong). I only see those limit lines when I introduce a ref offset of e.g. 80 and the lines are nowhere where I would expect them.
Perhaps the format is changed between firmware updates? It's not a big deal because those limits are easily be keyed in manually.

I saw that the saved format uses exponential notation like (+1.5000000000E+05,+6.6000000000E+01) and the stored files are using fixed like  ( 0.15, 66.00 ).  Could be a reason perhaps?

E.g. The picture below shows the content of this file below only when I introduce a reference offset.

Code: [Select]

Limit
"EN 55022, Conducted, Class A"
"Average Detector"
,
,01
Type, Upper
X Axis Unit, MHz
Amplitude Unit, dBuV
Frequency Interpolation, Logarithmic
Amplitude Interpolation, Logarithmic
X Control, Fixed
Y Control, Fixed
Margin, 0
X Offset, 0
Y Offset, 0
DATA
0.150000,66.00
0.500000,66.00
0.500000,60.00
30.00000,60.00

[Sully]

Still no go on Cross-Flashing to SVA FW.

I have a new SSA3021X_PLUS with V3.2.2.5.1R1.  Following electr_peter post 1619 I have made it to step IV) "Update with Siglent stock firmware for SVA1032X 3.2.2.4.0 (cross-flash SSA -> SVA).

I have a 1GB USB card, formatted FAT32, 4K clusters.
Attempted to upgrade to :
SVA1000X_V3.2.2.5.0.ADS - Screen changes to "Upgrading now, please wait" and after ~2 minutes it goes back to the U-Disk dir screen (reboot does not occur).
and after being unsuccessful, I attempted:
SVA1000X_V3.2.2.5.1R1.ADS - Screen changes to "Upgrading now, please wait" and after ~2 minutes it goes back to the U-Disk dir screen (reboot does not occur).

The two files I tried above are from the https://siglentna.com/service-and-support/firmware-software/ site.
I realize now, the *.ADS files being used in the cross-flashes are modified with a hex editor. 

---------------------------------------------------------------
So the *.ADS file needs to be modified using tv84s method in post:
https://www.eevblog.com/forum/testgear/hack-of-sigllent-spectrum-analyzer-ssa3021x/msg4249003/#msg4249003

Addressing V3.2.2.5.1R1 by creating a "hex mod" for V3.2.2.5.1R1 in post 2017:
https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/2000/

Update:
I did the hex editor change as seen in post 2017 by tv84.
No change on the upgrade behavior:
SVA1000X_V3.2.2.5.1R1.ADS - Screen changes to "Upgrading now, please wait" and after ~2 minutes it goes back to the U-Disk dir screen (reboot does not occur).  Tried three time.  1GB, Fat32, 4k cluster USB card.

Per directions in post 1619, my static is:
<upgrade_static_id>11403</upgrade_static_id>
should it be back to :
<upgrade_static_id>11411</upgrade_static_id>
as discussed in post 2016 by sbehnke? 

Update:
Bicurico is post 2023 addresses the double product ID:

Editing the SVA FW in an hex editor serves the purpose of changing the ID so that an SSA will accept it.

Changing the ID on the device is not necessary. If you do that you need to use the original SVA FW.

Doing both is reversing the mismatch and means you don't know what you are doing. Take a couple of hours and read through the relevant posts before bricking your device.

I'm changing back to :
<upgrade_static_id>11411</upgrade_static_id>
as discussed in post 2016 by sbehnke? 

Update:
Telnet'ed back into and changed back to 11411:
<upgrade_static_id>11411</upgrade_static_id>

Upgrade the FW to SVA1000X V3.2.2.5.1R1 and it took this time (1st attempt and with my primary USB 16GB flash drive)
SVA1000X_V3.2.2.5.1R1.ADS - Screen changes to "Upgrading now, please wait" and after ~2 minutes it rebooted with VNA as an option (in Sys info) and "Vector Network Analyzer" in Modes.

Product Info:
Still shows SSA3032X Plus as Model
...even after a couple of power cycles.  VNA enabled and needs to be ops checked.  All options Valid: Permanent, good to 3.2GHz. 

I'm happier - thanks again for posting progress updates as times change.

[ganevson]

Hi Sully
I understand from your odyssey that it was enough to simply modify the SVA1000X_V3.2.2.5.1R1.ADS file with the hex editor as per the TV84 instructions and flash the device.
If so, the ADS file will have to be modified for each new SVA update.
I wonder, since we have no ID change (remains original for SSA) will we be able to reflash the device with SSA firmware if we wanted to??

[EmBlocks]

It seems that the ssa3032x-r (but I think also others) is using 107 db(uv) as a sort of reference line for the internal EMI limits files.
The files are absolute but the SA is scaling everything according that 107 line.

I made a symlink in the Limits folder to the USB so that I could do some tests with the file syntax as that EMI module is expecting.

File:

Code: [Select]

Limit
"Test"
"Average Detector"
,
,01
Type, Upper
X Axis Unit, MHz
Amplitude Unit, dBuv
Frequency Interpolation, Logarithmic
Amplitude Interpolation, Logarithmic
X Control, Fixed
Y Control, Fixed
Margin, 0
X Offset, 0
Y Offset, 0
DATA
0.150000,-10.00
0.500000, 0.00
0.500000, 10.00
30.00000, 20.00

Picture:

[Sully]

Hi Sully
I understand from your odyssey that it was enough to simply modify the SVA1000X_V3.2.2.5.1R1.ADS file with the hex editor as per the TV84 instructions and flash the device.
If so, the ADS file will have to be modified for each new SVA update.
I wonder, since we have no ID change (remains original for SSA) will we be able to reflash the device with SSA firmware if we wanted to??

That is correct.  My inexperience in this process (although I read and reread much of this thread over a week to ten day period) convinced me to play it safe and start at Post 1619 when, in the end is exactly how you summarized it.  Pretty simple in hindsight (clearly due to the incredible efforts of many persons in this forum).
I thought it would be helpful to leave the step process I did for others to see.  Even though I studies the process that evolved over a 7+ year period, the Product ID matching (thanks again Vitor) and that the stock *.ADS file was modified via a hexeditor (and a huge thanks to tv84) was not readily apparent to me (simple for me now that I have been through the process). 

I purchased the SSA3021X-TG a the end of October and quickly expanded its capabilities with the Python script.  After getting comfortable with the device and aligning a few UHF duplexers for a few GMRS repeaters I am putting together with used mobile radios I realized a 'proper' VNA for tuning antennas was the next logical step, not mention I'd likely get a better alignment of the duplexers with the VNA (still learning).  I had been using the NanoVNA SAA-2N with good results, but really liked the larger screen and formfactor of the SSA. 
Earlier this month I purchased the SSA3021X-Plus (yes, I realize in hindsight, I could have just purchased the Plus and been here, but what's not cool about having both on the bench!?). 

So, here we are:
"modify the SVA1000X_V3.2.2.5.1R1.ADS file with the hex editor as per the TV84 instructions and flash the device"

Earlier today I was studying the Cal discussions in:
https://www.eevblog.com/forum/testgear/siglent-sva1015x-1-5ghz-spectrum-vector-network-analyzer-(coming)/625/
...seems I may or may not have the correct cal files.  I haven't looked yet.
I have the N Type Cal slugs I use with my NanoVNA SAA-2N and seeing if they will provided an adequate/good enough/proper cal for my hobbyist needs.
I don't want to screwup any cal files or settings in the device (still learning what's what), but am not opposed to seeing if it can be switched back and forth with a simple FW change.  I can do that.

Again, thanks to all who contribute to this awesome forum.  And to Siglent, yes I'll say it.  Thanks for not shutting this down for the hobbyist like myself.  It is highly likely this product line, properly licensed will outfit a medium sized engineering group who is currently using outdated older SAs and VNAs that are in need of retirement.  Expect a sale from a customer with deeper pockets than mine and can afford the maintenance and upkeep of this awesome equipment.  A shoutout to the former AF PMEL guys.

[Bicurico]

If so, the ADS file will have to be modified for each new SVA update.
I wonder, since we have no ID change (remains original for SSA) will we be able to reflash the device with SSA firmware if we wanted to??

You are wrong:

The firmware upgrade FIRST checks if the device has an ID that matches the firmware. If YES, it will proceed, if NO, it will just reboot.
As part of the upgrade, the ID will be rewritten, sometimes with a higher ID, so that downgrade is no longer possible.

What the hack does is: the ID of the CHECK is edited so it matches the ID of the SSA. Nothing else is changed.
The upgrade will proceed since the device and FW have the same ID during the check.
During the upgrade, the ID will be written, with the ID matching the corresponding SVA FW.
From now on, you can use regular SVA upgrades.

Note: the hex values provided by tv84 only work for that particular FW version. You cannot use them in any other version, because the FW checksum would be wrong. The bytes to edit include the ID and the checksum, which is why the hacked FW is accepted.

Take your time to read all posts until you understand everything.

[krzysiek-net]

My SSA3021X Plus purchased in December 2022 has firmware 3.2.2.5.1R20. This firmware is not yet available on SIGLENT....

[RoV]

My SSA3021X Plus purchased in December 2022 has firmware 3.2.2.5.1R20. This firmware is not yet available on SIGLENT....

It's not infrequent that they take months before publishing the upgrade. In the case of my scope SDS2000X-E it took more than one year  . Sometimes upgrades circulate through customer support.
It's a strange and unpleasant situation for us, but probably they are much more worried by the risk of introducing new bugs, so new customers are used as beta testers, while old customers survive to old features and existing bugs  .

[Bicurico]

Watch out, Siglent may be using a new HW platform, incompatible with existing FW releases. You should make sure you know what you are doing, because you might brick your device if that is indeed the case.

This happened with the non plus model.

[RoV]

Watch out, Siglent may be using a new HW platform, incompatible with existing FW releases. You should make sure you know what you are doing, because you might brick your device if that is indeed the case.

This happened with the non plus model.

True, but they changed the major release number in that case, from 1.3.9.8 to 2.1.1.1. In this case it is an Rxx change, bug fix only, I believe.

[Major1206]

Mine came as well with 3.2.2.5.1R20.
Therefore no cross-flash until release on the web.

Until then -> python gen to 3.2GHz + All options

Python @  #1968

@TV84
Can hex prod_id be found via sva*.ads and ssa*.ads hex compare? Or you need to unpack ADS file?

[tv84]

Mine came as well with 3.2.2.5.1R20.
Therefore no cross-flash until release on the web.

Until then -> python gen to 3.2GHz + All options

Python @  #1968

@TV84
Can hex prod_id be found via sva*.ads and ssa*.ads hex compare? Or you need to unpack ADS file?

At this moment, the safer way is downgrade to a crossflashable version (the latest I released) and do the crossflash.

Once the SVA 5.1R20 becomes available, you upgrade directly.

Don't try other gymnastics.

[Major1206]

OK, i assume, that due to minor change in FW revision 5.1R1 to 5.1R20 it should keep same prod_id and therefore be straightforward downgrade-able to 5.1R1

I noticed in .ads thread that parsing took a lot of effort.

[DeDe]

I received my SSA3021X+ a week ago with stock firmware 3.2.2.5.1R20.

After enabling telnet, doing some backups (nanddumps etc.) I directly cross-flashed stock SVA1000X_V3.2.2.5.1R1 firmware downloaded from Siglent after applying tv84's modifications in a HEX editor:
https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg4403962/#msg4403962

Finally I used the python script, set Model = 'SVA1000X', set my HOSTID and loaded licenses codes for 3032 and ALL.
Everything was working fine afterwards - except reloading VNA S11/Single-Port-Calibration data. To fix this, it was necessary to copy those 2 files na_1p + na_2p to /usr/bin/siglent/firmdata0/cali.

Maybe it would have been smarter to first downgrade to the older SSA3000XP_V3.2.2.5.1R1.ADS firmware and only then perform the cross-flash.

 

[Crambone]

I would love to upgrade to the SSA3015x plus but only if it was possible for me to upgrade it. As a computer illiterate person not even knowing what telnet is what would my odds be of performing this upgrade.

[el_man]

Hello and Happy New Year! to everyone

I've just received my new SSA 3021X plus and I'm very happy but the firmware is 3.2.2.5.1R20 
And Unfortunately the backup SSA3000X+_backup_11411.ADS doesn't work for me
The usb stick is empty only with ads file. Maybe I'm doing something wrong or it is related to the firmware
I also try downgrade to 3.2.2.5.1R1 the screen show progress but  after rebooting the firmware is the same.

Any ideas?

P.S. I'm not familiar with linux but is it anywhere instructions how to make backup trough telnet and of what?
I've already hex modified 3.2.2.5.1R1 ads file.

[DL4JY]

I would love to upgrade to the SSA3015x plus but only if it was possible for me to upgrade it. As a computer illiterate person not even knowing what telnet is what would my odds be of performing this upgrade.

are you aware to what you could upgrade with your model of SA?

[Crambone]

I would mostly like to open up all the options.

[DL4JY]

I would mostly like to open up all the options.

why are you not using the online Python script ?

[Crambone]

I’m not aware of Python script? The more I read on here the more I’m lost everyone seems to do something different or wrong. Is there a post that explains what and how it can be done?

[DL4JY]

the more you read the more you will understand. It's all in this thread. take your time. You may want to use the "search" function.