Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers

[cubitus]

I tried to decode this is what it gives
For 2G we will say that it is OK



For 3G even though the bandwidth is 4 MHz it doesn't seem to decode anything.


It's just for fun, but I would like to have QAM modulation somewhere... can we find it on the air?

[RobbiTobi]

Demodulation and decoding is part of digital modulation analysis.
I think, there is no confusion... and nobody judges here if something is wrong or right... 
Anyway, the statistic Trace with decoding samples in MA mode is somewhat useless, if no recording and saving is available.
And everybody likes the "pay one get three", right? 

Nonsense, show a universal spectrum analyzer even much more expensive which has such a recording option...

In SSA+/SVA you have all the modulation information you need and the filters you need for analysis. One disadvantage is the high CPU load and the GUI response slower with a larger sample buffer - as shown in the video.
You just need to know how to use it - really no decoded data analysis is needed for modulation analysis (these are useful for communication protocol analysis etc.).

The limitation is the number of symbols per second which results from the fact that it is not an RT spectrum analyzer (therefore it has limited bandwidth). Even if it had more bandwidth, you still have a problem with timeslots used on e.g. cellular networks, so this decoded data would be useless. On the other hand, I have shown that the SSA+/SVA  can modulation analyze both one UMTS variant and three LTE variants.

If you want to decode data cheaply, I suggest you buy some SDR like USRP. I use my own USRP to decode data on all types of cellular networks. However, the USRP, due to its inferior RF path, is less suitable for modulation analysis.

For consolation, I will add that in the equipment (R&S FSWP) in the pictures (photos of measurements of the amateur DMR repeater made last year) I also do not have such an option (Capability to record decoded data)

All fine my friend, no need to get upset 
We are all here to learn from each other... thank you for your lessons 

[tomud]

All fine my friend, no need to get upset 
We are all here to learn from each other... thank you for your lessons 

He is not nervous. I just want to show you what the subject of modulation analysis in general purpose spectrum analyzers looks like.
Different people read the forum and then different disappointments arise. Better to avoid it and explain it exactly.
Unfortunately, this is how it looks and it is probably dictated by the financial policy of companies producing measuring equipment, it is known that directing specialized devices to specific markets (mobile phone operators, TV operators, etc.), you can earn more.

SSA/SVA was supposed to be able to save the I/Q signal to a PC (via software Easy VSA), this information can be seen in older versions of the manual. However, it seems that for some reason they did not introduce such a possibility.

I tried to decode this is what it gives
For 2G we will say that it is OK

For 3G even though the bandwidth is 4 MHz it doesn't seem to decode anything.

In the case of UMTS (HSPA +), unfortunately it will not work, here you need more than 2.5Msps.
As for the occurrence of QAM modulation, at the moment it is difficult for me to think of something, the simplest and cheapest way is to generate QAM using SDR, e.g. ADALM-Pluto etc.

[alcor6502]

Thank you BitByBit, tomud and TV84! Amazing job!
Another successful and final conversion...
Mine was a SSA3021X+ cross-flashed to a SVA1032X, running  firmware version V3.2.2.4.0 following these instructions: https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3563577/#msg3563577
These are the steps I took:

• Make files writeable
• Rename back the files nsp_data_b1 and nsp_data_b (I did not touch the NSP_sn_bandwidth.xml (verify anyway the serial number field still there) nor I regenerate the serial number with SCPI command)
• I ran the pyton script (uncomment 'SVA1000X') but be aware to use HOSTID not the serial number.
• Applied first the '3032' option and waited for reboot
• Applied the 'ALL' option.
• After reboot performed a factory reset.
• Applied V3.2.2.5.0 firmware
• Applied V3.2.2.5.1R1 firmware
• After reboot performed a final factory reset
• Restored telnet access running the patched firmware (thanks TV84)

Code: [Select]

