Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers

[Mick B]

Hello, I am having a hard time telnetting into my fully working SSA/...SVA1032+. FW 3.2.2.5.1R1  It was working fine. Now the only way to get in is to use DEBTTT in SCPI then I can telnet 192.168.0.000 and then put in name and ding1234. Using SVA1000_telnet_11410.zip holds the door open but won't let me in. Looking at the /usr/bin/siglent/startup_app.sh File I see this /usr/bin/siglent/config_eth0.sh
sleep 1
portmap &
/sbin/telnetd -l /bin/sh -p 10101 &
/usr/bin/siglent/Aladdin &

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

telnetd&
- /usr/bin/siglent/startup_app.sh 71/71 100%

I don't think the "telnetd&" line is suppose to be there, I have edited it out but it just comes back.
 Any ideas? Or should I just be glad I can get into it at all?

[tv84]

Using SVA1000_telnet_11410.zip

Are you telnetting to port 10101? If so, you don't need credentials.

[Bicurico]

If you have everything working as you want it and can activate telnet by issuing a simple SCPI command, I would recommend to not mess any further with  your device!

If you want to be able to mess around a telnet console, get a Raspberry Pi! Your SSA/SVA is a test equipment - use it with care.

[killingtime]

Hi, does anyone know what Lupusz is on about in the post below?

https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3470576/?topicseen#msg3470576

From what I can gather, he's saying if you want to make S11 SWR reflection measurements on a SSA3000x Plus (non-SVA), you don't need an external reflection bridge (?), because you can use the internal one, by terminating the TG output with 50 ohms.

I thought all SSA models did need an external bridge?

[EE4all]

 After "upgrading" to an SVA, my NSP_trends_config_info.xml  looks like below. Should I remove the second product ID, and rename the first one to SVA1032X, or keep two entries there and only update one? Does it matter?

Also, should I change the PID from 0x1305 to 0x1301 as indicated in an earlier post, or not? Does it matter?

<?xml version="1.0" encoding="UTF-8"?>
<nsp_trends_info_root>
   <device>
      <language>english</language>
      <pid>0x1305</pid>
      <vid>0xf4ec</vid>
      <product_type_1>SSA3032X Plus</product_type_1>
      <product_type_2>SSA3021X Plus</product_type_2>
      <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>

[tautech]

Hi, does anyone know what Lupusz is on about in the post below?

https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3470576/?topicseen#msg3470576

From what I can gather, he's saying if you want to make S11 SWR reflection measurements on a SSA3000x Plus (non-SVA), you don't need an external reflection bridge (?), because you can use the internal one, by terminating the TG output with 50 ohms.

I thought all SSA models did need an external bridge?

They do....

While SSA3kXP and SVA essentially share the same HW they have different modes of operation where the internal bridge is only used in VNA mode which can't be selected in SSA models that require a RLB for DUT isolation and with them a S11 measurement is not possible in Analyser mode.

Lupusz is correct as he is using the instrument in VNA mode.

[Mick B]

Hello tv84, A personal Thank you! There are lots of contributors (Thanking you to!) on this bus, but you appear to be the mechanic and driver.
Yes telnet 10101 192.168.2.000   The response telnet: could not resolve 10101/192.168.2.000: Servname not supported for ai_socktype
The same thing happens when using your  SVA1000_telnet_11410.ADS file.
thanks again.

[Mick B]

I was just showing someone how telnet worked did not have anything else to use that's when I found it didn't work. I wasn't planning to screw with it.
While your here, can you tell me, am I missing any features that are not enabled that work on this unit?

[tautech]

In earliest units TG and VNA were options but in later SVA units they were both added and SVA prices increased to cover particularly the VNA option.
Use the US webpage option selection to see what is missing although it appears you have them all.
https://siglentna.com/spectrum-analyzers/sva1000x-spectrum-vector-analyzer/

[tv84]

192.168.2.000

