Author Topic: Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers  (Read 625883 times)

ronjovie and 4 Guests are viewing this topic.

Offline benishor

  • Contributor
  • Posts: 19
  • Country: ro
Re: Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers
« Reply #1925 on: June 21, 2022, 09:22:34 am »
I am becoming more and more convinced that I do not have a problem with the SA per se but with the connectors/cables. In the following pictures I used a short BNC cable from a HP equipment to pass through the TG to the SA and I measured the TG response on the full span at 4 attenuation levels: 10dB, 20dB, 30dB and 40dB: https://imgur.com/a/Th6PtaD

The results are well within the specs which leads me to think that the cable I used before is really crappy. I ordered some UKitSSA3X and we will see how that performs. The point raised by RoV regarding flux is valid though; I used noclean flux and apparently only cleaned the board around the chip. I did not know that flux is conductive at high frequencies. I will re-open the unit and clean the chip as best I can with isopropyl alcohol and see whether it makes a difference.

All being said, the insertion loss graph for the HMC1118 shows a spread of ~0.3dB between 0 and 3GHz so the simple change of this switch should not make too much of a difference with respect to the original calibration.

All the best,
Adrian
 

Offline John317

  • Newbie
  • Posts: 8
  • Country: us
Re: Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers
« Reply #1926 on: June 23, 2022, 07:01:42 pm »
Hi All,

First, thanks for all the hard work you folks have done on this forum to enhance the SSA3021X+. I recently got one to further debug ham radios like the Icom 7000 on the bench now. It is amazing using SAs over oscilloscopes … I wish I did not wait this long to get one as the decoding features are powerful. Anyway, after reading a ton here, I am looking to also enhance mine, but in a way not many seem to have gone.

I read thru the full threads for the process for taking it to a SVA and feel I could get there, but I am not sure I want to quite go to the SVA. Mainly due to the loss of serial number, developer mode stuff, and the challenge of reflashing the nand back if I wanted to undo it.

At this point, I'm comfortable adding the additional feature sets via option codes as well as opening it up to 3.2Ghz (Kind of like what I did to my SDS2352X-E). Unfortunately, I did not see a lot of folks going this direction so after this intensive research I started to trailblaze this path.

I have gone as far as:
  • Nand backups
  • Telnet enabled via the SPCI commands (I have version 3.2.2.4.0)
  • Exporting Aladdin and dissecting it with various developer/debugging tools
  • Exporting and investigating config files
  • Investigating SSA file system
  • Limited GDB debugging on Aladdin (I am not the best here)

I believe I have found the hash key in Aladdin, (funny the coincidences… 😉) and have tried to modify the python script used for SDS models without success. I did try many combinations for model and feature sets (using the NSP_sn_bandwidth.xml values). I went even as far as writing code to list all possibilities in order to match the TG licenses found in that file as the reference. No Joy.

This is where I come to you folks for any guidance you may have.
  • Has anyone successfully gone my preferred route of increasing the BW to 3.2Ghz and adding all the features? Any clues to the proper model and or feature “codes”?
  • Anyone gotten the SVA conversion to retain their SN and remove the developer stuff? (If I can’t go about it my preferred way)
  • Is reverting from SVA as scarry as the nand write could be?

Sorry for the long post, but truly value your collective input.

John
 
The following users thanked this post: Marcel G, Bad_Driver, DL4JY

Offline tautech

  • Super Contributor
  • ***
  • Posts: 28371
  • Country: nz
  • Taupaki Technologies Ltd. Siglent Distributor NZ.
    • Taupaki Technologies Ltd.
Re: Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers
« Reply #1927 on: June 28, 2022, 11:26:44 pm »
New firmware for SSA3000X Plus models is available.

Version: V3.2.2.5.1R1
https://int.siglent.com/upload_file/zip/firmware/Spectrum_analyzer/SSA3000X%20Plus_V3.2.2.5.1R1_EN.zip
26 MB

Release notes:
Notice:
This firmware must be upgraded from V3.2.2.4.0 or later. If your analyzer has an earlier version, please update to V3.2.2.4.0 first and then proceed to update to the latest version.
 
