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

jemp · « **Reply #1525 on:** February 13, 2021, 10:17:45 am »

Did the steps from #1224 again...
Screenshot...

/usr/bin/siglent/firmdata0 # mv nsp_data_b1 nsp_data_b1x
/usr/bin/siglent/firmdata0 # cd /usr/bin/siglent/usr/backup
/usr/bin/siglent/usr/backup # mv nsp_data_b nsp_data_bx

mv: can't rename 'nsp_data_b': No such file or directory --> this is strange... ?

Synced en rebooted.. but still the same, also Serial number is still there.. it did not change to XXXXX , do i have to change that somewhere ?

Can you tell me how to go back to my original setup.. where I took the Nand ?

Kibabalu · « **Reply #1526 on:** February 13, 2021, 10:49:57 am »

The error message should be fine, because you already renamed the file. The question is more, why you haven't got it two steps before.

could you have a look wether the files nsp_data_b1x and nsp_data_bx are inside the folders /usr/bin/siglent/firmdata0 and /usr/bin/siglent/usr/backup?

Unfortunately I don't know how to do a backup roll back.

jemp · « **Reply #1527 on:** February 13, 2021, 12:10:55 pm »

Ok, Done, Tnx

Kibabalu · « **Reply #1528 on:** February 13, 2021, 12:36:54 pm »

What was the issue? Maybe we others can learn from it

jemp · « **Reply #1529 on:** February 13, 2021, 12:49:57 pm »

No , done meant.. cleaning my mailbox..

If i have a solution.. I 'll post it for sure..

Happiness will shout out loud... !!

capt bullshot · « **Reply #1530 on:** February 16, 2021, 02:26:31 pm »

Just wanted to thank all the contributors to this thread

Sucessfully converted my spanking new SSA to the SVA:

It came with fw V3.2.2.3.2, that I downgraded to V2.2.1.2.8 before starting the conversion according to the instructions of reply #1223 / #1224. Internal SMA cable was factory installed, VNA gives plausible results.

Lupusz · « **Reply #1531 on:** February 18, 2021, 11:03:09 am »

I just wanted to share, that my SSA 3021XP must have a reflection bridge built in. I'm not sure if all owners know that?
And if I'm right, why do they sell the Siglent Bridge as mandatory for the SSA series when it is just about a license?

It costed me several hours to find the feature, when my self built bridge was not working as I expected at S11 mode. I thought I have to produce the same behavior as the RB3X25 with my bridge.
When I checked what happens when I terminate the TG output with 50 Ohms and I directly a plausible S11 response in Smith chart. After calibration everything worked perfectly without external bridge.

So I see no need to buy an expensive RB3x25 reflection bridge or to play around with self made bridges.

By the way, everything works fine with my upgraded SSA3021XP, but I cannot get the SVA1032X screen as capt bullshot has (SVA firmware seems to be on and also many features as useable). It still looks like an SSA.

As I cannot access the device any more because the "Telnet Acsess Frimware" is not working in this state any more.
Has anyone the same problem and a solution?

capt bullshot · « **Reply #1532 on:** February 18, 2021, 11:24:41 am »

Looks like you've got all interesting (and working) features enabled. Not all features shown at mine are useable, e.g., RT40 enables the real-time SA but doesn't work as the required hardware is missing. So I just wouldn't care whether it thinks it's a SSA or SVA.

BTW, I've upgraded the FW to V3.2.2.3.3R1 and everything is still fine.

Regarding telnet access, there's a more recent "update" file somewhere hidden in this thread that is supposed to work with this firmware (haven't tried).

Kibabalu · « **Reply #1533 on:** February 18, 2021, 02:21:34 pm »

Without an internal reflection bridge it wouldn't be possible to convert the SSA3000X Plus model to an SVA1000X model.

The dedicated external reflection bridge offered from Siglent is for the SSA3000X non-Plus model, I guess.

Bicurico · « **Reply #1534 on:** February 18, 2021, 02:56:01 pm »

The external bridge is indeed for the SSA3000X models.

The model name, after the hack, will only change to SVA if the corresponding file is edited, too. This is explained somewhere in this thread (too lazy to search for it). Having the device model set to SSA instead of SVA will, however not make any difference at all - not in available functionality nor in FW upgradeability.

If it was my case, I would actually prefer to have the device identify to the same model as the label...

Lupusz · « **Reply #1535 on:** February 19, 2021, 10:24:39 am »

Thank you all so much for the great help you provided!

I will happily stay with the device as it is, thanks for convincing me

antenna · « **Reply #1536 on:** February 26, 2021, 08:00:06 am »

Just got the SVA1032x and updated the firmware to 3.2.2.4.0 before finding this thread. Reading through this, I see mention of people converting SSA's to SVA's and noticing the serial number still displays SSA. I bought it new from TEquipment so that must be normal to see SSA after the conversion of an SSA.

I saw siglent america is a forum member here so I was surprised to see talk on the licensing hack stuff (which I am very much interested in - they charge an insulting amount). I am too chicken to try it because it started out as as SVA, not SSA like this thread talks about so I don't know what steps I can/need to omit to make my options permanent. Is there a way to get my license keys without trying to undo this latest firmware update?

Many thanks!
Brandon

tautech · « **Reply #1537 on:** February 26, 2021, 08:12:26 am »

Quote from: antenna on February 26, 2021, 08:00:06 am

Just got the SVA1032x and updated the firmware to 3.2.2.4.0 before finding this thread. Reading through this, I see mention of people converting SSA's to SVA's and noticing the serial number still displays SSA. I bought it new from TEquipment so that must be normal to see SSA after the conversion of an SSA.