mount -o remount,rw /usr/bin/siglent/firmdata0
cd /usr/bin/siglent/firmdata0
mv nsp_data_b1x nsp_data_b1
cd /usr/bin/siglent/usr/backup
mv nsp_data_bx nsp_data_b
sync && reboot

Worth mention, after applying the option codes the file NSP_sn_bandwidth.xml has a brand new section  <license> </license> with all the temporary options.
The Vector analyzer now works like a charm, no problem with 1 port calibration everything is super smooth! He truly believes to be an SVA!

Thanks again to all contributors!

[Bad_Driver]

One question to you all:

I did the detour with Electr_Peter's advice (as most of us I think) to cross flash my SSA to SVA (factory mode).
During this process some files were manipulated to get all licenses activated:

   NSP_sn_bandwidth.xml modified
   NSP_trends_config_info.xml modified
   nsp_data_b1 renamed to nsp_data_b1x
   nsp_data_b renamed to nsp_data_bx

Now I used the SCPI command to get my serial number back and relicensed the device with the pythons script. Everything seems to work correct.
But my NSP_sn_bandwidth.xml was not changed during relicensing.

Here my question:
Is there any need or benefit of restoring the original 4 files from my backup? Or better not to touch a running system?

[tv84]

Re-license the 3.2GHz BW and forget about the rest.

[drdupery]

Summarizing the collected information

Script to run:
https://www.online-python.com/PX3v0J8nbs

just for statistics:
generated for SSA3021X
AMK - invalid
EMI - valid
TG - valid and it is the same as from Siglent
Refl - invalid

[james38]

Jepp, the mistake he made was the option.
# Options:
# CAT  = AMK
# Meas = Refl
For AMK he must use CAT as an option also for Refl he must use Meas as an Option.

If he take this options everything is fine.

regards Chris

[RoV]

Why not ALL ?
Does it work only on the X+ ?

[Bicurico]

ALL does Not Work on the SSA3000X series.

There are options which are accepted, but don't do anything. Only 4 usefull options plus upper frequency option.

[sbehnke]

Is there a way to cross flash a 3000x+ with firmware V3.2.2.5.1R1? I might have jumped the gun a bit by updating all the way to the newest version. If I try to go back to the V3.2.2.5.0 release with the tv84 hex mod, it just says "Update Failed!" after attempting to cross flash.

[tv84]

Is there a way to cross flash a 3000x+ with firmware V3.2.2.5.1R1? I might have jumped the gun a bit by updating all the way to the newest version. If I try to go back to the V3.2.2.5.0 release with the tv84 hex mod, it just says "Update Failed!" after attempting to cross flash.

Are you saying that you did a downgrade to SSAX+ V3.2.2.5.0 and then a crossflash (with the "hex mod") and it failed? If so, that is interesting. If not, first do the downgrade.

[drdupery]

If he take this options everything is fine.

thank you, aliases do really work

[sbehnke]

Is there a way to cross flash a 3000x+ with firmware V3.2.2.5.1R1? I might have jumped the gun a bit by updating all the way to the newest version. If I try to go back to the V3.2.2.5.0 release with the tv84 hex mod, it just says "Update Failed!" after attempting to cross flash.

Are you saying that you did a downgrade to SSAX+ V3.2.2.5.0 and then a crossflash (with the "hex mod") and it failed? If so, that is interesting. If not, first do the downgrade.

I thought this might be the issue, and I tried the downgrade but it also says it fails. I had previously run with it cross flashed in "pro mode" but I put back stuff from my backup to allow it to upgrade to V3.2.2.5.1R1 with the 3000x firmware. That worked fine and I am able to license it, but I don't have the VNA option, obviously.

[Bicurico]

Problems with downgrade, upgrade and crossgrade occur 99% of the cases because the ID's don't match.

Each device has it's own ID, which the FW upgrade proceedure checks against the ID in the FW file. Flashing only happens if both ID's match.

Also, whenever a FW changes the file system substantially, so that a downgrade is no longer feasible or desired (by the manufacturer), the ID is changed.

