Hack of Sigllent spectrum analyzer ssa3021X?

[ShaneEEV]

TV84,

How does one "remove the hack"? ( I can see logging-in and copying the backed-up files back to the operating files. Perhaps you meant that?

I performed the upgrade on my new SSA3021X, but I see my SN has been 'X'd out.

Any way to get the feature set and retain the proper serial number?

Thanks, in advance!

Shane

[tv84]

You can reinsert the S/N via SCPI.

Try something like

:SRLN <serial_num>

(I don't remember if this is the right command for the SSA but should be here in the forum...)

[ShaneEEV]

Thank you, TV84. I don't seem to.be able to get an http session with the SA at this time.

I found a manual on the SCPI commands for the SA, but I don't see any command that allows configuring the S/N for the SA.

Best Regards,
Shane

[tautech]

Thank you, TV84. I don't seem to.be able to get an http session with the SA at this time.

I found a manual on the SCPI commands for the SA, but I don't see any command that allows configuring the S/N for the SA.

Best Regards,
Shane

Of course, it's a hidden undocumented command.

From P7 of the programming manual:
https://www.siglentamerica.com/wp-content/uploads/dlm_uploads/2017/10/SSA3000X_ProgrammingGuide_PG0703X_E04A.pdf
Telnet mode. The telnet SCPI service is available on port 5024.

[TTH]

TV84 is correct:

:SRLN <serial_num>

... is the correct SCPI command to set the serial number (note the space after :SRLN)

Thanks to TV84

[ShaneEEV]

Thank you TauTech and TTH!

I have successfully logged-in as you suggested, but I'm having difficulty getting the SN set.

I have tried:

:SLRN SSA3XABC1t2682

:SYST:SLRN SSA3XABC1t2682

:SYSTCONF:SYST:SLRN SSA3XABC1t2682 (Number changed to protect the innocent)

Nothing seems to set the serial number... Should I enter some sort of save command to fix the change into the SSA???

I skimmed through the manual- perhaps I missed the details???

Your hints are very helpful!

Thank you, again!
Shane

[tautech]

I have successfully logged-in as you suggested, but I'm having difficulty getting the SN set.

Sanity check *IDN?
Does this return the correct answer ?

For SCPI it's always a good idea to prove you have a valid connection first.....especially if you're a programming novice like me. 

[ShaneEEV]

Hi TauTech,

Yes, *IDN? returns the scope model and SNXXXXXXXXXX, 1.2.9.2.a

[tautech]

Hi TauTech,

Yes, *IDN? returns the scope model and SNXXXXXXXXXX, 1.2.9.2.a

See the little 't' in your SN# ? That doesn't look right to me. Double triple check it belongs there.

[ShaneEEV]

That's not the real SN of my SSA. When I do the *IDN? I get all X's for the SN.

[tautech]

That's not the real SN of my SSA.

Yes I know but it should be SSA3X***#R####

When I do the *IDN? I get all X's for the SN.

Yes, when they are hacked XXX...... is the SN#.

Someone here will pop by and rescue you. 
They go just fine without a SN# so no need to worry unduly.

[ShaneEEV]

Tautech-

Thank you- my SSA has the SN of this form:
SSA3X***2R####

I hope to be rescued! Ha ha! It would be good to put the SN right, even though it doesn't affect the function of the analyzer.

I appreciate your kind replies!

Best Regards,
Shane

[Emo]

Thank you TauTech and TTH!

I have successfully logged-in as you suggested, but I'm having difficulty getting the SN set.

I have tried:

:SLRN SSA3XABC1t2682

:SYST:SLRN SSA3XABC1t2682

:SYSTCONF:SYST:SLRN SSA3XABC1t2682 (Number changed to protect the innocent)

Nothing seems to set the serial number... Should I enter some sort of save command to fix the change into the SSA???

I skimmed through the manual- perhaps I missed the details???

Your hints are very helpful!

Thank you, again!
Shane

Just for the record and for others that might want to use this method.
In your SCPI commands you seem to have made a typo; :SLRN, should be :SRLN

[rf-loop]

Thank you TauTech and TTH!

I have successfully logged-in as you suggested, but I'm having difficulty getting the SN set.

I have tried:

:SLRN SSA3XABC1t2682

:SYST:SLRN SSA3XABC1t2682

:SYSTCONF:SYST:SLRN SSA3XABC1t2682 (Number changed to protect the innocent)

Nothing seems to set the serial number... Should I enter some sort of save command to fix the change into the SSA???

I skimmed through the manual- perhaps I missed the details???

Your hints are very helpful!

Thank you, again!
Shane

Just for the record and for others that might want to use this method.
In your SCPI commands you seem to have made a typo; :SLRN, should be :SRLN

Also, regardless of whether it worked or not. Until today, I have not seen Siglent serial numbers what include other than capital letters and numbers.

[tv84]

It's been a long time but I think when you force the S/N to be the one you want with the SCPI command, you automatically disable the hack that most people use.

After activated, if I remember correctly, the hack works by checking if the S/N is XXXXXXXXX.

But I could be wrong...

[TTH]

TV84 is correct:
The SCPI command
:SRLN SSA3X*********
... changes the serial number
... but results in the creation of a new NSP_sn_bandwidth.xml file (and backup)
... populated with  the serial number - but no option licence keys : (
It does appear that you have to live with the XXX serial number if you want all the options.

[tv84]

TV84 is correct:
The SCPI command
:SRLN SSA3X*********
... changes the serial number
... but results in the creation of a new NSP_sn_bandwidth.xml file (and backup)
... populated with  the serial number - but no option licence keys : (
It does appear that you have to live with the XXX serial number if you want all the options.

It looks like Alzheimer hasn't catch me yet...  I had this idea from what I saw in my code analysis although I didn't asked nobody to test. Now it's confirmed!

[Pinkus]

However, there is one drawback: AFAIR, Siglents software EasySpectrum will not work without the serial number. If you would like to use the analyzer for doing pre-compliance measurements, the software saves a lot of time and makes things much easier.
However: I cannot test/confirm this, as my unit does have serial number and all options. Maybe somebody can double check this.
But I am pretty sure that EasySpectrum was very sensitive about the connected analyzer.

[TTH]

Easy Spectrum functionality works (both Monitor and EMI) with Serial XXXXXXXXXX

[electronic_eel]

There is a new firmware 1.2.9.3a out.

This one seems to block telnet access to the device. It is not available on the regular port 23, and also not on 10101 (which some other Siglent products use).

Downgrading to 1.2.9.2a is possible, but does not bring telnet access back!

So I wouldn't recommend to install this update for now.

[BillB]

Seems like Siglent is starting to secure their product line. 

[tv84]

The new FW SSA3000X_v1.2.9.3a has 2 interesting files, besides new versions of the common ones.

See attached.

And, of course, SHELLCMD was removed from the main app. 

[markus_jlrb]

@tv,

how to mod the lines from

rm -f to echo rm -f
or  from         
rm -f to # rm -f

Any ide?

Markus

[electronic_eel]

how to mod the lines from

You'd have to package a modified ADS update file. The format is obfuscated and sometimes also encrypted. You can find some info here: https://www.eevblog.com/forum/testgear/siglent-ads-firmware-file-format/. But while the descriptions there are probably enough to get someone determined on the right track, they are not simple recipes you can just follow along. tv84 seems to have mastered this though.

Just an idea: if someone creates a modified ads file, wouldn't it be better to create one that just re-enables the telnet service and doesn't do anything else, like replacing ecomb? This way you could just install the regular update and install the re-enabler.ads afterwards. When Siglent releases the next update, it will most probably disable telnet again, so you could use the same re-enabler again and wouldn't have to do modifications again.

[tv84]

rm -f to echo rm -f

Test at your own risk.

This is the official ADS with additional.sh "slightly" modded.

If you already installed the official update, you already had telnetd deleted, so in that case this won't work.