Improvements:
Optimize the Ref level and Att couple
Add SCPI commands in MA Mode
•READ:ADEMod:AVG?
•[:SENSe]:ADEMod:FM:DEVI?
•[:SENSe]:ADEMod:FM:DRIFt?
•[:SENSe]:BWIDth[:RESolution]
•[:SENSe]:BWIDth[:RESolution]?
•[:SENSe]:BWIDth:EQLPf
•[:SENSe]:BWIDth:EQLPf?
•CALCulate:MARKer#:PTPeak
Add .trc file in EMI Mode
Add .lic file auto scan
 
Solved Issues:
Fix pi/4 DPSK和pi/8 DPSK decode errors in MA mode
Fix fft frequency error in narrow span in SA mode
Fix trace avg calculation error in SA mode
Fix the zero sweep type when fft in SA mode
Avid Rabid Hobbyist
Siglent Youtube channel: https://www.youtube.com/@SiglentVideo/videos
 
The following users thanked this post: benishor

Offline tossu

  • Contributor
  • Posts: 21
  • Country: 00
Re: Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers
« Reply #1928 on: June 29, 2022, 03:05:21 pm »
Has anyone successfully gone my preferred route of increasing the BW to 3.2Ghz and adding all the features? Any clues to the proper model and or feature “codes”?
Yes. All of the codes can be found in the Aladdin executable. The more interesting ones are probably 3032 and ALL.

Anyone gotten the SVA conversion to retain their SN and remove the developer stuff? (If I can’t go about it my preferred way)
You shouldn't lose the SN unless you activate the "pro mode" by manually removing the license file. It's not even required for the SVA conversion.

Is reverting from SVA as scarry as the nand write could be?
I should be as easy as doing a reverse conversion from SVA to SSA. That is, restore the original SSA config files and upgrade to SSA firmware. I haven't tested it so standard disclaimers apply.

It's a good idea to have another backup in a format that makes restoring individual files easier. That way you shouldn't need to restore the nand unless you lock yourself out completely.
 
The following users thanked this post: John317

Offline DL4JY

  • Regular Contributor
  • *
  • Posts: 67
  • Country: de
Re: Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers
« Reply #1929 on: June 30, 2022, 04:56:37 pm »
New firmware for SSA3000X Plus models is available.

Version: V3.2.2.5.1R1


thanks, are there any negativ implications to modded SAs / VNAs in Pro mode ?

cheerio

Juergen
 

Offline zkf0100007

  • Contributor
  • Posts: 18
  • Country: cn
Re: Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers
« Reply #1930 on: July 03, 2022, 01:31:56 pm »
The former edtion SSA3021X was built with SPARTAN 6 and AM335X as shown in the teardown video made by Dave.
I also bought one SSA3021X last year, it was built with only one ZYNQ FPGA.

 

Offline zkf0100007

  • Contributor
  • Posts: 18
  • Country: cn
Re: Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers
« Reply #1931 on: July 04, 2022, 11:05:52 am »
I want to upgrade SSA3021X to SVA, so I followed  electr_peter's instruction in Reply #1620.
When I run SSA3000X+_backup_11411.ADS, there is no backup files in my U-disk.
In order to see what happned, I connect the debug UART to PC, the UART output is shown as follws:

Code: [Select]
adpt_nspadapter_msg_deal::NSP_ADPT_MSG_USB_UPGRADE--------------/usr/bin/siglent/usr/mass_storage/U-disk0/SSA3000X+_backup_11411.ADS7777777777777777777777777
Archive:  /usr/bin/siglent/usr/usr/upgrade/config.zip
  inflating: siglent.jpg
  inflating: upgrade.sh