You need to check what your current ID is. You can do that using telnet. On the SSA-XP models, there is a SCPI command to activate telnet if I remember correctly. Also, you can edit and change the ID (described in the initial crossgrade instructions).

[tv84]

You need to check what your current ID is. You can do that using telnet. On the SSA-XP models, there is a SCPI command to activate telnet if I remember correctly. Also, you can edit and change the ID (described in the initial crossgrade instructions).

I guess there is no change from Prod_ID  in V3.2.2.5.0 to V3.2.2.5.1R1. Maybe Siglent is stopping people from upgrading by checking FW version...

If I'm in the mood, I'll create a "hex mod" for V3.2.2.5.1R1.

[sbehnke]

I guess there is no change from Prod_ID  in V3.2.2.5.0 to V3.2.2.5.1R1. Maybe Siglent is stopping people from upgrading by checking FW version...

If I'm in the mood, I'll create a "hex mod" for V3.2.2.5.1R1.

I do have telnet access. According to my /usr/bin/siglent/config/NSP_config_upgrade_info.xml my upgrade_static_id is 11411.

Code: [Select]

<?xml version="1.0" encoding="UTF-8"?>^M
<nsp_upgrade_info_root>^M
        <device>^M
                <upgrade_static_id>11411</upgrade_static_id>^M
                <upgrade_start_id>11400</upgrade_start_id>^M
                <upgrade_end_id>11499</upgrade_end_id>^M
        </device>^M
</nsp_upgrade_info_root>        ^M
                ^M

I couldn't locate the SCPI command to show the product id, but you can run SCPI commands through the web interface as well, though telnet to the appropriate port is probably just as easy. Originally I set my serial number back that way.

[tv84]

If I'm in the mood, I'll create a "hex mod" for V3.2.2.5.1R1.

Here.

[sbehnke]

Thanks so much! Works great!

[cubitus]

Hello

I was in factory mode with my SSA3021 plus with all the options.
I put it back in SSA 3021 plus

I generated with the python script serial numbers for the options, everything works.

I updated the analyzer to SSA3000XP_V3.2.2.5.1R1.ADS.

So far, everything is OK for the SSA3032+.

I would like to switch to VNA1032 mode 😊

 I modified the SVA1000X_V3.2.2.5.1R1.ADS with the hex codes from @TV84

I modified the file
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>
3) Finalise changes and reboot
   sync && reboot

OK

I flashed the new filmware SVA1000X_V3.2.2.5.1R1.ADS with @TV84 hex codes

I edited the NSP_sn_bandwidth.xml file,

Code: [Select]

<?xml version="1.0" encoding="UTF-8"?>
<nsp_trends_info_root>
<device>
<language>english</language>
<pid>0x1301</pid>
<vid>0xf4ec</vid>
<product_type_1>SVA1032X</product_type_1>
<manufacturer>Siglent</manufacturer>
<Support_Touch_Flag>1</Support_Touch_Flag>
<Support_VXI11_Flag>1</Support_VXI11_Flag>
<file_prefix>CP_</file_prefix>
</device>
</nsp_trends_info_root>
Do we really need to rename the 2 files
nsp_data_b1 nsp_data_b1x
mv nsp_data_b nsp_data_bx

for it to work ?

For the moment I still have the name is still SSA 3032X Plus
With my correct serial number and only the options of the SSA3032plus...

I must be close
Help please

[cubitus]

I think my SSA3021 did not accept the SVA1000X_V3.2.2.5.1R1.ADS with the hexadecimal codes from @tv84

if I enter the option codes, those made for SSA 3021+ work
those for SVA1000x do not work.
What did I do that I missed?
Thanks

[tv84]

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>

Wrong move. BTW, move to the hack thread.

[cubitus]

Sorry 
I didn't understand what you said (I don't speak English well)

Wrong move. BTW, move to the hack thread.

[Bicurico]

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.

[cubitus]

it's ok, I succeeded

A big thank you to all 
" alt="" class="bbc_img" />