This is an invalid IP. You'll never get it to work with such config. If you are not comfortable with IP addressing, configure DHCP on the machine and let it grab an IP from your router.

[DeDe]

Yes telnet 10101 192.168.2.000   The response telnet: could not resolve 10101/192.168.2.000: Servname not supported for ai_socktype

telnet needs first hostname/IP and then port number:

Code: [Select]

telnet 192.168.2.000 10101
And of course .000 ist an invalid IP..

[EE4all]

After "upgrading" to an SVA, my NSP_trends_config_info.xml  looks like below. Should I remove the second product ID, and rename the first one to SVA1032X, or keep two entries there and only update one? Does it matter?

Also, should I change the PID from 0x1305 to 0x1301 as indicated in an earlier post, or not? Does it matter?

<?xml version="1.0" encoding="UTF-8"?>
<nsp_trends_info_root>
   <device>
      <language>english</language>
      <pid>0x1305</pid>
      <vid>0xf4ec</vid>
      <product_type_1>SSA3032X Plus</product_type_1>
      <product_type_2>SSA3021X Plus</product_type_2>
      <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>

Anyone?

[Mick B]

192.168.2.000

This is an invalid IP. You'll never get it to work with such config. If you are not comfortable with IP addressing, configure DHCP on the machine and let it grab an IP from your router.

My bad, just a habit of never putting information out on the web, silly I know this information is already out there. DeDe. found the problem. I had it backwards port number then the IP address (a senior moment) Thanks

[Mick B]

Yes telnet 10101 192.168.2.000   The response telnet: could not resolve 10101/192.168.2.000: Servname not supported for ai_socktype

telnet needs first hostname/IP and then port number:

Code: [Select]

telnet 192.168.2.000 10101
And of course .000 ist an invalid IP..

Thank you, yes that was the problem. I don't use the command line much anymore. I used to, starter out with EDLIN & Basic but that was a lifetime ago. WINDOWS

[killingtime]

Hi,

Has anyone got a block diagram of the major internal components for a SSA3000X+?

I've looked though the user manual, service manual and application notes from Siglent and can't find one. It would be nice to know where they've actually put components like the attenuator, pre-amplifier and different mixers so I don't have to guess. They might have done something new, who knows.

An image search on Google does bring back many diagrams, but all generic. Best one I've found so far is attached.

Thanks.

[tv84]

After "upgrading" to an SVA, my NSP_trends_config_info.xml  looks like below. Should I remove the second product ID, and rename the first one to SVA1032X, or keep two entries there and only update one? Does it matter?

Also, should I change the PID from 0x1305 to 0x1301 as indicated in an earlier post, or not? Does it matter?

...

Don't reinvent the wheel. Just overwrite your .xml with the attached file, taken from an "official" SVA1032X.

[DL4JY]

Hi ,
Siglent released new firmware for the SSA3000x (plus & R) & SVA1000x : V3.2.2.6.0R7

New Functionality:
• Add ECal in VNA mode
• Add three new formats in VNA mode: Unwrap Phase/Real/Imaginary
• Add Z Reflection in VNA mode
• Add PM demodulation in MA mode
• The time of analog demodulation in MA mode is adjustable

Now the question - has somebody already been so brave to test? I am interested in the results for an upgraded SSAx+ to SVA.:-)
Any advers effects ??

Haven't seen an updated Manual so far, are there descriptions of the added functionality other than from e.g. Keysight et. al.?

Hasta la vista

[tomud]

Hi ,
Siglent released new firmware for the SSA3000x (plus & R) & SVA1000x : V3.2.2.6.0R7

Thanks for the information The firmware upgrade went through without any problems...

[EE4all]

Yes, the firmware update went just fine with my SVA that was earlier "upgraded" from a SSA.

[RoV]

Confirm that the SVA1032X 3.2.2.6.0R7 upgrade works, but...
  