cp: can't create directory '/usr/bin/siglent/usr/mass_storage/U-disk0/firmdata0/': Read-only file system
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
/usr/bin/siglent/usr/mass_storage/U-disk0/mtd0.bin: Read-only file system
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
/usr/bin/siglent/usr/mass_storage/U-disk0/mtd1.bin: Read-only file system
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
/usr/bin/siglent/usr/mass_storage/U-disk0/mtd2.bin: Read-only file system
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
/usr/bin/siglent/usr/mass_storage/U-disk0/mtd3.bin: Read-only file system
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
/usr/bin/siglent/usr/mass_storage/U-disk0/mtd4.bin: Read-only file system
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
/usr/bin/siglent/usr/mass_storage/U-disk0/mtd5.bin: Read-only file system
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
/usr/bin/siglent/usr/mass_storage/U-disk0/mtd6.bin: Read-only file system
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
/usr/bin/siglent/usr/mass_storage/U-disk0/mtd7.bin: Read-only file system
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
/usr/bin/siglent/usr/mass_storage/U-disk0/mtd8.bin: Read-only file system
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
/usr/bin/siglent/usr/mass_storage/U-disk0/mtd9.bin: Read-only file system
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
/usr/bin/siglent/usr/mass_storage/U-disk0/mtd10.bin: Read-only file system
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 4
/usr/bin/siglent/usr/mass_storage/U-disk0/mtd11.bin: Read-only file system
/dev/mtd12: No such file or directory
/dev/mtd13: No such file or directory
/dev/mtd14: No such file or directory
/dev/mtd15: No such file or directory
cp: can't create '/usr/bin/siglent/usr/mass_storage/U-disk0/memdump': Read-only file system
The system is going down NOW!
Sent SIGTERM to all processes
Sent SIGKILL to all processes
Requesting system reboot
▒   48.587150] reboot: Restarting system
 

Offline tv84

  • Super Contributor
  • ***
  • Posts: 3221
  • Country: pt
Re: Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers
« Reply #1932 on: July 04, 2022, 06:35:32 pm »
It seems the USB disk now is RO. I'll have to make it RW in the dump script.
 

Offline jhormilla

  • Contributor
  • Posts: 18
  • Country: us
Re: Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers
« Reply #1933 on: July 04, 2022, 10:56:29 pm »
I have a SSA 3021X (Non plus) FW 1.3.9.8, any info to liberate would be appreciated, I must have spent 2+ hours so far reading through posts and most of what I find is for the plus version. Not sure where to start.
 

Offline zkf0100007

  • Contributor
  • Posts: 18
  • Country: cn
Re: Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers
« Reply #1934 on: July 05, 2022, 01:02:59 am »
Thanks for your reply!
Will you post a new vesion 'SSA3000X+_backup_11411.ADS' which support U-disk RW?
 

Offline tubularnut

  • Regular Contributor
  • *
  • Posts: 225
  • Country: gb
Re: Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers
« Reply #1935 on: July 05, 2022, 07:25:44 am »
I have a SSA 3021X (Non plus) FW 1.3.9.8, any info to liberate would be appreciated, I must have spent 2+ hours so far reading through posts and most of what I find is for the plus version. Not sure where to start.

Have you read this topic?
https://www.eevblog.com/forum/testgear/hack-of-sigllent-spectrum-analyzer-ssa3021x/
 

Offline benishor

  • Contributor
  • Posts: 19
  • Country: ro
Re: Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers
« Reply #1936 on: July 05, 2022, 08:00:53 am »
New firmware for SSA3000X Plus models is available.

Version: V3.2.2.5.1R1


thanks, are there any negativ implications to modded SAs / VNAs in Pro mode ?

cheerio

Juergen

I just performed the upgrade from SVA1032X_V3.2.2.4.0 and for me it worked flawlessly. Options are still enabled and everything seems to work as it should. I had to issue a reset and clear after the update though. As a test, I tried to downgrade back to 3.2.2.4.0 but I couldn't. Maybe it's just me or perhaps this is a limitation.

73 de Adrian, YO6SSW
 
The following users thanked this post: DL4JY

Offline zkf0100007

  • Contributor
  • Posts: 18
  • Country: cn
Re: Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers
« Reply #1937 on: July 05, 2022, 03:25:14 pm »
It seems the USB disk now is RO. I'll have to make it RW in the dump script.
How to make U-disk RW in the dump script?
Thanks!
 

