Siglent SSA3021x Peak Table - Page 1
Forum section: electronics / testgear

author: baconcomposter
author_rank: Newbie
timestamp: May 01, 2019, 02:00:14 am
content: Hello all,I've been very happy with my recent Siglent purchase. I'm using it to monitor wireless microphones for broadcasts (currently on the road with Stanley Cup Playoffs). It has been even better than I hoped for.There is one thing I would love to do. The manual hinted at it but I can't find a setting.I would like to be able to sort the peak table by frequency rather than amplitude. The microphone signals I monitor vary with amplitude as they are often in motion. I am limited to 4 markers, so I would like to be able to monitor multiple signals across the spectrum with the peak table. Unfortunately, the table reorders itself with every sweep which is very frustrating.Does anyone have any idea how to change the sort option to frequency instead of amplitude?

author: tautech
author_rank: Super Contributor
timestamp: May 02, 2019, 05:33:15 am
content: Welcome to the forum.Have a look though the many Operating tips in the Siglent America website.https://www.siglentamerica.com/operating-tips/ssa3000x-series/This one should point you in the right direction:https://www.siglentamerica.com/operating-tip/ssa3000x-peak-table/

author: rf-loop
author_rank: Super Contributor
timestamp: May 02, 2019, 06:08:37 am
content: Quote from: tautech on May 02, 2019, 05:33:15 amYes but it list peaks with level order, not frequency order (what is some cases nice if it can).If there is example 100M 1 dbm 130M 2dBm and 150M -5dBmList order is, based to level (user defined level thresholds):Peak 1 130MHz 2dBmPeak 2 100MHz 1dBmPeak 3 150MHz -5dBmand so onAnd when levels fluctuate it is very extremely terrible when this table order change frequently. In live it is very frustrating to look. Some times just impossible to follow. Think if there is lot of peaks.Even in this very extremely simplified table if there is some level variations this table order is jumping like mad dog.It is VERY nice if user can also select displayed order based to frequency (user defined level thresholds)(let's hope some day it can...)Peak 1 100MHz 1dBmPeak 2 130MHz 2dBmPeak 3 150MHz -5dBmand so onNow if there is level variations this table order is rock solid and easy to follow (until some drops under threshold).Rant: It feels some times good if these FW programmers also have used SA's in real life with enough experience in different situations, then peoples do not need ask and try tell why this and that very basic things are important.

author: Unknown
author_rank: Unknown
timestamp: May 03, 2019, 01:46:17 pm
content: Quote from: baconcomposter on May 01, 2019, 02:00:14 amGood suggestion. We agree with you and the product manager said he would add the feature.Thanks for your comments.

author: Bicurico
author_rank: Super Contributor
timestamp: May 03, 2019, 01:59:26 pm
content: Hi,I'm a bit late, especially when Siglent decided to add this feature.Anyway: if you can afford to connect your Siglent through Ethernet with a PC, you can use my "VMA Simple Spectrum Analyzer" software for the SSA3021X.This adds several measurements, including automatic transponder recognition.Let me know if you need assistance in trying out the software. Just visit my blog (link in signature).Regards,Vitor

author: JPortici
author_rank: Super Contributor
timestamp: May 03, 2019, 06:53:47 pm
content: Quote from: Siglent America on May 03, 2019, 01:46:17 pmwhile we're at it (couldn't find the official thread)i think there is a bug when operating the tracking generator: Regardless of the current sweep time (for example you have a combination of span,rwb,vbw or even manual sweep time) when you enable the tracking generator the sweep is changed to the fastest time possible. To be more precise, if you've set up for example to be 100s and the minimum time would be 3s, when you enable the TG the label will still say 100s but the indicator and the update rate (and the measured output) will sweep at 3s.(I think i'm running the most recent firmware, but i'll check monday)

author: rf-loop
author_rank: Super Contributor
timestamp: May 04, 2019, 07:24:10 am
content: Quote from: JPortici on May 03, 2019, 06:53:47 pmIf I set it for some Span and manually set RBW and VBW and normal SA automatic sweep is around 3s. After then then I set manually sweep time to 100s.After then I turn TG on without touching any other things. It continue this 100s sweep time (checked with watch, it do not change) and also sweep time display stay correct. Checked with many different span, sweep times, RBW and VBW settings. Just nada. Works as it need work.(Example: C 1600MHz, Span 125MHz, RBW 30kHz, VBW 3kHz - Sweep auto:around 3s, set Sweep time manually to 100s. Turn TG on. Sweep still 100s in real and in displayed number. and so on, many different setups and same result)Latest FW: 1.2.9.2aPlease give FW version, ALL parameters and changes and what is error so that it can repeat.After you check FW version please also give perfect step to step instructions, including everything (Starting from known state: System -> PwrOn/Preset -> Factory Reset (no need full erase)) so that it can repeat exactly as you find it.Just for avoid possible false "bug alerts" sot that then real bugs get more weight value. (of course also this can be real bug but before it can know, need get enough information how how all researchers can repeat the experiment.)And if reason was old FW or some outside of SA reason then the wrong alarm must be canceled.

author: JPortici
author_rank: Super Contributor
timestamp: May 06, 2019, 07:08:56 am
content: FW V1.2.9.2aI'll make a video after work

author: Unknown
author_rank: Unknown
timestamp: May 06, 2019, 01:24:08 pm
content: Quote from: Siglent America on May 03, 2019, 01:46:17 pmAs a note, we already do have this on the SVA1015X version.

author: JPortici
author_rank: Super Contributor
timestamp: May 06, 2019, 09:44:04 pm
content: Therehttps://youtu.be/_pSayplpSH0I wonder, maybe i received the unit with the latest application firmware, but the other firmwares are outdated?

author: seronday
author_rank: Regular Contributor
timestamp: May 07, 2019, 12:54:32 am
content: In the Bandwidth menu, change the "FILTER" option from EMI to Gauss and test the operation again.You should find that it works correctly.Regards

author: JPortici
author_rank: Super Contributor
timestamp: May 07, 2019, 07:14:40 am
content: It does indeed work correctly! So it's related to using the EMI filters..