still 10 kHz BW only (grayed) in VNA mode!
 
I should really buy a new NanoVNA to overcome this problem

[Marcel G]

Here it also succeeded with the new firmware (updated SSA to SVA).

I think you expect too much the Spectrum Analyzer is pretty good for the money but the VNA function is just a toy.

Once you have worked with a real VNA you will not want anything else and you will soon forget the VNA function in the Siglent.

[RoV]

I think you expect too much the Spectrum Analyzer is pretty good for the money but the VNA function is just a toy.
Once you have worked with a real VNA you will not want anything else and you will soon forget the VNA function in the Siglent.

I don't agree with you. It is a T/R unit and not a full 2-port and this is a big limitation, but even hp used to build T/R units (e.g. 8714ET). Apart from this, it works quite well and the main limitation, in my opinion, is the IF bandwidth: 10 kHz is terrible. And it is clearly a software limitation, because the RF hardware is quite stable in frequency and has a phase noise low enough to reduce the IF bandwidth perhaps to 10 Hz. That would greatly improve the dynamic range.

[tomud]

Confirm that the SVA1032X 3.2.2.6.0R7 upgrade works, but...
  
still 10 kHz BW only (grayed) in VNA mode!

Hmm, did someone say that they will add a change in bandwidth in VNA mode in the new firmware ? Alternatively, has anyone sent a proposal for such changes in the firmware to Siglent ?

----

However, another question, does anyone know what ECal models support SVA and whether it actually works ?

----

I personally think about the SNA5000 - only this price 

...and here it already shows SNA6000 

https://www.siglent.com/u_file/download/22_12_12/SNA6000A_DataSheet_DS09060_C01B.pdf

[RoV]

Hmm, did someone say that they will add a change in bandwidth in VNA mode in the new firmware ? Alternatively, has anyone sent a proposal for such changes in the firmware to Siglent ?

I think the issue is very clear to Siglent, otherwise there wouldn't be an "IF bandwidth" option in the GUI... that, unfortunately, is grayed at 10 kHz, as it was more or less since the beginning.
The issue was discussed several times in eevblog and the option is long waited, I think they read the forum. I don't know of direct contacts to signal the issue, perhaps tautech could do so.

[tomud]

Hmm, did someone say that they will add a change in bandwidth in VNA mode in the new firmware ? Alternatively, has anyone sent a proposal for such changes in the firmware to Siglent ?

I think the issue is very clear to Siglent, otherwise there wouldn't be an "IF bandwidth" option in the GUI... that, unfortunately, is grayed at 10 kHz, as it was more or less since the beginning.
The issue was discussed several times in eevblog and the option is long waited, I think they read the forum. I don't know of direct contacts to signal the issue, perhaps tautech could do so.

Yes, I know that this option is currently inactive and something actually reminds me that the subject of the BW in the VNA mode was discussed. However, this does not mean anything and so the currently inactive option in one of the firmwares may well be removed.

Tautech mentioned that people from Siglent read this forum, but in such a long thread (there's also a thread about SVA https://www.eevblog.com/forum/testgear/siglent-sva1015x-1-5ghz-spectrum-vector-network-analyzer-(coming)/ ) it's very easy to miss something (even for someone who follows these topics often). Maybe it would be easier if there was a topic like in the case of oscilloscopes (bugs in the firmware and proposals for new functions).

IMHO, I still say that without submitting such proposals by distributors and customers themselves to support, it is difficult to count that writing only on the forum will somehow affect the manufacturer. Let's say as if they had to closely follow all the topics on all forums in the world, they would not have employees to read all of it 

----

Siglent for the SVA1000X and SHA800A models (higher dynamics 90dB vs 114dB, most likely improved electronics compared to the SVA1000X) clearly states IF BW 10KHz - so it is not known if they plan to change it. Only the SNA5000 and SNA6000 series offer IF BW 10Hz - 3MHz...