Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers

[RoV]

You should set the number of points before entering the calibration menu and not change it from there.
I recommend setting 10001 (the maximum possible), not 10000: this way you get a nicer frequency step.

[bicycleguy]

I can tell you that I performed the changes per this post (https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3563577/#msg3563577) and nothing else and it was painless.  Perhaps start over and go through that list.

That is exactly what I did, with several exceptions: I did not modify NSP_config_upgrade_info.xml to change the product ID's, since I had already crossflashed to the sva1032x, and even after mount -o remount,rw /usr/bin/siglent/firmdata0, I had to add write permission chmod o=rw NSP_sn_bandwidth.xml in order to modify it. maybe I should change it back to read only. I can't see how that would make any difference, but who knows?
It will not flash back to SSA3021_3032XP_V3.2.2.4.0.ADS so I cannot start over from scratch. I could try reflashing with the factory SVA1032X_V3.2.2.4.0.ADS, maybe something went wrong with the first time. That will likely remove telnet access, so I hope that telnet_11410.ads will get me back in.
Another difference from peter's summary, he says "serial number shows XXXX." however my serial number is shown in the system info screen, and starts with "SSA3....). Maybe I should change it to XXXX
Does anyone have a better idea?

update: I found a solution. I deleted /usr/bin/siglent/firmdata0/nsp_data_b1 once more, then sync && reboot. Voila! All options enabled and now the serial number shows as XXXXX. I do not know what happened the first time around. After my changes, I entered sync, but then cycled the power from the front panel. This time, I did sync && reboot. That is the only thing I can think of.
Many thanks to all who unlocked this gem! The built-in directional bridge works well over the full 3.2 Ghz band. After calibration, measuring S11 of a 20 dB pad reads 40 db return loss, just as it should. Clearly my unit has the internal reference cable that was missing on some units.

I too followed electr_peter's great instructions sort of(see below).  But like dirtcooker ended up with the same problem of nsp_data_b1 not being deleted.  Looking back at my terminal log, the first rename in part V step 5 in the firmdata0 directory

Code: [Select]

mv nsp_data_b1 nsp_data_b1xcaused a read only message I responded y to but result was a renamed copy and the original still there.  Turns out I had previously done an incorrect copy paste of

Code: [Select]

mount -o remount,rw /usr/bin/siglent in step 3 instead of

Code: [Select]

mount -o remount,rw /usr/bin/siglent/firmdata0Then I had difficulty deleting the file as it kept reappearing.  The solution was to use top to find the process number of the Aladdin process, kill it, do the correct mount remount, then rm nsp_data_b1, then sync, reboot... SUCCESS! YA!

To help others who might travel this path,  I did this on macOS Catalina.  I could not get telnet or PuTTy to work from MacPorts or Brew so I tried to use the Apple sanctioned nc as the secure telnet replacement.  Unfortunately nc and vi don't get along too good.  I tested vi by making a new file on the SA as in vi crap.  The problem is that the Esc key doesn't work to get back to command mode in vi!  So if you open a file you can't close it!  Had to apple-c which closed the telnet session.  Googling found many questions but no correct answers.  Experimenting found that whenever an esc is needed esc followed immediately with ctrl-d works.  So to get out esc ctrl-d :q!  Also all the command sequences and escapes end up all over the screen as it doesn't do telnet screen emulation(just the display, not the file).  Even moving the arrows requires the escape sequence and leaves artifacts.  Not really what you want to play with for something critical.  Perhaps nc could be setup to work correctly but I ended up coping all the files needing editing to the desktop and editing with BBedit, although TextEdit would have done.


So the bottom line is follow   https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3563577/#msg3563577   exactly, including using a proper telnet emulator.

Oh, thanks tv84, electr_peter, all the early nurds and brave testers and 'Linux for Dummies'!   I'm a linux geek soon to be a rf geek!

They keep forgetting the that everyone is a linux geek until access is lost (in a sealed machine)...

Quote of the month.... 

Edit:  Got PuTTy to work on macOS.  Reinstalled XQuartz and all was good.

[Bad_Driver]

Success! Another converted Xmas-SSA!
Thanks to all contributors, special thanks to TV84 and Electr_Peter!

Some small hick-ups during the process:

#1 Putty didn‘d work for me too, it established a FTP-connection on Port 21 to the SSA. I used instead Win10-TELNET without any issues.
#2 I followed step by step elctr_peter's guide and with my basic linux knowledge it was done in 40 min
#3 I also had to remount the USB-disk in Step V with
     (mount -o remount,rw /usr/bin/siglent/usr/mass_storage/U-disk0)
#4 after finishing the whole procedure bandwidth and licensing didn't work, before doing some nonsense on the console I went again thru
     this thread and found the advice of dirtcooker msg #1659 as described above too and voila! it's done!
     (deleting again /usr/bin/siglent/firmdata0/nsp_data_b1 once more, then sync && reboot)

Hope this helps other "improvers" in future.
Merry Xmas to you all around the world!

[EMCman]

Does anyone already have experience with cross-flashing a factory fresh SSA3021X+ which has newest FW V3.2.2.5.0?
Does procedure of https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3563577/#msg3563577 still work (of course with modification of SVA1032X 3.2.2.4.0 => SVA1032X 3.2.2.5.0)?

[Bad_Driver]

Is downgrading to firmware V3.2.2.4 possible? For me it seems the safest way.

[JNorton]

I apologize for opening this thread.  I have a SSA 3021x plus 3.2.2.4.0.  I cannot get telnet to connect after revising startup_app.sh.  Initially I had the line /sbin/telnetd -1 /bin/sh -p 10101 & after /usr/bin/siglent/Aladdin &.  I believe I have the startup_app.sh correct, but I cannot connect.  Here is the directory and the file.  And yes I am a Linux novice.

/usr/bin/siglent # ls -lsa
total 15196
     0 drwxrwxrwx    9 1000     1000          1320 Nov 21 16:51 .
     3 drwxrwxrwx    1 1000     232           3204 Jan  1  1970 ..
 14964 -rwxrwxrwx    1 root     root      15322628 Jul  7  2021 Aladdin
     0 drwxrwxrwx    8 1000     1000           704 Jul  7  2021 config
     4 -rwxrwxrwx    1 root     root          1078 Jul  7  2021 config_eth0.sh
     0 drwxrwxrwx    2 1000     1000          1904 Jul  7  2021 drivers
     0 drwxrwxrwx    3 1000     1000           752 Jul  9  2021 firmdata0
     0 drwxrwxrwx    2 1000     1000           160 Jan  8  2019 firmdata1
     0 drwxrwxrwx    2 root     root           688 Jul  7  2021 lib
    12 -rwxrwxrwx    1 root     root         12068 Jul  7  2021 lighttpd.conf
     0 drwxrwxrwx    2 1000     1000           232 Jan  8  2019 log
    68 -rwxrwxrwx    1 root     root         67085 Jul  7  2021 php.ini
     4 -rwxr-xr-x    1 root     root          2233 Dec 11 14:45 startup_app.sh
     4 -rwxrwxrwx    1 root     root            77 Jul  7  2021 startup_ftp.sh
     4 -rwxrwxrwx    1 root     root           482 Jul  7  2021 startup_vnc.sh
     0 drwxrwxrwx   10 1000     1000           904 Jan  1  2000 usr
     4 -rwxrwxrwx    1 root     root           490 Jul  7  2021 vdma_vnc.sh
    32 -rwxrwxrwx    1 root     root         29337 Jul  7  2021 vncserver
    96 -rwxrwxrwx    1 root     root         97611 Jul  7  2021 vsftpd


/usr/bin/siglent # cat startup_app.sh
#/bin/sh
echo "startup_app.sh   start++++++++++"


export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:$PATH
export LD_LIBRARY_PATH=/lib:/usr/lib:$LD_LIBRARY_PATH
#echo "qt path config"
export QT_PATH_ROOT=/opt/qt
export LD_LIBRARY_PATH=$QT_PATH_ROOT/lib:$QT_PATH_ROOT/lib/ts:$LD_LIBRARY_PATH
export QT_PLUGIN_PATH=$QT_PATH_ROOT/plugins
export FONTCONFIG_PATH=$QT_PATH_ROOT/share
export QT_QPA_PLATFORM=linuxfb:fb=/dev/fb0:size=1024x600:mmsize=223x125:rotation=0
export QT_QPA_GENERIC_PLUGINS=evdevtouch:/dev/input/event0
export QT_QPA_EVDEV_TOUCHSCREEN_PARAMETERS=/dev/input/event0

export LD_LIBRARY_PATH=/usr/bin/siglent:$LD_LIBRARY_PATH
export LANG=en_US.utf8

#for vnc upgrade ads residual+++++++++++++++++++++++++++++

echo "rm -f /usr/bin/siglent/usr/*.ADS"
rm -f /usr/bin/siglent/usr/*.ADS
rm -f /usr/bin/siglent/usr/*.CFG
rm -f /usr/bin/siglent/usr/*.ads
rm -f /usr/bin/siglent/usr/*.cfg
sync

#for vnc upgrade ads residual+++++++++++++++++++++++++++++

#for ads upgrade app, (space dependent)
if [ -f /usr/bin/siglent/usr/backup/upgrade_app1.sh ]; then
        mount -o remount,rw /usr/bin/siglent
        /usr/bin/siglent/usr/backup/upgrade_app1.sh
        echo "/usr/bin/siglent/usr/backup/upgrade_app1.sh"

        rm /usr/bin/siglent/usr/backup/upgrade_app1.sh -rf
        echo "rm /usr/bin/siglent/usr/backup/upgrade_app1.sh -rf"

        rm /usr/bin/siglent/usr/usr/upgrade/* -rf
        echo "rm /usr/bin/siglent/usr/usr/upgrade/* -rf"
        mount -o remount,ro /usr/bin/siglent
        sync
fi

#for udisk upgrade , no firmdata0
if [ -d /usr/bin/siglent/usr/backup/config ]; then
        mount -o remount,rw /usr/bin/siglent/firmdata0
        cp -rpf /usr/bin/siglent/usr/backup/config/* /usr/bin/siglent/firmdata0/
        echo "cp -pf /usr/bin/siglent/usr/backup/config/* /usr/bin/siglent/firmdata0/"
        sync
        mount -o remount,rw /usr/bin/siglent
        rm /usr/bin/siglent/usr/backup/config -r
        mount -o remount,ro /usr/bin/siglent
        sync
        mount -o remount,ro /usr/bin/siglent/firmdata0
fi

#for upgrade ads residual+++++++++++++++++++++++++++++
if [ -d /usr/bin/siglent/usr/usr/upgrade ]; then
        rm /usr/bin/siglent/usr/usr/upgrade -rf
fi

/usr/bin/siglent/config_eth0.sh
sleep 1
portmap &

/sbin/telnetd -1 /bin/sh -p 10101 &
/usr/bin/siglent/Aladdin &

echo "startup_app.sh   end++++++++++"

[tubularnut]

After /sbin/telnetd, it should be a a lowercase L (l) not a One (1)

Code: [Select]

/sbin/telnetd -l /bin/sh -p 10101  &


[JNorton]

Thank you.  I have looked at this repeatedly for over two months!  Once again thank you.

[bicycleguy]

After /sbin/telnetd, it should be a a lowercase L (l) not a One (1)

Code: [Select]

/sbin/telnetd -l /bin/sh -p 10101  &


Good eye !

[JNorton]

Another successful upgrade.  Thanks to tv84 and electr_peter.  I also found khutch004 comments helpful regarding VI commands versus putty commands.

[benjamin73]

Hello all. I am experiencing issues today with my 3021X, which has worked perfectly for 3 years now.

Here is a link to a video:
https://twitter.com/PatrickTopalof/status/1490014110825734150?s=20&t=pyb8LwUMY7Hn-jfqPgD9-Q

It keeps blinking and there is no action from the keyboard 

Would you have any idea?

[Bicurico]

That doesn't look like a software problem.
Hopefully it is just a bad contact between some connector.
If under warranty, talk to seller.
Otherwise it wouldn't hurt to open it and check all connectors.
Good luck!

[benjamin73]

So I will open it  Thank you!

[baldurn]

I managed to upgrade my SSA3032X-R to SSA3075X-R in "pro mode" (all options enabled). See screenshot. Thanks to tv84 and others for figuring this out. The upgrade was not hard but finding the information was. Had to guess a lot but in the end I mostly just needed to delete the license portion of one xml file and rename two other files.

Also thanks to Siglent for not making this harder. You did not lose any money here as I could not afford the more expensive version anyway. I also have no real need for it but just want to fool around. Never the less the possibility of a hack was what made me invest the extra to get this expensive (for me) instrument.

[electr_peter]

Does SSA3032X-R, SSA3050X-R and SSA3075X-R share the same HW internally? I was under impression that with more than double the frequency some HW has to change.

[Bicurico]

Those three do share the same hardware.

[Bad_Driver]

Following the advice of TV84 in the SDG2000X thread I removed the old hack and used the well known Python-script for a licensing of the bandwidth option for my SDG2000x.

Are there any news to do the same for the "improved" SSA3000X+ and to overcome the issues with SNAs without serial number? Is the Python-script working for SVA option licensing?

Thanks in advance!

[uouox]

Following the advice of TV84 in the SDG2000X thread I removed the old hack and used the well known Python-script for a licensing of the bandwidth option for my SDG2000x.

Are there any news to do the same for the "improved" SSA3000X+ and to overcome the issues with SNAs without serial number? Is the Python-script working for SVA option licensing?

Thanks in advance!

not the same script but very similar

[Bad_Driver]

Can you share some details more with us? Thanks!

[uouox]

Can you share some details more with us? Thanks!

1. You have root access of the system.
2. There is a GDB server in the system.
3. The xml has the hint for the option tag.
4. You have the keygen algorithm.

I believe that is enough.

[Bad_Driver]

Sorry but I tried to fiddle with your hints in the system but last time I did some debugging was around 1980
with Z80 assembler code 

I‘m not able to do this by myself, can someone be so kind and provide some support?

Can it be done with a crossflashed SSA or only with the SSA as it was delivered?
Thanks in advance!

[DL4JY]

Hello,
as we are not getting any further "guidance", I will summarize what I understood- not being a programmer even though I owe a TRACE80 in-circuit debugger (hint for the bad trabbi driver)

1. You have root access of the system. 
yes, this is true - with the help of this thread
2. There is a GDB server in the system.
yes, looking into the files, there is a GDB-Server in the files - now the task is to start it and debug finding the hash key - my layman's understanding is to fill the hash key found by setting a break point to the right program step in the VNA software - into the python script of the SDS2000 oscilloscope.
(https://gist.githubusercontent.com/Lauszus/c8d3f593b676a3e2ab29415e81405b6a/raw/215d7e7442158626d062c0370d40ca7f836c4cf1/main.py) 
3. The xml has the hint for the option tag.
One needs to examine an initial .xml file to find the option tag for the options.
4. You have the keygen algorithm.
see python file

To my understanding you need to give the VNA first of all again a serial number - with doing that all options would be removed.
Then you need to start the debugging with GDB-server and find the hashkey (which I believe is the same for all VNAs).
The modified SDS2000 script (new hash key and option found in xml) will create a key you can enter into the VNA.

This is all my speculation, it would be great if one of guys knowing the truth could comment on my ideas and help to proceed - how to start the GDBserver - where to set a breakpoint, how to extract the hash key, what option to use and is the python script attached the right one to modify ?

best regards,

Juergen

[devincody]

Thought that I would share my notes on the conversion since purchasing an SSA3021X+ was a huge investment and having additional information would have made me feel like making the purchase was less of a gamble.

I found this thread beginning of March, purchased the scope on April 5th from Amazon, and upon delivery, I immediately converted it. The process was largely painless, but sifting through the thread for cross-validated information was time-consuming. Ultimately, I followed a combination of advice from TV84 and electr_peter. The firmware that came with my scope was 3.2.2.4.0.

I made backups of the firmware as described in Section I electr_peter's post:
https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3563577/#msg3563577

I then did a "direct cross-flash" per TV84's post:
https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3564805/#msg3564805

TV84 mentions that you now need to do the changes mentioned in Section V of electr_peter's post (see above). However, to get access to telnet to make those changes, you need to launch the fake upload "SVA1000X_telnet_11410.ADS" from your USB stick as described and provided in Section IV. User msquared's post is similar to the experience I had and I'm glad I found it since it assured me that my issues were solvable:
https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3569773/?topicseen#msg3569773

Obvious thanks goes to TV84, electr_peter, msquared

[karl11]

Hello I have a huge problem.
My SSA3021+ was on SW 3.2.2.5.0 i tried to logon with telnet  Hack SVA1000X_telnet_11410.ads this works.
So i replaced
   <upgrade_static_id>11411</upgrade_static_id>
with
   <upgrade_static_id>11403</upgrade_static_id>
And reboot.
Then I tried to install SVA SVA1032X_V3.2.2.4.0_11411 whitch fails. I can not reach the SSA with telnet anymore i tried SVA1000X_telnet_11410 and SSA3000X+_telnet_11411 again with no connection. I there a way to bring back the restored files ? Can anybody help me ?

[tymm]

if the unit is generally working, can you try:
- telnet to port 5024 (SCPI) and send the command 'DEBTTT' (this should start up a telnet server on port 23)
- telnet to port 23 and login as 'root', pw 'ding1234'

hopefully that gets you in and you can sort things out from there