Offline jhormilla

  • Contributor
  • Posts: 18
  • Country: us
 

Offline uouox

  • Newbie
  • Posts: 6
  • Country: us
Re: Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers
« Reply #1939 on: July 07, 2022, 05:16:53 pm »
Well, I simply cannot apply 3.2.2.5.1 fw to 3.2.2.5.0 on a modded SSA3000plus. It stops during update but fortunately the spectrum analyzer still work after power cycle.
 

Offline NCG

  • Contributor
  • Posts: 45
  • Country: ee
Re: Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers
« Reply #1940 on: July 08, 2022, 07:56:30 pm »
Running out of space maybe? For me V3.2.2.5.1R1 update worked without problems.
« Last Edit: July 08, 2022, 08:03:47 pm by NCG »
 

Offline bicycleguy

  • Frequent Contributor
  • **
  • Posts: 265
  • Country: us
Re: Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers
« Reply #1941 on: July 09, 2022, 06:12:12 pm »
SVA1000X_V3.2.2.5.1R1.ADS on an updated SSA3021X+ worked fine for me.

Seems to have fixed a recurring  issue I've had since 3.2.2.4.0.r2 that I meant to post about.
The issue was that if I shut down in VNA mode and then restart the calibration would be messed up even though it showed 'Cor'.  No amount of recalibrating, changing cal kit, adjusting span, points ect would fix it.  Correction on/off seemed to be opposite.  The easy fix (when I remembered it) was just to change mode to SA then change it back to VNA.  This was with 'Power On'=Last and Preset=Def.  Was going to post a youtube but now it's fixed.

Spoke to soon.  As I'm writing this it happened again.  Not sure what I did different.

And now something new.  The last restart caused a freeze with the Siglent text only.  Telnet/top showed Aladdin on top but no buttons are responding.  After about 2 minutes it started running normally again. :-//
 

Offline bicycleguy

  • Frequent Contributor
  • **
  • Posts: 265
  • Country: us
Re: Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers
« Reply #1942 on: July 09, 2022, 08:00:16 pm »
SVA1000X_V3.2.2.5.1R1.ADS on an updated SSA3021X+ has now crashed for me.  I don't know if upgrading is a good idea.

It worked for about 5 or 6 startups then started freezing on startup for longer and longer.  Now never starts, just Siglent logo.  Can telnet.  Shows Aladdin 50% cpu.

what next?
 

Online Bicurico

  • Super Contributor
  • ***
  • Posts: 1714
  • Country: pt
    • VMA's Satellite Blog
Re: Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers
« Reply #1943 on: July 09, 2022, 08:11:47 pm »
Telnet
df -k
Check if Filesystem has free space
Check if the siglent folder has ecomb and Alladin executável
 

Offline bicycleguy

  • Frequent Contributor
  • **
  • Posts: 265
  • Country: us
Re: Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers
« Reply #1944 on: July 09, 2022, 08:23:57 pm »
thanks for the help!
Code: [Select]
/usr/bin/siglent # ls -l
total 13760
-rwxrwxrwx    1 root     root      13856588 Jul  9 09:32 Aladdin
drwxrwxrwx    8 1000     1000           704 Jul  9 09:32 config
-rwxrwxrwx    1 root     root          1078 Jul  9 09:32 config_eth0.sh
drwxrwxrwx    2 1000     1000          1904 Jul  9 09:32 drivers
drwxrwxrwx    3 1000     1000           752 Jul  9 09:32 firmdata0
drwxrwxrwx    2 1000     1000           160 Jan  8  2019 firmdata1
drwxrwxrwx    2 root     root           688 Jul  9 09:32 lib
-rwxrwxrwx    1 root     root         12068 Jul  9 09:32 lighttpd.conf
drwxrwxrwx    2 1000     1000           232 Jan  8  2019 log
-rwxrwxrwx    1 root     root         67085 Jul  9 09:32 php.ini
-rwxrwxrwx    1 root     root          2231 Jul  9 09:50 startup_app.sh
-rwxrwxrwx    1 root     root            77 Jul  9 09:32 startup_ftp.sh
-rwxrwxrwx    1 root     root           482 Jul  9 09:32 startup_vnc.sh
drwxrwxrwx   10 1000     1000           984 Dec  9  2021 usr
-rwxrwxrwx    1 root     root           490 Jul  9 09:32 vdma_vnc.sh
-rwxrwxrwx    1 root     root         29337 Jul  9 09:32 vncserver
-rwxrwxrwx    1 root     root         97611 Jul  9 09:32 vsftpd
/usr/bin/siglent # df -k
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root                63152     63152         0 100% /
devtmpfs                 69852         0     69852   0% /dev
none                     78140         4     78136   0% /tmp
ubi1_0                   30388     20860      9528  69% /usr/bin/siglent
ubi2_0                    5848       196      5652   3% /usr/bin/siglent/firmdata0
ubi3_0                    5848        24      5824   0% /usr/bin/siglent/log
ubi0_0                   84752      9320     75432  11% /usr/bin/siglent/usr
/usr/bin/siglent #
 