I saw siglent america is a forum member here so I was surprised to see talk on the licensing hack stuff (which I am very much interested in - they charge an insulting amount). I am too chicken to try it because it started out as as SVA, not SSA like this thread talks about so I don't know what steps I can/need to omit to make my options permanent. Is there a way to get my license keys without trying to undo this latest firmware update?

Many thanks!
Brandon

Welcome to the forum.

And you didn't find this thread:
https://www.eevblog.com/forum/testgear/hack-of-sigllent-spectrum-analyzer-ssa3021x/

Discussion of hacks is best kept there.

antenna · « **Reply #1538 on:** February 27, 2021, 02:57:13 am »

Thanks for the welcome. I did not see that thread, thank you! Ill go check it out!

mikeydread · « **Reply #1539 on:** March 08, 2021, 02:57:19 am »

Thanks.. tv84 and the team.. for all the help but now I'm stocked. Here is where i got to and can't figure out how to replace the license whether i have to delete the entire thing or edit it.
I am lost, i not into LINUX so any help will be appreciated. Ps An Attached photo in included.
Once again thanks.

mikeydread · « **Reply #1540 on:** March 11, 2021, 03:55:27 am »

Take a look.

mikeydread · « **Reply #1541 on:** March 12, 2021, 09:22:39 pm »

Take a look

oz2cpu · « **Reply #1542 on:** March 12, 2021, 10:02:13 pm »

to #1532
how exactly did you do this ?
where is the menu ?
mine should have all possible options turned on, so I should also be able to see this ?

mikeydread · « **Reply #1543 on:** March 12, 2021, 10:16:29 pm »

tv84 · « **Reply #1544 on:** March 13, 2021, 03:34:59 pm »

"Unix uses 0xA for a newline character. Windows uses a combination of two characters: 0xD 0xA. 0xD is the carriage return character. ^M happens to be the way vim displays 0xD (0x0D = 13, M is the 13th letter in the English alphabet)." Here.

You must purge the ^M from the files you've been editing! You shouldn´t edit the files in Windows without special attention to that detail.

TK · « **Reply #1545 on:** March 14, 2021, 01:57:52 pm »

Quote from: oz2cpu on March 12, 2021, 10:02:13 pm

to #1532
how exactly did you do this ?
where is the menu ?
mine should have all possible options turned on, so I should also be able to see this ?

I suggest you to use the "Quote" feature of the forum to make it easier for members to follow the thread. If you say "to #1532" and it is a couple of pages back, it is most probable that the reader will not answer to your questions because of the extra work to navigate looking for #1532... or at least add a direct link using the URL feature.

mikeydread · « **Reply #1546 on:** March 15, 2021, 11:36:15 pm »

Quote from: tv84 on March 13, 2021, 03:34:59 pm

"Unix uses 0xA for a newline character. Windows uses a combination of two characters: 0xD 0xA. 0xD is the carriage return character. ^M happens to be the way vim displays 0xD (0x0D = 13, M is the 13th letter in the English alphabet)." Here.

You must purge the ^M from the files you've been editing! You shouldn´t edit the files in Windows without special attention to that detail.

mikeydread · « **Reply #1547 on:** March 15, 2021, 11:38:12 pm »

Just take a look

tubularnut · « **Reply #1548 on:** March 16, 2021, 09:00:49 am »

Quote from: mikeydread on March 15, 2021, 11:36:15 pm

Quote from: tv84 on March 13, 2021, 03:34:59 pm
"Unix uses 0xA for a newline character. Windows uses a combination of two characters: 0xD 0xA. 0xD is the carriage return character. ^M happens to be the way vim displays 0xD (0x0D = 13, M is the 13th letter in the English alphabet)." Here.

You must purge the ^M from the files you've been editing! You shouldn´t edit the files in Windows without special attention to that detail.

I'm not sure what you are trying to do, but just about every command you are running is WRONG, which I expect you can already guess.

Unfortunately, because you have supplied a screen shot, rather than copy and paste the code from the screen which makes its very difficult to explain each error in context. So:

# /usr/bin/siglent/ecomb and ecomb_p & << You are trying to run 'ecomb' or 'comb_p' in the background, which is what the '&' means. You can't (shouldn't) do this! Same for Aladdin.

# mv /usr/siglnet/ecomb/Aladdin_p & /usr/b ..... <<< The '&' will leave the command and try to run it the background, hence the error, and also danger the danger of actually renaming it to '&'

I'll post the second screenshot as well, but give me a few minutes to type it up.

tubularnut · « **Reply #1549 on:** March 16, 2021, 09:11:13 am »

Quote from: mikeydread on March 15, 2021, 11:38:12 pm

Just take a look

Part 2:

# /usr/bin/siglent/config/NSP_config_upgrade_info.xml <<< this is NOT a command or script file, and you are trying to run it as such.

Next you are trying to mount it, it is NOT a filesystem.

I expect you are trying to edit the upgrade file, so you need to use the "vi" command.

To use "vi", it is not an intuitive command, and I suggest you look it up on the web, and try it out somewhere else before attempting to edit a crucial file on your SSA.

# <upgrade_static_id>11405</upgrade_static_id>. <<< Again, you are trying to run a command (a line from the xml file) which does not exist.

# mv <upgrade_static_id>11405</upgrade_static_id> <upgrade_static_id>11410</upgrade_static_id>. <<< Again, you are trying to RENAME (mv) a file which does not exist, but you have specified a line from the xml file.

You need to use "vi" to edit the file.

Suggested tutorial: https://ryanstutorials.net/linuxtutorial/vi.php


EEVblog Main Site	EEVblog on Youtube	EEVblog on Twitter	EEVblog on Facebook	EEVblog on Odysee

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

Share me