Preliminary, coming in the near future. Siglent new Spectrum analyzer serie is SSA3000X
There is 9kHz - 2.1GHz and 9kHz - 3.2GHz models with and without tracking generator.
My rough estimate about prices is ~6k$ - <12k$ depending model without optionals.
Preliminary, coming in the near future. Siglent new Spectrum analyzer serie is SSA3000X ...................Nice to see a decent image, I had heard whispers of a new SA.
My rough estimate about prices is ~6k$ - <12k$ depending model without optionals.
Full specs and pricing are now available on Siglent websites:
http://www.siglentamerica.com/pdxx.aspx?id=1546&T=2&tid=227 (http://www.siglentamerica.com/pdxx.aspx?id=1546&T=2&tid=227)
Comparison chart attached.Full specs and pricing are now available on Siglent websites:
http://www.siglentamerica.com/pdxx.aspx?id=1546&T=2&tid=227 (http://www.siglentamerica.com/pdxx.aspx?id=1546&T=2&tid=227)
so those initial price estimates were only off by a factor of 4 or so... :-DD
in that price range the direct competitors are Rigol DSA815/1030, maybe also Hameg HMS-X, something else?
google-spreadsheet for comparisons anyone?
so those initial price estimates were only off by a factor of 4 or so... :-DD
Nice. thanks for that, it will useful for all. :-+
Not that I am buying an SA anytime soon, but I entered some info into a spreadsheet anyway
https://docs.google.com/spreadsheets/d/1yijOHnEqQ5ffkcK3lZFgzSga9HShgZcXY4gEWarSnQI/edit?usp=sharing (https://docs.google.com/spreadsheets/d/1yijOHnEqQ5ffkcK3lZFgzSga9HShgZcXY4gEWarSnQI/edit?usp=sharing)
(PM me if you want to edit it!)
USB, Ethernet, GPIB, etc. connectivity would be good info to add.
Hameg HMS-X doesn't look great on specs, unless you need the small size, fanless design etc.
In general DANL numbers are all over the place, a bit like fuel consumption on cars - would be better to only trust measurements done by an independent third party not the manufacturer datasheet.
Tg option is here:
http://www.siglent.eu/catalog/product/view/id/1111/s/siglent-tg-ssa3000x-tracking-generator-license/category/98/ (http://www.siglent.eu/catalog/product/view/id/1111/s/siglent-tg-ssa3000x-tracking-generator-license/category/98/)
That option sounds like a mere software licence key, does it mean that the instrument come anyway with TG HW installed and it's only matter to activate it, even after the purchase ?Yes, this appears to be the case......so stated on the Siglent websites:
Anyway, someone found any test, review, "interior photo" or usage video other than Siglent "trailer".These units have been released for not yet a month and there's been internal discussion of upcoming external reviews, all one can say is it is a job for an experienced reviewer and also not a job that takes 10 minutes to do properly.
These units have been released for not yet a month and there's been internal discussion of upcoming external reviews, all one can say is it is a job for an experienced reviewer and also not a job that takes 10 minutes to do properly.
Watch this space. ;)
Any review out there ?My take on that: all ham amateurs and developers working on a small buget did purchase a DSA815 in the past (given a need of a SA), so this market is saturated. Now it will take much longer to bring a reasonable amount of SA devices into the market.
Those SA, together new 2000X DSO lineup are like ghosts ...
An instrument sample sent to Dave for a review / tear-down would come in handy to promote those new lines.You bet they do. I do know they've had to do some tweaks but AFAIK they're nearly finished those and I'll probably get a demo unit in my next shipment. The worry is; how many other accessories will I need as well? :scared:
Recently the Siglent SSA3032X appeared as "available ready to ship" from Batronix (Germany), so they actually exist ....
The worry is; how many other accessories will I need as well? :scared:
Just a piece of wire to use as an antenna and you can look & listen at radio stations. One of the interns I coached needed a spectrum analyser for his project but he mostly used it to listen to the radio ;DAn instrument sample sent to Dave for a review / tear-down would come in handy to promote those new lines.You bet they do. I do know they've had to do some tweaks but AFAIK they're nearly finished those and I'll probably get a demo unit in my next shipment. The worry is; how many other accessories will I need as well? :scared:
Recently the Siglent SSA3032X appeared as "available ready to ship" from Batronix (Germany), so they actually exist ....
There will be at least one review coming that I know of but I am guessing it will be in May at the earliest.
Please consider sending one to the Signal Path as previously mentioned as Shahriar is one of the few reviewers who will really "test" the machine and not just show us some signals.I couldn't possibly confirm Shahriar will be getting one to review, it's not my place to do so. ;)
Please consider sending one to the Signal Path as previously mentioned as Shahriar is one of the few reviewers who will really "test" the machine and not just show us some signals.I second this because a spectrum analyser isn't easy to test properly! But I'm afraid it won't happen because the firmware likely takes at least two years to get to a useful state as we have seen with all previous Siglent equipment.
I second this because a spectrum analyser isn't easy to test properly! But I'm afraid it won't happen because the firmware likely takes at least two years to get to a useful state as we have seen with all previous Siglent equipment.
But I'm not sure I want to be the first to try the waters on this one.
Our introduction has been rather slow. We made some improvements to the TG flatness which has slowed it down.
Has anyone tried calling Siglent or a rep?
Has anyone tried calling Siglent or a rep? I have to order a SA next week and would like to get any information I can. It will be purchasing by a customer and only be used by me for a specific job but I may end up with it. I did another job in which I had to purchased the DSA815 for a customer and it worked okay but I would like to try the Siglent this time if I can get any positive feedback.
Lets keep this post going as I think a lot of people may be interested in what is intended to be a very competitive piece of equipment.
i hope, rigol will respond to the new market situation with a free "bandwith upgrade" via firmware for DSA815... 8)
i hope, rigol will respond to the new market situation with a free "bandwith upgrade" via firmware for DSA815... 8)
Is there any way to see if the SA has the improved TG or not? Model number? Serial number?
I spoke with one of Siglent's local US distributors today and I was told that he has yet to sell a single unit. Lead time is ~ 1 week so they do sound available. I told him I was concerned about a new design and no return policy and nothing was offering to settle this concern. He even recommended I stay with Rigol (having used them in the past). I think if Siglent is going to make any serious headway into this market, they should either get some serious unbiased reviews out there or offer a fair or at least comparable return policy to that of Rigol. I would still consider trying it but without a return path, I wont be the first to purchase one based solely on speculation. If Siglent is interested in having a first EEVblog review and is willing to cut me some return slack, let me know.See reply #33
If you would like to see any particular screen shots then please let me know. I will take a shot of the TG across the full 9 KHz - 3.2 GHz (SSA3032X) or 9 KHz - 2.1 GHz (SSA3021X) if you like.
Steve
If you would like to see any particular screen shots then please let me know. I will take a shot of the TG across the full 9 KHz - 3.2 GHz (SSA3032X) or 9 KHz - 2.1 GHz (SSA3021X) if you like.
Steve
Hi Steve,
it would be nice to see a video that shows scan speed / dynamic range with different RBW settings.
Is also the 2.1Ghz version (SSA3021X) interested by new PCB revision issue ?
Is there any way to see if the SA has the improved TG or not? Model number? Serial number?
You couldn't get it on loan for evaluation at all? I'd try another distributor because IMHO you should be able to evaluate test equipment especially when it costs a couple of thousand dollars/euros.
However, the sweep speed and RBW are both tied to the size of the range you are sweeping.
We don't have an RF generator in this office so we used the SDG2122X.
I ran some curves but I guess Markone wanted to see some large RBW settings with smaller spans. I'll try to get some of those posted later.
I ran some curves but I guess Markone wanted to see some large RBW settings with smaller spans. I'll try to get some of those posted later.
Hi Steve,
many thanks for your attention, i have taken note of sweeping times and noise floor level.
If you can, pls repeat the 4th (RBW 10Hz) increasing signal level to -20dBm.
I ran the same trace with a -20 dBm signal, as you requested. Please see attached.
Note: The SSA3032X used the FFT mode in all three cases.
Steve
Hi guys,
I have been using SSA3021X for about two weeks now.
Hi guys,You better return it because it will take Siglent at least 2 years to fix the bugs!
I have been using SSA3021X for about two weeks now.
Initially, after a day of use, the firmware froze and the unit was refusing to start. From customer support they sent me a firmware image and instructions, so I can re-flash the firmware, but that didn't help. I needed to ship the unit back so they can fix it.
I hope Siglent will fix the firmware soon, because it is a real pain to work with it in its current state.
I haven't used any other spectrum analyser before, so I can't really speak about its performance. It did an alright job for my purpose (EMC pre-compliance testing). I don't think you have control over the FFT mode. I noticed it switches on automatically in some rare occasions, when I am playing around with the range.Get a second hand Advantest or a used spectrum analyser from another brand. There is a lot out there for sale (even with warranty)! AFAIK Siglent has a 30 day no hassle return policy.
I might consider returning it (if that's an option since it has been used already), but the problem is that there is no other cheap analyser on the market, which goes to 2GHz (I need that range for the particular EMC tests I am doing).
I might consider returning it (if that's an option since it has been used already), but the problem is that there is no other cheap analyser on the market, which goes to 2GHz (I need that range for the particular EMC tests I am doing).
Hi guys,
I have been using SSA3021X for about two weeks now.
Initially, after a day of use, the firmware froze and the unit was refusing to start. From customer support they sent me a firmware image and instructions, so I can re-flash the firmware, but that didn't help. I needed to ship the unit back so they can fix it.
After they send me the unit back (apparently they needed to flash some different firmware) it was working all good. However, the firmware (I believe the latest version) has lots of bugs. Just to name a few:
- A memory stick (used to transfer screenshots for example) cannot be mounted reliably. Sometimes it works, sometimes it doesn't.
- After you save some files (limits for example), they cannot be deleted in any way, even if they are not currently used. With screenshots for example that doesn't seem to be a problem.
- Screenshots cannot be saved reliably all the time. If you save a limit file for example and exit the menu, pressing save at any point after that (which normally saves a screenshot) will attempt re-saving the last limit file, without the option to change that.
- The screenshot save windows is visible in the middle of the screen on the saved screenshot. That way it covers a good amount of the spectrum.
- There doesn't seem to be a way to save waveforms.
- You can't create correction files from the menu. You can load correction files, but I don't see any way how to create them (even externally).
- After exiting EMI mode, some of the settings (bandwidth for example) are not remembered but restored to the default value. That could be quite annoying if you often need to switch to EMI mode and back.
- The current version of the user manual is not 100% related to the current version of the firmware. Some option are either different or missing.
- Many other small things.
I hope Siglent will fix the firmware soon, because it is a real pain to work with it in its current state.
^I've seen such units, but buying something old, second hand, without customer support has always seem somewhat dodgy to me. However, it might really turn out to be the better option.Documentation (including service manuals) can often been found online or downloaded somewhere. If a unit is less than 10 years old I'd be surprised if you don't get proper support from the manufacturer. IMHO you can't go wrong with an HP/Agilent/Keysight unit where it comes to support but don't rule out Advantest either because of the close relationship with R&S. My Adventest R3131 SA even has 'R&S calibration void' stickers all over it and I bought it for a very reasonable price from an equipment dealer including a 1 year warranty.
What do you think is the drawback of buying such units, compared to new ones, produced recently? Is documentation readily available?
It is good practise to tell also what is FW version together with this kind of reports.
^I've seen such units, but buying something old, second hand, without customer support has always seem somewhat dodgy to me. However, it might really turn out to be the better option.
What do you think is the drawback of buying such units, compared to new ones, produced recently? Is documentation readily available?
IMHO you can't go wrong with an HP/Agilent/Keysight unit where it comes to support but don't rule out Advantest either because of the close relationship with R&S.
- The screenshot save windows is visible in the middle of the screen on the saved screenshot. That way it covers a good amount of the spectrum.:palm:
Well, I had Siglent gear, and I'm not sure their "support" is something to write home about to be honest. Pretty much everything has to go through their resellers which may or may not be helpful if you have a problem (they are all great until they have your money). If not then, well, tough luck I guess.
I second that! :palm: :palm:- The screenshot save windows is visible in the middle of the screen on the saved screenshot. That way it covers a good amount of the spectrum.:palm:
I don't now about Europe offhand but here in North America the customer can certainly obtain an RMA from us and send a warranty repair directly to Siglent in Ohio. No reseller needs to be involved unless a customer wants them to be.
Our goal is to repair any defective instrument within 10 days of receiving it. We take this goal very seriously.
I second that! :palm: :palm:- The screenshot save windows is visible in the middle of the screen on the saved screenshot. That way it covers a good amount of the spectrum.:palm:
You are truly evil! I already wrote a similar comment but choose not to click 'post' >:DI don't now about Europe offhand but here in North America the customer can certainly obtain an RMA from us and send a warranty repair directly to Siglent in Ohio. No reseller needs to be involved unless a customer wants them to be.That's good to hear (and Siglent should really do the same in Europe), but that covers the hardware only. What about firmware problems? I doubt they'll be fixed within 10 days.
Our goal is to repair any defective instrument within 10 days of receiving it. We take this goal very seriously.
Regarding the tracking generator: can someone verify that with a different spectrum analyser? It looks so bad that it must be a measurement error!
Hmm, I think 1-2dB is fine. But I'd like to see the output level calibrated to zero out the peaks, so it's consistently 0-1dB low instead of going high. Just to avoid overloading external mixers and amplifiers in parts of the spectrum.
Hmm, I think 1-2dB is fine.
40, 80, 120, 160, 200, 240, 280, 520 (!!!), 560, 880, 960 (!!!), 1040 (!!!), 1120 (!!!), 1200, 1560 (!!!)
Frequencies marked with (!!!) are the really bad ones. Because this is my fist spectrum analyzer and I obviously have no EMC shielded room, I don't know if this tone are radiated into the analyzer or picked up internally.
You are truly evil!I don't now about Europe offhand but here in North America the customer can certainly obtain an RMA from us and send a warranty repair directly to Siglent in Ohio. No reseller needs to be involved unless a customer wants them to be.That's good to hear (and Siglent should really do the same in Europe), but that covers the hardware only. What about firmware problems? I doubt they'll be fixed within 10 days.
Our goal is to repair any defective instrument within 10 days of receiving it. We take this goal very seriously.
I already wrote a similar comment but choose not to click 'post' >:D
Regarding the tracking generator: can someone verify that with a different spectrum analyser? It looks so bad that it must be a measurement error!
But maybe I found an other issue, I would like to call it the "40 MHZ problem": I measure relatively high and sharp peaks (RBW 10 Hz) above DNL at 40 Mhz and harmonics, no matter if preamplifier on or off. Some harmonics are really bad, they are 10db above DNL. The critical frequencies are (Mhz):
40, 80, 120, 160, 200, 240, 280, 520 (!!!), 560, 880, 960 (!!!), 1040 (!!!), 1120 (!!!), 1200, 1560 (!!!)
Frequencies marked with (!!!) are the really bad ones. Because this is my fist spectrum analyzer and I obviously have no EMC shielded room, I don't know if this tone are radiated into the analyzer or picked up internally.
One obvious question : up to what SPAN width FFT mode is supported ?This is another interesting question that's worth investigating if someone with the instrument in their possession should find the time to do so. :)
So, please can somebody check with these settings: Center 80 MHz, span 90 Mhz, RBW and VBW 100 Hz, attenuator 50 dBm, trace A maximum hold, trace B average 8 times, detector positive peak.
After 8 sweeps I got the following results:
Average noise: -60.5 dBm
Peak 40 MHz: -46.38 dBm
Peak 80 MHz: -54.80 dBm
Peak 120 MHz: -56.94 dBm
-60.5 dBm average noise floor @ 100Hz RBW ?
I worked it out from the datasheet spec of DANL = -137dBm/Hz with the preamp off in this frequency range.
Add 50dB for the attenuation and then add another 20dB for the 100Hz RBW. So you get -67dBm.
To be fair, without my 40 MHz peaks the DANL is even in some ranges 2 dB below the typical specifications.
Hello, I've been following the thread for weeks : I'm about to get a SA, and the ( budgetwise) options are the Rigol 815 Tg and Siglent SSA3021X with TG option....mainly for amatorial use ( I'm an OM).
Are there any news on how to tell if the TG is the improved one ? I'm quite in a rush to get the SA ASAP, but not sure the one I will get will be the updated one... :-\
Thank you
Andrea
There is a new software program for the SSA3000X's called EasySpectrum. I have used it briefly on several occasions and it has some nice features. EasySpectrum has 3 basic modes of operations:I assume this requires the EMI measurement option on the SA?
[...snip...]
2) An EMI program for pre-compliance testing that mimics much more expensive EMI receivers used at certification labs. It also significantly speeds up these typically slow measurements - when using the quasi-peak detector - by jumping to a zero span mode when a peak response is reached during a scan. I have seen it speed up a quasi-peak detector-based EMI measurement from hours down to a few minutes.
There is a new software program for the SSA3000X's called EasySpectrum. I have used it briefly on several occasions and it has some nice features. EasySpectrum has 3 basic modes of operations:I assume this requires the EMI measurement option on the SA?
[...snip...]
2) An EMI program for pre-compliance testing that mimics much more expensive EMI receivers used at certification labs. It also significantly speeds up these typically slow measurements - when using the quasi-peak detector - by jumping to a zero span mode when a peak response is reached during a scan. I have seen it speed up a quasi-peak detector-based EMI measurement from hours down to a few minutes.
Can the SA do quasi-peak measurements without the EMI option?
Can the internal preamp operate using a high-impedance input (e.g. 1M, 10M) mode with field probes or will such probes require an external LNA with 50ohm source impedance?
Any news on the updated TG?
For guys who may interested in.
1?updated my newly bought SSA3021X to the latest FW 07.05 for twice ?seems some problem with Siglent Startup screen for the first time, so tried again),all work good.
2) The date was wrong after updating, so I changed the date and restart the machine,
3) Then, a, what I got as below photo, 3.2 G and all options opened,,,it saves me thousand of bucks if it valid forever!
is it a bug from Siglent new firmware?? don't exactly know why. Two steps if you wanna to try:
a. update for twice;
b. time modify. And as I think back, I may have enter a wrong date. But how does it possible the system finally display 1970-01-01?
I was hoping it was Shahriar. He does the best SA reviews by far.
Exactly.I was hoping it was Shahriar. He does the best SA reviews by far.That probably depends on how you define your target group.
I have seen a few of his videos, and they are extremely long and complex in the sense that he expectsBe sure after his review there'll be others and maybe they'll be at a newbie level.
that you already are an expert user on spectrum analyzers.
The educational approach from Dave Jones and Jack Gansle are much better in my opinion.For some they're fine, others not
Last thing that you want is a long video, that gets so technical up to the level that the video becomesTo demonstrate that one has more to learn to fully understand the subject.
boring, while at the same time you don't really learn any new things in it. What's the point of such videos? Can anyone tell me please?
Dave Jones has this big red "FAIL" button on the shelf behind his desk, which makes this "big fail" sound when you press it. That's the very same button which I like to press now at this very moment of writing.Well Shahriar it was always going to be after the unprofessional display Dave gave with his review of the SDS1000X.
I was hoping it was Shahriar. He does the best SA reviews by far.
That probably depends on how you define your target group.
I have seen a few of his videos, and they are extremely long and complex in the sense that he expects
that you already are an expert user on spectrum analyzers.
In most of his videos there is some "test filter that I had lying around". This is okey for one video,
but why use this approach over and over in every single video you make? Gets boring!
Moreover I have never seen him write some formulas on a blackboard, to explain some basic
concepts (e.g. Resolution BandWidth versus sweep time), like other people do,
such as Dave Jones and Jack Gansle.
When is the new TG version going to be released and how to ID them?They're out now and ID is explained in point #4 reply #101
I like Shariar's videos, in fact he's the only reviewer who's videos I watch regularly and completely, and the reason is that his videos are at a level of experienced professionals.
Aren't the results of classical tests part of the specification of a spectrum analyser?Yes, but the specs on the datasheet will typically involve some 'weasel wording' to mask performance limitations.
And are relatively low cost spectrum analysers targeted at serious use beyond measuring some simple filters, antenna matching and EMC pre-compliance checking?Probably not, but (generally speaking) the lower in class/cost you go with a spectrum analyser the harder it is to make reliable measurements. i.e. the overall uncertainty tends to go up.
I have seen a few of his videos, and they are extremely long and complex in the sense that he expectsI would say, spectrum analyzer is not a tool for beginners. You must have some background knowledge to understand it and to use it.
that you already are an expert user on spectrum analyzers.
Like I said, I suspect that Shahriar's videos are tailored towards the advanced student/hobbyist. They definitely are not aimed at a professional RF engineer for example. There's too many classic/basic tests missing.
QuoteI like Shariar's videos, in fact he's the only reviewer who's videos I watch regularly and completely, and the reason is that his videos are at a level of experienced professionals.
It depends on what you mean by a professional.
What I find a bit bewildering is that I seem to be the only person who thinks that none of the main bloggers ever reviews a spectrum analyser properly from a technical point of view. i.e. they don't do any of the classic formal tests.
I think that Shahriar's videos are aimed towards the typical 'casual' user of a spectrum analyser in this class. That's fine but some professional users of a spectrum analyser would (hopefully) want to see some formal/classic tests to see if this analyser can qualify to sit on their bench. However, most potential users of this class of instrument won't know (maybe won't even care that much?) if the analyser display is telling the truth about the spectrum it is attempting to measure. So maybe they don't want to see formal testing/comparing. They just want to see the features it offers and how easy it is to 'drive' it.
But if the analyser WAS reviewed properly from a technical point of view they would at least be able to see if it was a contender for serious use professionally.
Like I said, I suspect that Shahriar's videos are tailored towards the advanced student/hobbyist. They definitely are not aimed at a professional RF engineer for example. There's too many classic/basic tests missing.
Finally someone who is on the same page as I am! Thanks for backing!
I like Shariar's videos, in fact he's the only reviewer who's videos I watch regularly and completely, and the reason is that his videos are at a level of experienced professionals. I don't want to sit through having basics which I already know explained over and in extensive length. Simple as that. I don't mind the length because it's filled with interesting stuff.
Shahriar at The Signal Path currently has a SSA3032X he will review as soon as he can.That's great news! Im withholding my purchase until I can compare the SSA3000x and the rigol SA :-+
What I find a bit bewildering is that I seem to be the only person who thinks that none of the main bloggers ever reviews a spectrum analyser properly from a technical point of view. i.e. they don't do any of the classic formal tests.I for one have been quite interested in your comments on various SA's and your obvious knowledge and understanding the field of RF black magic and would/could you consider doing a writeup review on the SSA3000X if approached by Siglent?
But if the analyser WAS reviewed properly from a technical point of view they would at least be able to see if it was a contender for serious use professionally.
Like I said, I suspect that Shahriar's videos are tailored towards the advanced student/hobbyist. They definitely are not aimed at a professional RF engineer for example. There's too many classic/basic tests missing.
Which basic test are you referring to; IIP3, spurs, DANL, Amplitude accuracy, phase noise?
The problem that spectrum analyzers are facing nowadays is that they are like the Swiss army knife, they can do a lot but there is a lot of instruments out there that do each thing better. If you are into phase noise, buy an SSA, if you want a lot of BW you use an oscilloscope with VSA SW and the SA is just the downconverter, if you want to measure S11 and S21 you buy a VNA. This is how it goes in the high end market. So maybe yes, if you test for HAMs there maybe is still a need for basic tests, but for most real world professional users that use PXA, FSW etc. instruments the SA as it is is always something more than just a basic tool.
The complete instrument must work flawlessly to successfully demodulate a signal with 50dB+ of SNR and show the correct EVM. No need for basic tests of each individual component. The same goes to measure that same signal for adjacent channel leakage and receiver noise floor/sensitivity. Maybe I am wrong, but I use these things on a daily basis and if something is wrong with the unit it shows up immediately in the advanced measurements as it would in the basic ones. Maybe I am missing something?
BR
If the video is done well, it can be watched both by beginners and more advanced users.
Please check my posting more careful :)
Basically the videos from Shahriar, lack structure, and don't take up the classical formal tests from the start to the end.
With proper structure in place, educational explanations on a blackboard in between, to not only focus
on the instrument as such, but also about the background technology related to spectrum analyzers, you can do a video that is both learnful, not boring, includes variation, and which is accessible to beginners and more advanced users. With an index at the beginning advanced users can start the video at the proper section.
Like I said before: I think we are looking for a 3rd type of video blogger, next to Dave/Jack and Shahriar.
Nobody is perfect. And there is always room for improvement. If only more video bloggers and forum users would realize this :)
.......Of course and exactly the reason they need be compared to the main brands by someone competent to do so.
So I'm going to argue my point again that the innovative/interesting range of low cost/small/low power/wideband analysers that are hitting the market today should (ideally) be tested to see how well they hold up against the claimed performance in the glossy brochure. The risk that they don't meet these specs is going to be far greater than a conventional bench spectrum analyser made by the classic/top manufacturers.
@G0HZU:
Can you make such a video series? :) You could use both the Siglent SSA3021X and the Rigol DSA815.
If possible also cover the general background about spectrum analyzer technology. Use the models with TG.
I for one have been quite interested in your comments on various SA's and your obvious knowledge and understanding
the field of RF black magic and would/could you consider doing a writeup review on the SSA3000X if approached by Siglent?
.......Of course and exactly the reason they need be compared to the main brands by someone competent to do so.
So I'm going to argue my point again that the innovative/interesting range of low cost/small/low power/wideband analysers that are hitting the market today should (ideally) be tested to see how well they hold up against the claimed performance in the glossy brochure. The risk that they don't meet these specs is going to be far greater than a conventional bench spectrum analyser made by the classic/top manufacturers.
The UI is always going to different to that one is used to but what matters more is can the instrument be trusted as meeting spec.
Would/could you be interested?
That probably depends on how you define your target group.
I have seen a few of his videos, and they are extremely long and complex in the sense that he expects
that you already are an expert user on spectrum analyzers.
In most of his videos there is some "test filter that I had lying around". This is okey for one video,
but why use this approach over and over in every single video you make? Gets boring!
Moreover I have never seen him write some formulas on a blackboard, to explain some basic
concepts (e.g. Resolution BandWidth versus sweep time), like other people do,
such as Dave Jones and Jack Gansle.
Why not break the video in different sections, and make it in such a way, that both beginners and experts can enjoy it. Beginners watch the video from the start. Experts can watch the intro to get info
about where in time their sections of interest start, and then watch those specific parts.
The educational approach from Dave Jones and Jack Gansle are much better in my opinion.
They do have a section that works for beginners. They do use the blackboard for making notes.
I enjoy their videos much more, as they do have charisma. It's not the technical details that count always.
A good video, is a video that works for both a beginner and an expert, and where the speaker has charisma. It's a skill that you can't learn. Either you have it or you don't have it.
Last thing that you want is a long video, that gets so technical up to the level that the video becomes
boring, while at the same time you don't really learn any new things in it. What's the point of such videos? Can anyone tell me please?
If the video is technical and boring, but if you at least really learn something from it, then that's okey,
but if you don't really learn anything in the video, you better spend your time in watching another video :)
Dave Jones has this big red "FAIL" button on the shelf behind his desk, which makes this "big fail" sound when you press it. That's the very same button which I like to press now at this very moment of writing.
FYI.
The RBW on datasheet is 10Hz, but after the upgrade, I noticed it goes to 1Hz!!! Photo as below.
This means I got a totally 'revolutionized' SA with 1449 Euro?
More than satisfied with the SA. :popcorn:
3) Then, a, what I got as below photo, 3.2 G and all options opened,,,it saves me thousand of bucks if it valid forever!
Seems this is the case. :-\3) Then, a, what I got as below photo, 3.2 G and all options opened,,,it saves me thousand of bucks if it valid forever!
:wtf:
It's weird .... to say the least !
So SSA3021X and SSA3032X are HW wise identical and the only difference is the firmware ?
No different to most other brands of TE with models from the same series/family.
This is why there's so many attempted hacks of TE to enable further inbuilt functionality.
You're not the only one. ::)No different to most other brands of TE with models from the same series/family.
This is why there's so many attempted hacks of TE to enable further inbuilt functionality.
Agreed, but in this specific case the price gap between the hacked device and the "legit" one is sooo huge :palm:
But i'm ever more surprised about the self-hacking FW upgrade "gaffe" ... :o
Input terminated with 50ohm N terminator.That is very nice, somehow this SA appeals me more than the dsa815, and although I already have the SA from the Rohde CRTU I wouldn't mind adding this one to my lab
Atten 0, Input Amplifier ON, RBW10kHz (roughly: subtract 40dB for normalize to dBm/Hz, Positive peak average.
Thanks rf-loop for all those tests....Yes, I think you are the only one >:D . I'm still waiting for Signalpath's review to see if it is still a bugfest or not and whether it can be hacked.
Am I the only one who thinks this SA looks like a really good deal?? ;D
I have one ;DPreliminary thoughts Dave?
Yes, I think you are the only one >:D . I'm still waiting for Signalpath's review to see if it is still a bugfest or not and whether it can be hacked.
I have one ;DPreliminary thoughts Dave?
QuoteDave Jones has this big red "FAIL" button on the shelf behind his desk, which makes this "big fail" sound when you press it. That's the very same button which I like to press now at this very moment of writing.Well Shahriar it was always going to be after the unprofessional display Dave gave with his review of the SDS1000X.
He got a fail for that.
Only:Yes, I think you are the only one >:D . I'm still waiting for Signalpath's review to see if it is still a bugfest or not and whether it can be hacked.I was told it can be hacked to 3GHz. If so, it's a bargain and will completely kill the Rigol.
I have one ;DPreliminary thoughts Dave?
Sorry, have done literally nothing with it apart from turn it on for the photo.
But from that, great big screen, heavy, fan a bit annoying, and cheapish look'n'feel on the plastic case.
https://www.eevblog.com/forum/testgear/siglent-sds1000x-series-oscilloscopes/msg823502/#msg823502 (https://www.eevblog.com/forum/testgear/siglent-sds1000x-series-oscilloscopes/msg823502/#msg823502)QuoteDave Jones has this big red "FAIL" button on the shelf behind his desk, which makes this "big fail" sound when you press it. That's the very same button which I like to press now at this very moment of writing.Well Shahriar it was always going to be after the unprofessional display Dave gave with his review of the SDS1000X.
He got a fail for that.
Ok, I'll bite, what was wrong with it?
Only:I count on SW bugs, but im more interested in the HW specs. The former can be fixed with time, but the latter can't. Take for example the SDG2042x, the HW is very good, capable of generating rise times of 4.5ns, and outputting 10Vpp at high frequencies, something the Rigols signal gen can't even dream of. It has however some minor SW issues which are simply unimportant details to me.
IF is stays hackable
IF the advanced features are actually usefull/working and not checkbox features / pray-ware
IF it is free of bugs
BTW I really don't care if something looks cheap on the outside. All test equipment is a light to dark grey box with a display and buttons. Nowadays the Panda-look is hot to make the display look bigger.Agreed
True but how much time does Siglent need to get the firmware to an acceptable level if they aren't there yet? Their software team working on their oscilloscopes is horribly slow; you can count progress in years. OTOH a spectrum analyser is far less complicated from a software point of view so it shouldn't take too long to come up decent firmware but seeing is believing. As a general rule of thumb you have to make sure you can live with the device as it is out of the box with the most recent firmware and not wait for the firmware to mature because that may never happen within a reasonable timeframe.QuoteOnly:I count on SW bugs, but im more interested in the HW specs. The former can be fixed with time, but the latter can't.
IF is stays hackable
IF the advanced features are actually usefull/working and not checkbox features / pray-ware
IF it is free of bugs
Sorry, have done literally nothing with it apart from turn it on for the photo.
But from that, great big screen, heavy, fan a bit annoying, and cheapish look'n'feel on the plastic case.
Yes, I think you are the only one >:D . I'm still waiting for Signalpath's review to see if it is still a bugfest or not and whether it can be hacked.
I was told it can be hacked to 3GHz. If so, it's a bargain and will completely kill the Rigol.
30kHz RBW versus a couple of GHz is close to irrelevant :) . If the frequency response of a filter operating in the GHz area has a 1% accuracy you are already talking about a range of tens of MHz in which the filter meets it's specifications so even a much wider RBW would yield accurate results.
edit: written more clearly
https://www.eevblog.com/forum/testgear/siglent-sds1000x-series-oscilloscopes/msg823502/#msg823502 (https://www.eevblog.com/forum/testgear/siglent-sds1000x-series-oscilloscopes/msg823502/#msg823502)QuoteDave Jones has this big red "FAIL" button on the shelf behind his desk, which makes this "big fail" sound when you press it. That's the very same button which I like to press now at this very moment of writing.Well Shahriar it was always going to be after the unprofessional display Dave gave with his review of the SDS1000X.
He got a fail for that.
Ok, I'll bite, what was wrong with it?
I too cringed when I watched it for the first time.
You're good at what you do, well organised and we know you have to edit an episode to make it watchable while not excluding the important content and of course that's why you now have one in your hands.
What can I say that won't be taken the wrong way other than you looked like a newbie operating his new toy, aimlessly twiddling this and that however if that's done to demonstrate the responsiveness of the UI and resistance to simple lockups......well done, I've overlooked that.https://www.eevblog.com/forum/testgear/siglent-sds1000x-series-oscilloscopes/msg823502/#msg823502 (https://www.eevblog.com/forum/testgear/siglent-sds1000x-series-oscilloscopes/msg823502/#msg823502)QuoteDave Jones has this big red "FAIL" button on the shelf behind his desk, which makes this "big fail" sound when you press it. That's the very same button which I like to press now at this very moment of writing.Well Shahriar it was always going to be after the unprofessional display Dave gave with his review of the SDS1000X.
He got a fail for that.
Ok, I'll bite, what was wrong with it?
I too cringed when I watched it for the first time.
It was a quick "first impressions" review. I did not extensively test it, it was me basically playing around with it for the first time.
With that in mind, what was wrong with it?
I have one in my hand because the local dealer lent me their demo unit as soon as they got it. It did not come from Siglent to me.Thanks to Charles then.
IMHO it is difficult to tell what makes a good review. From a technical buyers perspective I'd like to see a full functional test (especially when it comes to Chinese equipment) so at least I can see it works and how easy it is to operate. However such a video would be boooring :=\ :=\ where was I... oh reviews... All in all I think Dave has to make a tradeoff between showing all the ins & out versus a cursory look to show a device exists and what the pros & cons are when compared to similar products.
Dave functions best when he follows his own motto - "Don't turn it on, take it apart". I find the internal shots and details of the electronic equipment a thousand times more interesting then seeing a basic functional review. It is also generally easier to find someone who shows off the user interface and functions versus seeing what makes a device tick internally as many people are afraid to take stuff apart.
So Dave, don't turn it on(we'll leave that to Shahriar), take it apart!
BTW, I think probably the best way to "review" the SSA is to compare it with the Rigol DSA, as they are basically the only two units on the market in this price point.
I checked the datasheet, it's not that heavy:Sorry, have done literally nothing with it apart from turn it on for the photo.
But from that, great big screen, heavy, fan a bit annoying, and cheapish look'n'feel on the plastic case.
Heavy is good, heavy is reliable ;D
BTW, I think probably the best way to "review" the SSA is to compare it with the Rigol DSA, as they are basically the only two units on the market in this price point.It wouldn't hurt to put an HP/Agilent/Keysight or Advantest spectrum analyser next to it.
Tg option is here:That option sounds like a mere softtware licence key, does it mean that the instrument come anyway with TG HW installed and it's only matter to activate it, even after the purchase ?
http://www.siglent.eu/catalog/product/view/id/1111/s/siglent-tg-ssa3000x-tracking-generator-license/category/98/ (http://www.siglent.eu/catalog/product/view/id/1111/s/siglent-tg-ssa3000x-tracking-generator-license/category/98/)
Did you bought both ?
Did you bought both ?
No, both are on loan.
Is this SSA3000X what you use for playing with SA equipped with new or old HW (afaik, main difference is TG)
If last 6 numbers of serial number is over 160100 (In some old information 160110) then TG is new improved version.
Is it normal selling version or distributors early phase demo version?
Playing with it now.
Both set to 1.5GHz span and same attenuation settings.
The Siglent is an almost exact copy of the Rigol menu system! (not the first time they have done this, they have copied Keysight before)
I looked at Batronix and siglent.eu, they don't even list the UKitSSA3X option.They're all listed in the datasheet and on the Siglent websites:
Anyone knows if this is a new addition to the options?
Playing with it now.
Both set to 1.5GHz span and same attenuation settings.
The Siglent is an almost exact copy of the Rigol menu system! (not the first time they have done this, they have copied Keysight before)
Theres a +20dB noise improvement right there... cio74 you should just hit "buy" with confidence, ask for the latest HW though
Dave have you checked out the new Rigol E variation?
http://www.emona.com.au/products/electronic-test-measure/rf-test-equipment/dsa-832e-865.html#.V2OKxvl97AQ (http://www.emona.com.au/products/electronic-test-measure/rf-test-equipment/dsa-832e-865.html#.V2OKxvl97AQ)
Wonder how that compares to the Siglent.
How much does the noise floor change with the preamps enabled?
How much does the noise floor change with the preamps enabled?
Is this SSA3000X what you use for playing with SA equipped with new or old HW (afaik, main difference is TG)
If last 6 numbers of serial number is over 160100 (In some old information 160110) then TG is new improved version.
Is it normal selling version or distributors early phase demo version?
Serial 2160239, May 2016 build.
It is the new one with the revised hardware. From what I have heard it's the front end they had to revise.
(https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/?action=dlattach;attach=233920;image)
(https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/?action=dlattach;attach=233920;image)
How'd you get the 4 difference traces with the different settings?
Buggered if I can do it...
Every trace have individual settings in trace menu and individual detector setting in detector menu where you select what trace use what detector. And when you want "freeze" one trace just in trace menu select "View". It need work sequentially (do one trace ready and freeze it, do next and freeze..etc. With this method can collect different things to same display).
Every trace have individual settings in trace menu and individual detector setting in detector menu where you select what trace use what detector. And when you want "freeze" one trace just in trace menu select "View". It need work sequentially (do one trace ready and freeze it, do next and freeze..etc. With this method can collect different things to same display).
Yes, I'm trying to do that (get a different RBW for each trace) but it seems buggy or something and doesn't want to leave the trace after I switch. It's weird.
After much struggle with the stupid Trace system, I got this.
1MHz, 100KHz, and 10KHz RBW
QuoteOnly:I count on SW bugs, but im more interested in the HW specs. The former can be fixed with time, but the latter can't.
IF is stays hackable
IF the advanced features are actually usefull/working and not checkbox features / pray-ware
IF it is free of bugs
True but how much time does Siglent need to get the firmware to an acceptable level if they aren't there yet? Their software team working on their oscilloscopes is horribly slow; you can count progress in years. OTOH a spectrum analyser is far less complicated from a software point of view so it shouldn't take too long to come up decent firmware but seeing is believing. As a general rule of thumb you have to make sure you can live with the device as it is out of the box with the most recent firmware and not wait for the firmware to mature because that may never happen within a reasonable timeframe.
Following up on this topic, I did report a bug 20 days ago on the sdg2042x ( actually tautech reported it to them :) ), today a new firmware is available addressing that isssue and adding the capability of combining both output channels... So from my point of view they were pretty responsive. :popcorn:Agreed! They even fixed the external reference issue I had. :-+
How much does the noise floor change with the preamps enabled?
Signal generators where the first real instruments they made (SDG1000 series) and the early versions where useable but far from complete. I'm also under the impression that Siglent has different software teams on different instruments so the update frequency on one product line does not necessarily says something about the update frequency on the other product lines. Because they have been doing signal generators for such a long time it is to be expected they can fix bugs quickly. However the spectrum analyser is (AFAIK) the latest addition so the software team is likely new as well.Following up on this topic, I did report a bug 20 days ago on the sdg2042x ( actually tautech reported it to them :) ), today a new firmware is available addressing that isssue and adding the capability of combining both output channels... So from my point of view they were pretty responsive. :popcorn:Agreed! They even fixed the external reference issue I had. :-+
However the spectrum analyser is (AFAIK) the latest addition so the software team is likely new as well.
It is very interesting to see a difference greater than 20dB between the 1MHz and 10kHz RBW. This might be due to a difference in filer shape?
BR
Works just simply and rock solid without any hassle.
Swatting up a bit on these myself and the Quick Start guide gives little instructive help while the User manual is much better. There's a inbuilt Help system that after selection any further keys pressed will give assistance on that topic to the user and to exit press Help again.Works just simply and rock solid without any hassle.
No, it's a hassle if you don't know the exact sequence to get it working to do that. It is non-obvious IMO.
It would be useful for those watching at home to know if the Help is any help at all. :-//
Phase noise for a 1GHz 0dBm carrier from my Rubidium + Marconi 2030 for a 1MHz offset on both the Rigol and Siglent.
Significantly different PLL responses.
Why does Siglent show no warning that input power 0dBm is higher than Ref -40dBm, Rigol shows UNCAL warning.
Why does Siglent show no warning that input power 0dBm is higher than Ref -40dBm, Rigol shows UNCAL warning.
That's not what the UNCAL warning is for on the Rigol, it has to do with sweep time.
The Siglent will eventually show an "ADC overload" warning message and beep continually if the input is overloaded.
Phase noise for a 1GHz 0dBm carrier from my Rubidium + Marconi 2030 for a 1MHz offset on both the Rigol and Siglent.
Significantly different PLL responses.
Very strange picture on Siglent.
Why does Siglent show no warning that input power 0dBm is higher than Ref -40dBm, Rigol shows UNCAL warning.
Why trace peak on Siglent is much much lower (-65dBm) than actual input power (0dBm) ?
That's not what the UNCAL warning is for on the Rigol, it has to do with sweep time.Exactly. In this setting everything below 100Hz RBW will show the UNCAL on the Rigol; in other cases in might appear earlier or later, probably depending on the sweep time.
The Siglent will eventually show an "ADC overload" warning message and beep continually if the input is overloaded.
Why does Siglent show no warning that input power 0dBm is higher than Ref -40dBm, Rigol shows UNCAL warning.
That's not what the UNCAL warning is for on the Rigol, it has to do with sweep time.
The Siglent will eventually show an "ADC overload" warning message and beep continually if the input is overloaded.
Can you explain what those images are supposed to show please, cos it's making no sense to me to set the ref to -40dBm and feed in an 0dBm signal.
Why does Siglent show no warning that input power 0dBm is higher than Ref -40dBm, Rigol shows UNCAL warning.
That's not what the UNCAL warning is for on the Rigol, it has to do with sweep time.
The Siglent will eventually show an "ADC overload" warning message and beep continually if the input is overloaded.
Can you explain what those images are supposed to show please, cos it's making no sense to me to set the ref to -40dBm and feed in an 0dBm signal.
We can set reference level lower than signal peak level. But, there need be careful also and know what do so that result in sideband is still valid. I will later show some test images what may explain this better but this may take bit time due to queued work and hobby situation.
Basic fundamentals of spectrum analyzers may also help.
Why trace peak on Siglent is much much lower (-65dBm) than actual input power (0dBm) ?
Why does Siglent show no warning that input power 0dBm is higher than Ref -40dBm, Rigol shows UNCAL warning.
That's not what the UNCAL warning is for on the Rigol, it has to do with sweep time.
The Siglent will eventually show an "ADC overload" warning message and beep continually if the input is overloaded.
Can you explain what those images are supposed to show please, cos it's making no sense to me to set the ref to -40dBm and feed in an 0dBm signal.
We can set reference level lower than signal peak level. But, there need be careful also and know what do so that result in sideband is still valid. I will later show some test images what may explain this better but this may take bit time due to queued work and hobby situation.
Basic fundamentals of spectrum analyzers may also help.
Interesting - so you are overdriving it for a portion of the sweep so that you have enough sensitivity left to see the sideband?
The SA I use has a phase noise mode for doing that and the dBc conversion. Possibly because it does not show anything like a sensible trace when overdriven to that level. I didn't realise other types permit it.
Not only is the 10dB attenuator set, the Siglent also has 10x averaging turned on.
Can you show a 10MHz signal with a 1MHz span at 30Hz RBW to verify Pinkus used the wrong settings which caused the wrong results?
Why trace peak on Siglent is much much lower (-65dBm) than actual input power (0dBm) ?
Because in this case Siglent use Detector mode what is ok for measure noise (average), not ok for measure signal peaks. Independent of this, there is still 0dBm signal what, due to phase noise, is rising sideband (noise) level what is (in principle) ok - exept that I suspect bit this result....
See edited postCan you show a 10MHz signal with a 1MHz span at 30Hz RBW to verify Pinkus used the wrong settings which caused the wrong results?
Why trace peak on Siglent is much much lower (-65dBm) than actual input power (0dBm) ?
Because in this case Siglent use Detector mode what is ok for measure noise (average), not ok for measure signal peaks. Independent of this, there is still 0dBm signal what, due to phase noise, is rising sideband (noise) level what is (in principle) ok - exept that I suspect bit this result....
Can you show a 10MHz signal with a 1MHz span at 30Hz RBW to verify Pinkus used the wrong settings which caused the wrong results?I edited my post above. The problem was VideoAverage mode on "ON" (I tried to use the same basic settings Dave was using). The same problem applies to Daves shot. As of this there is not enough data on the screen for the average, thus not enough data. With VideoAverage "Off" or a smaller SPAN (=more data) it is fine.
Can you show a 10MHz signal with a 1MHz span at 30Hz RBW to verify Pinkus used the wrong settings which caused the wrong results?
Why trace peak on Siglent is much much lower (-65dBm) than actual input power (0dBm) ?
Because in this case Siglent use Detector mode what is ok for measure noise (average), not ok for measure signal peaks. Independent of this, there is still 0dBm signal what, due to phase noise, is rising sideband (noise) level what is (in principle) ok - exept that I suspect bit this result....
Can you show a 10MHz signal with a 1MHz span at 30Hz RBW to verify Pinkus used the wrong settings which caused the wrong results?
Why trace peak on Siglent is much much lower (-65dBm) than actual input power (0dBm) ?
Because in this case Siglent use Detector mode what is ok for measure noise (average), not ok for measure signal peaks. Independent of this, there is still 0dBm signal what, due to phase noise, is rising sideband (noise) level what is (in principle) ok - exept that I suspect bit this result....
@Pinkus. If you still have available Rigol also, please look 1kHz span 100Hz RBW and example 4k span with 0dB signal and using normal pos peak and video average detectors and so that ref is also 0dBm. (perhaps you need also use some 2-5 times trace averaging for more steady image?)OK - done. Almost in the last minute...the Rigol is gone now - no more comparison possible.
Because, there is real drop out game.
Still I'm not sure whether it is correct the signal shows so low on the SSA3000 when using the normal detector. I just tried with my Advantest SA and with RBW=1kHz and VBW=10Hz a 0dBm signal stays at 0dBm. Could it be Siglent compresses multiple points into a single point by taking the average of several measurements instead of the maximum measured value?
Yes, but what happens if to decrease the RBW to 30Hz with a 1MHz span? IMHO normal detector mode should give a level around 0dBm.
Yes, but what happens if to decrease the RBW to 30Hz with a 1MHz span? IMHO normal detector mode should give a level around 0dBm.
The Siglent certainly appears to put the Rigol in the shade re phase noise. But (I'm sorry, I can't resist this as I've had an early Scotch & Dry...) My little Signal Hound SA44b does even better:
Moving in to 1KHz span and 10 Hz RBW begins to show the Hound's very close in noise:
(https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/?action=dlattach;attach=234563;image)
Apologise if I have missed it, have someone injected or/and sweep a signal very close to the noise floor level, say -80dBm, is it properly displayed/measured?Here you go: 0dB signal with external attenunator switched to
Thanks.
Apologise if I have missed it, have someone injected or/and sweep a signal very close to the noise floor level, say -80dBm, is it properly displayed/measured?
Thanks.
Here is the 10MHz phase noise comparison at 10KHz offset with a -110dBc source.
No contest, the Siglent wins hands down.
Here is the 10MHz phase noise comparison at 10KHz offset with a -110dBc source.
No contest, the Siglent wins hands down.
In Daves video at around 38:30 it shows a unit with firmware 100.01.02.07.06.I'm guessing it's a beta FW, we do occasionally get pre-release beta FW versions sent to us.
I am wondering where this FW 07.06 comes from, as the latest official available firmware is 07.05?
The amplifier on the 1st IF is a hmc716, so the frequency is between 3.1 and 3.9GHz.
Can anyone read the part number on U83/U84 (bottom right of picture)?
Do we know yet what the real-time FFT span is?The SAW filters have a 3dB BW of 15MHz and a flat passband region of 6Mhz, so I would guess the real time range is around 10MHz?
Pic.....How did yo do that^^^
Mode: 3.2GHz
Pic....
Mode: 2.1GHz
2.1GHz model and 3.2GHz model,
Pic.....How did yo do that^^^
Mode: 3.2GHz
Pic....
Mode: 2.1GHz
2.1GHz model and 3.2GHz model,
Have you 2 units or 1 improved model? >:D
:-DDPic.....How did yo do that^^^
Mode: 3.2GHz
Pic....
Mode: 2.1GHz
2.1GHz model and 3.2GHz model,
Have you 2 units or 1 improved model? >:D
Magic under the polar lights, dual personality, speaks during the day and at night she howls like a wolf.
Pic.....How did yo do that^^^
Mode: 3.2GHz
Pic....
Mode: 2.1GHz
2.1GHz model and 3.2GHz model,
Have you 2 units or 1 improved model? >:D
Magic under the polar lights, dual personality, speaks during the day and at night she howls like a wolf.
.... 2) there is a free PC software called EasySpectrum, this works good. You can save the screen picture to PC with a black or white background.@Deuze: On my SSA3021x with firmware 07.05, the software Easyspectrum will not start. It shows an errror message that my firmware is not the latest one (which it is). When I downgrade to 07.03, everything is fine. Can you confirm this behaviour on your machine too?
If the video is done well, it can be watched both by beginners and more advanced users.
Please check my posting more careful :)
Basically the videos from Shahriar, lack structure, and don't take up the classical formal tests from the start to the end.
With proper structure in place, educational explanations on a blackboard in between, to not only focus
on the instrument as such, but also about the background technology related to spectrum analyzers, you can do a video that is both learnful, not boring, includes variation, and which is accessible to beginners and more advanced users. With an index at the beginning advanced users can start the video at the proper section.
Like I said before: I think we are looking for a 3rd type of video blogger, next to Dave/Jack and Shahriar.
Nobody is perfect. And there is always room for improvement. If only more video bloggers and forum users would realize this :)
On mine with version 07.05 is connected to LAN and shows up in the Home network list in the ADSL modem. However, in the "Connect" dialog box it does not show up (It shows my SDM3055 though). It is a bug :(.... 2) there is a free PC software called EasySpectrum, this works good. You can save the screen picture to PC with a black or white background.@Deuze: On my SSA3021x with firmware 07.05, the software Easyspectrum will not start. It shows an errror message that my firmware is not the latest one (which it is). When I downgrade to 07.03, everything is fine. Can you confirm this behaviour on your machine too?
I did connect it through USB (the connector on the back side) to the PC, not LAN.On mine with version 07.05 is connected to LAN and shows up in the Home network list in the ADSL modem. However, in the "Connect" dialog box it does not show up (It shows my SDM3055 though). It is a bug :(.... 2) there is a free PC software called EasySpectrum, this works good. You can save the screen picture to PC with a black or white background.@Deuze: On my SSA3021x with firmware 07.05, the software Easyspectrum will not start. It shows an errror message that my firmware is not the latest one (which it is). When I downgrade to 07.03, everything is fine. Can you confirm this behaviour on your machine too?
On mine with version 07.05 is connected to LAN and shows up in the Home network list in the ADSL modem. However, in the "Connect" dialog box it does not show up (It shows my SDM3055 though). It is a bug :(Welcome to the forum.
So, both LAN and USB do not work. I noticed today: if I leave EasySpectrum running and the connect dialog open sometimes the SSA will say "press escape to go local". So the PC it is trying to connect.Interesting.....
Dear Siglent,
Have you investigated the issue with a ghost frequency that Dave reported in his review video?
He could find a ghost frequency in the spectrum, that seemed to come from the internal electronics in the spectrum analyzer itself.
There is a good chance Siglent are aware of this and you may have noticed the unit Dave did his EEVblog review with had FW version 7.06 installed. We have yet to see this version offered publicly however I'll point Siglent tech support to your post so we can get some idea if there is an outstanding LAN connection problem and when it will be fixed.I updated my SSA to version 07.07, EasySpectrum to 03SP1, and the VISA drivers to 15.5 and it works now! :popcorn:
Image frequencies
fin – 2 × 21.4 MHz < –70 dBc, typ. –80 dBc
fin – 2 × 831.4 MHz < –70 dBc, typ. –90 dBc
fin – 2 × 4881 MHz –60 dBc
Intermediate frequencies
21.4 MHz, 831.4 MHz, 4881.4 MHz –60 dBc, typ. –80 dBc
8931.4 MHz –50 dBc
Other interfering signals,
signal level – RF attenuation < –20 dBm
f ? 3.6 GHz
spurious at fin – 2440.7 MHz < –60 dBc
3.6 GHz < f ? 6 GHz
spurious at fin – 4465.7 MHz < –60 dBc
Other interfering signals,
related to local oscillators
f ? 3.6 GHz
?f < 300 kHz –60 dBc
?f ? 300 kHz < –60 dBc
f > 3.6 GHz
?f < 300 kHz –54 dBc
?f ? 300 kHz < –54 dBc
f = receive frequency
Residual spurious response
input matched with 50 ohm,
without input signal, RBW < 30 kHz,
f ? 3 MHz, RF attenuation = 0 dB,
tracking generator = OFF
< –90 dBm
Residual response (= Residual spurious response)
input terminated = 50 ohm, attenuation = 0 dB
<-90 dBm,typ.
Spectrum Analyzer Residual Spurious Response
When the RF input is terminated, the spectrum analyzer may still show discrete responses while the LO's are sweeping. This occurs because at certain LO frequencies, the harmonics of the first and second LO mix together forming a product that is equal to an IF frequency. If this "spurious" IF frequency gets into the IF path, the detector will see a signal and therefor the display will show a blip at the RF frequency where m*LO1-n*LO2 = +/-IF. IF can be any of the IF frequencies in the instrument.
Re: New FirmwareThanks.
Apparently no more system lock ups when manually adjusting the bandwidth!
... issue with a ghost frequency that Dave reported in his review video?
In all T&M instruments, all what you see are errors and lies mixed with illusions of reality.:-+ Too bad this text is too long for a T-shirt though.
Re: New FirmwareThanks.
Apparently no more system lock ups when manually adjusting the bandwidth!
Please tell us more.....previous firmware? Was it an ongoing problem?
I don't think I've seen this problem mentioned before. :-//
...
(later how it looks with SSA TG)
So the TG is only in a +-2dB range up to approx. 2.7 Ghz.
Fine for me.... :) but good to know.
Is it too costly to make a spectrum analyzer with zero spurious response, or is it just impossible by design, based on the topology and build up of the various stages in the spectrum analyzer?
Considering the Spurious Performance of
Spectrum Analyzers
Measuring low level spurs requires care even when the
spectrum analyzer’s Displayed Average Noise Level has
sufficient margin to perform the required measurements.
All spectrum analyzers create artifacts or spurs that can
appear at low levels. Some spurs are created internally by the
Spectrum Analyzer’s circuitry. Others are generated inside the
instrument as a result of input signal interactions with internal
signals and non-linear circuit behavior. These unwanted
signals, typically related to harmonics of the input signal, are
highly dependent on the maximum signal level present in the
input, even when the large signal lies outside the displayed
span.
Residuals
Residual Spurious responses are internally generated spurs
that exist in all spectrum analyzers and are independent of
any input signal. These unwanted signal components are
the result of imperfect isolation between the various signal
paths inside the spectrum analyzer and can come from digital
clocks, local oscillators or switching power supplies. Spectrum
analyzers are regularly used to measure spurs far below their
Residual Spurious specifications. One technique to account
for these residual signals is to measure them by taking a spur
sweep with the input terminated. The resulting list of spur
locations and levels can be tabulated and then removed from
the subsequent measurement results. Residual Spurious
are expressed as an absolute power level, specified in dBm.
This means they do not change level with any input. The
specification for the RSA6120B is -90 dBm for frequencies
from 40 MHz to 200MHz, and -95 dBm (-110 dBm Typical)
from 200 MHz to 20 GHz. These signals must be well
understood to ensure they are not mistakenly included in the
results as they may not be from the DUT.
Spurious with Signal
Spurious with Signal Present or signal-related spurs are the
result of unintended interactions between the input signal
and the various internal clocks and local oscillators that are
part of the spectrum analyzer’s circuitry. Most signal-related
spurs are caused by non-linear behavior in the spectrum
analyzer’s circuitry and are highly dependent on the levels
of signals present at the spectrum analyzer input. There are
several types of signal-related spurs which are often specified
separately. They include image rejection, harmonics, third
order intermodulation, second order intermodulation, etc.
The specifications for signal-related spurs are usually in terms
of dB below the input signal level or dBc. Signal related
spurs specifications are especially relevant if a low level spur
search must be made in the presence of a high level signal.
Measuring spurs in a transmitter output, for example, may
require the measurement of spurs at the -120 dBm level as in
our example while the transmitters intended output signal has
a power of several watts. In these cases, it might be required
to filter out the transmitter’s signal (notch filter) to make sure
that its level does not exceed the input level specified in the
analyzer’s spurious specifications.
All spectrum analyzers publish spurious with signal
specifications that vary with acquisition BW and input
frequency at a specified level of input signal. The RSA6120B,
for example, performance varies from -78 dBc to -70 dBc
depending settings with a maximum signal level of -25 dBm
after RF attenuation. The option 51 preamplifier, when used,
would typically achieve similar performance with a maximum
input signal at approximately a 30 dB lower level.
Harmonics
These unwanted signals can appear whenever the analyzer
is tuned to N times the frequency of a signal present at the
input (N is an integer). The most relevant is the 2nd-harmonic
specification (N=2). The RSA6100B Series specifies 80 dBc
harmonics for -25 dBm input signals with no RF attenuation
and preamplifier off. The Option 51 preamplifier, when used,
would typically achieve similar performance with a maximum
input signal at -55 dBm with no RF attenuation.
Predicting the spurious behavior with Input is usually more
difficult than harmonics or residual spurious. A detailed
analysis requires knowledge of the frequency conversion
stages internal to the Spectrum Analyzer (Local Oscillators,
IF frequencies, ADC clocks, etc.) These kinds of spurs will
be present at frequencies related the mixing of internal
frequencies and harmonics of the input. For example, if one of
the local oscillators in a spectrum analyzer is at 9 GHz, then
signals harmonically related to the combination of the input
signal and 9 GHz could show up as spurs.
If the spurious response comes from the device internals itself, isn't there an easy way to characterize the spurious response for a spectrum analyzer under no load, and calibrate, adjust, and eliminate it from the readings?
Or would that spurious response be unstable over time, depending on external parameters, such as electro-magnetic noise, interference, reflection, ambient temperature?
For comparison: Are all spectrum analyzers subject to this? How does the Rigol DSA185-TG perform on this front?
Is it too costly to make a spectrum analyzer with zero spurious response, or is it just impossible by design, based on the topology and build up of the various stages in the spectrum analyzer?
Are there different variations possible in the build up of the various stages in the spectrum analyzer,
and are some variations less subject to spurious response compared to others?
Is the build up of the stages in most spectrum analyzers the same or very similar, or are there 2 or more fundamental variations and approaches that are completely different from each other, and that have a completely different internal spurious response by design?
What about the spurious response (both internal spurs without signals connected, or spurs as a result of the interaction with a connected signal) in an analog spectrum analyzer versus the spurious response in a digital spectrum analyzer?As suggested study replies #298 and #314.
Maybe analog spectrum analyzers are better in this field? Or are they worse?
How is the analog spectrum analyzer HP 8560E doing in this field, in comparison with the digital spectrum analyzer Siglent SSA3021X? Any clear winner to identify in terms of low to zero spurious response? (both internal spurs without signals connected, or spurs as a result of the interaction with a connected signal)
What about the spurious response (both internal spurs without signals connected, or spurs as a result of the interaction with a connected signal) in an analog spectrum analyzer versus the spurious response in a digital spectrum analyzer?
Maybe analog spectrum analyzers are better in this field? Or are they worse?
...
That's better, only 2 Hz off without an external reference. :phew:
Not having a frequency counter I wasn't sure what to expect but I did know there are many that use the SDG1k series externally referenced and some even rework/replace the internal reference for better accuracy. There's quite a bit of discussion about that in the SDG1000 and 800 thread.That's better, only 2 Hz off without an external reference. :phew:
Impressive! At 40 MHz thats 50ppb isn't it? :-+
20Hz out in the previous post is 2ppm by the same logic.
I don't know if thats the correct way to calculate it, the beauty of EEVBlog is there is always someone who knows.
A few tweaks later in manual mode revealed what I was looking for.
108 Hz out. :scared:
But from the SDS2kX datasheet:
SDS2000X series AWG Frequency Accuracy ±50 ppm
A few tweaks later in manual mode revealed what I was looking for.
108 Hz out. :scared:
But from the SDS2kX datasheet:
SDS2000X series AWG Frequency Accuracy ±50 ppm
Isn't it funny how all SDS2k(X) seem to run a little high in terms of internal reference frequency?
My measurements with 25MHz out of the WaveGen:
SDS2k: +440Hz (+17.6ppm)
SDS2kX: +333Hz (+13.3ppm)
My standalone Function Genrator is specified to +/-100ppm for 1 year over the temperature range of 18°C ~ 28°C, and right now it's +29.2°C here in my home lab and the instrument is several years old without recalibration. And guess what? It is just 38Hz high at 25MHz, which is only +1.5ppm. This is what I'm used to with all my equipment and I have always wondered why Siglent seems to struggle to do the same...
The winner amongst the SDS2k(X) instruments so far is your SDS2kX with just +108Hz (+4.3ppm). :-+
Not sure how accurate the measurement with the SSA3kX is though. Yes, according to the data sheet, internal reference of the SA should be within 1ppm, but the marker peak search might also be a little off.
Unless the SA has a built-in true frequency counter (some have), it isn't the instrument of choice for me when it comes to highly accurate frequency measurements. Of course it should be fine as long as we're talking about a couple of ppm, but you really cannot trust it whenever you want accuracies better than that... ;)
Ha, funny how all these inbuilt AWG's so far have been a little high in frequency.A few tweaks later in manual mode revealed what I was looking for.
108 Hz out. :scared:
But from the SDS2kX datasheet:
SDS2000X series AWG Frequency Accuracy ±50 ppm
Isn't it funny how all SDS2k(X) seem to run a little high in terms of internal reference frequency?
My measurements with 25MHz out of the WaveGen:
SDS2k: +440Hz (+17.6ppm)
SDS2kX: +333Hz (+13.3ppm)
My standalone Function Genrator is specified to +/-100ppm for 1 year over the temperature range of 18°C ~ 28°C, and right now it's +29.2°C here in my home lab and the instrument is several years old without recalibration. And guess what? It is just 38Hz high at 25MHz, which is only +1.5ppm. This is what I'm used to with all my equipment and I have always wondered why Siglent seems to struggle to do the same...
The winner amongst the SDS2k(X) instruments so far is your SDS2kX with just +108Hz (+4.3ppm). :-+
Not sure how accurate the measurement with the SSA3kX is though. Yes, according to the data sheet, internal reference of the SA should be within 1ppm, but the marker peak search might also be a little off.
Unless the SA has a built-in true frequency counter (some have), it isn't the instrument of choice for me when it comes to highly accurate frequency measurements. Of course it should be fine as long as we're talking about a couple of ppm, but you really cannot trust it whenever you want accuracies better than that... ;)
476 Hz low. :o
Be carefull which reference point to choose. Basically you can't measure more accurately than the accuracy specs of the clock source in the SA or generator.::)
Be carefull which reference point to choose. Basically you can't measure more accurately than the accuracy specs of the clock source in the SA or generator.
I just see a lot of comparing between various generators going on without mentioning what frequency reference is being used.Be carefull which reference point to choose. Basically you can't measure more accurately than the accuracy specs of the clock source in the SA or generator.::)
And you never took the moment to read rf-loops reply above. :palm:
I just see a lot of comparing between various generators going on without mentioning what frequency reference is being used.Be carefull which reference point to choose. Basically you can't measure more accurately than the accuracy specs of the clock source in the SA or generator.::)
And you never took the moment to read rf-loops reply above. :palm:
I guess my name has the same effect on you :) So no, I was just making a comment about Tautech's screendumps and the good habit of questioning the meaning of measurement results in general. He compares his generators with eachother and makes comments on their frequency being off based on -appearantly- the clock in his spectrum analyser. Statiscally it is odd that all generators he tested deviate in the same direction. It could happen but it requires some more investigation to determine whether his spectrum analyser is a bit off or the generators all are slightly high. When measuring 10MHz the 1ppm reference in the spectrum analyser has an error of +/-10Hz. At >50ppm accuracy the SDG1010 may be off by +/-500Hz at 10MHz.I just see a lot of comparing between various generators going on without mentioning what frequency reference is being used.Be carefull which reference point to choose. Basically you can't measure more accurately than the accuracy specs of the clock source in the SA or generator.::)
And you never took the moment to read rf-loops reply above. :palm:
It looks like name Siglent generate some biased blind point in your eyes.
My turn.I guess my name has the same effect on you :) So no, I was just making a comment about Tautech's screendumps and the good habit of questioning the meaning of measurement results in general. He compares his generators with eachother and makes comments on their frequency being off based on -appearantly- the clock in his spectrum analyser. Statiscally it is odd that all generators he tested deviate in the same direction. It could happen but it requires some more investigation to determine whether his spectrum analyser is a bit off or the generators all are slightly high. When measuring 10MHz the 1ppm reference in the spectrum analyser has an error of +/-10Hz. At >50ppm accuracy the SDG1010 may be off by +/-500Hz at 10MHz.I just see a lot of comparing between various generators going on without mentioning what frequency reference is being used.Be carefull which reference point to choose. Basically you can't measure more accurately than the accuracy specs of the clock source in the SA or generator.::)
And you never took the moment to read rf-loops reply above. :palm:
It looks like name Siglent generate some biased blind point in your eyes.
A few tweaks later in manual mode revealed what I was looking for.
108 Hz out. :scared:
But from the SDS2kX datasheet:
SDS2000X series AWG Frequency Accuracy ±50 ppm
Isn't it funny how all SDS2k(X) seem to run a little high in terms of internal reference frequency?
My measurements with 25MHz out of the WaveGen:
SDS2k: +440Hz (+17.6ppm)
SDS2kX: +333Hz (+13.3ppm)
My standalone Function Genrator is specified to +/-100ppm for 1 year over the temperature range of 18°C ~ 28°C, and right now it's +29.2°C here in my home lab and the instrument is several years old without recalibration. And guess what? It is just 38Hz high at 25MHz, which is only +1.5ppm. This is what I'm used to with all my equipment and I have always wondered why Siglent seems to struggle to do the same...
The winner amongst the SDS2k(X) instruments so far is your SDS2kX with just +108Hz (+4.3ppm). :-+
Not sure how accurate the measurement with the SSA3kX is though. Yes, according to the data sheet, internal reference of the SA should be within 1ppm, but the marker peak search might also be a little off.
Unless the SA has a built-in true frequency counter (some have), it isn't the instrument of choice for me when it comes to highly accurate frequency measurements. Of course it should be fine as long as we're talking about a couple of ppm, but you really cannot trust it whenever you want accuracies better than that... ;)
Marker peak tracking is quite accurate. Much better than 1Hz resolution what it show. When follow it, it discipline very accurately to peak and follow it. When I take this image it some times move ine pixel left or right and some times it also show 10MHz but mostly 1Hz less.
Signal is coming from Rb (Rb error sure less than +/- 5mHz but I do not promise more because there is time when I have adjusted it)
Same signal is also reference for HP83131A for measure SSA3000X 10MHz Ref Out.
It is bit high, (so, SA readings bit low). When I take this image SSA Ref Out freq is around 10 000 000.430 Hz after over half hour stabilizing time (some first minutes it really sweep lot, nearly like ocxo)
But If turn (in marker functions) freq counter on (yes there is), there is some (perhaps systematic) small error. This counter resolution is 1Hz also with GHz range.
But, in this image it is not used. This is just with normal marker and tracking on.
Also if set scale to 10dB/div this peak top is wide but still it discipline marker very accurate to top middle, even when part of trace peak top looks straight horizontal line (due to TFT resolution) still marker is well adjusted to center
Resolution is something different than accuracy. With an internal reference accuracy of 1ppm in the SSA3000 measuring a 1GHz signal has an accuracy of +/-1000Hz so when the marker says it is at 1 000 000 000 Hz in reality the frequency can be anywhere between 999 999 000 Hz and 1 000 001 000 Hz.Oh for heavens sake.
I don't doubt rf-loop has the equipment to do that but the thing is that when it comes to drawing conclusions from measurements you have to go by the accuracy specification for the instrument. If rf-loop's SSA3000X happends to be accurate within 0.05ppm (for example) that doesn't mean the SSA3000X you have or which I could get has the same (initial) accuracy. Siglent specifies it will be accurate within 1ppm over a certain time and temperature range so that is as sure as you can get without using an external (more accurate) frequency reference.Resolution is something different than accuracy. With an internal reference accuracy of 1ppm in the SSA3000 measuring a 1GHz signal has an accuracy of +/-1000Hz so when the marker says it is at 1 000 000 000 Hz in reality the frequency can be anywhere between 999 999 000 Hz and 1 000 001 000 Hz.Oh for heavens sake.
rf-loop has made that statement based on fact.....by verification of the frequency counters accuracy.
Do you doubt he has the equipment to do that?
:blah: :blah: :blah:I don't doubt rf-loop has the equipment to do that but the thing is that when it comes to drawing conclusions from measurements you have to go by the accuracy specification for the instrument. If rf-loop's SSA3000X happends to be accurate within 0.05ppm (for example) that doesn't mean the SSA3000X you have or which I could get has the same (initial) accuracy. Siglent specifies it will be accurate within 1ppm over a certain time and temperature range so that is as sure as you can get without using an external (more accurate) frequency reference.Resolution is something different than accuracy. With an internal reference accuracy of 1ppm in the SSA3000 measuring a 1GHz signal has an accuracy of +/-1000Hz so when the marker says it is at 1 000 000 000 Hz in reality the frequency can be anywhere between 999 999 000 Hz and 1 000 001 000 Hz.Oh for heavens sake.
rf-loop has made that statement based on fact.....by verification of the frequency counters accuracy.
Do you doubt he has the equipment to do that?
For example: earlier this year I bought a Keysight 6.5 digit DMM for a project. It's calibration sheet shows the readings during factory calibration are well within it's accuracy specification but still I can't say it will always perform better than specified based because it worked so well during it's factory calibration. It has been transported, went through temperature cycles, was switched on/off several times, humidity changes, etc which could have changed it's reference a little bit. Keysight's specs guarantees it will meet a certain level of accuracy but there is no way for me to tell how much it has actually drifted.
Again you fail to read a post for the info contained within and are blatantly trolling.I guess my name has the same effect on you :) So no, I was just making a comment about Tautech's screendumps and the good habit of questioning the meaning of measurement results in general. He compares his generators with eachother and makes comments on their frequency being off based on -appearantly- the clock in his spectrum analyser. Statiscally it is odd that all generators he tested deviate in the same direction. It could happen but it requires some more investigation to determine whether his spectrum analyser is a bit off or the generators all are slightly high. When measuring 10MHz the 1ppm reference in the spectrum analyser has an error of +/-10Hz. At >50ppm accuracy the SDG1010 may be off by +/-500Hz at 10MHz.I just see a lot of comparing between various generators going on without mentioning what frequency reference is being used.Be carefull which reference point to choose. Basically you can't measure more accurately than the accuracy specs of the clock source in the SA or generator.::)
And you never took the moment to read rf-loops reply above. :palm:
It looks like name Siglent generate some biased blind point in your eyes.
Ha, funny how all these inbuilt AWG's so far have been a little high in frequency.A few tweaks later in manual mode revealed what I was looking for.
108 Hz out. :scared:
But from the SDS2kX datasheet:
SDS2000X series AWG Frequency Accuracy ±50 ppm
Isn't it funny how all SDS2k(X) seem to run a little high in terms of internal reference frequency?
My measurements with 25MHz out of the WaveGen:
SDS2k: +440Hz (+17.6ppm)
SDS2kX: +333Hz (+13.3ppm)
My standalone Function Genrator is specified to +/-100ppm for 1 year over the temperature range of 18°C ~ 28°C, and right now it's +29.2°C here in my home lab and the instrument is several years old without recalibration. And guess what? It is just 38Hz high at 25MHz, which is only +1.5ppm. This is what I'm used to with all my equipment and I have always wondered why Siglent seems to struggle to do the same...
The winner amongst the SDS2k(X) instruments so far is your SDS2kX with just +108Hz (+4.3ppm). :-+
Not sure how accurate the measurement with the SSA3kX is though. Yes, according to the data sheet, internal reference of the SA should be within 1ppm, but the marker peak search might also be a little off.
Unless the SA has a built-in true frequency counter (some have), it isn't the instrument of choice for me when it comes to highly accurate frequency measurements. Of course it should be fine as long as we're talking about a couple of ppm, but you really cannot trust it whenever you want accuracies better than that... ;)
My nearly 3 yr old SDS2304 (HW 3.3)
(https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/?action=dlattach;attach=242938)
476 Hz low. :o
Resolution is something different than accuracy. With an internal reference accuracy of 1ppm in the SSA3000 measuring a 1GHz signal has an accuracy of +/-1000Hz so when the marker says it is at 1 000 000 000 Hz in reality the frequency can be anywhere between 999 999 000 Hz and 1 000 001 000 Hz.
So +/-1ppm of 1GHz is not +/-1000Hz?
Just answer the question yes or no.So +/-1ppm of 1GHz is not +/-1000Hz?Why such question? Has someone said something like that?
Do you like the strawman?
My measurements are based to one selected Trimble Tb and Z3801A GPS (or based to these some times readjusted Rb's). With accuracy what I need they are enough, but still not true NIST traceable. Real accuracy is not so simple thing, depending of course if we are satisfied with max 1ppm or <0.1ppb error.
I too use the Z3801A. It's tied to a UPS and looks like it been on for almost 13 years now. Even back then I don't remember them selling for a whole lot. I have an antenna located in the attic of the house for it. Modified mine to use an internal supply and enabled the RS-232. I thought the 10MHz reference was was 10-9, so 1hz/GHz. Also thought this was not very good compared to what they had at the time.
Looking in the manual, "Frequency Accuracy: < 1 x 10-9, one day average" Certainly good enough for 1ppm.
Hello.Yes.
Can someone please tell me if it is possible to downgrade the firmware? If I buy a new one and get it with FW0707, can I still install FW0705?
Thanks!
One of the improvements in 7.07 was to enable the saving of jpeg file types, not only bmp as was in 7.05
I've asked for more file types for a little while, SSA3kX is the first of any Siglent AFAIK to offer jpeg and we hope there will be more in the future. Png? Maybe. Discussion with Tech support has been around the time to convert each of the different types and the effect it has on the Save file computation times.
Jpeg takes a few more seconds to compute than BMP and with the jpeg format I have missed files by removing a USB pen drive too quickly before it has fully loaded. Annoying, yes but with the SSA3kX it is very quick to use the File management UI to check the file is present and does actually contain data.
I need to learn to more patient. :)
PNG is lossless.
When designer put jpg to this kind of purpose in equipment it can nearly say it is design error.
@Tautech: I just tested some cheap DC blockers from Ebay and they work quite well.Yep, spied that one and found it for less from other sources.
This one is the blue line (yellow is no DC blocker): www.ebay.com/itm/141638175057 (http://www.ebay.com/itm/141638175057)
However it seems the Siglent SSA3000X series has DC blocking capacitors build in so there is no need for an external one for DC levels up to +/-50V.Quite, but with a rated 50V input how much more isolation is wise to use?
Quite, but with a rated 50V input how much more isolation is wise to use?
IMO if a significant amount more is not added there's still a risk that a SA newbie like me might do damage.
I'd rather be safe rather than sorry with a $3K+ SA .
I'm looking for something reasonable and a bit higher spec to offer as an option to customers rather than have unnecessary equipment failures as a result of misuse.
Anyone suggest a source of a suitable DC block, a bit better spec'ed?
Maybe its is, but for some this might be considered an essential accessory too:Quite, but with a rated 50V input how much more isolation is wise to use?
IMO if a significant amount more is not added there's still a risk that a SA newbie like me might do damage.
I'd rather be safe rather than sorry with a $3K+ SA .
I'm looking for something reasonable and a bit higher spec to offer as an option to customers rather than have unnecessary equipment failures as a result of misuse.
Anyone suggest a source of a suitable DC block, a bit better spec'ed?
Maybe 50V is the standard ......
Maybe its is, but stuff for some this might be considered an essential accessory too:Quite, but with a rated 50V input how much more isolation is wise to use?
IMO if a significant amount more is not added there's still a risk that a SA newbie like me might do damage.
I'd rather be safe rather than sorry with a $3K+ SA .
I'm looking for something reasonable and a bit higher spec to offer as an option to customers rather than have unnecessary equipment failures as a result of misuse.
Anyone suggest a source of a suitable DC block, a bit better spec'ed?
Maybe 50V is the standard ......
http://www.aliexpress.com/store/product/N-M-F-DC-VARIABLE-POWER-block-DC-2-5GHz-200W-1000V-RF-Coaxial-high-voltage/1247757_32628218601.html (http://www.aliexpress.com/store/product/N-M-F-DC-VARIABLE-POWER-block-DC-2-5GHz-200W-1000V-RF-Coaxial-high-voltage/1247757_32628218601.html)
Not really, there's stuff out there for 1kW and more. Have a hunt on eBay, you'll see. ;)Maybe its is, but for some this might be considered an essential accessory too:Quite, but with a rated 50V input how much more isolation is wise to use?
IMO if a significant amount more is not added there's still a risk that a SA newbie like me might do damage.
I'd rather be safe rather than sorry with a $3K+ SA .
I'm looking for something reasonable and a bit higher spec to offer as an option to customers rather than have unnecessary equipment failures as a result of misuse.
Anyone suggest a source of a suitable DC block, a bit better spec'ed?
Maybe 50V is the standard ......
http://www.aliexpress.com/store/product/N-M-F-DC-VARIABLE-POWER-block-DC-2-5GHz-200W-1000V-RF-Coaxial-high-voltage/1247757_32628218601.html (http://www.aliexpress.com/store/product/N-M-F-DC-VARIABLE-POWER-block-DC-2-5GHz-200W-1000V-RF-Coaxial-high-voltage/1247757_32628218601.html)
Thats an impressive beast. Just curious is it just projection from accidents when probing around or is there a type of application where they might need that type of protection - kinda sounds like you have something in mind?
The breakdown voltage is specified at 1kV. See below.@Tautech: I just tested some cheap DC blockers from Ebay and they work quite well.Yep, spied that one and found it for less from other sources.
This one is the blue line (yellow is no DC blocker): www.ebay.com/itm/141638175057 (http://www.ebay.com/itm/141638175057)
But if you check the specs it's true DC blocking voltage is only 50V. >:(
If you look at Dave's SSA3000X teardown you'll see the MLCC capacitors for the DC blocking near the input. Even though they are rated for 50V MLCC capacitors in general have a very high dielectric breakdown voltage (over 1kV). This PDF has more information on it: http://www.koaspeer.com/pdfs/MLCC.pdf (http://www.koaspeer.com/pdfs/MLCC.pdf)QuoteHowever it seems the Siglent SSA3000X series has DC blocking capacitors build in so there is no need for an external one for DC levels up to +/-50V.Quite, but with a rated 50V input how much more isolation is wise to use?
IMO if a significant amount more is not added there's still a risk that a SA newbie like me might do damage.
I'd rather be safe rather than sorry with a $3K+ SA .
Why typically 50V dc.It's all starting to make a little more sense now. (to me)
Look typical cheap SMD capacitors specifications.
Note also that for 9kHz in 50ohm system this capasitance need be quite high.
Many DC blocks looks like they have nF class capacitors there instead of around uF class.
Example one in ebay tell that center pin DC block capacitor is 1nF
Now look this corner frequency just for simple estimation without more complex math.
But if do not really need 9kHz and starting from MHz or so is ok it may give much more protection in practice what can read from DC value. Rising from 50V to 200V feeels like some improvement but... think also if freq range bottom is more high, it may also give more protection in practice because it is high pass filter before all internals and more low frequency things are attenuated.
Pity these eBay sellers do not give enough data or data is copied and not exactly from what they are selling..
Also it need think if need DC/High pass block both, center and shield and not only center.
"Sensitive test equipment input protection ideas would have made for a great sticky thread. "
I am glad, my question was not as stupid as I feared...
Again, coming from TV/CATV/SAT field meters, I never had to worry about connecting the coaxial cable, but it would worry me to connect a unknown source to an expensive equipment like a spectrum analyzer.
Would it be wise to open a separate thread on this?
Regards
Antennas, SAT and CATV should all be grounded, hence there should be no static at all.
I will open a separate thread.
Regards
I was referring to TV antennas and SAT/CATV distribution! These are definitly grounded - in Germany by law as a protection against lightening.
Since I found the 30kHz RBW limit on the SSA3X Analyzers (when the TG is active) a little awkward (see here: https://www.eevblog.com/forum/testgear/hack-of-sigllent-spectrum-analyzer-ssa3021x/msg975408/#msg975408 (https://www.eevblog.com/forum/testgear/hack-of-sigllent-spectrum-analyzer-ssa3021x/msg975408/#msg975408)), and while "rf-loop" correctly pointed out that this shouldn't be a problem, I wanted to dig a little bit deeper into the matter of the tracking generator in this machine.
What made me really wonder is that I wasn't able to get a proper parallel resonance dip with a very accurate 1MHz crystal, whatever I tried -- there was always some kind of "hills and valleys" where the dip should be visible. Also the series resonance peak appeares a little "wiggly", see the screenshots in the above link.
Other (less accurate) crystals measure fine without any visible artefacts. The difference is that the mentioned "high accuracy crystal" has a very small frequency span between series and parallel resonance, it's just about 950Hz whereas more common crystals have spacings more like several tens of kilohertz. The reading cannot be an inherent characteristic of the crystal since on my other SA (Rigol 815TG) and also on my 8753C VNA it measures fine. So the problem has to be related to the way the TG in the SSA3X works.
Why on SSA3k, using a 30 kHz RBW, we got a peak with its 3dB BW far less than 30kHz in a 3k span, even like a 100Hz RBW ?There's some explanation of your "seen" behaviour in reply #304.
Why on SSA3k, using a 30 kHz RBW, we got a peak with its 3dB BW far less than 30kHz in a 3k span, even like a 100Hz RBW ?There's some explanation of your "seen" behaviour in reply #304.
Edit
And welcome to the forum
Can you give a summary of this firmware? :)
Does it give SSA3021X super powers (aka SSA3032X)? :)
Experienced two system crashes in short order on my SSA3021 w/TG and firmware .07.07. No hacks have been tried or applied to this unit. The unit had been displaying a 10.7 Mhz signal @-20db, 10hz RBW, 300Hz span. TG was not running. Signal was removed from the input for about an hour and the analyzer ran untouched and unterminated for the entire period. When the exact same signal was reconnected to the input, no signal was displayed. A scope was used to verify the signal being input was still present. The analyzer preset button was then activated, the same conditions set up on the analyzer and the input signal was then displayed as before. Within two minutes the system fully locked up and would not even respond to the power off button being momentarily depressed. The power off button was then held down for about 10-15 seconds until the unit finally went into shut down and reset. No system problems were apparent on reboot.
Anyone else had a similar issue?
Hi,
I am trying out my new SSA3021X and have a question:
Using the DEMOD button, I can demodulate AM and FM signals and make them auditable through an earphone.
I tried it with an FM radio station and indeed it works, I can listen to the radio, though I am not totally sure about some parameters. I.e. first I thought that I need to use ZERO SPAN on the carrier frequency, but apparently that is not the case. I seem to need to use a RWB of 100KHz, which kind of makes sense. I don't understand the timing parameter: I guess that is to give the SSA3021X more time to actually demodulating the audio instead of doing screen rendering?
The main question, however, is this: while I can listen to FM radio, I failed to get any signal (even noise) in AM mode. I have a radio scanner and can i.e. listen to aviation. If I use the same frequency on the SSA3021X I won't hear any sound, while the radio is reproducing fine. I can, however see the signal on the spectrum.
Is my AM demodulator broken or am I doing something stupid, like using wrong RWB, VWB, sweep, amplitude, etc.?
Thanks!
Thanks for your reply.
Can you please elaborate on the precautions required to not fry the input?
I am i.e. using a broadband amateur radio reception antenna. The signal is -50 to -70 dBm. I would have thought that there is no danger at all connecting this antenna to the SA. Am I missing something?
The same with cables carrying TV, CATV or SAT signals: I am using a DC blocker (mainly for SAT cable, due to the LNB power sent by the receiver). The signal itself varies from -40 to -70 dBm. That's safe, right?
I have a TV field meter which has a full spectrum analyzer and here the same 50VDC limit exists and the +20dBm. I never fried the input stage of any of my devices.
Still, I would appreciate a little more insight on this subject.
Thanks,
Vitor
(Btw: my name is Vitor and I just used the nick "Bicurico" because all my other commonly used nicks were not available)
It is still good to tightly realize and remember that even if look 1kHz wide band around 1MHz using 10Hz RBW whole front end get in all what is available in input terminal from nearly DC (<9kHz) to far over 3GHz and all, entire total amount, is going there to attenuator, switches and preamplifier and mixer. Whole this front end take even this 145MHz +30dBm even if you listen 7Mhz and see only -90dBm signals... this fact is some times too easy forget. In normal environment this is not big problem but if in house is also some transmitter or this and that what produce high LF - HF field when antenna is connected to SA..
Messing around with EasySpectrum.
The pictures show once again aviation communication, the pilot talking to the tower. The 3D waterfall diagram is spectacular and I wasn't even expecting this funcion to be available!
Sidenote to use EasySpectrum, as information is scarce: before installing the EasySpectrum package from Siglent, you need to download and install the National Instruments VISA package (https://www.ni.com/visa/ (https://www.ni.com/visa/)). This provides the required driver/framework for the GPIB protocol.
After installing it, run NI MAX and under network add the SSA3021X. Make sure the SSA3021X has the network correctly configured and you know what IP it is using.
Now run EasySpectrum and it should just work.
Regards,
Vitor
The 3D image is part of theMessing around with EasySpectrum.
The pictures show once again aviation communication, the pilot talking to the tower. The 3D waterfall diagram is spectacular and I wasn't even expecting this funcion to be available!
Sidenote to use EasySpectrum, as information is scarce: before installing the EasySpectrum package from Siglent, you need to download and install the National Instruments VISA package (https://www.ni.com/visa/ (https://www.ni.com/visa/)). This provides the required driver/framework for the GPIB protocol.
After installing it, run NI MAX and under network add the SSA3021X. Make sure the SSA3021X has the network correctly configured and you know what IP it is using.
Now run EasySpectrum and it should just work.
Regards,
Vitor
Really nice 3D software!
Is EasySpectrum included with the SA or is it an additional cost?It should be on the CD (haven't checked) but it's freely available from the Siglent America website:
Advanced Measurements Kit (AMK-SSA3000X) – Includes automatic measurements for
– Channel Power
– Adjacent Channel Power Ratio
– Time Domain Power
– Occupied Bandwidth
– Includes Waterfall Display
Here waterfall image how my SSA3000X display it. It show level only with color.
(I can not test without this AMK-SSA3000X Option because permanent Option can not remove using SSA GUI)
This looks very different what PC software EasySpectrum image @Bicurico posted and it looks 3-d waterfall.
(note also image quality when used JPG or PNG where PNG wins like 10-1. I hope Siglent add this PNG and make it as default. Peoples can take selfies and scenery or what ever art pictures using JPG but this is not suitable for this kind of technical document images.
d scenery or what ever art pictures using JPG but this is not suitable for this kind of technical document images.
Quoted scenery or what ever art pictures using JPG but this is not suitable for this kind of technical document images.
That is not correct. JPEG can provide a similar image quality as PNG, but it depends on the parameters (i.e. quality level, compression factor) that are used for generating them. If the screenshots in JPG are inferior in quality to PNG shots then this isn't the fault of JPEG but of Siglent because they set the JPG parameters in their firmware to low quality.
Not at all if we look result file size.
Original TFT BMP is 1843254 bytes.
Perhaps need some lesson? PNG is a lossless compression format when JPG is lossy.
You can try your self some exercises if you never have done.
After convert SSA 1.8M BMP to PNG so that PNG file size is around 30k. Look result. (file size depends what you have in picture, because it IS lossless. But also this is why it pack well this kind if images where image do not have nearly anything)
Then do same using conversion to JPG so that result is around same file size. Look result.
But, if you take normal camera image situation is very very different if look PNG and good quality JPG file sizes. In this case JPG win 10-1. Also in normal photograph, it is not so criticalk (usually( if we loose something..
And vice versa... in this kind of SSA etc technical images, mostly PNG win JPG like 10-1.
These things is best you self study using example google and read.
But in other hand, everyone has the right to choose a religion, and it must be respected.
Of course if we use very high quality settings for JPG package result is quite good, also for this kind of images, but why we then use packing if file size is big when we can get still better quality with lot of smaller file size.
Do you think we want out from BMP just because file size. Best result is with PNG and difference is not even only marginal.
Here attacehed two images.
Exatly same. Same BMP converted ti PNG and JPG.
We've had some behind the scenes discussion as which formats might be offered and the likely phase in time over the product range. Word I have is that other image file formats will gradually be rolled out in subsequent versions of new FW. We hope for a good selection of formats that offer users the image file type that will suit them best.
Exactly what we've asked for. :)We've had some behind the scenes discussion as which formats might be offered and the likely phase in time over the product range. Word I have is that other image file formats will gradually be rolled out in subsequent versions of new FW. We hope for a good selection of formats that offer users the image file type that will suit them best.
I don't think there's a need to offer some dozen of more or less obscure image format for a simple screenshot. Offering BMP, PNG AND JPG (maybe with some slamm tweaks to improve quality) is perfectly fine and already more than many other instruments offer.
:-+We've had some behind the scenes discussion as which formats might be offered and the likely phase in time over the product range. Word I have is that other image file formats will gradually be rolled out in subsequent versions of new FW. We hope for a good selection of formats that offer users the image file type that will suit them best.
I don't think there's a need to offer some dozen of more or less obscure image format for a simple screenshot. Offering BMP, PNG AND JPG (maybe with some slamm tweaks to improve quality) is perfectly fine and already more than many other instruments offer.
Exactly what we've asked for. :)
I think they should focus R&D efforts more into the debugging and performance sectors, far more important for a SA than the picture format. How often except for really basic report did you even use screen shots at work?
I think they should focus R&D efforts more into the debugging and performance sectors, far more important for a SA than the picture format. How often except for really basic report did you even use screen shots at work?Well I do that all the time because it is easy. Sure you can use external software but you need a PC, set the software up (and this is often a painful process due to drivers, the right NI VISA driver, etc) and then control the instrument from your PC -if that works at all-. It is just much easier to press a button and when making the report you just drag&drop the images into the document from a USB stick.
I think they should focus R&D efforts more into the debugging and performance sectors, far more important for a SA than the picture format. How often except for really basic report did you even use screen shots at work?
Pretty much every day. It's the quickest way to document all kind of stuff.
I think normal waterfall, "Spectrum monitor" as it is named in SA GUI is included with Option: AMK-SSA3000X.QuoteAdvanced Measurements Kit (AMK-SSA3000X) – Includes automatic measurements for
– Channel Power
– Adjacent Channel Power Ratio
– Time Domain Power
– Occupied Bandwidth
– Includes Waterfall Display
Here waterfall image how my SSA3000X display it. It show level only with color.
(I can not test without this AMK-SSA3000X Option because permanent Option can not remove using SSA GUI)
This looks very different what PC software EasySpectrum image @Bicurico posted and it looks 3-d waterfall.
(https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/?action=dlattach;attach=250175;image)
@Bicurico posted nice 3-d waterfall using PC software EasyWave (free)
(https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/?action=dlattach;attach=250405;image)
My SSA3000X (FW 7.05, with Option: AMK-SSA3000X). Image from SSA display.
(note also image quality when used JPG or PNG where PNG wins like 10-1. I hope Siglent add this PNG and make it as default. Peoples can take selfies and scenery or what ever art pictures using JPG but this is not suitable for this kind of technical document images. If yoy zoom some details etc you can see what kind of pixel porridge JPG is coocking in details)
I have a question on the everyday use of the SSA3021X: when I start to play with Frequencies, Span, Amplitude, Sweep and Trace options, after some time everything gets slow. Even if I set the parameters back to reasonable values, the refresh rate is low. If I press the PRESET button, however, things speed up again.
I did some tests and with the JPG quality set over 90% you won't see the differences between BMP and JPG but still get a more than 10 times reduction in size. What is most worrying is that nobody at Siglent gave any thought about the JPG compression setting or which file format to support. It is all trial & error with the end user in the loop.That is not correct. JPEG can provide a similar image quality as PNG, but it depends on the parameters (i.e. quality level, compression factor) that are used for generating them. If the screenshots in JPG are inferior in quality to PNG shots then this isn't the fault of JPEG but of Siglent because they set the JPG parameters in their firmware to low quality.
Not at all if we look result file size.
Original TFT BMP is 1843254 bytes.
Perhaps need some lesson? PNG is a lossless compression format when JPG is lossy.
I have a question on the everyday use of the SSA3021X: when I start to play with Frequencies, Span, Amplitude, Sweep and Trace options, after some time everything gets slow. Even if I set the parameters back to reasonable values, the refresh rate is low. If I press the PRESET button, however, things speed up again.
I have never meet this exept in situations when I have changed some parameter what affect speed. I mean example if I have adjusted VBW, after adjusting it is manually forced until I change its mode back to auto. Now If I forget this and if I do some other things and then just example change span. Then I wonder why this is so slow. Until I realize that oops... VBW is narrow. There is many this kind of things what do not return back to auto where SSA set itself better value when user select some other parameter. Also then, example sweep mode, in some (most) cases sweep is slower that FFT. If you normally use in auto sweep mode and then you select manually sweep mode sweep. Then change freq, span etc it may work much slower than usually if in sweep mode auto where is select FFT or (default) speed optimize instead of accuracy.
Of course I have not tested all possible combinations (human life is not enough for all possible combinations), so it is still possible there is some situation where it live some process on what slows system. When find this, it is good to document exacxtly these kind of findings so that same can repeat example by other user or in Siglent.
One I know. If use AMK option "waterfall". When it start from empty waterfall image it is more fast. After it collect more and more data it goes slower, until there is full waterfall image, after then it run with this speed.
Also if turn on Demod and set demod time long then forget demod on and go to look some other things. But demod time still make "pause" between sweeps. (in this case there is AM or FM displayed in left side)
If there is example 500ms demod time and then you go to some other things and your sweep time is example 10s. You do not perhaps note this extra pause. But then you adjust BW and or span etc and you expect much more fast sweep. Then you wornder why 24ms sweep is so slow. It keep demod time pauses (and you are not using it but forget it on)
Needs a lot of experience before the device is so familiar with that note of all the factors that affect each other and how they interact with each other.
Know your device - it is always important.
Then, when you know or seriously suspect that something is really wrong, it is good to document it well. So well that the problem may be repeated anywhere at any time by other user and I'm sure Siglent want also check all documented problems carefully.
Isn’t it funny how the picture format for screenshot files has become a major topic here in a thread about a spectrum analyzer – quite obviously just because it looks like a good opportunity to bash Siglent once again.:palm: Siglent has a long history of getting the format for saving screenshots totally wrong. So yes, this is an issue! Every manufacturer of test equipment has been using JPEG, PNG or even compressed BMP for decades. So it is just dumb they choose to use JPEG and not care to have a look whether the output is 'grainy' or visually perfect. People do need screendumps for reports and copying large BMPs into a document isn't going to help to keep the size down so the document can be e-mailed.
But Siglent needs not give a thought about JPEG compression settings, since this is an SA and not a camera of any kind, hence it outputs technical graphs.
Isn’t it funny how the picture format for screenshot files has become a major topic here in a thread about a spectrum analyzer – quite obviously just because it looks like a good opportunity to bash Siglent once again.
Since you don't even own one and have often declared your dislike for Siglent products after a previous unfortunate experience we can only assume you are trolling again. :palm: :palm:Isn’t it funny how the picture format for screenshot files has become a major topic here in a thread about a spectrum analyzer – quite obviously just because it looks like a good opportunity to bash Siglent once again.:palm: Siglent has a long history of getting the format for saving screenshots totally wrong. So yes, this is an issue!
But Siglent needs not give a thought about JPEG compression settings, since this is an SA and not a camera of any kind, hence it outputs technical graphs.
@Tautech: On the Siglent SDS2000 I owned the BMP screendumps where already an issue and thus brought to Siglent's attention over 2 years ago.:-DD
Besides that: I wrote I did some tests and hinted on how Siglent can fix the JPEG output quickly.
Defaulting to calling me a troll isn't going to work. Better come up with good arguments or just accept the truth hurts.
Siglent should really implement PNG. It's the perfect format for saving instrumentation screenshots. It's also patent free. https://tools.ietf.org/html/rfc2083We know.
RF-Loop has pointed out that PNG is the best file format for this, since it’s lossless and the resulting files are tiny nevertheless.Let's just be clear about one thing in general - PNG is not inherently lossless. For continuous-tone images it has to map the tonal values to palette entries, which is a lossy operation that results in dither. In fact, it's horribly poor for photography and you'll easily see dither and blotchy skin type artifacting as it applies a histogram-based mapping and dither. It's *only* lossless when there are fewer discrete colors in the image than the selected PNG palette, so if you convert an instrument graphic with a 3-bit palette to a 4-bit PNG color map you're golden. In that case it's lossless. If you map a 10-bit palette to a 4-bit one there will be decimation and dither and the results are butt ugly. It's *only* lossless in this particular use case of saving instrument screenshots and graphs, one it's absolutely perfectly suited for.
RF-Loop has pointed out that PNG is the best file format for this, since it’s lossless and the resulting files are tiny nevertheless.Let's just be clear about one thing in general - PNG is not inherently lossless. For continuous-tone images it has to map the tonal values to palette entries, which is a lossy operation that results in dither. In fact, it's horribly poor for photography and you'll easily see dither and blotchy skin type artifacting as it applies a histogram-based mapping and dither. It's *only* lossless when there are fewer discrete colors in the image than the selected PNG palette, so if you convert an instrument graphic with a 3-bit palette to a 4-bit PNG color map you're golden. In that case it's lossless. If you map a 10-bit palette to a 4-bit one there will be decimation and dither and the results are butt ugly. It's *only* lossless in this particular use case of saving instrument screenshots and graphs, one it's absolutely perfectly suited for.
All in all, I do like the device very much. It is a great step up in regards to the best of my field meters with spectrum function.But it can't do many of the things that field meters do. I'm also interested of the Siglent but I also want DVB-S/S2/T/T2 signal functions. So looks like it's devices like Rover HD Tab 7 or Promax HD Ranger that offer those functions with decent spectrum function. Too bad that those are way more expensive than the Siglent. I own two Emitor devices already.
Your profile gives no hint to where you are. :-//All in all, I do like the device very much. It is a great step up in regards to the best of my field meters with spectrum function.But it can't do many of the things that field meters do. I'm also interested of the Siglent but I also want DVB-S/S2/T/T2 signal functions. So looks like it's devices like Rover HD Tab 7 or Promax HD Ranger that offer those functions with decent spectrum function. Too bad that those are way more expensive than the Siglent. I own two Emitor devices already.
Your profile gives no hint to where you are. :-//Added the flag. So I'm from RF-Loop country... :D
All in all, I do like the device very much. It is a great step up in regards to the best of my field meters with spectrum function.But it can't do many of the things that field meters do. I'm also interested of the Siglent but I also want DVB-S/S2/T/T2 signal functions. So looks like it's devices like Rover HD Tab 7 or Promax HD Ranger that offer those functions with decent spectrum function. Too bad that those are way more expensive than the Siglent. I own two Emitor devices already.
All in all, I do like the device very much. It is a great step up in regards to the best of my field meters with spectrum function.But it can't do many of the things that field meters do. I'm also interested of the Siglent but I also want DVB-S/S2/T/T2 signal functions. So looks like it's devices like Rover HD Tab 7 or Promax HD Ranger that offer those functions with decent spectrum function. Too bad that those are way more expensive than the Siglent. I own two Emitor devices already.
Here is an example: the first pictures shows the spectrum of Astra 19.2E as seen by the Emitor Satlook Color (which I presume you have).Thanks for the info and pics. I have Combolook Color HD S2T2 and Satlook Micro. How fast is the spectrum display (of Astra) on the Siglent? Can you set it to almost realtime with resolution similar to Satlook? Or is it always way above Satlook Color's spectrum performance?
The next three pictures show the SAME spectrum as seen by the SSA3021X. Notice how far I can "zoom" into the spectrum, revealing the tiniest signals!
Here is an example: the first pictures shows the spectrum of Astra 19.2E as seen by the Emitor Satlook Color (which I presume you have).Thanks for the info and pics. I have Combolook Color HD S2T2 and Satlook Micro. How fast is the spectrum display (of Astra) on the Siglent? Can you set it to almost realtime with resolution similar to Satlook? Or is it always way above Satlook Color's spectrum performance?
The next three pictures show the SAME spectrum as seen by the SSA3021X. Notice how far I can "zoom" into the spectrum, revealing the tiniest signals!
So I made a return loss bridge to use with the Siglent analyzer in VSWR mode.
I'm quite curious what effect shielding (and maybe a little bit of tweaking) of the DIY RLB may have... Definitely still room for improvement, but as a starting point not too bad I would say! :)
The low frequency performance of my DIY RLB is superb and outperforms the MiniCircuits coupler considerably!
So I made a return loss bridge to use with the Siglent analyzer in VSWR mode. Some of the more difficult parts to find is very thin 50Ohm quality coax cable to make the balun to couple the bridge to the measurement port. Actually I found a seller for 1.2mm PTFE coax but then I came across an offer for adapters that connect an SMA socket to one of those ultra-tiny PCB clip-on connectors (for WiFi or cell phone equipment). But the best about this was that it contained about half a meter 0.8mm PTFE coax and cost close to nothing (at least compared to the amounts to be spent for a "proper" RLB -- it must have been arond 4€). So I quickly found some scrap double sided FR4 (ages old but the photoresist still working), mixed some developer and etching solution and tried if I still can "cook" PCBs "the old way"... :)
What I really think needs improvement on the SSA is how "frozen" traces are processed. They scale properly if level-related adjustments are done, but if frequency-related parameters are changed, they just stay where/as they are. No stretching/shrinking or shifting at all so they are completely useless if they are supposed to be compared to a newly recorded trace that (partly) covers a similar span. On the DSA815 this is solved much better!
What I really think needs improvement on the SSA is how "frozen" traces are processed. They scale properly if level-related adjustments are done, but if frequency-related parameters are changed, they just stay where/as they are. No stretching/shrinking or shifting at all so they are completely useless if they are supposed to be compared to a newly recorded trace that (partly) covers a similar span. On the DSA815 this is solved much better!
Funny, as this is exactly the same problem I have with my SMA Simple Spectrum Analyzer software! I implemented traces (and set each to WRITE, MIN, MAX, AVG permanently on later versions). When you change amplitude, the stored values are correctly shifted in Y direction. But if you change frequencies, I simply delete what is stored in each trace.
Alternatively I could just draw whatever bit of trace is stored, like a curve that starts and ends somewhere in the middle of the screen.
TurboTom
Nice work on the bridge. I'm also wondering about your source for the thin coax -- this looks like a fun project indeed.
Since you and rf-loop had a good look at it... Question on the RBW limit when the TG is on: How would you characterize a filter that has a very deep notch, say 70 to 80 dB? The 30 kHz RBW limit seems to be a problem in that case since it's not possible to further reduce the displayed noise level. Or am I mistaken? I have to admit that while I feel confident about having understood how spectrum analyzers work, I don't think I have fully understood what's going on with the tracking generator in this instrument.
Nice video.
Perhaps you might want to make further videos:
- explaining general and special functionality in more depth (even for existing users)
- showing general performance (which is what I tried to show on my video): people are often just interested in seeing basic things like the sweep rate
Regards
Let me try to put it like this: The Rigol DSA815 has a very simple but otherwise clearly understandable approach to measuring with its TG in use: Both TG and SA section scan the frequency span in constant increments, defined by the count of displayable pixels on the screen (round about 700 in case of the DSA815) and the span. So the TG outputs the center frequency of the "bin" (defined by the resolution bandwidth) the SA is sampling. Since the bandwidth of the TG signal in each "bin" is much smaller than the minimum 100Hz RBW of the Rigol, you can consider the signal to be picked up after a narrow-bandwith component (crystal for instance) a discrete frequency scan of the component. The video bandwith setting has no effect on the TG output.
The situation with the Siglent is much more complex and so far, I'm not sure if I understood it completely. Since the RBW of the instrument with the TG in use is limited to 30kHz and above, frequency discrimination has to be done by scanning with the TG. And here's the big difference vs. the Rigol SA: The VBW setting affects the discrete frequencies to be swept with the TG, i.e. a lower VBW setting results in the TG discrete frequencies to be more closely spaced while a higher VBW causes them to be further apart. Consequently, this also affects scan speed. Why this method of sweeping the frequency results in the "hills and valleys" may be the result of some "chirping" of the TG when setting the new frequency during a sweep. It should be possible yet to eliminate this problem by temporal "windowing" the measurement after the TG has settled. I guess Siglent should address this issue.
Cheers,
Thomas
Thanks!@ MotoDog
Yes, I actually laid out a pcb and built a noise source. 2 RF Amp ICs looking at a Zener Noise source.
I never got it to work. I guess I gave up. I even used stip line technique per a data sheet. Trying to keep 50 ohms.
So, maybe I better go pull out the project from the junk in the garage.
I guess if I could get my Rigol sold for a decent price $500? It is still over another $1000 for the slick Siglent!
BUT, Rigol just released a cheaper model! Crap. I should have bought what I wanted in the first place.
OK, go find the noise maker in the junk box.
Mike
@Jester --
that's basically what I found here: https://www.eevblog.com/forum/testgear/hack-of-sigllent-spectrum-analyzer-ssa3021x/msg975408/#msg975408 (https://www.eevblog.com/forum/testgear/hack-of-sigllent-spectrum-analyzer-ssa3021x/msg975408/#msg975408), yet I don't know why Siglent have arranged it like that. May it be unintentional, or is it done like this by purpose? So at that time, I wouldn't consider it normal but apparently it's present on all the TGs of the SSA3000X series of Analyzers. Other SA's TGs are also not the "cleanest" but not as weird as this. When testing high-Q components, the huge frequency spread may actually excite resonances that aren't part of the span one is looking at. As yet, there's no official statement on this behavior from Siglent. And obviously, there's the documented problem with analyzing components with very steep slopes in the frequency domain.
Cheers,
Thomas
I know the US distributor is in New York State, but isn't service on these done back in China?Ohio actually.
I just starting reading thru this, a quick question, is the general conscious this is better overall than the Rigol?
Upper image is from PC, running free PC software named EasySpectrum.For anyone not familiar with this 'add on' from NI, it is H-U-G-E!!! And I mean HUGE! I tried it once and removed it as quick as possible and that was no simple task since the installer did NOT completely remove everything, not even close.
This EasySpectrum PC software come free with SA or it can also free download from Siglent.
Before install it, first need install National Instruments VISA (Ni-Visa 15.0.1)
Also it is free. It can get from National Instruments.
Yes it is large, it's a connection utility for many brands and types of instruments, however I've never had a problem with it or noticed it being hungry on resources. :-//Upper image is from PC, running free PC software named EasySpectrum.For anyone not familiar with this 'add on' from NI, it is H-U-G-E!!! And I mean HUGE! I tried it once and removed it as quick as possible and that was no simple task since the installer did NOT completely remove everything, not even close.
This EasySpectrum PC software come free with SA or it can also free download from Siglent.
Before install it, first need install National Instruments VISA (Ni-Visa 15.0.1)
Also it is free. It can get from National Instruments.
It installs a ton of processes that runs continuously even if you aren't running the software which is unacceptable to me.
You might as well call it a M$ product, just as bloated, if not worse. I have no idea why on earth anything has to be this enormous for what should be a somewhat simple interface.
Has anyone come up with a 'wish list' or a 'fix this list' for these?
To start;
1. A Mechanical on-off switch to completely remove power w/o using a power strip or pulling the plug,
2. A lower speed fan to cut down on the noise, and/or one that has a thermistor to operate when it needs to, not continuously,
3. Option to remove (hide) the on screen display in the upper left of the grid which is: A. too large, B. usually not necessary,
4. Resign the standby mode to meet the Energy Star limit of under one watt, not FIVE watts which may of been ok 15-20 years ago, but shouldn't be now,
5. Expand the 'grid' by narrowing the side bars and merging the top to the bottom. Too much dead (wasted) space around the perimeter. To much of the larger screen (over the competition) is wasted
The first three also apply to Rigols SA's. Number four does not. ;)
1. Important. But not only SSA. All X series equipment same. I do not think so much energy save but also safety. All T&M equipment should have this!See the attachment for clarification.
3. Display menu, Screen text --> OFF. It is there. Do you mean some other thing? Not the entire display text, just what is inside the grid
5. Number of display points is 751. It need many things if rise this. It is not alone display question. Perhaps many internal things are based to this amount of data points. No, the area of the grid.
What is with all these trailing zeros, especially with RBW, VBW, Sweep & Span? ???
But if they are zero then just cut them. It just clutters the screen and makes the numbers difficult to read. Also there are very few situations where the numbers have to show so many digits anyway.Quote
What is with all these trailing zeros, especially with RBW, VBW, Sweep & Span? ???
those trailing zeros are needed because they may not always be zero,
But if they are zero then just cut them. It just clutters the screen and makes the numbers difficult to read. Also there are very few situations where the numbers have to show so many digits anyway.Quote
What is with all these trailing zeros, especially with RBW, VBW, Sweep & Span? ???
those trailing zeros are needed because they may not always be zero,
But if they are zero then just cut them. It just clutters the screen and makes the numbers difficult to read. Also there are very few situations where the numbers have to show so many digits anyway.Quote
What is with all these trailing zeros, especially with RBW, VBW, Sweep & Span? ???
those trailing zeros are needed because they may not always be zero,
3. Display menu, Screen text --> OFF. It is there. Do you mean some other thing?Yeah, but then you are not able to see your data entry when typing in e.g. "FREQ" and then "433.1750" "Mhz". You have to type the whole number blindly.
Why do the data points have to change? I'm talking about enlarging the active area as one would enlarging a photograph.
I think the "real estate" balance is about right.
OK, I'm no expert but if you keep bashing around in the UI you'll find that the "little" additional space that could be gained will only clutter the GUI and possible confuse newbies to spectrum analyzers more.
For those that are proficient with such tools, yes some more enlargement/compaction might be advantageous but who is the target market ?
If the UI is used to a full extent like some of rf-loops screenshots the GUI is then getting quite busy.
A quick look back a few pages to P13 finds some screenshots to illustrate both sides of the discussion:
(https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/?action=dlattach;attach=239603)
(https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/?action=dlattach;attach=240557)
Of course Siglent will see/read these comments and no doubt have some discussion about your suggestions Bruce, whatever the outcome it's good to examine these things so thanks for bringing them up. :-+
Unfortunately, the SSA somehow works erroneously on other traces if TG normalization is used so the following scans are taken without normalization. It appears the SSA occupies one of the traces for the normalization data but I didn't look at this in detail for the moment, I just disabled this function.
And the liberated options are also gone.
So BEWARE!
Have you tried activating them again through TELNET?
I wonder if they only reset the evaluation time settings or the actual activation settings: the hacks described in the other thread point to two different ways of doing the hack. One way is to change the eval period to infinite, the other consists in setting the option as activated.
...
So apparently, Siglent is not being too harsh. :-+
...
*** These posts should really be moved to the "Hack of Sigllent spectrum analyzer ssa3021X?" @thread... Can some MOD do this, please? ***
Regards,
Vitor
I think that 1Hz and 3MHz RBW is not within specification and can actually cause overload, which is probably why they removed it again.
I had an overload alarm once, when I was messing around trying out things on the SSA3021X with nothing more than an unamplified DVB-T antenna connected! I accidentally rotated the encoder while in RWB mode to 1Hz without noticing it and focused for some reason to the PC and only after a short period of time did I notice the overload alarm. Fortunaltly nothing broke, but it left me with an odd feeling about having the 1Hz option... So I disabled it myself, to prevent accidental setting.
What I am saying might be complete nonsense and the alarm may have been triggered by something else, but somehow I think one should not operate the filter out of specs.
Regards,
Vitor
I think that 1Hz and 3MHz RBW is not within specification and can actually cause overload, which is probably why they removed it again.
What I am saying might be complete nonsense and the alarm may have been triggered by something else, but somehow I think one should not operate the filter out of specs.
Regards,
Vitor
Is it safe to measure so low frequencies ever, and when not why this is not blocked (in software?)?
Unfortunately, is not many stuff about that on the web? :-//
Regards
Here some other example. One 14.2MHz filter. (bit off)
New FW 8.01
TG is now bit improved.
New FW 8.01
TG is now bit improved.
Also, I saw a few post from people using Perseus software, does it work?
Does anyone know the SCPI port for the SSA3000X?
I apologize for asking such a simple question : how do I connect a parallel resonant circuit ( capacitor and coil ) tuned to around 1Mhz to a Siglent spectrum analyzer with tracking generator ? Do I need some sort of impedance adapters ?
AFAIK that is called a pi-network. Another option is to use a directional coupler / directional bridge but either way this is getting into network analyser territory.I apologize for asking such a simple question : how do I connect a parallel resonant circuit ( capacitor and coil ) tuned to around 1Mhz to a Siglent spectrum analyzer with tracking generator ? Do I need some sort of impedance adapters ?Just put 50Ohm 10dB pads before and behind the circuit to avoid reflections and/or
impedance transformation on the cables.
This costs you 20dB of dynamic range but you can afford this easily as there are around
90dB DR if you set the SSA to 30Hz RBW.
I apologize for asking such a simple question : how do I connect a parallel resonant circuit ( capacitor and coil ) tuned to around 1Mhz to a Siglent spectrum analyzer with tracking generator ? Do I need some sort of impedance adapters ?
Just put 50Ohm 10dB pads before and behind the circuit to avoid reflections and/or
impedance transformation on the cables.
This costs you 20dB of dynamic range but you can afford this easily as there are around
90dB DR if you set the SSA to 30Hz RBW.
regards
AFAIK that is called a pi-network. Another option is to use a directional coupler / directional Bridge...I apologize for asking such a simple question : how do I connect a parallel resonant circuit ( capacitor and coil ) tuned to around 1Mhz to a Siglent spectrum analyzer with tracking generator ? Do I need some sort of impedance adapters ?Just put 50Ohm 10dB pads before and behind the circuit to avoid reflections and/or
impedance transformation on the cables.
This costs you 20dB of dynamic range but you can afford this easily as there are around
90dB DR if you set the SSA to 30Hz RBW.
but either way this is getting into network analyser territory.
Hi,
Does anyone know the SCPI port for the SSA3000X?
I am considering writing my own software, but don't want to friend on NI to interface.
Thanks,
Vitor
Great!What happens if you telnet to the spectrum analyser? Does that work? If yes, then you shouldn't worry about the return port because that will be handled by the OS.
Could I then make a wish?
Using i.e. Rigol, one can interface to SCPI through one single port. This even allows using telnet as a client.
With Siglent, the port on the PC side is constantly changing. This may be documented and part of the TCP/IP protocol, but it does make life difficult for people like me, who do not master TCP/IP and want to start in VB .net with basic networking code samples.
Hi.So it is a bug!
With telnet I can send commands and the SSA will switch to remote.
But I won't receive any return data, because it is sent to a different port.
I don't think it is a bug. The port is previously indicated in TCPIP but I don't know how to handle that. Wireshark shows that well. And VISA works, too.
First use a telnet client (the telnet command) and then write code! A component which sets up a tcp/ip connection should do the trick.
In the screenshot underneath the spectrum analyzer is "looking" at it's 50 ohm terminated input between 0 and 2Mhz. The first 600Khz or so are very high. Is this normal ???? Shouldn't be flat(ish) from 9Khz ?
all our units been selling fast for this item and we checked with the warehouse in SOLON OHIO, and they have been experiencing delays due to the Asian holidays.
Many items delay since China Holiday
Ruby Wu
Siglent Technologies America Inc.
Ruby.wu@siglent.com
440-3985800x103
I've spoken with TrioTest in Australia too, they are in much the same boat - they have *one* demo unit (fully unlocked for all features), but no stock of any new units for another ~4 weeks.Welcome to the forum.
Chig.
(long LONG time reader, first time poster...)
1. This firmware must be upgraded from V1.2.8.1 or later. If your SSA3000X has an earlier version, please to V1.2.8.1 first and then proceed to uplate to the latest version.
2. Add socket/telnet-scpi, you can operate remote control through LAN port without NI-VISA installed. Please check SSA3000X Programming Guide for more details.
3. Change two limit lines in different colours.
4. When quit from TG, stay in“Auto”sweep.
5. Lower some spurs when FFT.
6. Improve the stability.
Hi,You will see more of this in Siglent products in the near future....but it's best left to be discussed in other threads when it happens. ;)
This new FW is actually the answer of Siglent to a request I made in this thread (they didn't do it for me, of course - at least I wouldn't think so):
It allows SCPI commands through a regular telnet connection. This opens doors to people like me to program custom applications that use the SSA3021X remotely.
Without any promise, imagine this: a software similar to my "VMA Simple Spectrum Analyser" (made for the cheap ADF4350, ADF4351, MAX2870 range of devices, like the NWT4000 - discussed in a different thread) in a special version for the SSA3021X, offering all the "advanced" measurements, but based on measurements of a propper spectrum analyser!
http://vma-satellite.blogspot.pt/2017/02/siglent-ssa3021x-new-firmware-p0802.html (http://vma-satellite.blogspot.pt/2017/02/siglent-ssa3021x-new-firmware-p0802.html)Exactly. :-+
:)
Regards,
Vitor
http://vma-satellite.blogspot.pt/2017/02/siglent-ssa3021x-new-firmware-p0802.html (http://vma-satellite.blogspot.pt/2017/02/siglent-ssa3021x-new-firmware-p0802.html)
Hi Vitor,
now seen on your Satellite Blog, looks very promising - congratulation :-+
Regards,
Bozidar
1. This firmware must be upgraded from V1.2.8.1 or later. If your SSA3000X has an earlier version, please to V1.2.8.1 first and then proceed to uplate to the latest version.
After a few months without my hobby, I decided to look for a new firmware for my SSA, and found this note:All previous versions of firmware for any Siglent model or series are listed in this page:Quote1. This firmware must be upgraded from V1.2.8.1 or later. If your SSA3000X has an earlier version, please to V1.2.8.1 first and then proceed to uplate to the latest version.
Hmm. I don't have V1.2.8.1. :-// And Siglent doesn't provide a link to this older firmware. :palm:
Please, can somebody help me and send me the older firmware? ^-^
Thank you in advance!
Hi Gents,Yes, to date this has happened in all firmware updates. It is normal.
During upgrade (from 7.07 to 8.1 and then up to 8.2) the progress bar I get goes up to 40% and then instrument reboots.
I get logo which stays for a while and the instrument reboots again into the normal working mode.
Is this the same behavior you have during the upgrade?
Thanks!
Hello,
I am after accurate noise measurements.
I have applied flat White Gaussian noise -120dBm/Hz to the analyzer.
I have done two measurements with and without pre-amplifier and I get about 0.35dB difference.
See attached picture. Probably this PA offset can be fixed?
Anyone with experience with the instrument calibration?
(https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/?action=dlattach;attach=294561;image)
Thanks
Dimitar
Hello,
Another things that puzzle me.
My setup:
-120dBm/Hz flat white Gaussian noise
I have tried to measure using "Noise marker" and setting few RBWs.
Each time I keep the VBW same as RBW and average traces enough to get low variance (0.5dB)
Detector is "Average"
RBW=10KHz(100 avg traces) Noise marker= -120.1dBm/Hz (trace variance +/-0.5dB)
RBW=3Khz (100 avg traces) Noise marker= -120dBm/Hz (trace variance +/-0.5dB)
RBW=1KHz (100 avg traces) Noise marker= -120dBm/Hz (trace variance +/-0.5dB)
RBW=300 (3 avg traces) Noise marker= -117.8Bbm/Hz (trace variance +/-0.5dB)
RBW=100 (1 avg traces) Noise marker= -118.3Bbm/Hz (trace variance +/-0.5dB)
For the RBW 300Hz and 100Hz my measurement is about 2dB too strong. Do you think it is a bug?
Should I prefer big RBW and many trace averaging or small RBW and less trace averaging?
I also have compared the dBm readings on the screen at the marker and what the "Noise marker" calculates
for example I see my trace at -95dBm with the RBW=300Hz and I expect power density -95-10*log10(300)=-119.77 dBm/Hz
but the noise marker calculates it to -117.8 dBm/Hz (2dB too strong)
It is interesting how the analyzer is calculating the "Noise marker"?
Things are getting even more confusing as I noticed that what I see on screen differs from the regular dBm marker with sometimes 1dB
See the attached picture. So I am not sure I should believe the trace and grid or the marker.
Any comments on all this is welcome.
Thanks
Dimitar
Hi rf-loot,
Thank you for the measurements.
I have double check and clearly see the issue.
See attached.
Yellow measurement is for the span 0 - 50MHz
Pink trace is for the span 0 - 10MHz
In your case you have not checked the 50MHz range.
Can you set wide band white noise at the analyzer input (the signal level you have used I think should be OK)
Measure with the same settings you already used from 0 - 10MHz and then 0 - 50 MHz.
Thanks
Dimitar
when I start to play with Frequencies, Span, Amplitude, Sweep and Trace options, after some time everything gets slow. Even if I set the parameters back to reasonable values, the refresh rate is low. If I press the PRESET button, however, things speed up again. So I tried to memorize those PRESET settings and on the next slow down entered them manually: the SA was still slow. Pressing the PRESET made it run faster again.I would say not since you didn't make any reference to RBW & VBW, nor to it the speed constantly dropping. ;)
I have never meet this exept in situations when I have changed some parameter what affect speed. I mean example if I have adjusted VBW, after adjusting it is manually forced until I change its mode back to auto.That referred to a one time manual change then back to auto.
Engineering has started work on that bug with the sweep time changing. When you set it to manual, it should stay that way.:-+
I entered the information in our bug tracking system. Case 1327. When the case is resolved, I’ll contact you with the solution
And no one noticed this at all?? :-//
I trust this was spelled out enough to get a handle on it. If it wasn't please ask where I lost anyone.
It would of been much nicer if the case material was more substantial. It looks like it's very thin, no padding which surely gives pause using it for that type of equipment.The material is a sleek and finely woven synthetic. Front and rear padding is in multiple layers, feels ~8mm thick for each layer and there's at least 2 layers each face. Not your usual soft foam, pretty tough stuff.
What is the US price for the bridge??RB3X20 RB (1 MHz~2 GHz), N (M) ?N (M) adaptor (2 pcs) list is US$ 345
The price for that case is $120 US?US $125
Is there a 3GHz version of the bridge?
Keen to get a reflection bridge too... But i'm not paying that sort of money for it.There is the advantage that there's no cables required, it adapts directly onto the TG and Sig In ports of SSA3kX models.
That said... i'm struggling to find anything else around online for a reasonable price that doesn't look like it was made in a 16 year old's electronics class...
Since there is no activity in this thread for over a week, I guess it's the new participants are eagerly awaiting delivery of SSA3021X? Who is latest to receive their unit, and what firmware are they shipping with now?Others may have had different but one I got a few weeks back fresh from the factory had 8.1 installed. 8.2 is the latest firmware.
The Siglent SSA also has an option to connect headphones. I used my Samsung Galaxy headphones and demodulated some radio stations already1. That was brought out in a very good review on YouTube. The guy did connect a small speaker by itself and it worked.
The volume was set to "1" and my ears nearly started bleeding. So either it's an output to connect a speaker or the pre-amp inside the SSA is not yet adjusted right.
5. Is there any easier way to jump to peaks while the measurement is not stopped (trace set to view)?Turn 'Cont Peak' on & and choose 'Peak Peak'.
Selecting center freq (which results in 2.75 GHz), with a freq step of 10 MHz and turning the rot-enc wheel, shouldn't the next step be at 2.76 GHz? Here it jumps to 2.7505 GHz, doing 500 kHz steps ...It is here. You must be doing something wrong somewhere.
I'll have to double check my 8920B, I don't recall it having any skips, but maybe.
I figured I could set the default startup behavior, just haven't gone through the manual well yet. I've been pretty much just been pushing buttons and playing.
Thanks for the tips.
Joel
I'll have to double check my 8920B, I don't recall it having any skips, but maybe.
I figured I could set the default startup behavior, just haven't gone through the manual well yet. I've been pretty much just been pushing buttons and playing.
Thanks for the tips.
Joel
If you compare 8920B RF Communications Test Set and normal Spectrum analyzer it need note that they are extremely different machines. Yes it have also spectrum function but... example 8922 can listen AND sweep SA at same time, 8920B I do not have any own experience. (least these units (GSM test set's) what I have owned and used.) These machines are very different, and if look these units (new) prices and example Siglent SA (new) price.
Hi rf-loot,
Thank you for the measurements.
I have double check and clearly see the issue.
See attached.
Yellow measurement is for the span 0 - 50MHz
Pink trace is for the span 0 - 10MHz
In your case you have not checked the 50MHz range.
Can you set wide band white noise at the analyzer input (the signal level you have used I think should be OK)
Measure with the same settings you already used from 0 - 10MHz and then 0 - 50 MHz.
Thanks
Dimitar
Many of these have already been reported I'm told by Siglent, but since I already composed a list of needed 'changes' I'll post them here for convenience. Note " 1" is skipped since it requires a separate entry due to it being what I consider fairly severe!
2.Trying to use the Normalize function with the Tracking Generator when the 'Units' are set to anything other than dBm will not work. Normalize is grayed out. One has to remember to go back and change the setting to dBm unlike other SA's that do this automatically (Rigol for starters). Note, dBmV has been common for receive measurements for Signal Level Meters (MATV/CATV etc) for as long as I can remember.
3. Tracking Generator menu: Remove the "Normalize" soft key on the 1st page since all it is is a .next page' go to button and move the four entries on that 2nd page to page one. There will still be a vacant soft key left over. This eliminates jumping back and forth between pages something they have done well to eliminate over the Rigol menu structure.
4. No mechanical power button. I see no reason why ALL test equipment shouldn't have one. Yes, they can be connected to switched power strips, but having a true removal of power w/o physically unplugging can also be a safety factor. Keep the standby button, but I'm sure there is room on the rear panel for a rocker switch.
5. The 'standby mode' is a power hog by todays standards. Five watts running 24/7 shouldn't be acceptable anymore. That's 1/6th of the operational current (28-29 watts). I assume this has wake on LAN or similar? Fine, but does it have to be that much of a hog? How about a option to disable and 'wake' mode to get the draw down below 1 watt (EPA standard)? At least that would be a somewhat quick fix, assuming it can be done thru the firmware.
6. Need a option to blank out the ridiculously long default name/number assigned to saved screen shots. Considering that the time & date is in the instrument directory and when copied to a flash drive, there isn't any real need for it to be the file name. Deleting it one digit at a time is even more annoying.
7. Those annoying front feet that collapses ever time they are extended after one picks up the instrument by the handle when it brushes the desk or table top is really annoying. Copying a good idea is one thing, but copying a bad idea is another.
8. How about a carrying case option? One that is designed to allow actually using the SA while still in the case. Mind you, I'm not suggesting climbing a tower, utility pole or rooftop, just for remote monitoring etc where AC is available.
Apparently everyone uses auto settings for Sweep, RBW & VBW since no one here has apparently noticed this somewhat severe firmware problem as follows. ???
This has been reported and confirmed!
To justify my reason to declare this a #1 is this; the need for speed for real time monitoring complex waveforms. Namely ATSC (8VSB) for OTA (Over The Air) broadcast TV for just one example. Many analyzers allow adjusting sweep speeds in manual mode and they stay set no matter what is done otherwise,. But once set, the setting doesn't change (and shouldn't) if it is in 'Manual' mode.
Knowing that there isn't any free ride, in this case accuracy, something usually has to suffer which is acceptable in this case since missing changes in the signal for the sake of accuracy isn't. Manual modes are provided for a purpose. They allow operator choices which they should. You don't have to use them, but they are still there. I for one prefer to take advantage of a supplied option. ;)
Setup conditions (easy to duplicate):
1. Place the RBW, VBW & Sweep settings all in manual mode. Set the two bandwidths to a middle setting. Settings for the attenuator or units shouldn't matter. No signal is required.
2. Change the Sweep to the fastest setting (usually 24ms)
3. Set the frequency range to whatever you want, the full bandwidth is fine though I never have a need for that. My ranges are usually between 50 & 500 Mhz.
4. Go to the BW page and start changing either of the two adjustments paying attention to the sweep speed. You can use either the 'jog' dial or the up/down buttons. You will see it drop to the next slower speed.
5. Now, here where it gets more interesting, return to the previous setting. Note the sweep speed still slowing instead of returning to where it was. Everytime you make any adjustment to either the RBW or the VBW in either direction the sweep slows down to the next fixed setting forcing one to return to the sweep page and crank to back to the fastest setting allowed. Trying to get a respectable display is a real chore jumping back and forth between BW & Sweep.
This brings up a few questions;
A. Why is it changing in the first place since all settings are in or supposed to be in manual mode??
B. Why are these preset sweep speeds fixed at these 'odd' figures? Some mathematical formula and/or a limitation of the system??
With further testing I did find a couple of exceptions where the speed reversed direction, but only to a certain extent.
And no one noticed this at all?? :-//
I trust this was spelled out enough to get a handle on it. If it wasn't please ask where I lost anyone.
Regarding the tracking generator: can someone verify that with a different spectrum analyser? It looks so bad that it must be a measurement error!
It's still within specs ;-)
(https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/?action=dlattach;attach=211927;image)
Also Rigol's TG is not that brilliant ...
(https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/?action=dlattach;attach=211929;image)
I wonder about the performance of incoming SSA3000X improved version.
Regarding the tracking generator: can someone verify that with a different spectrum analyser? It looks so bad that it must be a measurement error!
It's still within specs ;-)
(https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/?action=dlattach;attach=211927;image)
Also Rigol's TG is not that brilliant ...
(https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/?action=dlattach;attach=211929;image)
I wonder about the performance of incoming SSA3000X improved version.
Difference between Rigol and Siglent TG output scan between 0 and 1.5GHz scan. Both SA's had a 10db attenuator on input and TG output. Notice the sudden 1db drop at 600MHz on Siglent. looks like crap compared to Rigol but still within spec. I remember Rigol had something similar way back when but they came out with a firmware fix. Thank GOD for normalization LOL !
73 N8AUM Vidas
Difference between Rigol and Siglent TG output scan between 0 and 1.5GHz scan. Both SA's had a 10db attenuator on input and TG output. Notice the sudden 1db drop at 600MHz on Siglent. looks like crap compared to Rigol but still within spec. I remember Rigol had something similar way back when but they came out with a firmware fix. Thank GOD for normalization LOL !
73 N8AUM Vidas
Are you sure you got those around the right way? The Siglent looks much flatter than the Rigol to me.
Edit: Or did I miss something - perhaps you used the Siglent to measure the Rigol and vice versa?
Sorry, I forgot to mention that I used the Rigol to measure the Siglent and the Siglent to measure the Rigol. My HP took a dump otherwise I would have used it to compare, sorry 4 the confusion ! :palm:Confusion reigns if you don't bother to mention the firmware version for each model. :scared:
Difference between Rigol and Siglent TG output scan between 0 and 1.5GHz scan. Both SA's had a 10db attenuator on input and TG output. Notice the sudden 1db drop at 600MHz on Siglent. looks like crap compared to Rigol but still within spec. I remember Rigol had something similar way back when but they came out with a firmware fix. Thank GOD for normalization LOL !
73 N8AUM Vidas
Are you sure you got those around the right way? The Siglent looks much flatter than the Rigol to me.
Edit: Or did I miss something - perhaps you used the Siglent to measure the Rigol and vice versa?
Sorry, I forgot to mention that I used the Rigol to measure the Siglent and the Siglent to measure the Rigol. My HP took a dump otherwise I would have used it to compare, sorry 4 the confusion ! :palm:
Sorry, I forgot to mention that I used the Rigol to measure the Siglent and the Siglent to measure the Rigol. My HP took a dump otherwise I would have used it to compare, sorry 4 the confusion ! :palm:Confusion reigns if you don't bother to mention the firmware version for each model. :scared:
You need to check in at the TEA thread >:D
Folks,
what are you doing or discussing here doesn't make any sense.
A tracking generator is called tracking generator because it TRACKS the SA's sweeping frequency.
So if you feed the TG from e.g. a Siglent into any other SA,no matter if Rigol, HP or whatever,
it cannot track the SA's sweep because it is not locked to the SA's LO(s).
So it's just random results what you are seeing.When at a certain point of time the SA's tracking filter is on another frequency than the TG the input impedance of the SA as seen by the TG is high and reactive.
That's why you can reduce the amplitude variations by putting in some attenuation.
For further in depth information I recommend reading
" Spectrum Analysis Basics" - Application Note 150 by keysight/HP.
73
Clemens
"The attached image shows the MAXIMUM signal power and took around 5 minutes to generate. The reason is obviously the non-syncronized TG output sweep vs the spectrum input sweep. This accounts for a significant error, as you may see values that were captured under the required time, because the TG moved to the next frequency, before the measurement was complete. The longer you let this setup run, the smoother and flatter the curve will get.
In my opinion this is not a good way to actually evaluate a TG of an SSA."
Folks,
what are you doing or discussing here doesn't make any sense.
A tracking generator is called tracking generator because it TRACKS the SA's sweeping frequency.
So if you feed the TG from e.g. a Siglent into any other SA,no matter if Rigol, HP or whatever,
it cannot track the SA's sweep because it is not locked to the SA's LO(s).
So it's just random results what you are seeing.When at a certain point of time the SA's tracking filter is on another frequency than the TG the input impedance of the SA as seen by the TG is high and reactive.
That's why you can reduce the amplitude variations by putting in some attenuation.
For further in depth information I recommend reading
" Spectrum Analysis Basics" - Application Note 150 by keysight/HP.
73
Clemens
Difference between Rigol and Siglent TG output scan between 0 and 1.5GHz scan. Both SA's had a 10db attenuator on input and TG output. Notice the sudden 1db drop at 600MHz on Siglent. looks like crap compared to Rigol but still within spec. I remember Rigol had something similar way back when but they came out with a firmware fix. Thank GOD for normalization LOL !
Sorry, I forgot to mention that i used the Rigol to measure the Siglent and the Siglent to measure the Rigol.
73 N8AUM Vidas
SSA3032X TG output shut off after being on several hrs even tho it says its on. Turned off TG than on again but still no output. Reset (Preset) no help, had to power cycle unit in order to get TG to work again.
SSA3032X Firmware ver 1.2.8.3
I received an SSA3021X today but only had a few minutes to play with it before work intervened. It's my first SA so I'm quite impressed.
I have a quick question about packaging. Mine came with no peel off screen protector and a few small scratches on the bottom of the unit. Every photo I've seen online of a new unit shows the peel off film in place. Should I be concerned that I received a "used" model or do all the latest ones come w/o the film. It has an April cal date and came with 8.2 FW For $1500 I was expecting to get to peel film off something. :'(
Most Siglent product that I have received lately has been minus peel off screen protectors.
:-DDMost Siglent product that I have received lately has been minus peel off screen protectors.
I've been intercepting your mail Tautech!
1. Changing RBW and/or VBW settings (in manual mode) changes sweep speeds. Everytime one adjusts either setting the sweep speed slows down one step. This continues to happen even if you return the setting to where it was. The sweep speed keeps slowing. I never encountered this before and it is REAL annoying. (see below)
5. The 'standby mode' is a power hog by todays standards. Five watts running 24/7 shouldn't be acceptable anymore. That's 1/6th of the operational current (28-29 watts). I assume this has wake on LAN or similar? Fine, but does it have to be that much of a hog? How about a option to disable and 'wake' mode to get the draw down below 1 watt (EPA standard)? At least that would be a somewhat quick fix, assuming it can be done thru the firmware.
6. A option to blank out the ridiculously long default name/number assigned to saved screen shots. Considering that the time & date is in the instrument directory and when copied to a flash drive, there isn't any real need for it to be the file name. Deleting it one digit at a time is even more annoying.
Setup conditions for #1 (easy to duplicate):
1. Place the RBW, VBW & Sweep settings all in manual mode. Set the two bandwidths to a middle setting. Settings for the attenuator or units shouldn't matter. No signal is required.
2. Change the Sweep to the fastest setting (usually 24ms)
3. Set the frequency range to whatever you want[/b], the full bandwidth is fine though I never have a need for that. My ranges are usually between 50 & 500 Mhz.
4. Go to the BW page and start changing either of the two adjustments paying attention to the sweep speed. You can use either the 'jog' dial or the up/down buttons. You will see it drop to the next slower speed.
5. Now, here where it gets more interesting, return to the previous setting. Note the sweep speed still slowing instead of returning to where it was.Everytime you make any adjustment to either the RBW or the VBW in either direction the sweep slows down to the next fixed setting forcing one to return to the sweep page and crank to back to the fastest setting allowed. Trying to get a respectable display is a real chore jumping back and forth between BW & Sweep.
With further testing I did find a couple of exceptions where the speed reversed direction, but only to a certain extent.
Please stand by on this.
Our beta version here in Ohio worked fine last week, it was released today but when we installed the new released version we are also having trouble.
We will post an update - hopefully tomorrow.
Thanks
I notice something odd not sure if it existed before 8.5.
When I first turn on the SA and set say freq to 100MHz and span to 1 MHz, I cannot set a RBW below 10Hz.
If I then set freq to 50KHz and span to 10KHz, I can set RBW below 10Hz
If I now go back to freq 100MHz and span 1MHz I can set RBW below 10Hz
I have to redo the low freq steps again if I power cycle the SA.
edit: I set the SA above 1GHz and lost the RBW less than 10Hz, probably not a surprise, but when I went back to 100MHz and span 1MHz, I again could not set RBW less than 10Hz.
Is there a max frequency and span for this to work?
edit 2: playing some more I find the limits, basically span is the limiter before hitting a sweep time error. Higher center frequency, smaller span. I think this is good and normal. There does still seem to be some oddness if I set an allowable 1Hz RBW setting, it seems to let me set some frequency and spans that wouldn't otherwise work.
I notice something odd not sure if it existed before 8.5.
When I first turn on the SA and set say freq to 100MHz and span to 1 MHz, I cannot set a RBW below 10Hz.
If I then set freq to 50KHz and span to 10KHz, I can set RBW below 10Hz
If I now go back to freq 100MHz and span 1MHz I can set RBW below 10Hz
Start at frequency 50KHz and span 10KHz and set the RBW to 1HZ
Leave the RBW at 1Hz and set the frequency to 100MHz and the span to 1MHz.
Go back to RBW, it stays 1Hz ok and I can also change the RBW up and back down to 1Hz no issue.
Edit, I just had my ah ha moment. I went to take pictures so I could show what I was doing and realized that when I set span to 1 MHz, it was staying at 10KHz. No error message.
I guess all is good in the world again.
Joel
Hi to community,Yes, the deletion of saved files is not obvious but is outlined in the User manual in the Files section on P67: 2.5.3.9 Operate
i am wonder how you get manages the problem within file management system - inability to delete files?
It can't be that this bother only me?
Is it some way to resolve this? :-//
Yes, the deletion of saved files is not obvious but is outlined in the User manual in the Files section on P67: 2.5.3.9 Operate
Simply, when in File UI select/highlight the file or folder and use the Operate softkey where then the Delete option becomes available for use.
Edit.
After further thought "Operate" as a selection to enter the deeper file management UI could be changed to Operator which IMO will be a more intuitive name for it as it suggests further file management possibilities.
I'll suggest this change to Siglent.
Hmmm, still on 8.3 here and I had zero problems with any file type. :-//QuoteYes, the deletion of saved files is not obvious but is outlined in the User manual in the Files section on P67: 2.5.3.9 Operate
Simply, when in File UI select/highlight the file or folder and use the Operate softkey where then the Delete option becomes available for use.
Edit.
After further thought "Operate" as a selection to enter the deeper file management UI could be changed to Operator which IMO will be a more intuitive name for it as it suggests further file management possibilities.
I'll suggest this change to Siglent.
Thanks tautech,
unfortunately, it seems that my SSA has a life of its own.:o
For some files deleting was successful (first i must rename the file, until only .jpg remains - and than i can delete), for some not!
Anyway, file management remain wired - maybe some days Siglent would resolve that.
2) Reflection measurement (selected as "mode") is unusuable; starting the measurement by entering in this mode, the "reset" and "Cal open load" don't perform the appropriate functions.
So a rollback to 1.2.8.3 was executed waiting for a new FW release.
I have created a short video but can't upload(MP4).We shared some PM's to help with this, maybe bozidarms can report his progress since and offer some tips.
Anyway, i can't even create a new folder in SSA alone.
If i understand all right, file manipulation is possible on SSA alone too,
or i have completely misunderstood, and file management is possible only with USB stick.
(With USB stick - is, in my case, possible every operation.)
I just discovered that the situation is far worse than I thought. Firmware is 1.2.8.2. My initial test this morning was:
1) power on
2) set start and stop at 88-107 MHz
3) set attenuator to 0 dB
4) select Pk-Pk
5) display reports marker @ 1.19 MHz !!!!!
6) select left Pk
7) display reports marker @ 343 KHz !!!
8) repeatedly selecting Pk-Pk results in the marker frequency reported @ random values including -1.99 MHz!!!!!
I've attached a JPEG of the last result. I took other pics showing the marker reported at a variety of frequencies all outside the sweep range with the maker located in the same spot.
I had lots of strange results earlier, but I just put that down to unfamiliarity. But with the marker staying in the same spot and absurd frequencies being reported on screen this thing is clearly not trustworthy.
The specs looked very attractive, so I found it odd that places that were carrying it had discontinued it. I think the reason is becoming clear.
I think the reason is becoming clear.
After rereading the entire manual it became clear that it's a language issue. To an English speaker "Peak Peak" is synonymous with "Maximum Peak". In fact, that button selects the minimum and maximum points on the trace and then gives the frequency difference between the two points. As the minimum changed the behavior was random. "Min Max" would be a more appropriate label in English.
I notice that with the input terminated with 50 ohms and the unit at the factory preset, power on settings there is a 5-10dB slope rising from 0 Hz to 2.1 GHz. Is there a setting to correct this?
In general I would like to store a trace and then subtract it from another stored trace or the current input trace. Is this possible? If so, how?
I am using the 1.2.8.2 firmware installed by the factory in May 2017. The seller does not allow returns if the buyer has modified the unit, so I do not want to update the firmware until I have satisfied myself that there are no show stoppers.That's very unreasonable, you should contact them and insist that you can install at least 8.3 FW that seems it may be addressing some of your issues.
I have found it difficult to consistently reproduce problem behaviors.So did I until I found ways to return the unit to startup settings and become more familiar with the UI.
I'm looking seriously for a replacement, but am going to ask for a demo before I commit and a service manual is going to be a requirement. I was told by Siglent support that the service manual for the SSA3021X had not been finished despite the product being on the market for 2 years.What do you expect to find in a service manual? You might find a procedure to check the device and determine which board to replace in case of a failure but that's it. Service manuals with detailed repair procedures and schematics are something from a long forgotten past. Repair is still possible but you'd have to reverse engineer the device and have a good understanding of how it should work in principle.
I've taken to power cycling the unit to be assured of reproducible initial state.There's no need to do that, use the Preset button that when new is set to factory default but is user definable for your favourite setup.
I do wish there were more information about the hardware. For example if the unit has power but is "off" is the internal reference running? I have all the stuff on my bench on a power strip so that I can turn it all on and off at once. That's obviously not desirable if the soft power was done to keep the oscillator running.
I'm used to HP & Tek gear and manuals. I have a Motorola spectrum analyzer, but it needs work. My reason for buying this was repair fatigue and the cost of new from Tek and Keysight. So very poorly done manuals without so much as a block diagram is discouraging. Were I making the purchase in a professional context rather than a hobby context I should not have considered Siglent after reviewing the documentation and seeing how skimpy and error ridden it was.There's further documentation that might help prepared by the guys in Siglent Ohio here:
I plan to discuss further tomorrow before returning the unit. There are some things that suggest a hardware fault.Take some more time to get your head around this unit, faults are unheard of.
I've already been through used gear dying shortly after the warranty expired.I've got Siglent DSO's running for 5 years in tech schools that have never given any problem. None.
I already had gotten an RMA before I ever stuck a USB drive in it. So the initial hang was not related. More curious is that I just used that USB drive to transfer the RMA PDF from my OpenIndiana system to my Solaris system for printing. No issues, but neither Windows 7 Pro nor the Linux distros I tried can even see the stick.
It is. I transferred the RMA PDF after I had reformatted the USB stick. When I inserted it in the SSA3021X it was as formatted when I received it with some reports from a Stanford research consortium on it. These were commercially produced drives with a logo showing the year and the files. I had used it once to do a firmware update on my Rigol DS1102E. Saving some data on the Rigol deleted all the consortium reports and theses. At the time I blamed it on the Rigol, but I need to do some testing with a USB hard drive. It may well be that the USB stick was wonky. Using a different USB stick, the SSA3021X worked fine.
I noticed a while back that my 3032X and someone else's 3021X running 1.2.8.5 that signals at -125dbm are about 2db lower than what they should be and at -135dbm its over 10db lower when RBW is 3Hz or 1Hz. 10Hz RBW and wider show the correct level.Something wrongly implemented in the firmware for the 1 and 3Hz RWB. Siglent perhaps need a push to look at it. See also
If the answer is in AN-150 I just don't see it.
Vidas N8AUM
Hello all, can someone in layman's terms explain what I am seeing and why?This could be the cable or attenuator, or a blown SA input, (not 50 Ohns any more)
TG output set @ -20dbm, input att set at 20db. Yellow trace was normalized with a good quality JFW attenuator on input. Cable is 20" long of from a batch of M17/128-RG400 MIL-C-17. When I remove the attenuator from input I get the "ringing" and same thing with the other 6 cables.
Thanks in advance
N8AUM Vidas
I'm interested in building a reflection bridge and was wondering which toroids you used in your design?Google this: directional coupler design
Are there any high impedance probes that can be used with the SSA3000X?
Seems like the interest for this has died off.
No F/W updates for 3 months especially for doing manual B/W adjustments that keep decreasing sweep speeds no matter if the B/W settings are increased or decreased.
No F/W updates for 3 months especially for doing manual B/W adjustments that keep decreasing sweep speeds no matter if the B/W settings are increased or decreased.
Hi guys
Just picked up a 3021x.
Seems pretty good so far but just scratched the surface.
Wondered if there was a way to turn off the time limited measurement functions and re-enable when needed?
Couldn't see a setting for that in the menu.
Is it just done on run time so once the 48hrs is up that's it?
Had a quick search though this thread but didn't spot anything in regards to that. (or even looked at the manual yet....)
Cheers
No F/W updates for 3 months especially for doing manual B/W adjustments that keep decreasing sweep speeds no matter if the B/W settings are increased or decreased.
I have now used this SA after it have first time be available.
I have never meet this problem what I do not even understand what you mean.
I have adjusted RBW's up and down and always sweep speed follow logically up and down automatically (until I force sweep speed to - manual mode - what operation seems to have little development needs)
No F/W updates for 3 months especially for doing manual B/W adjustments that keep decreasing sweep speeds no matter if the B/W settings are increased or decreased.
I have now used this SA after it have first time be available.
I have never meet this problem what I do not even understand what you mean.
I have adjusted RBW's up and down and always sweep speed follow logically up and down automatically (until I force sweep speed to - manual mode - what operation seems to have little development needs)
I have found this issue as well, when configuring the spectrum analyser to work with an external sweep generator.
When Manual sweep time is selected, manually changing the resolution bandwidth or video bandwidth will change the sweep time.
For example, reducing the RBW will slow the sweep speed.
After that increasing the RBW slows the sweep speed some more.
If the RBW or VBW is continually changed Up and Down, the sweep time just keeps getting slower.
Several other issues have also shown up.
1. With FW ver 1.2.8.5a, In the Amplitude menu when the Units are changed from dB to anything else, the vertical scale does not
change. Only the Reference Level text changes to reflect the new Units.
Previously the Vert Scale did change to show the selected units.
2. In Zero Span mode, at frequencies below 9.3Mhz, the Tracking Generator level increases by approx. 2.5dB.
When sweeping, this increase in level does not occur.
Regards.
I notice that with the input terminated with 50 ohms and the unit at the factory preset, power on settings there is a 5-10dB slope rising from 0 Hz to 2.1 GHz. Is there a setting to correct this?
In general I would like to store a trace and then subtract it from another stored trace or the current input trace. Is this possible? If so, how?
Base noise can not correct to flat. (oh well... it "can" but then we loose most important things, signal level flatness what is real important. )
It is natural and quite common in spectrum analyzers that base noise level rise when we go to higher frequencies.
This do not affect signal level accuracy. It is corrected by internal flatness table (1) - for every single individual SA (this is done by factory and this is one important part of factory calibration data (discussed also in some "hack" threads.
Also PreaAmplifier flatness is corrected so that measured signal levels are in specifications. And as can see it also produce bit different base noise. If we look more carefully this base noise it have quite complex shape with many hills and valleys.
This is one individual SA noise floor but other SA may be some amount different.
(https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/?action=dlattach;attach=234072;image)
SSA3021X (previously in this thread:"Reply #212 on: June 18, 2016, 11:54:05 AM" )
Do not worry it is not flat. (as long as it is inside specs.)
(https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/?action=dlattach;attach=354386;image)
SSA3000X DANL
(https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/?action=dlattach;attach=354395;image)
Edit/add: Keysight N9320B DANL specs.
(1) every SSA3000X have after factory calibration process individual level and flatness correction table. It is in folder "calib".
Example every 52 attenuator level (0-51dB) have its own 8kb level correction table. Also, there are many other factory cal data.
I know this reply dates quite a while, but I received my SA last week and it "seemed" to be a previously used/returned unit (no screen plastic, really small dent on the casing).
After unpacking the unit, noise floor curve looked quite higher than the average ones I saw in videos/reviews but the image you posted makes me think there's something wrong with my SA.
I've used the same parameters you used to do a 2.1gig sweep, RBW/VBW 1kHz, all traces average (same colour/trace per measurement), sweep mode "sweep" and input 50ohm terminated. Check this out:
(https://preview.ibb.co/jEM6n7/PNG13.png) (https://ibb.co/kcVz77)
Also, the TG flatness (which I think it should be somewhere less or around 3dB) is quite off to. I'm not that concerned about that since the cables I had lying around are long and old but still, I have a bad feeling about this particular unit...
Has anyone had a problem like this with Siglent instruments?
Seems like rf-loop has some particularly good specimen of this analyzer - maybe some early hand-crafted/polished prototype ;)
If I look at your measurements @ 2.1GHz and compare it to the specifications, then I get this:
RBW=10kHz, Preamp=on Measured: -119dBm; Specified: <-115dBm, typ. -118dBm; >typ.
RBW=10kHz, Preamp=off Measured: -101dBm; Specified: <-95dBm, typ. -99dBm; >typ.
RBW=1MHz, Preamp=on Measured: -98dBm; Specified: <-95dBm, typ. -98dBm; =typ.
RBW=1MHz, Preamp=off Measured: -80dBm; Specified: <-75dBm, typ. -78dBm; >typ.
As far as I can tell your unit is not only within the guaranteed specifications, but also meets or even exceeds the typical ones.
I know this reply dates quite a while, but I received my SA last week and it "seemed" to be a previously used/returned unit (no screen plastic, really small dent on the casing).
After unpacking the unit, noise floor curve looked quite higher than the average ones I saw in videos/reviews but the image you posted makes me think there's something wrong with my SA.
I've used the same parameters you used to do a 2.1gig sweep, RBW/VBW 1kHz, all traces average (same colour/trace per measurement), sweep mode "sweep" and input 50ohm terminated. Check this out:
(https://preview.ibb.co/jEM6n7/PNG13.png) (https://ibb.co/kcVz77)
Also, the TG flatness (which I think it should be somewhere less or around 3dB) is quite off to. I'm not that concerned about that since the cables I had lying around are long and old but still, I have a bad feeling about this particular unit...
Has anyone had a problem like this with Siglent instruments?
I think it need look bit more deeply.
I have one concern from what I see in your image. But I do not tell it yet before some further knowledge about your individual unit. (these traces are still in specs but....)
But first I need know do you have any reliable trusted signal source, pure sine wave and example between 5 - 50MHz what level you really KNOW so that absolute error is least less 1 dBm. Something between -30dBm to 0dBm.
Measure some these known level signals with SSA and note if level error is inside this method reliable limits or clearly outside.
And note, RF input is extremely sensitive for EOS/ESD and it happen easy! You do not feel any "static electric" and still it can be damage level. This is common to all, not for just you.
Even if you do not have reliable known level source:
1.
Set factory defaul. RF input terminated
Set trace A Clear write
Set trace D Clear write
Set Detector Trace A: "Average Log Pwr"
Set Detector Trace D: "Pos Peak"
Set RBW=VBW=10kHz
Set Attenuator 0dB
Set Ref level -50dBm
(https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/?action=dlattach;attach=407208;image)
Take this kind of image, SA continuously running
2.
Set SA for factory preset (defaults)
Connect SSA own Ref Out (10MHz) to RF input.
Set Atten 30dB
Set Ref level +10dBm
Set center Frequency 10MHz
Set RBW 300kHz
Press Peak (marker show now peak value, note this value)
(https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/?action=dlattach;attach=407210;image)
Take this kind of image, SA continuously running
Then if you want at this time do more
Set factory defaults
connect again 10MHz ref out to RF in.
Set center freq 10MHz, Span 10kHz (I believe you see 1kHz RBW)
Set attenuator 30dB and reference level +10dBm
Press Peak and select also in this menu Cont Peak ON
Note marker level
Press System
In this menu select Calibration
There open selection AutoCal and it is "Close"
Turn it "Open" and note how much your marker level change.
Write down "Open" value and "Close" value of marker level.
Tell these both values.
Short (maybe stupid) question...In Siglent specifications there read bit more: sample detector, trace average >50
I would like to verify the DANL of my device.
In the specifications table, they write "detector = sample detector".
Wouldn't "detector = average Log Pwr" make more sense?
Short (maybe stupid) question...In Siglent specifications there read bit more: sample detector, trace average >50
I would like to verify the DANL of my device.
In the specifications table, they write "detector = sample detector".
Wouldn't "detector = average Log Pwr" make more sense?
Exercise:
Set center freq 250MHz, Span 100MHJz. Atten 0, ref level -50dBm, RBW=VBW=1kHz
Set trace A for sample detector. set trace A first for Clear write
Set trace B for average Log Pwr, no trace average.
Set Marker 1 trace B (just normal marker)
Set Marker 2 trace B abs go to Marker Fn, set marker 2 function as Noise marker
Marker menu, set marker table on.
Look values and look also how Sample and Average LogPwr tracews differ.
Set trace A Average times 50 and leave it alone. After some time come and look result. ;)
About visible noise level (trace on the screen):
THis what you see is after gaussian type RBW. But also it is displayed noise.
Now all know that 1000Hz RBW and 1Hz RBW difference is 30dB if look noise.
But it not right for noise dBm/Hz because this mean 1Hz wide noise after square filter, not after gaussian shape filter. If normal marker there read example -118dBm it can not convert for noise level just subtracting 30dB.
Now look again markers. Noise marker and normal marker difference is not 30dB, it is 27.5dB. Simple story can read in this Keysight pdf what also explain lot of how SSA3000X works.
Keysight AN-150
http://literature.cdn.keysight.com/litweb/pdf/5952-0292.pdf (http://literature.cdn.keysight.com/litweb/pdf/5952-0292.pdf)
-----------
@leix_99
This do not proof all is ok but in these images I can not see this kind of signs of damaged front end what I have previously seen. This tiny test result: all looks like ok.
Why I previously slightly suspect something and like see bit more. You told that perhaps this your unit is not exactly factory new. Other thing was that base noise looks bit different what I have seen in many units - perhaps older ones.
Also there is not visible these Spur signals what have been typical and what I also bit wonder - perhaps they have done some improvements in HW.
If front GaAs RF switch is damaged it typically leads to wrong signal levels, perhaps noise level wrong but also I have seen big difference between AutoCal Open and Close.
What is your manufacturing date (or cal cert date). It looks like it have perhaps improved HW what I have.
Just do not look this base noise level with magnifier. It is less important what you perhaps think when we are talking this kind of levels, example what can see in your images, in this kind of SA. There is lot of much more important things.
Hi,Welcome to the forum Kevin.
New forum member here.
Just received my 3021x yesterday. Repaired instruments including Spec ans early in my working life. But used them for the last 30+ years.
Still getting my head around using the Siglent user interface.
I notice when using the tracking generator and normalising the display..when leaving the TG mode to look at noise levels..it retains the normalised offset, which is a little confusing..so have to remember to switch normalizing off, also when switching The TG off.
But impressed with the package.
hello.
I update from 1.2.8.5a to 1.2.9.1 and lost the service info to.?? Bugs? Never tried to hack the SSA3021.
Get it few days ago.
Someone tried to only activate the the options on this last firmware? It was delivered with TG
could you please verify the issue I described in my previous thread (from May 20, 2018, 06:56:05 am),
means the behavior of the SSA when changing the RBW from 10Hz to 3Hz if you have a SSA with the
newest FW (1.2.9.1).
Hi,
I'm thinking about adding the RBSSA3X20 reflection bridge to my new SA3032x, but I have a few novice questions:
- Has anyone done a review of it?
- What are the main uses ?
- Is is anyway worth buying one considering I have a DG8SAQ VNWA, which I'm pretty happy with?
High spec Wiltron bridges can be good value from ebay.
These regularly sell at <$200 on ebay.
I am considering buying my first SA in the near future to expand my projects and understanding towards the RF space. If I do decide to go that road, SSA3021X seems like a strong candidate at the moment. I have checked RF explorers and such lower cost solutions to start with but feel I might regret it later, considering these low-cost 'proper' bench units.Hi, Dunno why you'd want to overlook your local authorized agents ? :-//
How the price of these instruments have developed in the past? Siglent.eu have SSA3021X €1299 now, including TG, plus VAT. I'm in the UK so this means around £1400. Siglent.eu also seem to have 4% discount if paid by bank transfer. Has there been good prices and/or bundles elsewhere?
I ignored Tester simply because it is more expensive. If I do all research myself and do not need actual service or help from the store, I am not willing to pay much premium. But a little bit for a local shop. I will definitely use Labtronix if I decide to buy. I am just still trying to understand my requirements in the near future and the differences between SSA3021X and SVA1015X. So maybe I will need help from a store after all :>If you don't need the 2.1 GHz (or 3.2 GHz liberated) BW then the SVA is the better choice.
Has this finally fixed that RBW/VBW manual adjustment problem the keeps slowing down manually set speed speeds?? ???No, of course not. Bad set of priorities. :--
I used a 60mm fan from noctua.
That I now regret, since that I believe my unit might have its power measurements off by 5 dBm...
File Header Size: 00000070
00000000 - File Checksum: C6D2CA2A [00000004-0072EEFA] (with only the File Header decrypted) CKSM OK
00000004 - File Size: 0072EE8B (without 0x70 bytes of the File Header)
0000000C - Product_ID: 11201
00000026 - Vendor/Brand: SIGLENT
0000003A - USB Host Controller: ISP1763
****************************************************
Decrypting the 0x2800 and 0x1400 blocks...
Reversing file...
XORing with 0xFF (incrementing pattern)...
XORing with 0xFF from 0x00397746 until 0x0072EE8A
****************************************************
00000000 --- Section Checksum: C488E8D3
00000004 --- Section Size: 0072EE57 [00000034-0072EE8A] CKSM OK
00000008 --- Section # 00000007
00000034 --- 0072EE8A ***** ZIP file *****
Offset Ver Flag Comp Size Packed Modified CRC32 Name Permissions Extra Details
00000034 2.0 0000 0008 00200000 00001375 25-09-2018 11:36:16 6819C331 [00000078-000013EC] datafs.img -rw-rw-r-- MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:32 UID: 1000 GID: 1000
000013ED 1.0 0000 0000 00000000 00000000 25-09-2018 11:36:16 00000000 [0000142F-0000142E] drivers/ drwxrwxr-x MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:33 UID: 1000 GID: 1000
0000142F 2.0 0000 0008 00002A4A 00000F3A 25-09-2018 11:36:16 14C7A03C [00001478-000023B1] drivers/gpib.ko -rw-rw-r-- MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:32 UID: 1000 GID: 1000
000023B2 2.0 0000 0008 00006A48 00002BE5 25-09-2018 11:36:16 CA33EA6B [000023FF-00004FE3] drivers/g_usbtmc.ko -rw-rw-r-- MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:32 UID: 1000 GID: 1000
00004FE4 2.0 0000 0008 00005EDF 00002556 25-09-2018 11:36:16 78A95587 [00005031-00007586] drivers/da8xx-fb.ko -rw-rw-r-- MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:32 UID: 1000 GID: 1000
00007587 2.0 0000 0008 0000128D 0000089F 25-09-2018 11:36:16 6CCA4FE4 [000075D5-00007E73] drivers/cfbimgblt.ko -rw-rw-r-- MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:32 UID: 1000 GID: 1000
00007E74 2.0 0000 0008 000013AC 00000A2A 25-09-2018 11:36:16 8FEE5627 [00007EC4-000088ED] drivers/cfbcopyarea.ko -rw-rw-r-- MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:32 UID: 1000 GID: 1000
000088EE 2.0 0000 0008 0000186C 00000ADB 25-09-2018 11:36:16 C239CAAF [0000893E-00009418] drivers/cfbfillrect.ko -rw-rw-r-- MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:32 UID: 1000 GID: 1000
00009419 2.0 0000 0008 004D964C 0022795D 25-09-2018 11:35:17 049F1727 [00009458-00230DB4] ecomb -rwxrwxr-x MTime: 25-09-2018 03:35:33 UID: 1000 GID: 1000 MTime: 25-09-2018 03:35:33 ATime: 25-09-2018 03:35:33 UID: 1000 GID: 1000
00230DB5 2.0 0000 0008 001E0000 00001023 25-09-2018 11:36:16 B3370AC7 [00230DFC-00231E1E] firmdata0.img -rw-rw-r-- MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:32 UID: 1000 GID: 1000
00231E1F 2.0 0000 0008 0016AF20 000651E4 25-09-2018 11:36:16 AE4CBE43 [00231E64-00297047] LcdFpga.bin -rwxrwxr-x MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:32 UID: 1000 GID: 1000
00297048 2.0 0000 0008 0001E41C 0000F77C 25-09-2018 11:36:16 F38C8EDE [0029708F-002A680A] libpng12.so.0 -rwxrwxr-x MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:32 UID: 1000 GID: 1000
002A680B 2.0 0000 0008 0001E41C 0000F77C 25-09-2018 11:36:16 F38C8EDE [002A6857-002B5FD2] libpng12.so.0.49.0 -rwxrwxr-x MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:32 UID: 1000 GID: 1000
002B5FD3 2.0 0000 0008 0000BA27 00006871 25-09-2018 11:36:16 9C495326 [002B6010-002BC880] MLO -rw-rw-r-- MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:32 UID: 1000 GID: 1000
002BC881 2.0 0000 0008 0021B0D0 00218F31 25-09-2018 11:36:16 7A0BB362 [002BC8C4-004D57F4] ro_uImage -rw-rw-r-- MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:32 UID: 1000 GID: 1000
004D57F5 2.0 0000 0008 0021B0D0 00218F47 25-09-2018 11:36:16 B2C5AD17 [004D5838-006EE77E] rw_uImage -rw-rw-r-- MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:32 UID: 1000 GID: 1000
006EE77F 2.0 0000 0008 000020DC 00000815 25-09-2018 11:36:16 347B8F86 [006EE7C6-006EEFDA] siglentlib.sh -rwxrwxr-x MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:32 UID: 1000 GID: 1000
006EEFDB 2.0 0000 0008 000595D0 0002D08B 25-09-2018 11:36:16 EC7B07E7 [006EF01F-0071C0A9] u-boot.img -rw-rw-r-- MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:32 UID: 1000 GID: 1000
0071C0AA 1.0 0000 0000 00000000 00000000 25-09-2018 11:36:16 00000000 [0071C0EC-0071C0EB] ui_data/ drwxrwxr-x MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:33 UID: 1000 GID: 1000
0071C0EC 2.0 0000 0008 0000160D 00000689 25-09-2018 11:36:16 D002C2A9 [0071C143-0071C7CB] ui_data/english_text_info.xml -rw-rw-r-- MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:32 UID: 1000 GID: 1000
0071C7CC 2.0 0000 0008 0000623D 00000FBF 25-09-2018 11:36:16 F2DA58A7 [0071C820-0071D7DE] ui_data/simp_menu_info.xml -rw-rw-r-- MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:32 UID: 1000 GID: 1000
0071D7DF 2.0 0000 0008 00006565 00000ED8 25-09-2018 11:36:16 C86FDA59 [0071D836-0071E70D] ui_data/english_menu_info.xml -rw-rw-r-- MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:32 UID: 1000 GID: 1000
0071E70E 2.0 0000 0008 00014785 00004BB6 25-09-2018 11:36:16 2B0CA9CE [0071E765-0072331A] ui_data/russian_help_info.xml -rw-rw-r-- MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:32 UID: 1000 GID: 1000
0072331B 2.0 0000 0008 00011F50 00004523 25-09-2018 11:36:16 17828A1B [0072336F-00727891] ui_data/simp_help_info.xml -rw-rw-r-- MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:32 UID: 1000 GID: 1000
00727892 2.0 0000 0008 00008345 0000127C 25-09-2018 11:36:16 B5388358 [007278E9-00728B64] ui_data/russian_menu_info.xml -rw-rw-r-- MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:32 UID: 1000 GID: 1000
00728B65 2.0 0000 0008 000144C3 000049A0 25-09-2018 11:36:16 47F8EB83 [00728BBC-0072D55B] ui_data/english_help_info.xml -rw-rw-r-- MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:32 UID: 1000 GID: 1000
0072D55C 2.0 0000 0008 0000163B 0000071B 25-09-2018 11:36:16 C6247586 [0072D5B0-0072DCCA] ui_data/simp_text_info.xml -rw-rw-r-- MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:32 UID: 1000 GID: 1000
0072DCCB 2.0 0000 0008 0000160D 00000689 25-09-2018 11:36:16 D002C2A9 [0072DD22-0072E3AA] ui_data/russian_text_info.xml -rw-rw-r-- MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:32 UID: 1000 GID: 1000
0072E3AB 2.0 0000 0008 00000139 0000009B 25-09-2018 11:36:16 1815AEC9 [0072E3EF-0072E489] upgrade.sh -rwxr--r-- MTime: 25-09-2018 03:36:32 UID: 1000 GID: 1000 MTime: 25-09-2018 03:36:32 ATime: 25-09-2018 03:36:32 UID: 1000 GID: 1000
Disk Entries: 29 Total Entries: 29 Directory Size: 2539 bytes [0072E48A-0072EE74]
****************************************************
File Processed OK
There have been numerous reports in the other Siglent thread about failed flashing with this F/W. One user had to send his unit back ti Siglent to be flashed.
I'm surprised there aren't any comments either way here.
Separately, on Siglents website, their date shows "Release Date 02.08.19" which is almost three months later from the above posts. Was there more than one version of this "a" ???
Yes, I did notice that Sept. date.
There were at least three starting Jan 4th, post 586. I thought there were more, but it was regarding moding. It just seem very odd, three in a row.
I would love to know what will it take to get this fixed??1. Changing RBW and/or VBW settings (in manual mode) changes sweep speeds. Everytime one adjusts either setting the sweep speed slows down one step. This continues to happen even if you return the setting to where it was. The sweep speed keeps slowing. I never encountered this before and it is REAL annoying. (see below)
2. The 'standby mode' is a power hog by today's standards. Five watts running 24/7 shouldn't be acceptable anymore. That's 1/6th of the operational current (28-29 watts). I assume this has wake on LAN or similar? Fine, but does it have to be that much of a hog? How about a option to disable and 'wake' mode to get the draw down below 1 watt (EPA standard)? At least that would be a somewhat quick fix, assuming it can be done thru the firmware.
Setup conditions for #1 (easy to duplicate):
1. Place the RBW, VBW & Sweep settings all in manual mode. Set the two bandwidths to a middle setting. Settings for the attenuator or units shouldn't matter. No signal is required.
2. Change the Sweep to the fastest setting (usually 24ms)
3. Set the frequency range to whatever you want[/b], the full bandwidth is fine though I never have a need for that. My ranges are usually between 50 & 500 Mhz.
4. Go to the BW page and start changing either of the two adjustments paying attention to the sweep speed. You can use either the 'jog' dial or the up/down buttons. You will see it drop to the next slower speed.
5. Now, here where it gets more interesting, return to the previous setting. Note the sweep speed still slowing instead of returning to where it was.Everytime you make any adjustment to either the RBW or the VBW in either direction the sweep slows down to the next fixed setting forcing one to return to the sweep page and crank to back to the fastest setting allowed. Trying to get a respectable display is a real chore jumping back and forth between BW & Sweep.
Am I missing something here, or it that the ultimate 'bug'? ???
If something like that appeared on my unit I would create a real fuss! :box:
Correct, I was not joking.
A. I don't do vidiot games having close to zero interest in that lame pastime (same goes for toy idiot phones)
B. I didn't consider this a "Linux PC" in spite of it running Linux (which I kinda forgot since that isn't a day to day function).
"Ancient"?? ::)
New firmware for SSA3000X models.
Version 1.2.9.3a
7.5 MB
http://old.siglentamerica.com/USA_website_2014/Firmware&Software/firmware/SSA3000X_1.2.9.3a_EN.zip (http://old.siglentamerica.com/USA_website_2014/Firmware&Software/firmware/SSA3000X_1.2.9.3a_EN.zip)
New firmware for SSA3000X models.
Version 1.2.9.3a
7.5 MB
http://old.siglentamerica.com/USA_website_2014/Firmware&Software/firmware/SSA3000X_1.2.9.3a_EN.zip (http://old.siglentamerica.com/USA_website_2014/Firmware&Software/firmware/SSA3000X_1.2.9.3a_EN.zip)
number 7 alone is worth it
New firmware for SSA3000X models.
Version 1.2.9.3a
7.5 MB
http://old.siglentamerica.com/USA_website_2014/Firmware&Software/firmware/SSA3000X_1.2.9.3a_EN.zip (http://old.siglentamerica.com/USA_website_2014/Firmware&Software/firmware/SSA3000X_1.2.9.3a_EN.zip)
SSA3032X TG output shut off after being on several hrs even tho it says its on. Turned off TG than on again but still no output. Reset (Preset) no help, had to power cycle unit in order to get TG to work again.
SSA3032X Firmware ver 1.2.8.3
HmmmmSSA3032X TG output shut off after being on several hrs even tho it says its on. Turned off TG than on again but still no output. Reset (Preset) no help, had to power cycle unit in order to get TG to work again.
SSA3032X Firmware ver 1.2.8.3
I have a brand new ssa3021x, just couple of days old. and today, after playing with TG for an hour, TG output was gone even though display said it was on. power cycle it again and same problem happened again 20 min later. do you find any solution?
here is the info:
SW1 1.2.9.2.a
SW2 20180708-1
SW3 000000E1
HW 0F.03.00
Hasn’t there been a delay on delivery of the first SSA3032X because Siglent had to do a revision of the tracking generator for its unsatisfactory output level flatness?No, while the TG flatness is early units was not good later HW versions were revised to improve flatness but supply AFAIK was never affected. The Ohio GM made posts about this HW change earlier in this thread.
I would not be surprised if the circuit boards produced up to that point had not been thrown away but used up for the low cost 2.1GHz SSA3021X instead.Possibly IDK or even reworked for better flatness. AFAIK there are screen shots of early HW TG flatness here if you hunt them out, however the issue didn't effect typical operation after Normalization.
Does anybody have any idea how to recover a SSA3021x that is stuck on the boot screen?I'm sure the forum community can help but we need a bit more info than what you have provided here:
Regarding the latest F/W. Any issues so far (in spite of nothing reported) and any of those 'fixes' amount to anything?No issues, all new units come with 9a installed.
I see Siglent still refuses to acknowledge, let along address the BW/Sweep issue.From my investigations it's a known issue and a big rewrite of code to fix so will take time.
Does anybody have any idea how to recover a SSA3021x that is stuck on the boot screen?
Thanks for that, that is the 1st I had a somewhat straight answer (including Siglent) as to the problem that is well over a year old. But, if the newer model doesn't have the problem, they obviously figured out what/where the problem is, one would logically think that would/could be re-written here also.I see Siglent still refuses to acknowledge, let along address the BW/Sweep issue.From my investigations it's a known issue and a big rewrite of code to fix so will take time.
FYI SVA models are not affected.
We hope so too and it's only recently that I've had a direct line to the SSA/SVA team.Thanks for that, that is the 1st I had a somewhat straight answer (including Siglent) as to the problem that is well over a year old. But, if the newer model doesn't have the problem, they obviously figured out what/where the problem is, one would logically think that would/could be re-written here also.I see Siglent still refuses to acknowledge, let along address the BW/Sweep issue.From my investigations it's a known issue and a big rewrite of code to fix so will take time.
FYI SVA models are not affected.
Anyone have a recommendation for a good transient limiter? Since I will be mainly using by Siglent for EMC work something with high pass filter would be nice.What pads/attenuators do you have already ?
Anyone have a recommendation for a good transient limiter? Since I will be mainly using by Siglent for EMC work something with high pass filter would be nice.I don't have it, but this one looks really decent:
couldn't for the life of me remember where i bought the darn thing, spent a week looking for the receipts and what not for the ohio peeps, and then when i turned it back on it was back to normal, it's been good for a few weeks now. so i guess we shall see how it goes.Great ! :clap:
HiI was just wondering that, I'll find out.....I hope so.
Are the Plus software options available for the "old" model?
Dazz
From the price list the options have different name:HiI was just wondering that, I'll find out.....I hope so.
Are the Plus software options available for the "old" model?
Dazz
HiFirst reply is NO as the HW is different. :(
Are the Plus software options available for the "old" model?
Dazz
Next we investigate if these demod options can be added after a new SSA3kX FW.............
HiFirst reply is NO as the HW is different. :(
Are the Plus software options available for the "old" model?
Dazz
Next we investigate if these demod options can be added after a new SSA3kX FW.............this reply is taking longer.....maybe we don't get that reply tonight......just came in, sorry no, cannot be done.
Sorry Dazz. :(
Cmon, open the other box. Chop chop...:P
Hello everybody,Welcome to the forum.
this is my first post in this amazing Forum.
I have finally decided to buy my first SA and I am thinking about the SSA3021. It's a big investment (for me) but it seems a good device to learn and experiment.
I have a question: Is it possible to get out the IF signal (or data about it, e.g., I/Q stream?).The recently updated SSA3021X Plus now incorporates Modulation Analysis as the SVA range had from release.
The recently updated SSA3021X Plus now incorporates Modulation Analysis as the SVA range had from release.
It also has been upgraded to a touch and mouse capable instrument and is little more expensive than the more basic SSA3021X.
Other than missing the VNA capability of the SVA models, SSA3021X Plus works the same as earlier models except for the new features I've mentioned and you can see them demonstrated in this The Signal Path video stopped at the start of IQ demodulation:
https://youtu.be/ToVJTKCyIU8?t=2660
Thanks a lot for the informative answer!TG is still free for SSA3kX, SSA3kX Plus and SVA1kX models and I expect it to remain so.QuoteThe recently updated SSA3021X Plus now incorporates Modulation Analysis as the SVA range had from release.
It also has been upgraded to a touch and mouse capable instrument and is little more expensive than the more basic SSA3021X.
Other than missing the VNA capability of the SVA models, SSA3021X Plus works the same as earlier models except for the new features I've mentioned and you can see them demonstrated in this The Signal Path video stopped at the start of IQ demodulation:
https://youtu.be/ToVJTKCyIU8?t=2660 (https://youtu.be/ToVJTKCyIU8?t=2660)
Unfortunately my budget is very limited so I'd like to focus mostly on the features of the basic SSA3021X, especially because it is offered wit the TG option for free until the end of March. Or I will be forced to look for 2nd-hand instruments.
So, please correct me if I am wrong, but it seems the only way to get a signal out (either in an analogue or digital, i.e., I/Q samples) of the SSA3021X is via the headphone/speaker jack (audio).Yes, but SSA3kX models cannot demodulate IQ signals, only SSA3kX Plus and SVA1kX models.
Question 1: Is this correct?
The SSA3021X can perform analog AM and FM demodulation using the speakers. ButUnknown to me sorry as I've only done AM and FM.
Question 2: Is it possible to perform SSB (USB or LSB) demodulation, somehow? I coudn't find infos about it in the manual. More generally, has anybody managed to use the SSA3021X to listen/receive Ham Radio bands?
Lastly, in my mind (but I stress that I am learning and don't have a SA yet), when in SPAN ZERO mode and using linear scale on the vertical axis, the SA acts as a simple Oscilloscope around the center frequency and the bandwidth of this "scope" is the RBW.Well sort of but a SA is a frequency domain instrument while a DSO's strength is the time domain. In this case CF and Span will be more use to cover the width of the signal of interest.
QUESTION 3: Isn't it possible to get out this "scope" signal, at least when the RBW = 16Khz or something, using the headphone?
N9340B:
(Attachment Link)
SSA3000:
https://www.flickr.com/photos/eevblog/27749729501/in/album-72157669490076552 (https://www.flickr.com/photos/eevblog/27749729501/in/album-72157669490076552)
...
Kind of interesting though... i guess this makes it an HP / Rigol bastard child? I'm kinda tempted to take my Plus version open and take some pics to compare with now
Is it really THAT similar? Isn't the design conditioned by physics?
And of course they opened existing devices for some reverse engineering... Everyone does that.
I don't see any problem here.
Regards,
Vitor
The one thing that makes me wonder is that Siglent used components for designing the SSA3000X series of which at least some must have been listed EOL or even obsolete already at the time of design. If these are identical with the N9340B (codes not clearly readable in @Elasia's photo), I would call this strong evidence.
Maybe the release of the "Plus" model after only a few years into production of its predecessor was required due to the availability situation of these components?
Sorry, confused you with @1design -- was about to leave and somewhat in a hurry... Apologies to you both ;)
Who wants to try? ;)
As always Tv84 doing his thing :-+
So the big question is can you obtain the VNA on this model as well?
I present to you a SSA fully optioned up including the hidden features
Big thanks to tv84 for his decryption work
By request, screenshot of unlocked 3021X-PlusHmmm, not quite as interesting as the one from Elasia a few posts back. :popcorn:
By request, screenshot of unlocked 3021X-PlusHmmm, not quite as interesting as the one from Elasia a few posts back. :popcorn:
SSA3075X Plus and SVA1075X are new HW AFAIK.
Also, is there a SSA7075X Plus? Or the 7.GHz is a SSA3032X Plus on steroids?
Elasia :
Where did you buy your SSA3021X ?
Is it from Batronix in Germany ?
Thank you :)
SSA3075X Plus and SVA1075X are new HW AFAIK.
Also, is there a SSA7075X Plus? Or the 7.GHz is a SSA3032X Plus on steroids?
Also SSA3000X-R models of 5 and 7.5 GHz might be new HW too ? :-//
What about my 4-year old question? :)
Assuming I'm 4 years old, who can explain me the differences between:
Siglent SVA1032X
Siglent SSA3032X Plus
Also, is there a SSA7075X Plus? Or the 7.GHz is a SSA3032X Plus on steroids?
SSA3075X Plus and SVA1075X are new HW AFAIK.
Also, is there a SSA7075X Plus? Or the 7.GHz is a SSA3032X Plus on steroids?
Also SSA3000X-R models of 5 and 7.5 GHz might be new HW too ? :-//
What about my 4-year old question? :)
Just like tau said.. its a different hardware platform im pretty sure as well from everything i could read on it.. also this one is limited by hardware design that TSP goes over in his breakdown, so yeah no 7Ghz here
SSA3075X Plus and SVA1075X are new HW AFAIK.
Also, is there a SSA7075X Plus? Or the 7.GHz is a SSA3032X Plus on steroids?
Also SSA3000X-R models of 5 and 7.5 GHz might be new HW too ? :-//
What about my 4-year old question? :)
Just like tau said.. its a different hardware platform im pretty sure as well from everything i could read on it.. also this one is limited by hardware design that TSP goes over in his breakdown, so yeah no 7Ghz here
I was asking the differences between these 2:
Siglent SVA1032X
Siglent SSA3032X Plus
Registering on this forum was the most dangerous decision for my money wallet :rant:
Also this requires more moderate knowledge as its not just enabling option keys and makes it not compatible with future updates without rework
Also this requires more moderate knowledge as its not just enabling option keys and makes it not compatible with future updates without rework
I thought a bit over this phrase and.... :popcorn:
You just have to flash the appropriate stock file! No need for further rework.
Also this requires more moderate knowledge as its not just enabling option keys and makes it not compatible with future updates without rework
I thought a bit over this phrase and.... :popcorn:
You just have to flash the appropriate stock file! No need for further rework.
Your mileage may vary, i suspect so but not trying that one, i like to always have a backout plan :P
I'd assume you could just change the product type bits in the file and put out a new one
Also this requires more moderate knowledge as its not just enabling option keys and makes it not compatible with future updates without rework
I thought a bit over this phrase and.... :popcorn:
You just have to flash the appropriate stock file! No need for further rework.
Your mileage may vary, i suspect so but not trying that one, i like to always have a backout plan :P
I'd assume you could just change the product type bits in the file and put out a new one
;D You just have to do a NAND backup of the equipment. With that you're safe.
Yes, but there is even no need for it because the app is already expecting the new Prod_ID! Poetry...
A few hours later, after a very stressful session!
(Attachment Link)
.. and permanent telnet enabled :)
What are the Options RCV and RTA?
What are the Options RCV and RTA?
It's a bit off topic, but if tautech was really a nice guy, He would have bought each model from Siglent with detailed teardown.I am a really nice guy :P but like most, I too don't have unlimited funds. :(
Only on SDS5000X, if it turns out that now the front end is the same on the whole family, it would double sales of this model for Siglent ;DWe'll know soon enough when member supperman gets a recent build SDS5034X and tests it to 1 GHz. :popcorn:
It's a bit off topic, but if tautech was really a nice guy, He would have bought each model from Siglent with detailed teardown.I am a really nice guy :P but like most, I too don't have unlimited funds. :(QuoteOnly on SDS5000X, if it turns out that now the front end is the same on the whole family, it would double sales of this model for Siglent ;DWe'll know soon enough when member supperman gets a recent build SDS5034X and tests it to 1 GHz. :popcorn:
Still 3 unknowns: NA, MA and tALL
I just bought an SSA3021X Plus |O
I just bought an SSA3021X Plus |O
Have you been going to your TEA sessions?
I just bought an SSA3021X Plus |O
I just bought an SSA3021X Plus |O
I just don't get it...
Is there something wrong with the SSA3021X Plus ??
(Yes, I just bought one. Now I'm nervous!)
Hallo,
I own a SSA3021X Plus and I wondered what would happen if I just by mistake uploaded the SVA1032 firmware file. Would it work and would the telnet firmware upgrade file for the SSA3021X Plus stil work?
Just wondering.
Ok I volonteerd,Hallo,
I own a SSA3021X Plus and I wondered what would happen if I just by mistake uploaded the SVA1032 firmware file. Would it work and would the telnet firmware upgrade file for the SSA3021X Plus stil work?
Just wondering.
"Hallo"! You definitely can't do that by mistake! Nonetheless I have a feeling it will work. But that is one of the current open questions. Any volunteer?
Regarding the telnet FW: the SSA probably will not work, but the SVA one should work...
Ok I volonteerd,
first I did it with the upgrade intact and there was the same upgrade window as with the telnet session. After 20 min I did a soft powerdown and the Analyzer booted up fine as a SSA.
After that I rolled bach the upgrade and tryed again with the same result.
It could have been so nice.
I put the SVA1032X_2.2.1.2.5.ADS on a memory stick and did a Firmware Update. That gave me a screen with "Updating" for 20 min. Then I aborted bij a soft powerdown.
No harm done but no gain
New firmware for SSA3021X and SSA3032X Plus models.
Version V2.2.1.2.7
15.8MB
https://int.siglent.com/upload_file/zip/firmware/Spectrum_analyzer/SSA3021&32X%20Plus_2.2.1.2.7_EN.zip
:-//New firmware for SSA3021X and SSA3032X Plus models.
Version V2.2.1.2.7
15.8MB
https://int.siglent.com/upload_file/zip/firmware/Spectrum_analyzer/SSA3021&32X%20Plus_2.2.1.2.7_EN.zip
Hmm ??? Now is this going to work out of the box for an SSA3032X Plus that "thinks" it's an SVA with all options.
:-//New firmware for SSA3021X and SSA3032X Plus models.
Version V2.2.1.2.7
15.8MB
https://int.siglent.com/upload_file/zip/firmware/Spectrum_analyzer/SSA3021&32X%20Plus_2.2.1.2.7_EN.zip
Hmm ??? Now is this going to work out of the box for an SSA3032X Plus that "thinks" it's an SVA with all options.
Then why would you use an SSA update ? :-DD
Makes sense don't it ? ;):-//New firmware for SSA3021X and SSA3032X Plus models.
Version V2.2.1.2.7
15.8MB
https://int.siglent.com/upload_file/zip/firmware/Spectrum_analyzer/SSA3021&32X%20Plus_2.2.1.2.7_EN.zip
Hmm ??? Now is this going to work out of the box for an SSA3032X Plus that "thinks" it's an SVA with all options.
Then why would you use an SSA update ? :-DD
Ah, ok :-+
Makes sense don't it ? ;):-//New firmware for SSA3021X and SSA3032X Plus models.
Version V2.2.1.2.7
15.8MB
https://int.siglent.com/upload_file/zip/firmware/Spectrum_analyzer/SSA3021&32X%20Plus_2.2.1.2.7_EN.zip
Hmm ??? Now is this going to work out of the box for an SSA3032X Plus that "thinks" it's an SVA with all options.
Then why would you use an SSA update ? :-DD
Ah, ok :-+
:scared:Makes sense don't it ? ;):-//New firmware for SSA3021X and SSA3032X Plus models.
Version V2.2.1.2.7
15.8MB
https://int.siglent.com/upload_file/zip/firmware/Spectrum_analyzer/SSA3021&32X%20Plus_2.2.1.2.7_EN.zip
Hmm ??? Now is this going to work out of the box for an SSA3032X Plus that "thinks" it's an SVA with all options.
Then why would you use an SSA update ? :-DD
Ah, ok :-+
Lol, indeed, I’m being an idiot :palm: But never been in this situation before, so new territory for me :)
Hmm ??? Now is this going to work out of the box for an SSA3032X Plus that "thinks" it's an SVA with all options.:-//
Then why would you use an SSA update ? :-DD
Hmm ??? Now is this going to work out of the box for an SSA3032X Plus that "thinks" it's an SVA with all options.:-//
Then why would you use an SSA update ? :-DD
The answer is not so easy as all the "hybrid" SSAs up to now are precisely that: hybrid. ;)
The best way would be for what techneut has "volunteered" to do: test a crossflash with the full SVA FW.
If that goes OK, then he would have a true SVA from then on.
I'll have to console it later and see what its doing now
********** Zynq-7000 SoC Boot Header **********
00000000 - ARM Vector Table: 8 x EAFFFFFE
00000020 - Width Detection: AA995566
00000024 - Header Signature: XLNX
00000028 - Key Source: 00000000 - Not Encrypted
0000002C - Version: 01010000 (0x01010000)
00000030 - FSBL Image Offset: 00001700
00000034 - FSBL Image Length: 00014014
00000038 - FSBL Load Address (RAM): 00000000
0000003C - FSBL Exec Address (RAM): 00000000
00000040 - Total FSBL Length: 00014014
00000044 - QSPI Configuration: 00000001 (0x00000001)
00000048 - Boot Header Checksum: FC16C518 CHKSUM OK
0000004C - User Defined: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
00000098 - Image Header Table Offset: 000008C0
0000009C - Partit. Header Table Offset: 00000C80
********** Zynq-7000 SoC Device Register Initialization Table **********
000000A0 - Register Initialization Pairs [000000A0-0000089F]
********** Zynq-7000 SoC Device Image Header Table **********
000008C0 - Version: 01020000 (0x01020000)
000008C4 - # Image Headers: 00000003
000008C8 - 1st Partition Header Offset: 00000C80
000008CC - 1st Image Header Offset: 00000900
000008D0 - Header Auth Certif Offset: 00000000
000008D4 - Reserved: FFFFFFFF
********** Zynq-7000 SoC Device Image Headers **********
Partitio Reserved Length Name
00000900 - 00000C80 00000000 00000001 fsbl.elf
00000940 - 00000CC0 00000000 00000001 fpga_top_sva3000x.bit
00000980 - 00000D00 00000000 00000001 u-boot.elf
********** Zynq-7000 SoC Device Partition Headers **********
EncryLen UnencLen TotalLen DestLoad DestExec ImgOffst AttrBits Sections Checksm ImHdOffs AuthOffs HdChkSum
00000C80 - 00014014 00014014 00014014 00000000 00000000 00001700 00000010 00000001 00000000 00000900 00000000 FFFF07DF CHKSUM OK
00000CC0 - 003DBB00 003DBB00 003DBB00 00000000 00000000 00080000 00000020 00000001 00000000 00000940 00000000 FFCFB14E CHKSUM OK
00000D00 - 0006D21C 0006D21C 0006D21C 04000000 04000000 00580000 00000010 00000001 00000000 00000980 00000000 F7E4DFF9 CHKSUM OK
yeah i got smoked, stuck at boot screen and also the prior system key trick doesnt work
I'll have to console it later and see what its doing now
- overwriting ONLY the SSA3032X app with the SVA1032X app (of the same FW version package).
echo "upgrade_app: starting"
if [ -f /usr/bin/siglent/ecomb ]; then
rm /usr/bin/siglent/ecomb
rm /usr/bin/siglent/libscpi*
fi
Thanks tv84 - that's great news!If you are worried about the nice shiny sticker, I applied some ipa and a hairdryer and put a thin wire in the slit between case and front bhind the sticker. With soft pulling it in the direction of the front it came loose.
At least there is no brick wall - small steps in the right direction and we will get there :)
Perhaps to help those with appropriate SSA3000x Plus hardware who are game enough to 'try' for themselves, we could post a failsafe recovery process from the 11 nandbackup images??
Easy enough to generate the backup images - but not sure if the recovery process is just plain simple restore the backup with a 'reverse' command script?
My worry is that if the device will be totally 'bricked' - so no access to file system (boot , let alone telnet not possible), then there is no option other than direct console access via PCB header.
Not so keen to 'break-into' new device just now if I brick it :(
Any 'passive' recovery method(s) would always be welcome - so more of us can 'have a go' at mastering the crossflash process ;)
Thanks tv84 - that's great news!If you are worried about the nice shiny sticker, I applied some ipa and a hairdryer and put a thin wire in the slit between case and front bhind the sticker. With soft pulling it in the direction of the front it came loose.
At least there is no brick wall - small steps in the right direction and we will get there :)
Perhaps to help those with appropriate SSA3000x Plus hardware who are game enough to 'try' for themselves, we could post a failsafe recovery process from the 11 nandbackup images??
Easy enough to generate the backup images - but not sure if the recovery process is just plain simple restore the backup with a 'reverse' command script?
My worry is that if the device will be totally 'bricked' - so no access to file system (boot , let alone telnet not possible), then there is no option other than direct console access via PCB header.
Not so keen to 'break-into' new device just now if I brick it :(
Any 'passive' recovery method(s) would always be welcome - so more of us can 'have a go' at mastering the crossflash process ;)
Successful upgrade
Also note.. some of the options vanished?
After restoration i just changed the version config file to the SVA code and ran the .7 ads file
Also here is the updated file to change the product id
its in /usr/bin/siglent/config
Successful upgrade
Also note.. some of the options vanished?
After restoration i just changed the version config file to the SVA code and ran the .7 ads file
Congrats Elasia - especially your quick recovery from a 'bricked' device.
Looking at your SVA system Info page - I drool with envy and fully appreciate the taste of the sweet nectar of success you must be enjoying now :clap:
Successful upgrade
Also note.. some of the options vanished?
After restoration i just changed the version config file to the SVA code and ran the .7 ads file
Congrats Elasia - especially your quick recovery from a 'bricked' device.
Looking at your SVA system Info page - I drool with envy and fully appreciate the taste of the sweet nectar of success you must be enjoying now :clap:
Thanks, yeah wasnt really bricked to the point of needing to hit them with jtag... it was my computer being a horses ass earlier and making all the serial port data garbage... switched to the tablet i use normally for reprogramming network switches... worked fine... pos comp lol
And yeah, tv knows what to do now to repack the firmware to convert it.. HOWEVER you need to buy the calibration kit, they do not come with SVA calibration data loaded, you must use the sva cali menu to do this yourself
I'll pick it up one of these days myself unless someone wanted to send me one :P~
SDR-kits.net in UK has excellent SMA calibration kits up to 12GHz for about $65 US. Each set (male and female) is individually calibrated and comes with full calibration specifications that should be able to be entered manually into the SVA1032XFrom a few days ago:
Jerry NY2KW
Those are good parts, but they are not properly characterised.hendorog and I have checked a few Cal kits against the factory SVA calibration and unless you're characterizing DUT's at some detail the factory calibration is quite good enough .....but it's only to the port so adapters and cables do add some error. DTF could give you some ps delay measurements to add into Port extensions that might improve basic results without the need for Cal kits.
But probably good enough for the low freq range of the vnwa based on what I remember of their analysis. And so could be usable for the 1.5GHz SVA. However, the load resistance they provide cant be used for a custom cal kit, but the offsets can.
How to crossflash a SSA3000X Plus into a SVA1032X:
1. Telnet into the equipment
2. rename
/usr/bin/siglent/ecomb_p
to
/usr/bin/siglent/ecomb
3. in file /usr/bin/siglent/startup_app.sh change the line
/usr/bin/siglent/ecomb_p &
to
/usr/bin/siglent/ecomb &
4. in file /usr/bin/siglent/config/NSP_config_upgrade_info.xml change the line
<upgrade_static_id>11405</upgrade_static_id>
to
<upgrade_static_id>11403</upgrade_static_id>
5. Reboot
6. Now you can update your SSA with the Siglent's SVA stock FW.
(should work with SVA1032X_2.2.1.2.5 or SVA1032X_2.2.1.2.7, at least)
7. After having flashed your first SVA stock FW, the SSA has become a "true" SVA.
To lower the risk you can do an additional step which is to activate the telned daemon before the line reference in step 3.
(for example, place there: /sbin/telnetd -l /bin/sh -p 10101 & )
As always: do it at your own risk.
SDR-kits.net in UK has excellent SMA calibration kits up to 12GHz for about $65 US. Each set (male and female) is individually calibrated and comes with full calibration specifications that should be able to be entered manually into the SVA1032XFrom a few days ago:
Jerry NY2KWThose are good parts, but they are not properly characterised.hendorog and I have checked a few Cal kits against the factory SVA calibration and unless you're characterizing DUT's at some detail the factory calibration is quite good enough .....but it's only to the port so adapters and cables do add some error. DTF could give you some ps delay measurements to add into Port extensions that might improve basic results without the need for Cal kits.
But probably good enough for the low freq range of the vnwa based on what I remember of their analysis. And so could be usable for the 1.5GHz SVA. However, the load resistance they provide cant be used for a custom cal kit, but the offsets can.
I have the Siglent 4.5 GHz SMA kit coming in a few weeks so hendorog and I will be running against several Cal kits he already has with Nano's, HP VNA and Signal Hound stuff he has.
Edit
Oh and how could I forget, also with a SVA1075X ! 8)
Sorry no, it has an NDA attached to it. ;)SDR-kits.net in UK has excellent SMA calibration kits up to 12GHz for about $65 US. Each set (male and female) is individually calibrated and comes with full calibration specifications that should be able to be entered manually into the SVA1032XFrom a few days ago:
Jerry NY2KWThose are good parts, but they are not properly characterised.hendorog and I have checked a few Cal kits against the factory SVA calibration and unless you're characterizing DUT's at some detail the factory calibration is quite good enough .....but it's only to the port so adapters and cables do add some error. DTF could give you some ps delay measurements to add into Port extensions that might improve basic results without the need for Cal kits.
But probably good enough for the low freq range of the vnwa based on what I remember of their analysis. And so could be usable for the 1.5GHz SVA. However, the load resistance they provide cant be used for a custom cal kit, but the offsets can.
I have the Siglent 4.5 GHz SMA kit coming in a few weeks so hendorog and I will be running against several Cal kits he already has with Nano's, HP VNA and Signal Hound stuff he has.
Edit
Oh and how could I forget, also with a SVA1075X ! 8)
Teardown? ^^ pcb pics? ^^
oh thats a nice find noreply.. i'll have to get one of those
and yeah more than likely... you just need a similar kit to at least give it basic cal data
When you become familiar with SVA's UI you might find the setting to reset to the factory cal so to check any discrepancies between another Cal kit. ;)oh thats a nice find noreply.. i'll have to get one of those
and yeah more than likely... you just need a similar kit to at least give it basic cal data
I guess we can always use the SSA part of the SVA to get some basic calibration of the VNA calibration kit's SMA connectors and associated cables ;)
We can always normalize the basic 'test' setup and then 'plug-in' the various Kit elements - and get a decent calibration - so any discrepancies in the connectors can be factored into the final calibration of the VNA :-+
This way we might as well use the US$1600 SSA we already have - to get some decent measurement and save some $$ rather than buy an expensive calibration kit :)
I bet after using SSA to calibrate the NanoVNA calibration kit's connectors - SVA VNA calibration will be close to the Siglent Kit's result :P
When you become familiar with SVA's UI you might find the setting to reset to the factory cal so to check any discrepancies between another Cal kit. ;)
Start exploring into 0.01dB/div and you'll find differences alright. ;)
When you become familiar with SVA's UI you might find the setting to reset to the factory cal so to check any discrepancies between another Cal kit. ;)
Start exploring into 0.01dB/div and you'll find differences alright. ;)
Sounds good - once I get my 'SSA' SVA up and running - looking forward in exploring the UI :)
@ 0.01db/div - just touching the connectors will definitely generate differences :P
I guess getting some connector torque wrenches will come in handy - if you are really serious about calibration.
How to crossflash a SSA3000X Plus into a SVA1032X:
1. Telnet into the equipment
2. rename
/usr/bin/siglent/ecomb_p
to
/usr/bin/siglent/ecomb
3. in file /usr/bin/siglent/startup_app.sh change the line
/usr/bin/siglent/ecomb_p &
to
/usr/bin/siglent/ecomb &
4. in file /usr/bin/siglent/config/NSP_config_upgrade_info.xml change the line
<upgrade_static_id>11405</upgrade_static_id>
to
<upgrade_static_id>11403</upgrade_static_id>
5. Reboot
6. Now you can update your SSA with the Siglent's SVA stock FW.
(should work with SVA1032X_2.2.1.2.5 or SVA1032X_2.2.1.2.7, at least)
7. After having flashed your first SVA stock FW, the SSA has become a "true" SVA.
To lower the risk you can do an additional step which is to activate the telned daemon before the line reference in step 3.
(for example, place there: /sbin/telnetd -l /bin/sh -p 10101 & )
As always: do it at your own risk.
tv84 - thanks for your great mentoring and guidence for newbees like me on this subject :clap:
I could not resist in 'closing the loop' with your crossflashing proof of concept - to reverse the process ;)
How to crossflash a SVA1032X into a SSA3000X Plus:
1. Telnet into the equipment
2. Rename
/usr/bin/siglent/ecomb
to
/usr/bin/siglent/ecomb_p
3. in file /usr/bin/siglent/startup_app.sh change the line
/usr/bin/siglent/ecomb &
to
/usr/bin/siglent/ecomb_p &
4. in file /usr/bin/siglent/config/NSP_config_upgrade_info.xml change the line
<upgrade_static_id>11403</upgrade_static_id>
to
<upgrade_static_id>11405</upgrade_static_id>
5. Reboot
6. Now you can update your SVA with the Siglent's SSA stock FW.
(should work with SSA3021/3032X Plus_V2.2.1.2.5 or SSA3021/3032X Plus_V2.2.1.2.7, at least)
7. After having flashed your first SSA stock FW, the SVA has become a "true" SSA.
8. If you already ‘own’ a SVA1032X – there may not be a good reason for crossflashing the FW for this device to turn into a SSA3021/3032X Plus.
It’s just proof of concept as proposed by tv84
To lower the risk you can do an additional step which is to activate the telned daemon before the line reference in step 3.
(for example, place there: /sbin/telnetd -l /bin/sh -p 10101 & )
As always: do it at your own risk.
tv84 - thanks for your great mentoring and guidence for newbees like me on this subject :clap:
I could not resist in 'closing the loop' with your crossflashing proof of concept - to reverse the process ;)
How to crossflash a SVA1032X into a SSA3000X Plus:
1. Telnet into the equipment2. Rename
/usr/bin/siglent/ecomb
to
/usr/bin/siglent/ecomb_p
3. in file /usr/bin/siglent/startup_app.sh change the line
/usr/bin/siglent/ecomb &
to
/usr/bin/siglent/ecomb_p &
4. in file /usr/bin/siglent/config/NSP_config_upgrade_info.xml change the line
<upgrade_static_id>11403</upgrade_static_id>
to
<upgrade_static_id>11405</upgrade_static_id>
5. Reboot
6. Now you can update your SVA with the Siglent's SSA stock FW.
(should work with SSA3021/3032X Plus_V2.2.1.2.5 or SSA3021/3032X Plus_V2.2.1.2.7, at least)
7. After having flashed your first SSA stock FW, the SVA has become a "true" SSA.
8. If you already ‘own’ a SVA1032X – there may not be a good reason for crossflashing the FW for this device to turn into a SSA3021/3032X Plus.
It’s just proof of concept as proposed by tv84
To lower the risk you can do an additional step which is to activate the telned daemon before the line reference in step 3.
(for example, place there: /sbin/telnetd -l /bin/sh -p 10101 & )
As always: do it at your own risk.
I found this chinese N type VNA calibration set for... 21 bucks, i'll have it in about a week.. go go primeHmmm, if you haven't got a factory cal like a legit SVA you might be better served with a SMA cal kit and N-SMA adaptors as mostly you use SMA cables anyways.
https://www.amazon.com/gp/product/B081J14316/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 (https://www.amazon.com/gp/product/B081J14316/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1)
tv84 - thanks for your great mentoring and guidence for newbees like me on this subject :clap:
I could not resist in 'closing the loop' with your crossflashing proof of concept - to reverse the process ;)
How to crossflash a SVA1032X into a SSA3000X Plus:
1. Telnet into the equipment2. Rename
/usr/bin/siglent/ecomb
to
/usr/bin/siglent/ecomb_p
3. in file /usr/bin/siglent/startup_app.sh change the line
/usr/bin/siglent/ecomb &
to
/usr/bin/siglent/ecomb_p &
4. in file /usr/bin/siglent/config/NSP_config_upgrade_info.xml change the line
<upgrade_static_id>11403</upgrade_static_id>
to
<upgrade_static_id>11405</upgrade_static_id>
5. Reboot
6. Now you can update your SVA with the Siglent's SSA stock FW.
(should work with SSA3021/3032X Plus_V2.2.1.2.5 or SSA3021/3032X Plus_V2.2.1.2.7, at least)
7. After having flashed your first SSA stock FW, the SVA has become a "true" SSA.
8. If you already ‘own’ a SVA1032X – there may not be a good reason for crossflashing the FW for this device to turn into a SSA3021/3032X Plus.
It’s just proof of concept as proposed by tv84
To lower the risk you can do an additional step which is to activate the telned daemon before the line reference in step 3.
(for example, place there: /sbin/telnetd -l /bin/sh -p 10101 & )
As always: do it at your own risk.
WARNING! THIS WILL NOT WORK! (If you do it, it will require bootloader access.)
To do what you have described, you MUST NOT execute your Steps 2 and 3. All the rest is OK.
So, in the extreme, a simple re-setting of the Product_ID in the NSP_config_upgrade_info.xml file allows for the reverse crossflashing.
And to show a hybrid SVA:
tv84 - thanks for your great mentoring and guidence for newbees like me on this subject :clap:
I could not resist in 'closing the loop' with your crossflashing proof of concept - to reverse the process ;)
How to crossflash a SVA1032X into a SSA3000X Plus:
1. Telnet into the equipment
2. Rename
/usr/bin/siglent/ecomb
to
/usr/bin/siglent/ecomb_p
3. in file /usr/bin/siglent/startup_app.sh change the line
/usr/bin/siglent/ecomb &
to
/usr/bin/siglent/ecomb_p &
4. in file /usr/bin/siglent/config/NSP_config_upgrade_info.xml change the line
<upgrade_static_id>11403</upgrade_static_id>
to
<upgrade_static_id>11405</upgrade_static_id>
5. Reboot
6. Now you can update your SVA with the Siglent's SSA stock FW.
(should work with SSA3021/3032X Plus_V2.2.1.2.5 or SSA3021/3032X Plus_V2.2.1.2.7, at least)
7. After having flashed your first SSA stock FW, the SVA has become a "true" SSA.
8. If you already ‘own’ a SVA1032X – there may not be a good reason for crossflashing the FW for this device to turn into a SSA3021/3032X Plus.
It’s just proof of concept as proposed by tv84
To lower the risk you can do an additional step which is to activate the telned daemon before the line reference in step 3.
(for example, place there: /sbin/telnetd -l /bin/sh -p 10101 & )
As always: do it at your own risk.
WARNING! THIS WILL NOT WORK! (If you do it, it will require bootloader access.)
To do what you have described, you MUST NOT execute your Steps 2 and 3. All the rest is OK.
So, in the extreme, a simple re-setting of the Product_ID in the NSP_config_upgrade_info.xml file allows for the reverse crossflashing.
OOPS!!!
Apologies to all following the crossflashing proof of concept in this thread.
tv84 noted such a concise step-by-step process after the successful and brave effort of Elasia and Techneut to do the crossflash from SSA to become a SVA, that I could not resist in simply reversing his process and posting as a tong-in-cheek.
Unfortunately, when you think about it (I clearly did not) it’s not a directly ‘flip-flop’ process!!! :palm:
The startup_app.sh for the SVA is different to the startup_app.sh for the SSA rendering the 'reversing' instructions DESTRUCTIVE if you do what was suggested by MY tong-in-cheek post
Despite the fact that you need to examine your thinking, if you ever decide to crossflash from an original SVA to become a SSA |O
PLEASE TAKE NOTE and DO NOT perform the ‘reverse’ procedure that I posted as a tong-in-cheek.
I found this chinese N type VNA calibration set for... 21 bucks, i'll have it in about a week.. go go primeHmmm, if you haven't got a factory cal like a legit SVA you might be better served with a SMA cal kit and N-SMA adaptors as mostly you use SMA cables anyways.
https://www.amazon.com/gp/product/B081J14316/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 (https://www.amazon.com/gp/product/B081J14316/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1)
That way, Cal can be performed near the port or close to the DUT at the end of cabling.
These might seem suitable:
https://www.amazon.com/Calibration-Dedicated-Include-Short-DC-3Ghz/dp/B07DGSF59F/ref=sr_1_9?dchild=1&keywords=SMA+calibration+kit&qid=1590914147&sr=8-9 (https://www.amazon.com/Calibration-Dedicated-Include-Short-DC-3Ghz/dp/B07DGSF59F/ref=sr_1_9?dchild=1&keywords=SMA+calibration+kit&qid=1590914147&sr=8-9)
But there are some cheaper ones here:
https://www.amazon.com/s?k=SMA+calibration+kit&ref=nb_sb_noss_2 (https://www.amazon.com/s?k=SMA+calibration+kit&ref=nb_sb_noss_2)
Don't feel too bad, your instructions would just confuse someone. Here is the startup_app.sh
startup_app.sh.txt
Don't feel too bad, your instructions would just confuse someone. Here is the startup_app.sh
startup_app.sh.txt
Yeah, but there is no excuse - you can't make stupid comments - even tong-in-cheek - because you are 100% correct about possible confusion!
I was so euphoric about the success you guys demonstrated - that basic instincts did not kick-in, like making sure the start-up files were identical - which they clearly are not - thereby cannot have symmetrical reverse process.
Just to top-off my carelessness - I just performed a crossflash on my SSA with SVA1032X_2.2.1.2.7.ADS - the process went fine, but still reporting in system info a SSA3032x PLUS device with original options (I never enabled hack in my original SSA).
The real salt-in-the-wound is that I should have realized that by changing the ID - my SSA telnet is no longer useful
I did take tv84 suggestion for the ‘safety’ /sbin/telnetd -ll /bin/sh -p 10101 & , but this only worked (could go straight into telnet after crossflash) on the initial boot after the FW update.
Unfortunately (carelessness again) I did not perform the mopping up housekeeping whilst having an open telnet session and decided to reboot - just to see if it comes back up without any problems.
It did, but I guess the original start-up we modified with the telnet start demon line is now gone, and since the ID is now set for the SVA my telnet_10101.ADS is not responding :palm:
Not a bad start to the day I guess :(
Don't feel too bad, your instructions would just confuse someone. Here is the startup_app.sh
startup_app.sh.txt
Yeah, but there is no excuse - you can't make stupid comments - even tong-in-cheek - because you are 100% correct about possible confusion!
I was so euphoric about the success you guys demonstrated - that basic instincts did not kick-in, like making sure the start-up files were identical - which they clearly are not - thereby cannot have symmetrical reverse process.
Just to top-off my carelessness - I just performed a crossflash on my SSA with SVA1032X_2.2.1.2.7.ADS - the process went fine, but still reporting in system info a SSA3032x PLUS device with original options (I never enabled hack in my original SSA).
The real salt-in-the-wound is that I should have realized that by changing the ID - my SSA telnet is no longer useful
I did take tv84 suggestion for the ‘safety’ /sbin/telnetd -ll /bin/sh -p 10101 & , but this only worked (could go straight into telnet after crossflash) on the initial boot after the FW update.
Unfortunately (carelessness again) I did not perform the mopping up housekeeping whilst having an open telnet session and decided to reboot - just to see if it comes back up without any problems.
It did, but I guess the original start-up we modified with the telnet start demon line is now gone, and since the ID is now set for the SVA my telnet_10101.ADS is not responding :palm:
Not a bad start to the day I guess :(
tv im sure will fix you up.. or if he really wanted to he could put out a special one that permanently turns it back on after a firmware update by adding the line to the startup scripts.. or adds it to the crossflasher :P
I think I need to take a break and get some fresh air - perhaps this will make me think before leap ;)
I took some screnshots, the systems info just after the crossflash of the SVA firmware - remember I had a 'stock' SSA3021x Plus - untouched!
Then I had a look at the mode screen - can see the SVA stuff grayed out - BUT silly me did not note if this is already present (also grayed out) in the stock SSA?? I think not - but cannot be sure :(
I think I need to take a break and get some fresh air - perhaps this will make me think before leap ;)
I took some screnshots, the systems info just after the crossflash of the SVA firmware - remember I had a 'stock' SSA3021x Plus - untouched!
Then I had a look at the mode screen - can see the SVA stuff grayed out - BUT silly me did not note if this is already present (also grayed out) in the stock SSA?? I think not - but cannot be sure :(
They dont show up at all unless you are running the SVA program, they are hard disabled in the SSA program
The real salt-in-the-wound is that I should have realized that by changing the ID - my SSA telnet is no longer useful
I did take tv84 suggestion for the ‘safety’ /sbin/telnetd -ll /bin/sh -p 10101 & , but this only worked (could go straight into telnet after crossflash) on the initial boot after the FW update.
Unfortunately (carelessness again) I did not perform the mopping up housekeeping whilst having an open telnet session and decided to reboot - just to see if it comes back up without any problems.
It did, but I guess the original start-up we modified with the telnet start demon line is now gone, and since the ID is now set for the SVA my telnet_10101.ADS is not responding :palm:
Not a bad start to the day I guess :(
I can confirm that. The last thing I did was changing the ID and after that the SSA telnet.ads didn't work anymore and the SVA telnet.ads also not. I changed the ID back and hope that er are some very smart people with a fix before the next firmware update. And there is always the UART.
|O |O
Gentlemen, test please.
And thanks to tv84 no longer a unidentified (flying) object
And to show a hybrid SVA:So what does the Mode list now look like ?
(https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/?action=dlattach;attach=998685)
Thank You to everyone involved in the last 48 hours of SSA to SVA FW crossflasing experimentation :clap:
Its amazing what you can learn in 48 hours :)
Special thanks to tv84 for his helping hand in helping us to 'get up' when we fall along the path (best analogy I could think of this late at night) :-+
Now its time to check out the fully loaded SVA to see if she lives up to her potential :popcorn:
Thank You to everyone involved in the last 48 hours of SSA to SVA FW crossflasing experimentation :clap:
Its amazing what you can learn in 48 hours :)
Special thanks to tv84 for his helping hand in helping us to 'get up' when we fall along the path (best analogy I could think of this late at night) :-+
Now its time to check out the fully loaded SVA to see if she lives up to her potential :popcorn:
Clearly more work to be done by tv84 and I.. pro mode has exposed more options on your main menu!
Also as far as your name hack... thats not the important one.. ;p It does still think of itself as an SSA at the kernel level, the true conversion will most likely take tv84/myself getting a hold of a copy of the SVA base software that we can dissect as what siglent posts truly are just patches.. not the entire OS
usbtmc_para = insmod /usr/bin/siglent/drivers/g_usbtmc.ko idVendor=0xf4ec idProduct=0x1305 iManufacturer=Siglent iProduct=SSA3032XPlus iSerialNum=SSABBBBBCCCDDD
Thank You to everyone involved in the last 48 hours of SSA to SVA FW crossflasing experimentation :clap:
Its amazing what you can learn in 48 hours :)
Special thanks to tv84 for his helping hand in helping us to 'get up' when we fall along the path (best analogy I could think of this late at night) :-+
Now its time to check out the fully loaded SVA to see if she lives up to her potential :popcorn:
Clearly more work to be done by tv84 and I.. pro mode has exposed more options on your main menu!
Also as far as your name hack... thats not the important one.. ;p It does still think of itself as an SSA at the kernel level, the true conversion will most likely take tv84/myself getting a hold of a copy of the SVA base software that we can dissect as what siglent posts truly are just patches.. not the entire OS
usbtmc_para = insmod /usr/bin/siglent/drivers/g_usbtmc.ko idVendor=0xf4ec idProduct=0x1305 iManufacturer=Siglent iProduct=SSA3032XPlus iSerialNum=SSABBBBBCCCDDD
Interesting :-\
Yeah, the name hack is nothing
- change in NSP_trends_config_info
- I think you are correct it simply modifies some internal tag but nothing in the base software, as there are other snags which revert to the SSA
The serial number is also a problem
- easy way is to use the SCPI :SRLN <serial_num> command.
- This works , but it will wipe your license settings.
Not sure if there is a proper license number 'fix' which does not screw with the system??
- not a fan of doing temp paches which are prone to failure
These two things are certainly challenging - short of patching hex files (not recommended) would be great to have a nice solution that does not get wiped with FW updates.
BTW
Has anyone got their WEB Server interface working??
Not sure what I'm doing wrong - but having problems in connecting :(
EDIT: Its OK - my network cable was loose - the plastic clip which secures the cable into the socket snapped-off and cable was loose.
Should have noticed this on the SVA screen - there is a blue symbol in top RH corner - indicating an active connection, was too busy trying to figure out what's wrong rather than checking cable or looking at screen - I guess too much fiddling for one day ;)
Thank You to everyone involved in the last 48 hours of SSA to SVA FW crossflasing experimentation :clap:
Its amazing what you can learn in 48 hours :)
Special thanks to tv84 for his helping hand in helping us to 'get up' when we fall along the path (best analogy I could think of this late at night) :-+
Now its time to check out the fully loaded SVA to see if she lives up to her potential :popcorn:
Clearly more work to be done by tv84 and I.. pro mode has exposed more options on your main menu!
Also as far as your name hack... thats not the important one.. ;p It does still think of itself as an SSA at the kernel level, the true conversion will most likely take tv84/myself getting a hold of a copy of the SVA base software that we can dissect as what siglent posts truly are just patches.. not the entire OS
usbtmc_para = insmod /usr/bin/siglent/drivers/g_usbtmc.ko idVendor=0xf4ec idProduct=0x1305 iManufacturer=Siglent iProduct=SSA3032XPlus iSerialNum=SSABBBBBCCCDDD
Interesting :-\
Yeah, the name hack is nothing
- change in NSP_trends_config_info
- I think you are correct it simply modifies some internal tag but nothing in the base software, as there are other snags which revert to the SSA
The serial number is also a problem
- easy way is to use the SCPI :SRLN <serial_num> command.
- This works , but it will wipe your license settings.
Not sure if there is a proper license number 'fix' which does not screw with the system??
- not a fan of doing temp paches which are prone to failure
These two things are certainly challenging - short of patching hex files (not recommended) would be great to have a nice solution that does not get wiped with FW updates.
There is ;)
Thanks for the tip with SCPI wiping out the license file... interesting option for something I am investigating now and it appears the license file low level itself is key to unlocking more features than just changing the program and typing the keys in
Have just completed my crossflash successfully, only extra step was to make the filesystem writable.
Do we know why some of the licenses disappear (particularly Refl) or is it not an issue?
Before:
(Attachment Link)
After:
(Attachment Link)
Shouldnt be an issue, from my investigations the program will use only the licenses that the hardware AND program can use
This stemming from that ALL can license everything but only adds into the license files the correct options for the given hardware and program executable
This is why you can see the real time options in pro mode for the VNA program even though the hardware cant handle that.. i did try and it put out bus errors that it could not contact the needed components.
But once you license the unit it will return only the ones it should have and the realtime options drop off completely.. not even being a disabled option
Have just completed my crossflash successfully, only extra step was to make the filesystem writable.
Do we know why some of the licenses disappear (particularly Refl) or is it not an issue?
Before:
(Attachment Link)
After:
(Attachment Link)
Any chance of 'seeing' your Mode options screenshot??
Am in the process of some detective work - and any information on this subject is very welcome :)
Yeah, when I first found this - I was very impressed at the level of work he did - even all the SimSmith stuff - excellent information, not to mention the fantastic insight into getting 'linear rf response' in SMD resistors - 2 x 100 in parallel better response than 1 x 50 - however does not scale beyond the 2 - very interesting stuff.
I guess once the SVA's VNA option is calibrated - we can then investigate how to 'home' the calibrations for the instrument to ensure the measurements we make ourselves thereafter are accurate
- not sure if the above statement made sense - I just wanted to use the 'bootstrap' effect - get going first - then use device to improve ;)
Shouldnt be an issue, from my investigations the program will use only the licenses that the hardware AND program can use
This stemming from that ALL can license everything but only adds into the license files the correct options for the given hardware and program executable
This is why you can see the real time options in pro mode for the VNA program even though the hardware cant handle that.. i did try and it put out bus errors that it could not contact the needed components.
But once you license the unit it will return only the ones it should have and the realtime options drop off completely.. not even being a disabled option
Ok, thank you :)
Of course I suppose that Refl from the SSA is now redundant as you have a VNA that supersedes it.
Have just completed my crossflash successfully, only extra step was to make the filesystem writable.
Do we know why some of the licenses disappear (particularly Refl) or is it not an issue?
Before:
(Attachment Link)
After:
(Attachment Link)
Shouldnt be an issue, from my investigations the program will use only the licenses that the hardware AND program can use
This stemming from that ALL can license everything but only adds into the license files the correct options for the given hardware and program executable
This is why you can see the real time options in pro mode for the VNA program even though the hardware cant handle that.. i did try and it put out bus errors that it could not contact the needed components.
But once you license the unit it will return only the ones it should have and the realtime options drop off completely.. not even being a disabled option
Can you confirm that 'EMI Measurement' is a valid license option for the SVA?It shows as an option to buy:
If it is, why is it then that it is no longer visible in the Mode Options menu?? (see screenshot from tubularnut)
(I suspect we might be indirectly involved at solving same problem ;) )
There are in fact TWO forms of EMICorrect.
One is a basic EMI that is limited to you having to use it in scanner mode over your given range
the other is REAL TIME EMI and is the 6th option in the mode list for a real time SA
That is what you are seeing
There are in fact TWO forms of EMI
One is a basic EMI that is limited to you having to use it in scanner mode over your given range
the other is REAL TIME EMI and is the 6th option in the mode list for a real time SA
That is what you are seeing
Of course I suppose that Refl from the SSA is now redundant as you have a VNA that supersedes it.More of less correct as SVA has the reflection bridge built in and offers better directivity than the external bridge from Siglent.
Of course I suppose that Refl from the SSA is now redundant as you have a VNA that supersedes it.More of less correct as SVA has the reflection bridge built in and offers better directivity than the external bridge from Siglent.
Still, it still might be useful with other bridges with more ports.
You can see this in screenshots here where I used SSA3032X and SVA1015X for N-Pk and Log Mag measurements:
https://www.eevblog.com/forum/rf-microwave/antenna-project-log/ (https://www.eevblog.com/forum/rf-microwave/antenna-project-log/)
There are in fact TWO forms of EMICorrect.
One is a basic EMI that is limited to you having to use it in scanner mode over your given range
the other is REAL TIME EMI and is the 6th option in the mode list for a real time SA
That is what you are seeing
It seems has been polished and added into the Mode menu for RTSA whereas for SSA and SVA it is a Trace Filter mode.
Latest RTSA have EMI in the Mode Menu with a different GUI layout.
For those interrested in EMi, myself included:
https://interferencetechnology.com/diy-near-field-probes-preamplifiers/ (https://interferencetechnology.com/diy-near-field-probes-preamplifiers/)
I ordered some semi rigid cable for this in China but I think its comming by long distance swimmer.
The good news is that the cost of a 250W 30dB 1GHz attenuator will cost me considerably less than $100
Anyway, any tips, unusual ways of using the SVA and its functions is always a welcome topic :)
For those interrested in EMi, myself included:I’m not entirely sure you need a preamp with EMI probes more so probes that have been properly characterised.
https://interferencetechnology.com/diy-near-field-probes-preamplifiers/
I ordered some semi rigid cable for this in China but I think its comming by long distance swimmer.
For those interrested in EMi, myself included:I’m not entirely sure you need a preamp with EMI probes more so probes that have been properly characterised.
https://interferencetechnology.com/diy-near-field-probes-preamplifiers/
I ordered some semi rigid cable for this in China but I think its comming by long distance swimmer.
The internal SSA/SVA 20dB preamp and the unit’s inherent sensitivity is sufficient to work well with a range of passive EMI probes.
More accurately, it's a coupler.
So what exactly is with the 'built in' reflection bridge?
Was the SSA just soft disabled to make someone get an external one?Early SSA didn't have the internal coupler and associated signal path however since it's been spotted SSA+ models do that's been the driver for the recent explorations.
AKA this part?
https://siglentna.com/product/rb3x25/ (https://siglentna.com/product/rb3x25/)
I was under the impression they all needed an external bridge till you brought this up
Edit: For clarity before I even opened the thing up physically, I was expecting a SSA that needed a bridge and this reminded me of that question since once opened there it was all interconnected already internally and was confusing when reading one thing and seeing another which in turn lead us down to cross flashWith an external bridge SSA could do much of SVA capabilities but not in the way or with the feature set of measurements that the SVA offers and was up to the knowledge and skill of the operator.
Have a wonder through this where I examine a few antennas on hand.The good news is that the cost of a 250W 30dB 1GHz attenuator will cost me considerably less than $100
Anyway, any tips, unusual ways of using the SVA and its functions is always a welcome topic :)
Both of those would be interesting :)
My assumption is feedlines are part of the antenna system so they should be included in VNA tests at the final installation and as the SVA models are so portable this is simple to accomplish.
Have fun, I certainly have while getting to know the couple of SVA's I've had. :)
I've got a few sets of these in for customers which I believe are fair value for the type 7 set:For those interrested in EMi, myself included:I’m not entirely sure you need a preamp with EMI probes more so probes that have been properly characterised.
https://interferencetechnology.com/diy-near-field-probes-preamplifiers/ (https://interferencetechnology.com/diy-near-field-probes-preamplifiers/)
I ordered some semi rigid cable for this in China but I think its comming by long distance swimmer.
The internal SSA/SVA 20dB preamp and the unit’s inherent sensitivity is sufficient to work well with a range of passive EMI probes.
I've got a few sets of these in for customers which I believe are fair value for the type 7 set:For those interrested in EMi, myself included:I’m not entirely sure you need a preamp with EMI probes more so probes that have been properly characterised.
https://interferencetechnology.com/diy-near-field-probes-preamplifiers/ (https://interferencetechnology.com/diy-near-field-probes-preamplifiers/)
I ordered some semi rigid cable for this in China but I think its comming by long distance swimmer.
The internal SSA/SVA 20dB preamp and the unit’s inherent sensitivity is sufficient to work well with a range of passive EMI probes.
https://www.aliexpress.com/item/33029566295.html?spm=a2g0s.9042311.0.0.76394c4dvHkz2M (https://www.aliexpress.com/item/33029566295.html?spm=a2g0s.9042311.0.0.76394c4dvHkz2M)
A dumb experiment ...Will do tomorrow.......oh hell....later today !
Just took a screen shot of an Open Port1 (TG Source) - nothing connected!
Would be interesting to see what others are getting with same Open Port - just to see 'how consistent Siglent SVA manufacturing really is :P
In theory - all should be identical - but most likely will not be depending on tolerances and calibration or lack of it.
Post you screenshot if you can ;)
Near field probes ?I've got a few sets of these in for customers which I believe are fair value for the type 7 set:For those interrested in EMi, myself included:I’m not entirely sure you need a preamp with EMI probes more so probes that have been properly characterised.
https://interferencetechnology.com/diy-near-field-probes-preamplifiers/ (https://interferencetechnology.com/diy-near-field-probes-preamplifiers/)
I ordered some semi rigid cable for this in China but I think its comming by long distance swimmer.
The internal SSA/SVA 20dB preamp and the unit’s inherent sensitivity is sufficient to work well with a range of passive EMI probes.
https://www.aliexpress.com/item/33029566295.html?spm=a2g0s.9042311.0.0.76394c4dvHkz2M (https://www.aliexpress.com/item/33029566295.html?spm=a2g0s.9042311.0.0.76394c4dvHkz2M)
Do you and hedgerog have a few different sets to compare with for that sva demo? I wonder how they would compare to tek's and more named branded ones
A dumb experiment ...Will do tomorrow.......oh hell....later today !
Just took a screen shot of an Open Port1 (TG Source) - nothing connected!
Would be interesting to see what others are getting with same Open Port - just to see 'how consistent Siglent SVA manufacturing really is :P
In theory - all should be identical - but most likely will not be depending on tolerances and calibration or lack of it.
Post you screenshot if you can ;)
Use R+JX as that's what you mostly use for antenna work.
Also you can crank up the measurement points to 751 IIRC for more detail at the expense of a bit slower sweep.
Oh and change the display screenshot to normal.
Only when using a wide sweep but nuthing objectionable. Data points are data points, even if they are all zeros. ;)A dumb experiment ...Will do tomorrow.......oh hell....later today !
Just took a screen shot of an Open Port1 (TG Source) - nothing connected!
Would be interesting to see what others are getting with same Open Port - just to see 'how consistent Siglent SVA manufacturing really is :P
In theory - all should be identical - but most likely will not be depending on tolerances and calibration or lack of it.
Post you screenshot if you can ;)
Use R+JX as that's what you mostly use for antenna work.
Also you can crank up the measurement points to 751 IIRC for more detail at the expense of a bit slower sweep.
Oh and change the display screenshot to normal.
Thanks for tip ...
Does not make much difference with 751 points - in terms of processing / sweep time - perhaaps it somehow knows its OPEN and nothing to process :P
BTW - is there an 'eject USB' option?? could not see anything & don't like pulling out USB if still mountedNope, no eject feature and a bit why I like drives with activity LED's.
QuoteBTW - is there an 'eject USB' option?? could not see anything & don't like pulling out USB if still mountedNope, no eject feature and a bit why I like drives with activity LED's.
Here is mine, some differences but similar
No crud.
The only time I get screens like yours is when I enter into calibration wizard ...
(Attachment Link)
And after applying calibration ...
(Attachment Link)
No crud.
The only time I get screens like yours is when I enter into calibration wizard ...
(Attachment Link)
And after applying calibration ...
(Attachment Link)
No crud.What do you see when you connect SHORT and OPEN calibration standards, after performing the calibration? DOTs or ARCs?
The only time I get screens like yours is when I enter into calibration wizard ...
(Attachment Link)
And after applying calibration ...
(Attachment Link)
BTW ...
Has anyone tried using a Wi-Fi dongle on USB - does this device support (existing driver in FW) any 5G dongles - or would we need to load our 'own' Linux driver to do this??
Also - anyone tried a mini USB hub - for simultaneous connection of Wi-Fi, Flash memory and wireless keyboard devices?
Sometimes the USB port / driver will not support multiple channels - just wondering if the SVA is one of these :(
No crud.What do you see when you connect SHORT and OPEN calibration standards, after performing the calibration? DOTs or ARCs?
The only time I get screens like yours is when I enter into calibration wizard ...
(Attachment Link)
And after applying calibration ...
(Attachment Link)
Why measuring the calibration standards on a VNA results in arcs, not dots on a Smith Chart as most people expect:
https://www.kirkbymicrowave.co.uk/Support/FAQ/Why-do-I-not-see-a-dot-on-the-Smith-Chart-for-the-opens-and-shorts/ (https://www.kirkbymicrowave.co.uk/Support/FAQ/Why-do-I-not-see-a-dot-on-the-Smith-Chart-for-the-opens-and-shorts/)
Maybe RF experts can jump in and shine some light about this issue. We should see ARCs or DOTs? I experimented with HP VNAs and having no money to buy the calibration standards, I tried to make a SOLT set, and manipulated the parameters that you enter into the VNA to get DOTs, but then I read about the ARCs posted by Kirkby... Then I got a decent N-connector SOLT kit and calibrated the VNA and I saw the ARCs, consistent with the report...No crud.What do you see when you connect SHORT and OPEN calibration standards, after performing the calibration? DOTs or ARCs?
The only time I get screens like yours is when I enter into calibration wizard ...
(Attachment Link)
And after applying calibration ...
(Attachment Link)
Why measuring the calibration standards on a VNA results in arcs, not dots on a Smith Chart as most people expect:
https://www.kirkbymicrowave.co.uk/Support/FAQ/Why-do-I-not-see-a-dot-on-the-Smith-Chart-for-the-opens-and-shorts/ (https://www.kirkbymicrowave.co.uk/Support/FAQ/Why-do-I-not-see-a-dot-on-the-Smith-Chart-for-the-opens-and-shorts/)
I see DOTS.
I have a sneaking suspicion that we are not done yet and do indeed need the SVA base firmware to full reflash with, this happens when trying to calibrate
[DEBUG] /home/share/qingyu.an/1032X/2.7/product_aladdin/drivers/hw_platform_access/zynq_common/zynq_ttc_pwm_driver.cpp Line:192 msg:::::::::::::::::::::::zynq_ttc_pwm_driver::start()
[DEBUG] /home/share/qingyu.an/1032X/2.7/product_aladdin/drivers/hw_platform_access/zynq_common/zynq_ttc_pwm_driver.cpp Line:208 msg:::::::::::::::::zynq_ttc_pwm_driver::stop()
[ 6060.503270] cdns-i2c e0004000.i2c: timeout waiting on completion
[ 6060.683256] cdns-i2c e0004000.i2c: timeout waiting on completion
I have a sneaking suspicion that we are not done yet and do indeed need the SVA base firmware to full reflash with, this happens when trying to calibrate
[DEBUG] /home/share/qingyu.an/1032X/2.7/product_aladdin/drivers/hw_platform_access/zynq_common/zynq_ttc_pwm_driver.cpp Line:192 msg:::::::::::::::::::::::zynq_ttc_pwm_driver::start()
[DEBUG] /home/share/qingyu.an/1032X/2.7/product_aladdin/drivers/hw_platform_access/zynq_common/zynq_ttc_pwm_driver.cpp Line:208 msg:::::::::::::::::zynq_ttc_pwm_driver::stop()
[ 6060.503270] cdns-i2c e0004000.i2c: timeout waiting on completion
[ 6060.683256] cdns-i2c e0004000.i2c: timeout waiting on completion
Where are you seeing this, I'll check mine.
Ah, I can't see that then :(
Ah, I can't see that then :(
I made a small header using 0.1 pin header and soldered some 22 awg directly to that, heat shrunk it and placed it under the metal cage itself so the cage keeps it pressed in then snaked the rest out the side to hang out by the bnc connectors
I'll be doing the same for my sds2k+.. because why not.. handy to have
Hmm, interesting.
At first I see DOTS after calibration on shorts and open.
Having saved my calibration to file, rebooting SVA, then reloading my saved file, I now see ARCS on short and open!
Maybe something is not being applied when it should be at calibration time? yes, I was hitting 'apply' at end of calibration.
(Attachment Link)
Could it be imply a bug?
I wouldnt be surprised due to unattended use and we are just shooting semi blind at it
I'll try the file method.. i didnt do that and just left it to do its thing and now it looks like it dumped the cal on reboot
Maybe RF experts can jump in and shine some light about this issue. We should see ARCs or DOTs? I experimented with HP VNAs and having no money to buy the calibration standards, I tried to make a SOLT set, and manipulated the parameters that you enter into the VNA to get DOTs, but then I read about the ARCs posted by Kirkby... Then I got a decent N-connector SOLT kit and calibrated the VNA and I saw the ARCs, consistent with the report...No crud.What do you see when you connect SHORT and OPEN calibration standards, after performing the calibration? DOTs or ARCs?
The only time I get screens like yours is when I enter into calibration wizard ...
(Attachment Link)
And after applying calibration ...
(Attachment Link)
Why measuring the calibration standards on a VNA results in arcs, not dots on a Smith Chart as most people expect:
https://www.kirkbymicrowave.co.uk/Support/FAQ/Why-do-I-not-see-a-dot-on-the-Smith-Chart-for-the-opens-and-shorts/ (https://www.kirkbymicrowave.co.uk/Support/FAQ/Why-do-I-not-see-a-dot-on-the-Smith-Chart-for-the-opens-and-shorts/)
I see DOTS.
So... DOTs or ARCs?
Real stock SVA1032X running FW .2.7 after Factory Reset. Open ports.
And yes Reset sets screenshot to Inverted and Points back to 201.
Remind us all what it started life as ? :popcorn:Real stock SVA1032X running FW .2.7 after Factory Reset. Open ports.
And yes Reset sets screenshot to Inverted and Points back to 201.
Just like mine :phew:
Remind us all what it started life as ? :popcorn:
Remind us all what it started life as ? :popcorn:
I've up/sidegraded mine from a SSA3021X Plus to an SVA1032X Plus too, and from all the other VNA and other test equipment I have, using the same calibration standard, they all line up so I know it's as accurate as my standards are.
They're from a cheap SMA calibration kit, so sure, they're not going to be perfect at 3.2GHz, but for 2.4GHz, which is where I use it most, it's good enough.
Thanks for all the information in this thread :)
Do you have a recommendation for a cheap but decent quality calibration kit?
I'm not sure you and others looking at this right.I've up/sidegraded mine from a SSA3021X Plus to an SVA1032X Plus too, and from all the other VNA and other test equipment I have, using the same calibration standard, they all line up so I know it's as accurate as my standards are.
They're from a cheap SMA calibration kit, so sure, they're not going to be perfect at 3.2GHz, but for 2.4GHz, which is where I use it most, it's good enough.
Thanks for all the information in this thread :)
Nice.. so what we have been seeing isnt crazy, once i figure out how to stuff factory cals with our own cals then that should get them working like the real SVA models and less wonky
I'm not sure you and others looking at this right.I've up/sidegraded mine from a SSA3021X Plus to an SVA1032X Plus too, and from all the other VNA and other test equipment I have, using the same calibration standard, they all line up so I know it's as accurate as my standards are.
They're from a cheap SMA calibration kit, so sure, they're not going to be perfect at 3.2GHz, but for 2.4GHz, which is where I use it most, it's good enough.
Thanks for all the information in this thread :)
Nice.. so what we have been seeing isnt crazy, once i figure out how to stuff factory cals with our own cals then that should get them working like the real SVA models and less wonky
With a VNA, you calibrate it before you use it. It's not a case of calibrate it once and leave it until next year when it's cal date comes up.
That's why you can get cal kits, because you need them as much as you need probes for a scope :).
Now sure, you can save the calibration and run off that, but you have to assume that nothing has drifted sufficiently to throw out your measurements, and calibration only takes a minute.
Remember, the ambient temperature, humidity and a ton of other factors can change a VNA measurement, and that wouldn't have been accounted for in a saved calibration.
This is what our screens should be looking like out of the box
https://www.eevblog.com/forum/testgear/siglent-sva1015x-1-5ghz-spectrum-vector-network-analyzer-(coming)/msg3086871/#msg3086871 (https://www.eevblog.com/forum/testgear/siglent-sva1015x-1-5ghz-spectrum-vector-network-analyzer-(coming)/msg3086871/#msg3086871)
My SSA/SVA looks completely different.
My SSA/SVA looks completely different.
Is there a control to dim the SVA1032x 'LCD display' (not the reticule display - which has a control)??
Trying to make some videos - but the screen is 'too bright' for my setup - would be nice to turn it down a little if possible :-\
My SSA/SVA looks completely different.
My SSA/SVA looks completely different.
Did you have something connected to TG aka Port 1?
My SSA/SVA looks completely different.
Did you have something connected to TG aka Port 1?
No both ports completly open. Also as I do a open or short cal it's very fast and I can't apply.
It looks like a hardware failure but I didn't think that I can send it for repair under waranty.
My SSA/SVA looks completely different.
Did you have something connected to TG aka Port 1?
No both ports completly open. Also as I do a open or short cal it's very fast and I can't apply.
It looks like a hardware failure but I didn't think that I can send it for repair under waranty.
My SSA/SVA looks completely different.
Did you have something connected to TG aka Port 1?
No both ports completly open. Also as I do a open or short cal it's very fast and I can't apply.
It looks like a hardware failure but I didn't think that I can send it for repair under waranty.
I opend the machine and guess what? It is realy a hardware fault.
I opend the machine and guess what? It is realy a hardware fault.
LOL WTF!
Did you pull that one off and forget to put it back on? :P Or did they really short you the cable?
I opend the machine and guess what? It is realy a hardware fault.
I opend the machine and guess what? It is realy a hardware fault.
Broken seal does not void warranty in the US. Actually it is illegal to put the "WARRANTY VOID IF REMOVED" stickerI opend the machine and guess what? It is realy a hardware fault.There might be some logic in the missing cable - Siglent has a default 'security device' (missing cable) as a prevention for SVA crossflashing - you will need to break 'seal' to fix the problem and hence void your warranty :P
Broken seal does not void warranty in the US. Actually it is illegal to put the "WARRANTY VOID IF REMOVED" stickerI opend the machine and guess what? It is realy a hardware fault.There might be some logic in the missing cable - Siglent has a default 'security device' (missing cable) as a prevention for SVA crossflashing - you will need to break 'seal' to fix the problem and hence void your warranty :P
It Federal https://www.bbc.com/news/technology-43724348#:~:text=Stickers%20on%20gadgets%20warning%20%22warranty,them%20about%20using%20misleading%20language. (https://www.bbc.com/news/technology-43724348#:~:text=Stickers%20on%20gadgets%20warning%20%22warranty,them%20about%20using%20misleading%20language.)Broken seal does not void warranty in the US. Actually it is illegal to put the "WARRANTY VOID IF REMOVED" stickerI opend the machine and guess what? It is realy a hardware fault.There might be some logic in the missing cable - Siglent has a default 'security device' (missing cable) as a prevention for SVA crossflashing - you will need to break 'seal' to fix the problem and hence void your warranty :P
That's interesting ...
Is this a Fedral law or State driven?
I guess it would be nice to check the UK legislation on 'warranty security stickers' - at least that's one hurdle gone from preventing you to 'take a look inside' ;)
Yeah thats why i pointed him at superbat, I'd bet if someone specd one of them if the need arises they would just repeat the order for anyone else
If it was just a matter of some falling off the back of a truck, i'd drive over to the NA HQ and beat on their door :P
Still though, anyone know what that blue tented semi rigid cable is?
I was in doubt if I should post it here or in the post for the SVA but sinds the calibration is still a hot topic for the upgraded SSA I decided for this forum. If I was wrong then please move or delete this post.
I came along this post:
https://www.instructables.com/id/23GHz-SMA-Calibration-Kit/ (https://www.instructables.com/id/23GHz-SMA-Calibration-Kit/)
I build it on a N-connector to see how good that was only to discover that the SVA showed a poor open. My ohmmeter confirmed 50 Ohms? After close up inspection I notisted that the pin was much tinner, probebly a 75 Ohm connector. :-X
I still think the site is good and I will try again when I have the right connectors.
Guess I didn't do something right with my mods, cause I don't have the serial number and I can see the options for the RTSA.
Still works though, so i'm not entirely too concerned :).
I came across something useful for myself – at least a ‘hands free’ way of investigating circuit behaviour :)
My question is if something similar can be implemented (if not already) that can be used for SSA’s
– especially when matched impedances are required
– not to mention much higher frequencies than typical with MSO’s
It’s possible to fabricate a suitable cable with an appropriate termination at the SSA end
Can we do same at the probe end?
I guess it’s a matter of simply trying to see what the frequency response will be – using the SSA itself ??
We can create two cables terminated at the TG and SSA input using suitable N terminations
– then simply ‘tune’ the 'probe end' and if not perfectly flat response for the entire 3.2G span
– normalize it before use :-\
This should work I guess for TG sweeps … but if just ‘probing’ with SSA input alone will we have any problems??
Has anyone attempted something similar?
Any feedback welcome ;)
I do also have that same set with 4 scope probes and 8 digital probes
very handy
sad they only go up to 100MHz ;(
I was in doubt if I should post it here or in the post for the SVA but sinds the calibration is still a hot topic for the upgraded SSA I decided for this forum. If I was wrong then please move or delete this post.
I came along this post:
https://www.instructables.com/id/23GHz-SMA-Calibration-Kit/ (https://www.instructables.com/id/23GHz-SMA-Calibration-Kit/)
I build it on a N-connector to see how good that was only to discover that the SVA showed a poor open. My ohmmeter confirmed 50 Ohms? After close up inspection I notisted that the pin was much tinner, probebly a 75 Ohm connector. :-X
I still think the site is good and I will try again when I have the right connectors.
Making your own calibration set is possible, but you need to keep high precision here.
In the case of the N connector there are greater distances and it should be remembered that the cable connected to the resistor must have an impedance of 50ohm (impedance not resistance). In principle, the resistor should also be non-inductive.
However, by using very short connections and a small resistor, this condition can be omitted (Can be made with small SMA connectors)...
Therefore, such a set will be easier to make using SMA connectors and using the SMA to N adapter.
I was in doubt if I should post it here or in the post for the SVA but sinds the calibration is still a hot topic for the upgraded SSA I decided for this forum. If I was wrong then please move or delete this post.
I came along this post:
https://www.instructables.com/id/23GHz-SMA-Calibration-Kit/ (https://www.instructables.com/id/23GHz-SMA-Calibration-Kit/)
I build it on a N-connector to see how good that was only to discover that the SVA showed a poor open. My ohmmeter confirmed 50 Ohms? After close up inspection I notisted that the pin was much tinner, probebly a 75 Ohm connector. :-X
I still think the site is good and I will try again when I have the right connectors.
Making your own calibration set is possible, but you need to keep high precision here.
In the case of the N connector there are greater distances and it should be remembered that the cable connected to the resistor must have an impedance of 50ohm (impedance not resistance). In principle, the resistor should also be non-inductive.
However, by using very short connections and a small resistor, this condition can be omitted (Can be made with small SMA connectors)...
Therefore, such a set will be easier to make using SMA connectors and using the SMA to N adapter.
I do also have that same set with 4 scope probes and 8 digital probes
very handy
sad they only go up to 100MHz ;(
P20B - NICE :-+
Any chance of getting the Sensepeek probe (100Mhz) and hooking it up to the SSA - to see how long it stays 'flat' for ??
- just curious if its labeled at 100Mhz but has some more milage :P
I do also have that same set with 4 scope probes and 8 digital probes
very handy
sad they only go up to 100MHz ;(
P20B - NICE :-+
Any chance of getting the Sensepeek probe (100Mhz) and hooking it up to the SSA - to see how long it stays 'flat' for ??
- just curious if its labeled at 100Mhz but has some more milage :P
Yeah i'll sweep it if i remember sometime next week.. gear is busy atm :P
Official as from Siglent? Looks good, it is like the box they deliver limited edition in.
Official as from Siglent? Looks good, it is like the box they deliver limited edition in.Yep, SVA1000X models accessory F603FE:
Pics of the official sma cal kit... spare no expenses! Look at that fine wood craftsmanship
Keep you eyes peeled on the SVA thread in a few weeks when my F603FE Cal kit arrives.Pics of the official sma cal kit... spare no expenses! Look at that fine wood craftsmanship
If you still have (or ever got) the NanoVNA's SMA calibration kit - would be nice to see a direct comparison to the 'official' Siglent kit ;)
My bet is that the NanoVNA's kit is not that far off the 'official' :P
But I can always be wrong :)
Or maybe I just wanted the box.... :-DD
Oh and you can be sure it'll get tested on all of hendorog's VNA's as well !
Or maybe I just wanted the box.... :-DD
Well I am exhibiting some signs of Jealousy for the 'box' already - you know the old saying ... good things come inside small boxes :P :P :P
... looking foward to tautech feedback soon ...
Keep you eyes peeled on the SVA thread in a few weeks when my F603FE Cal kit arrives.Pics of the official sma cal kit... spare no expenses! Look at that fine wood craftsmanship
If you still have (or ever got) the NanoVNA's SMA calibration kit - would be nice to see a direct comparison to the 'official' Siglent kit ;)
My bet is that the NanoVNA's kit is not that far off the 'official' :P
But I can always be wrong :)
I have a 7 GHz Kirkby SMA calibration 'correction' loaded into a fair dinkum SVA1032X and F603FE will be checked against it and another trip to see hendorog (my local VNA guru) might arise if he has any full Nano Cal kits left.
How to crossflash a SSA3000X Plus into a SVA1032X:
1. Telnet into the equipment
2. rename
/usr/bin/siglent/ecomb_p
to
/usr/bin/siglent/ecomb
3. in file /usr/bin/siglent/startup_app.sh change the line
/usr/bin/siglent/ecomb_p &
to
/usr/bin/siglent/ecomb &
4. in file /usr/bin/siglent/config/NSP_config_upgrade_info.xml change the line
<upgrade_static_id>11405</upgrade_static_id>
to
<upgrade_static_id>11403</upgrade_static_id>
5. Reboot
6. Now you can update your SSA with the Siglent's SVA stock FW.
(should work with SVA1032X_2.2.1.2.5 or SVA1032X_2.2.1.2.7, at least)
7. After having flashed your first SVA stock FW, the SSA has become a "true" SVA.
To lower the risk you can do an additional step which is to activate the telned daemon before the line reference in step 3.
(for example, place there: /sbin/telnetd -l /bin/sh -p 10101 & )
As always: do it at your own risk.
How is it possible to convert a Spectrum Analyzer into a Network Vector Analyzer by just reflashing the firmware?They are both spectrum analyzers first and foremost but SVA models have the VNA additional capability.
Is the hardware identical?
Is an NVA better than an SA in all categories?
Is there a good detailed description available about the differences in capabilities of both devices?
Is the hardware identical?
Is the hardware identical?
Yes...
SSA3021X Plus, SSA3032X Plus, SVA1032X this is the same hardware, only restrictions have been introduced using the firmware.
https://www.siglenteu.com/spectrum-analyzers/ssa3000x-plus/ (https://www.siglenteu.com/spectrum-analyzers/ssa3000x-plus/)
https://www.siglenteu.com/spectrum-analyzers/sva1000x-spectrum-vector-analyzer/ (https://www.siglenteu.com/spectrum-analyzers/sva1000x-spectrum-vector-analyzer/)
A physical difference spotted in the wild is the lacking of the extra sma cable to interconnect the boards for SVA use... thats rather trival to fix.. out of everyone that has done this i believe only one forum member ran into this so far
The term normalization noise floor is not a thing. :popcorn:
....................Normal ^^^ SA behavior over a full Span sweep !
Fortunately the SSA still has a sufficiently low noise floor
– if you are prepared to slow down the sweep time by a massive amount
..........................
yeah i got smoked, stuck at boot screen and also the prior system key trick doesnt workI came across a situation similar to yours after crossflashing a ssa3021x+ to sva... :palm: |O
I'll have to console it later and see what its doing now
I came across a situation similar to yours after crossflashing a ssa3021x+ to sva... :palm: |O
How can you recover the bricked device? :scared:
yeah i got smoked, stuck at boot screen and also the prior system key trick doesnt workI came across a situation similar to yours after crossflashing a ssa3021x+ to sva... :palm: |O
I'll have to console it later and see what its doing now
How can you recover the bricked device? :scared:
I came across a situation similar to yours after crossflashing a ssa3021x+ to sva... :palm: |O
How can you recover the bricked device? :scared:
What did you do?
Now, you have to open it and access the UART port and check its boot log to see where it stands.
yeah i got smoked, stuck at boot screen and also the prior system key trick doesnt workI came across a situation similar to yours after crossflashing a ssa3021x+ to sva... :palm: |O
I'll have to console it later and see what its doing now
How can you recover the bricked device? :scared:
You will need to open the back shell and expose the uart pins
Once direct connected to the console, login and look in your /usr/bin/siglent folder and see if you got both executables
Also do a df -k and see if all your drive space was consumed
If so then delete them and rerun the contents of the ads file manually
thats the jist of it
Correct me if I’m wrong (I think I am wrong in my interpretation)
– but all of the ‘internal attenuation’ settings in the SSA are automatically taken into account when the SSA displays the resultant ‘dBm’ value at the marker for a given frequency??
Is this correct??
First problem for me
– SSA displays gain as dBm
– the attenuation outside the SSA is 50dB
– that’s reducing the signal by 100,000 times
– is it correct to still interpret this as 50 dBm
– I guess the answer is YES
– since the dB part is correct
– but we are looking at ‘power’ so the ‘m’ ??
I've surmised its possible to make a boot stick with whats around but never went into that, tv84 might be able to help and see if you can at least get a kernel loaded and reflash your backup in, assuming you have backup images
Hopefully this has not confused things even more for you.
Regards.
I've surmised its possible to make a boot stick with whats around but never went into that, tv84 might be able to help and see if you can at least get a kernel loaded and reflash your backup in, assuming you have backup images
>My advice would be to do it interactively on the uboot prompt.I've surmised its possible to make a boot stick with whats around but never went into that, tv84 might be able to help and see if you can at least get a kernel loaded and reflash your backup in, assuming you have backup images
My advice would be to do it interactively on the uboot prompt.
Nonetheless, I'm available to unpack and pack a package to reflash the necessary NAND part.
BUT, i won't be able to help in creating/testing the necessary scripts because that requires a good knowledge of the update scripts and a machine to do the hands-on experimentation.
I've surmised its possible to make a boot stick with whats around but never went into that, tv84 might be able to help and see if you can at least get a kernel loaded and reflash your backup in, assuming you have backup images
backup images... sadly, no. |O
So, the contents of MTD1 (kernel) is the uImage file that Elasia shared.
You go in uboot and flash that file in the MTD1 address.
That will solve the Kernel problem. Then send the boot log to see how it ends.
Here (https://cld.pt/dl/download/a7001e0c-aef3-445d-97a8-ad61cac3c231/SSA%2BSVA.zip?download=true) are 2 ZIPs with the stock firmwares of both SVA and SSA (latest versions). I unpacked the .ADS files for you.Everything works like a charm. Big thumb up to you! :-+
Below is the NAND map of the SSA X+:
(Attachment Link)
Study the stuff.
(Maybe you can ask someone to send you their NAND dump and you flash the necessary MTDs.)
Yes, it boots normally after flashing MTD1. :-+So, the contents of MTD1 (kernel) is the uImage file that Elasia shared.
You go in uboot and flash that file in the MTD1 address.
That will solve the Kernel problem. Then send the boot log to see how it ends.
I suspect that will take care of it.. as the fact that its corrupt should mean he either stopped it or it crashed mid flash of that partition and the others should be ok
Then if his program partition is full that can be easily fixed up with some basic clean up like i had to do
Everything works like a charm. Big thumb up to you! :-+
Certainly :clap: :popcorn:Everything works like a charm. Big thumb up to you! :-+
You owe us a beer! :popcorn:
Now, go slowly and do the crossflash as required. ;)
I think you don't have a reliable setup. You didn't follow the instructions correctly or else you wouldn't be in such troubles.
In order to verify that all is correct, try to upgrade the equipment with the latest stock SVA firmware.
I did reflash the mtd7 from uboot but the files was still missing. I found these files are also missing in my backup mtd7 image. Don't ask me why. ??? :palm: Indeed, I only backup (not nanddump) the whole filesystem from telnet before trying my first attempt of FW update.
To fix the problem, I had to fix my backup mtd7 image. The simplest solution was to ask you all to share with me an untouched mtd7 image and reflash it. I didn't do so simply because I wanna fix it by myself first.
Does post #963 still work with the latest shipping SSA3021X Plus?Yes, works like a charm. :-+
Does post #963 still work with the latest shipping SSA3021X Plus?Yes, works like a charm. :-+
P.S. My SSA was shipped directly from SZ. I received it by the end of June.
Going to System -> System Info I now says it's a SSA3032XPlus ! (Not an SVA!)
durec, empty your inbox!
When I hooked up up the GPSDO - it got a 'GSP lock' within 60 seconds - great!
I don't know what version of GPSDO you bought :)
But "catching a gps fix" doesn't mean having a stable frequency. In such systems, GPS stabilizes the work of OCXO, while OCXO requires a longer warm-up for stable operation. 60 seconds is definitely not enough and the system has not stabilized for sure.
In such systems, phase noise at the output also plays an important role - but as I said, the quality of such a system depends on the design.
The best systems are based on Trimble Thunderbolt and Chinese ham BG7TLB. Both are sufficient for amateurs.
Personally, with the Trimble Thunderbolt + rubidium generator (also bought used in China) I have all the equipment synchronized (frequency meter, oscilloscope, SSA etc.)
Follow up on cross flash
There is no such thing as coincidence.
So there has been a change in hardware/assembly
Follow up on cross flash
There is no such thing as coincidence.
So there has been a change in hardware/assembly
How to crossflash a SSA3000X Plus into a SVA1032X:
1. Telnet into the equipment
2. rename
/usr/bin/siglent/ecomb_p
to
/usr/bin/siglent/ecomb
3. in file /usr/bin/siglent/startup_app.sh change the line
/usr/bin/siglent/ecomb_p &
to
/usr/bin/siglent/ecomb &
4. in file /usr/bin/siglent/config/NSP_config_upgrade_info.xml change the line
<upgrade_static_id>11405</upgrade_static_id>
to
<upgrade_static_id>11403</upgrade_static_id>
5. Reboot
6. Now you can update your SSA with the Siglent's SVA stock FW.
(should work with SVA1032X_2.2.1.2.5 or SVA1032X_2.2.1.2.7, at least)
7. After having flashed your first SVA stock FW, the SSA has become a "true" SVA.
To lower the risk you can do an additional step which is to activate the telned daemon before the line reference in step 3.
(for example, place there: /sbin/telnetd -l /bin/sh -p 10101 & )
As always: do it at your own risk. (if you don't feel comfortable with linux commands ask somebody else to help)
EDIT Jun 27th:
ATTENTION: You MUST do a "sync" command before rebooting to flush any pending file operation.
SSA
New Functionality:
• Update EMI option to a new EMI measurement mode
Improvements:
• Improve TG output harmonic performance
• Update Help file
Solved Issues:
• Fix ADC overload warning
• Fix Ch Power calculation bug in small span
Post cross flash firmware update using SVA .7 firmware to stock SVA .8 firmware file confirmed working, have at it
SVAA new SSAX Plus/SVA and SSAX-R User manual version E02A with chapter 7 for this new EMI mode on P134.
New Functionality:
• Update EMI option to a new EMI measurement mode
SSA
New Functionality:
• Update EMI option to a new EMI measurement mode
Crossflashing to SVA1032X final step
For all those that want to get an official "SVA1032X" designation after having crossflashed their SSA3000X+, the only thing that you need to do is replace the firmdata0/NSP_trends_config_info.xml file with the attached one.
Reboot and voilá.
PS: This is a stock NSP_trends_config_info.xml taken from an "original" SVA1032X.
If you want to take it further from here, to have the correct Serial number, you'll also need a way to generate the correct license info for your specific device's Serial + Host ID.
This can be done with some help from the forum, but the procedure is not public yet. ;)
If one needed to restore their equipment from a NAND dump, how would that occur? Is that done via JTAG interface?
Found out one can use FTP client to transfer screenshots and measument data from the instrument. Is there also a way to enable write access to the internal storage to create folders and rename files?
Does the cross flashing to SVA1032X work on the SSA3015X plus?I guess you mean SVA1015X.
No, I mean SSA3015X plus. It was announced recently.Does the cross flashing to SVA1032X work on the SSA3015X plus?I guess you mean SVA1015X.
SVA1032X has a different LF VNA spec that suggests the HW is different. Check the datasheets.
Oh wow....No, I mean SSA3015X plus. It was announced recently.Does the cross flashing to SVA1032X work on the SSA3015X plus?I guess you mean SVA1015X.
SVA1032X has a different LF VNA spec that suggests the HW is different. Check the datasheets.
https://siglentna.com/news-article/siglent-ssa3000x-r-plus-spectrum-analyzer-family-welcomes-new-models-new-functions/ (https://siglentna.com/news-article/siglent-ssa3000x-r-plus-spectrum-analyzer-family-welcomes-new-models-new-functions/)
Does the cross flashing to SVA1032X work on the SSA3015X plus?
Does the cross flashing to SVA1032X work on the SSA3015X plus?
Looking at the datasheet and knowing about the SVA1015X and SVA1032X differences, maybe this new SSA3015X Plus can only be crossflashed to SVA1015X.
I can see RT40 activated... does it work on this crossflashed SVA1032X?Crossflashing to SVA1032X final step
For all those that want to get an official "SVA1032X" designation after having crossflashed their SSA3000X+, the only thing that you need to do is replace the firmdata0/NSP_trends_config_info.xml file with the attached one.
Reboot and voilá.
PS: This is a stock NSP_trends_config_info.xml taken from an "original" SVA1032X.
Hi tv84, thanks for the awesome work on this SSA/SVA crossflash!
* However, I suspect your attachment is wrong, it seems to be an .sh file (with the dumpnand script) instead of the NSP_trends_config_info.xml
* Also, I have crossflashed my device (to the latest 2.2.1.2.8), but still have XXXXXXXXXXXXXX as serial number / SN.
What's the way to do this right, while retaining all licenses as "Permanent" ?
Screenshot of my current system info is attached.
I can see RT40 activated... does it work on this crossflashed SVA1032X?
HELP PLEASE :((((( I JUST BRIKED MY SSA3021X-PLUS :(((( I follow the 1223 post and now my siglent does not boot up the TG and MODE are light but that is all.PLEASE HELP.
HELP PLEASE :((((( I JUST BRIKED MY SSA3021X-PLUS :(((( I follow the 1223 post and now my siglent does not boot up the TG and MODE are light but that is all.PLEASE HELP.
Do you know what step bricked it?
Take a deep breath and wait for @Elasia.
Are you sure you have your serial port well connected and configured? Verify all once again.
Take a deep breath and wait for @Elasia.
Are you sure you have your serial port well connected and configured? Verify all once again.
I've tryied with 2 computers , 2 terminals all native serials.Puty and hercules show the the same ==it :( do not know :(
What do you mean with native serial? RS232? Doesn't the UART in-out pins work at 3.3V levels?
What do you mean with native serial? RS232? Doesn't the UART in-out pins work at 3.3V levels?
Ok , so I put GND ,RX, TX DIRECTRLY TO RS232 INTO A computer , I was wrong ?
Not all computers work, my own main machine garbled it completely actually so that does happen
1. Check your pinouts and post pics of your pinouts to both sides labeled
2. Check 115200 8N1 is set
3. Sanity check your terminal uart does indeed actually work
4. Use a different computer if uart works but still cant read the device
If you have a scope that can decode uart, attach it to the lines, you can confirm that it is indeed actually putting out correct data
Doing all of this should lead you to finding the issue
Good to see you rescued your SSA. nice work :clap:Not all computers work, my own main machine garbled it completely actually so that does happen
1. Check your pinouts and post pics of your pinouts to both sides labeled
2. Check 115200 8N1 is set
3. Sanity check your terminal uart does indeed actually work
4. Use a different computer if uart works but still cant read the device
If you have a scope that can decode uart, attach it to the lines, you can confirm that it is indeed actually putting out correct data
Doing all of this should lead you to finding the issue
I manage to make him alive ! the problem was the interface : so I put a ttl to translate from SSA to computer.And now I will start again with the update. Thank you all my friends. you are so smart, thank you.
Good news iulisan, glad you've got your SSA3021X Plus working again and upgraded too :-+
I'm not especially gifted in all this, but have successfully upgraded my SDS2120X Plus (this went well) and more recently the SDG2042X (some difficultly since I am using a MAC) with the help of folks here. Now considering the SSA3021X Plus, which seems at another level of difficulty.
Is it possible to upgrade the SSA3021X Plus without having to go thru all the issues you've encountered, especially having to get inside the instrument and use the UART?
Best,
I took the plunge and tried the cross to the SVA1032 from a new SSA3021X Plus following the details from #963. Long story short is the Model Number changed to SSA3021X Plus, but only SA and MA are highlighted under Mode, VNA and DTF are not highlighted. Under SA use the top frequency range is still 2.1GHz. Still only the TG is Permanent.
System Info
SW1 2.2.1.2.5
SW2 20191022-5
SW3 000000D4
HW 00.00.00
The SSA has SW version 2.2.1.2.3r1 initially and after a failed attempt at the cross I updated the SSA FM to 2.2.1.2.5
Any suggestions on what to try and help is appreciated.
Best
I took the plunge and tried the cross to the SVA1032 from a new SSA3021X Plus following the details from #963. Long story short is the Model Number changed to SSA3021X Plus, but only SA and MA are highlighted under Mode, VNA and DTF are not highlighted. Under SA use the top frequency range is still 2.1GHz. Still only the TG is Permanent.
System Info
SW1 2.2.1.2.5
SW2 20191022-5
SW3 000000D4
HW 00.00.00
The SSA has SW version 2.2.1.2.3r1 initially and after a failed attempt at the cross I updated the SSA FM to 2.2.1.2.5
Any suggestions on what to try and help is appreciated.
Best
Follow this updated process that someone compiled from our various back and forth
https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3180754/#msg3180754 (https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3180754/#msg3180754)
The SSA has SW version 2.2.1.2.3r1 initially
As your SA was originally delivered withQuoteThe SSA has SW version 2.2.1.2.3r1 initially
Once you have it up and running your HW may be missing the connection between the tracking generator and the input. So if your VNA results shows abnormal graphs and it cannot be calibrated you will have to open up your box and insert a short SMA jumper(approx 5 cm/2 inch needed with 90o connectors
Eric
Good news, looks like the SSA3021X Plus has been transformed into the SVA1032X :phew:I'm not so sure.
It appears the SMA cable is installed also
Good news, looks like the SSA3021X Plus has been transformed into the SVA1032X :phew:I think the trace you are seeing is the result of the missing cable
It appears the SMA cable is installed also :)
Thanks to to Elasia, tv84 and Emo for all the help :clap:
Best,
Good news, looks like the SSA3021X Plus has been transformed into the SVA1032X :phew:I'm not so sure.
It appears the SMA cable is installed also
Best as I can see mawyatt's settings and after a Preset to clear mine here's what a real SVA1032X looks like in the same Smith chart mode. FW = latest dot 8 version.
(https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/?action=dlattach;attach=1058570)
Maybe rig up a 50 ohm resistor on a cable and LF sweep it in Smith R+jX mode and see if it returns a result near the center of the display. :popcorn:
Data point for you, much the same setup as yours but with N-BNC adapter and BNC to croc clips cable with 47 ohm resistor.Good news, looks like the SSA3021X Plus has been transformed into the SVA1032X :phew:I'm not so sure.
It appears the SMA cable is installed also
Best as I can see mawyatt's settings and after a Preset to clear mine here's what a real SVA1032X looks like in the same Smith chart mode. FW = latest dot 8 version.
(https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/?action=dlattach;attach=1058570)
Maybe rig up a 50 ohm resistor on a cable and LF sweep it in Smith R+jX mode and see if it returns a result near the center of the display. :popcorn:
I am waiting to order a cal kit (see if this conversion actually worked), and made up a simple test cable as you suggested. Used a 47 Ohm on a banana adapter to a BNC to the N to BNC cable I have (I'm waiting on other cables and adpaters that I've ordered). The trace didn't move to the center of the Smith Chart for a sweep of 100K to 10MHz as it should, so evidently I do not have the interior cable installed :o
Looks as if I'll have get a cable, or make one up.
Best,
Good news, looks like the SSA3021X Plus has been transformed into the SVA1032X :phew:I think the trace you are seeing is the result of the missing cable
It appears the SMA cable is installed also :)
Thanks to to Elasia, tv84 and Emo for all the help :clap:
Best,
I dissembled the unit and these are images of the inside. The "missing cable" is present :phew:Yep, should do.
For a test I used a simple leaded 1/8 Watt 47 ohm resistor on a Banana to BNC adapter (between the screw terminals), hanging on the end of a N to BNC 700mm cable. Two plots, one from 100K to 3.2GHz (Full span), the other from 100K to 100MHz.
Maybe a proper cal will make this look better?
Best,
Yep, should do.
Member hendorog has my Cal kit for comparisons against his HPAK ones on his HPAK legacy VNA so no, not had a session with it yet. He's also cross checking results against his SSA3075X-R which has SVA functionality.Yep, should do.
Did you finish the experiments comparing the NanoVNA (1 and 2) cal kits and the official Siglent one? It seems that the latest firmware lets you export and import calibration data, maybe there is a way to get real calibration data into the "improved" SSA.
Maybe a proper cal will make this look better?
Best,
Here is a suggestion for Siglent FW developers ...
The Keysighr MXA signal analyser has a 'phase noise' function - see attached screen shot
Would this be possible to do with the SSA3000x range?
There is enough ability in the SSA to get the raw data - so it just needs to be processed and displayed in the same domain as the Keysight MXA
Or am I missing something here - where the SSA simply does not have the HW to perform such a plot?
Its a very interesting feature to have - especially if its just a bit of code in the end without any HW enhancements.
Just Saying ...
FYI, the Phase measurement feature is available standard in SVA models.
(https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/?action=dlattach;attach=1061430)
Here is a suggestion for Siglent FW developers ...
The Keysighr MXA signal analyser has a 'phase noise' function - see attached screen shot
Would this be possible to do with the SSA3000x range?
There is enough ability in the SSA to get the raw data - so it just needs to be processed and displayed in the same domain as the Keysight MXA
Or am I missing something here - where the SSA simply does not have the HW to perform such a plot?
Its a very interesting feature to have - especially if its just a bit of code in the end without any HW enhancements.
Just Saying ...
SSA3000X own phase noise is not so nice for direct PN measurements
20 °C to 30 °C fc=1 GHz
<-95 dBc/Hz @10 kHz offset
<-96 dBc/Hz @100 kHz offset
<-115 dBc/Hz @1 MHz offset
MSA X performance is in tis own class and have lot of better own phase noise (but not true excellent)
Noise sidebands
(20 to 30 °C, CF = 1 GHz)
10 Hz –80 dBc/Hz, nominal
100 Hz –91 dBc/Hz
1 kHz –112 dBc/Hz, nominal
10 kHz –113 dBc/Hz
100 kHz –116 dBc/Hz
1 MHz –135 dBc/Hz
10 MHz –148 dBc/Hz, nominal
Data point for you, much the same setup as yours but with N-BNC adapter and BNC to croc clips cable with 47 ohm resistor.Good news, looks like the SSA3021X Plus has been transformed into the SVA1032X :phew:I'm not so sure.
It appears the SMA cable is installed also
Best as I can see mawyatt's settings and after a Preset to clear mine here's what a real SVA1032X looks like in the same Smith chart mode. FW = latest dot 8 version.
(https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/?action=dlattach;attach=1058570)
Maybe rig up a 50 ohm resistor on a cable and LF sweep it in Smith R+jX mode and see if it returns a result near the center of the display. :popcorn:
I am waiting to order a cal kit (see if this conversion actually worked), and made up a simple test cable as you suggested. Used a 47 Ohm on a banana adapter to a BNC to the N to BNC cable I have (I'm waiting on other cables and adpaters that I've ordered). The trace didn't move to the center of the Smith Chart for a sweep of 100K to 10MHz as it should, so evidently I do not have the interior cable installed :o
Looks as if I'll have get a cable, or make one up.
Best,
(https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/?action=dlattach;attach=1058644)
As we are talking about files, while the menu and copying can be survived, the lack of export to touchstone (s2p) files is a pain.
Yes - this has been requested already, hopefully it will come soon. I'm sure it helps if more people request it.
They keep an eye out for suggestions here and in a few threads however there are a few of us that pass stuff to them too, dealers and beta testers etc.Yes - this has been requested already, hopefully it will come soon. I'm sure it helps if more people request it.
Is there an official Siglent idea/feature request tracker where I can place my vote on this, or does someone pass this along to Siglent?
I don't know if it was already posted here, but found it by accident ;)Nice find. :)
I wonder what the differences in the firmware (some old firmware versions: T3SA3000_1.2.9.3a.ADS & T3VNA1500_2.2.1.2.7.ADS)LeCroy display branding. :-//
LeCroy display branding. :-//
LeCroy display branding. :-//
I think he can paint LeCroy with a felt-tip pen :-DD
and interesting things - documentation on how to program with NI-VISA (Visual C++, LabView, Matlab)
http://cdn.teledynelecroy.com/files/manuals/t3vna-programming-manual.pdf (http://cdn.teledynelecroy.com/files/manuals/t3vna-programming-manual.pdf)
Further to this tautech and I have had a chat, and these are the ideas we have bounced around:
1.
As mentioned - on the device itself, implement a Copy All/Export All function to bulk copy Local files to the USB drive in one step.
1a.
Improve the file management function in general. The copy paste mechanism is functional, but clunky.
A simple improvement would be to remove the need to switch between Dir and File mode when pasting.
2.
Run an FTP and/or a Samba server on the device to provide a way to remote access files on the local and USB filesystems.
3.
Implement a web based file browser which is accessible via the built in Siglent Instrument Control web page.
4.
(Bonus feature, this is a bit novel)
On the filesystem provide a set of 'virtual files' which allow access to the device data and screenshots without having to save the files on the device.
e.g.
to take a screenshot, just open the screenshot.png virtual file on the PC (via FTP or using the web browser). The act of opening the file will take the screenshot and then save the data on the PC as normal.
to download a CSV file of the current sweep open the sweep.csv file on the PC. The data is returned at the end of the sweep.
etc etc for all of the different file types.
Hi-
Does the Real Time Spectrum Analyzer (RTSA) work with your crossflashed SSA+?
--
Olivier
Little update, FTP access is already functional by default however file access is PW protected but improved SSA/SVA Local file access from PC has been accepted as a feature request to be added in the near future.Further to this tautech and I have had a chat, and these are the ideas we have bounced around:
1.
As mentioned - on the device itself, implement a Copy All/Export All function to bulk copy Local files to the USB drive in one step.
1a.
Improve the file management function in general. The copy paste mechanism is functional, but clunky.
A simple improvement would be to remove the need to switch between Dir and File mode when pasting.
2.
Run an FTP and/or a Samba server on the device to provide a way to remote access files on the local and USB filesystems.
3.
Implement a web based file browser which is accessible via the built in Siglent Instrument Control web page.
4.
(Bonus feature, this is a bit novel)
On the filesystem provide a set of 'virtual files' which allow access to the device data and screenshots without having to save the files on the device.
e.g.
to take a screenshot, just open the screenshot.png virtual file on the PC (via FTP or using the web browser). The act of opening the file will take the screenshot and then save the data on the PC as normal.
to download a CSV file of the current sweep open the sweep.csv file on the PC. The data is returned at the end of the sweep.
etc etc for all of the different file types.
I swapped out telnet for ssh and just use winscp on this and my scope.. my suggestion would be they do the same.. i'd be surprised if they did though.. i think the best you will get is some kinda file management os additions to the gui and some further additions to the webgui to download the files
We have a SSA3021X Plus "enabled" to 3.2GHz and "expanded" to SVA1032X following the procedures and help from folks on here.Mike, when you have no luck entering the settings you require sometimes it's best to clear all previous settings with a press of Preset and return everything to factory defaults.
System Info shows SVA1032X. SW1 is 2.2.1.2.8, SW2 is 20200616-1, SW3 is 000000D4 and HW is 00.00.00
Question on the TG "Normalize" button not active (greyed out) when the TG is on. The TG works fine but I can't activate the Normalize function. Same goes for the Ref Trace not being active, all the other TG related bottons are active, just Normalize and Ref Trace are greyed out and inactive.
I've followed the procedure in 2.2.7.4 in the manual. Any help is greatly appreciated.
Best,
the Normalise procedure has changed in the Plus and SVA models where now you must set a reference trace first.Why is this?? ???
Did someone had already a look into the SSA3032X-R?
Would be interesting if the -R is only some additional parts / modules or only other Software??
Does somebody know if its save tu upgrade the firmware of a "promode" SSA3021X Plus -> SVA1032X with the newest firmware?
SVA1032X Firmware - V3.2.2.3.2 (Release Date 09.18.20 ) ?
Would be nice because :
Functionality:
•Adduser definedVNAcalibration kits
•Add VNA 0 span calibration
Would be nice to use a not official calkit..?
more pics
ln -s -f -r /etc/init.d/telnetd /etc/rc0.d/K10telnetd
ln -s -f -r /etc/init.d/telnetd /etc/rc1.d/K10telnetd
ln -s -f -r /etc/init.d/telnetd /etc/rc5.d/S10telnetd
ln -s -f -r /etc/init.d/telnetd /etc/rc6.d/K10telnetd
With the help of betatester @Bicurico here is the WORKING script that enables telnet on the SSA3000X. #STOP_THE_BRICKSOh good. DL4RAJ has a problem with his however as I don't have a recovery package for these older analysers you 2 may have saved his bacon. :phew:
The port is 10101 as always.
A special thanks to Bicurico who has tested it successfully. :clap:
With the help of betatester @Bicurico here is the WORKING script that enables telnet on the SSA3000X. #STOP_THE_BRICKS
The port is 10101 as always.
A special thanks to Bicurico who has tested it successfully. :clap:
Would I be correct in assuming that this replaces the earlier version (telnet_SSA3000X.zip dated 2020-06-07) from the list of telnet session *.ADS files associated with the "How to open a telnet session in a Siglent when the root password is unknown" which I'd downloaded back in August?
Dear all
I am about to order SSA300X with the clear goal in mind >:D… and I am asking myself if the SSA3015X plus is suitable (same HW platform?) for cross flashing, or SSA3021X (Plus) minimum platform/model is required to become an SVA3032X?
Reading Choosing "hobbyist grade" spectrum analyzer - Page 1 (eevblog.com) I am not being any smarter.
Best regards, and vy 73, Joe
Rumors tell that if user do some "semirandom but careful mistakes" it can some times happen the machine's perception of itself changes... :-/O
BTW ...
Has anyone tried using a Wi-Fi dongle on USB - does this device support (existing driver in FW) any 5G dongles - or would we need to load our 'own' Linux driver to do this??
Also - anyone tried a mini USB hub - for simultaneous connection of Wi-Fi, Flash memory and wireless keyboard devices?
Sometimes the USB port / driver will not support multiple channels - just wondering if the SVA is one of these :(
Rumors tell that if user do some "semirandom but careful mistakes" it can some times happen the machine's perception of itself changes... :-/O
:-DD I'll have to open a thread with this title: Semirandom but careful mistakes
What are the login credentials for the serial port, or VNC?
Did someone had already a look into the SSA3032X-R?
This is likely, if you watch Dave's teardown you can see the PCB areas that might be populated for the -R version. I would think that a higher speed (maybe resolution) ADC than the 12 Bit 40MSPS ADC would need be employed, and the additional components would be for a high performance anti-aliasing LPF.
Maybe someone with the -R version could do a teardown ::)
Best,
So I have found and interesting problem, when I use VI to make these changes;
update.sh starting ...
current version:
upgrade_app: starting
rm: can't remove '/usr/bin/siglent/libscpi*': No such file or directory
cp: write error: No space left on device
cp: can't preserve times of '/usr/bin/siglent/startup_app.sh': No space left on device
cp: can't preserve ownership of '/usr/bin/siglent/startup_app.sh': No space left on device
cp: can't preserve permissions of '/usr/bin/siglent/startup_app.sh': No space left on device
-rpf /usr/bin/siglent/usr/usr/upgrade/app/startup_app.sh /usr/bin/siglent/
cp -rpf /usr/bin/siglent/usr/usr/upgrade/app/ /usr/bin/siglent/usr/backup/
cp: write error: No space left on device
cp: can't preserve times of '/usr/bin/siglent/drivers/insmod_before_app.sh': No space left on device
cp: can't preserve ownership of '/usr/bin/siglent/drivers/insmod_before_app.sh': No space left on device
cp: can't preserve permissions of '/usr/bin/siglent/drivers/insmod_before_app.sh': No space left on device
cp: write error: No space left on device
cp: can't preserve times of '/usr/bin/siglent/drivers/uinput.ko': No space left on device
cp: can't preserve ownership of '/usr/bin/siglent/drivers/uinput.ko': No space left on device
cp: can't preserve permissions of '/usr/bin/siglent/drivers/uinput.ko': No space left on device
cp -rpf /usr/bin/siglent/usr/usr/upgrade/drivers/* /usr/bin/siglent/drivers/
cp -rpf /usr/bin/siglent/usr/usr/upgrade/fpga/* /usr/bin/siglent/config/fpga/
cp -rpf /usr/bin/siglent/usr/usr/upgrade/www/* /usr/bin/siglent/config/www/
upgrade_app: there is no *.dtb to upgrade
upgrade_app: ending
rm: can't remove '/usr/bin/siglent/config/log/log4qt.conf': No such file or directory
upgrade_add: upgrade /usr/bin/siglent/usr/usr/upgrade/add/log4cpp.properties(I have full telnet and UART logs from the entire time I was attempting the cross-flash, so I can post much more detail if that helps.)Always do a FULL BACKUP of your equipment before crossflashing!
Script to make a NAND dump + RAM dump + firmdata0 backup on a SSA3000X+ is attached. (Tested OK.)
Use a pendisk >= 1 GBytes. It can take up to 20 minutes.
Edit: Now it should reboot after backup is complete.
Well, I did see no mtd12 either...
If you run the "dmesg" command you should obtain all that info.
Looking at dmesg output you can easily verify the individual mtd sizes.
Regarding the latest FW versions:
I haven't looked at it but I think there is no major problem. People just have to see if there is any need for the app rename or not (1st step).
The theory behind the method is pretty well explained so anyone with some linux knowledge can extrapolate any new step.
One thing is strongly advised: you should only crossflash with the same FW version. If not, there is an unnecessary higher risk in the operation.
...
crossflashed with SVA1032X_V3.2.2.3.2.ADS
and (stays) bricked with Siglent logo on the display (TG and Mode button illuminated).
BR Joe
Tomorrow I will open it to connect to console (have to look for the pin description In the forum)
You have the same problem as gussy!
(...)
Excuse me guys i know probably you told a lot of time but i’m a little bit confused, if i’ll buy a SSA3021XPLUS the exact and best procedure is first to port it into SSA3032XPLUS or is it enought to follow the procedure to crossflash it into SVA? I’d like to have all option on and keep the serial number, thanks
It's safe.
(I haven't completed the step to enable all options with serial # turning into all Xs).
Hi -
I have a SSA3021X Plus with the latest V3.2.2.3.3R1 firmware, and followed post #1223 (except step 2/3 since it's no longer required per a later post), and was able to flash the factory SVA 1032X V3.2.2.3.3R1 firmware.
However, after the upgrade, I have TG menu disabled (and TG not even showing a permanently enabled option under info like before the flash), I also don't see disabled VNA option under "Mode".
I then updated "NSP_trends_config_info.xml" as per instruction, and have since got TG option back. However, I'm still capped at 2.1G, but it's my understanding that it should now have been expanded to 3.2G, what am I doing wrong?
(I haven't completed the step to enable all options with serial # turning into all Xs).
Thanks!
Hi -
I have a SSA3021X Plus with the latest V3.2.2.3.3R1 firmware, and followed post #1223 (except step 2/3 since it's no longer required per a later post), and was able to flash the factory SVA 1032X V3.2.2.3.3R1 firmware.
However, after the upgrade, I have TG menu disabled (and TG not even showing a permanently enabled option under info like before the flash), I also don't see disabled VNA option under "Mode".
I then updated "NSP_trends_config_info.xml" as per instruction, and have since got TG option back. However, I'm still capped at 2.1G, but it's my understanding that it should now have been expanded to 3.2G, what am I doing wrong?
(I haven't completed the step to enable all options with serial # turning into all Xs).
Thanks!
Hi -
I have a SSA3021X Plus with the latest V3.2.2.3.3R1 firmware, and followed post #1223 (except step 2/3 since it's no longer required per a later post), and was able to flash the factory SVA 1032X V3.2.2.3.3R1 firmware.
However, after the upgrade, I have TG menu disabled (and TG not even showing a permanently enabled option under info like before the flash), I also don't see disabled VNA option under "Mode".
I then updated "NSP_trends_config_info.xml" as per instruction, and have since got TG option back. However, I'm still capped at 2.1G, but it's my understanding that it should now have been expanded to 3.2G, what am I doing wrong?
(I haven't completed the step to enable all options with serial # turning into all Xs).
Thanks!
How did you get to FW V3.2.2.3.3R1?
How did you handle the renaming of ecomb_p to ecomp and changing the call of it inside "startup_app.sh"?
For the newest FW the name of the application changed from ecomp to Aladdin, thus an application like ecomp should not exist for FW V3.2.2.3.3R1.
--> See post 1368 from tv84!
(I haven't completed the step to enable all options with serial # turning into all Xs).
From memory, you need to unlock the options to get the bandwidth and VNA enabled.
Hi -
I have a SSA3021X Plus with the latest V3.2.2.3.3R1 firmware, and followed post #1223 (except step 2/3 since it's no longer required per a later post), and was able to flash the factory SVA 1032X V3.2.2.3.3R1 firmware.
However, after the upgrade, I have TG menu disabled (and TG not even showing a permanently enabled option under info like before the flash), I also don't see disabled VNA option under "Mode".
I then updated "NSP_trends_config_info.xml" as per instruction, and have since got TG option back. However, I'm still capped at 2.1G, but it's my understanding that it should now have been expanded to 3.2G, what am I doing wrong?
(I haven't completed the step to enable all options with serial # turning into all Xs).
Thanks!
3.2 GHz is one of the options, so you have to unlock them to get it.
tv84 - could there be hope for glimpse into the realtime versions internals? It seems there is no teardowns up anywhere I have managed to look.
Also, for me, the VNA is not really interesting. It's not four port, the smith chart is so-so (no values) and from what I've read, only 201 points.201 is the default setting applied with a factory Preset however max VNA points are 751.
U-Boot 2014.07-svn118162 (Sep 03 2020 - 12:37:11)
Board: Xilinx Zynq
I2C: ready
DRAM: ECC disabled 128 MiB
NAND: 256 MiB
MMC: zynq_sdhci: 0
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
int board_late_init(void)+++++
buzzer_off---------------
buzzer_on---------------
buzzer_off---------------
int board_late_init(void)-----
Net: Gem.e000b000
Hit any key to stop autoboot: 1 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
USB1: ULPI request timed out
zynq ULPI viewport init failed
lowlevel init failed
scanning usb for storage devices... 1 Storage Device(s) found
Copying Linux from USB to RAM...
reading boot_uImage
** Unable to read file boot_uImage **
reading sva1000x_udiskEnv.txt
** Unable to read file sva1000x_udiskEnv.txt **
Copying Linux from NAND flash to RAM...
NAND read: device 0 offset 0x780000, size 0x400000
4194304 bytes read: OK
NAND read: device 0 offset 0xb80000, size 0x80000
524288 bytes read: OK
## Booting kernel from Legacy Image at 02080000 ...
Image Name: Linux-3.19.2-omg-xilinx-svn35686
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3121840 Bytes = 3 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 02000000
Booting using the fdt blob at 0x2000000
EHCI failed to shut down host controller.
Loading Kernel Image ... OK
Loading Device Tree to 06d0d000, end 06d13db2 ... OK
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.19.2-omg-xilinx-svn35686 (ding@ding-T5810) (gcc version 4.6.1 (Sourcery CodeBench Lite 2011.09-50) ) #11 SMP PREEMPT Fri Jan 4 15:28:26 CST 2019
[ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine model: Zynq Zed Development Board
[ 0.000000] cma: Reserved 16 MiB at 0x09000000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] PERCPU: Embedded 9 pages/cpu @48e92000 s8128 r8192 d20544 u36864
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 40640
[ 0.000000] Kernel command line: console=ttyPS0,115200 root=/dev/mtdblock5 rootfstype=cramfs init=/linuxrc earlyprintk uboot_version=3
[ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Memory: 139704K/163840K available (3835K kernel code, 213K rwdata, 1580K rodata, 196K init, 216K bss, 7752K reserved, 16384K cma-reserved, 0K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0x4a800000 - 0xff000000 (2888 MB)
[ 0.000000] lowmem : 0x40000000 - 0x4a000000 ( 160 MB)
[ 0.000000] pkmap : 0x3fe00000 - 0x40000000 ( 2 MB)
[ 0.000000] modules : 0x3f000000 - 0x3fe00000 ( 14 MB)
[ 0.000000] .text : 0x40008000 - 0x40552200 (5417 kB)
[ 0.000000] .init : 0x40553000 - 0x40584000 ( 196 kB)
[ 0.000000] .data : 0x40584000 - 0x405b96a0 ( 214 kB)
[ 0.000000] .bss : 0x405b96a0 - 0x405ef914 ( 217 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
[ 0.000000] L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
[ 0.000000] L2C-310 erratum 769419 enabled
[ 0.000000] L2C-310 enabling early BRESP for Cortex-A9
[ 0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[ 0.000000] L2C-310 ID prefetch enabled, offset 1 lines
[ 0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[ 0.000000] L2C-310 cache controller enabled, 8 ways, 512 kB
[ 0.000000] L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
[ 0.000000] slcr mapped to 4a804000
[ 0.000000] zynq_clock_init: clkc starts at 4a804100
[ 0.000000] Zynq clock init
[ 0.000010] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns
[ 0.000128] timer #0 at 4a806000, irq=17
[ 0.000477] Console: colour dummy device 80x30
[ 0.000495] Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096)
[ 0.090270] pid_max: default: 32768 minimum: 301
[ 0.090420] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.090436] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.091059] CPU: Testing write buffer coherency: ok
[ 0.091253] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.091320] Setting up static identity map for 0x39c880 - 0x39c8d8
[ 0.240257] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.240333] Brought up 2 CPUs
[ 0.240353] SMP: Total of 2 processors activated (2664.03 BogoMIPS).
[ 0.240361] CPU: All CPU(s) started in SVC mode.
[ 0.240863] devtmpfs: initialized
[ 0.241585] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 0.247260] NET: Registered protocol family 16
[ 0.249163] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.271077] cpuidle: using governor ladder
[ 0.301042] cpuidle: using governor menu
[ 0.309216] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[ 0.309232] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 0.309362] zynq-ocm f800c000.ocmc: ZYNQ OCM pool: 256 KiB @ 0x4a880000
[ 0.319988] vgaarb: loaded
[ 0.320392] SCSI subsystem initialized
[ 0.320773] usbcore: registered new interface driver usbfs
[ 0.320860] usbcore: registered new interface driver hub
[ 0.321047] usbcore: registered new device driver usb
[ 0.321200] phy0 supply vcc not found, using dummy regulator
[ 0.321295] phy1 supply vcc not found, using dummy regulator
[ 0.321414] --------------usb_udc_init ------
[ 0.321658] pps_core: LinuxPPS API ver. 1 registered
[ 0.321670] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.321728] PTP clock support registered
[ 0.321874] EDAC MC: Ver: 3.0.0
[ 0.323408] Switched to clocksource arm_global_timer
[ 0.335318] NET: Registered protocol family 2
[ 0.336059] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.336110] TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.336168] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.336212] TCP: reno registered
[ 0.336228] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.336258] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.336455] NET: Registered protocol family 1
[ 0.336768] RPC: Registered named UNIX socket transport module.
[ 0.336781] RPC: Registered udp transport module.
[ 0.336790] RPC: Registered tcp transport module.
[ 0.336798] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.337166] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[ 0.338495] futex hash table entries: 512 (order: 3, 32768 bytes)
[ 0.340105] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 0.341126] io scheduler noop registered
[ 0.341146] io scheduler deadline registered
[ 0.341197] io scheduler cfq registered (default)
[ 0.343216] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
[ 0.343236] dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[ 0.343754] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 145, base_baud = 2500000) is a xuartps
[ 0.917282] console [ttyPS0] enabled
[ 0.921432] xdevcfg f8007000.devcfg: ioremap 0xf8007000 to 4a878000
[ 0.928171] [drm] Initialized drm 1.1.0 20060810
[ 0.940640] brd: module loaded
[ 0.947608] loop: module loaded
[ 0.956769] libphy: MACB_mii_bus: probed
[ 1.033526] macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 149 (00:0a:35:00:01:23)
[ 1.043428] macb e000b000.ethernet eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:1e, irq=-1)
[ 1.054940] i2c /dev entries driver
[ 1.060164] rtc-ds1307 0-0068: rtc core: registered ds1340 as rtc0
[ 1.066614] cdns-i2c e0004000.i2c: 400 kHz mmio e0004000 irq 143
[ 1.073887] zynq-edac f8006000.memory-controller: ecc not enabled
[ 1.080100] Xilinx Zynq CpuIdle Driver started
[ 1.085189] ledtrig-cpu: registered to indicate activity on CPUs
[ 1.092190] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[ 1.098503] nand: Micron MT29F2G08ABAEAWP
[ 1.102482] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 1.110076] nand: WARNING: pl353-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
[ 1.121581] Bad block table found at page 131008, version 0x01
[ 1.127857] Bad block table found at page 130944, version 0x01
[ 1.133986] 12 ofpart partitions found on MTD device pl353-nand
[ 1.139837] Creating 12 MTD partitions on "pl353-nand":
[ 1.145093] 0x000000000000-0x000000780000 : "fsbl"
[ 1.150912] 0x000000780000-0x000000b80000 : "kerneldata"
[ 1.157160] 0x000000b80000-0x000000c00000 : "device-tree"
[ 1.163529] 0x000000c00000-0x000001100000 : "Manufacturedata"
[ 1.170216] 0x000001100000-0x000001600000 : "reserved1"
[ 1.176418] 0x000001600000-0x000003e00000 : "rootfs"
[ 1.182297] 0x000003e00000-0x000004800000 : "firmdata0"
[ 1.188441] 0x000004800000-0x000006c00000 : "siglent"
[ 1.194472] 0x000006c00000-0x00000d000000 : "datafs"
[ 1.200494] 0x00000d000000-0x00000da00000 : "log"
[ 1.206168] 0x00000da00000-0x00000f800000 : "upgrade_cramdisk"
[ 1.212968] 0x00000f800000-0x000010000000 : "reserved2"
[ 1.221035] TCP: cubic registered
[ 1.224522] NET: Registered protocol family 17
[ 1.229141] Registering SWP/SWPB emulation handler
[ 1.235795] rtc-ds1307 0-0068: setting system clock to 2021-01-07 16:25:40 UTC (1610036740)
[ 1.249172] cramfs_fill_nand blocks is 320-----------------------
[ 1.249172]
[ 1.249172]
[ 1.249172]
[ 1.262187] VFS: Mounted root (cramfs filesystem) readonly on device 31:5.
[ 1.269090] devtmpfs: mounted
[ 1.272232] Freeing unused kernel memory: 196K (40553000 - 40584000)
Starting rcS...
[ 1.544516] UBI-1: ubi_attach_mtd_dev:attaching mtd7 to ubi1
[ 1.692213] UBI-1: scan_all:scanning is finished
[ 1.703199] UBI-1 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 3, need 40
[ 1.714340] UBI-1: ubi_attach_mtd_dev:attached mtd7 (name "siglent", size 36 MiB)
[ 1.721757] UBI-1: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 1.730414] UBI-1: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 1.738913] UBI-1: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[ 1.747611] UBI-1: ubi_attach_mtd_dev:good PEBs: 288, bad PEBs: 0, corrupted PEBs: 0
[ 1.755362] UBI-1: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[ 1.764317] UBI-1: ubi_attach_mtd_dev:max/mean erase counter: 14/2, WL threshold: 4096, image sequence number: 1331120951
[ 1.775276] UBI-1: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 288, PEBs reserved for bad PEB handling: 3
[ 1.786165] UBI-1: ubi_thread:background thread "ubi_bgt1d" started, PID 582
[ 1.788517] UBI-2: ubi_attach_mtd_dev:attaching mtd6 to ubi2
[ 1.832666] UBI-2: scan_all:scanning is finished
[ 1.843444] UBI-2 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 9, need 40
[ 1.854474] UBI-2: ubi_attach_mtd_dev:attached mtd6 (name "firmdata0", size 10 MiB)
[ 1.862071] UBI-2: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 1.870712] UBI-2: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 1.879222] UBI-2: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[ 1.887920] UBI-2: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[ 1.895576] UBI-2: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[ 1.904538] UBI-2: ubi_attach_mtd_dev:max/mean erase counter: 25/13, WL threshold: 4096, image sequence number: 2009223325
[ 1.915604] UBI-2: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 80, PEBs reserved for bad PEB handling: 9
[ 1.926390] UBI-2: ubi_thread:background thread "ubi_bgt2d" started, PID 586
[ 1.928526] UBI-3: ubi_attach_mtd_dev:attaching mtd9 to ubi3
[ 1.972834] UBI-3: scan_all:scanning is finished
[ 1.983606] UBI-3 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 9, need 40
[ 1.994595] UBI-3: ubi_attach_mtd_dev:attached mtd9 (name "log", size 10 MiB)
[ 2.001662] UBI-3: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 2.010298] UBI-3: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 2.018813] UBI-3: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[ 2.027512] UBI-3: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[ 2.035193] UBI-3: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[ 2.044187] UBI-3: ubi_attach_mtd_dev:max/mean erase counter: 6/3, WL threshold: 4096, image sequence number: 1866265482
[ 2.055009] UBI-3: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 80, PEBs reserved for bad PEB handling: 9
[ 2.065807] UBI-3: ubi_thread:background thread "ubi_bgt3d" started, PID 590
[ 2.074476] UBI-0: ubi_attach_mtd_dev:attaching mtd8 to ubi0
[ 2.474095] UBI-0: scan_all:scanning is finished
[ 2.486319] UBI-0: ubi_attach_mtd_dev:attached mtd8 (name "datafs", size 100 MiB)
[ 2.493781] UBI-0: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 2.502346] UBI-0: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 2.510890] UBI-0: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[ 2.519586] UBI-0: ubi_attach_mtd_dev:good PEBs: 800, bad PEBs: 0, corrupted PEBs: 0
[ 2.527340] UBI-0: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[ 2.536293] UBI-0: ubi_attach_mtd_dev:max/mean erase counter: 6/3, WL threshold: 4096, image sequence number: 626955013
[ 2.547079] UBI-0: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 800, PEBs reserved for bad PEB handling: 40
[ 2.558055] UBI-0: ubi_thread:background thread "ubi_bgt0d" started, PID 594
[ 2.571547] UBIFS: background thread "ubifs_bgt1_0" started, PID 597
[ 2.603045] UBIFS: recovery needed
[ 2.701549] UBIFS: recovery completed
[ 2.705247] UBIFS: mounted UBI device 1, volume 0, name "siglent"
[ 2.711268] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 2.720423] UBIFS: FS size: 34410496 bytes (32 MiB, 271 LEBs), journal size 4952064 bytes (4 MiB, 39 LEBs)
[ 2.730074] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 2.735121] UBIFS: media format: w4/r0 (latest is w4/r0), UUID F1827086-F8DE-48BE-B9C2-AF1F551BC6EE, small LPT model
[ 2.780797] UBIFS: recovery needed
[ 2.821225] UBIFS: recovery deferred
[ 2.824822] UBIFS: mounted UBI device 2, volume 0, name "firm0", R/O mode
[ 2.831546] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 2.840702] UBIFS: FS size: 7237632 bytes (6 MiB, 57 LEBs), journal size 1650688 bytes (1 MiB, 13 LEBs)
[ 2.850088] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 2.855136] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 68D1D634-0B41-44C3-8EE7-5B148BE8F0D7, small LPT model
[ 2.868520] UBIFS: background thread "ubifs_bgt3_0" started, PID 600
[ 2.899988] UBIFS: recovery needed
[ 2.922587] UBIFS: recovery completed
[ 2.926264] UBIFS: mounted UBI device 3, volume 0, name "log"
[ 2.931944] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 2.941097] UBIFS: FS size: 7237632 bytes (6 MiB, 57 LEBs), journal size 1650688 bytes (1 MiB, 13 LEBs)
[ 2.950484] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 2.955535] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 35E3C92F-68EC-461E-A46E-9F549FBFB3F1, small LPT model
[ 2.969176] UBIFS: background thread "ubifs_bgt0_0" started, PID 602
[ 3.000723] UBIFS: recovery needed
[ 3.091182] UBIFS: recovery completed
[ 3.094874] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[ 3.100811] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 3.109966] UBIFS: FS size: 94597120 bytes (90 MiB, 745 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[ 3.119613] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 3.124663] UBIFS: media format: w4/r0 (latest is w4/r0), UUID AB78C81C-0D18-4506-91AE-D6D46AF0DBD0, small LPT model
rm: can't remove '/usr/bin/siglent/usr/mass_storage/U-disk*': No such file or directory
rm: can't remove '/usr/bin/siglent/usr/tmp/*_U-disk*': No such file or directory
[ 5.556271] Unhandled fault: external abort on non-linefetch (0x818) at 0x36f0a380
Bus error
[ 5.583000] irq = 170
[ 5.595039] <<-GTP-INFO->> GTP driver installing...
[ 5.600037] <<-GTP-INFO->> GTP Driver Version: V2.4<2014/11/28>
[ 5.605918] <<-GTP-INFO->> GTP Driver Built@22:06:06, Apr 27 2018
[ 5.611975] <<-GTP-INFO->> GTP I2C Address: 0x14
[ 5.616624] 0-0014 supply vdd_ana not found, using dummy regulator
[ 5.622834] 0-0014 supply vcc_i2c not found, using dummy regulator
[ 5.629063] <<-GTP-INFO->> Guitar reset
[ 5.753919] <<-GTP-INFO->> IC Version: 928_1060
[ 5.764591] <<-GTP-INFO->> X_MAX: 1024, Y_MAX: 600, TRIGGER: 0x00
[ 5.783429] <<-GTP-INFO->> create proc entry gt9xx_config success
[ 5.789709] input: goodix-ts as /devices/virtual/input/input0
[ 5.795699] <<-GTP-INFO->> GTP works in interrupt mode.
[ 5.811437] gpib_usb_init
[ 5.814208] usbcore: registered new interface driver usb-gpib
[ 5.909323] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 5.920626] ehci-pci: EHCI PCI platform driver
[ 5.949646] e0002000.usb supply vbus not found, using dummy regulator
[ 5.956418] ci_hdrc ci_hdrc.0: EHCI Host Controller
[ 5.961252] ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1
[ 5.983503] ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00
[ 5.988988] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 5.995786] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 6.002941] usb usb1: Product: EHCI Host Controller
[ 6.007830] usb usb1: Manufacturer: Linux 3.19.2-omg-xilinx-svn35686 ehci_hcd
[ 6.014983] usb usb1: SerialNumber: ci_hdrc.0
[ 6.019965] hub 1-0:1.0: USB hub found
[ 6.023721] hub 1-0:1.0: 1 port detected
[ 6.028201] e0003000.usb supply vbus not found, using dummy regulator
[ 6.067631] usbcore: registered new interface driver usb-storage
[ 6.087229] usbcore: registered new interface driver usbhid
[ 6.092742] usbhid: USB HID core driver
[ 6.102279] mousedev: PS/2 mouse device common for all mice
0x00000000
0x00000000
[ 6.343496] usb 1-1: new high-speed USB device number 2 using ci_hdrc
[ 6.477558] random: lighttpd urandom read with 17 bits of entropy available
Initializing framebuffer device /dev/fb0...
xres=1024, yres=600, xresv=1024, yresv=600, xoffs=0, yoffs=0, bpp=16[ 6.505149] input: PolyVision Touch Screen as /devices/virtual/input/input1
Initializing touch device /dev/input/event0 ...
Reading From :(goodix-ts)
buttonMask: xmin:0
xmax: 1024
ymin:0
ymax: 600
Initi[ 6.527562] usb 1-1: New USB device found, idVendor=1f75, idProduct=0918
alizing VNC server:
width: 1024
height: 600
bpp: 16
[ 6.535509] usb 1-1: New USB device strings: Mfr=0, Product=3, SerialNumber=4
port: 5900
Initializing server...
[ 6.548187] usb 1-1: Product: STORAGE DEVICE
07/01/2021 16:25:45 [ 6.556268] usb 1-1: SerialNumber: 201005KT202010000000424
Listening for VNC connections on TCP port 5900
[ 6.564240] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 6.582779] scsi host0: usb-storage 1-1:1.0
rcS Complete
(none) login: [ 7.587012] scsi 0:0:0:0: Direct-Access Specific STORAGE DEVICE 0009 PQ: 0 ANSI: 4
[ 7.596083] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 7.601372] sd 0:0:0:0: [sda] 61440000 512-byte logical blocks: (31.4 GB/29.2 GiB)
[ 7.609938] sd 0:0:0:0: [sda] Write Protect is off
[ 7.615432] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 7.630193] sda: sda1
[ 7.635972] sd 0:0:0:0: [sda] Attached SCSI removable disk
insert~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
devName ==sda
devName ==sda1
sda1
sleep time == 0
/usr/bin/siglent/usr/tmp/sda1_U-disk0
[ 162.570846] usb 1-1: USB disconnect, device number 2
remove~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
sda
name == sda
mapfilelist == /usr/bin/siglent/usr/tmp/sda1_U-disk0
mapfile == /usr/bin/siglent/usr/tmp/sda1_U-disk0
mountFile == /usr/bin/siglent/usr/mass_storage/U-disk0
[ 162.623682] FAT-fs (sda1): unable to read boot sector to mark fs as dirty
[ 226.213452] usb 1-1: new high-speed USB device number 3 using ci_hdrc
[ 226.384188] usb 1-1: New USB device found, idVendor=1f75, idProduct=0918
[ 226.390838] usb 1-1: New USB device strings: Mfr=0, Product=3, SerialNumber=4
[ 226.397993] usb 1-1: Product: STORAGE DEVICE
[ 226.402224] usb 1-1: SerialNumber: 201005KT202010000000424
[ 226.410545] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 226.416874] scsi host1: usb-storage 1-1:1.0
[ 227.417025] scsi 1:0:0:0: Direct-Access Specific STORAGE DEVICE 0009 PQ: 0 ANSI: 4
[ 227.426271] sd 1:0:0:0: Attached scsi generic sg0 type 0
[ 227.431754] sd 1:0:0:0: [sda] 61440000 512-byte logical blocks: (31.4 GB/29.2 GiB)
[ 227.440215] sd 1:0:0:0: [sda] Write Protect is off
[ 227.445705] sd 1:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 227.460464] sda: sda1
[ 227.466117] sd 1:0:0:0: [sda] Attached SCSI removable disk
insert~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
devName ==sda
devName ==sda1
sda1
sleep time == 0
[ 227.498323] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
/usr/bin/siglent/usr/tmp/sda1_U-disk0
U-Boot 2014.07-svn118162 (Sep 03 2020 - 12:37:11)
Board: Xilinx Zynq
I2C: ready
DRAM: ECC disabled 128 MiB
NAND: 256 MiB
MMC: zynq_sdhci: 0
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
int board_late_init(void)+++++
buzzer_off---------------
buzzer_on---------------
buzzer_off---------------
int board_late_init(void)-----
Net: Gem.e000b000
Hit any key to stop autoboot: 1 0
zynq-uboot> j*hj*hj*ll
Unknown command 'j*hj*hj*ll' - try 'help'
zynq-uboot> help
? - alias for 'help'
base - print or set address offset
bdinfo - print Board Info structure
boot - boot default, i.e., run 'bootcmd'
bootd - boot default, i.e., run 'bootcmd'
bootelf - Boot from an ELF image in memory
bootm - boot application image from memory
bootp - boot image via network using BOOTP/TFTP protocol
bootvx - Boot vxWorks from an ELF image
bootz - boot Linux zImage image from memory
clk - CLK sub-system
cmp - memory compare
coninfo - print console devices and information
cp - memory copy
crc32 - checksum calculation
dcache - enable or disable data cache
dfu - Device Firmware Upgrade
dhcp - boot image via network using DHCP/TFTP protocol
echo - echo args to console
editenv - edit environment variable
env - environment handling commands
exit - exit script
ext2load- load binary file from a Ext2 filesystem
ext2ls - list files in a directory (default /)
ext4load- load binary file from a Ext4 filesystem
ext4ls - list files in a directory (default /)
ext4write- create a file in the root directory
false - do nothing, unsuccessfully
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls - list files in a directory (default /)
fatwrite- write file into a dos filesystem
fdt - flattened device tree utility commands
fpga - loadable FPGA image support
go - start application at address 'addr'
help - print command description/usage
i2c - I2C sub-system
icache - enable or disable instruction cache
iminfo - print header information for application image
imxtract- extract a part of a multi-image
itest - return true/false on integer compare
loadb - load binary file over serial line (kermit mode)
loads - load S-Record file over serial line
loadx - load binary file over serial line (xmodem mode)
loady - load binary file over serial line (ymodem mode)
loop - infinite loop on address range
md - memory display
md5check- check MD5 message digest
mdio - MDIO utility commands
mii - MII utility commands
mm - memory modify (auto-incrementing address)
mmc - MMC sub system
mmcinfo - display MMC info
mw - memory write (fill)
nand - NAND sub-system
nboot - boot from NAND device
nfs - boot image via network using NFS protocol
nm - memory modify (constant address)
ping - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
reset - Perform RESET of the CPU
run - run commands in an environment variable
saveenv - save environment variables to persistent storage
setenv - set environment variables
showvar - print local hushshell variables
sleep - delay execution for some time
source - run script from memory
spl - SPL configuration
test - minimal test like /bin/sh
tftpboot- boot image via network using TFTP protocol
tftpput - TFTP put command, for uploading files to a server
thordown- TIZEN "THOR" downloader
true - do nothing, successfully
usb - USB sub-system
usbboot - boot from USB device
version - print monitor, compiler and linker vers
The uImage file to reflash that portion with can be extracted from any of their firmware files
This one is from 2.2.1.2.5
EasySpectrum exists since the launch of the SSA3000X series and indeed supports the 3D waterfall rendering, even without active MEAS option on the device.
The drawback of EasySpectrum is that it relies on third-party VISA software, which is a HUGE install.
An alternative is my software, which does not need any install, as it uses the SCPI telnet port directly. However, you do need to have Windows 10. Not sure about Windows 8, but Windows 7 does definitly not work.
https://vma-satellite.blogspot.com/2017/03/vma-simple-spectrum-analyser-for.html
Regards,
Vitor
I do the same error! :-[
I had a SSA3021X-PLUS => upgrade to SSA3032X-PLUS
I would like to upgrade to SVA1032X and now my siglent wont boot after update firmware :palm:The uImage file to reflash that portion with can be extracted from any of their firmware files
This one is from 2.2.1.2.5
How can I solve my mistake ?
The root password was know?
Please help me |O :-[
Thanks
The problem of stefkpl was fixed over night.
The main advise is to NOT try to use that particular FW upgrade, as it contains an error, which was previously described in the blog.
Note that a fix requires AT LEAST access to a working copy of the main executable (in this case Aladdin), in order to be able to carry out a new FW upgrade.
@mawyatt: I have no plans to port the software - sorry! But it should run fine using Bootcamp or Parallels.
Regards,
Vitor
stefkpl tried to upgrade with "SVA1032X_3.2.2.3.2_EN.ADS".
As explained before, this FW is not safe!
It will not delete the executable (ecomb_p) correctly and as a result the FW upgrade will run out of free flash memory and fail. The executable will be corrupt and the device will not start.
It is recommended to use the newer SVA1032X_V3.2.2.3.3R1_EN.ADS which is safe.
@tautech,We'll see in a few days when new SSA3kX+ stock arrives that will more than likely need a FW update.
Please tell Siglent to remove the bad versions from the websites.
@tautech,We'll see in a few days when new SSA3kX+ stock arrives that will more than likely need a FW update.
Please tell Siglent to remove the bad versions from the websites.
I fully expect it to install without issue and only the cross flashing with the earlier version is a problem.
LOL they did exactly what I thoughtExactly and why wouldn't they.
They killed the convenient cross check they had in them to delete the misnamed files
..................
This isnt a bug at all... siglent trolled cross flashers by removing a convenience from their scripting for something that should never have been in prod in the first place from their perspective
Like Tau is getting at... its not an issue
LOL they did exactly what I thoughtExactly and why wouldn't they.
They killed the convenient cross check they had in them to delete the misnamed files
..................
This isnt a bug at all... siglent trolled cross flashers by removing a convenience from their scripting for something that should never have been in prod in the first place from their perspective
Like Tau is getting at... its not an issue
They want the $3400 sale not the $1600 one.........so do I just quietly. >:D
You are not correct.
Early SVA FW releases did not use Aladdin.
The latest FW will correctly remove ecomb_p and Aladdin.
This isnt a bug at all... siglent trolled cross flashers by removing a convenience from their scripting for something that should never have been in prod in the first place from their perspective
Ran into this interesting bit...
B&K rebadged this and some other siglent products..
Also apparently the easy spectrum pc software has a 3d spectrum monitor inside it hiding that's not advertised much
I also just received my SSA3021X Plus (calibrated 17/09-2020) So I would expect that mine is also missing the cable
Where did you get the cable?
@Ghislain
Any idea what this connector is used for?
Would be interesting whats missing in the P to become a R. Maybe it is possible to add the things which are missing really cheap..
As it appears, the "-R" versions are equipped with a completely different power supply unit , to tell from the fan much enlarged and relocated to the rear (https://www.batronix.com/shop/spectrum-analyzer/Siglent-SSA3032X-R.html). This may indicate that the "pimped" FFT engine consumes considerably more power than the standard configuration so a more powerful PSU was required. This makes it quite questionable if a hack (even combined HW/SW) would be possible.Good spotting, hadn't noticed this.
True or a pre release photo..From the US website but yes, obviously a prerelease unit as it’s not even sporting a SN# label. ::)
Markings arent there for the connectors?
I don't want to downgrade to 3.2.2.3.2 because it appears it will brick my spectrum analyzer.
I don't want to downgrade to 3.2.2.3.2 because it appears it will brick my spectrum analyzer. But I really need the Reflection option to work to tune my duplexer
IP does not change, and I have access to the web interface a all times
Got telnet access with SVA1032X_telnet.ADS
but the first command fails
/usr/bin/siglent # $ mount -o remount,rw /usr/bin/siglent/firmdata0
/bin/sh: $: not found
SVA1032X Firmware – V3.2.2.4.0 (Release Date 01.20.21 )
WARNING (https://www.eevblog.com/forum/testgear/siglent-sva1015x-1-5ghz-spectrum-vector-network-analyzer-(coming)/msg3425970/#msg3425970) for all crossflashers regarding this latest version.
3.2.2.4.0.r2 is working 100% on my SVA1032X (SSA3021X Plus with pro mode features).
3.2.2.4.0.r2 is working 100% on my SVA1032X (SSA3021X Plus with pro mode features).
3.2.2.4.0.r2
Where did "r2" come from then ??
I did the same as MOTechGuy, and also got 3.2.2.4.0.r23.2.2.4.0.r2 is working 100% on my SVA1032X (SSA3021X Plus with pro mode features).
3.2.2.4.0.r2
Where did "r2" come from then ??
Related to the cross flash I'm guessing as it's not available on official Siglent sites.I did the same as MOTechGuy, and also got 3.2.2.4.0.r23.2.2.4.0.r2 is working 100% on my SVA1032X (SSA3021X Plus with pro mode features).
3.2.2.4.0.r2
Where did "r2" come from then ??
Did you download from int.siglent.com ?
Related to the cross flash I'm guessing as it's not available on official Siglent sites.
Related to the cross flash I'm guessing as it's not available on official Siglent sites.I did the same as MOTechGuy, and also got 3.2.2.4.0.r23.2.2.4.0.r2 is working 100% on my SVA1032X (SSA3021X Plus with pro mode features).
3.2.2.4.0.r2
Where did "r2" come from then ??
Did you download from int.siglent.com ?
I agreee, I did download the SVA1032X_V3.2.2.4.0_EN, so it must have something to do with the cross flash.I suspect it's a little flag added by the SW engineers. ;)
I agreee, I did download the SVA1032X_V3.2.2.4.0_EN, so it must have something to do with the cross flash.I suspect it's a little flag added by the SW engineers. ;)
The r2 is from using pro mode and not actually have entered license keys... nothing to do with cross flash itselfI think I understand, I actually entered the keys on mine, with a little help ;)
Just bought a SSA3021X plus. I have upgraded it to a SVA1032X. I was able to flash the unit with the newer firmware V3.2.2.4.0 successfully.
I noticed that the any of the telnet ADS don't work anymore?
Just bought a SSA3021X plus. I have upgraded it to a SVA1032X. I was able to flash the unit with the newer firmware V3.2.2.4.0 successfully.
I noticed that the any of the telnet ADS don't work anymore?
The device shows that it is a SSA3032XP but goes to 2.1GHz only.
I shoes the VNA mode greyed out.
(I haven't completed the step to enable all options with serial # turning into all Xs).
From memory, you need to unlock the options to get the bandwidth and VNA enabled.Hi -
I have a SSA3021X Plus with the latest V3.2.2.3.3R1 firmware, and followed post #1223 (except step 2/3 since it's no longer required per a later post), and was able to flash the factory SVA 1032X V3.2.2.3.3R1 firmware.
However, after the upgrade, I have TG menu disabled (and TG not even showing a permanently enabled option under info like before the flash), I also don't see disabled VNA option under "Mode".
I then updated "NSP_trends_config_info.xml" as per instruction, and have since got TG option back. However, I'm still capped at 2.1G, but it's my understanding that it should now have been expanded to 3.2G, what am I doing wrong?
(I haven't completed the step to enable all options with serial # turning into all Xs).
Thanks!
3.2 GHz is one of the options, so you have to unlock them to get it.
Thanks! That's indeed the case, I'm now unlocked all options with SN becoming all Xs. Now to research how to get the actual SN back. :)
Thanks everyone and happy new year!
Continuing on from where I left off, I've since got the calibration kit.
After performing the 1-port calibration under the VNA menu, it still shows "---" on the upper left corner, which according to the manual means "No calibration data". I expected it to show "Cor" to indicate calibrated.
Performing calibration under DTF appears to be working, and I get "Cor" showing once completed.
Does anyone else see this? Could this be due to missing the SMA cable?
Thanks!
Hello hero’s,
I received my SSA3021X-plus today.
I made a backup of the nand with the tool provided by TV84.
It is only 488 MB. Is this correct?
Grtz. Niek
The cross flash backup script worked?
On my cross flashed SVA same Firmware it didn't work. Maybe i will try a 2. USB stick..
How did you display the contents of the startup file?
There was an issue a while back with hidden control characters messing up the printed output
https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3367292/#msg3367292 (https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3367292/#msg3367292)
Try displaying the file with the cat command.
I found a NSP_trends_config_info.xml file in this thread and thought to be smart and instead of editing the NSP_ config_upgrade_info.xml I copied this over the upgrade file. |O :palm:
Now I’m missing the original NSP_ config_upgrade_info.xml file.
Does someone have a copy of that file for me?
thanks to a helpful member i have now a SVA3000X-Plus :clap:Not exactly, it's a SVA1000X.
I am thinking to get a SSA3021X+ while they can still be worked on, and cross flashed. If I understand what I saw in the VNA thread, they are locking things down. I am curious if current stock with distributors need the cable added inside.To know this we would need to break the warranty seal....not gunna happen.
I am thinking to get a SSA3021X+ while they can still be worked on, and cross flashed. If I understand what I saw in the VNA thread, they are locking things down. I am curious if current stock with distributors need the cable added inside.To know this we would need to break the warranty seal....not gunna happen.
Despite how difficult Siglent might make it there are some very smart people here that will just find a way around it.
If they could be software updated to 7G, that would really be something. ;D
Maybe it's only about software development optimization...Entirely.
Hello Everybody and TV84 , i did everything following the book
Started with SSA1021X+ 3.2.2.3.2, downgraded to 2.2.1.2.5
then did the whole trick telnet etc.. according msg 1223 and following
now i am stuck with a working but not unlocked.. SVA1032x
how to proceed further
Tnx for help
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.Welcome to the forum.
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
to #1532I 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.
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 ?
"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 (https://stackoverflow.com/questions/5843495/what-does-m-character-mean-in-vim).
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.
"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 (https://stackoverflow.com/questions/5843495/what-does-m-character-mean-in-vim).
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.
Just take a look
It allows me to send 1032SVA telnet script and also 1032SVA firmwares. It shows 100% upload and after some time aprox 10 minutes it will write "Failed" with no difference.
No. I am able to run www vnc interface.
I'm having the same behavior. I got my SA yesterday, and I have not been able to get anything to work from flash; not the crossflash firmware, ...
Perhaps. One more finding, I tried to flash back the stock SSA+ Firmware and now lost the Tracking Generator :palm: doesn't even show up as an option after what looked like a successful flash.
Can't Telnet in with this file. Sits on Upgrade Screen for 60 seconds before exiting back to the File Explorer, same as any other ADS
Interesting... ::) Maybe some countermeasures have indeed made their way into this latest version.Yes, it works for me (3.2.2.4.0)
Can any of you telnet with this file? (should only work on SSA3021_3032XP_V3.2.2.4.0 or up)
Remember that it's port 10101.
In a nutshell:
1 - Flash the latest SSA+ FW.
2 - Go in with a telnet .ADS.
3 - Make the FS RW.
4 - Change the ProdID in config/NSP_config_upgrade_info.xml to 11403.
5 - Sync & Reboot
6 - Flash the latest SVA1032X FW.
I received my SSA3021X-Plus that shipped with version V3.2.2.4.0 today and everything is working as expected. Thanks!... by doing what, exactly? I am in the same situation, but I have only tested telnet by now. Not sure what procedure is best to follow.
Hi tv84, am I correct in saying that, having an SSA3021+ with FW 3.2.2.4, I should change ProdID from 11411 to 11410 and not 11403 before upgrading to SVA 3.2.2.4?
If you already know that the SVA1032X_telnet.ADS doesn't work because the upgrade changes the Prod ID from 11403 to 11410, I will close up my disconnect my serial and close up my SA because no you don't need any more debug info.
Kevin
Is it possible to use integrated bridge instead of external one (RB3x25) for SWR measurement with SSA3000X-Plus models ?No, not unless you convert the SSA3kX Plus into something else ;) with a different feature set that allows for single port SWR measurements.
Is it possible to use integrated bridge instead of external one (RB3x25) for SWR measurement with SSA3000X-Plus models ?No, not unless you convert the SSA3kX Plus into something else ;) with a different feature set that allows for single port SWR measurements.
Do some research here and it will all become clear.
Change USB disk.
Try to partition and format your USB disk to a 2gb FAT32 partition. No need to buy a new disk.
Can you write the screenshot to that USB stick?
Anyway, I think you have a totally different issue.
The SSA3000+ will have different HostID according to installed FW. You can only used the fake update if you are currently on the compatible FW. Otherwise the HostID does not match and the upgrade is refused.
The SSA3000+ will have different HostID according to installed FW. You can only used the fake update if you are currently on the compatible FW. Otherwise the HostID does not match and the upgrade is refused.
Backup script for V3.2.2.4.0 FW and up.
:( Let's wait for someone else to test. If he has the same behavior, I'll remove it.
You have v3.2.2.4.0, right?
BTW, you still have a SSA3000X+ or you did the crossflash to SVA?
Try to reflash the stock version 3.2.2.4.0 and tell us what happens. You shouldn't be able to do it.
Trying to update with factory firmware just did the same loading for 20-30 seconds then fall back to file manager window.
I tried the last ads file you attached on other flash drives and I think it was successful.
It did the loading screen for about 1.5minutes, then beeped and rebooted. I have extra files now. mtd?.bin, firmdata0 and memdump.
Trying to update with factory firmware just did the same loading for 20-30 seconds then fall back to file manager window.
I tried the last ads file you attached on other flash drives and I think it was successful.
It did the loading screen for about 1.5minutes, then beeped and rebooted. I have extra files now. mtd?.bin, firmdata0 and memdump.
So, all went according to plan. (It's the 2nd time I see these things working only at the 2nd try. Don't know why and I don't care.)
The stock FW is impossible to reflash (it's a feature), as you've witnessed, because of the ProdID change. ATM, only my 11411 .ADS files can be used in this specific equipment.
The "extra files" are the backup as intended. The "errors found" are not significant and Windows took care of them.
You can use the 11411 telnet .ADS and go for the crossflash.
Since you already have the Aladdin app, you only have to change the Prod ID to 11403 in order to be able to crossflash the SVA FW SVA1032X_V3.2.2.4.0. Good luck.
Trying to update with factory firmware just did the same loading for 20-30 seconds then fall back to file manager window.
I tried the last ads file you attached on other flash drives and I think it was successful.
It did the loading screen for about 1.5minutes, then beeped and rebooted. I have extra files now. mtd?.bin, firmdata0 and memdump.
So, all went according to plan. (It's the 2nd time I see these things working only at the 2nd try. Don't know why and I don't care.)
The stock FW is impossible to reflash (it's a feature), as you've witnessed, because of the ProdID change. ATM, only my 11411 .ADS files can be used in this specific equipment.
The "extra files" are the backup as intended. The "errors found" are not significant and Windows took care of them.
You can use the 11411 telnet .ADS and go for the crossflash.
Since you already have the Aladdin app, you only have to change the Prod ID to 11403 in order to be able to crossflash the SVA FW SVA1032X_V3.2.2.4.0. Good luck.
I don't get it, now the telnet ADS file works. I have already tried these files and flash drives a dozen times. :-// sorry my post added little help for future people.
I will follow in hopes you can get this sorted out. I am expecting my SA to arrive any day now... hopefully i will be able to learn how to do all this right and what causes this issue with your conversion. Can you tell me which FW it originally had and i'll compare when i get mine.
thx
I will follow in hopes you can get this sorted out. I am expecting my SA to arrive any day now... hopefully i will be able to learn how to do all this right and what causes this issue with your conversion. Can you tell me which FW it originally had and i'll compare when i get mine.
thx
Mine had the latest 3.2.2.4.0
not sure if the issue is related to my unit or if some how I am messing something up. hopefully tv84 can get me sorted and shed some light.
Thank you TV84! :-+
And a big thanks to members for their great time and patience for helping others. Your expertise is hugely appreciated! :-+ :clap:
Will let you all know when things have "Improved"! 8)
All the best to everyone.
Marty
I recently got interested in getting a spectrum analyzer for some EMI stuff and have read the past ~15 pages of this thread. It seems that buying a SSA3021X Plus and crossflashing it to a SVA3032X is the best bang per buck. A big thanks to everyone who makes this possible!
Before I take the leap I was wondering if anyone could confirm two things:
The SVA3032X has the same hardware as the SSA3021X Plus and the unit will have the same specifications (except for one cable which may occasional be missing? People seem to not have reported that recently, so perhaps those units were a fluke?)
The latest firmware on the siglent website is V3.2.2.4.0 which people have successfully upgraded, so wherever I buy the the SSA3021X Plus from I should be able to upgrade?
Marty,
I'll share this once again: https://files.fm/u/a3rnz873y (https://files.fm/u/a3rnz873y)
This allows a direct crossflashing from SSAX+ to SVA, assuming that the SSAX+ version is V3.2.2.4.0.
No previous modifications are required to the inside files!
If required, the after modifications are as usual (see point V in electr_peter's latest summary (https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3563577/#msg3563577)) .
PS: If it doesn't work 1st time, reboot and try a 2nd time...
Inside the device there are two connectors that need to be connected with a cable for the SVA functionality. This cable was missing on some SSA models, where the cable is not needed. By upgrading to SVA the cable is needed and can be fitted.
I don't have any pictures of this nor do I know what the cable looks like. I guess it is just a short cable with two SMA connectors but perhaps someone can share more insight.
Thank you.
Could anyone repost the link of file of tv84
"I'll share this once again: https://files.fm/u/a3rnz873y"
"This allows a direct crossflashing from SSAX+ to SVA, assuming that the SSAX+ version is V3.2.2.4.0."
Another question:
is it possible only on SSA3021X Plus or also on SSA3015X Plus?
In Zero Span mode, the TG frequency will match the center frequency of the analyzer.
I performed the modifications under item V of electr_peter's post 16124
I performed the modifications under item V of electr_peter's post 16124
It looks like you didn't do this correctly or, at least, complete...
I performed the modifications under item V of electr_peter's post 16124
It looks like you didn't do this correctly or, at least, complete...
yes probably, but I can't see what is wrong. I also renamed the two files to nsp_data_b1x and nsp_data_bx, adding an x at the end of each. Those two files are still there upon reboot, although the system added new ones with the original names after rebooting. I suppose that is normal. Perhaps I should remove them and reboot.
I can tell you that I performed the changes per this post (https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3563577/#msg3563577 (https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3563577/#msg3563577)) and nothing else and it was painless. Perhaps start over and go through that list.That is exactly what I did, with several exceptions: I did not modify NSP_config_upgrade_info.xml to change the product ID's, since I had already crossflashed to the sva1032x, and even after mount -o remount,rw /usr/bin/siglent/firmdata0, I had to add write permission chmod o=rw NSP_sn_bandwidth.xml in order to modify it. maybe I should change it back to read only. I can't see how that would make any difference, but who knows?
Another success in running the SSA3021X with all options, full bandwidth and the SVA firmware. Serial number all the XX of course.Welcome to the forum.
Like others I too found that the USB drive was mounted read only and my solution required checking the drive block device name, unmounting it and mounting it again. More or less a long hand way of doing what has already been described by Weston in 1653 which I hadn’t noticed at the time so I won’t add unnecessary instructions to the thread.
At one point I took a pause of a few minutes to deal with another matter and when I returned the USB drive was read only again. I haven’t checked but I am guessing there is a cron job that is scheduled to do this regularly. I re-enabled write access and all was well.
Can I just add that I am retired and have no real “need” for a nice SVA1032X with all the options. I am educating myself in some finer arts of RF analysis and will derive no financial gain from doing these upgrades. But I am deriving much pleasure and knowledge. I suspect many home customers are the same.
I wouldn’t have purchased an SSA3021X if it would have remained as a base unit. There are better second hand options on the market for educational purposes. I would hazard a guess that Siglent are not losing money by us doing these upgrades, probably the contrary. If I was still in business I wouldn’t dream of doing this kind of thing. Imagine going to the boss to explain why you’ve bricked the test gear and lost the warranty ?!
So thank you tv84 et al, your extensive work and your time is hugely appreciated.
files that TEMPORARILY activate telnet on a specific port (don't remember which port - it is normally not the common port 21!).
G'day,Welcome to the forum.
I have a SSA3021x that developed a problem with the display becoming unstable after warming up for a few minutes. A video showing the problem can be viewed here -
https://www.ping.net.au/SSA3021x_Display_Fault.mov (https://www.ping.net.au/SSA3021x_Display_Fault.mov)
AFAICT, everything else continues to work just fine. This unit is about 5 years old and has performed flawlessly until now. It is running firmware 1.3.9.7 on HW 07.03.00, which I believe is current. I suspect the fault to be either the power supply, video controller or LCD. At the moment I'm lost without a circuit diagram and spare parts. Has anyone seen this before and fixed the problem? I really appreciate any help you can provide.
Hello,SSA Plus and SVA have a different programming guide to SSA so maybe your code and command set needs to account for the differences.
I need some help from owners of the SSA3000X-Plus and SVA3000:
My "VMA Simple Spectrum Analyser Software for SSA3000X" (https://vma-satellite.blogspot.com/2017/03/vma-simple-spectrum-analyser-for.html) does not work with the Plus and SVA models.
I suspect this is because the ":TRACe:DATA? 1" command will not output exactly 752 samples as the SSA3000X model, but a different amount of samples.
I wonder if someone can tell me how many samples this SCPI command produces.
Also, if someone happens to know what else could cause the incompatibility, I would appreciate it. The only command that seems to be causing issues with my software is this ":TRACe:DATA?" command. Setting thiings like Start/Stop Frequency works apparently fine. Unfortunately I don't own the Plus model...
Thanks,
Vitor
Hello,
I need some help from owners of the SSA3000X-Plus and SVA3000:
My "VMA Simple Spectrum Analyser Software for SSA3000X" (https://vma-satellite.blogspot.com/2017/03/vma-simple-spectrum-analyser-for.html) does not work with the Plus and SVA models.
I suspect this is because the ":TRACe:DATA? 1" command will not output exactly 752 samples as the SSA3000X model, but a different amount of samples.
I wonder if someone can tell me how many samples this SCPI command produces.
Also, if someone happens to know what else could cause the incompatibility, I would appreciate it. The only command that seems to be causing issues with my software is this ":TRACe:DATA?" command. Setting thiings like Start/Stop Frequency works apparently fine. Unfortunately I don't own the Plus model...
Thanks,
Vitor
| PIN | Color | Voltage | Remarks |
| 1 | black | 0V | chassis ground |
| 2 | grey | -9.6V | |
| 3 | red | 7.3V | |
| 4 | red | 7.3V | |
| 5 | blue | 14.9V | |
| 6 | brown | 0V | soft power switch? |
| 7 | black | 0V | chassis ground |
| 8 | black | 0V | chassis ground |
The first task was to measure the power supply voltages on the back of J16. The values obtained are shown below:SSA3000X and SDS1004X-E DSO's apparently share the same PSU.
[PIN/td]
Color Voltage Remarks 1 black 0V chassis ground 2 grey -9.6V 3 red 7.3V 4 red 7.3V 5 blue 14.9V 6 brown 0V soft power switch? 7 black 0V chassis ground 8 black 0V chassis ground
These measurements were taken immediately after applying power to the equipment, which may be helpful for others in the future. Unable to source the datasheet for the power supply, it is impossible to determine if these voltages are within specifications.
I'm grateful for any help in sourcing a spare power supply.
This may be nothing more than a LDO 15V regulator. How many pins, and what are the voltages to the pins. Check with a scope to see if the voltages are dynamic or static, that will provide an additional clew.
SSA3000X and SDS1004X-E DSO's apparently share the same PSU.
From the SDS1004X-E service manual:
Measured at PSU.....note there are some lead color differences between SSA and SDS.
GND Pin 4, Pin5, Pin 6 Black NULL
Primary Power Pin 1, Pin 2 Red +6.5 V𝐷𝐶 ± 10%
Positive Auxiliary Pin 8 Blue +15 V𝐷𝐶 ± 10%
AC Line Trigger Pin 7 Brown 2V𝑃𝑃 ± 20% This will only affect AC Line Trigger function.
Negative Auxiliary Power Pin 3 Orange -9.5 V𝐷𝐶 ± 10%
Hope that helps.
The 15V regulator getting very hot may indicate a problem with the LCD, and as Mark indicated the regulator may be protecting itself by dropping to low output voltage due to over thermal stress (some are designed to do this, rather than just burn up). If the LCD is unplugged does the 15 Volts return? If so then maybe the regulator (and PS) is OK and the fault is with the LCD??
Not knowing the exact architecture of this power supply, it might be a wide input range supply with a pre boost mechanisme so the unit can remain efficient both on 100-140 as well as 200 - 250 V. If this stage is not operating well then the regulator will have troubles operating at to high voltage. In your case it behaves like it is on the low range and gets input according to the high range. But again I haven't seen any schematics yet. One way of testing is to put the scope on 110-120 V and see if it behaves as it should
Let us know how you get on and if necessary I can give these guys a poke into action.Not knowing the exact architecture of this power supply, it might be a wide input range supply with a pre boost mechanisme so the unit can remain efficient both on 100-140 as well as 200 - 250 V. If this stage is not operating well then the regulator will have troubles operating at to high voltage. In your case it behaves like it is on the low range and gets input according to the high range. But again I haven't seen any schematics yet. One way of testing is to put the scope on 110-120 V and see if it behaves as it should
Thanks and I agree with your theory as Australia has 240VAC mains supply. Using a variac set to 120VAC, I performed the same test and can report that the 15V measures a rock solid 14.98V and the regulator is only getting moderately warm. The 6.5V rail measures 6.49V and is in specifications. Running the equipment for over 30 minutes and the fault hasn't shown up. All I need now is a replacement part.... I've yet to receive a reply from the Australian Siglent distributor (IPD) and Siglent HQ in response to my support request.
Continuing on from where I left off, I've since got the calibration kit.
After performing the 1-port calibration under the VNA menu, it still shows "---" on the upper left corner, which according to the manual means "No calibration data". I expected it to show "Cor" to indicate calibrated.
Performing calibration under DTF appears to be working, and I get "Cor" showing once completed.
Does anyone else see this? Could this be due to missing the SMA cable?
Thanks!
More observation - in VNA, if I perform a "open cal", it should display "Cor" on the upper left corner of the chart, same if I perform a "close cal".
But if I do a "1 port cal", it would display "---". I also notice that after calibrating with open/close/load with "1 port cal", pressing Enter will hang the system for a few seconds before the beep, not sure if related.
I too want to buy one but not sure if this a Plus model here on amazonIt is NOT the plus model.
https://www.amazon.com/Siglent-Technologies-SSA3021X-TG-Spectrum-Analyzers/dp/B08C37Z1X6/?_encoding=UTF8&pd_rd_w=Wo98x&pf_rd_p=205b21f0-8557-4ea8-a863-e58f77379cf8&pf_rd_r=P7YGNMD6HYDXARTJ7G88&pd_rd_r=26389e0c-ea62-4574-a0de-c80b6724d72e&pd_rd_wg=NyIBn&ref_=pd_gw_ci_mcx_mr_hp_atf_m (https://www.amazon.com/Siglent-Technologies-SSA3021X-TG-Spectrum-Analyzers/dp/B08C37Z1X6/?_encoding=UTF8&pd_rd_w=Wo98x&pf_rd_p=205b21f0-8557-4ea8-a863-e58f77379cf8&pf_rd_r=P7YGNMD6HYDXARTJ7G88&pd_rd_r=26389e0c-ea62-4574-a0de-c80b6724d72e&pd_rd_wg=NyIBn&ref_=pd_gw_ci_mcx_mr_hp_atf_m)
Thanks for your help!
Another question:
is it possible only on SSA3021X Plus or also on SSA3015X Plus?
Once a SSAX+ reaches V3.2.2.4.0, they all start using the same FW.
So, you can do a conversion to SVA1015X but you can't upgrade beyond that. Here (https://www.eevblog.com/forum/testgear/semirandom-but-careful-mistakes/msg3374756/#msg3374756).
Does that mean the "new" SVA will always stay at firmware V3.2.2.4.0 ? No future updates ?
I opend the machine and guess what? It is realy a hardware fault.
There are 2 main series of SSA3000, X and X+ with has the enhancements of the earlier X series.I opend the machine and guess what? It is realy a hardware fault.
So, I have been reading this thread about the upgrade, of a SSA to a SVA. And I came across this "cabel fix".
BUT, if you look at this video from the repair thread, this guys SSA does not have those extra connectors
or that second short cable.
https://www.eevblog.com/forum/repair/fixing-the-rf-front-end-of-a-spectrum-analyzer/ (https://www.eevblog.com/forum/repair/fixing-the-rf-front-end-of-a-spectrum-analyzer/)
Does that mean that this can not be converted to a fully functioning SVA ??
Many Thanks !
rudi
BUT, if you look at this video from the repair thread, this guys SSA does not have those extra connectors
or that second short cable.
Does that mean the "new" SVA will always stay at firmware V3.2.2.4.0 ? No future updates ?
I believe the reference to 'upgrade' was that you can't go from a 3015 to a 3021/32
So I will be able to flash future SVA firmware upgrades in to my unit, correct ?
hp85033C
I have a question regarding calibration kits.
What kits do you use ?
So far I have been using the cheap SMA kit from AliExpress: open, short and load.Generally speaking, yes.
But I see so many really expensive kits. What is your take for up to 3.2 GHz calibrations ?
Do the expensive kits really make a difference ?
You’re doing a S21 measurement.
S21 sends out the signal from port 2 and measures on port 1.
So where (how) have you attached the 50ohm load??
Did you re-enable telnet in the startup script after the upgrade? If you are using the telnet ADS script, are you using the right model number, as it changes in later firmware and after a cross flash.
....
The worst of it all, I can not longer telnet in to the unit. Even the telnet ADS that used to work, have
stopped working. I tried static IP and DHCP, same result.
...
Port 1 is TG, Port 2 is RF In.You’re doing a S21 measurement.
S21 sends out the signal from port 2 and measures on port 1.
So where (how) have you attached the 50ohm load??
Did you re-enable telnet in the startup script after the upgrade? If you are using the telnet ADS script, are you using the right model number, as it changes in later firmware and after a cross flash.
There is no change in the image when I set it to S11. Sorry about the mixup, I do
understand the difference between S11 and S21, etc ;)
The Load is on the "RF Input" I assumed that would be "Port 1", but I have tried
to add the load on the TG port, and nothing changes.
Thanks,
rudi
Port 1 is TG, Port 2 is RF In.
S11 measurements are reflection measurements on Port 1 whereas Port 2 measurements (S21) come from RF In.
The garbage you see is a product of interpolation from too few points (201) and a wide frequency sweep.
In the VNA menu you can set the points to the max of 751 and a totally different result will be produced and likewise with a narrow sweep.
Jump over into the SVA thread for more info and stuff on Cal kits:
https://www.eevblog.com/forum/testgear/siglent-sva1015x-1-5ghz-spectrum-vector-network-analyzer-(coming)/ (https://www.eevblog.com/forum/testgear/siglent-sva1015x-1-5ghz-spectrum-vector-network-analyzer-(coming)/)
I have followed Reply #1624 to upgrade my SSA3021 PLUS.
After step I) Initial backup of SSA3021X Plus
There's no back files in my U disk.
What's wrong happened?
I have tried several U disks.
All the U disks were formatted as FAT32 on Windows 10 PC.
yes, I have unzipped the file.
I have followed your advice. After excuting the .ads file，the SSA3000 showing “upgrading …”，and reboot automatically.
There's no other files in the USB disk except ssa3000x+_backup_11411.ads after rebooting.
How to check the product id in the ads file？
How to check the product id in the ads file？
Damn! I made a bigger mistake!!! :palm:
Now the SSA3032X-R became a SSA3075X-R.
There goes the neighborhood...
Damn! I made a bigger mistake!!! :palm:
Now the SSA3032X-R became a SSA3075X-R.
There goes the neighborhood...
I presume that this is a joke, since there don't appear to be any instructions on all of eevblog on how to get apply this sort of hack to an SSA3000X-R series model. (only models without the -R)
Damn! I made a bigger mistake!!! :palm:
Now the SSA3032X-R became a SSA3075X-R.
There goes the neighborhood...
I presume that this is a joke, since there don't appear to be any instructions on all of eevblog on how to get apply this sort of hack to an SSA3000X-R series model. (only models without the -R)
It is not a joke, but the hack is not public.
Damn! I made a bigger mistake!!! :palm:
Now the SSA3032X-R became a SSA3075X-R.
There goes the neighborhood...
So what is stopping this hack from going public?
How do we know this hack is legit if no other person has duplicated your steps so far and a almost year has gone by. These could be just images from a higher end model superimposed (i.e., Photoshoped) over the screen of the SSA3032X-R for all we know!
So what is stopping this hack from going public?
It's called "freedom of choice".How do we know this hack is legit if no other person has duplicated your steps so far and a almost year has gone by. These could be just images from a higher end model superimposed (i.e., Photoshoped) over the screen of the SSA3032X-R for all we know!
I use Paintbrush.
PS: Those type of comments/demands are usually the best reason for not disclosing some of these things publicly. Think about it.
Can you at least tell us if it is a SW/FW hack only, or if HW needed to be "adjusted" as well?
My SSA IP is 192.168.31.18
I can PING 192.168.31.18 successfully.
When I telnet 192.168.31.18 10101, it showed: unable to open host connection. on port:10101 connection failed.
Thank you.
Could anyone repost the link of file of tv84
"I'll share this once again: https://files.fm/u/a3rnz873y"
"This allows a direct crossflashing from SSAX+ to SVA, assuming that the SSAX+ version is V3.2.2.4.0."
Plan B
Take the SVA stock FW and do the changes in the attached picture.
A simple question: the cross-flash SSA3021X-Plus to SVA1032X results in an uncalibrated spectrum analyzer in the 2.1 to 3.2GHz range... It's correct?
If so, this could be a big problem!
A simple question: the cross-flash SSA3021X-Plus to SVA1032X results in an uncalibrated spectrum analyzer in the 2.1 to 3.2GHz range... It's correct?
If so, this could be a big problem!
I'm wondering the same thing myself. If the SSA3021X-Plus is "upgraded" does it need to be re-calibrated up to 3.2GHz? Does anyone know?
I would say it is well calibrated, because it behaves very well in all tests. Besides, by looping with the TG, the response is flat.
Perfectly agree, in fact I said "I would say it is well calibrated...".I would say it is well calibrated, because it behaves very well in all tests. Besides, by looping with the TG, the response is flat.
The flat response when used in loop with TG is a "relative calibration". It is not indicative of the analyzer's absolute calibration status...
It is a pity that no one has any certainty about the calibration status of the instrument once ... "expanded".
Personally, I think that a measuring instrument without the necessary guarantees regarding its accuracy has very little value (even for those who make use of it as a hobby ...)
I bought the SVA1032x from TEquipment and I don't remember seeing a calibration certificate. Perhaps I missed it and it is buried deep in the file cabinet. I am, however, confused about this now with how concerned people seem about it. At the time, I also bought the F503ME cal kit from Siglent.You should have a calibration certificate similar to the one in photo for the analyzer and another for the cal kit.
I found it. Yep, I'm just a hobbyist. If I can tune some UHF antennas with it 10 years from now, I'll be happy. I got it so I could make wifi antennas and passive cellular repeaters when the nano wasn't getting the job done. I never intended on doing test work with it for other people, I just worried that it will drift into uselessness over time with the widespread concern over lab calibrations. I want to believe, for my uses, I should never have to worry about it.I bought the SVA1032x from TEquipment and I don't remember seeing a calibration certificate. Perhaps I missed it and it is buried deep in the file cabinet. I am, however, confused about this now with how concerned people seem about it. At the time, I also bought the F503ME cal kit from Siglent.You should have a calibration certificate similar to the one in photo for the analyzer and another for the cal kit.
Companies are very concerned about certificates and their validity, because quality assurance require them. It's a chain: as you see, Siglent uses calibrated instruments of a superior class to guarantee that this one satisfies specs.
If you are an hobbist, you can probably live with expired certificates.
If you restore the serial number, you will loose the factory mode and all options it enabled.
If everything is working fine, stop messing around with it!
Yeah, you’re right (of course). I discovered that involves more than just SCPI’ing back your old number but that you have to generate a new serial number. Oh well, can’t complain really.
Now, that SDS2104X Plus looks mighty tasty, and I can convince myself I’ve outgrown my Rigol DS1054Z…
Can someone please explain to me, what measurements are requir do for EMC? I might eventually add those to my software.A wee overview is in the SSA3000X Plus manual on P134
EMC testing is something I have never done, so I would need some assistance.
What can the SSA3021X be upgraded to?SSA3032X
Hello,
has someone already tested the new version of the firmware (V3.2.2.5.0 - Release Date 12.03.21 ) for the SVA1000x plus? Will all options and modification remain?
best regards,
Juergen
They keep forgetting the that everyone is a linux geek until access is lost (in a sealed machine)...
Hello,I suggest you to post to the sibling thread on the SVA https://www.eevblog.com/forum/testgear/siglent-sva1015x-1-5ghz-spectrum-vector-network-analyzer-(coming)/725/ (https://www.eevblog.com/forum/testgear/siglent-sva1015x-1-5ghz-spectrum-vector-network-analyzer-(coming)/725/)
after upgrading my "SVA1032X" to 3.2.2.5.0.r8, I experience some issues with the VNA, SA not tested so far.
1) When being through the calibration procedure (e.g. 1-port-cal) the "apply calibration" is "on", but garbage is shown on the screen. Cal status is "C?" - see Pic 1. After Switching it to "off" it seems to be working, see Pic 2 of the calibrated load. But it shows "---" in the upper left corner for the cal status.Didn't understand what was on the input ports during those measurements. However, it remembers the bug in "pro mode" being discussed in the other thread for release 3.2.2.4
Hi,Please, the SVA thread is here:
what I found out to 2) : If you change the no. of points in the calibration menu (when asked to apply the open standard) by touching the points (751) on the screen to e.g. 10000 - calibration will work for the number of points selected. However, it jumps back to 751 point frequently.
Regarding the PIC1&pic2 attached, they show the same 50 Ohm load, used for calibration.
I can tell you that I performed the changes per this post (https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3563577/#msg3563577 (https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3563577/#msg3563577)) and nothing else and it was painless. Perhaps start over and go through that list.That is exactly what I did, with several exceptions: I did not modify NSP_config_upgrade_info.xml to change the product ID's, since I had already crossflashed to the sva1032x, and even after mount -o remount,rw /usr/bin/siglent/firmdata0, I had to add write permission chmod o=rw NSP_sn_bandwidth.xml in order to modify it. maybe I should change it back to read only. I can't see how that would make any difference, but who knows?
It will not flash back to SSA3021_3032XP_V3.2.2.4.0.ADS so I cannot start over from scratch. I could try reflashing with the factory SVA1032X_V3.2.2.4.0.ADS, maybe something went wrong with the first time. That will likely remove telnet access, so I hope that telnet_11410.ads will get me back in.
Another difference from peter's summary, he says "serial number shows XXXX." however my serial number is shown in the system info screen, and starts with "SSA3....). Maybe I should change it to XXXX
Does anyone have a better idea?
update: I found a solution. I deleted /usr/bin/siglent/firmdata0/nsp_data_b1 once more, then sync && reboot. Voila! All options enabled and now the serial number shows as XXXXX. I do not know what happened the first time around. After my changes, I entered sync, but then cycled the power from the front panel. This time, I did sync && reboot. That is the only thing I can think of.
Many thanks to all who unlocked this gem! The built-in directional bridge works well over the full 3.2 Ghz band. After calibration, measuring S11 of a 20 dB pad reads 40 db return loss, just as it should. Clearly my unit has the internal reference cable that was missing on some units.
mv nsp_data_b1 nsp_data_b1xcaused a read only message I responded y to but result was a renamed copy and the original still there. Turns out I had previously done an incorrect copy paste of mount -o remount,rw /usr/bin/siglent in step 3 instead of mount -o remount,rw /usr/bin/siglent/firmdata0Then I had difficulty deleting the file as it kept reappearing. The solution was to use top to find the process number of the Aladdin process, kill it, do the correct mount remount, then rm nsp_data_b1, then sync, reboot... SUCCESS! YA!Edit: Got PuTTy to work on macOS. Reinstalled XQuartz and all was good.
They keep forgetting the that everyone is a linux geek until access is lost (in a sealed machine)...
Quote of the month.... :-+
/sbin/telnetd -l /bin/sh -p 10101 &
After /sbin/telnetd, it should be a a lowercase L (l) not a One (1)Code: [Select]/sbin/telnetd -l /bin/sh -p 10101 &
Following the advice of TV84 in the SDG2000X thread I removed the old hack and used the well known Python-script for a licensing of the bandwidth option for my SDG2000x.
Are there any news to do the same for the "improved" SSA3000X+ and to overcome the issues with SNAs without serial number? Is the Python-script working for SVA option licensing?
Thanks in advance!
Can you share some details more with us? Thanks!
Hello I have a huge problem.
My SSA3021+ was on SW 3.2.2.5.0 i tried to logon with telnet Hack SVA1000X_telnet_11410.ads this works.
So i replaced
<upgrade_static_id>11411</upgrade_static_id>
with
<upgrade_static_id>11403</upgrade_static_id>
And reboot.
Then I tried to install SVA SVA1032X_V3.2.2.4.0_11411 whitch fails. I can not reach the SSA with telnet anymore i tried SVA1000X_telnet_11410 and SSA3000X+_telnet_11411 again with no connection. I there a way to bring back the restored files ? Can anybody help me ?
@karl11
Even with cross-flash you can't do the downgrade to V3.2.2.4.0 I think.
You have to cross-flash 3.2.2.5.0 SVA on V3.2.2.5.0 SSA+
I assume with 3.2.2.5.0 firmware 11411 and 11403 PIDs remain unchanged.
Has any of you got success to add or install the EMC option (EMI Receiver Measurement) on SS3021X or SSA3032X ?The EMI UI was substantially improved in the later Plus/X-R and SVA models and later the SSA3kX Plus/X-R/SVA User manual updated with how to best use it.
Thanks, Albert
Has any of you got success to add or install the EMC option (EMI Receiver Measurement) on SS3021X or SSA3032X ?
Thanks, Albert
Perhaps I missed it in the specs, but what is the maximum sweep bandwidth?The full BW of the model.
Paul
The full BW of the model.Is it possible to choose specific start freq and end freq when displaying in LOG mode the frequency axis (i.e. EMC testing case) ?
Eg. SSA3021X/X Plus 9Khz - 2.1 GHz or any frequency range between including a zero Hz sweep at any frequency within the model's range.
Which model series ?The full BW of the model.Is it possible to choose specific start freq and end freq when displaying in LOG mode the frequency axis (i.e. EMC testing case) ?
Eg. SSA3021X/X Plus 9Khz - 2.1 GHz or any frequency range between including a zero Hz sweep at any frequency within the model's range.
Sorry I should have mentioned, my question was about the SSA3kX not the Plus.Which model series ?The full BW of the model.Is it possible to choose specific start freq and end freq when displaying in LOG mode the frequency axis (i.e. EMC testing case) ?
Eg. SSA3021X/X Plus 9Khz - 2.1 GHz or any frequency range between including a zero Hz sweep at any frequency within the model's range.
X and X Plus EMI modes are very different, X Plus have a selection of EMI measurement ranges that you select and use to measure within bands.
3kX I'm sorry I don't have anymore so can't advise in any detail other than what you can find in the manuals and App notes and such on the US and EU websites.
Some info here applicable more to the SSA3kX UI than the later EMI UI in X Plus models.:
https://siglentna.com/application-note/electromagnetic-compliance-pre-compliance-conducted-emissions-testing/
Yes.Sorry I should have mentioned, my question was about the SSA3kX not the Plus.Which model series ?The full BW of the model.Is it possible to choose specific start freq and end freq when displaying in LOG mode the frequency axis (i.e. EMC testing case) ?
Eg. SSA3021X/X Plus 9Khz - 2.1 GHz or any frequency range between including a zero Hz sweep at any frequency within the model's range.
X and X Plus EMI modes are very different, X Plus have a selection of EMI measurement ranges that you select and use to measure within bands.
3kX I'm sorry I don't have anymore so can't advise in any detail other than what you can find in the manuals and App notes and such on the US and EU websites.
Some info here applicable more to the SSA3kX UI than the later EMI UI in X Plus models.:
https://siglentna.com/application-note/electromagnetic-compliance-pre-compliance-conducted-emissions-testing/
On a side note, I'm asking my previous question because it was still unanswered by Siglent representative in France plus the datasheet is very vague.
See first screenshot in the App note linked above. This is from EMI mode in a SSA3000X, not Plus.Many thanks, now it is clear because when asked in France, they only said possible from this datasheet https://www.limpulsion.fr/upload/docs/SSA3000X.PDF (https://www.limpulsion.fr/upload/docs/SSA3000X.PDF) by looking at the section
See first screenshot in the App note linked above. This is from EMI mode in a SSA3000X, not Plus.Many thanks, now it is clear because when asked in France, they only said possible from this datasheet https://www.limpulsion.fr/upload/docs/SSA3000X.PDF (https://www.limpulsion.fr/upload/docs/SSA3000X.PDF) by looking at the section
where that version of datasheet states did not state clearly possible to set any start and stop freq while in LOG freq scale.
Thank you again for this clarification, Albert
As with linear freq scale also with Log freq scale you can free adjust start and stop frequencies. You set start and stop freq or center and span just as you need/want.
Naturally not absolutely free. Start < (stop - minimum span). If I remember right minimum span is 100Hz.
And this is independent of if you then use EMI filters or normal and independent of what detector you use (often with EMC measurements we want use Quasi-Peak detector).
One limit is. Linear freq scale minimum normal gaussian RBW filter is 1Hz and maximum is 1MHz. Log freq scale minimum RBW is 30Hz. (1) (not normaly used at all with EMC measurements.)
In this (3000X) model available (EMI) filters are 200Hz, 9kHz and 120kHz.
Log freq scale is of course not limited to use only with EMI filters. With all start/stop/span freq combinations can use Lin or Log freq scale. (limit (1))
As with linear freq scale also with Log freq scale you can free adjust start and stop frequencies. You set start and stop freq or center and span just as you need/want.
Naturally not absolutely free. Start < (stop - minimum span). If I remember right minimum span is 100Hz.
And this is independent of if you then use EMI filters or normal and independent of what detector you use (often with EMC measurements we want use Quasi-Peak detector).
One limit is. Linear freq scale minimum normal gaussian RBW filter is 1Hz and maximum is 1MHz. Log freq scale minimum RBW is 30Hz. (1) (not normaly used at all with EMC measurements.)
In this (3000X) model available (EMI) filters are 200Hz, 9kHz and 120kHz.
Log freq scale is of course not limited to use only with EMI filters. With all start/stop/span freq combinations can use Lin or Log freq scale. (limit (1))
Does the SA3000X has inside programmed or stored the different limits (EN 55011 EN 55014 EN 55015...) or do we need to enter them by hand ?
Is this normal or did I not understand something?
Hi Guys,
I have a SSA3032X+ which I converted to a SVA3032X.
System Info lists it a "SVA1032X", and firmware is 3.2.2.4.0.r2
Everything appears to work just fine.
Now I am trying to upgrade to the latest firmware for the SVA.
I see these options:
SVA1000X Firmware-V3.2.2.5.0 (Release Date 12.03.21 )
SVA1032X Firmware – V3.2.2.4.0 (Release Date 01.20.21 )
What is the difference between "SVA1000X" and "SVA1032X" ?
I obviously want "SVA1000X Firmware-V3.2.2.5.0", but each time I try, it somehow aborts the update.
What am I doing wrong ?
Many Thanks !
luudee
Least from official Siglent Europa area side it can download (whole package with release notes and instructions).
https://www.siglenteu.com/download/11716/ (https://www.siglenteu.com/download/11716/)
and release notes (pdf):
https://www.siglenteu.com/download/11719/ (https://www.siglenteu.com/download/11719/)
Hi Guys,
I have a SSA3032X+ which I converted to a SVA3032X.
System Info lists it a "SVA1032X", and firmware is 3.2.2.4.0.r2
Everything appears to work just fine.
Now I am trying to upgrade to the latest firmware for the SVA.
I see these options:
SVA1000X Firmware-V3.2.2.5.0 (Release Date 12.03.21 )
SVA1032X Firmware – V3.2.2.4.0 (Release Date 01.20.21 )
What is the difference between "SVA1000X" and "SVA1032X" ?
I obviously want "SVA1000X Firmware-V3.2.2.5.0", but each time I try, it somehow aborts the update.
What am I doing wrong ?
Many Thanks !
luudee
Least from official Siglent Europa area side it can download (whole package with release notes and instructions).
https://www.siglenteu.com/download/11716/ (https://www.siglenteu.com/download/11716/)
and release notes (pdf):
https://www.siglenteu.com/download/11719/ (https://www.siglenteu.com/download/11719/)
Yes, I know that, my questions are:
1. What is the difference between "SVA1000X" and "SVA1032X" ? Which one should I use ?
2. Why do my update attempts not complete ?
(It sits there for a few minutes with the rotating hour glass, then gets back the Update Menu".
luudee
Sorry, first (too fast) read I think you can not download... sorry.
Btw, why you have 3.2.2.4.0.r2 (it must not be problem but still I ask...) and not 3.2.2.4.0
Because r2 was just for only: " Fixed the VNA option license error on some SVA1015 and SVA1075 units "
And you do not have 1015 or 1075.
Does the digital modulation analysis work after the upgrade?YES :-+
- Is the procedure 100% reversible?
Has anyone done it, AFAIK? No because there was no need.
Leaves some residues in the filesystem? Most probably.
I have since reconverted it and restored the serial number and it's working fine as an SVA1032X.
Hello, can you please share how you restored your serial with keeping the conversion to an SVA1032x including all options enabled.
What does it make more to change from SSA 3000 to SVA 1000?
On the VNA part, I had hoped to have more than 751 points, but it is not the case.
Is this number of points limited by the firmware version 3.2.2.4.0.r2 or is there a trick to go beyond 751 points?
I launched SVA1000X_V3.2.2.5.0.ADS but after a long time the device did not restart and therefore did not install the Update... :-BROKE
After 6 months, finally decided to try SVA1000X_V3.2.2.5.0.ADS on an updated SSA3021X+ that System Info said was SVA1032X, 3.2.2.4.0.r2Yes 5 r8 is the latest version although there is no mention of r8 in any of the documentation, only the V5.
Everything went fine, cal files still work, 10,001 points on VNA, etc. Only curious thing I haven't seen posted is the sw1 reports as: 3.2.2.5.0.r8 , don't remember others having the r8?
The update took < 2 minutes and rebooted 2 or 3 times. Seemed to work correctly without another manual restart but I did one anyway after a little tinkering.
Perhaps the thumb drive used makes a difference on success. I used an old 256M fat16 drive. The drive had 75 other files and folders so it doesn't need to be empty.
Wouldn't the SSA3000X-R firmware be a closer fit to upgrade to?One must be very careful as there are 3 HW versions in the SSA X Plus and SVA ranges, >1.5, >3.2 and 3.2 > 7.5 GHz
It also has VNA. (although I assume too slow for any real time tasks)Yes X-R does have VNA, exactly the same as SVA1000X models and the RTSA can be tuned for a bunch of different analysis.
Wouldn't the SSA3000X-R firmware be a closer fit to upgrade to?
It also has VNA. (although I assume too slow for any real time tasks)
Not sure if this one deserves a new post so I'll just post here and see what happens: I feel rather dumb but somehow in the process of playing with the newly acquired SSA3021X Plus, I managed to introduce a 15dB amplitude offset which I cannot seem to get rid of. I feed a 0dBm signal from a trusty old 8656B siggen (whose amplitude I can verify on another HP SA) and I constantly get 15dB of attenuation on the Siglent SA reading. Not sure whether I encountered a bug or not. I know for a fact that it used to work correctly and all I did was to play with demodulation analyzer.Hit Preset and set it all up again but this time hit Save then Enter with a USB stick fitted and post the image here but be sure to have the Amplitude menu showing.
Can anyone lend a hand, please?
Thank you!
Hi Tautech and thank you for your reply. Here's the screenshot taken from vnc: https://imgur.com/a/qewpEmUHmmm, okay before I get my SVA1032X out can you instead use your SSA TG with a 0dB output to see where levels actually are ?
it don't seem right indeed. Here's the TG view using the same cable: https://imgur.com/a/sCTmziZ (https://imgur.com/a/sCTmziZ)Maybe somehow you have damaged the RF input.
it don't seem right indeed. Here's the TG view using the same cable: https://imgur.com/a/sCTmziZScreenshot from SVA1032X, full sweep TG @ -20dB
Thank you, @tautech,No chance unless you can find someone that's reverse engineered it.
It seems likely that I have blown one of the RF input switches acoording to the video in the thread you linked. Is there by any chance a way to get a hold of the hw schematics? I would need to know what chips to change.
Thank you!
I found a nice easter egg while looking at the firmware.
And while we're at it, I was considering adding some protection diodes on the input when changing the switch. Does anyone have an idea on what the part the footprints are there for?
>Sorry to hear that oz2cpu, I feel your pain.
Thanks a lot mate.. yes i was actually so mad, and sad, it took me 2hrs to fall a sleep yesterday,
mostly on my self, for beeing so mega stupid.. i knew this SSA input was a weak spot, i knew how to protect against it,
and i knew how to minimize the risks, yet did i ignore and forget all good known tricks..
now it is 11 and i just got up..
>Any idea on how it happened?
YES i know EXACTLY what happened, in fact i got a VIDEO of me blowing up the front end !!
======snipped interesting tale of woe=============
please remember : the more clever and smart you think you are..
the higher risk to forget even the most simple things,
always : go slow.. do all things right, you know how, you know what to do.
here is part 1 of my SSA3021X front end repair video
https://youtu.be/geoafvnSW3Q
>I found a nice easter egg while looking at the firmware. If you open the Mode menu and type 7445368 on the numeric keypadX or X Plus ?
Dont work on normal SSA software ??
i just tried, nothing..
>X or X Plus ?Only SVA and SSA X Plus models it seems carry eggs:
SSA3021X no plus written on the front here
and no easter egg,
if I click MODE and start typing, it thinks i want to dB something
here is part 2 of the videoThank you for the video, but... don't you think the unit would need recalibration after dismounting, changing the switch and remounting? I wouldn't bet it is still inside specifications.
https://youtu.be/zQ1lPbTwKaU
i dont use it for any kinds of certification measurements, so a db more or less, here or there, i care not..The PV tests start on P14 of the service manual:
but check the specs of the switch i changed, it is very small dB it can vary in its insertion loss
the alu shields and pcb, are made so it will be very close to same location, so.. i am happy as it is.
The alternative is to take it back to work, and compare its measurements to another one, with a brand new call sheet,
I got access to that in a few month, so of course i try that.
Does anyone already have experience with cross-flashing a factory fresh SSA3021X+ which has newest FW V3.2.2.5.0?
a bit of solder fell on the switch output microstrip
a bit of solder fell on the switch output microstrip
as most of the RF-current is flowing on the copper line in the dielectric medium - on the underside of the micro-stripline - the effect of a bit of tin on the upper side should not be that large.
as reference : https://incompliancemag.com/article/pcb-return-current-distribution-in-a-microstrip-line/
cheerio
Juergen
I also made these measurements, perhaps they provide more insight: https://docs.google.com/spreadsheets/d/18hqW8TiC1fAGkZ6ko35K19osOYpmgXjIjTDdKNzEp_w/edit?usp=sharing
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.
New firmware for SSA3000X Plus models is available.
Version： V3.2.2.5.1R1
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
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.
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
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?
Have you read this topic?
https://www.eevblog.com/forum/testgear/hack-of-sigllent-spectrum-analyzer-ssa3021x/ (https://www.eevblog.com/forum/testgear/hack-of-sigllent-spectrum-analyzer-ssa3021x/)
/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 #
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]
New firmware for SSA3000X Plus models is available.what's the .lic file for?
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
...
New firmware for SSA3000X Plus models is available.thanks, are there any negativ implications to modded SAs / VNAs in Pro mode ?
Version： V3.2.2.5.1R1
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
/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 #
.lic file should be license files.The release note said it's adding .lic auto scan. Whats that mean for us?
last_config.xml is indeed strange... Can you share it?
Do you have your SSA properly licensed or with S/N "XXXXXXXXX"?
/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
/usr/bin/siglent/usr/config # 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 20852 9536 69% /usr/bin/siglent
ubi2_0 5848 192 5656 3% /usr/bin/siglent/firmdata0
ubi3_0 5848 24 5824 0% /usr/bin/siglent/log
ubi0_0 84752 7692 77060 9% /usr/bin/siglent/usr
/usr/bin/siglent/usr/config #
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 148 5700 3% /usr/bin/siglent/firmdata0
ubi3_0 5848 24 5824 0% /usr/bin/siglent/log
ubi0_0 84752 8460 76292 10% /usr/bin/siglent/usr
We'll, I am bit more savvy on x86, but I took a swing at ARM debugging and figured out the differences needed to make the previous Python KG work with some modifications. :-+ Note that this code is only tested on an SVA1015X, and I had to use model 'SVA1000X' per what was listed in memory during key entry. All trial features are permanently unlocked and the serial # remains.
a little changed version with the ability to run the code:
If someone has SSA3000X Plus version (without SVA conversion), you can check if this code change works:
Model = 'SSA3000X+'
'SSA3000X_Plus' ;)
'SSA3000X_Plus' ;)
No more time to hand in homework...
To close things off:
"SSA3000X", "SSA3000X_Plus", "SVA1000X", "SSA3000R"
I have been chasing the option codes for the SSA3000X_Plus
Ha, I changed the model to SVA1000X in the python script and it accepted the options. I guess I have a crossflashed unit now, lol. Just the Model number is incorrect. If I remember right, I can change that in a config file. From what I read (or think I did), the model would have updated on its own.
<?xml version="1.0" encoding="UTF-8"?>
<nsp_trends_info_root>
<device>
<language>english</language>
<pid>0x1301</pid>
<vid>0xf4ec</vid>
<product_type_1>SVA1032X</product_type_1>
<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>
I wanted to analyse small band Frequency modulation - 144 MHz FM .
But the lowest deviation I can adjust in the analog demod mode is 60khz - which is a bit (much) too much. Any idea how to accomplish lower bandwidth? Has somebody raised this issue before - is Siglent planning to change their firmware.
I am sorry to tell you that BW is limited to <10MHz in MA mode for the SVA/SSA3000X+
So, modern digital communication modulation with 20-80MHz BW is way out of reach for this unit
Furthermore, you even cannot store any decoded data stream into a file for post analysis.
the demodulation function is a joke ???
Furthermore, you even cannot store any decoded data stream into a file for post analysis.
It is more for playing around with HAM communication and looking at GSM/2G modulation. :-DD
You are absolutely right!
I am a beginner, this is my first analyzer, it is for hobby use, there is no way I will invest in expensive professional equipment.
I will be satisfied with this equipment which is exceptional for the price.
Thank you for your clarifications :-+
the demodulation function is a joke ???Furthermore, you even cannot store any decoded data stream into a file for post analysis.
It is more for playing around with HAM communication and looking at GSM/2G modulation. :-DD
you probably confuse the modulation analysis function with modulation decoding (demodulation).
In SSA you have modulation analysis and this feature has nothing to do with decoding. It is used for something else - for example, you can set up the RF amplifier so that it does not introduce nonlinear distortions affecting the modulations, etc.
For example, I suggest watching this video in which such an example of digital modulation analysis is discussed - and watching how the distorted RF amplifier behaves.
"TSP #159 - Siglent SVA1032X 3.2GHz Spectrum & Vector Network Analyzer Review, Teardown & Experiments" - The Signal Path (from the time of 44:20)
https://youtu.be/ToVJTKCyIU8?t=2660 (https://youtu.be/ToVJTKCyIU8?t=2660)
In general, I recommend this channel on YT, you can learn a lot of interesting things about measurements and learn about the equipment - in a pleasant form (without having to go into the literature - I know that reading books is a problem for many today)
The defined "ready-made modulations" (GSM/2G etc.) are only a help, so that you do not have to do it manually by setting.
If you want to analyze some faster modulations, you should choose RealTime spectrum analyzer (for example SSA3032X-R). Alternatively, you can buy professional equipment (e.g. some communication analyzer from R&S). What you expect is a specialized communication analyzer, not a universal spectrum analyzer (where such options are only often a limited addition).
If you want to analyze TV, you can use devices such as the R&S ETL TV analyzer or the compact R&S ETC TV analyzer.
https://www.rohde-schwarz.com/pl/products/test-i-pomiaru/analizatory-transmycji/rs-etl-tv-analyzer_63493-9255.html (https://www.rohde-schwarz.com/pl/products/test-i-pomiaru/analizatory-transmycji/rs-etl-tv-analyzer_63493-9255.html)
https://www.rohde-schwarz.com/pl/products/test-i-pomiaru/analizatory-transmycji/rs-etc-compact-tv-analyzer_63493-12060.html (https://www.rohde-schwarz.com/pl/products/test-i-pomiaru/analizatory-transmycji/rs-etc-compact-tv-analyzer_63493-12060.html)
There are also specialized analyzers to work in GSM/UMTS/ LTE networks. Unfortunately, it is not the case that when you buy one of the cheaper universal spectrum analyzers on the market, you get the possibilities of specialized communication analyzers. It's a bit like after buying a Victorinox pocket knife you complain that you can't unscrew the wheel on a truck with it.
So I suggest that you first read a little bit about analyzers, their uses, etc, before you start determining what's wrong and what's right. Unfortunately, the lack of knowledge later causes such disappointments.
I also do not recommend using the factory mode. This mode does not guarantee that the spectrum analyzer is fully operational. It is known that there are some bugs with VNA. However, no one knows 100% if similar problems occur in other functions of the spectrum analyzer. Especially that now the publicly available method allows you to expand the capabilities of the device - without having to turn on the factory mode.
Demodulation and decoding is part of digital modulation analysis.
I think, there is no confusion... and nobody judges here if something is wrong or right... :scared:
Anyway, the statistic Trace with decoding samples in MA mode is somewhat useless, if no recording and saving is available.
And everybody likes the "pay one get three", right? :-DD
Demodulation and decoding is part of digital modulation analysis.
I think, there is no confusion... and nobody judges here if something is wrong or right... :scared:
Anyway, the statistic Trace with decoding samples in MA mode is somewhat useless, if no recording and saving is available.
And everybody likes the "pay one get three", right? :-DD
Nonsense, show a universal spectrum analyzer even much more expensive which has such a recording option...
In SSA+/SVA you have all the modulation information you need and the filters you need for analysis. One disadvantage is the high CPU load and the GUI response slower with a larger sample buffer - as shown in the video.
You just need to know how to use it - really no decoded data analysis is needed for modulation analysis (these are useful for communication protocol analysis etc.).
The limitation is the number of symbols per second which results from the fact that it is not an RT spectrum analyzer (therefore it has limited bandwidth). Even if it had more bandwidth, you still have a problem with timeslots used on e.g. cellular networks, so this decoded data would be useless. On the other hand, I have shown that the SSA+/SVA can modulation analyze both one UMTS variant and three LTE variants.
If you want to decode data cheaply, I suggest you buy some SDR like USRP. I use my own USRP to decode data on all types of cellular networks. However, the USRP, due to its inferior RF path, is less suitable for modulation analysis.
For consolation, I will add that in the equipment (R&S FSWP) in the pictures (photos of measurements of the amateur DMR repeater made last year) I also do not have such an option (Capability to record decoded data) :scared:
All fine my friend, no need to get upset :box:
We are all here to learn from each other... thank you for your lessons :-+
I tried to decode this is what it gives
For 2G we will say that it is OK
For 3G even though the bandwidth is 4 MHz it doesn't seem to decode anything.
mount -o remount,rw /usr/bin/siglent/firmdata0
cd /usr/bin/siglent/firmdata0
mv nsp_data_b1x nsp_data_b1
cd /usr/bin/siglent/usr/backup
mv nsp_data_bx nsp_data_b
sync && reboot
Summarizing the collected information :)
Script to run:
https://www.online-python.com/PX3v0J8nbs (https://www.online-python.com/PX3v0J8nbs)
Is there a way to cross flash a 3000x+ with firmware V3.2.2.5.1R1? I might have jumped the gun a bit by updating all the way to the newest version. If I try to go back to the V3.2.2.5.0 release with the tv84 hex mod, it just says "Update Failed!" after attempting to cross flash.
If he take this options everything is fine.
Is there a way to cross flash a 3000x+ with firmware V3.2.2.5.1R1? I might have jumped the gun a bit by updating all the way to the newest version. If I try to go back to the V3.2.2.5.0 release with the tv84 hex mod, it just says "Update Failed!" after attempting to cross flash.
Are you saying that you did a downgrade to SSAX+ V3.2.2.5.0 and then a crossflash (with the "hex mod") and it failed? If so, that is interesting. If not, first do the downgrade.
You need to check what your current ID is. You can do that using telnet. On the SSA-XP models, there is a SCPI command to activate telnet if I remember correctly. Also, you can edit and change the ID (described in the initial crossgrade instructions).
I guess there is no change from Prod_ID in V3.2.2.5.0 to V3.2.2.5.1R1. Maybe Siglent is stopping people from upgrading by checking FW version...
If I'm in the mood, I'll create a "hex mod" for V3.2.2.5.1R1.
<?xml version="1.0" encoding="UTF-8"?>^M
<nsp_upgrade_info_root>^M
<device>^M
<upgrade_static_id>11411</upgrade_static_id>^M
<upgrade_start_id>11400</upgrade_start_id>^M
<upgrade_end_id>11499</upgrade_end_id>^M
</device>^M
</nsp_upgrade_info_root> ^M
^M
If I'm in the mood, I'll create a "hex mod" for V3.2.2.5.1R1.
<?xml version="1.0" encoding="UTF-8"?>
<nsp_trends_info_root>
<device>
<language>english</language>
<pid>0x1301</pid>
<vid>0xf4ec</vid>
<product_type_1>SVA1032X</product_type_1>
<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>2) edit /usr/bin/siglent/config/NSP_config_upgrade_info.xml to change ProductID:
replace
<upgrade_static_id>11411</upgrade_static_id>
with
<upgrade_static_id>11403</upgrade_static_id>
Wrong move. BTW, move to the hack thread.
Weird.No more time to hand in homework...
To close things off:
"SSA3000X", "SSA3000X_Plus", "SVA1000X", "SSA3000R"
Summarizing the collected information :)
Script to run:
https://www.online-python.com/PX3v0J8nbs (https://www.online-python.com/PX3v0J8nbs)
And added to the attachment (as if the links stopped working).
Weird.No more time to hand in homework...
To close things off:
"SSA3000X", "SSA3000X_Plus", "SVA1000X", "SSA3000R"
Summarizing the collected information :)
Script to run:
https://www.online-python.com/PX3v0J8nbs (https://www.online-python.com/PX3v0J8nbs)
And added to the attachment (as if the links stopped working).
On sds3021x (non plus) with factory-enabled tg only EMI and 3032 options worked. AMK and REFL are rejected...
Any idea?
tcpsvd -vE 0.0.0.0 21 ftpd /Also before this I changed root password to connect via ftp.21 stream tcp nowait root ftpd ftpd /But it is located in cramps file system and therefore read-only. :(tcpsvd -vE 0.0.0.0 21 ftpd / -w & to startup_app.sh after telnet line solved problem.Quote from: tomud on August 13, 2022, 10:59:43 am
Quote from: tv84 on August 13, 2022, 10:11:42 am
No more time to hand in homework...
To close things off:
"SSA3000X", "SSA3000X_Plus", "SVA1000X", "SSA3000R"
Summarizing the collected information :)
Script to run:
https://www.online-python.com/PX3v0J8nbs (https://www.online-python.com/PX3v0J8nbs)
And added to the attachment (as if the links stopped working).
Weird.
On sds3021x (non plus) with factory-enabled tg only EMI and 3032 options worked. AMK and REFL are rejected...
Any idea?
Jepp, the mistake he made was the option.
# Options:
# CAT = AMK
# Meas = Refl
For AMK he must use CAT as an option also for Refl he must use Meas as an Option.
If he take this options everything is fine.
regards Chris
otheropt = ('AMK', 'EMI', 'TG', 'Refl', 'DMA', 'AMA', 'WDMA', 'DTF', 'VNA', 'RT40', '3021', '3032', '3050', '3075', 'ALL', 'Meas', 'CAT', '1HZ', '3M')Of course "Meas" and "CAT" was used (with success).Hi. I did it.
But the system messages says that the key is invalid with CAT or AMK.
With Meas, the system inmediatly says that key is invalid and I can't continue.
So, I tought that I was doing wrong. But the script worked fine with BW.
I have SSA 3021X, it came with FW 2.1.1.1
Maybe the problem is that I updated the FW.
Regards
Jipo
Do you have any official option license inserted?
But I was unable to know if others key are valid. I belive that they are valid since first time, even without aliases.All/any license key is only valid to one instrument and all/any option license status is displayed in the Sys Info as Permanent or trial time remaining in minutes.
At this moment, all options work. I don't know if it is because the licence's time is running yet, or the permanent key is valid.
All/any license key is only valid to one instrument and all/any option license status is displayed in the Sys Info as Permanent or trial time remaining in minutes.
The status of every license is plain to see.
Hello,IIRC SWR is an optional measurement in SSA3000X Plus models and yes it requires the bridge whereas in VNA mode in a SVA1000X SWR no bridge is required and has a dedicated chart that you can assign a trace to and have several traces on one chart, each of which is a different measurement.
Quick question about SWR measurements, if I may.
Thinking of buying an SSA300X Plus.
I see from the manual for the SAA3000x Plus that you need a directional bridge to complete SWR measurements. Then I realised that if you have VNA functionality providing a complex impedance, you can work out the SWR from this (relative to 50 Ohms resistive).
If I've read the manual correctly, in VNA mode SWR is a menu option.
Not being able to flash firmware (up or down) "Upgrade Fails."Welcome to the forum.
I got a new SSA3021X+ and I it's running V3.2.2.5.0 but I can't seem to flash the firmware up to the latest (V3.2.2.5.1R1) or down to the previous. Anyone have any suggestions on things to try?
Not being able to flash firmware (up or down) "Upgrade Fails."Welcome to the forum.
I got a new SSA3021X+ and I it's running V3.2.2.5.0 but I can't seem to flash the firmware up to the latest (V3.2.2.5.1R1) or down to the previous. Anyone have any suggestions on things to try?
Incorrectly formatted or too large USB stick ?
Needs to be 8GB max and formatted in FAT32 with 4k clusters.
It's safe to assume all Siglent instruments however TBH I have yet to investigate their limits and would need a larger selection of USB sticks in order to do so.Not being able to flash firmware (up or down) "Upgrade Fails."Welcome to the forum.
I got a new SSA3021X+ and I it's running V3.2.2.5.0 but I can't seem to flash the firmware up to the latest (V3.2.2.5.1R1) or down to the previous. Anyone have any suggestions on things to try?
Incorrectly formatted or too large USB stick ?
Needs to be 8GB max and formatted in FAT32 with 4k clusters.
The USB stick max size of 8GB apply to the 3021x (non-Plus) version as well? I would think it does but want to be sure.
Thanks
Mike
Did anyone find a solution to enabling individual options on the SSA2031X Plus?
The hack below allowed users to enable specific options, and keep the serial number, but Siglent closed the door on this with a new firmware that didn't allow reverting to an older firmware.
https://www.eevblog.com/forum/testgear/hack-of-sigllent-spectrum-analyzer-ssa3021x/msg998095/#msg998095 (https://www.eevblog.com/forum/testgear/hack-of-sigllent-spectrum-analyzer-ssa3021x/msg998095/#msg998095)
Telnet was closed down as well, but a modified ads file can restore it with appropriate commands.
Having read 80+ pages of this thread, it looks like the only hack left is one that enables all options and removes the serial number. Is that a fair assessment of the current status?
Thanks.
SSA3000X Plus models have a price reduction for the rest of 2022:
SSA3015X Plus Save $260
SSA3021X Plus Save $296
SSA3032X Plus Save $496
https://int.siglent.com/info/detail-64.html (https://int.siglent.com/info/detail-64.html)
https://siglentna.com/news-article/save-up-to-591-get-sds1202x-e-sdg2000x-ssa3000x-plus-at-a-super-low-price/ (https://siglentna.com/news-article/save-up-to-591-get-sds1202x-e-sdg2000x-ssa3000x-plus-at-a-super-low-price/)
https://www.siglenteu.com/news-article/save-up-to-e340-get-sds1202x-e-ssa3000x-plus-at-a-super-low-price/ (https://www.siglenteu.com/news-article/save-up-to-e340-get-sds1202x-e-ssa3000x-plus-at-a-super-low-price/)
Hello everyone,
I am looking to purchase the SSA3032X Plus and I have searched around to know if it can be hacked and what options I can have unlocked, what I find seems to be mostly for the SSA3021. I think I also saw something on here a while back (cant seem to find it) about unlocking to a VNA up to 7Ghz... is that still possible?
Can you please let me know what version will be best to get (Christmas gift to myself) that has the most/best unlock capability? I appreciate any information I can get on this, thank you!
The question reminds me what car should I buy.
Volkswagen Beetle or Aston Martin ? What do you need ??
If you look at Tautechs Info, I would go for the SSA3021x plus - technical educated folks can modify it to behave as a native SVA 1032x (my knowledge today - by experience - no legal obligations)
Probably without talking about your needs, nobody will answer to your question, I would suggest a Ford Mach E - go for it !! :-+
The Siglent SSA3032X-R 3.2GHz Real Time spectrum analyzer is the base model you're thinking of. The 3050X-R and 3075X-R models are just pre 'liberated' 3032X-R versions. ::)
IOW, it'll cost you a lot more than an SSA3021X+ to upgrade to a 7.5GHz BW SSA. :(
SSA3015X - can be hacked to activate all options
SSA3021X - can be hacked to activate all options and increase bandwidth to 3.2GHz
SSA3021X-P - can be crossgraded to SVA1032 with all options and 3.2GHz bandwidth
SSA3032X-R - can be hacked to activate all options nd increase bandwidth to 7.5GHz
Conclusion:
- Don't bother to buy any of the xx15 models, they cannot be bandwidth upgraded (at least in the past, it seems they might now with the new HW platform)
- If you are a hobbyist, you wouldn't buy any SVA model, nor any xx32 (or greater) model, except you are in business for the SSA3032X-R.
I guess this summs up all options.
I am curious- can the SVA1032 be hacked to a SVA1075X?
I am curious- can the SVA1032 be hacked to a SVA1075X?
No, read his words carefully.
It's all there what's possible and what's not.
BTW, a -R will get you the VNA features. You don't need to buy an extra VNA.
Concerning a SSA3021X-P enhanced to SVA, do we need an external diectional coupler for the VNA function or the input stage is really the same as a SVA ?SVA in VNA mode is a single port VNA with its Stimulus originating from Port 1, the TG port behind which is the directional coupler to direct the reflection measurements (S11) and DUT through measurements (S21) enter the instrument in Port 2, the RF In port.
Hi all,
I just ordered the ssa3021x+ to replace my bricked DSA815 (no TG calibration anymore) and I'm collecting all the data needed to perform the full sva1032x migration.
I think that I have the picture complete except that there should be a way to install licenses the clean way with serial number. I also found a post mentioning script/tool that should do this but that one is removed. But later on that clean method is still mentioned as a viable option. Meanwhile I already have searched all these 84 pages a couple of times but I can't find it.
Do I look at the wrong places? Can anyone give a short hint?
Thanks!
I think the Crossgrade might be unnecessary now that the keygen is public...
Hello, I have two questions regarding the SSA3000
The first is general, I am used to using tv analyzers and they all bring spectrum analyzers. Normally the noise floor is usually around 20db. Nowadays almost all the signals are digital, for example, a COFDM signal With 8mhz of bandwidth, that type of signal, in a spectrum analyzer like the one that television analyzers bring, would logically begin to be seen from 20db. The question would be: From what lower level would you start? know that there is such a signal in an SSA3000? We could add the variable of the amplifier but in any case it would be a question of knowing what advantage in terms of weak signals an SSA3000 has over a spectrum analyzer of a normal TV analyzer.
The second question would be to know the dynamic range of these analyzers
Best Regards
HelloThere is the functionality for the screen to go into power saving mode.
Can someone tell me how to reduce the brightness of the display on SSA 3021XP?
There is a grid only brightness setting.
Hello, I have two questions regarding the SSA3000Refer to P10 of the datasheet:
The first is general, I am used to using tv analyzers and they all bring spectrum analyzers. Normally the noise floor is usually around 20db. Nowadays almost all the signals are digital, for example, a COFDM signal With 8mhz of bandwidth, that type of signal, in a spectrum analyzer like the one that television analyzers bring, would logically begin to be seen from 20db. The question would be: From what lower level would you start to know that there is such a signal in an SSA3000? We could add the variable of the amplifier but in any case it would be a question of knowing what advantage in terms of weak signals an SSA3000 has over a spectrum analyzer of a normal TV analyzer.
The second question would be to know the dynamic range of these analyzers
Best Regards
Hello, I have a question about EMI module.Can I offer some guidance from the NA website, EU should have these too but I didn't look.
I'm struggling for hours now to load those predefined limits but nothing is shown. Is this still under construction?
Also, when I'm going to menu meter1->limit and turn this on the e.g. "limit1 to value" is enabled but pressing it throws an error "unknown error!".
ssa3032x-r with latest firmware
update:
Those limit files are useless. I think that those files are for other machines, they are way off. If I put a ref offset of 50db I get some limits insight. 167db(uv) where it should be in the 80 db(uv) range.
FCC files are not visible at all.
Limit
"EN 55022, Conducted, Class A"
"Average Detector"
,
,01
Type, Upper
X Axis Unit, MHz
Amplitude Unit, dBuV
Frequency Interpolation, Logarithmic
Amplitude Interpolation, Logarithmic
X Control, Fixed
Y Control, Fixed
Margin, 0
X Offset, 0
Y Offset, 0
DATA
0.150000,66.00
0.500000,66.00
0.500000,60.00
30.00000,60.00Editing the SVA FW in an hex editor serves the purpose of changing the ID so that an SSA will accept it.
Changing the ID on the device is not necessary. If you do that you need to use the original SVA FW.
Doing both is reversing the mismatch and means you don't know what you are doing. Take a couple of hours and read through the relevant posts before bricking your device.
Limit
"Test"
"Average Detector"
,
,01
Type, Upper
X Axis Unit, MHz
Amplitude Unit, dBuv
Frequency Interpolation, Logarithmic
Amplitude Interpolation, Logarithmic
X Control, Fixed
Y Control, Fixed
Margin, 0
X Offset, 0
Y Offset, 0
DATA
0.150000,-10.00
0.500000, 0.00
0.500000, 10.00
30.00000, 20.00
Hi Sully
I understand from your odyssey that it was enough to simply modify the SVA1000X_V3.2.2.5.1R1.ADS file with the hex editor as per the TV84 instructions and flash the device.
If so, the ADS file will have to be modified for each new SVA update.
I wonder, since we have no ID change (remains original for SSA) will we be able to reflash the device with SSA firmware if we wanted to??
If so, the ADS file will have to be modified for each new SVA update.
I wonder, since we have no ID change (remains original for SSA) will we be able to reflash the device with SSA firmware if we wanted to??
My SSA3021X Plus purchased in December 2022 has firmware 3.2.2.5.1R20. This firmware is not yet available on SIGLENT....
Watch out, Siglent may be using a new HW platform, incompatible with existing FW releases. You should make sure you know what you are doing, because you might brick your device if that is indeed the case.
This happened with the non plus model.
Mine came as well with 3.2.2.5.1R20.
Therefore no cross-flash until release on the web.
Until then -> python gen to 3.2GHz + All options
Python @ #1968
@TV84
Can hex prod_id be found via sva*.ads and ssa*.ads hex compare? Or you need to unpack ADS file?
I would love to upgrade to the SSA3015x plus but only if it was possible for me to upgrade it. As a computer illiterate person not even knowing what telnet is what would my odds be of performing this upgrade.
I would mostly like to open up all the options.why are you not using the online Python script ?
To fix this, it was necessary to copy those 2 files na_1p + na_2p to /usr/bin/siglent/firmdata0/caliNow I have permission issue to firmdata0/cali " Read-only file system"
No more time to hand in homework...
To close things off:
"SSA3000X", "SSA3000X_Plus", "SVA1000X", "SSA3000R"
Summarizing the collected information :)
Script to run:
https://www.online-python.com/PX3v0J8nbs (https://www.online-python.com/PX3v0J8nbs)
And added to the attachment (as if the links stopped working).
No more time to hand in homework...
To close things off:
"SSA3000X", "SSA3000X_Plus", "SVA1000X", "SSA3000R"
Summarizing the collected information :)
Script to run:
https://www.online-python.com/PX3v0J8nbs (https://www.online-python.com/PX3v0J8nbs)
And added to the attachment (as if the links stopped working).
I used this (excellent!) script to enhance my aging SSA 3021X (non-Plus).
Analyzer data:
SW1: 1.3.9.8
SW2: 20201230-1
SW3: 000000D1
HW: 07.03.00
Bought with TG included permanently and 48 hours of trial for the other options (expired now).
I uncommented Model = 'SSA3000X' and filled in HOSTID as instructed, ran the script and got a list of license keys for all options. Plain and simple :)
But I am only able to activate options 3032 and EMI, even though that is great in itself.
I don't understand why AMK and Refl won't activate. I get an "Invalid License!" message on the screen when entering the license key for these.
The order of activating licenses is irrelevant, right? I think we're supposed to be able to buy these and activate at any time?
In hindsight I realize I should have activated 3032 and then ALL, but I find it hard to believe this is essential.
Any pointers or suggestions are welcome!
No more time to hand in homework...
To close things off:
"SSA3000X", "SSA3000X_Plus", "SVA1000X", "SSA3000R"
Summarizing the collected information :)
Script to run:
https://www.online-python.com/PX3v0J8nbs (https://www.online-python.com/PX3v0J8nbs)
And added to the attachment (as if the links stopped working).
I used this (excellent!) script to enhance my aging SSA 3021X (non-Plus).
Analyzer data:
SW1: 1.3.9.8
SW2: 20201230-1
SW3: 000000D1
HW: 07.03.00
Bought with TG included permanently and 48 hours of trial for the other options (expired now).
I uncommented Model = 'SSA3000X' and filled in HOSTID as instructed, ran the script and got a list of license keys for all options. Plain and simple :)
But I am only able to activate options 3032 and EMI, even though that is great in itself.
I don't understand why AMK and Refl won't activate. I get an "Invalid License!" message on the screen when entering the license key for these.
The order of activating licenses is irrelevant, right? I think we're supposed to be able to buy these and activate at any time?
In hindsight I realize I should have activated 3032 and then ALL, but I find it hard to believe this is essential.
Any pointers or suggestions are welcome!
otheropt = ('AMK', 'EMI', 'TG', 'Refl', 'DMA', 'AMA', 'WDMA', 'DTF', 'VNA', 'RT40', '3021', '3032', '3050', '3075', 'ALL', 'Meas', 'CAT')And now I have all options unlocked and full 3.2GHz bandwidth 8)as in reply #2007?
/usr/bin/siglent # ps
PID USER TIME COMMAND
1 root 0:00 {linuxrc} init
2 root 0:00 [kthreadd]
3 root 0:00 [ksoftirqd/0]
5 root 0:00 [kworker/0:0H]
6 root 0:00 [kworker/u4:0]
7 root 0:00 [rcu_preempt]
8 root 0:00 [rcu_sched]
9 root 0:00 [rcu_bh]
10 root 0:00 [migration/0]
11 root 0:00 [migration/1]
12 root 0:00 [ksoftirqd/1]
13 root 0:00 [kworker/1:0]
14 root 0:00 [kworker/1:0H]
15 root 0:00 [khelper]
16 root 0:00 [kdevtmpfs]
19 root 0:00 [perf]
56 root 0:01 [kworker/1:1]
202 root 0:00 [writeback]
205 root 0:00 [bioset]
207 root 0:00 [kblockd]
238 root 0:00 [edac-poller]
326 root 0:01 [kworker/0:1]
327 root 0:00 [rpciod]
341 root 0:00 [kswapd0]
342 root 0:00 [fsnotify_mark]
343 root 0:00 [nfsiod]
441 root 0:00 [spi0]
455 root 0:00 [spi1]
564 root 0:00 [irq/23-f8007100]
571 root 0:00 [deferwq]
574 root 0:00 [kworker/0:1H]
575 root 0:00 [kworker/1:1H]
582 root 0:00 [ubi_bgt1d]
586 root 0:00 [ubi_bgt2d]
590 root 0:00 [ubi_bgt3d]
594 root 0:00 [ubi_bgt0d]
597 root 0:00 [ubifs_bgt1_0]
600 root 0:00 [ubifs_bgt3_0]
602 root 0:00 [ubifs_bgt0_0]
648 root 0:00 [goodix_wq]
692 root 0:00 telnetd
716 root 0:00 [ci_otg]
730 root 0:00 [kworker/0:2]
739 root 0:00 /usr/bin/siglent/vsftpd
742 1 0:00 portmap
774 root 0:00 [kworker/u4:3]
882 root 0:00 /usr/bin/siglent/vncserver
887 root 0:00 /usr/sbin/lighttpd -f /usr/bin/siglent/lighttpd.conf
888 root 0:00 /usr/bin/php-cgi -c /usr/bin/siglent/php.ini
890 root 0:00 /sbin/getty -L ttyPS0 115200 vt100
894 root 0:00 /usr/bin/php-cgi -c /usr/bin/siglent/php.ini
895 root 0:00 -sh
897 root 0:00 ps
/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 20864 9524 69% /usr/bin/siglent
ubi2_0 5848 192 5656 3% /usr/bin/siglent/firmdata0
ubi3_0 5848 24 5824 0% /usr/bin/siglent/log
ubi0_0 84752 7784 76968 9% /usr/bin/siglent/usr
/usr/bin/siglent #
Hello
This afternoon we turned on the analyzer the curve was displayed but everything remained frozen... I turned it off and restarted it and since then it remains on a black screen with the logo Siglent to display :palm:
I still have access to the ssa3000 via ssh
What do you advise me to do?
SSA 3021 plus transformed into SVA1032 with all enabled options and the latest firmware.Code: [Select]/usr/bin/siglent # ps
PID USER TIME COMMAND
1 root 0:00 {linuxrc} init
2 root 0:00 [kthreadd]
3 root 0:00 [ksoftirqd/0]
5 root 0:00 [kworker/0:0H]
6 root 0:00 [kworker/u4:0]
7 root 0:00 [rcu_preempt]
8 root 0:00 [rcu_sched]
9 root 0:00 [rcu_bh]
10 root 0:00 [migration/0]
11 root 0:00 [migration/1]
12 root 0:00 [ksoftirqd/1]
13 root 0:00 [kworker/1:0]
14 root 0:00 [kworker/1:0H]
15 root 0:00 [khelper]
16 root 0:00 [kdevtmpfs]
19 root 0:00 [perf]
56 root 0:01 [kworker/1:1]
202 root 0:00 [writeback]
205 root 0:00 [bioset]
207 root 0:00 [kblockd]
238 root 0:00 [edac-poller]
326 root 0:01 [kworker/0:1]
327 root 0:00 [rpciod]
341 root 0:00 [kswapd0]
342 root 0:00 [fsnotify_mark]
343 root 0:00 [nfsiod]
441 root 0:00 [spi0]
455 root 0:00 [spi1]
564 root 0:00 [irq/23-f8007100]
571 root 0:00 [deferwq]
574 root 0:00 [kworker/0:1H]
575 root 0:00 [kworker/1:1H]
582 root 0:00 [ubi_bgt1d]
586 root 0:00 [ubi_bgt2d]
590 root 0:00 [ubi_bgt3d]
594 root 0:00 [ubi_bgt0d]
597 root 0:00 [ubifs_bgt1_0]
600 root 0:00 [ubifs_bgt3_0]
602 root 0:00 [ubifs_bgt0_0]
648 root 0:00 [goodix_wq]
692 root 0:00 telnetd
716 root 0:00 [ci_otg]
730 root 0:00 [kworker/0:2]
739 root 0:00 /usr/bin/siglent/vsftpd
742 1 0:00 portmap
774 root 0:00 [kworker/u4:3]
882 root 0:00 /usr/bin/siglent/vncserver
887 root 0:00 /usr/sbin/lighttpd -f /usr/bin/siglent/lighttpd.conf
888 root 0:00 /usr/bin/php-cgi -c /usr/bin/siglent/php.ini
890 root 0:00 /sbin/getty -L ttyPS0 115200 vt100
894 root 0:00 /usr/bin/php-cgi -c /usr/bin/siglent/php.ini
895 root 0:00 -sh
897 root 0:00 ps
/usr/bin/siglent # dmesg
[ 0.336218] TCP: reno registered
[ 0.336234] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.336264] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.336460] NET: Registered protocol family 1
[ 0.336805] RPC: Registered named UNIX socket transport module.
[ 0.336818] RPC: Registered udp transport module.
[ 0.336827] RPC: Registered tcp transport module.
[ 0.336836] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.336867] PCI: CLS 0 bytes, default 64
[ 0.337196] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[ 0.338540] futex hash table entries: 512 (order: 3, 32768 bytes)
[ 0.340126] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 0.341154] io scheduler noop registered
[ 0.341174] io scheduler deadline registered
[ 0.341231] io scheduler cfq registered (default)
[ 0.343272] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
[ 0.343360] dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[ 0.343828] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 145, base_baud = 2500000) is a xuartps
[ 0.917296] console [ttyPS0] enabled
[ 0.921446] xdevcfg f8007000.devcfg: ioremap 0xf8007000 to 4a878000
[ 0.928185] [drm] Initialized drm 1.1.0 20060810
[ 0.940673] brd: module loaded
[ 0.947643] loop: module loaded
[ 0.956927] libphy: MACB_mii_bus: probed
[ 1.043419] macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 149 (00:0a:35:00:01:23)
[ 1.053307] macb e000b000.ethernet eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:1e, irq=-1)
[ 1.064867] i2c /dev entries driver
[ 1.070148] rtc-ds1307 0-0068: rtc core: registered ds1340 as rtc0
[ 1.076593] cdns-i2c e0004000.i2c: 400 kHz mmio e0004000 irq 143
[ 1.083835] zynq-edac f8006000.memory-controller: ecc not enabled
[ 1.090051] Xilinx Zynq CpuIdle Driver started
[ 1.095137] ledtrig-cpu: registered to indicate activity on CPUs
[ 1.102140] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[ 1.108452] nand: Micron MT29F2G08ABAEAWP
[ 1.112430] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 1.120023] nand: WARNING: pl353-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
[ 1.131531] Bad block table found at page 131008, version 0x01
[ 1.137807] Bad block table found at page 130944, version 0x01
[ 1.143935] 12 ofpart partitions found on MTD device pl353-nand
[ 1.149785] Creating 12 MTD partitions on "pl353-nand":
[ 1.155041] 0x000000000000-0x000000780000 : "fsbl"
[ 1.160857] 0x000000780000-0x000000b80000 : "kerneldata"
[ 1.167142] 0x000000b80000-0x000000c00000 : "device-tree"
[ 1.173491] 0x000000c00000-0x000001100000 : "Manufacturedata"
[ 1.180156] 0x000001100000-0x000001600000 : "reserved1"
[ 1.186367] 0x000001600000-0x000003e00000 : "rootfs"
[ 1.192260] 0x000003e00000-0x000004800000 : "firmdata0"
[ 1.198384] 0x000004800000-0x000006c00000 : "siglent"
[ 1.204412] 0x000006c00000-0x00000d000000 : "datafs"
[ 1.210426] 0x00000d000000-0x00000da00000 : "log"
[ 1.216087] 0x00000da00000-0x00000f800000 : "upgrade_cramdisk"
[ 1.222900] 0x00000f800000-0x000010000000 : "reserved2"
[ 1.230968] TCP: cubic registered
[ 1.234458] NET: Registered protocol family 17
[ 1.239084] Registering SWP/SWPB emulation handler
[ 1.245704] rtc-ds1307 0-0068: setting system clock to 2023-01-10 08:53:07 UTC (1673340787)
[ 1.259101] cramfs_fill_nand blocks is 320-----------------------
[ 1.259101]
[ 1.259101]
[ 1.259101]
[ 1.272121] VFS: Mounted root (cramfs filesystem) readonly on device 31:5.
[ 1.279013] devtmpfs: mounted
[ 1.282156] Freeing unused kernel memory: 196K (40553000 - 40584000)
[ 1.554972] UBI-1: ubi_attach_mtd_dev:attaching mtd7 to ubi1
[ 1.703267] UBI-1: scan_all:scanning is finished
[ 1.714262] UBI-1 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 3, need 40
[ 1.725400] UBI-1: ubi_attach_mtd_dev:attached mtd7 (name "siglent", size 36 MiB)
[ 1.732818] UBI-1: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 1.741476] UBI-1: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 1.749975] UBI-1: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[ 1.758672] UBI-1: ubi_attach_mtd_dev:good PEBs: 288, bad PEBs: 0, corrupted PEBs: 0
[ 1.766427] UBI-1: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[ 1.775376] UBI-1: ubi_attach_mtd_dev:max/mean erase counter: 27/10, WL threshold: 4096, image sequence number: 1996219743
[ 1.786425] UBI-1: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 288, PEBs reserved for bad PEB handling: 3
[ 1.797314] UBI-1: ubi_thread:background thread "ubi_bgt1d" started, PID 582
[ 1.799673] UBI-2: ubi_attach_mtd_dev:attaching mtd6 to ubi2
[ 1.843974] UBI-2: scan_all:scanning is finished
[ 1.854764] UBI-2 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 9, need 40
[ 1.865756] UBI-2: ubi_attach_mtd_dev:attached mtd6 (name "firmdata0", size 10 MiB)
[ 1.873376] UBI-2: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 1.881961] UBI-2: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 1.890504] UBI-2: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[ 1.899203] UBI-2: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[ 1.906857] UBI-2: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[ 1.915819] UBI-2: ubi_attach_mtd_dev:max/mean erase counter: 158/101, WL threshold: 4096, image sequence number: 1168290863
[ 1.927041] UBI-2: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 80, PEBs reserved for bad PEB handling: 9
[ 1.937849] UBI-2: ubi_thread:background thread "ubi_bgt2d" started, PID 586
[ 1.944942] UBI-3: ubi_attach_mtd_dev:attaching mtd9 to ubi3
[ 1.990185] UBI-3: scan_all:scanning is finished
[ 2.000959] UBI-3 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 9, need 40
[ 2.011967] UBI-3: ubi_attach_mtd_dev:attached mtd9 (name "log", size 10 MiB)
[ 2.019099] UBI-3: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 2.027668] UBI-3: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 2.036189] UBI-3: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[ 2.044899] UBI-3: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[ 2.052534] UBI-3: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[ 2.061508] UBI-3: ubi_attach_mtd_dev:max/mean erase counter: 16/9, WL threshold: 4096, image sequence number: 479844541
[ 2.072388] UBI-3: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 80, PEBs reserved for bad PEB handling: 9
[ 2.083185] UBI-3: ubi_thread:background thread "ubi_bgt3d" started, PID 590
[ 2.085348] UBI-0: ubi_attach_mtd_dev:attaching mtd8 to ubi0
[ 2.485725] UBI-0: scan_all:scanning is finished
[ 2.497905] UBI-0: ubi_attach_mtd_dev:attached mtd8 (name "datafs", size 100 MiB)
[ 2.505374] UBI-0: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 2.513957] UBI-0: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 2.522464] UBI-0: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[ 2.531179] UBI-0: ubi_attach_mtd_dev:good PEBs: 800, bad PEBs: 0, corrupted PEBs: 0
[ 2.538933] UBI-0: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[ 2.547886] UBI-0: ubi_attach_mtd_dev:max/mean erase counter: 19/12, WL threshold: 4096, image sequence number: 1984375540
[ 2.558932] UBI-0: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 800, PEBs reserved for bad PEB handling: 40
[ 2.569907] UBI-0: ubi_thread:background thread "ubi_bgt0d" started, PID 594
[ 2.583511] UBIFS: background thread "ubifs_bgt1_0" started, PID 597
[ 2.615063] UBIFS: recovery needed
[ 2.686073] UBIFS: recovery completed
[ 2.689742] UBIFS: mounted UBI device 1, volume 0, name "siglent"
[ 2.695795] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 2.704917] UBIFS: FS size: 34410496 bytes (32 MiB, 271 LEBs), journal size 4952064 bytes (4 MiB, 39 LEBs)
[ 2.714577] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 2.719610] UBIFS: media format: w4/r0 (latest is w4/r0), UUID DFEF06B5-93BD-405D-955B-0D192442F33A, small LPT model
[ 2.785946] UBIFS: mounted UBI device 2, volume 0, name "firm0", R/O mode
[ 2.792670] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 2.801829] UBIFS: FS size: 7237632 bytes (6 MiB, 57 LEBs), journal size 1650688 bytes (1 MiB, 13 LEBs)
[ 2.811213] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 2.816263] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 89BA13B0-5EF6-4E0F-BE2E-B95726632087, small LPT model
[ 2.830634] UBIFS: background thread "ubifs_bgt3_0" started, PID 600
[ 2.862228] UBIFS: recovery needed
[ 2.884958] UBIFS: recovery completed
[ 2.888634] UBIFS: mounted UBI device 3, volume 0, name "log"
[ 2.894332] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 2.903463] UBIFS: FS size: 7237632 bytes (6 MiB, 57 LEBs), journal size 1650688 bytes (1 MiB, 13 LEBs)
[ 2.912839] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 2.917903] UBIFS: media format: w4/r0 (latest is w4/r0), UUID DBC2ADDB-2E45-46BE-8553-F5AEAB2F89BD, small LPT model
[ 2.931544] UBIFS: background thread "ubifs_bgt0_0" started, PID 602
[ 2.963172] UBIFS: recovery needed
[ 3.044372] UBIFS: recovery completed
[ 3.048042] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[ 3.054006] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 3.063119] UBIFS: FS size: 94597120 bytes (90 MiB, 745 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[ 3.072786] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 3.077836] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 27A2060B-95C4-4CE0-ACBD-280A13E9C15D, small LPT model
[ 5.516861] Unhandled fault: external abort on non-linefetch (0x818) at 0x36f2e380
[ 5.542077] irq = 170
[ 5.553152] <<-GTP-INFO->> GTP driver installing...
[ 5.558186] <<-GTP-INFO->> GTP Driver Version: V2.4<2014/11/28>
[ 5.564081] <<-GTP-INFO->> GTP Driver Built@22:06:06, Apr 27 2018
[ 5.570124] <<-GTP-INFO->> GTP I2C Address: 0x14
[ 5.574775] 0-0014 supply vdd_ana not found, using dummy regulator
[ 5.580961] 0-0014 supply vcc_i2c not found, using dummy regulator
[ 5.587265] <<-GTP-INFO->> Guitar reset
[ 5.713798] <<-GTP-INFO->> IC Version: 928_1060
[ 5.724470] <<-GTP-INFO->> X_MAX: 1024, Y_MAX: 600, TRIGGER: 0x00
[ 5.743323] <<-GTP-INFO->> create proc entry gt9xx_config success
[ 5.749597] input: goodix-ts as /devices/virtual/input/input0
[ 5.755587] <<-GTP-INFO->> GTP works in interrupt mode.
[ 5.771618] gpib_usb_init
[ 5.774381] usbcore: registered new interface driver usb-gpib
[ 7.043496] macb e000b000.ethernet eth0: link up (100/Full)
[ 10.602623] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 10.621906] ehci-pci: EHCI PCI platform driver
[ 10.680048] e0002000.usb supply vbus not found, using dummy regulator
[ 10.687358] ci_hdrc ci_hdrc.0: ChipIdea HDRC found, lpm: 0; cap: 4abfc100 op: 4abfc140
[ 10.687380] ci_hdrc ci_hdrc.0: It is OTG capable controller
[ 10.687400] ci_hdrc ci_hdrc.0: EHCI Host Controller
[ 10.692233] ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1
[ 10.723343] ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00
[ 10.728863] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 10.735636] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 10.742817] usb usb1: Product: EHCI Host Controller
[ 10.747704] usb usb1: Manufacturer: Linux 3.19.2-omg-xilinx-svn35686 ehci_hcd
[ 10.754839] usb usb1: SerialNumber: ci_hdrc.0
[ 10.760001] hub 1-0:1.0: USB hub found
[ 10.763823] hub 1-0:1.0: 1 port detected
[ 10.768426] e0003000.usb supply vbus not found, using dummy regulator
[ 10.775198] ci_hdrc ci_hdrc.1: ChipIdea HDRC found, lpm: 0; cap: 4abfe100 op: 4abfe140
[ 10.775220] ci_hdrc ci_hdrc.1: It is OTG capable controller
[ 10.831060] usbcore: registered new interface driver usb-storage
[ 10.859701] usbcore: registered new interface driver usbhid
[ 10.868287] usbhid: USB HID core driver
[ 10.882227] mousedev: PS/2 mouse device common for all mice
[ 12.540768] random: Aladdin urandom read with 21 bits of entropy available
[ 12.892722] spidev spi1.1: setup: unsupported mode bits 60
[ 13.036710] UBIFS: background thread "ubifs_bgt2_0" started, PID 756
[ 13.080274] UBIFS: background thread "ubifs_bgt2_0" stops
[ 13.121244] UBIFS: background thread "ubifs_bgt2_0" started, PID 761
[ 13.159043] UBIFS: background thread "ubifs_bgt2_0" stops
[ 13.177131] UBIFS: background thread "ubifs_bgt2_0" started, PID 778
[ 13.221521] UBIFS: background thread "ubifs_bgt2_0" stops
[ 13.240604] UBIFS: background thread "ubifs_bgt2_0" started, PID 788
[ 13.250671] UBIFS: background thread "ubifs_bgt2_0" stops
[ 13.265515] UBIFS: background thread "ubifs_bgt2_0" started, PID 794
[ 13.293002] UBIFS: background thread "ubifs_bgt2_0" stops
[ 13.309112] UBIFS: background thread "ubifs_bgt2_0" started, PID 808
[ 13.327784] UBIFS: background thread "ubifs_bgt2_0" stops
[ 13.351298] UBIFS: background thread "ubifs_bgt2_0" started, PID 813
[ 13.366858] UBIFS: background thread "ubifs_bgt2_0" stops
[ 13.822426] <<-GTP-INFO->> System resume.
[ 13.822437] gpio-963 (GTP INT IRQ): _gpiod_direction_output_raw: tried to set a GPIO tied to an IRQ as output
[ 13.833489] <<-GTP-INFO->> GTP wakeup sleep.
[ 13.833498] gpio-963 (GTP INT IRQ): _gpiod_direction_output_raw: tried to set a GPIO tied to an IRQ as output
[ 13.962236] UBIFS: background thread "ubifs_bgt2_0" started, PID 825
[ 13.999042] UBIFS: background thread "ubifs_bgt2_0" stops
[ 14.033277] UBIFS: background thread "ubifs_bgt2_0" started, PID 830
[ 14.048697] UBIFS: background thread "ubifs_bgt2_0" stops
[ 14.337720] UBIFS: background thread "ubifs_bgt2_0" started, PID 837
[ 14.369317] UBIFS: background thread "ubifs_bgt2_0" stops
[ 16.548160] UBIFS: background thread "ubifs_bgt2_0" started, PID 844
[ 16.576941] UBIFS: background thread "ubifs_bgt2_0" stops
[ 22.610170] input: PolyVision Touch Screen as /devices/virtual/input/input1
[ 137.330684] random: nonblocking pool is initialized
It's done ;)Sorry don’t have the correct tools.
/usr/bin/siglent # ls -la
total 13772
drwxrwxrwx 9 1000 1000 1392 Sep 10 20:22 .
drwxrwxrwx 1 1000 232 3204 Jan 1 1970 ..
-rw------- 1 root root 6972 Jan 10 09:18 .ash_history
-rwxrwxrwx 1 root root 13856588 Sep 10 20:00 Aladdin
drwxrwxrwx 8 1000 1000 792 Sep 10 20:01 config
-rwxrwxrwx 1 root root 1078 Sep 10 20:00 config_eth0.sh
drwxrwxrwx 2 1000 1000 1904 Sep 10 20:01 drivers
drwxrwxrwx 3 1000 1000 752 Sep 10 20:01 firmdata0
drwxrwxrwx 2 1000 1000 160 Jan 8 2019 firmdata1
drwxrwxrwx 2 root root 688 Sep 10 20:00 lib
-rwxrwxrwx 1 root root 12068 Sep 10 20:00 lighttpd.conf
drwxrwxrwx 2 1000 1000 232 Jan 8 2019 log
-rwxrwxrwx 1 root root 67085 Sep 10 20:00 php.ini
-rwxrwxrwx 1 root root 2204 Sep 10 20:23 startup_app.sh
-rwxrwxrwx 1 root root 77 Sep 10 20:00 startup_ftp.sh
-rwxrwxrwx 1 root root 482 Sep 10 20:00 startup_vnc.sh
drwxrwxrwx 10 1000 1000 1144 Jan 10 12:38 usr
-rwxrwxrwx 1 root root 490 Sep 10 20:00 vdma_vnc.sh
-rwxrwxrwx 1 root root 29337 Sep 10 20:00 vncserver
-rwxrwxrwx 1 root root 97611 Sep 10 20:00 vsftpd
[ 1.112430] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 1.120023] nand: WARNING: pl353-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
[ 1.131531] Bad block table found at page 131008, version 0x01
[ 1.137807] Bad block table found at page 130944, version 0x01
[ 1.143935] 12 ofpart partitions found on MTD device pl353-nand
[ 1.149785] Creating 12 MTD partitions on "pl353-nand":
/usr/bin/siglent # md5sum Aladdin
29f1dc880f90a2702d0b6d90ee48a1c6 Aladdin
/usr/bin/siglent # ls -ltra
total 13772
drwxrwxrwx 1 65534 254 3204 Jan 1 1970 ..
drwxrwxrwx 10 65534 65534 904 Jan 1 2000 usr
drwxrwxrwx 2 65534 65534 160 May 7 2021 firmdata1
drwxrwxrwx 2 65534 65534 232 May 7 2021 log
-rwxrwxrwx 1 root root 97611 Dec 30 14:55 vsftpd
-rwxrwxrwx 1 root root 77 Dec 30 14:55 startup_ftp.sh
-rwxrwxrwx 1 root root 1078 Dec 30 14:55 config_eth0.sh
-rwxrwxrwx 1 root root 29337 Dec 30 14:55 vncserver
-rwxrwxrwx 1 root root 482 Dec 30 14:55 startup_vnc.sh
-rwxrwxrwx 1 root root 67085 Dec 30 14:55 php.ini
-rwxrwxrwx 1 root root 12068 Dec 30 14:55 lighttpd.conf
drwxrwxrwx 2 root root 688 Dec 30 14:55 lib
-rwxrwxrwx 1 root root 13856588 Dec 30 14:55 Aladdin
-rwxrwxrwx 1 root root 490 Dec 30 14:55 vdma_vnc.sh
drwxrwxrwx 2 65534 65534 1904 Dec 30 14:56 drivers
drwxrwxrwx 8 65534 65534 704 Dec 30 14:56 config
drwxrwxrwx 3 65534 65534 840 Dec 30 15:08 firmdata0
drwxrwxrwx 9 65534 65534 1392 Jan 4 11:59 .
-rwxrwxrwx 1 root root 2205 Jan 5 21:05 startup_app.sh
-rw------- 1 root root 6126 Jan 10 17:06 .ash_history
/usr/bin/siglent # cd drivers/
/usr/bin/siglent/drivers # ls -ltra
total 552
-rwxrwxrwx 1 65534 65534 17192 May 7 2021 usbtmc.ko
-rwxrwxrwx 1 65534 65534 11629 May 7 2021 usbmisc_imx.ko
-rwxrwxrwx 1 65534 65534 45018 May 7 2021 usbhid.ko
-rwxrwxrwx 1 65534 65534 100267 May 7 2021 usb-storage.ko
-rwxrwxrwx 1 65534 65534 15141 May 7 2021 uinput.ko
-rwxrwxrwx 1 65534 65534 10516 May 7 2021 siglentaxidma.ko
-rwxrwxrwx 1 65534 65534 8864 May 7 2021 siglent_vnc.ko
-rwxrwxrwx 1 65534 65534 20202 May 7 2021 mousedev.ko
-rwxrwxrwx 1 65534 65534 60742 May 7 2021 libcomposite.ko
-rwxrwxrwx 1 65534 65534 288 May 7 2021 insmod_before_app.sh
-rwxrwxrwx 1 65534 65534 740 May 7 2021 insmod_after_app.sh
-rwxrwxrwx 1 65534 65534 21193 May 7 2021 gt9xx.ko
-rwxrwxrwx 1 65534 65534 11406 May 7 2021 gpib.ko
-rwxrwxrwx 1 65534 65534 9904 May 7 2021 ehci-pci.ko
-rwxrwxrwx 1 65534 65534 56724 May 7 2021 ehci-hcd.ko
-rwxrwxrwx 1 65534 65534 5550 May 7 2021 ci_hdrc_zevio.ko
-rwxrwxrwx 1 65534 65534 6990 May 7 2021 ci_hdrc_usb2.ko
-rwxrwxrwx 1 65534 65534 6588 May 7 2021 ci_hdrc_pci.ko
-rwxrwxrwx 1 65534 65534 6623 May 7 2021 ci_hdrc_msm.ko
-rwxrwxrwx 1 65534 65534 10170 May 7 2021 ci_hdrc_imx.ko
-rwxrwxrwx 1 65534 65534 44456 May 7 2021 ci_hdrc.ko
-rwxrwxrwx 1 65534 65534 22747 May 7 2021 ads7846.ko
-rwxrwxrwx 1 65534 65534 189 May 7 2021 .sh
-rwxrwxrwx 1 root root 27844 Dec 30 14:55 g_usbtmc.ko
drwxrwxrwx 2 65534 65534 1904 Dec 30 14:56 .
drwxrwxrwx 9 65534 65534 1392 Jan 4 11:59 ..
/usr/bin/siglent # uname -a
Linux (none) 3.19.2-omg-xilinx-svn35686 #11 SMP PREEMPT Fri Jan 4 15:28:26 CST 2019 armv7l GNU/Linux
/usr/bin/siglent # ls -ltra
total 13772
drwxrwxrwx 1 1000 232 3204 Jan 1 1970 ..
drwxrwxrwx 2 1000 1000 160 Jan 8 2019 firmdata1
drwxrwxrwx 2 1000 1000 232 Jan 8 2019 log
-rwxrwxrwx 1 root root 97611 Sep 10 20:00 vsftpd
-rwxrwxrwx 1 root root 77 Sep 10 20:00 startup_ftp.sh
-rwxrwxrwx 1 root root 1078 Sep 10 20:00 config_eth0.sh
-rwxrwxrwx 1 root root 29337 Sep 10 20:00 vncserver
-rwxrwxrwx 1 root root 482 Sep 10 20:00 startup_vnc.sh
-rwxrwxrwx 1 root root 12068 Sep 10 20:00 lighttpd.conf
-rwxrwxrwx 1 root root 13856588 Sep 10 20:00 Aladdin
-rwxrwxrwx 1 root root 67085 Sep 10 20:00 php.ini
drwxrwxrwx 2 root root 688 Sep 10 20:00 lib
-rwxrwxrwx 1 root root 490 Sep 10 20:00 vdma_vnc.sh
drwxrwxrwx 2 1000 1000 1904 Sep 10 20:01 drivers
drwxrwxrwx 8 1000 1000 792 Sep 10 20:01 config
drwxrwxrwx 3 1000 1000 752 Sep 10 20:01 firmdata0
drwxrwxrwx 9 1000 1000 1392 Sep 10 20:22 .
-rwxrwxrwx 1 root root 2204 Sep 10 20:23 startup_app.sh
drwxrwxrwx 10 1000 1000 1056 Jan 10 14:11 usr
-rw------- 1 root root 7061 Jan 10 17:28 .ash_history
/usr/bin/siglent/drivers # ls -ltra
total 552
-rwxrwxrwx 1 1000 1000 10516 Jan 8 2019 siglentaxidma.ko
-rwxrwxrwx 1 1000 1000 21193 Jan 8 2019 gt9xx.ko
-rwxrwxrwx 1 1000 1000 11406 Jan 8 2019 gpib.ko
-rwxrwxrwx 1 1000 1000 5550 Jan 8 2019 ci_hdrc_zevio.ko
-rwxrwxrwx 1 1000 1000 6588 Jan 8 2019 ci_hdrc_pci.ko
-rwxrwxrwx 1 1000 1000 44456 Jan 8 2019 ci_hdrc.ko
-rwxrwxrwx 1 1000 1000 17192 Jan 8 2019 usbtmc.ko
-rwxrwxrwx 1 1000 1000 100267 Jan 8 2019 usb-storage.ko
-rwxrwxrwx 1 1000 1000 20202 Jan 8 2019 mousedev.ko
-rwxrwxrwx 1 1000 1000 288 Jan 8 2019 insmod_before_app.sh
-rwxrwxrwx 1 1000 1000 6623 Jan 8 2019 ci_hdrc_msm.ko
-rwxrwxrwx 1 1000 1000 11629 Jan 8 2019 usbmisc_imx.ko
-rwxrwxrwx 1 1000 1000 8864 Jan 8 2019 siglent_vnc.ko
-rwxrwxrwx 1 1000 1000 740 Jan 8 2019 insmod_after_app.sh
-rwxrwxrwx 1 1000 1000 9904 Jan 8 2019 ehci-pci.ko
-rwxrwxrwx 1 1000 1000 56724 Jan 8 2019 ehci-hcd.ko
-rwxrwxrwx 1 1000 1000 10170 Jan 8 2019 ci_hdrc_imx.ko
-rwxrwxrwx 1 1000 1000 45018 Jan 8 2019 usbhid.ko
-rwxrwxrwx 1 1000 1000 60742 Jan 8 2019 libcomposite.ko
-rwxrwxrwx 1 1000 1000 6990 Jan 8 2019 ci_hdrc_usb2.ko
-rwxrwxrwx 1 1000 1000 22747 Jan 8 2019 ads7846.ko
-rwxrwxrwx 1 1000 1000 189 Jan 8 2019 .sh
-rwxrwxrwx 1 1000 1000 15141 Oct 18 2019 uinput.ko
-rwxrwxrwx 1 root root 27844 Sep 10 20:00 g_usbtmc.ko
drwxrwxrwx 2 1000 1000 1904 Sep 10 20:01 .
drwxrwxrwx 9 1000 1000 1392 Sep 10 20:22 ..
[ 1.109927] nand: WARNING: pl353-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
[ 1.121444] Bad block table found at page 131008, version 0x01
[ 1.127734] Bad block table found at page 130944, version 0x01
/usr/bin/siglent # ./Aladdin&
/usr/bin/siglent # log init finished
udhcpc: started, v1.26.0.git
Setting IP address 0.0.0.0 on eth0
udhcpc: sending discover
udhcpc: sending select for 192.168.178.171
udhcpc: lease of 192.168.178.171 obtained, lease time 864000
Setting IP address 192.168.178.171 on eth0
Deleting routers
route: SIOCDELRT: No such process
Adding router 192.168.178.1
Recreating /usr/bin/siglent/usr/etc/resolv.conf
Adding DNS server 192.168.178.1
rotationAngle: 0 invertx: false inverty: false
rotationAngle: 0 invertx: false inverty: false
[INFO] /home/share/yangh/aladdin_no_mod/tag5_1/product_aladdin/business/dp_control/module_business/dp_vna/vector_calibrator.cpp 129 msg:vector_calibrator. load_s11_factory_calibration success!!!!!!!!!!!!
[INFO] /home/share/yangh/aladdin_no_mod/tag5_1/product_aladdin/business/dp_control/module_business/dp_vna/vector_calibrator.cpp 135 msg:vector_calibrator. load s21 factory calibration ref data success!!!!!!!!!!!!
[INFO] /home/share/yangh/aladdin_no_mod/tag5_1/product_aladdin/business/dp_control/module_business/dp_vna/vector_calibrator.cpp 168 msg:edison:vector_calibrator::set_cali_kit_file_name kitName=User1,gender is 1645,index = 7
/usr/bin/siglent # strings Aladdin | grep insmod
insmod /usr/bin/siglent/drivers/g_usbtmc.ko
insmod /usr/bin/siglent/drivers/udc-core.ko;insmod /usr/bin/siglent/drivers/musb_hdrc.ko;insmod /usr/bin/siglent/drivers/ti81xx.ko
insmod /usr/bin/siglent/drivers/libcomposite.ko;insmod /usr/bin/siglent/drivers/udc-xilinx.ko;
insmod /usr/bin/siglent/drivers/libcomposite.ko;
insmod
/usr/bin/siglent #
/usr/bin/siglent #
/usr/bin/siglent # ls -la /usr/bin/siglent/drivers/g_usbtmc.ko
-rwxrwxrwx 1 root root 27844 Dec 30 14:55 /usr/bin/siglent/drivers/g_usbtmc.ko
/usr/bin/siglent # ls -la /usr/bin/siglent/drivers/udc-core.ko
ls: /usr/bin/siglent/drivers/udc-core.ko: No such file or directory
/usr/bin/siglent # ls -la /usr/bin/siglent/drivers/musb_hdrc.ko
ls: /usr/bin/siglent/drivers/musb_hdrc.ko: No such file or directory
/usr/bin/siglent # ls -la /usr/bin/siglent/drivers/ti81xx.ko
ls: /usr/bin/siglent/drivers/ti81xx.ko: No such file or directory
/usr/bin/siglent # ls -la /usr/bin/siglent/drivers/libcomposite.ko
-rwxrwxrwx 1 65534 65534 60742 May 7 2021 /usr/bin/siglent/drivers/libcomposite.ko
/usr/bin/siglent # ls -la /usr/bin/siglent/drivers/udc-xilinx.ko
ls: /usr/bin/siglent/drivers/udc-xilinx.ko: No such file or directory
/usr/bin/siglent # ls -la /usr/bin/siglent/drivers/libcomposite.ko
-rwxrwxrwx 1 65534 65534 60742 May 7 2021 /usr/bin/siglent/drivers/libcomposite.ko
the checksum :Code: [Select]/usr/bin/siglent # md5sum Aladdin
29f1dc880f90a2702d0b6d90ee48a1c6 Aladdin
After the SSA > SVA cross flash I admit that I did not see big differences in operation because it was pro with all options.
Maybe something messed in your config files?
/usr/bin/siglent/firmdata0/NSP_trends_config_info.xml + NSP_sn_bandwidth.xml
/usr/bin/siglent/config/NSP_config_upgrade_info.xml
<?xml version="1.0" encoding="UTF-8"?>
<nsp_trends_info_root>
<device>
<language>english</language>
<pid>0x1301</pid>
<vid>0xf4ec</vid>
<product_type_1>SVA1032X</product_type_1>
<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><?xml version="1.0"?>
<nsp_system_info_root>
<device>
<system_information>
<serial_number>
<chip>0123456789</chip>
</serial_number>
</system_information>
</device>
<serial_number>SSA3PCEQ5R....</serial_number>
<license>
<_3021>
<lic>pykq4w6najjqb352</lic>
<remain>7680</remain>
</_3021>
<_TG>
<lic>sxnfmn3v2pjqv93z</lic>
<remain>7680</remain>
</_TG>
<_tEMI>
<lic>v6p76xetfany7s2p</lic>
<remain>7680</remain>
</_tEMI>
<_tAMK>
<lic>dtf6bh923ns35gze</lic>
<remain>7680</remain>
</_tAMK>
<_tCAT>
<lic>yrszgcmt36wkp84e</lic>
<remain>7680</remain>
</_tCAT>
<_tDMA>
<lic>z2cs4mq2fkbcsbxn</lic>
<remain>7680</remain>
</_tDMA>
<_tAMA>
<lic>3fmu2335p5b3hpja</lic>
<remain>7680</remain>
</_tAMA>
</license>
<nsp_system_info_root>
<device>
<system_information>
<serial_number>
<chip>0123456789</chip>
</serial_number>
</system_information>
</device>
<serial_number>SSA3PCEQ5R....</serial_number>
<license>
<_3021>
<lic>pykq4w6najjqb352</lic>
<remain>7680</remain>
</_3021>
<_TG>
<lic>sxnfmn3v2pjqv93z</lic>
<remain>7680</remain>
</_TG>
<_tEMI>
<lic>v6p76xetfany7s2p</lic>
<remain>7680</remain>
</_tEMI>
<_tAMK>
<lic>dtf6bh923ns35gze</lic>
<remain>7680</remain>
</_tAMK>
<_tCAT>
<lic>yrszgcmt36wkp84e</lic>
<remain>7680</remain>
</_tCAT>
<_tDMA>
<lic>z2cs4mq2fkbcsbxn</lic>
<remain>7680</remain>
</_tDMA>
<_tAMA>
<lic>3fmu2335p5b3hpja</lic>
<remain>7680</remain>
</_tAMA>
</license>
</nsp_system_info_root>
</nsp_system_info_root>
<?xml version="1.0" encoding="UTF-8"?>
<nsp_upgrade_info_root>
<device>
<upgrade_static_id>11410</upgrade_static_id>
<upgrade_start_id>11400</upgrade_start_id>
<upgrade_end_id>11499</upgrade_end_id>
</device>
</nsp_upgrade_info_root>
<?xml version="1.0" encoding="UTF-8"?>
<nsp_upgrade_info_root>
<device>
<upgrade_static_id>11410</upgrade_static_id>
<upgrade_start_id>11400</upgrade_start_id>
<upgrade_end_id>11499</upgrade_end_id>
</device>
</nsp_upgrade_info_root>
<?xml version="1.0"?>
<nsp_system_info_root>
<device>
<system_information>
<serial_number>
<chip>SSA3..........</chip>
</serial_number>
</system_information>
</device>
</nsp_system_info_root>
<?xml version="1.0" encoding="UTF-8"?>
<nsp_system_info_root>
<device>
<system_information>
<serial_number>
<chip>SSA3..........</chip>
</serial_number>
</system_information>
</device>
<Device>
<Mac>74:5b:....</Mac>
</Device>
</nsp_system_info_root>
I had made a small mistake of copying and pasting. :P
The analyzer always works properly,
:-+ thank you all for your support! :-+
Signent Europe responded and sent me a procedure for restoring the factory word.
SSA3X Plus USB recovery
I made a correction file with 76 points it seems to work normally.
Forgive me, I am bit confused:It is not a calibration it is just a correction to have a horizontal trace when there is a 50 \$\Omega\$ cap on the entrance
After recovering you lost your calibration and you had to redo it ?
Hi all
If I disassemble the spectrum analyzer and remove the NAND flash and make a full backup with a programmer, will it be enough if something goes wrong during the cross-flashing?
Hello My new Siglent SSA3021X Plus is behaving strangely. All input signals are displayed with -10dbm down. The test was performed with an R&S®SML02 signal generator. Then I connected an Oscilloscope to the output of the generator along with SSA to monitor the amplitude. When SSA is connected the amplitude drops significantly. I guess there is a weak link in the input. As can be seen from the reviews of colleagues, the group of input safety diodes is missing, which is unacceptable.You may have damaged the RF input.
The link you provided does not open. I did a factory reset. It does not help. I contacted the local Siglent Service. I'm waiting for a response for warranty service.It does with corrections to the URL. Try again:
Hello Yes I checked. The attenuators work normally. But when I read the link from tautech that in Europe they don't repair at the component level but replace the whole board, I wonder if I should send it for warranty repair. I guess they will refuse or announce a high price for repairs. And I will have to cover the shipping costs to Germany and back. There is the warranty service. There is none in our country! Poor support for the EU.New performance an only be guaranteed with board level replacement hence the high cost.
I think the input switch HMC1118 is faulty. I will order one and replace it. I know how to work with hot air. I have been repairing mobile phones for over 20 years. What will you advise me?DIY as many have succeeded and you sound well experienced in SMD repair.
Thanks for the support. I will order a chip from Aliexpress. In my country I did not find. I have no intention of writing to Siglent to have them sent to me. I probably won't answer. Hot air is like a mother tongue to me. I have dozens of refurbished video cards and thousands of phones in my life. I could make a video but there is already one on YouTube. My SA is SSA3021XP:-+
Thanks for the support. I will order a chip from Aliexpress. In my country I did not find.
584-HMC1118LP3DETR or
584-HMC1118LP3DE
Available in 2 variants. Who should I choose?
Thank you so much. It seems almost like my case. But with you, I don't notice the amplitude front at 18.3mhz at 0dbm level584-HMC1118LP3DETR or
584-HMC1118LP3DE
Available in 2 variants. Who should I choose?
It seems just a difference in packaging (cut tape, reel, etc.), I can't see an explanation in the datasheet.
I confirm the jumpy level of TG (see figure), specially at high output levels. It seems they are leveling the output of the internal generator with a step attenuator having relatively large steps. I don't know if leveling is in real time (with detector and feedback) or using a factory calibration table.
Hello again
Does anyone know if the warranty service will deny warranty if I have enabled all options with the python calculator?
They agree to repair, but I don't know how they will react to this if they do an inspection.
I didn't see a procedure for the reverse path anywhere. I don't have a backup.Hello again
Does anyone know if the warranty service will deny warranty if I have enabled all options with the python calculator?
They agree to repair, but I don't know how they will react to this if they do an inspection.
Since the digital part works, it shouldn't be too difficult to restore the original software configuration.
Since the digital part works, it shouldn't be too difficult to restore the original software configuration.I didn't see a procedure for the reverse path anywhere. I don't have a backup.
Any ideas?
Since the digital part works, it shouldn't be too difficult to restore the original software configuration.I didn't see a procedure for the reverse path anywhere. I don't have a backup.
Any ideas?
Never tried myself, but according to me you should restore the instrument ID for the SSA and immediately install the original software (ID and version must match). Then you can clear the licenses in the usual files and reinstall the original ones using the Python script. Traces will surely remain if you miss a backup, but the technicians may not be interested in checking them.
Since I haven't ever tried this, I may have skipped some critical information. Help from the gurus will certainly arrive soon :-+ .
In any case, if you damaged the front end, the repair may not be covered by warranty.
As for the 1.5dB jump of the TG at 18.3MHz and 0dBm - I can confirm that.This comparison you made will be of help here. I have no worries about TG anymore
I have compared in the second screenshot: Range 0-100MHz once with TG set to 0dBm (yellow trace) and once -3dBm (purple).
They probably won't care. They don't know who provided the keys and how they were generated.I think that the Siglent website has statistics on the purchase of keys by serial number of the device, and a possible check would confirm this. About the files, this is a job for programmers. Unfortunately, that's where I'm weak.
But you could edit the license file and remove the extra option that the key added. I don't remember which file it is but it is in the Siglent folder or its subfolders.
Hello, this is my first post.Hello and welcome to the forum. My advice is for now to leave the device in original condition if it works well. The SSA to SVA conversion procedure is scattered all over the forum here. There is no clear sequence of actions written in one post. Everything is in pieces. Everyone has contributed something. I am therefore still waiting for a systematized solution for such a transformation. I'll even enlist the help of a programmer friend because I'm a hardware engineer. But provided someone comes along here who knows the steps for the respective software version. But one thing is certain. There are smart people here, professionals who understand their work.If I'm wrong, forgive me.
I read everything (probably with understanding) and decided to act..
I have brand new SSA3021X Plus with firmare 3.2.2.5.0.
I followed the post #1619
1. Initial backup of SSA3021X Plus with SSA3000X+_backup_11411.ADS - OK.
2. Telnet access for SSA3021X Plus - OK
Backup main directories - not OK.
I wanted to understand your words properly, so I used chroma's built-in translator,
but the translator in the command lines was creating errors
from aryginal line:
"cp -R /usr/bin/siglent/usr/backup /usr/bin/siglent/usr/mass_storage/U-disk0/SA-backup"
after translation, I got an extra space in the destination directory:
"cp -R /usr/bin/siglent/usr/backup /usr/bin/siglent /usr/mass_storage/U-disk0/SA-backup".
Of course, I didn't notice it. With the help of ^c and ^v I sent these commands to SSA.
I received many error messages.
Most messages were of the type: "cp: can't create symlink ...",
and some: "cp: recursion detected, omitting directory..."
I don't have the entire log from putty :(.
I checked bakckup and on the device that the following directories are empty:
/usr/bin/siglent/usr/backup and
/usr/bin/siglent/usr/usr.
I updated the firmware to 3.2.2.5.1R1
I restored the factory settings
This did not change anything.
I think I broke something.
Device seems to work well, what should I do next?
If some files are missing how to restore them?
In the end, of course, I want an SVA.
best regards
Darek
I just saw a video where an ssa3000 is shown working on a computer screen and the truth is that it has been quite depressing. Does easy spectrum always work like this or is this the exception that proves the rule?
The image is at the moment 44.15
https://youtu.be/VoefxhPKokU?t=2578
Best regards
...
But the directory /usr/mass_storage/U-disk0/SA-backup does not exist, so the cp command should have shown an error "cp: usr/mass_storage/U-disk0/SA-backup is not a directory" immediately...
...
I just saw a video where an ssa3000 is shown working on a computer screen and the truth is that it has been quite depressing. Does easy spectrum always work like this or is this the exception that proves the rule?As the model Tony has is SSA3021X Plus he is using the inbuilt webserver NOT EasySpectrum and PC display latency might be from a # of things, not excluding his PC or LAN.
The image is at the moment 44.15
https://youtu.be/VoefxhPKokU?t=2578
Best regards
Had a moment to hunt the worthy ones out:Thanks for the support. I will order a chip from Aliexpress. In my country I did not find. I have no intention of writing to Siglent to have them sent to me. I probably won't answer. Hot air is like a mother tongue to me. I have dozens of refurbished video cards and thousands of phones in my life. I could make a video but there is already one on YouTube. My SA is SSA3021XP:-+
There are other threads here on RF input damage/repair including one from the Asian chap that did the video near the end of the thread linked above. If I get some time I'll try to find it again and link it here.
Looks similar on my instrument - maybe the dip between 0-5kHz is a little bit lower..
Hello
After successfully repairing the RF input, I want to compare the TG at low frequencies. Can someone take a screenshot of mine?
I think in the area around 9khz it should straighten the line to -20dbm.
I checked the RF input with an external tracking generator and the line becomes horizontal after 9khz. And with the built-in generator, this is what is obtained in the picture.
I didn't follow the whole discussion, but you should know that the instrument specifications start at 9 kHz. So it's normal that the line is not horizontal.
Convert it to a SVA and be prepared for a further very pleasant experience. ;)
IMHO this is splendid performance for a SA in this price category :-+
Today I repaired my SSA3021XP for the second time. The repair was much easier than the first time because I already had experience and I used low temperature solder.
Do not worry. That's how we get better. Twice in two weeks. New WR😁Today I repaired my SSA3021XP for the second time. The repair was much easier than the first time because I already had experience and I used low temperature solder.
Wow...
You have a talent... :clap: Damage the input of the spectrum analyzer twice is already a high level of talent :-DD
only because Mouser is offering volume discounts on parts you don't need to replace the frontend every day ! 😉
Have mercy with the PCB.
BW RBW not workingNo, normal.
SSA3021X+/hacked SVA
FW 3.2.2.5.1R1
all options enabled
as per TV84 instructions
when BW pressed during NVA mode, the option is greyed out , only default IFBW 10KHz
it works in SSA mode
Anybody has the same problem ?
did I do something wrong ?
BW RBW not workingNo, normal.
SSA3021X+/hacked SVA
FW 3.2.2.5.1R1
all options enabled
as per TV84 instructions
when BW pressed during NVA mode, the option is greyed out , only default IFBW 10KHz
it works in SSA mode
Anybody has the same problem ?
did I do something wrong ?
cd /
mount -o remount,rw /usr/bin/siglent/usr/mass_storage/U-disk0
cp -R /usr/bin/siglent/usr/backup /usr/bin/siglent/usr/mass_storage/U-disk0/SA-backup
cp -R /usr/bin/siglent/usr/config /usr/bin/siglent/usr/mass_storage/U-disk0/SA-config
cp -R /usr/bin/siglent/usr/usr /usr/bin/siglent/usr/mass_storage/U-disk0/SA-usr
cp -R /usr/bin/siglent/usr/vnacalikitdata /usr/bin/siglent/usr/mass_storage/U-disk0/SA-vnacalikitdata
cp -R /usr/bin/siglent/firmdata0 /usr/bin/siglent/usr/mass_storage/U-disk0/SA-firmdata05) Make files writeablemount -o remount,rw /usr/bin/siglent6) and add telnet server startup line in file “/usr/bin/siglent/startup_app.sh”:vi /usr/bin/siglent/startup_app.shenter the following line exactly close to the end, just before line "/usr/bin/siglent/Aladdin &" /sbin/telnetd -l /bin/sh -p 10101 &7)The end of file will look like:portmap &
/sbin/telnetd -1 /bin/sh -p 10101 &
/usr/bin/siglent/Aladdin &
echo "startup_app.sh end++++++++++"sync && rebootmount -o remount,rw /usr/bin/siglent/firmdata06) Copy calibration files from USB stick to SSAcp /usr/bin/siglent/usr/mass_storage/U-disk0/SA-firmdata0/cali/na_1p /usr/bin/siglent/firmdata0/cali/na_1p
cp /usr/bin/siglent/usr/mass_storage/U-disk0/SA-firmdata0/cali/na_2p /usr/bin/siglent/firmdata0/cali/na_2p7) finalise changes and reboot sync && rebootVI) Recalibrate VNA using short/load/open calibration kitDoes it need to be SSA3021X Plus or can it be a SSA3021X as they include tracking now and cost less?Get the X Plus Drew as the little more cost is rewarded with a touch display and mouse/keyboard capable device and a few more fruits too.
Drew
mount -o remount,rw /usr/bin/siglent/usr/mass_storage/U-disk0- in my terminal (Linux console) I had the last line of the '/usr/bin/siglent/startup_app.sh' file hidden by the vi bar --- I've simply ignored it, and checked that everything was ok by doing a 'cat' of the file afterwards (for the non-Linux users, simply type: cat /usr/bin/siglent/startup_app.sh)telnet 10.0.0.50 23
username: root
password: ding1234Hello, I have two questions regarding the SSA3000Refer to P10 of the datasheet:
The first is general, I am used to using tv analyzers and they all bring spectrum analyzers. Normally the noise floor is usually around 20db. Nowadays almost all the signals are digital, for example, a COFDM signal With 8mhz of bandwidth, that type of signal, in a spectrum analyzer like the one that television analyzers bring, would logically begin to be seen from 20db. The question would be: From what lower level would you start to know that there is such a signal in an SSA3000? We could add the variable of the amplifier but in any case it would be a question of knowing what advantage in terms of weak signals an SSA3000 has over a spectrum analyzer of a normal TV analyzer.
The second question would be to know the dynamic range of these analyzers
Best Regards
https://int.siglent.com/u_file/download/22_08_23/SSA3000X%20Plus_DataSheet_DS0703P_E04C.pdf
Range is RBW setting and Preamp dependant in that we need the Preamp ON to obtain best sensitivity and RBW at a low value too but the penalty for selecting all sensitivity possible is much increased sweep times.
AM DEMODULATION QUESTION: I recently got a used SSA3021X, with version list: SW1 is at 1.2.9.1, SW2 is 20180320-1, SW3 is 000000D1, HW 07.03.00. Tag says March 2017. It's had so little use it still has many hours remaining on the unlicensed options.
I can't get AM demod out of the audio jack. I located a strong local AM station at 1.42 Mhz, tried RBW 20kHz, SPAN .5 MHz with 5s sweep - also tried various RBW/VBW and zero span. There is absolutely no output at all from the audio jack. I am able to get FM audio just fine from local FM stations feeding it into computer speakers. Did I set something up wrong for AM? I only recall one other poster having such trouble - but can't find that reference now. It seems generally functional and in-spec, and I was able to sweep a 5.3 MHz filter just fine.
From what I have seen on the internet, I very much doubt that any spectrum analyzer can represent, without problems, a 10 dBm signal together with a -150 dBm signal.From P3 in this thread is an example taken from an early SSA3000X prior to release as an example setting the RBW and REF level to explore the lower levels of sensitivity. Since those early days many later firmware versions improved on what these instruments can do to now we have RBW of 1 Hz whereas once it was 10 Hz as shown in this screenshot.
The unit is working but I think I made a mistake with the NSP config file in model it is empty, I am unable to get telnet access what ADS file do I need to use to get telnet access so I can correct the NSP file.
Once access and changed the file should i be able to flash the FW again?
Yep, seen that. I don't think Siglent are saying that the instrument will be distortion free and linear all the way up to that power level though. That's just the power below which you don't let the magic smoke out the front end.Right, well actually all the datasheet specifications need be considered for any usage.....including accuracy specs....level and frequency.
That is the reason, why my old R&S SA had a little button, which switched a 2 or 3 db attenuator into the signal path - you were than able to see if the spur you are watching was part of a real signal, or if it was intermodulation of 2nd oder 3rd order (or higher) by seeing the nominal attenuation or multiples of it.
Distortion products tend to rise in accordance to their order. If we increase the input signal by 1 dB, the 2nd order distortion products will rise by 2 dB; likewise, the 3rd order distortion products will rise by 3 dB.
1. The noise figure (NF) for the formulas is the *actual* displayed noise level given your RBW (& other) settings?Yes, of course!
The spec sheet gives -141 dBm (typ.), but only with att = 0 dB, RBW = 1 Hz, sample detector, trace average > 50, TG off. In practice, very few people use a RBW of 1 Hz & >50 trace average as it's so slow and not always needed. Increasing the RBW and decreasing the trace average will speed the refresh up but increase the noise floor. I think turning the TG on also adds some noise, which is why Siglent turned it off to get the best DANL for their spec sheet.Well, it's always a tradeoff. If you need to measure very low distortion levels, then you will have to choose settings that provide the highest sensitivity, i.e. the lowest noise floor. For the usual harmonics of a transmitter, in the range up to -60 dBc, it should not be much of a challenge and you can use wider RBW. Practice will tell you what works.
2. Is 'Second harmonic distortion (SHI)' the same thing as 2nd Order Intercept (SOI)? Siglent have an entry for SHI but not for SOI in their spec sheet (see my post above for attachment). If not, can anyone explain what Siglent are talking about in the spec sheet when they quote -65 dBc / +45 dBm (nom.) for the SSA3000X-Plus?I could write a Novel about this, but I'll try to keep it short and simple. Either way, everyone using an SA should be familiar with these fundamentals…
3. 1dB gain compression is quoted at > -5 dBm (nom.) given fc ≥ 50 MHz, att = 0 dB, preamp off. Given this is so much higher than the -30dBm level discussed above, Can you think of a scenario where you'd want to drive the input this hard?Of course there are a few scenarios where the distortion of the SA frontend isn't a problem. Think of phase noise measurements for example. Since the CP already has 1 dB amplitude compression, we generally don't want to drive the input that hard indeed. I recommend to stay at least 10 dB below the CP.
If you don't need to drive the input this hard then you wouldn't as a smaller signal would yield less amplitude compression. You'd just add attenuation before the SA, but in doing so you'd give up any very small signal detail as it'd be lost int he noise.
Re: SSA3021X Plus Upgrade IssueCut the power and reboot......yeah I know they say not to do that with FW upgrades.....trust me on this one.
Followed all the steps and got to sync && reboot. It rebooted, then came up with Siglent on the screen and just sits there. Can't telnet to 23 or 10101. Just gets connection closed. Did a port scan and 5024 & 5025 are open but SCPI doesn't respond back with anything including *IDN?. No output at all from 5024 & 5025. Is it bricked? I got all the backups but can't seem to find a way back into OS on it to restore and start over.
Thoughts?
Any help would be awesome!
No, it can't.Really ? P16 of the datasheet suggests otherwise.
The data stream is much too high.
You need a propper TV field meter to be able to do that.
Let me know if you want some suggestions on capable TV field meters and/or other options.
No, it can't.Really ? P16 of the datasheet suggests otherwise.
The data stream is much too high.
You need a propper TV field meter to be able to do that.
Let me know if you want some suggestions on capable TV field meters and/or other options.
https://int.siglent.com/u_file/download/22_08_23/SSA3000X%20Plus_DataSheet_DS0703P_E04C.pdf
Do the 3021X+ or 3032X+ have any kind of directional coupling / RLB?Yes either as an combined option of the RLB HW and SW:
If not, how does "converting" a 3021X+ or 3032X+ to a 1032X get you true VNA capabilities? Wouldn't that need directional coupling of some kind?Yep, they are preinstalled in the SSA3000X Plus and actively used in VNA mode in SVA1000X and SSA3000X-R models.
I plugged a USB mouse into my SSA3021X+ [from USB port] but got nothing. Is there something I need to enable? I waded through all of the menus but didn't see anything.In the System menu ensure the Touch screen is enabled.
In the System menu ensure the Touch screen is enabled.
You didn't say if you had tried it on another device and it worked on that ?In the System menu ensure the Touch screen is enabled.
Thanks. It was. Turns out the SSA3021X+ is pretty picky about what devices it will use. A wired USB mouse worked --- both directly thru the front USB connector and thru a USB hub thru the front connector. One of my 2.4 GHz dongle-driven keyboard+touchpads worked great. Exactly once. Then it never worked again. And the foldable 2.4 GHz dongle-driven keyboard+touchpad that I bought just to take with the SSA3021X+ never worked. I guess it's not that big a deal, especially with the touch screen. But it's frustrating.
...R
You didn't say if you had tried it on another device and it worked on that ?
Please state brand and exact model of any accessory that won’t work in any Siglent device for engineers to investigate.You didn't say if you had tried it on another device and it worked on that ?
Yep. Everything worked fine on a Windows machine.
Please state brand and exact model of any accessory that won’t work in any Siglent device for engineers to investigate.
Using SVA1000_telnet_11410.zip
Hi, does anyone know what Lupusz is on about in the post below?They do....
https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3470576/?topicseen#msg3470576 (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?
192.168.2.000
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 192.168.2.000 10101After "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>
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.
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..
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?
...
Hi ,
Siglent released new firmware for the SSA3000x (plus & R) & SVA1000x : V3.2.2.6.0R7
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.
Confirm that the SVA1032X 3.2.2.6.0R7 upgrade works, but...
|O >:(
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 ?
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.
def gen(x):
h = hashlib.md5((
hashkey +
Model.ljust(32, '\x00') +
opt.ljust(5, '\x00') +
HOSTID.upper().ljust(32, '\x00') +
'\x00'*48).encode('ascii')
).digest()
key = ''
for b in h:
if (b <= 0x2F or b > 0x39) and (b <= 0x60 or b > 0x7A):
m = b % 0x24
b = m + (0x57 if m > 9 else 0x30)
if b == 0x30:
b = 0x32
if b == 0x31:
b = 0x33
if b == 0x6c:
b = 0x6d
if b == 0x6f:
b = 0x70
key += chr(b)
return key.lower()
for opt in otheropt:
print('{:5} {}'.format(opt, gen(HOSTID)))
Thank you for the fix. I found a copy of this file from the last time I did this and used that. The problem is for new users, the online file is corrupt, I don't think I can edit the file that's online. :-//
Just saw this enormous thread, but can a brand new SSA3021X-Plus still be cracked this day?I bought my SSA 3021X Plus in April & it upgraded with no problems. From reading this thread, I also thought that it had to be upgraded to an SVA first, but it doesn't. I've increased the frequency and enabled all the options whilst keeping it as an SSA. Go to the post by tomud linked below. Either run the online script or download the attachment to run it locally on your pc.
And I guess to buy one directly from Siglent is perhaps not a good idea if you want to have any small chance to crack it, aka all the options? So better from somewhere else and I think I have an idea.
And if I get it right so to crack it, it MUST be changed to a SVA1032X, there is no other way? Not only a SSA3021X-Plus and crack that to all options and still the same sort of speak?
Is there a page with all the steps to do? My python skills are non existent :( but I'm good at following steps. :)
I bought my SSA 3021X Plus in April & it upgraded with no problems. From reading this thread, I also thought that it had to be upgraded to an SVA first, but it doesn't. I've increased the frequency and enabled all the options whilst keeping it as an SSA.
I bought my SSA 3021X Plus in April & it upgraded with no problems. From reading this thread, I also thought that it had to be upgraded to an SVA first, but it doesn't. I've increased the frequency and enabled all the options whilst keeping it as an SSA.
But it's still not a SVA...
I bought my SSA 3021X Plus in April & it upgraded with no problems. From reading this thread, I also thought that it had to be upgraded to an SVA first, but it doesn't. I've increased the frequency and enabled all the options whilst keeping it as an SSA.
But it's still not a SVA...
Any higher with VNA?No, different HW.
Do the TG still work on the upgraded 3000-series for filter characterization? And I could do exactly the same on the 1000-series VNA, or?The TG option is permanent in all models.
...So I actually also get 3.2GHz even if I don't upgrade to VNA?...
Aha so that's how it works, thanks! :) I thought you had to connect to the analyzer or anything but I guess that's more if you want SVA.
By the way if i upgrade it to 3032 can I then whenever I want upgrade that to the 1000-series in some way or is it permanently locked to 3032 since it was not done the right way in the beginning?
And do I need to do the 3032 key first and then all or just all is enough?
...and it will also need to be cross flashed with the SVA firmware of course
Thanks. Can it be flashed back to a ordinary one without SVA or that will be permanent?
And I think I saw some disadvantage with SVA like BW or something? Or maybe I was incorrect with this, or?
Thanks for the info! About as i thought. So due the price I think I'll wait 3 years when the guarantee has went out to flash it then, because I'm not that keen on to buy a new one if its goes south.
But what exactely do I earn in options when cross flashed compared to a fully optioned 3021X Plus? Have seen slightly different answers about this.
But what exactely do I earn in options when cross flashed compared to a fully optioned 3021X Plus? Have seen slightly different answers about this.
And DTF/TDR capability.But what exactely do I earn in options when cross flashed compared to a fully optioned 3021X Plus? Have seen slightly different answers about this.
The VNA option.
And DTF/TDR capability.
The SVA1000X Mode button menu attached.
I have seen what a VNA can be used for and that is things I very, very rarely do, but who knows. But do reflection test without a bridge is cool, don't know how the VNA can do that though.That's what I thought too until getting a SVA1015X to complement my SSA3023X (before X Plus). Both later sold and replaced with SVA1032X.
So is there really any downsides at all to do VNA?No.
Good work! Interesting.SSA1015X Plus and SVA1015X share HW. SSA3021X Plus and higher BW models are slightly different spec and some share HW with SVA1032X, your target. ;)
Ok, more leaning towards it, and even if you don't need it its no problems in any way to have it there I guess since well the 1015X is a VNA with the same HW and all as I have understood.
On to a 1015 later on?Certainly not ! Different HW.
Can the option RT40 be completely removed when flash so it will never been shown? I saw that someone said it was seen and could even be started but since it doesn't contain a RT so will it of course not show anything.
When cross-flash 3032 to 1032 all available options is put into the 1032 incl RF40 which cant be used but allegedly is shown anyway. I assume the RT40 option in the 1032 would be greyed out instead until you enable that option with the pyton script?RT40 has never been an option for SVA whereas it is a SSA3000X-R option.
No of course not but it is enabled never the the less according to the bottom of post 1619 with the install instruction and also a picture of bottom post with it enabled:
SVA1032X now has all options permanently enabled (including RT40 which does not work in this HW version). Model name is SVA1032X, serial number shows XXXX.
Post 1619 and 1628
These are 2 years back so I don't know it ifs still the same today, and thus the question about this. Cross-flashed 1032 does not support RT40 as we all know because it doesn't have RT, but it is seen and can be started never the less as it seem but doesn't show anything and thus the question if it can be totally removed from the installation instead.
No of course not but it is enabled never the the less according to the bottom of post 1619 with the install instruction and also a picture of bottom post with it enabled:
SVA1032X now has all options permanently enabled (including RT40 which does not work in this HW version). Model name is SVA1032X, serial number shows XXXX.
Post 1619 and 1628
These are 2 years back so I don't know it ifs still the same today, and thus the question about this. Cross-flashed 1032 does not support RT40 as we all know because it doesn't have RT, but it is seen and can be started never the less as it seem but doesn't show anything and thus the question if it can be totally removed from the installation instead.
Finally the answer I was looking for, thanks! :)
U-Boot 2014.07-svn118162 (Sep 03 2020 - 12:37:11)
Board: Xilinx Zynq
I2C: ready
DRAM: ECC disabled 128 MiB
NAND: 256 MiB
MMC: zynq_sdhci: 0
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
int board_late_init(void)+++++
buzzer_off---------------
buzzer_on---------------
buzzer_off---------------
int board_late_init(void)-----
Net: Gem.e000b000
Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
USB1: ULPI request timed out
zynq ULPI viewport init failed
lowlevel init failed
scanning usb for storage devices... 1 Storage Device(s) found
Copying Linux from USB to RAM...
reading boot_uImage
** Unable to read file boot_uImage **
reading sva1000x_udiskEnv.txt
** Unable to read file sva1000x_udiskEnv.txt **
Copying Linux from NAND flash to RAM...
NAND read: device 0 offset 0x780000, size 0x400000
4194304 bytes read: OK
NAND read: device 0 offset 0xb80000, size 0x80000
524288 bytes read: OK
## Booting kernel from Legacy Image at 02080000 ...
Image Name: Linux-3.19.2-omg-xilinx-svn35686
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3121840 Bytes = 3 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 02000000
Booting using the fdt blob at 0x2000000
EHCI failed to shut down host controller.
Loading Kernel Image ... OK
Loading Device Tree to 06d0d000, end 06d13ec2 ... OK
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.19.2-omg-xilinx-svn35686 (ding@ding-T5810) (gcc version 4.6.1 (Sourcery CodeBench Lite 2011.09-50) ) #11 SMP PREEMPT Fri Jan 4 15:28:26 CST 2019
[ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine model: Zynq Zed Development Board
[ 0.000000] cma: Reserved 16 MiB at 0x09000000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] PERCPU: Embedded 9 pages/cpu @48e92000 s8128 r8192 d20544 u36864
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 40640
[ 0.000000] Kernel command line: console=ttyPS0,115200 root=/dev/mtdblock5 rootfstype=cramfs init=/linuxrc earlyprintk uboot_version=3
[ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Memory: 139704K/163840K available (3835K kernel code, 213K rwdata, 1580K rodata, 196K init, 216K bss, 7752K reserved, 16384K cma-reserved, 0K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0x4a800000 - 0xff000000 (2888 MB)
[ 0.000000] lowmem : 0x40000000 - 0x4a000000 ( 160 MB)
[ 0.000000] pkmap : 0x3fe00000 - 0x40000000 ( 2 MB)
[ 0.000000] modules : 0x3f000000 - 0x3fe00000 ( 14 MB)
[ 0.000000] .text : 0x40008000 - 0x40552200 (5417 kB)
[ 0.000000] .init : 0x40553000 - 0x40584000 ( 196 kB)
[ 0.000000] .data : 0x40584000 - 0x405b96a0 ( 214 kB)
[ 0.000000] .bss : 0x405b96a0 - 0x405ef914 ( 217 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
[ 0.000000] L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
[ 0.000000] L2C-310 erratum 769419 enabled
[ 0.000000] L2C-310 enabling early BRESP for Cortex-A9
[ 0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[ 0.000000] L2C-310 ID prefetch enabled, offset 1 lines
[ 0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[ 0.000000] L2C-310 cache controller enabled, 8 ways, 512 kB
[ 0.000000] L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
[ 0.000000] slcr mapped to 4a804000
[ 0.000000] zynq_clock_init: clkc starts at 4a804100
[ 0.000000] Zynq clock init
[ 0.000010] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns
[ 0.000128] timer #0 at 4a806000, irq=17
[ 0.000478] Console: colour dummy device 80x30
[ 0.000497] Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096)
[ 0.090269] pid_max: default: 32768 minimum: 301
[ 0.090419] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.090435] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.091060] CPU: Testing write buffer coherency: ok
[ 0.091254] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.091321] Setting up static identity map for 0x39c880 - 0x39c8d8
[ 0.240256] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.240334] Brought up 2 CPUs
[ 0.240353] SMP: Total of 2 processors activated (2664.03 BogoMIPS).
[ 0.240362] CPU: All CPU(s) started in SVC mode.
[ 0.240864] devtmpfs: initialized
[ 0.241588] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 0.247222] NET: Registered protocol family 16
[ 0.249126] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.271078] cpuidle: using governor ladder
[ 0.301040] cpuidle: using governor menu
[ 0.309307] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[ 0.309323] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 0.309451] zynq-ocm f800c000.ocmc: ZYNQ OCM pool: 256 KiB @ 0x4a880000
[ 0.320136] vgaarb: loaded
[ 0.320546] SCSI subsystem initialized
[ 0.320929] usbcore: registered new interface driver usbfs
[ 0.321043] usbcore: registered new interface driver hub
[ 0.321154] usbcore: registered new device driver usb
[ 0.321298] phy0 supply vcc not found, using dummy regulator
[ 0.321385] phy1 supply vcc not found, using dummy regulator
[ 0.321516] --------------usb_udc_init ------
[ 0.321762] pps_core: LinuxPPS API ver. 1 registered
[ 0.321775] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.321823] PTP clock support registered
[ 0.321960] EDAC MC: Ver: 3.0.0
[ 0.323480] Switched to clocksource arm_global_timer
[ 0.335236] NET: Registered protocol family 2
[ 0.335962] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.336012] TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.336070] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.336117] TCP: reno registered
[ 0.336134] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.336164] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.336356] NET: Registered protocol family 1
[ 0.336669] RPC: Registered named UNIX socket transport module.
[ 0.336682] RPC: Registered udp transport module.
[ 0.336691] RPC: Registered tcp transport module.
[ 0.336699] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.337069] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[ 0.338408] futex hash table entries: 512 (order: 3, 32768 bytes)
[ 0.339989] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 0.341002] io scheduler noop registered
[ 0.341022] io scheduler deadline registered
[ 0.341074] io scheduler cfq registered (default)
[ 0.343097] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
[ 0.343117] dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[ 0.343643] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 145, base_baud = 2500000) is a xuartps
[ 0.916938] console [ttyPS0] enabled
[ 0.921086] xdevcfg f8007000.devcfg: ioremap 0xf8007000 to 4a878000
[ 0.927835] [drm] Initialized drm 1.1.0 20060810
[ 0.940232] brd: module loaded
[ 0.947231] loop: module loaded
[ 0.955892] libphy: MACB_mii_bus: probed
[ 1.033613] macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 149 (00:0a:35:00:01:23)
[ 1.043513] macb e000b000.ethernet eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:1e, irq=-1)
[ 1.055057] i2c /dev entries driver
[ 1.060263] rtc-ds1307 0-0068: rtc core: registered ds1340 as rtc0
[ 1.066709] cdns-i2c e0004000.i2c: 400 kHz mmio e0004000 irq 143
[ 1.074050] zynq-edac f8006000.memory-controller: ecc not enabled
[ 1.080258] Xilinx Zynq CpuIdle Driver started
[ 1.085299] ledtrig-cpu: registered to indicate activity on CPUs
[ 1.092294] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[ 1.098601] nand: Micron MT29F2G08ABAEAWP
[ 1.102579] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 1.110172] nand: WARNING: pl353-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
[ 1.121677] Bad block table found at page 131008, version 0x01
[ 1.127948] Bad block table found at page 130944, version 0x01
[ 1.134081] 11 ofpart partitions found on MTD device pl353-nand
[ 1.139926] Creating 11 MTD partitions on "pl353-nand":
[ 1.145182] 0x000000000000-0x000000780000 : "fsbl"
[ 1.151008] 0x000000780000-0x000000b80000 : "kerneldata"
[ 1.157266] 0x000000b80000-0x000000c00000 : "device-tree"
[ 1.163604] 0x000000c00000-0x000001100000 : "Manufacturedata"
[ 1.170305] 0x000001100000-0x000001600000 : "reserved1"
[ 1.176506] 0x000001600000-0x000003e00000 : "rootfs"
[ 1.182404] 0x000003e00000-0x000004800000 : "firmdata0"
[ 1.188538] 0x000004800000-0x000006c00000 : "siglent"
[ 1.194590] 0x000006c00000-0x00000d000000 : "datafs"
[ 1.200596] 0x00000d000000-0x00000da00000 : "log"
[ 1.206281] 0x00000da00000-0x000010000000 : "upgrade_cramdisk"
[ 1.215007] TCP: cubic registered
[ 1.218252] NET: Registered protocol family 17
[ 1.222928] Registering SWP/SWPB emulation handler
[ 1.229657] rtc-ds1307 0-0068: setting system clock to 2023-08-07 22:53:36 UTC (1691448816)
[ 1.242999] cramfs_fill_nand blocks is 320-----------------------
[ 1.242999]
[ 1.242999]
[ 1.242999]
[ 1.256080] VFS: Mounted root (cramfs filesystem) readonly on device 31:5.
[ 1.262946] devtmpfs: mounted
[ 1.266201] Freeing unused kernel memory: 196K (40553000 - 40584000)
Starting rcS...
[ 1.538880] UBI-1: ubi_attach_mtd_dev:attaching mtd7 to ubi1
[ 1.686996] UBI-1: scan_all:scanning is finished
[ 1.697972] UBI-1 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 3, need 40
[ 1.709111] UBI-1: ubi_attach_mtd_dev:attached mtd7 (name "siglent", size 36 MiB)
[ 1.716574] UBI-1: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 1.725157] UBI-1: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 1.733681] UBI-1: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[ 1.742365] UBI-1: ubi_attach_mtd_dev:good PEBs: 288, bad PEBs: 0, corrupted PEBs: 0
[ 1.750137] UBI-1: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[ 1.759085] UBI-1: ubi_attach_mtd_dev:max/mean erase counter: 8/3, WL threshold: 4096, image sequence number: 995858657
[ 1.769873] UBI-1: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 288, PEBs reserved for bad PEB handling: 3
[ 1.780762] UBI-1: ubi_thread:background thread "ubi_bgt1d" started, PID 574
[ 1.783121] UBI-2: ubi_attach_mtd_dev:attaching mtd6 to ubi2
[ 1.827346] UBI-2: scan_all:scanning is finished
[ 1.838131] UBI-2 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 9, need 40
[ 1.849161] UBI-2: ubi_attach_mtd_dev:attached mtd6 (name "firmdata0", size 10 MiB)
[ 1.856782] UBI-2: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 1.865381] UBI-2: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 1.873904] UBI-2: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[ 1.882592] UBI-2: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[ 1.890260] UBI-2: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[ 1.899221] UBI-2: ubi_attach_mtd_dev:max/mean erase counter: 15/8, WL threshold: 4096, image sequence number: 725220286
[ 1.910112] UBI-2: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 80, PEBs reserved for bad PEB handling: 9
[ 1.920900] UBI-2: ubi_thread:background thread "ubi_bgt2d" started, PID 578
[ 1.923042] UBI-3: ubi_attach_mtd_dev:attaching mtd9 to ubi3
[ 1.967465] UBI-3: scan_all:scanning is finished
[ 1.978241] UBI-3 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 9, need 40
[ 1.989273] UBI-3: ubi_attach_mtd_dev:attached mtd9 (name "log", size 10 MiB)
[ 1.996378] UBI-3: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 2.004979] UBI-3: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 2.013529] UBI-3: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[ 2.022184] UBI-3: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[ 2.029858] UBI-3: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[ 2.038815] UBI-3: ubi_attach_mtd_dev:max/mean erase counter: 6/3, WL threshold: 4096, image sequence number: 898190011
[ 2.049614] UBI-3: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 80, PEBs reserved for bad PEB handling: 9
[ 2.060415] UBI-3: ubi_thread:background thread "ubi_bgt3d" started, PID 582
[ 2.062554] UBI-0: ubi_attach_mtd_dev:attaching mtd8 to ubi0
[ 2.462347] UBI-0: scan_all:scanning is finished
[ 2.474547] UBI-0: ubi_attach_mtd_dev:attached mtd8 (name "datafs", size 100 MiB)
[ 2.481963] UBI-0: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 2.490595] UBI-0: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 2.499112] UBI-0: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[ 2.507811] UBI-0: ubi_attach_mtd_dev:good PEBs: 800, bad PEBs: 0, corrupted PEBs: 0
[ 2.515561] UBI-0: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[ 2.524518] UBI-0: ubi_attach_mtd_dev:max/mean erase counter: 8/5, WL threshold: 4096, image sequence number: 1537676743
[ 2.535392] UBI-0: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 800, PEBs reserved for bad PEB handling: 40
[ 2.546367] UBI-0: ubi_thread:background thread "ubi_bgt0d" started, PID 586
[ 2.566280] UBIFS: background thread "ubifs_bgt1_0" started, PID 589
[ 2.597836] UBIFS: recovery needed
[ 2.661972] UBIFS: recovery completed
[ 2.665669] UBIFS: mounted UBI device 1, volume 0, name "siglent"
[ 2.671692] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 2.680846] UBIFS: FS size: 34410496 bytes (32 MiB, 271 LEBs), journal size 4952064 bytes (4 MiB, 39 LEBs)
[ 2.690493] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 2.695544] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 5C5CCD6E-B776-45EE-88E7-DEEF45ABC232, small LPT model
[ 2.776996] UBIFS: mounted UBI device 2, volume 0, name "firm0", R/O mode
[ 2.783746] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 2.792858] UBIFS: FS size: 7237632 bytes (6 MiB, 57 LEBs), journal size 1650688 bytes (1 MiB, 13 LEBs)
[ 2.802265] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 2.807313] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 28B4FA39-A856-4B39-8D0F-996D0C2183E7, small LPT model
[ 2.820914] UBIFS: background thread "ubifs_bgt3_0" started, PID 592
[ 2.852470] UBIFS: recovery needed
[ 2.875155] UBIFS: recovery completed
[ 2.878818] UBIFS: mounted UBI device 3, volume 0, name "log"
[ 2.884514] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 2.893644] UBIFS: FS size: 7237632 bytes (6 MiB, 57 LEBs), journal size 1650688 bytes (1 MiB, 13 LEBs)
[ 2.903022] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 2.908084] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 13FF4DCA-F17A-42CE-A91A-1BCF38124B00, small LPT model
[ 2.921465] UBIFS: background thread "ubifs_bgt0_0" started, PID 594
[ 2.952971] UBIFS: recovery needed
[ 3.027173] UBIFS: recovery completed
[ 3.030841] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[ 3.036831] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 3.045954] UBIFS: FS size: 94597120 bytes (90 MiB, 745 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[ 3.055582] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 3.060621] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 3535A866-5122-4B8D-B7B9-F062E23F9C13, small LPT model
rm: can't remove '/usr/bin/siglent/usr/mass_storage/U-disk*': No such file or directory
rm: can't remove '/usr/bin/siglent/usr/tmp/*_U-disk*': No such file or directory
[ 5.506012] Unhandled fault: external abort on non-linefetch (0x818) at 0x36f65380
Bus error
[ 5.531517] irq = 170
[ 5.542155] <<-GTP-INFO->> GTP driver installing...
[ 5.547193] <<-GTP-INFO->> GTP Driver Version: V2.4<2014/11/28>
[ 5.553042] <<-GTP-INFO->> GTP Driver Built@22:06:06, Apr 27 2018
[ 5.559169] <<-GTP-INFO->> GTP I2C Address: 0x14
[ 5.563875] 0-0014 supply vdd_ana not found, using dummy regulator
[ 5.570030] 0-0014 supply vcc_i2c not found, using dummy regulator
[ 5.576239] <<-GTP-INFO->> Guitar reset
[ 5.703956] <<-GTP-INFO->> IC Version: 928_1060
[ 5.714378] <<-GTP-INFO->> X_MAX: 1024, Y_MAX: 600, TRIGGER: 0x00
[ 5.733499] <<-GTP-INFO->> create proc entry gt9xx_config success
[ 5.739770] input: goodix-ts as /devices/virtual/input/input0
[ 5.745771] <<-GTP-INFO->> GTP works in interrupt mode.
[ 5.761546] gpib_usb_init
[ 5.764309] usbcore: registered new interface driver usb-gpib
/bin/sh: can't access tty; job control turned off
/usr/bin/siglent #
- Tell me I'm wrong. :-//
did you try the online python script? this is probably all you need . No downgrade required.
Is it possible to upgrade to SSA3032X without spending hard earned ducats? If yes could someone please point to the right Post# to start reading the process? Thanks
great, thank you!You need to change Refl to CAT in the script.
didn't load the ALL key
just the AMK, EMI and the 3032. Now 3.2GHz full span :)
tried the Refl key 2x; is invalid for some reason
I will try the key re-gen later. happy for now
thank you again
great, thank you!You need to change Refl to CAT in the script.
didn't load the ALL key
just the AMK, EMI and the 3032. Now 3.2GHz full span :)
tried the Refl key 2x; is invalid for some reason
I will try the key re-gen later. happy for now
thank you again
You have added the comment:-
"If there is a problem with AMK and Refl licenses, use CAT for AMK and Meas for Refl"
Shouldn't that be "...use CAT for Refl"?
Jepp, the mistake he made was the option.
# Options:
# CAT = AMK
# Meas = Refl
For AMK he must use CAT as an option also for Refl he must use Meas as an Option.
If he take this options everything is fine.
regards Chris
I received my SHA800A today and conducted some reverse engineering on the software. It seems that the software is based on the SSA5000A software, which suggests that the hardware is likely similar. It probably doesn't share the same design as the SVX1000X.SHA800A thread here:
Notice:
This firmware must be upgraded from v2.1.1.1 or later. If your analyzer has an earlier version, don’t
use this FW to update.
<?xml version="1.0" encoding="UTF-8"?>
<nsp_trends_info_root>
<device>
<language>english</language>
<pid>0x1301</pid>
<vid>0xf4ec</vid>
<product_type_1>SSA3075X</product_type_1>
<product_type_2>SSA3050X</product_type_2>
<product_type_3>SSA3032X</product_type_3>
<product_type_4>SSA3021X</product_type_4>
<product_type_5>SSA3015X</product_type_5>
<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>
#/bin/sh (as well as with #!)
export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:$PATH
export LD_LIBRARY_PATH=/lib:/usr/lib:$LD_LIBRARY_PATH
export USBDEV=`df -h | tail -1 | awk '{print $6}'`
for i in `seq 0 1 12`
do
nanddump -f ${USBDEV}/mtd${i} /dev/mtd${i}
if [ $? == 0 ]
then
echo SUCCESS dumping /dev/mtd${i} >> ${USBDEV}/SDS5KXDMP.log
else
echo ERROR dumping /dev/mtd${i} >> ${USBDEV}/SDS5KXDMP.log
fi
sleep 1
done
#/bin/sh
echo "startup_app.sh start++++++++++"
export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:$PATH
export LD_LIBRARY_PATH=/lib:/usr/lib:$LD_LIBRARY_PATH
#echo "qt path config"
export QT_PATH_ROOT=/opt/qt
export LD_LIBRARY_PATH=$QT_PATH_ROOT/lib:$QT_PATH_ROOT/lib/ts:$LD_LIBRARY_PATH
export QT_PLUGIN_PATH=$QT_PATH_ROOT/plugins
export FONTCONFIG_PATH=$QT_PATH_ROOT/share
export QT_QPA_PLATFORM=linuxfb:fb=/dev/fb0:size=1024x600:mmsize=223x125:rotation=0
export QT_QPA_GENERIC_PLUGINS=evdevtouch:/dev/input/event0
export QT_QPA_EVDEV_TOUCHSCREEN_PARAMETERS=/dev/input/event0
export LD_LIBRARY_PATH=/usr/bin/siglent:$LD_LIBRARY_PATH
export LANG=en_US.utf8
#for vnc upgrade ads residual+++++++++++++++++++++++++++++
echo "rm -f /usr/bin/siglent/usr/*.ADS"
rm -f /usr/bin/siglent/usr/*.ADS
rm -f /usr/bin/siglent/usr/*.CFG
rm -f /usr/bin/siglent/usr/*.ads
rm -f /usr/bin/siglent/usr/*.cfg
sync
#for vnc upgrade ads residual+++++++++++++++++++++++++++++
#for ads upgrade app, (space dependent)
if [ -f /usr/bin/siglent/usr/backup/upgrade_app1.sh ]; then
mount -o remount,rw /usr/bin/siglent
/usr/bin/siglent/usr/backup/upgrade_app1.sh
echo "/usr/bin/siglent/usr/backup/upgrade_app1.sh"
rm /usr/bin/siglent/usr/backup/upgrade_app1.sh -rf
echo "rm /usr/bin/siglent/usr/backup/upgrade_app1.sh -rf"
rm /usr/bin/siglent/usr/usr/upgrade/* -rf
echo "rm /usr/bin/siglent/usr/usr/upgrade/* -rf"
mount -o remount,ro /usr/bin/siglent
sync
fi
#for udisk upgrade , no firmdata0
if [ -d /usr/bin/siglent/usr/backup/config ]; then
mount -o remount,rw /usr/bin/siglent/firmdata0
cp -rpf /usr/bin/siglent/usr/backup/config/* /usr/bin/siglent/firmdata0/
echo "cp -pf /usr/bin/siglent/usr/backup/config/* /usr/bin/siglent/firmdata0/"
sync
mount -o remount,rw /usr/bin/siglent
rm /usr/bin/siglent/usr/backup/config -r
mount -o remount,ro /usr/bin/siglent
sync
mount -o remount,ro /usr/bin/siglent/firmdata0
fi
#for upgrade ads residual+++++++++++++++++++++++++++++
if [ -d /usr/bin/siglent/usr/usr/upgrade ]; then
rm /usr/bin/siglent/usr/usr/upgrade -rf
fi
/usr/bin/siglent/config_eth0.sh
sleep 1
portmap &
/usr/bin/siglent/Aladdin &
echo "startup_app.sh end++++++++++"
/usr/bin/siglent # export USBDEV=`df -h | tail -1 | awk '{print $6}'`
mount -o remount,rw ${USBDEV}
for i in `seq 0 1 9`
do
nanddump -f ${USBDEV}/mtd${i} /dev/mtd${i}
if [ $? == 0 ]
then
echo SUCCESS dumping /dev/mtd${i} >> ${USBDEV}/SSA3KXRDMP.log
else
echo ERROR dumping /dev/mtd${i} >> ${USBDEV}/SSA3KXRDMP.log
fi
sleep 1
done
/usr/bin/siglent # cat ${USBDEV}/SSA3KXRDMP.log
SUCCESS dumping /dev/mtd0
SUCCESS dumping /dev/mtd1
SUCCESS dumping /dev/mtd2
SUCCESS dumping /dev/mtd3
SUCCESS dumping /dev/mtd4
SUCCESS dumping /dev/mtd5
SUCCESS dumping /dev/mtd6
SUCCESS dumping /dev/mtd7
SUCCESS dumping /dev/mtd8
SUCCESS dumping /dev/mtd9
What does the VNA option in the keygen do? The Key is accepted as valid, but when I reboot it's still a SSA with no VNA features?
What does the VNA option in the keygen do? The Key is accepted as valid, but when I reboot it's still a SSA with no VNA features?
You self discovered the answer: nothing.
To get VNA you must crossflash to SVA.
Hello!All ^^ different HW to SVA1015X/SSA3015X Plus.
As I understood from the video, at 24:10 : https://youtu.be/gkLciTsjGZg?si=PxZobFicirJqfxck&t=1450 (https://youtu.be/gkLciTsjGZg?si=PxZobFicirJqfxck&t=1450)
Is Siglent significantly superior to Rigol ?? (Is Siglent much better than Rigol ??)
I want to purchase SSA3015X PLUS 1.5GHz
https://www.siglent.eu/product/2160699/siglent-ssa3015x-plus-1-5ghz-spectrum-analyzer-free-tg-license (https://www.siglent.eu/product/2160699/siglent-ssa3015x-plus-1-5ghz-spectrum-analyzer-free-tg-license)
Please tell me how it differs from SSA3021X 2.1GHz
https://www.siglent.eu/product/1137260/siglent-ssa3021x-2-1ghz-spectrum-analyzer-free-tg-license (https://www.siglent.eu/product/1137260/siglent-ssa3021x-2-1ghz-spectrum-analyzer-free-tg-license)
I mean the differences in the series in the prefix "PLUS"...
And the second question, can SSA3015X PLUS be hacked to SSA3032X Plus or even to SSA3075X Plus?
I'm sorry, I didn't understand you..SSA3000X are the earlier models whereas 3000X Plus versions and SSA3000X-R and SVA1000X are all touch screen capable.
I was asking what is the difference between SSA3021X and SSA3015X PLUS (SSA3021X PLUS, SSA3032X PLUS)?
Which series is better?
And I would also compare it with SVA1015X, what are the differences between SSA and SVA?
SSA3021X - 1.395$
SSA3015X Plus - 1.295$
SSA3021X Plus - 1.650$
SVA1015X - 1.690$
Thank you, so it makes sense to take SSA3015X Plus or SSA3021X Plus instead of SSA3021X ?
In the SSA3000X PLUS series , is the functionality exactly not cut down compared to SSA3000X ?
Is the SVA1015X series older than SSA3015X ?
And can you please explain what are the functions of VNA's and DTF and Modulation analysis? What are they for, examples?
I've never had a spectrum analyzer before and I don't know how to use it, and I don't understand this issue well. That's why I want to buy it to study this direction.
SSA3021X - 1.395$100% because of feature set and capabilities.
SSA3015X Plus - 1.295$
SSA3021X Plus - 1.650$
SVA1015X - 1.690$
Thank you, so it makes sense to take SSA3015X Plus or SSA3021X Plus instead of SSA3021X ?
In the SSA3000X PLUS series , is the functionality exactly not cut down compared to SSA3000X ?3000X is a very similar but older series and not touch/mouse capable and with lesser features.
Is the SVA1015X series older than SSA3015X ?These are the same HW and SVA models were released first in which VNA was an option for a short time then with a price change VNA was included as Std.
And can you please explain what are the functions of VNA's and DTF and Modulation analysis? What are they for, examples?Many VNA functions can be performed with a analyzer with TG and a return loss/reflection bridge however a full featured VNA mode provides better and more measurements.
I've never had a spectrum analyzer before and I don't know how to use it, and I don't understand this issue well.
SSA3021X Plus to say SSA3032X Plus -> Yes.
All others -> No.
Now I know, and I will take SSA3021X Plus to hack it to SSA3032X Plus.
Andrey, sorry but you have even more study to do here:Now I know, and I will take SSA3021X Plus to hack it to SSA3032X Plus.
You can even do better: go from SSA3021X Plus to SVA1032X.
Is the SSA3121Xplus still recommended, are there any known issues with it?
Ah, 0, not 1...was too late in the evening for me. :D
The price for the 3021plus is is the maximum in this case, but I'm not yet too familiar with it and don't do enough with it.
If that changes, you can always upgrade to a better device.
Hello! I purchased SSA3021X Plus, I want to flash it, hack it to SSA3032X Plus.Go study here:
But here they write that it is possible to hack better, to flash to SVA1032,
but I still can't figure out what is better or worse than SVA1032 compared to SSA3032X Plus..
See my edited msg.
If you're not thinking in going up to a FPC1500 (Rudi's opinion (https://www.eevblog.com/forum/testgear/rohde-schwarz-fpc1500-(fpc-com2-kit)-or-siglent/msg4231192/#msg4231192)) which costs double, I think there is no other choice.We should add, that Rudi talked about the unhacked SSA3000X, when he stated that he wanted a VNA (Vector Network Analyzer) which the FPC1500 is, whereas the unhacked SSA3000X is just an SA, which can be only turned into an SNA (Scalar Network Analyzer) by means of an additional bridge or directional coupler.
And S21 measurements. ;)If you're not thinking in going up to a FPC1500 (Rudi's opinion (https://www.eevblog.com/forum/testgear/rohde-schwarz-fpc1500-(fpc-com2-kit)-or-siglent/msg4231192/#msg4231192)) which costs double, I think there is no other choice.We should add, that Rudi talked about the unhacked SSA3000X, when he stated that he wanted a VNA (Vector Network Analyzer) which the FPC1500 is, whereas the unhacked SSA3000X is just an SA, which can be only turned into an SNA (Scalar Network Analyzer) by means of an additional bridge or directional coupler.
But if an SSA3000X Plus is hacked to an SVA1000X, it obviously becomes a VNA as well and doesn't need any external devices to make S11 measurements.
The Rigol analyzer is already a VNA, so where's the fun in that... ;)
That suggested Rigol is realtime! A totally different beast.
Anyone successfully adjust the reference oscillator in a SSA3000x Plus? I know there was a calib directory in the X (non Plus), but that does not appear to exist in the Plus version.
So the SSA3015X+, is that already at it's hardware limit and it's not upgradable ?Not BW. ;)
https://www.siglent.eu/product/1150679/siglent-f503me-4-5-ghz-n-male-type-vna-calibration-kit (https://www.siglent.eu/product/1150679/siglent-f503me-4-5-ghz-n-male-type-vna-calibration-kit)
... do they want 399 euros? Is this some kind of joke?
Seems a good price.
Most of these cheap sets are crap, just for the bin. The threads are bad, the resistor is with large inductivity and ...Seems a good price.
Here is a good adequate price. :)
https://aliexpress.ru/item/1005006046277389.html
In general, is the VNA function needed only for testing antennas?No you can do more with the SVA models.
After all, you can use an RF Bridge for this?
I'm sorry, but I can't figure out what the advantages and differences of the SSA3032X Plus and SVA1032X are ...Your call, same HW.
Whether it's worth flashing the device as SVA or limiting it to SSA.
And what is the Refl option?Reflection measurements are standard in SVA models and enhanced to provide Smith charts, Mag Loss, SWR and Phase of which you can overlay all using the 4 traces available.
I noticed that it is on SSA, but it is no longer on SVA.
But DTF and VNA options have been added to SVAThese are standard in SVA models now whereas when SVA1015X was first released they were optional.
Any idea ?
If you already have the files, don't touch them. Continue with business as usual.
https://www.siglent.eu/product/1150679/siglent-f503me-4-5-ghz-n-male-type-vna-calibration-kit (https://www.siglent.eu/product/1150679/siglent-f503me-4-5-ghz-n-male-type-vna-calibration-kit)
... do they want 399 euros? Is this some kind of joke?
Seems a good price.
Compare e.g. with this one, which is a good 6 GHz product https://coppermountaintech.com/calibration-kits/n612-calibration-kit/ (https://coppermountaintech.com/calibration-kits/n612-calibration-kit/). And compare with Keysight 85032E, that sells online "starting at 1299 U$D".
hello, i have a new siglent ssa3021x+. i am interested in unlocking it. i do not want to flash it to a sva. the firmware is 3.2.2.6.0r8. 20230524-1501. is the procedure still good, or is it no longer possible? thanks.
What are the 3021 thru 3075 keys for?Plus models.
Sorry for asking, but I am not familiar with downgrading from a 3075 to a 3032. I thought I had read this blog well but there are a lot of pages to read. I only heard about downgrading of firmware. Can you please explaine a little to make it more clear to me ?
Exactly that.Only what study of the X-R range datasheet tells me.
And again, you can't really go wrong with activating the additional options with the keygen. But increasing the bandwidth can mean that the bandwidth increases, but that this is not a calibrated function anymore because of missing calibration by the factory.
Maybe Tautech knows more.
The first thing everyone seems to do is "expand" the bandwidth.
Question:
Is this really necessary, if I buy a model with say 2.1Ghz now, am I "missing out" on anything if I don't upgrade it to X.XGhz?
The first thing everyone seems to do is "expand" the bandwidth.
Question:
Is this really necessary, if I buy a model with say 2.1Ghz now, am I "missing out" on anything if I don't upgrade it to X.XGhz?
Increasing the bandwidth of my scope and AWG made them vastly more useful.
For the 2.1GHz spectrum analyser, 1GHz would probably be enough for anything I've done so far. Increasing ihe bandwidth to 3.2 GHz was a bit of harmless fun.
No, it can't.
The data stream is much too high.
You need a propper TV field meter to be able to do that.
Let me know if you want some suggestions on capable TV field meters and/or other options.
When it comes to VNA's the calibration is everything. Its not cheap to make a good OSL with a known and true 42dB return loss into the GHz. There are books just on the calibration process alone. This one is in my amazon wish list
I picked up this OSL, very good quality but not too bad a price for a home lab https://rftestparts.com/ (https://rftestparts.com/)
I would really like one with female ends as well.
No.
When it comes to VNA's the calibration is everything. Its not cheap to make a good OSL with a known and true 42dB return loss into the GHz. There are books just on the calibration process alone. This one is in my amazon wish list
I picked up this OSL, very good quality but not too bad a price for a home lab https://rftestparts.com/ (https://rftestparts.com/)
I would really like one with female ends as well.
Can this be used as a RLB??
Ok, thanks. I guess that is off my short list for another RLB.It was and I got one when I got my first SSA3032X.....probably 2018 ?
Unfortunately what I choose many years ago for my SA was not the one Siglent offered since for some reason or another I never knew they offered one. :palm:
To make matters worse, I paid $200 over what Siglent is selling theirs now, but at least, it is US made. ;)
My SA is the original 'X' version. Maybe it wasn't offered in 2017?? ???
I see there is a F/W update for the 'X' version which I didn't expect, especially after this amount of time since it was introduced (2016). My current version is v1.3.9.7.You are actually a few versions behind and there are update steps required to get to the latest.
I just received my SSA3015X Plus from Saelig and the cal cert says first time use was 9-2-2019 and next cal is due 9-2-2020 which means cal has expired. Is this right to get a new one with expired cal cert?
You are actually a few versions behind and there are update steps required to get to the latest.There is only a version 1.3.9.8 after 1.3.9.7 that I'm running and before the current 1.3.9.10 issued 2/25/24. Unless I missed a v1.3.9.9 which I didn't see on that page you linked. ???
They are described in a PDF that comes in the FW package so a quick study up will reveal the steps needed.
You can find everything you need here:
https://int.siglent.com/download/firmwares/?ProId=29
V2.1.1.4 is the latest SSA3000X version.You are actually a few versions behind and there are update steps required to get to the latest.There is only a version 1.3.9.8 after 1.3.9.7 that I'm running and before the current 1.3.9.10 issued 2/25/24. Unless I missed a v1.3.9.9 which I didn't see on that page you linked. ???
They are described in a PDF that comes in the FW package so a quick study up will reveal the steps needed.
You can find everything you need here:
https://int.siglent.com/download/firmwares/?ProId=29
Sorry, too many numbers. I missed the v2xxx part, I was only looking at the last digit(s). :-//Did you try ?
Well, those v2 won't work with the non Plus version which I have. I see the size of the v2 file is 4x larger than the v1. :o
It is old mistake when these both models, X and Xplus are mixed here in same thread. If later Siglent produce different different models where HW etc is very different, even if model number is nearly same etc. It is best to keep both tightly in totally separate threads for avoid confusion and mess what can also see here in this thread many places.
If your analyzer has an earlier version（V1.x.x.x）, it can not upgrade to” V2.x.x.x” version and
the “V2.x.x.x” version also can not downgrade to the earlier version
The v2.x FW is for a completely different HW platform!Yep, I bought my SSA3021X in 2019, and it can only upgraded with v1.x FW. It does not accept v2.x FW.
There is no issue with the increased filesize of the FW - the new HW platform has simply a bigger flash. No problem with that!
In other words this means:
1) The original SSA3000X hardware platform has been discontinued.
2) The new SSA3000X hardware platform is compatible with the SSA-P/SSA-R/SVA hardware and shares the same FW base, which uses the same main application. This makes sense, because it reduces manufacturing cost.
3) It does not make much sense to buy the SSA3000X, since you can get for little more money the Plus version. I think the SSA3000X is kept to just complete the portfolio and to be competitive on the cheapest end.
I haven't tried, but I would expect that the device with v1.x FW would not accept the v2.x FW and vice-versa.
The firmware update instructions pdf states:I already posted that in a previous post in red !
2. If your analyzer has an earlier version（V1.x.x.x）, it can not upgrade to” V2.x.x.x” version and
the “V2.x.x.x” version also can not downgrade to the earlier version
So I guess "SSA3000X_Firmware_V1.3.9.10 (Release Date 02.05.24 )" is the save way to go.
I think it was created spontaneously by some singularity in the time and space fabric...You must of been a 'Fringe' fan............. :-+
Not the same series as theses SSA's !
After sending DEBTTT via SCPI I can telnet to port 23 with "root" PW "1234ding"I enabled telnet and the instrument responds to PuTTY, but I'm unable to log in as root. My machine has 3.2.2.6.0R8 firmware and 01.00.00 hardware versions, for which I haven't been able to find any posts in this thread.