Offline bicycleguy

  • Frequent Contributor
  • **
  • Posts: 265
  • Country: us
Re: Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers
« Reply #1945 on: July 09, 2022, 08:24:54 pm »
Code: [Select]
Mem: 95028K used, 61256K free, 4K shrd, 12424K buff, 36716K cached
CPU: 50.3% usr  0.5% sys  0.0% nic 49.2% idle  0.0% io  0.0% irq  0.0% sirq
Load average: 1.03 0.96 0.56 5/77 1119
  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND
  688     1 root     S     287m187.7   1 50.6 /usr/bin/siglent/Aladdin
 1115   914 root     R     2092  1.3   0  0.1 top
  880     1 root     S    21588 13.7   0  0.0 /usr/bin/siglent/vncserver
  891   890 root     S    12888  8.2   0  0.0 /usr/bin/php-cgi -c /usr/bin/siglent/php.ini
  892   891 root     S    12888  8.2   0  0.0 /usr/bin/php-cgi -c /usr/bin/siglent/php.ini
  691     1 root     S     4868  3.1   1  0.0 /sbin/telnetd -l /bin/sh -p 10101
  890     1 root     S     2320  1.4   0  0.0 /usr/sbin/lighttpd -f /usr/bin/siglent/lighttpd.conf
  738     1 root     S     2132  1.3   0  0.0 /usr/bin/siglent/vsftpd
  914   691 root     S     2092  1.3   1  0.0 /bin/sh
  887     1 root     S     2092  1.3   1  0.0 /sbin/getty -L ttyPS0 115200 vt100
    1     0 root     S     2088  1.3   0  0.0 {linuxrc} init
  741     1 1        S     2000  1.2   0  0.0 portmap
  205     2 root     SW       0  0.0   0  0.0 [kworker/0:1]
   56     2 root     SW       0  0.0   1  0.0 [kworker/1:1]
    7     2 root     SW       0  0.0   0  0.0 [rcu_preempt]
  455     2 root     SW       0  0.0   0  0.0 [spi1]
   17     2 root     SW       0  0.0   0  0.0 [kworker/u4:1]
  574     2 root     SW<      0  0.0   0  0.0 [kworker/0:1H]
  575     2 root     SW<      0  0.0   1  0.0 [kworker/1:1H]
  803     2 root     SW       0  0.0   0  0.0 [kworker/u4:5]
  582     2 root     SW       0  0.0   0  0.0 [ubi_bgt1d]
  586     2 root     SW       0  0.0   0  0.0 [ubi_bgt2d]
  594     2 root     SW       0  0.0   0  0.0 [ubi_bgt0d]
    2     0 root     SW       0  0.0   0  0.0 [kthreadd]
    3     2 root     SW       0  0.0   0  0.0 [ksoftirqd/0]
    4     2 root     SW       0  0.0   0  0.0 [kworker/0:0]
    5     2 root     SW<      0  0.0   0  0.0 [kworker/0:0H]
    8     2 root     SW       0  0.0   0  0.0 [rcu_sched]
    9     2 root     SW       0  0.0   0  0.0 [rcu_bh]
   10     2 root     SW       0  0.0   0  0.0 [migration/0]
   11     2 root     SW       0  0.0   1  0.0 [migration/1]
   12     2 root     SW       0  0.0   1  0.0 [ksoftirqd/1]
   14     2 root     SW<      0  0.0   1  0.0 [kworker/1:0H]
   15     2 root     SW<      0  0.0   1  0.0 [khelper]
   16     2 root     SW       0  0.0   0  0.0 [kdevtmpfs]
   19     2 root     SW<      0  0.0   0  0.0 [perf]
  202     2 root     SW<      0  0.0   1  0.0 [writeback]
  206     2 root     SW<      0  0.0   0  0.0 [bioset]
  208     2 root     SW<      0  0.0   1  0.0 [kblockd]
  239     2 root     SW<      0  0.0   0  0.0 [edac-poller]
  327     2 root     SW<      0  0.0   0  0.0 [rpciod]
  341     2 root     SW       0  0.0   1  0.0 [kswapd0]
  342     2 root     SW       0  0.0   0  0.0 [fsnotify_mark]
  343     2 root     SW<      0  0.0   1  0.0 [nfsiod]
 

Offline bicycleguy

  • Frequent Contributor
  • **
  • Posts: 265
  • Country: us
Re: Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers
« Reply #1946 on: July 09, 2022, 08:29:48 pm »
When I power up the Siglent logo shows for about 5 seconds, then it looks like it reboots and the logo appears again but stays there continuously.  Holding the power button about 10 seconds will turn it off.
 

Offline bicycleguy

  • Frequent Contributor
  • **
  • Posts: 265
  • Country: us
Re: Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers
« Reply #1947 on: July 10, 2022, 03:05:14 pm »
New firmware for SSA3000X Plus models is available.

Version: V3.2.2.5.1R1
https://int.siglent.com/upload_file/zip/firmware/Spectrum_analyzer/SSA3000X%20Plus_V3.2.2.5.1R1_EN.zip
  ...
Improvements:
...
Add .lic file auto scan
...
what's the .lic file for?
New firmware for SSA3000X Plus models is available.

Version: V3.2.2.5.1R1

thanks, are there any negativ implications to modded SAs / VNAs in Pro mode ?
cheerio
Juergen

I just performed the upgrade from SVA1032X_V3.2.2.4.0 and for me it worked flawlessly. Options are still enabled and everything seems to work as it should. I had to issue a reset and clear after the update though. As a test, I tried to downgrade back to 3.2.2.4.0 but I couldn't. Maybe it's just me or perhaps this is a limitation.

73 de Adrian, YO6SSW

Mine was working too.  Then I shut down and restarted many times and got longer and longer reboots.  I never did the 'reset and clear'.  Today I found this rather large 'last_config.xml' file.  Maybe that's my problem.  Any thoughts anyone?
Code: [Select]
/usr/bin/siglent/usr/config # ls -l
total 7844
drwxrwxrwx    5 root     root           352 Jul  9 22:28 Limits
-rw-r--r--    1 root     root            53 Jan  1  1970 NSP_config.xml
-rw-r--r--    1 root     root            59 Jan  1  1970 NSP_default.xml
-rw-r--r--    1 root     root            53 Jan  1  1970 NSP_user.xml
-rw-r--r--    1 root     root           393 Jul 10 07:44 NSP_usr_system_info.xml
-rw-r--r--    1 root     root           407 Jul  9 16:24 dev_system_info.xml
-rw-r--r--    1 root     root         61782 Jul  6 17:39 enh_rsp_calib.bin
-rw-r--r--    1 root     root         81702 Jul  6 17:39 enh_rsp_calib_log.bin
drwxrwxrwx    3 root     root           392 Jul  9 22:28 help
-rw-r--r--    1 root     root       7775999 Jul  9 17:01 last_config.xml
drwxrwxrwx    2 1000     1000           160 Jan  8  2019 mode
-rw-r--r--    1 root     root         26278 Jul  5 17:21 usr_vna_calib.bin
-rw-r--r--    1 root     root          4918 Jul  6 17:39 usr_vna_o_calib.bin
-rw-r--r--    1 root     root         17702 Jul  6 17:39 usr_vna_o_calib_log.bin
-rw-r--r--    1 root     root          4918 Jul  6 17:39 usr_vna_s_calib.bin
-rw-r--r--    1 root     root         17702 Jul  6 17:39 usr_vna_s_calib_log.bin
/usr/bin/siglent/usr/config #
 

Offline tv84

  • Super Contributor
  • ***
  • Posts: 3221
  • Country: pt
Re: Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers
« Reply #1948 on: July 10, 2022, 03:16:40 pm »
.lic file should be license files.

last_config.xml is indeed strange... Can you share it?

Do you have your SSA properly licensed or with S/N "XXXXXXXXX"?
 

Offline bicycleguy

  • Frequent Contributor
  • **
  • Posts: 265
  • Country: us
Re: Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers
« Reply #1949 on: July 10, 2022, 03:27:35 pm »
.lic file should be license files.

last_config.xml is indeed strange... Can you share it?

Do you have your SSA properly licensed or with S/N "XXXXXXXXX"?
The release note said it's adding .lic auto scan.  Whats that mean for us?

here is the 'last_config.xml' contents minus the last 8meg ^-^
Code: [Select]
/usr/bin/siglent/usr/config # less last_config.xml
<?xml version="1.0" encoding="utf-8"?>
<configuration mode="Analyzer">
      <Analyzer>
              <FREQ min_start="0" def_start="0" start="0" stop="3200000000" step="320000000" step_auto="true" axis_typ
e="1" offset="0" />
              <BW rbw="12" vbw="12" vrr="6" rbw_auto="true" vbw_auto="true" avg_type="0" />
              <SWEEP time="627200" rule="0" time_auto="true" continuous="true" times="1" mode="0" speed_coeff="3" unca
l="false" fft="false" min_dwell_time="0" max_dwell_time="0" def_dwell_time="0" dwell_time="0" />
              <AMPT min_ref="-200" max_ref="30" def_ref="0" ref="10" ref_offset="0" scale_div="10" line_value="0" att=
"30" att_auto="true" scale_type="0" unit="0" input="50" preamp="false" line_on="false" correctionFun="false">
                      <correction0 on="false" len="0" />
                      <correction1 on="false" len="0" />
                      <correction2 on="false" len="0" />
                      <correction3 on="false" len="0" />
              </AMPT>
              <TRACE math="0" input_x="0" input_y="1" output_z="2" power_diff_offset="0" power_sum_offset="0" log_offs
et="0" log_diff_ref="0">
                      <TRACE1 type="1" state="5" detect="0" avg_times="10" />
                      <TRACE2 type="5" state="0" detect="4" avg_times="20" />
                      <TRACE3 type="5" state="0" detect="4" avg_times="100" />
                      <TRACE4 type="5" state="0" detect="4" avg_times="50" />
              </TRACE>
              <MARKER table_on="false">
                      <MARKER1 type="0" trace="0" fn_type="0" ndb_value="-3" related="1" readout="0" freqcounter_on="f
alse" xAxis="10000008" yAxis="-11.738482890941221" />
                      <MARKER2 type="0" trace="1" fn_type="0" ndb_value="-3" related="2" readout="0" freqcounter_on="f
alse" xAxis="119960000" yAxis="-74.846999783325202" />
                      <MARKER3 type="0" trace="0" fn_type="0" ndb_value="-3" related="3" readout="0" freqcounter_on="f
alse" xAxis="51320000" yAxis="0" />
                      <MARKER4 type="0" trace="0" fn_type="0" ndb_value="-3" related="4" readout="0" freqcounter_on="f
alse" xAxis="0" yAxis="0" />
                      <MARKER5 type="0" trace="0" fn_type="0" ndb_value="-3" related="5" readout="0" freqcounter_on="f
alse" xAxis="0" yAxis="0" />
                      <MARKER6 type="0" trace="0" fn_type="0" ndb_value="-3" related="6" readout="0" freqcounter_on="f
alse" xAxis="0" yAxis="0" />
                      <MARKER7 type="0" trace="0" fn_type="0" ndb_value="-3" related="7" readout="0" freqcounter_on="f
alse" xAxis="0" yAxis="0" />
                      <MARKER8 type="0" trace="0" fn_type="0" ndb_value="-3" related="0" readout="0" freqcounter_on="f
alse" xAxis="0" yAxis="0" />
              </MARKER>
              <PEAK type="0" threshold="-140" excursion="15" table_on="false" sort_by="0" continuous1="false" continuo
us2="false" continuous3="false" continuous4="false" continuous5="false" continuous6="false" continuous7="false" continuo
us8="false" />
              <TRIG type="0" edge="0" level="0" delay_en="false" delay="0" />
              <LIMIT limit_test="false" buzzer_on="false" fail_stop="false" x_axis_type="0">
                      <limit1 on="false" type="0" mode="0" freq_interp="1" line_value="0" offset_on="false" offset_x="
0" offset_y="0" />
last_config.xml                    <limit2 on="false" type="1" mode="0" freq_interp="1" line_value="-100" offset_on="false" offset_
x="0" offset_y="0" />
              </LIMIT>
              <TG status="false" min_level="-20" max_level="0" def_level="-20" level="-20" min_m_ref_level="-20" max_m
_ref_level="0" def_m_ref_level="0" m_ref_level="0" offset="0" normalize_ref_level="0" normalize_ref_pos="50" />
              <DEMOD mode="0" earp="false" volume="6" time="5000000" />
              <MEAS type="0" integral_bw="100" main_ch_bw="100" adjacent_ch_bw="100" adjacent_ch_space="100" occupied_
bw="0" occupied_bw_precent="99" occupied_bw_dBc="26" start_line="0" stop_line="606" carrier_bw="100" noise_bw="100" freq
_offset="-100" harmonic_enable="false" fundamental="120000043.56545754" freq_step="120000043.56545754" harmonic_num="10"
 harmonic_freq_num="327680" harmonic_freq1="0" harmonic_freq2="0" harmonic_freq3="0" harmonic_freq4="0" harmonic_freq5="
0" harmonic_freq6="0" harmonic_freq7="0" harmonic_freq8="0" harmonic_freq9="0" harmonic_freq10="0" harmonic_freq11="0" h
armonic_freq12="0" harmonic_freq13="0" harmonic_freq14="0" harmonic_freq15="0" harmonic_freq16="0" harmonic_freq17="0" h
armonic_freq18="0" harmonic_freq19="0" harmonic_freq20="0" harmonic_freq21="0" harmonic_freq22="0" harmonic_freq23="0" h
armonic_freq24="0" harmonic_freq25="0" harmonic_freq26="0" harmonic_freq27="0" harmonic_freq28="0" harmonic_freq29="0" h
armonic_freq30="0" harmonic_freq31="0" harmonic_freq32="0" harmonic_freq33="0" harmonic_freq34="0" harmonic_freq35="0" h
armonic_freq36="0" harmonic_freq37="0" harmonic_freq38="0" harmonic_freq39="0" harmonic_freq40="0" harmonic_freq41="0" h
armonic_freq42="0" harmonic_freq43="0" harmonic_freq44="0" harmonic_freq45="0" harmonic_freq46="0" harmonic_freq47="0" h
armonic_freq48="0" harmonic_freq49="0" harmonic_freq50="0" harmonic_freq51="0" harmonic_freq52="0" harmonic_freq53="0" h
armonic_freq54="0" harmonic_freq55="0" harmonic_freq56="0" harmonic_freq57="0" harmonic_freq58="0" harmonic_freq59="0" h

I already deleted it and success ! :phew:   Did a reset and clear too.

I have the XXX
« Last Edit: July 10, 2022, 03:34:04 pm by bicycleguy »
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf