EEVblog Electronics Community Forum

Products => Test Equipment => Topic started by: tautech on August 01, 2017, 04:54:02 am

Title: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tautech on August 01, 2017, 04:54:02 am
Models of 200, 350 and 500 MHz, 2 channels and 2.4GSa / s sampling rate with 16 bit vertical resolution.

(https://siglentna-qwavztc8hvq2w.stackpathdns.com/wp-content/uploads/2017/11/SDG6052Xmain.png)

Sine wave amplitude:
20 Vpp ? 40 MHz, high impedance load
10 Vpp 40 MHz to 120 MHz (inclusive), high impedance load
5 Vpp 120 MHz ~ 160 MHz (included), high impedance load
3 Vpp 160 MHz to 350 MHz (inclusive), high impedance load
1.28 Vpp above 350MHz

Square wave to 120 MHz, risetime 2.4 ns max.

196 built-in arbitrary waveforms.
Arbitrary memory depth 2-20 Mpts

Webpage
https://int.siglent.com/products-overview/sdg6000x/ (https://int.siglent.com/products-overview/sdg6000x/)
http://www.siglentamerica.com/pdxx.aspx?id=6464&T=2&tid=16 (http://www.siglentamerica.com/pdxx.aspx?id=6464&T=2&tid=16)

Datasheet:
http://www.siglentamerica.com/USA_website_2014/Documents/DataSheet/SDG6000X_datasheet.pdf (http://www.siglentamerica.com/USA_website_2014/Documents/DataSheet/SDG6000X_datasheet.pdf)

Review from Shahriar:
https://youtu.be/_2LcpH_JxYM (https://youtu.be/_2LcpH_JxYM)
Title: Re: Siglent SDG6000 series 200-500 MHz AWG's
Post by: Wuerstchenhund on August 01, 2017, 09:22:16 am
Nice! The specs look pretty good, and it can do PRBS patterns and I/Q modulation as well.

Any ideas when these devices will be available outside China? And what the targeted RRP is for the various versions?

If they get the price right then I'd consider the 500Mhz variant. Hell, I'd even be willing to play beta tester for this thing if that means I could get one at reasonable conditions  ;)
Title: Re: Siglent SDG6000 series 200-500 MHz AWG's
Post by: simone.pignatti on August 01, 2017, 09:36:19 am
Siglent will take 4 to 6 months before shipping out of the domestic market. Or at least this is what they use to do.
Title: Re: Siglent SDG6000 series 200-500 MHz AWG's
Post by: simone.pignatti on August 01, 2017, 09:46:49 am
It seems there will be a SDG6000X-E version too starting at 160MHz
http://www.siglent.com/function-arb-generator/SDG6000X-E (http://www.siglent.com/function-arb-generator/SDG6000X-E)
Only for domestic market, will not be available out of China
Title: Re: Siglent SDG6000 series 200-500 MHz AWG's
Post by: Tsippaduida on August 26, 2017, 12:05:23 pm
This series actually interests me, no need to buy a Windows-machine (or license) to get wide range of functions out of this. Currently I have no need for fancy AVG, but you never know.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: MrW0lf on November 03, 2017, 03:59:49 pm
https://www.youtube.com/watch?v=RGZkpMaGW-U (https://www.youtube.com/watch?v=RGZkpMaGW-U)
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: Plasmateur on November 04, 2017, 11:44:50 pm
Released in the Chinese marketplace but as yet no western market release date or pricing.
Models of 200, 350 and 500 MHz, 2 channels and 2.4GSa / s sampling rate with 16 bit vertical resolution.

(http://www.siglent.com/Chinese_website2014/picture/SDG6000X/6000xmain.png:image)

Sine wave amplitude:
20 Vpp ? 40 MHz, high impedance load
10 Vpp 40 MHz to 120 MHz (inclusive), high impedance load
5 Vpp 120 MHz ~ 160 MHz (included), high impedance load
3 Vpp 160 MHz to 350 MHz (inclusive), high impedance load
1.28 Vpp above 350MHz

Square wave to 120 MHz, risetime 2.4 ns max.

196 built-in arbitrary waveforms.
Arbitrary memory depth 2-20 Mpts

Datasheet: (Chinese)
http://www.siglent.com/Chinese_website2014/Datasheet/SDG6000X_DataSheet_DS0206E-C01A.pdf (http://www.siglent.com/Chinese_website2014/Datasheet/SDG6000X_DataSheet_DS0206E-C01A.pdf)

Very interested in one of these for my lab at work, as the SDG2042X has been pretty good to me except for that one thing they couldn't fix.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tautech on November 05, 2017, 12:47:38 am
Released in the Chinese marketplace but as yet no western market release date or pricing.
Models of 200, 350 and 500 MHz, 2 channels and 2.4GSa / s sampling rate with 16 bit vertical resolution.

(http://www.siglent.com/Chinese_website2014/picture/SDG6000X/6000xmain.png:image)

Sine wave amplitude:
20 Vpp ? 40 MHz, high impedance load
10 Vpp 40 MHz to 120 MHz (inclusive), high impedance load
5 Vpp 120 MHz ~ 160 MHz (included), high impedance load
3 Vpp 160 MHz to 350 MHz (inclusive), high impedance load
1.28 Vpp above 350MHz

Square wave to 120 MHz, risetime 2.4 ns max.

196 built-in arbitrary waveforms.
Arbitrary memory depth 2-20 Mpts

Datasheet: (Chinese)
http://www.siglent.com/Chinese_website2014/Datasheet/SDG6000X_DataSheet_DS0206E-C01A.pdf (http://www.siglent.com/Chinese_website2014/Datasheet/SDG6000X_DataSheet_DS0206E-C01A.pdf)

Very interested in one of these for my lab at work, as the SDG2042X has been pretty good to me except for that one thing they couldn't fix.
I'd like to say that I can tell you more about the SDG6000X series but I passed on beta testing one as I wanted to focus on the 4 ch X-E that was offered at the same time too.  :scared:
Last I heard Wuerstchenhund might be getting one to beta test but Dave has unfortunately banned him from the forum so we've not likely to get much unless he PM's one of us. Last I looked at his profile he was keeping an eye on us all. He gave Siglent a good bit of stick over the years so I hope he makes some contribution to their products.

WRT 2042X, I'll have some more in a week or two and I'll reinvestigate the thing you wanted fixed/changed/added.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: simone.pignatti on November 05, 2017, 03:10:34 pm
Last Friday I went trough the specs of the Chinese PDF, it seems the 500MHz will be kind of unique product. It is not easy to create the best test set-up, for sure high frequency calibrate coaxial cables and at least a 1GHz bandwidth oscilloscope with high sampling rate and accurate vertical resolution. I'm not sure I'll be ready to test it before Xmas even if I will get then unit as soon as it will be available in EU.  :(
However I'm available for specific tests, if you are interested just drop me a line with your test requirement.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: simone.pignatti on November 06, 2017, 08:45:51 am
The European public launch for the SDG6000X is scheduled for November the 16th
It seems it will carry a surprise surprise for all of us ... the frequency maybe hackable as it is for the SDG2000X  :-+
Can't wait  :popcorn:
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: gby on November 11, 2017, 03:23:01 pm
Go an email Nov 10 from Circuit Specialists in the US showing  these generators up for order.
SDG6022X 200MHz $1,499 (back order ships 11/29/17)
SDG6032X 350Mhz  $3,339 (ships in 1-2 business days)
SDG6052X 500Mhz $5,299 (ships in 1-2 business days)

A fair bit pricier than the SDG2000x series but if you need the higher frequencies still probably a reasonable value.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: alreadystarted on November 13, 2017, 08:26:23 pm
I see this page on the English language site mentions a SDG6000X-E series.  But there's no listed devices from that series.  That's pretty interesting.  Anyone have more info on that?  Possibly from Chinese market?

The only details are just a note on rise times:
The rise/fall times of the SDG6000X can be set to as low as 1 ns (SDG6000X-E series as low as 2 ns), comparable to much higher – priced units.

http://www.siglent.com/ENs/qyxwxx.aspx?id=2217&sid=25 (http://www.siglent.com/ENs/qyxwxx.aspx?id=2217&sid=25)
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: simone.pignatti on November 13, 2017, 09:25:26 pm
I see this page on the English language site mentions a SDG6000X-E series.  But there's no listed devices from that series.  That's pretty interesting.  Anyone have more info on that?  Possibly from Chinese market?

The only details are just a note on rise times:
The rise/fall times of the SDG6000X can be set to as low as 1 ns (SDG6000X-E series as low as 2 ns), comparable to much higher – priced units.

http://www.siglent.com/ENs/qyxwxx.aspx?id=2217&sid=25 (http://www.siglent.com/ENs/qyxwxx.aspx?id=2217&sid=25)

SDG6000X-E only for domestic market

EU launch was planned for the 16th not sure why is already online.
For this reason on our website we have activated the 3 models and the IQ option too so you can check European pricing.
All models available.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: bson on November 14, 2017, 12:09:23 am
All info is on all Siglent web sites now.
US:
http://www.siglentamerica.com/pdxx.aspx?id=6464&T=2&tid=16 (http://www.siglentamerica.com/pdxx.aspx?id=6464&T=2&tid=16)
Nice...  :-+
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: Qw3rtzuiop on November 15, 2017, 01:32:27 pm
Which scope is used in that video? Afaik there is no siglent scope with that high bandwidth. There is just a branding Siglent powered by LeCroy. Can we also expect a high bandwidth scope from siglent?
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: simone.pignatti on November 15, 2017, 01:53:48 pm
SDS3000 or LeCroy WaveSurfer 3000 (same unit)
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: bson on November 16, 2017, 07:10:02 am
It's not a WaveSurfer 3000 - it lacks the ProBus probe connectors and seems to have only basic BNC inputs.  Otherwise looks very similar, though white instead of black.  Interesting that the Siglent scope runs LeCroy firmware.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: simone.pignatti on November 16, 2017, 07:30:17 am
I just checked again and I confirm is the SDS3000 (white version of the WaveSurfer 3000)
If you jump to 1’34” you can see the logic pod on the right.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: rf-loop on November 16, 2017, 08:38:43 am
It's not a WaveSurfer 3000 - it lacks the ProBus probe connectors and seems to have only basic BNC inputs.  Otherwise looks very similar, though white instead of black.  Interesting that the Siglent scope runs LeCroy firmware.

It looks like  "alternative truth" aka "trumth" is so popular that it has to penetrate everywhere. Or how this must think?

Checking the facts.

TeledyneLecroy WaveSurfer 3000  is manufactured by Siglent and  is same as Siglent SDS3000.
Yes labels are different and outer case plastic color is different.

No ProBus in Siglent?  Where from this information come?
Look this image. Only BNC's ?

Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tautech on November 16, 2017, 08:42:45 am
Which scope is used in that video? Afaik there is no siglent scope with that high bandwidth. There is just a branding Siglent powered by LeCroy. Can we also expect a high bandwidth scope from siglent?
Maybe next year.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: simone.pignatti on November 16, 2017, 08:54:11 am
It's not a WaveSurfer 3000 - it lacks the ProBus probe connectors and seems to have only basic BNC inputs.  Otherwise looks very similar, though white instead of black.  Interesting that the Siglent scope runs LeCroy firmware.

It looks like  "alternative truth" aka "trumth" is so popular that it has to penetrate everywhere. Or how this must think?

Checking the facts.

TeledyneLecroy WaveSurfer 3000  is manufactured by Siglent and  is same as Siglent SDS3000.
Yes labels are different and outer case plastic color is different.

No ProBus in Siglent?  Where from this information come?
Look this image. Only BNC's ?
The probus in next to each BNC. Siglent and LeCroy are exactly the same.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: rf-loop on November 16, 2017, 10:23:58 am
It's not a WaveSurfer 3000 - it lacks the ProBus probe connectors and seems to have only basic BNC inputs.  Otherwise looks very similar, though white instead of black.  Interesting that the Siglent scope runs LeCroy firmware.

It looks like  "alternative truth" aka "trumth" is so popular that it has to penetrate everywhere. Or how this must think?

Checking the facts.

TeledyneLecroy WaveSurfer 3000  is manufactured by Siglent and  is same as Siglent SDS3000.
Yes labels are different and outer case plastic color is different.

No ProBus in Siglent?  Where from this information come?
Look this image. Only BNC's ?
The probus in next to each BNC. Siglent and LeCroy are exactly the same.

I know this of course.
 
But @bson  "know" the "alternative truth".
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: JPortici on November 16, 2017, 10:50:42 am
Which scope is used in that video? Afaik there is no siglent scope with that high bandwidth. There is just a branding Siglent powered by LeCroy. Can we also expect a high bandwidth scope from siglent?
Maybe next year.

hopefully with more horsepower and capacitive touch instead of that crappy resistive one.. it's been a real pain to use that lecroy
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tautech on November 17, 2017, 09:12:31 am
Which scope is used in that video? Afaik there is no siglent scope with that high bandwidth. There is just a branding Siglent powered by LeCroy. Can we also expect a high bandwidth scope from siglent?
Maybe next year.

hopefully with more horsepower and capacitive touch instead of that crappy resistive one.. it's been a real pain to use that lecroy
I didn't try the touch screen when I was at the Siglent factory 3 years back, only the physical controls, however I don't hear of negative comments of the SDG2000X AWG touch screen so one would imagine any touch interface for a new high BW Siglent DSO will follow the experience gained with the popular SDG2000X series.

https://www.eevblog.com/forum/testgear/siglent's-new-products-sds3000-series-oscilloscopes/msg558936/#msg558936 (https://www.eevblog.com/forum/testgear/siglent's-new-products-sds3000-series-oscilloscopes/msg558936/#msg558936)
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: JPortici on November 17, 2017, 11:32:15 am
well, screen is about twice as big..
in the lecroy we demoed the touchscreen was so bad that you had to press too hard to use it and when you didn't move your finger the cursor would move frenetically. with a stylus, not so bad but at that point i'd rather use a mouse thank you very much :(
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: smarteebit on November 19, 2017, 07:12:51 am
Has anyone got the AWG? Any review or comment?
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: emax on November 22, 2017, 07:40:27 pm
Batronix Germany has them on stock and delivers:

https://www.batronix.com/versand/siglent/SDG6000X.html (https://www.batronix.com/versand/siglent/SDG6000X.html)


PS: The SDG6022X is out of stock now. That was a short pleasure.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: simone.pignatti on November 22, 2017, 07:43:01 pm
We also got delivered them today and already made an unboxing video on YouTube.
Next week a video testing the 500MHz with an oscilloscope   :-+
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: emax on November 22, 2017, 07:49:14 pm
Hi Simone,

I'am currently sitting in the office in Trento, maybe you're not so far away ?
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: simone.pignatti on November 22, 2017, 07:51:30 pm
We are in Bologna. People are welcome to come to our office and test all kind of equipment.
So yes, come for some test and tortellini :)
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: emax on November 22, 2017, 08:00:39 pm
Pasta, oh yes, I love it  :-+

Bologna is just around the corner (at least compared to eevblog), around 200Km from Trento - which you do of course know yourself ;-)
 
But no way, I'm on the job here - though I'll keep it in mind. Both, the shop and the tortellini!  ^-^

Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: simone.pignatti on November 22, 2017, 08:01:08 pm
Tomorrow morning I will be able to test the SDG6052X with a LeCroy HDO6104A 12 bit 1GHz
I should be able to test the sine wave. I’ll do my best to make a short video and print screen to share.
Please send me test request before tomorrow morning!
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: simone.pignatti on November 22, 2017, 08:03:45 pm
Pasta, oh yes, I love it  :-+

But no way, I'm on the job here - though I'll keep it in mind. Both, the shop and the tortellini!  ^-^
Are you in a electronic lab? Let me know if you like equipment delivered to your office for a test.
Ciao
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: emax on November 22, 2017, 08:04:13 pm
Request: Maximum sinewave voltage across entire frequency-range.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: emax on November 22, 2017, 08:06:21 pm
Are you in a electronic lab? Let me know if you like equipment delivered to your office for a test.

No, I am a software architect, not even embedded. But doesn't matter: I am in the lucky situation to do electronics just for fun. :-)

But thank you anyway, very kind offer.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: simone.pignatti on November 23, 2017, 11:28:51 am
Check this image! Video coming in few minutes.

Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: simone.pignatti on November 23, 2017, 11:55:31 am
Forgive me for any mistake I could have done.

https://youtu.be/DpxAsNBt-hY
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: dpenev on November 23, 2017, 06:35:11 pm
Hi simone.pignatti,

Thank you for the measurements.
Does you scope has 50 Ohm input? If yes please measure as you set 50 Ohm at both generator and the scope.

High impedance termination of your cable is not very good for this kind of measurement you have done.

Also it will be nice if you can hook spectrum analyzer and show spectrum purity around single tone.

Dimitar

 
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: simone.pignatti on November 23, 2017, 06:39:17 pm
Yes. Did it after the video. Almost same results!
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: dpenev on November 23, 2017, 06:58:26 pm
If i understand the SDG6052X specification right
we should expect -3dB drop at 500MHz with 50 Ohm termination

Or you should see only 30% level drop switching 0.5Vpp sine wave from 10MHz into 500MHz     
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: smarteebit on November 27, 2017, 02:14:50 am
Hi simone.pignatti,

Thank you for the measurements.
Does you scope has 50 Ohm input? If yes please measure as you set 50 Ohm at both generator and the scope.

High impedance termination of your cable is not very good for this kind of measurement you have done.

Also it will be nice if you can hook spectrum analyzer and show spectrum purity around single tone.

Dimitar

 

+1.

The sine wave looks in good shape while the the amplitude is obviously not in spec. I think this is caused by the 1M input impedance setting on the scope. Reflection happens on the scope input port if it is not 50ohm impedance, and this may introduce huge amplitude distortion in high frequency.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: rf-loop on November 27, 2017, 06:45:24 am
This is totally wrong way to measure signal generator amplitude flatness and accuracy from low frequencies up to 500MHz. There is all wrong. Totally. Even if you connect external 50ohm terminator to oscilloscope input it is wrong. This oscilloscope have 50ohm internal selectable impedance but even if there is oscilloscope internal 50ohm input many times they are not at all well enough for accurate amplitude flatness measurements. Because many times they are not enough accurate 50ohm impedance over whole frequency band. Oscilloscope specs say only -3dB @ 50ohm without more detailed data. Also this cable looks like some audio quality coaxial.

About external feed thru terminator (what do not with this oscilloscope exept if want go over oscilloscope specified max level with its internal 50ohm) connected to oscilloscpe 1Mohm example 16pF input (what in real world have all three: resistance, capasitive reactance and also some inductive reactance.  Result is far away from 50ohm if look 500MHz (problems start in practice when we go roughly saying over 100MHz  and more and more out of order what higher freq we go.  If it is 50ohm terminator with coaxial T - this is most crap way. Specially if terminator is cheap "Ethernet network grade crap terminator".  Without perfect impedance match you work with standing waves what amplify your signal with some frequency anmd attenuate with some frequency, dpending these waves phase. Also these reflected return to generator output may affect its ALC depending how it is done some generators.

Fun side note about this oscilloscope. Sad that this level of scope have this kind of trigger jitter. Visible around video time position 12.15. Do they have at all fine interpolation for accurate positioning. Also there was linear interpolation. Sinc interpolation is better for sinewave like signals. 

For good level flatness measurements you need different tools. 500MHz is not anymore "audio".
Rough measurements you can do using enough good and trusted SA, also it can show  something about sinewave quality. If you claim from oscilloscope screen that sinewave quality is very very good it is bit loosy to say so.  Simply, it is difficult to see it from oscilloscope screen, exept if we talk about very poor sinewave what have very high levels of harmonics or other impurities. Example if there is second harmonic.
Think we simply combine 500MHz 0dBm  sinewave  and then 1000MHz -30dBm sinewave and this combined wave you connect to oscilloscope. What you see. Looks like quite pure 500MHz sinewave. How about if this, 500MHz sine,  1000MHz (500MHz 2. harmonic) is -20dBm and then 3. harmonic (1500MHz) is example -40dBm. Still you can see it is quite nice looking sine shape in oscilloscope screen. But in reality, it is quite poor.
 
Just for info so that random reader do not need calculate: With 500MHz,  16pF reactance is 19.9 ohms!
(16pF is because in this example it is nominal 1M input capacitance with this named oscilloscope.)



Summarized briefly:
This video do not tell anything about SDG6000 amplitude accuracy or flatness or sinewave quality.
It can be worse or better or what ever. This test is faulty for this purpose.
But, other ways still very nice to see this LeCroy model and this Siglent model live in video.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: simone.pignatti on November 27, 2017, 07:13:01 am
Hi rf-loop , thanks for your comment. Yes my test setup wasn't the best and as stated I had very limited time. The idea was to show the unit working.
We are collecting better quality cables and will perform new tests in the short future to be shared.
However I was well impressed by the sine wave shape, in the past I tried other units and when generating the sine wave the results (already at half of the stated max value) wa horrible. Thanks again for helping with your experience!
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: rf-loop on November 27, 2017, 08:23:28 am
The idea was to show the unit working.
We are collecting better quality cables and will perform new tests in the short future to be shared.
However I was well impressed by the sine wave shape, in the past I tried other units and when generating the sine wave the results (already at half of the stated max value) wa horrible.

Yes, it was nice to see this equipment live in video.

But, oscilloscope, even with good signal pathway from generator to scope, is wrong way to characterize  signal generator amplitude flatness over whole frequency range from LF to 500MHz.  First thing is oscilloscope itself flatness. Other thing is inaccuracy with transmission from signal gen to oscilloscope.

One good instrument for flatness measurement is wide band good power meter. Something like example Keysight U2004A  power meter or some other like this.  (with these need note that they measure total, including harmonics because they are wide band power meters. With selective level receivcers can walk over this. ) Also many spectrum analyzers are much better flatness than most of oscilloscopes.
If you have there Siglent SSA3000X you can use it. It give typically better than 1dB accuracy and now you see also more details about sine wave quality.  If you need good RF cables with good connector. Example with Huber-Suhner or Rosenberger can not go very wrong.   (there is also other goods and after then tons of total crap cables with crap connectors. Mostly these cheap crap (even if they looks like good) are useless because you can not trust anything and all tests are  just  more bad as weakest part of test setup because total error is sum of all errors and all errors can be just worst side position - or not.

10MHz is easy. 100MHz need bit more. 500MHz need really think RF. 1GHz and over, all fun magick start where 8nH inductance reactance is 50ohm and this kind of inductance is example 19mm long and 5mm thick straight copper rod. ;)
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: Plasmateur on December 04, 2017, 05:42:11 pm
Does this pretty much have the same functionality as the SDG2000X series?

Would it be possible to do both a burst and sweep?

1.) Flat/no signal.
2.) send SDG6000X a trigger
3.) SDG sends a signal beginning at some phase and sweeps from X frequency to Y frequency.



Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: dpenev on December 15, 2017, 10:34:23 pm
I have probed the sine wave flatness of the SDG6052X in the whole frequency band
using SSA3021X and relatively good coax.

My results:
1MHz     +0.08dBm
100MHz  -0.03dBm
200MHz  -0.17dBm
300MHz  -0.15dBm
350MHz  -0.39dBm
400MHz  -0.11dBm
450MHz  -0.23dBm
500MHz  -0.29dBm
 
Some of the deviation is due to the generator but also some due to the cable and due to analyzer.
So the instrument seems to match its specified amplitude flatness +/-0.3dB

So far so good
Dimitar
 
 
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: JohnG on January 16, 2018, 06:35:08 pm
Has anyone else had any experience with one of these? I have an SDG2042X, but am likely to need both higher frequency operation and faster rise/fall times.

Also, wondering if it has essentially the same command set as the SDG2000x series, since I have some ATE software that presently controls the SDG2042x and would like to avoid changing it.

Thanks,
John
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tautech on January 16, 2018, 07:03:41 pm
Has anyone else had any experience with one of these? I have an SDG2042X, but am likely to need both higher frequency operation and faster rise/fall times.

Also, wondering if it has essentially the same command set as the SDG2000x series, since I have some ATE software that presently controls the SDG2042x and would like to avoid changing it.

Thanks,
John
I'm going to get one sometime in the next month or so but simone.pignatti should be able to give you some info as he has one.
There's a new SDG series programming guide that includes the new commands for the added features in the 6kX models. The basic command set will be the same.
Here's the new programming manual:
http://siglenteu.com/dow.aspx?u=aHR0cDovL3d3dy5zaWdsZW50YW1lcmljYS5jb20vVVNBX3dlYnNpdGVfMjAxNC9Eb2N1bWVudHMvUHJvZ3JhbV9NYXRlcmlhbC9TREdfUHJvZ3JhbW1pbmdHdWlkZV9QR19FMDNCLnBkZg%3d%3d (http://siglenteu.com/dow.aspx?u=aHR0cDovL3d3dy5zaWdsZW50YW1lcmljYS5jb20vVVNBX3dlYnNpdGVfMjAxNC9Eb2N1bWVudHMvUHJvZ3JhbV9NYXRlcmlhbC9TREdfUHJvZ3JhbW1pbmdHdWlkZV9QR19FMDNCLnBkZg%3d%3d)
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: Deuze on January 22, 2018, 07:42:51 am
Got mine after a long waiting.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tautech on January 22, 2018, 08:23:24 am
Got mine after a long waiting.
Model ?
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: Ghislain on March 28, 2018, 07:28:56 am
This is the video review I personally like the most so far  :D
https://www.youtube.com/watch?v=Fzq68nXrWLM (https://www.youtube.com/watch?v=Fzq68nXrWLM)
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: emax on April 16, 2018, 12:46:43 pm
I have a question related to the "pulse" parameter settings.

The manual (and the monitor as well) states that (besides amplitude, offset, load etc.) you can set frequency or period, rise- and fall time, and pulse-width or dutycycle.

With these parameters, I would have guessed, that the horizontal shape of the pulse is completely described. But there is another parameter called "delay". The manual explains how to set this, all nice and dandy. But I haven't found an axplanation what the delay is and where in the pattern it resides.

So I guess that this a unique one-time delay at the very beginning of the output. Or did I miss something?
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: siglent5 on April 21, 2018, 08:32:13 am
The ''delay'' of pulse  can be considered to  the ''phase'' of sine or other waveform.The maximum phase of the waveform is 360 degrees,so the maximum delay is one period of the pulse.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tautech on May 23, 2018, 02:26:07 am
Just got some SDG6022X for a customer so a quick first look (for me) at what these are like.
First thing noted they are the same physical size as SDG1kX and 2kX AWG's but they also have a smart fan that when first turned on is very quiet. The basic UI's between these 3 series is very similar. Running a 80 MHz squarewave for a while had the fan going but certainly no worse than a DSO.

SDG6022X (200 MHz) 80 MHz squarewave, max p-p into 50 \$\Omega\$
SDS2304X, Siglent BNC cable.

(https://www.eevblog.com/forum/testgear/siglent-sdg6000-series-awg_s/?action=dlattach;attach=439270)
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: radiolistener on May 23, 2018, 04:03:53 am
200 MHz model looks good for home lab, but it's too expensive.
I think it's a crazy to buy so expensive generator for a hobby purposes.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: jgalak on June 05, 2018, 04:09:01 am
Does anyone know if the SDG6022X is "upgradable" to 500MHz? 
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tv84 on July 06, 2018, 02:58:39 pm
Does anyone know if the SDG6022X is "upgradable" to 500MHz?

It should be. Do you know how to enter licenses via SCPI?

To ease the life to every owner:

root:$1$NLwMj1Ox$1y4YFcXYiZILqUehDFKuB1:15672:0:99999:7:::

Just have to crack it. I can't.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: janekivi on July 06, 2018, 07:54:19 pm
...and for all other model owners as the password is the same
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: KaneTW on July 06, 2018, 09:01:19 pm
That makes this a very attractive unit. Nice.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tv84 on July 06, 2018, 09:20:13 pm
It can be done.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tautech on July 06, 2018, 09:23:49 pm
It can be done.
Wow.
That's a big $$ saving !  :scared:
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: BillB on July 06, 2018, 10:52:27 pm
nice job, tv84!  :clap:
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tautech on July 26, 2018, 10:52:53 am
New firmware for SDG6000X series.

Version 6.01.01.29R10
26.2 MB
https://www.siglentamerica.com/download/6886/ (https://www.siglentamerica.com/download/6886/)

Changelog
1. Optimized TrueArb algorithm and added 3 types of interpolation: sinc, sinc27 and sinc13
2. Optimized jitter performance of Square and Pulse
3. Optimized algorithm of Noise generating so the bandwidth setting lower limit of Noise optimized from 80 MHz to 1 mHz
4. [2017/12/22-174663] Changed the clock switch strategy: When the clock source is set to External and no actual external clock signal is being received, the clock source will not switch to Internal automatically but the clock icon will indicate that external clock is lost
5. [2017/12/22-174663] Changed default state of 10 MHz Out to "Disable"
6. Added Slave Delay option in Multi-Device Synchronization function
7. Added indicator for double function of the soft keys
8. Fixed the following bugs:
a) Crashes when downloading 20 Mpts waveform data from the EasyWave program
b) Inaccurate burst delay
c) In TrueArb mode enabling AM with large amplitude may trigger OVP
d) Switching the waveform from IQ to sine with large amplitude may trigger OVP
e) Switching off the output on the SDG6kX only drops the output level by approx 20 dB but does not completely switch it off
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: JohnG on July 26, 2018, 02:25:25 pm
New firmware for SDG6000X series.

Version 6.01.01.29R10
26.2 MB
https://www.siglentamerica.com/download/6886/ (https://www.siglentamerica.com/download/6886/)

Changelog
2. Optimized jitter performance of Square and Pulse


Do you know what "optimized jitter performance" means in terms of specification?

Thanks,
John
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: janekivi on July 26, 2018, 04:21:05 pm
I know what "New firmware for SDG6000X series" means in technical terms.
It means: we can change root password.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tv84 on July 26, 2018, 05:16:41 pm
It means: we can change root password.

Now, at last, "officially".

Code: [Select]
File Header Size: 00000070
00000000 - File Checksum: 3492CF01 [00000004-0199B704] (with only the File Header decrypted)  CKSM OK
00000004 - File Size: 0199B695 (without 0x70 bytes of the File Header)
0000000C - Product_ID: 10800
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 0x00CCDB4B until 0x0199B694
****************************************************
00000000 --- Section Checksum: 2E68F57E
00000004 --- Section Size: 0199B661 [00000034-0199B694]  CKSM OK
00000008 --- Section # 00000007
00000034 --- 0199B694  ***** ZIP file *****
Offset    Ver  Flag  Comp  Size      Packed    Modified             CRC32                          Name         Permissions     Extra Details
00000034  1.0  0000  0000  00000000  00000000  26-06-2018 17:19:03  00000000  [00000059-00000058]  config/
00000059  1.0  0000  0000  00000000  00000000  26-06-2018 17:19:03  00000000  [00000082-00000081]  config/arb/
00000082  2.0  0000  0008  00010000  0000EF3C  30-03-2018 22:13:10  B1F7055B  [000000B9-0000EFF4]  config/arb/0_sine_ram.bin
0000EFF5  2.0  0000  0008  00010000  0000BE93  30-03-2018 22:13:10  4E8F563F  [0000F02F-0001AEC1]  config/arb/100_ecg11_ram.bin
0001AEC2  2.0  0000  0008  00010000  0000C3F1  30-03-2018 22:13:10  6BF84577  [0001AEFC-000272EC]  config/arb/101_ecg12_ram.bin
000272ED  2.0  0000  0008  00010000  0000CD17  30-03-2018 22:13:10  C3802FFA  [00027327-0003403D]  config/arb/102_ecg13_ram.bin
0003403E  2.0  0000  0008  00010000  0000CFB5  30-03-2018 22:13:10  A24DDF5A  [00034078-0004102C]  config/arb/103_ecg14_ram.bin
0004102D  2.0  0000  0008  00010000  0000C272  30-03-2018 22:13:10  1D799C83  [00041067-0004D2D8]  config/arb/104_ecg15_ram.bin
0004D2D9  2.0  0000  0008  00010000  0000BF1E  30-03-2018 22:13:10  F2F294C7  [0004D315-00059232]  config/arb/105_lfpulse_ram.bin
00059233  2.0  0000  0008  00010000  00009F95  30-03-2018 22:13:10  942FCB67  [0005926D-00063201]  config/arb/106_tens1_ram.bin
00063202  2.0  0000  0008  00010000  000002D0  30-03-2018 22:13:10  B9AC8FAB  [0006323C-0006350B]  config/arb/107_tens2_ram.bin
0006350C  2.0  0000  0008  00010000  00002136  30-03-2018 22:13:10  518DA7BC  [00063546-0006567B]  config/arb/108_tens3_ram.bin
0006567C  2.0  0000  0008  00010000  000061E6  30-03-2018 22:13:10  554389D3  [000656B5-0006B89A]  config/arb/109_airy_ram.bin
0006B89B  2.0  0000  0008  00010000  0000A182  30-03-2018 22:13:10  62F9139D  [0006B8D7-00075A58]  config/arb/10_exp_fall_ram.bin
00075A59  2.0  0000  0008  00010000  0000EB0E  30-03-2018 22:13:10  58968693  [00075A95-000845A2]  config/arb/110_besselj_ram.bin
000845A3  2.0  0000  0008  00010000  0000BA47  30-03-2018 22:13:10  2AE115C0  [000845DF-00090025]  config/arb/111_bessely_ram.bin
00090026  2.0  0000  0008  00010000  0000ECC0  30-03-2018 22:13:10  13D87C2F  [00090064-0009ED23]  config/arb/112_dirichlet_ram.bin
0009ED24  2.0  0000  0008  00010000  0000B7CE  30-03-2018 22:13:10  6361D3D4  [0009ED5C-000AA529]  config/arb/113_erf_ram.bin
000AA52A  2.0  0000  0008  00010000  0000BF6F  30-03-2018 22:13:10  22D799F8  [000AA563-000B64D1]  config/arb/114_erfc_ram.bin
000B64D2  2.0  0000  0008  00010000  0000C38E  30-03-2018 22:13:10  49212B1C  [000B650E-000C289B]  config/arb/115_erfcinv_ram.bin
000C289C  2.0  0000  0008  00010000  0000C4C2  30-03-2018 22:13:10  3A74BF25  [000C28D7-000CED98]  config/arb/116_erfinv_ram.bin
000CED99  2.0  0000  0008  00010000  0000C385  30-03-2018 22:13:10  4F47BAD9  [000CEDD6-000DB15A]  config/arb/117_laguerre_ram.bin
000DB15B  2.0  0000  0008  00010000  0000C819  30-03-2018 22:13:10  1658CA7F  [000DB196-000E79AE]  config/arb/118_legend_ram.bin
000E79AF  2.0  0000  0008  00010000  0000CCFA  30-03-2018 22:13:10  6FB2EB66  [000E79EC-000F46E5]  config/arb/119_versiera_ram.bin
000F46E6  2.0  0000  0008  00010000  0000A183  30-03-2018 22:13:10  6BC5E338  [000F4722-000FE8A4]  config/arb/11_exp_rise_ram.bin
000FE8A5  2.0  0000  0008  00010000  000093D6  30-03-2018 22:13:10  BE68741A  [000FE8E1-00107CB6]  config/arb/120_weibull_ram.bin
00107CB7  2.0  0000  0008  00010000  0000DDB2  30-03-2018 22:13:10  F5390B5B  [00107CF5-00115AA6]  config/arb/121_lognormal_ram.bin
00115AA7  2.0  0000  0008  00010000  0000F1C2  30-03-2018 22:13:10  E58083D0  [00115AE3-00124CA4]  config/arb/122_laplace_ram.bin
00124CA5  2.0  0000  0008  00010000  0000A350  30-03-2018 22:13:10  74F9E16B  [00124CE1-0012F030]  config/arb/123_maxwell_ram.bin
0012F031  2.0  0000  0008  00010000  0000AF0F  30-03-2018 22:13:10  0729FBCB  [0012F06E-00139F7C]  config/arb/124_rayleigh_ram.bin
00139F7D  2.0  0000  0008  00010000  0000D3F4  30-03-2018 22:13:10  34018AC5  [00139FB8-001473AB]  config/arb/125_cauchy_ram.bin
001473AC  2.0  0000  0008  00010000  0000C250  30-03-2018 22:13:10  E585FA7E  [001473E5-00153634]  config/arb/126_cosh_ram.bin
00153635  2.0  0000  0008  00010000  00005575  30-03-2018 22:13:10  C949B875  [00153670-00158BE4]  config/arb/127_cosint_ram.bin
00158BE5  2.0  0000  0008  0000412A  00000A4F  30-03-2018 22:13:10  8B96B9E9  [00158C18-00159666]  config/arb/128QAM.wav
00159667  2.0  0000  0008  00010000  00002784  30-03-2018 22:13:10  9E3728E9  [001596A0-0015BE23]  config/arb/128_coth_ram.bin
0015BE24  2.0  0000  0008  00010000  00003BF1  30-03-2018 22:13:10  52A153E0  [0015BE5D-0015FA4D]  config/arb/129_csch_ram.bin
0015FA4E  2.0  0000  0008  00010000  00009A77  30-03-2018 22:13:10  A0A3C424  [0015FA89-001694FF]  config/arb/12_logfall_ram.bin
00169500  2.0  0000  0008  00010000  0000BE75  30-03-2018 22:13:10  BAA95447  [00169539-001753AD]  config/arb/130_sech_ram.bin
001753AE  2.0  0000  0008  00010000  0000A58C  30-03-2018 22:13:10  68A86E5F  [001753E7-0017F972]  config/arb/131_sinh_ram.bin
0017F973  2.0  0000  0008  00010000  0000AB2F  30-03-2018 22:13:10  16E5F37F  [0017F9AE-0018A4DC]  config/arb/132_sinint_ram.bin
0018A4DD  2.0  0000  0008  00010000  00007766  30-03-2018 22:13:10  EAB472AB  [0018A516-00191C7B]  config/arb/133_tanh_ram.bin
00191C7C  2.0  0000  0008  00010000  0000F0D1  30-03-2018 22:13:10  3A4F74B6  [00191CB6-001A0D86]  config/arb/134_acosh_ram.bin
001A0D87  2.0  0000  0008  00010000  00008BE1  30-03-2018 22:13:10  B9FD11CA  [001A0DC1-001A99A1]  config/arb/135_asech_ram.bin
001A99A2  2.0  0000  0008  00010000  0000F686  30-03-2018 22:13:10  F75E3C13  [001A99DC-001B9061]  config/arb/136_asinh_ram.bin
001B9062  2.0  0000  0008  00010000  000089B0  30-03-2018 22:13:10  828619AD  [001B909C-001C1A4B]  config/arb/137_atanh_ram.bin
001C1A4C  2.0  0000  0008  00010000  00008357  30-03-2018 22:13:10  F763152F  [001C1A86-001C9DDC]  config/arb/138_acsch_ram.bin
001C9DDD  2.0  0000  0008  00010000  00002B83  30-03-2018 22:13:10  E8D330BF  [001C9E17-001CC999]  config/arb/139_acoth_ram.bin
001CC99A  2.0  0000  0008  00010000  00009A75  30-03-2018 22:13:10  A99F3481  [001CC9D5-001D6449]  config/arb/13_logrise_ram.bin
001D644A  2.0  0000  0008  00010000  0000F248  30-03-2018 22:13:10  1691575C  [001D6487-001E56CE]  config/arb/140_bartlett_ram.bin
001E56CF  2.0  0000  0008  00010000  0000FF09  30-03-2018 22:13:10  3CA8587B  [001E570F-001F5617]  config/arb/141_barthannwin_ram.bin
001F5618  2.0  0000  0008  00010000  0000E18F  30-03-2018 22:13:10  9243E29D  [001F5656-002037E4]  config/arb/142_bohmanwin_ram.bin
002037E5  2.0  0000  0008  00010000  0000D9A8  30-03-2018 22:13:10  6492DB5A  [00203821-002111C8]  config/arb/143_chebwin_ram.bin
002111C9  2.0  0000  0008  00010000  0000C6FE  30-03-2018 22:13:10  D64B1A3D  [00211208-0021D905]  config/arb/144_flattopwin_ram.bin
0021D906  2.0  0000  0008  00010000  0000DA9B  30-03-2018 22:13:10  B7077A2F  [0021D944-0022B3DE]  config/arb/145_parzenwin_ram.bin
0022B3DF  2.0  0000  0008  00010000  0000F43F  30-03-2018 22:13:10  E37C838A  [0022B41D-0023A85B]  config/arb/146_taylorwin_ram.bin
0023A85C  2.0  0000  0008  00010000  00007D94  30-03-2018 22:13:10  222AB8C7  [0023A899-0024262C]  config/arb/147_tukeywin_ram.bin
0024262D  2.0  0000  0008  00010000  00000059  30-03-2018 22:13:10  1861B3BB  [0024266B-002426C3]  config/arb/148_square_duty01.bin
002426C4  2.0  0000  0008  00010000  00000059  30-03-2018 22:13:10  82EFE13B  [00242702-0024275A]  config/arb/149_square_duty02.bin
0024275B  2.0  0000  0008  00010000  0000F83D  30-03-2018 22:13:10  C48745E9  [00242793-00251FCF]  config/arb/14_sqrt_ram.bin
00251FD0  2.0  0000  0008  00010000  0000005A  30-03-2018 22:13:10  304795EA  [0025200E-00252067]  config/arb/150_square_duty04.bin
00252068  2.0  0000  0008  00010000  00000058  30-03-2018 22:13:10  B9BF3283  [002520A6-002520FD]  config/arb/151_square_duty06.bin
002520FE  2.0  0000  0008  00010000  0000005A  30-03-2018 22:13:10  939CA0FD  [0025213C-00252195]  config/arb/152_square_duty08.bin
00252196  2.0  0000  0008  00010000  0000005A  30-03-2018 22:13:10  3FE99976  [002521D4-0025222D]  config/arb/153_square_duty10.bin
0025222E  2.0  0000  0008  00010000  00000058  30-03-2018 22:13:10  D72A4B1C  [0025226C-002522C3]  config/arb/154_square_duty12.bin
002522C4  2.0  0000  0008  00010000  00000059  30-03-2018 22:13:10  98CBCF7B  [00252301-00252359]  config/arb/155_quare_duty14.bin
0025235A  2.0  0000  0008  00010000  00000059  30-03-2018 22:13:10  3512B741  [00252398-002523F0]  config/arb/156_square_duty16.bin
002523F1  2.0  0000  0008  00010000  00000059  30-03-2018 22:13:10  213B5B4D  [0025242F-00252487]  config/arb/157_square_duty18.bin
00252488  2.0  0000  0008  00010000  00000059  30-03-2018 22:13:10  C474C4F3  [002524C6-0025251E]  config/arb/158_square_duty20.bin
0025251F  2.0  0000  0008  00010000  00000059  30-03-2018 22:13:10  25EC0A77  [0025255D-002525B5]  config/arb/159_square_duty22.bin
002525B6  2.0  0000  0008  00010000  0000DF25  30-03-2018 22:13:10  115F5A42  [002525EF-00260513]  config/arb/15_root3_ram.bin
00260514  2.0  0000  0008  00010000  00000059  30-03-2018 22:13:10  8D52DE44  [00260552-002605AA]  config/arb/160_square_duty24.bin
002605AB  2.0  0000  0008  00010000  00000059  30-03-2018 22:13:10  DBE7401D  [002605E9-00260641]  config/arb/161_square_duty26.bin
00260642  2.0  0000  0008  00010000  00000059  30-03-2018 22:13:10  CE0520FD  [00260680-002606D8]  config/arb/162_square_duty28.bin
002606D9  2.0  0000  0008  00010000  00000059  30-03-2018 22:13:10  00920F3B  [00260717-0026076F]  config/arb/163_square_duty30.bin
00260770  2.0  0000  0008  00010000  00000059  30-03-2018 22:13:10  F122C564  [002607AE-00260806]  config/arb/164_square_duty32.bin
00260807  2.0  0000  0008  00010000  00000059  30-03-2018 22:13:10  3B6E351A  [00260845-0026089D]  config/arb/165_square_duty34.bin
0026089E  2.0  0000  0008  00010000  00000059  30-03-2018 22:13:10  4353928B  [002608DC-00260934]  config/arb/166_square_duty36.bin
00260935  2.0  0000  0008  00010000  00000058  30-03-2018 22:13:10  413D5E36  [00260973-002609CA]  config/arb/167_square_duty38.bin
002609CB  2.0  0000  0008  00010000  0000005A  30-03-2018 22:13:10  7C83F164  [00260A09-00260A62]  config/arb/168_square_duty40.bin
00260A63  2.0  0000  0008  00010000  0000005A  30-03-2018 22:13:10  9EE7BB00  [00260AA1-00260AFA]  config/arb/169_square_duty42.bin
00260AFB  2.0  0000  0008  00004128  0000255E  30-03-2018 22:13:10  20FFC115  [00260B2D-0026308A]  config/arb/16QAM.wav
0026308B  2.0  0000  0008  00010000  0000F11B  30-03-2018 22:13:10  C9B6E33A  [002630C2-002721DC]  config/arb/16_x^2_ram.bin
002721DD  2.0  0000  0008  00010000  00000058  30-03-2018 22:13:10  C38AA9FD  [0027221B-00272272]  config/arb/170_square_duty44.bin
00272273  2.0  0000  0008  00010000  0000005A  30-03-2018 22:13:10  CBFC1F28  [002722B1-0027230A]  config/arb/171_square_duty46.bin
0027230B  2.0  0000  0008  00010000  0000005A  30-03-2018 22:13:10  D76651FA  [00272349-002723A2]  config/arb/172_square_duty48.bin
002723A3  2.0  0000  0008  00010000  00000057  30-03-2018 22:13:10  42922C71  [002723E1-00272437]  config/arb/173_square_duty50.bin
00272438  2.0  0000  0008  00010000  0000005A  30-03-2018 22:13:10  E4F65825  [00272476-002724CF]  config/arb/174_square_duty52.bin
002724D0  2.0  0000  0008  00010000  0000005A  30-03-2018 22:13:10  0E779380  [0027250E-00272567]  config/arb/175_square_duty54.bin
00272568  2.0  0000  0008  00010000  00000058  30-03-2018 22:13:10  FC9A26F2  [002725A6-002725FD]  config/arb/176_square_duty56.bin
002725FE  2.0  0000  0008  00010000  0000005A  30-03-2018 22:13:10  2558AEBE  [0027263C-00272695]  config/arb/177_square_duty58.bin
00272696  2.0  0000  0008  00010000  0000005A  30-03-2018 22:13:10  68C72279  [002726D4-0027272D]  config/arb/178_square_duty60.bin
0027272E  2.0  0000  0008  00010000  00000058  30-03-2018 22:13:10  A5F9C0FC  [0027276C-002727C3]  config/arb/179_square_duty62.bin
002727C4  2.0  0000  0008  00010000  0000B772  30-03-2018 22:13:10  C6AD7960  [002727FB-0027DF6C]  config/arb/17_x^3_ram.bin
0027DF6D  2.0  0000  0008  00010000  00000059  30-03-2018 22:13:10  ED598744  [0027DFAB-0027E003]  config/arb/180_square_duty64.bin
0027E004  2.0  0000  0008  00010000  00000059  30-03-2018 22:13:10  4462F39C  [0027E042-0027E09A]  config/arb/181_square_duty66.bin
0027E09B  2.0  0000  0008  00010000  00000059  30-03-2018 22:13:10  EA29B4BF  [0027E0D9-0027E131]  config/arb/182_square_duty68.bin
0027E132  2.0  0000  0008  00010000  00000059  30-03-2018 22:13:10  75FF6C95  [0027E170-0027E1C8]  config/arb/183_square_duty70.bin
0027E1C9  2.0  0000  0008  00010000  00000059  30-03-2018 22:13:10  82148736  [0027E207-0027E25F]  config/arb/184_square_duty72.bin
0027E260  2.0  0000  0008  00010000  00000059  30-03-2018 22:13:10  BE74B4BF  [0027E29E-0027E2F6]  config/arb/185_square_duty74.bin
0027E2F7  2.0  0000  0008  00010000  00000059  30-03-2018 22:13:10  EC61321A  [0027E335-0027E38D]  config/arb/186_square_duty76.bin
0027E38E  2.0  0000  0008  00010000  00000059  30-03-2018 22:13:10  44DCD1A9  [0027E3CC-0027E424]  config/arb/187_square_duty78.bin
0027E425  2.0  0000  0008  00010000  00000059  30-03-2018 22:13:10  7CEA24CC  [0027E463-0027E4BB]  config/arb/188_square_duty80.bin
0027E4BC  2.0  0000  0008  00010000  00000059  30-03-2018 22:13:10  BFF920D5  [0027E4FA-0027E552]  config/arb/189_square_duty82.bin
0027E553  2.0  0000  0008  00010000  0000B521  30-03-2018 22:13:10  1818E01B  [0027E58B-00289AAB]  config/arb/18_sinc_ram.bin
00289AAC  2.0  0000  0008  00010000  00000059  30-03-2018 22:13:10  DE98C289  [00289AEA-00289B42]  config/arb/190_square_duty84.bin
00289B43  2.0  0000  0008  00010000  00000059  30-03-2018 22:13:10  91AEF330  [00289B81-00289BD9]  config/arb/191_square_duty86.bin
00289BDA  2.0  0000  0008  00010000  00000058  30-03-2018 22:13:10  36DDF3D4  [00289C18-00289C6F]  config/arb/192_square_duty88.bin
00289C70  2.0  0000  0008  00010000  0000005A  30-03-2018 22:13:10  7BCE461B  [00289CAE-00289D07]  config/arb/193_square_duty90.bin
00289D08  2.0  0000  0008  00010000  0000005A  30-03-2018 22:13:10  00B1CBC4  [00289D46-00289D9F]  config/arb/194_square_duty92.bin
00289DA0  2.0  0000  0008  00010000  00000058  30-03-2018 22:13:10  20CEA2C3  [00289DDE-00289E35]  config/arb/195_square_duty94.bin
00289E36  2.0  0000  0008  00010000  0000005A  30-03-2018 22:13:10  9A813AC7  [00289E74-00289ECD]  config/arb/196_square_duty96.bin
00289ECE  2.0  0000  0008  00010000  0000005A  30-03-2018 22:13:10  E9728D70  [00289F0C-00289F65]  config/arb/197_square_duty98.bin
00289F66  2.0  0000  0008  00010000  00000059  30-03-2018 22:13:10  1B62D645  [00289FA4-00289FFC]  config/arb/198_square_duty99.bin
00289FFD  2.0  0000  0008  000002EE  00000022  30-03-2018 22:13:10  5A7659F3  [0028A03A-0028A05B]  config/arb/199_demo1_375pts.bin
0028A05C  2.0  0000  0008  00010000  0000C1AC  30-03-2018 22:13:10  754B6831  [0028A097-00296242]  config/arb/19_gussian_ram.bin
00296243  2.0  0000  0008  00010000  0000F9F6  30-03-2018 22:13:10  069EF566  [0029627B-002A5C70]  config/arb/1_noise_ram.bin
002A5C71  2.0  0000  0008  00010000  0000006F  30-03-2018 22:13:10  48591011  [002A5CAE-002A5D1C]  config/arb/200_demo1_16kpts.bin
002A5D1D  2.0  0000  0008  00001770  00000048  30-03-2018 22:13:10  7C4E9B2E  [002A5D59-002A5DA0]  config/arb/201_demo2_3kpts.bin
002A5DA1  2.0  0000  0008  00008000  00000067  30-03-2018 22:13:10  DBFC2D6F  [002A5DDE-002A5E44]  config/arb/202_demo2_16kpts.bin
002A5E45  2.0  0000  0008  00010000  0000F6E0  30-03-2018 22:13:10  1BC74ED8  [002A5E89-002B5568]  config/arb/203_sine_harmonic2_wave.bin
002B5569  2.0  0000  0008  00010000  0000F65B  30-03-2018 22:13:10  C69870D7  [002B55AD-002C4C07]  config/arb/204_sine_harmonic3_wave.bin
002C4C08  2.0  0000  0008  00010000  00003F14  30-03-2018 22:13:10  DDABDF02  [002C4C4C-002C8B5F]  config/arb/205_sine_harmonic4_wave.bin
002C8B60  2.0  0000  0008  00010000  0000F7C5  30-03-2018 22:13:10  411C783B  [002C8BA4-002D8368]  config/arb/206_sine_harmonic5_wave.bin
002D8369  2.0  0000  0008  00010000  0000F772  30-03-2018 22:13:10  1FB6A772  [002D83AD-002E7B1E]  config/arb/207_sine_harmonic6_wave.bin
002E7B1F  2.0  0000  0008  00010000  0000F6FB  30-03-2018 22:13:10  23DC7C6B  [002E7B63-002F725D]  config/arb/208_sine_harmonic7_wave.bin
002F725E  2.0  0000  0008  00010000  00001F9E  30-03-2018 22:13:10  149C22D7  [002F72A2-002F923F]  config/arb/209_sine_harmonic8_wave.bin
002F9240  2.0  0000  0008  00010000  0000778C  30-03-2018 22:13:10  BF56E815  [002F927C-00300A07]  config/arb/20_dlorentz_ram.bin
00300A08  2.0  0000  0008  00010000  0000F6EB  30-03-2018 22:13:10  9ADD73E3  [00300A4C-00310136]  config/arb/210_sine_harmonic9_wave.bin
00310137  2.0  0000  0008  00010000  0000F80E  30-03-2018 22:13:10  0DC757DD  [0031017C-0031F989]  config/arb/211_sine_harmonic10_wave.bin
0031F98A  2.0  0000  0008  00010000  0000F705  30-03-2018 22:13:10  D355BECD  [0031F9CF-0032F0D3]  config/arb/212_sine_harmonic11_wave.bin
0032F0D4  2.0  0000  0008  00010000  00003FE0  30-03-2018 22:13:10  01E387B8  [0032F119-003330F8]  config/arb/213_sine_harmonic12_wave.bin
003330F9  2.0  0000  0008  00010000  0000F823  30-03-2018 22:13:10  7EA1671C  [0033313E-00342960]  config/arb/214_sine_harmonic13_wave.bin
00342961  2.0  0000  0008  00010000  0000F877  30-03-2018 22:13:10  E9A7207C  [003429A6-0035221C]  config/arb/215_sine_harmonic14_wave.bin
0035221D  2.0  0000  0008  00010000  0000F78F  30-03-2018 22:13:10  BE21AE87  [00352262-003619F0]  config/arb/216_sine_harmonic15_wave.bin
003619F1  2.0  0000  0008  00010000  0000111C  30-03-2018 22:13:10  32DE0B3A  [00361A36-00362B51]  config/arb/217_sine_harmonic16_wave.bin
00362B52  2.0  0000  0008  00010000  0000F3ED  30-03-2018 22:13:10  CA7AEE0B  [00362B8F-00371F7B]  config/arb/21_haversine_ram.bin
00371F7C  2.0  0000  0008  00010000  000093E8  30-03-2018 22:13:10  88C57271  [00371FB7-0037B39E]  config/arb/22_lorentz_ram.bin
0037B39F  2.0  0000  0008  00010000  0000CAB0  30-03-2018 22:13:10  6A602CC3  [0037B3DB-00387E8A]  config/arb/23_gauspuls_ram.bin
00387E8B  2.0  0000  0008  00010000  0000D4EA  30-03-2018 22:13:10  17DFCD27  [00387EC8-003953B1]  config/arb/24_gmonopuls_ram.bin
003953B2  2.0  0000  0008  0000412A  0000255E  30-03-2018 22:13:10  D49145AB  [003953E5-00397942]  config/arb/256QAM.wav
00397943  2.0  0000  0008  00010000  000031EF  30-03-2018 22:13:10  494BD9BF  [0039797E-0039AB6C]  config/arb/25_tripuls_ram.bin
0039AB6D  2.0  0000  0008  00010000  0000852B  30-03-2018 22:13:10  DEF79A0A  [0039ABA8-003A30D2]  config/arb/26_cardiac_ram.bin
003A30D3  2.0  0000  0008  00010000  000030BA  30-03-2018 22:13:10  4171747A  [003A310C-003A61C5]  config/arb/27_quake_ram.bin
003A61C6  2.0  0000  0008  00010000  0000F2B0  30-03-2018 22:13:10  898E2F75  [003A61FF-003B54AE]  config/arb/28_chirp_ram.bin
003B54AF  2.0  0000  0008  00010000  0000EC2B  30-03-2018 22:13:10  71D0B844  [003B54EA-003C4114]  config/arb/29_twotone_ram.bin
003C4115  2.0  0000  0008  00004126  0000177D  30-03-2018 22:13:10  4A2D18DD  [003C4146-003C58C2]  config/arb/2ASK.wav 
003C58C3  2.0  0000  0008  00010000  00000074  30-03-2018 22:13:10  0B50B3F0  [003C58FD-003C5970]  config/arb/2_stairup_ram.bin
003C5971  2.0  0000  0008  00010000  0000F7C2  30-03-2018 22:13:10  C8FABEA4  [003C59A8-003D5169]  config/arb/30_snr_ram.bin
003D516A  2.0  0000  0008  00004128  0000253F  30-03-2018 22:13:10  B2E71A1D  [003D519C-003D76DA]  config/arb/32QAM.wav
003D76DB  2.0  0000  0008  00010000  0000F221  30-03-2018 22:13:10  9A32322A  [003D7716-003E6936]  config/arb/34_hamming_ram.bin
003E6937  2.0  0000  0008  00010000  0000F3F6  30-03-2018 22:13:10  23CFB6C9  [003E6972-003F5D67]  config/arb/35_hanning_ram.bin
003F5D68  2.0  0000  0008  00010000  0000E180  30-03-2018 22:13:10  EE9299B0  [003F5DA2-00403F21]  config/arb/36_kaiser_ram.bin
00403F22  2.0  0000  0008  00010000  0000EB4B  30-03-2018 22:13:10  23EDEF95  [00403F5E-00412AA8]  config/arb/37_blackman_ram.bin
00412AA9  2.0  0000  0008  00010000  0000FAC9  30-03-2018 22:13:10  037C41A0  [00412AE5-004225AD]  config/arb/38_gausswin_ram.bin
004225AE  2.0  0000  0008  00010000  0000FB3B  30-03-2018 22:13:10  DB0E6DD1  [004225E8-00432122]  config/arb/39_triang_ram.bin
00432123  2.0  0000  0008  00010000  00000074  30-03-2018 22:13:10  026C4355  [0043215D-004321D0]  config/arb/3_stairdn_ram.bin
004321D1  2.0  0000  0008  00010000  0000D05C  30-03-2018 22:13:10  C360DC35  [00432213-0043F26E]  config/arb/40_blackmanharris_ram.bin
0043F26F  2.0  0000  0008  00010000  0000FF0A  30-03-2018 22:13:10  832E2F41  [0043F2AE-0044F1B7]  config/arb/41_barthannwin_ram.bin
0044F1B8  2.0  0000  0008  00010000  00003677  30-03-2018 22:13:10  358D257B  [0044F1EF-00452865]  config/arb/42_tan_ram.bin
00452866  2.0  0000  0008  00010000  00003676  30-03-2018 22:13:10  3CB1D5DE  [0045289D-00455F12]  config/arb/43_cot_ram.bin
00455F13  2.0  0000  0008  00010000  00004572  30-03-2018 22:13:10  E97AF125  [00455F4A-0045A4BB]  config/arb/44_sec_ram.bin
0045A4BC  2.0  0000  0008  00010000  00004574  30-03-2018 22:13:10  E0460180  [0045A4F3-0045EA66]  config/arb/45_csc_ram.bin
0045EA67  2.0  0000  0008  00010000  0000F8B7  30-03-2018 22:13:10  80530FD7  [0045EA9F-0046E355]  config/arb/46_asin_ram.bin
0046E356  2.0  0000  0008  00010000  0000F8B6  30-03-2018 22:13:10  8287D646  [0046E38E-0047DC43]  config/arb/47_acos_ram.bin
0047DC44  2.0  0000  0008  00010000  00006F29  30-03-2018 22:13:10  0FEF4D94  [0047DC7C-00484BA4]  config/arb/48_atan_ram.bin
00484BA5  2.0  0000  0008  00010000  00006F25  30-03-2018 22:13:10  109CCD6A  [00484BDD-0048BB01]  config/arb/49_acot_ram.bin
0048BB02  2.0  0000  0008  00004126  00001874  30-03-2018 22:13:10  396369EE  [0048BB33-0048D3A6]  config/arb/4ASK.wav 
0048D3A7  2.0  0000  0008  00010000  00000090  30-03-2018 22:13:10  46B62C90  [0048D3E1-0048D470]  config/arb/4_stairud_ram.bin
0048D471  2.0  0000  0008  00010000  00000057  30-03-2018 22:13:10  42922C71  [0048D4AB-0048D501]  config/arb/50_square_ram.bin
0048D502  2.0  0000  0008  00010000  0000C841  30-03-2018 22:13:10  0C7C166F  [0048D53D-00499D7D]  config/arb/51_sinetra_ram.bin
00499D7E  2.0  0000  0008  00010000  00007648  30-03-2018 22:13:10  4A894F64  [00499DB9-004A1400]  config/arb/52_sinever_ram.bin
004A1401  2.0  0000  0008  00010000  0000F38D  30-03-2018 22:13:10  7F7A0DF2  [004A143B-004B07C7]  config/arb/53_ampalt_ram.bin
004B07C8  2.0  0000  0008  00010000  0000F3AA  30-03-2018 22:13:10  725F01C9  [004B0802-004BFBAB]  config/arb/54_attalt_ram.bin
004BFBAC  2.0  0000  0008  00010000  0000E01A  30-03-2018 22:13:10  EAA096B8  [004BFBE9-004CDC02]  config/arb/55_roundhalf_ram.bin
004CDC03  2.0  0000  0008  00010000  0000BDC2  30-03-2018 22:13:10  49566C28  [004CDC3F-004D9A00]  config/arb/56_roundspm_ram.bin
004D9A01  2.0  0000  0008  00010000  00007721  30-03-2018 22:13:10  7D5B366A  [004D9A3F-004E115F]  config/arb/57_blaseiwave_ram.bin
004E1160  2.0  0000  0008  00010000  0000C77B  30-03-2018 22:13:10  ADD1B72B  [004E119D-004ED917]  config/arb/58_dampedosc_ram.bin
004ED918  2.0  0000  0008  00010000  0000D6BD  30-03-2018 22:13:10  69414977  [004ED954-004FB010]  config/arb/59_swingosc_ram.bin
004FB011  2.0  0000  0008  00010000  00000058  30-03-2018 22:13:10  239191BA  [004FB04A-004FB0A1]  config/arb/5_ppulse_ram.bin
004FB0A2  2.0  0000  0008  00010000  0000ADFA  30-03-2018 22:13:10  63C407EE  [004FB0DF-00505ED8]  config/arb/60_discharge_ram.bin
00505ED9  2.0  0000  0008  00010000  0000B1D3  30-03-2018 22:13:10  AEBD81F1  [00505F13-005110E5]  config/arb/61_pahcur_ram.bin
005110E6  2.0  0000  0008  00010000  00005701  30-03-2018 22:13:10  C5E2FF2B  [00511120-00516820]  config/arb/62_combin_ram.bin
00516821  2.0  0000  0008  00010000  000094A5  30-03-2018 22:13:10  C9F70728  [00516858-0051FCFC]  config/arb/63_scr_ram.bin
0051FCFD  2.0  0000  0008  00004128  00002541  30-03-2018 22:13:10  2D4305F5  [0051FD2F-0052226F]  config/arb/64QAM.wav
00522270  2.0  0000  0008  00010000  0000A99E  30-03-2018 22:13:10  0CB42250  [005222AF-0052CC4C]  config/arb/64_butterworth_ram.bin
0052CC4D  2.0  0000  0008  00010000  00009D46  30-03-2018 22:13:10  AA06DEA8  [0052CC8B-005369D0]  config/arb/65_chebyshev1_ram.bin
005369D1  2.0  0000  0008  00010000  0000BF0B  30-03-2018 22:13:10  79B33003  [00536A0F-00542919]  config/arb/66_chebyshev2_ram.bin
0054291A  2.0  0000  0008  00010000  00000093  30-03-2018 22:13:10  50E14207  [00542950-005429E2]  config/arb/67_tv_ram.bin
005429E3  2.0  0000  0008  00010000  0000664A  30-03-2018 22:13:10  49FDC530  [00542A1C-00549065]  config/arb/68_voice_ram.bin
00549066  2.0  0000  0008  00010000  0000B6C1  30-03-2018 22:13:10  31463571  [0054909F-0055475F]  config/arb/69_surge_ram.bin
00554760  2.0  0000  0008  00010000  00000058  30-03-2018 22:13:10  2AAD611F  [00554799-005547F0]  config/arb/6_npulse_ram.bin
005547F1  2.0  0000  0008  00010000  00000093  30-03-2018 22:13:10  62E5F642  [0055482A-005548BC]  config/arb/70_radar_ram.bin
005548BD  2.0  0000  0008  00010000  0000D21E  30-03-2018 22:13:10  D7EF0CDE  [005548F7-00561B14]  config/arb/71_ripple_ram.bin
00561B15  2.0  0000  0008  00010000  0000A3E7  30-03-2018 22:13:10  38DA0A48  [00561B4E-0056BF34]  config/arb/72_gamma_ram.bin
0056BF35  2.0  0000  0008  00010000  00008D8B  30-03-2018 22:13:10  D0BF1B92  [0056BF71-00574CFB]  config/arb/73_stepresp_ram.bin
00574CFC  2.0  0000  0008  00010000  000026D7  30-03-2018 22:13:10  B88C5B7C  [00574D37-0057740D]  config/arb/74_bandlimited.bin
0057740E  2.0  0000  0008  00010000  00000070  30-03-2018 22:13:10  246C8F8A  [00577448-005774B7]  config/arb/75_cpulse_ram.bin
005774B8  2.0  0000  0008  00010000  00007D2C  30-03-2018 22:13:10  449FA1CE  [005774F3-0057F21E]  config/arb/76_cwpulse_ram.bin
0057F21F  2.0  0000  0008  00010000  0000E081  30-03-2018 22:13:10  3CCD9976  [0057F25B-0058D2DB]  config/arb/77_gatevibr_ram.bin
0058D2DC  2.0  0000  0008  00010000  00007E9A  30-03-2018 22:13:10  2D8A7D5C  [0058D318-005951B1]  config/arb/78_lfmpulse_ram.bin
005951B2  2.0  0000  0008  00010000  0000BCE0  30-03-2018 22:13:10  F9A2DBE6  [005951ED-005A0ECC]  config/arb/79_mcnoise_ram.bin
005A0ECD  2.0  0000  0008  00010000  00007312  30-03-2018 22:13:10  364E6EF9  [005A0F08-005A8219]  config/arb/7_trapezia_ram.bin
005A821A  2.0  0000  0008  00010000  00007C6B  30-03-2018 22:13:10  084222E7  [005A8250-005AFEBA]  config/arb/80_am_ram.bin
005AFEBB  2.0  0000  0008  00010000  00003DE8  30-03-2018 22:13:10  D8629FE9  [005AFEF1-005B3CD8]  config/arb/81_fm_ram.bin
005B3CD9  2.0  0000  0008  00010000  000000AE  30-03-2018 22:13:10  00754F3C  [005B3D10-005B3DBD]  config/arb/82_pfm_ram.bin
005B3DBE  2.0  0000  0008  00010000  00007FB0  30-03-2018 22:13:10  A25DDBBB  [005B3DF4-005BBDA3]  config/arb/83_pm_ram.bin
005BBDA4  2.0  0000  0008  00010000  00000122  30-03-2018 22:13:10  3CDD9B7F  [005BBDDB-005BBEFC]  config/arb/84_pwm_ram.bin
005BBEFD  2.0  0000  0008  00010000  0000B28C  30-03-2018 22:13:10  2ABB7F6F  [005BBF34-005C71BF]  config/arb/85_eog_ram.bin
005C71C0  2.0  0000  0008  00010000  0000C2AF  30-03-2018 22:13:10  E4CF97F1  [005C71F7-005D34A5]  config/arb/86_eeg_ram.bin
005D34A6  2.0  0000  0008  00010000  0000CB30  30-03-2018 22:13:10  241BD6CC  [005D34DD-005E000C]  config/arb/87_emg_ram.bin
005E000D  2.0  0000  0008  00010000  0000C37B  30-03-2018 22:13:10  C8880F5E  [005E004D-005EC3C7]  config/arb/88_pulseilogram_ram.bin
005EC3C8  2.0  0000  0008  00010000  0000C5BF  30-03-2018 22:13:10  05B37362  [005EC404-005F89C2]  config/arb/89_resspeed_ram.bin
005F89C3  2.0  0000  0008  00004126  000018A6  30-03-2018 22:13:10  4204968E  [005F89F4-005FA299]  config/arb/8ASK.wav 
005FA29A  2.0  0000  0008  00004126  00002531  30-03-2018 22:13:10  DF529822  [005FA2CB-005FC7FB]  config/arb/8PSK.wav 
005FC7FC  2.0  0000  0008  00004126  000024B8  30-03-2018 22:13:10  CA97DAFF  [005FC82D-005FECE4]  config/arb/8QAM.wav 
005FECE5  2.0  0000  0008  00010000  0000F0AA  30-03-2018 22:13:10  F56DB708  [005FED1E-0060DDC7]  config/arb/8_upramp_ram.bin
0060DDC8  2.0  0000  0008  00010000  0000BF7C  30-03-2018 22:13:10  5F9ADD96  [0060DE00-00619D7B]  config/arb/90_ecg1_ram.bin
00619D7C  2.0  0000  0008  00010000  0000BD46  30-03-2018 22:13:10  B1680D2D  [00619DB4-00625AF9]  config/arb/91_ecg2_ram.bin
00625AFA  2.0  0000  0008  00010000  0000D48C  30-03-2018 22:13:10  D7FD7B39  [00625B32-00632FBD]  config/arb/92_ecg3_ram.bin
00632FBE  2.0  0000  0008  00010000  0000C3F9  30-03-2018 22:13:10  CCFEBC7C  [00632FF6-0063F3EE]  config/arb/93_ecg4_ram.bin
0063F3EF  2.0  0000  0008  00010000  0000C48C  30-03-2018 22:13:10  EDE23CC7  [0063F427-0064B8B2]  config/arb/94_ecg5_ram.bin
0064B8B3  2.0  0000  0008  00010000  0000C0B2  30-03-2018 22:13:10  A6892CAD  [0064B8EB-0065799C]  config/arb/95_ecg6_ram.bin
0065799D  2.0  0000  0008  00010000  0000D927  30-03-2018 22:13:10  94629745  [006579D5-006652FB]  config/arb/96_ecg7_ram.bin
006652FC  2.0  0000  0008  00010000  0000BEFF  30-03-2018 22:13:10  CA5BA402  [00665334-00671232]  config/arb/97_ecg8_ram.bin
00671233  2.0  0000  0008  00010000  0000C221  30-03-2018 22:13:10  9A9CE68A  [0067126B-0067D48B]  config/arb/98_ecg9_ram.bin
0067D48C  2.0  0000  0008  00010000  0000B45D  30-03-2018 22:13:10  008128CC  [0067D4C5-00688921]  config/arb/99_ecg10_ram.bin
00688922  2.0  0000  0008  00010000  0000F0A9  30-03-2018 22:13:10  F7B96E99  [0068895B-00697A03]  config/arb/9_dnramp_ram.bin
00697A04  2.0  0000  0008  00004126  000018F9  30-03-2018 22:13:10  ABE74254  [00697A35-0069932D]  config/arb/BPSK.wav 
0069932E  2.0  0000  0008  00004127  00002537  30-03-2018 22:13:10  C39A9324  [00699360-0069B896]  config/arb/D8PSK.wav
0069B897  2.0  0000  0008  00004128  000018E6  30-03-2018 22:13:10  798C5104  [0069B8C9-0069D1AE]  config/arb/DBPSK.wav
0069D1AF  2.0  0000  0008  000002EE  00000022  30-03-2018 22:13:10  5A7659F3  [0069D1EC-0069D20D]  config/arb/demo_stairdn_ram.bin
0069D20E  2.0  0000  0008  00004128  000024FF  30-03-2018 22:13:10  725F01B8  [0069D240-0069F73E]  config/arb/DQPSK.wav
0069F73F  2.0  0000  0008  00004800  000008B4  30-03-2018 22:13:10  35CC51E2  [0069F775-006A0028]  config/arb/lina2_512.bin
006A0029  2.0  0000  0008  00012000  00001D55  30-03-2018 22:13:10  7F7243D2  [006A005F-006A1DB3]  config/arb/lina_2048.bin
006A1DB4  2.0  0000  0008  00004126  000024F7  30-03-2018 22:13:10  17FB12F4  [006A1DE5-006A42DB]  config/arb/QPSK.wav 
006A42DC  2.0  0000  0008  00005453  00004395  30-03-2018 22:13:10  39E03C4E  [006A4323-006A86B7]  config/arb/SDG2000X_Arb_Summary_V1.2.xlsx
006A86B8  2.0  0000  0008  00012000  0000A7F4  30-03-2018 22:13:10  FA31F4C2  [006A86EA-006B2EDD]  config/arb/sin17.bin
006B2EDE  2.0  0000  0008  00004800  000033C2  30-03-2018 22:13:10  17FB0A6B  [006B2F14-006B62D5]  config/arb/sin17_512.bin
006B62D6  2.0  0000  0008  00012000  0000B4DE  30-03-2018 22:13:10  F9E0DBA7  [006B6308-006C17E5]  config/arb/sin31.bin
006C17E6  2.0  0000  0008  00004800  000034D6  30-03-2018 22:13:10  BC4B9BED  [006C181C-006C4CF1]  config/arb/sin31_512.bin
006C4CF2  2.0  0000  0008  00004800  0000360D  30-03-2018 22:13:10  55FA7453  [006C4D27-006C8333]  config/arb/sinc_512.bin
006C8334  2.0  0000  0008  00012000  0000BCD5  30-03-2018 22:13:10  A32E0CB8  [006C8369-006D403D]  config/arb/sin_2048.bin
006D403E  2.0  0000  0008  0000110C  000010A8  30-03-2018 22:13:10  571A43E0  [006D406F-006D5116]  config/arb/test.wav 
006D5117  1.0  0000  0000  00000000  00000000  26-06-2018 17:23:16  00000000  [006D5141-006D5140]  config/fpga/
006D5141  2.0  0000  0008  002DF366  000E498A  03-05-2018 18:41:22  B01C15D8  [006D5171-007B9AFA]  config/fpga/iq.bit
007B9AFB  2.0  0000  0008  003DBB6C  0005BC7D  26-06-2018 16:18:05  987195DC  [007B9B39-008157B5]  config/fpga/top_unicorn_zynq.bit
008157B6  2.0  0000  0008  002DF367  00139056  03-05-2018 18:41:22  66FDC721  [008157F3-0094E848]  config/fpga/unicorn_k7_fpga.bit
0094E849  2.0  0000  0008  000000FF  00000086  03-05-2018 18:41:22  5CD202F6  [0094E889-0094E90E]  config/NSP_config_upgrade_info.xml
0094E90F  2.0  0000  0008  00000DF4  00000408  03-05-2018 18:41:22  F08CA04A  [0094E946-0094ED4D]  config/NSP_limit_data.xml
0094ED4E  2.0  0000  0008  000000ED  0000008A  03-05-2018 18:41:22  EC0A19A9  [0094ED86-0094EE0F]  config/NSP_system_info.xml
0094EE10  2.0  0000  0008  0000022F  00000103  03-05-2018 18:41:22  A67A123B  [0094EE4F-0094EF51]  config/NSP_trends_config_info.xml
0094EF52  1.0  0000  0000  00000000  00000000  26-06-2018 17:19:03  00000000  [0094EF7F-0094EF7E]  config/ui_data/
0094EF7F  2.0  0000  0008  00000034  00000036  03-05-2018 18:41:22  C00B0D37  [0094EFC1-0094EFF6]  config/ui_data/english_help_info.xml
0094EFF7  2.0  0000  0008  0000DC0A  00001226  03-05-2018 18:41:22  507A3AFF  [0094F039-0095025E]  config/ui_data/english_menu_info.xml
0095025F  2.0  0000  0008  0000554C  00001326  03-05-2018 18:41:22  0ED5F8BE  [009502A1-009515C6]  config/ui_data/english_text_info.xml
009515C7  2.0  0000  0008  00000034  00000036  03-05-2018 18:41:22  C00B0D37  [00951606-0095163B]  config/ui_data/simp_help_info.xml
0095163C  2.0  0000  0008  0000DEE3  000013D2  03-05-2018 18:41:22  560B79A4  [0095167B-00952A4C]  config/ui_data/simp_menu_info.xml
00952A4D  2.0  0000  0008  00005240  000014C6  03-05-2018 18:41:22  3CB8306C  [00952A8C-00953F51]  config/ui_data/simp_text_info.xml
00953F52  2.0  0000  0008  00000043  0000003E  03-05-2018 18:41:22  9FD467D9  [00953F82-00953FBF]  config/version.txt
00953FC0  1.0  0000  0000  00000000  00000000  26-06-2018 17:19:04  00000000  [00953FE6-00953FE5]  drivers/
00953FE6  2.0  0000  0008  00002C5E  00000FB4  03-05-2018 18:41:22  9E392D9E  [00954013-00954FC6]  drivers/gpib.ko
00954FC7  2.0  0000  0008  000069A5  00002875  03-05-2018 18:41:22  75D3D5E3  [00954FF8-0095786C]  drivers/g_usbtmc.ko 
0095786D  2.0  0000  0008  0000ECB5  00005D32  03-05-2018 18:41:22  50E7B35A  [009578A2-0095D5D3]  drivers/libcomposite.ko
0095D5D4  2.0  0000  0008  00002965  00000E97  03-05-2018 18:41:22  50725F38  [0095D606-0095E49C]  drivers/siglentkb.ko
0095E49D  2.0  0000  0008  00002087  00000A7D  03-05-2018 18:41:22  6C85FEBF  [0095E4DA-0095EF56]  drivers/siglent_overload_irq.ko
0095EF57  2.0  0000  0008  00001FF5  00000A65  03-05-2018 18:41:22  D022F4A3  [0095EF91-0095F9F5]  drivers/siglent_touch_irq.ko
0095F9F6  2.0  0000  0008  000020E5  00000ACC  03-05-2018 18:41:22  9A061A8A  [0095FA32-009604FD]  drivers/siglent_usbflag_irq.ko
009604FE  2.0  0000  0008  00002396  00000D39  03-05-2018 18:41:22  EB447535  [00960533-0096126B]  drivers/siglent_vdma.ko
0096126C  2.0  0000  0008  00003729  00001639  03-05-2018 18:41:22  77B79D3A  [009612A3-009628DB]  drivers/xilinx_axicdma.ko
009628DC  2.0  0000  0008  00003B9B  00001758  03-05-2018 18:41:22  651931A8  [00962912-00964069]  drivers/xilinx_axidma.ko
0096406A  2.0  0000  0008  0000412D  0000199B  03-05-2018 18:41:22  45D124EA  [0096409E-00965A38]  drivers/xilinx_vdma.ko
00965A39  1.0  0000  0000  00000000  00000000  26-06-2018 17:19:04  00000000  [00965A61-00965A60]  firmdata0/
00965A61  2.0  0000  0008  000000ED  0000008A  03-05-2018 18:41:22  EC0A19A9  [00965A9C-00965B25]  firmdata0/NSP_system_info.xml
00965B26  2.0  0000  0008  0000025A  0000010C  03-05-2018 18:41:22  71729FAF  [00965B68-00965C73]  firmdata0/NSP_trends_config_info.xml
00965C74  2.0  0000  0008  00000043  0000003E  03-05-2018 18:41:22  9FD467D9  [00965CA7-00965CE4]  firmdata0/version.txt
00965CE5  2.0  0000  0008  0093BFF0  002AE09B  27-06-2018 01:18:08  DAF23EC5  [00965D0A-00C13DA4]  awg.app
00C13DA5  2.0  0000  0008  00467A1C  00094A88  26-06-2018 10:16:11  F183FD0C  [00C13DCB-00CA8852]  BOOT.bin
00CA8853  2.0  0000  0008  00003D6C  00000FCD  03-05-2018 18:41:22  BA7B5E61  [00CA887F-00CA984B]  devicetree.dtb
00CA984C  2.0  0000  0008  009FB000  009F5967  03-05-2018 18:41:22  F88E82FB  [00CA9877-0169F1DD]  rootfs.cramfs
0169F1DE  2.0  0000  0008  002F9EF8  002F48B5  03-05-2018 18:41:22  2D57AE62  [0169F202-01993AB6]  uImage
01993AB7  2.0  0000  0008  00000A28  000002C9  03-05-2018 18:41:22  A2F49362  [01993ADE-01993DA6]  update.sh
Disk Entries: 281   Total Entries: 281   Directory Size: 30936 bytes  [01993DA7-0199B67E]
****************************************************
  File Processed OK
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tautech on July 26, 2018, 07:54:35 pm
New firmware for SDG6000X series.

Version 6.01.01.29R10
26.2 MB
https://www.siglentamerica.com/download/6886/ (https://www.siglentamerica.com/download/6886/)

Changelog
2. Optimized jitter performance of Square and Pulse


Do you know what "optimized jitter performance" means in terms of specification?

Thanks,
John
Sorry, no particular knowledge on why Siglent has addressed this.
From the datasheet Square wave spec:
Jitter (rms) cycle to cycle 100 ps.

That seems quite a bit to me for a cycle to cycle spec so I guess they've made it much better.
IIRC Shahriar (TSP) picked up on jitter could be better. Have you watched his video ? I linked it in the OP.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: JohnG on July 27, 2018, 12:20:33 am
Thanks, I saw the original 100 ps RMS spec, and it's about 2x too much for what I wish to do. It is a bigger problem if it is non-random, which I suspect is the case based on my experience with the SDG2042x (which is a fantastic siggen for the price).

Thanks,
John
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tautech on July 27, 2018, 12:56:19 am
Thanks, I saw the original 100 ps RMS spec, and it's about 2x too much for what I wish to do. It is a bigger problem if it is non-random, which I suspect is the case based on my experience with the SDG2042x (which is a fantastic siggen for the price).

Thanks,
John
For all we know it will be much better that the 100ps max spec'ed in the datasheet but it really needs someone to run some checks to see what typical jitter is now.
I should really get around to getting the 500 MHz demo model offered or do I wait and see if they'll bring out something even higher BW.  :-//
Maybe I'll shoot an email to tech support for typical jitter values as they are now.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: gperoni on July 29, 2018, 06:01:53 pm
tv84, any plans on releasing the SDG6000X hack? I would like to purchase one :)
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tv84 on July 29, 2018, 08:42:55 pm
tv84, any plans on releasing the SDG6000X hack? I would like to purchase one :)

Now that you have a FW update with root access is just a question of applying some of the knowledge of the SSA thread. One of the ways is identical.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: nctnico on July 29, 2018, 08:58:57 pm
tv84, any plans on releasing the SDG6000X hack? I would like to purchase one :)

Now that you have a FW update with root access is just a question of applying some of the knowledge of the SSA thread. One of the ways is identical.
Please just post a step-by-step plan. Being cryptic doesn't help anyone.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: gperoni on July 29, 2018, 09:25:23 pm
I think that actually helps a lot... thank you tv84! :)
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: bson on July 30, 2018, 09:06:44 am
Is it the same hardware in the 200 and 500MHz units?  If so, then this looks quite attractive...
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tautech on July 30, 2018, 09:08:36 am
See reply #59.  :)
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: gperoni on August 14, 2018, 09:29:55 am
Ok so, first off, a HUGE thank you to janekivi, as only thanks to his file (https://www.eevblog.com/forum/testgear/siglent-ads-firmware-file-format/msg1740527/#msg1740527) I got root access to the device.

@tv84: I tried reading the SSA thread and pretty much all the methods, the only one that seems to work for me (upgrading from 200 to 500 MHz) is removing (moving to a different name) the /usr/bin/siglent/NSP_system_info.xml file. Touching the NSP_trends_config_info file results in me losing the PRBS/IQ entry in the Waveform menu. I tried playing around with the ./config directory too, as some files there are the same or similar, but I couldn't get the IQ option to work (the 500 MHz hack works fine though!).

Can you write a line on what you did?

Thank you :)
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tv84 on August 15, 2018, 02:41:51 pm
Can you write a line on what you did?

There are several alternatives... The most accessible for everyone: search in the memdump.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tautech on August 16, 2018, 07:52:30 pm
well, screen is about twice as big..
in the lecroy we demoed the touchscreen was so bad that you had to press too hard to use it and when you didn't move your finger the cursor would move frenetically. with a stylus, not so bad but at that point i'd rather use a mouse thank you very much :(
@ JPortici
I've not long had the new SVA1015X SA/VNA unit, it has a 10" touch screen as well as the normal UI so to address any reservations you might have on the latest Siglent touch screens I can assure you this new SVA screen is a joy to drive. There's also some shortcut menu icons and they're very nice to use.
This SVA is the first big touch display we've seen from Siglent other than the WS3000 that LeCroy market and Siglent engineers look to have done a nice job implementing it.
SVA also offers mouse and keyboard control......I've only had a little play with it and only with a wireless KB/mouse combo which of course is not ideal for SA usage.
Hope that addresses any nagging doubts you had.  :)
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: TurboTom on September 13, 2018, 06:14:38 pm
Today I received an SDG6022X and I've got to admit I'm already disappointed after the first ten minutes of testing. I believed (I know, that's generally a bad thing to do when purchasing Chinese test gear...) that I could use it to replace my Rigol DG4102 but as it seems, it's got EXACTLY the same shortcomings as the latter! You may find my rants about the Rigol generator here: https://www.eevblog.com/forum/testgear/annoying-bug-in-rigol-dg4000-series-function-generator/ (https://www.eevblog.com/forum/testgear/annoying-bug-in-rigol-dg4000-series-function-generator/)

I found the SDG6000x to generate runt pulses if "Waveform: Pulse" is selected and the pulse width is adjusted with the encoder. That is a job that's not too special to tolerate this behavior, shown in the attached screenshots.

The user interface is partially okay and partially still a nightmare, especially considering the availability of the touchscreen. Selecting built-in arbitrary waveforms is virtually the same catastrophe as with the Rigol. Siglent, don't copy other's crappy solutions, rather have your engineers use their own brains! A list of some 200 ARB waveforms without any way to quickly scroll through them with at least a small indication of their shape is mostly useless. At least in my opinion.

The incremental encoder on this machine also skips a step now and then although it's by far not as bad as on the DG4000. Anyway, to reliably do incremental adjustments of pulse widths or frequencies or whatyoulike without looking at the screen, just by sensing the detents of the encoder, it simply isn't good enough.

I didn't do much more testing so far, rise time and general signal quality looks decent at the first glance. But considering the price of the instrument, I've got to admit that I expected more than that, especially usability-wise. Or am I asking too much?

Probably I'll have a second, more thorough look at the instrument during the next days but if my first impressions prevail, this thing will get returned...
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tautech on September 13, 2018, 07:24:30 pm
Tom, can I ask if this unit has the latest firmware installed, Version: 6.01.01.29R10 ?
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: TurboTom on September 13, 2018, 08:44:07 pm
Yes it came from the distributor with the mentioned firmware installed.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tautech on September 13, 2018, 08:53:38 pm
Yes it came from the distributor with the mentioned firmware installed.
Thanks for confirmation. I'll pass your findings to the factory.
Probably I'll have a second, more thorough look at the instrument during the next days but if my first impressions prevail, this thing will get returned...
Yes do that and study what it can do and a liberated one can.  ;)
If you want to venture that path these units are good value.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: TurboTom on September 14, 2018, 09:28:17 am
Did some more testing already and my impression of the instrument doesn't get better. The signal appears to get interrupted/distorted upon any timing-related change of the settings via the incremental encoder, regardless of the waveform. I attached three screenshots, the fist changing the frequency of a 5kHz sine by one least significant digit, the second the same thing for a 50% duty cycle square (now also a runt pulse is generated), and finally I change the duty cycle by 1% of the same square wave, causing the signal to pause for more than 2ms. If you use the generator to test a switch mode power stage, it easily goes "poof"  :-BROKE if this happens with the drive signal.

Edit: Just added a screenshot of what a frequency change looks like on the Rigol DG4000 (same for ramp; sqare & pulse similar or even a little worse than on the SDG6000X).

Edit 2: I figured out that if the -> Utility -> Phase Mode setting is changed from the default "Phase Locked" to "Independent", the Sine (and probably also Ramp) signal permit change of frequencies without the mentioned discontinuities. So in this configuration, the SDG6000X performs just as the Rigol DG4000. Square and pulse still broken, unfortunately.

The user interface will also easily ruin your day since it doesn't store the digit of the parameter that was adjusted, i.e. if you do fine adjustments of the frequency (say you're changing the 100Hz digit of a 100kHz output signal) via the encoder and then do an amplitude correction, to return to the frequency adjustment afterwards, you will be adjusting the 100kHz digit. This kind of behavior is very unproductive since especially in case of a signal generator, you're usually not looking at the generator's screen but at the screen of an oscilloscope or other test gear to observe the results of changes of the input parameters to your DUT. It must be possible to reliably change parameters incrementally without having to look at the generator all the time only to check that it's performing correctly.

The SDG6000X may have many bells and whistles but still it has to operate as a plain and simple "old" versatile fequency generator in my opinion. If it doesn't work okay in all these modes, I consider it not up to the task and not worth the money. Even the Rigol DG4000 performs better in many of these scenarios, and the best generator I own concerning this, is my cheapest one (though it's -- been -- plagued with other problems), the Hantek HDG2002B.

So far I think Siglent should focus on the details that make an instrument comfortable and enjoyable to use in real lab scenarios, otherwise (and here I remember one statement from some other thread about LCR meters, refering to some TFT-equipped poo ...) the instrument is not much more than some touchscreen-featured poo.

Even though all these issues can probably be adressed by firmware / FPGA code updates, I doubt that Siglent will take care of them all. I haven't got any experience with the SDG2000X generator but I assume that the SDG6000X's code bases heavily on the aforementioned one so I'm almost certain that these shortcomings can be found there as well (maybe someone who owns an SDG2000X could test it?). If this is the case and Siglent didn't adress these problems yet, I doubt they will do so on the SDG6000X either. I will test the generator probably for a week or two and then return it. It's not worth the money if you're not buying it specifically for its I/Q functionality (costs more money, I don't want to talk about the "liberation of options" here and now), the baseline model is just not adequate as an allround lab generator that's confortable to use. In it's current condition, I'ld rate it two stars out of five for its signal quality and fast slopes. It's too expensive for its usability value.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: MrW0lf on September 14, 2018, 12:41:08 pm
I haven't got any experience with the SDG2000X generator but I assume that the SDG6000X's code bases heavily on the aforementioned one so I'm almost certain that these shortcomings can be found there as well (maybe someone who owns an SDG2000X could test it?).

No switching issues with SDG2000X. Still very pleased with my 4 channel 120MHz phase locked combo for <1000€ ;)

(https://www.eevblog.com/forum/testgear/siglent-sdg6000-series-awg_s/?action=dlattach;attach=523037;image)
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: TurboTom on September 14, 2018, 12:53:52 pm
Thanks for testing this @MrWolf -

so there may be hope that Siglent will sort this problem on the SDG6000X eventually...
If this will happen in acceptable time for me to risk to keep the instrument is another question, though  :-\
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: MrW0lf on September 14, 2018, 01:28:48 pm
Edit 2: I figured out that if the -> Utility -> Phase Mode setting is changed from the default "Phase Locked" to "Independent", the Sine (and probably also Ramp) signal permit change of frequencies without the mentioned discontinuities. So in this configuration, the SDG6000X performs just as the Rigol DG4000. Square and pulse still broken, unfortunately.

Oh no! :scared:
Phase Locked it was, but switched CH Copy Coupling=OFF (before both channels were locked in all but phase deviation). 5kHz square on one channel, set second channel to 20MHz. Now look :'(
Glitches on both channels but <50us, not ~2ms like in your case.

(https://www.eevblog.com/forum/testgear/siglent-sdg6000-series-awg_s/?action=dlattach;attach=523061;image)

However when I set to Independent, duty transition is again seamless. Now if think about it may be indeed somewhat problematic to do seamless switch when both channels phase locked, and run different frequencies. But it might work a little better... Think would be helpful if mr tautech pokes HQ a bit on this...
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: TurboTom on September 14, 2018, 02:33:04 pm
In my tests, I was't looking at different channels. It's just a single one that pauses for a certain duration (probably while the FPGA is reconfigured) and then resumes to output the signal with the new parameters. No phase lock, no coupling, just a single channel. And in my opinion it must be possible to get a seamless signal changes in square and pulse mode (if minimum slope times are configured so no slope scaling is required).

I did some more tests regarding time base accuracy and this looks quite good. I find on "my" specimen the time base to be approx. 0.6ppm slow, i.e. if I enter a frequency of 10.0000059MHz to be generated, I get a slow drift on the scope agains my 10MHz Rb source as shown on the screenshot. It's funny that I just must have recorded an adjustment step of the TCXO that's used as the reference inside the SDG6000X.

DC amplitude accuracy looks good, deviating next to nothing below 3V and a maximum of 0.5% at 10V. AC level accuracy still needs to be tested.

Edit: I just checked level accuracy of the Sine wave from 100kHz to 200MHz (instrument isn't "liberated") with my venerable HP 436A + 8482A and found it (converted to Veff) to be better than -0 / +0.8% absolute on both channels over the full range (-0 / +0.07dB). So it's well within spec.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: MrW0lf on September 14, 2018, 03:46:00 pm
Can you please check how 5kHz 50=>51% duty transition looks on DG4000 with second channel phase locked and set to max square freq (or 20MHz like in my test)? This could prove a good "torture test" for gen. Solving this situation elegantly would require certain effort.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tautech on September 14, 2018, 08:45:12 pm
Think would be helpful if mr tautech pokes HQ a bit on this...
Done yesterday but it's the weekend here and at HQ now.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: TurboTom on September 14, 2018, 08:49:51 pm
@MrWolf

Okay, here we are. Frequencies were 5kHz and 40MHz (CH1 / CH2), phase coupling between the two with CH1 as "master" as shown in the first screenshot. The DG4000 pauses a long time, more than 6ms and also produces some glitch in between as shown in the last screenshot. It performs clearly worse than the SDG6000X. But in my opinion the difference is marginal as long as there's a pause at all. This renders the generator useless for many critical applications.

One clear advantage of the DG4000 is its frequency counter which is way more advanced than those included with any other AWG, featuring full statistics and graphics display. But that's not really what I get an AWG for even though it may be a nice "goodie" if everything else was working flawlessly...
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: TurboTom on September 15, 2018, 10:13:00 pm
I guess I have missed the opportunity to download the file "SDG6000X_eevblog_29R10.zip" linked to by @janekivi about a month ago. Now the wikisend link has expired and I would like to gain root access to my SDG6000X. Any chance someone could upload it again or provide it attached to a PN? You would do me a great favor and I'll be eternally thankful  ;).

Cheers,
Thomas
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tv84 on September 16, 2018, 11:39:10 am
I guess I have missed the opportunity to download the file "SDG6000X_eevblog_29R10.zip" linked to by @janekivi about a month ago. Now the wikisend link has expired and I would like to gain root access to my SDG6000X. Any chance someone could upload it again or provide it attached to a PN? You would do me a great favor and I'll be eternally thankful  ;).

Does that mean you are convinced by the SDG6000X?   ::) 
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: janekivi on September 16, 2018, 11:49:09 am
For next 30 days
SDG6000X_eevblog_29R10.zip (https://ufile.io/r9rah)
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: 2N3055 on September 16, 2018, 07:14:01 pm
I did a quick test on a DG1032Z.

1. Sinewave is glitch free
2. Square and pulse wave is glitch free up until 1MHz, for both frequency and duty cycle. Over 1MHz they start glitching.
3. Ramp is glitching all the time
4. AWG seems to be glitch free

Glitches are represented with abrupt cutoff of generated waveform at whatever random moment, creating really short runt pulse, followed by 3-4 ms zero level without signal generated..

Didn't try chanel phase coupling..
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: TurboTom on September 16, 2018, 08:11:48 pm
I guess I have missed the opportunity to download the file "SDG6000X_eevblog_29R10.zip" linked to by @janekivi about a month ago. Now the wikisend link has expired and I would like to gain root access to my SDG6000X. Any chance someone could upload it again or provide it attached to a PN? You would do me a great favor and I'll be eternally thankful  ;).

Does that mean you are convinced by the SDG6000X?   ::)

No, actually I'm looking for a way to convince myself to keep it, bad case of TEA, you know what I mean  ;)

Thanks a lot to all those who helped me with getting root access to the device by PM or on the forum.

As it seems, Siglent intended to also provide bandwidth upgrades but they may have shelved that idea. So far, I'm still ambiguous regarding the performance of the SDG6000X. Signal quality, accuracy and options are really good but the shortcomings that I mentioned are showstoppers for me and the applications that I'ld like to use the instrument for. Fortunately, I've still got a few weeks time to make a decision.

Cheers,
Thomas
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: willie.from.texas on September 17, 2018, 11:46:17 pm
I upgraded both my SDG6022X function generator and my SDS1104X-E four channel oscilloscope. Here is an indication of my performance improvement from both updates.  The chart below was generated using a 1.5Vpp sine wave driving a 50 ohm load through a 12" coax as measured by the oscilloscope...
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: TurboTom on September 18, 2018, 06:50:19 am
I've got some new findings with the SDG6022X that appear to indicate that there's actually a hardware difference between this and the higher rated models of the SDG6000X series that preclude hacks to higher frequencies. As yet, I'm not 100% sure since the behaviour may also point into the direction of a hardware problem of the particular unit that I got. Anyway, currently my recommendation to all those who are playing with the thought to purchase such an instrument with the perspective of a bandwidth upgrade, don't take it for granted that it will work.

I've got to review some screenshots and edit some recordings before I can post a more detailed report of my findings. This may happen later today or tomorrow...
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: markus_jlrb on September 18, 2018, 02:12:21 pm
Dears,

FYI

just to show you my experience with the SDG6022X device.
Was playing with FSK sigs.
The attached pics, show a 2MHz/10MHz carrier switched with
1MHz frequency.
To get a proper 0V change in frequency some adjustments
with phase angle parameter were necessary due to coax
delay to the dso.
Extern triggering with switching frequency was done on a
SDS2000X.

So for my purpose the dev is quite suitable.

Markus
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: TurboTom on September 18, 2018, 09:13:08 pm
As I mentioned before, I did some more experiments with the SDG6022X and made some peculiar findings. As it seems, the instrument (at least the one that I have got) is either speed graded or defective. In its original configuration, I initially didn't find any unforseen behavior except for the short pauses when changing settings that I mentioned several posts above.

Now that I was able to "liberate" the machine with the help of @janekivi's firmware file  :-+, I did some more testing and initially everything appeared to work normally. After some testing, I noticed more and more strange reaction to parameter changes which finally led to the following two video clips (I apologize for the unsteady camera, I recorded the clip with my cell phone and had to operate the AWG / 'scope with the left hand... but I guess it hilights my points):

http://www.turbinemuseum.de/files/SDG6000X/SDG6000X_lib1.mp4 (http://www.turbinemuseum.de/files/SDG6000X/SDG6000X_lib1.mp4)

http://www.turbinemuseum.de/files/SDG6000X/SDG6000X_lib2.mp4 (http://www.turbinemuseum.de/files/SDG6000X/SDG6000X_lib2.mp4)

Please keep in mind that these two clips had been taken with the "liberated" machine, even though the software configuration should have matched a stock SDG6052X. I even rolled back the firmware (to the stock one without known root access) without any observable change. I also got the impression that the effect worsened over time. It is definitely not related to operating temperatures of the instrument since I just powered it up before the first take after it had been disconnected from mains over the night.

After that I removed all my patches completely so the instrument is in its original configuration as I initially received it. The following tests didn't show any of the curiosities that I observed before, it reacts flawlessly to keyboard inputs (well, at least not worse than before... ::) ). What I noticed when I observed steep square wave or pulse edges is some minor "undulation" or whatever one may call it, shown in the following clip (sorry, german language since I thought I may use it for my future correspondence with the distributor):

http://www.turbinemuseum.de/files/SDG6000X/SDG6000X_org1.mp4 (http://www.turbinemuseum.de/files/SDG6000X/SDG6000X_org1.mp4)

I'ld be glad if those of you who own or have access to one of these AWGs could try to replicate these tests and report their findings. Proper termination and wiring is required during all of these tests.

One thing that really surprises me is that Siglent must be calibrating all the units up to 500MHz since the amplitude flatness over the full range is superb. With an HP RF power meter, I find the 0dBm level to fall between 0.05 and 0.15 dBm from 100kHz to 500MHz, a reading taken every 10MHz. Interestingly, with an offset of 2V (the HP 8482A power sensor is A/C coupled at the input with a capacitor of approx. 125nF), the level flatness goes pretty much south (relatively speaking) with excursions of 0.9dBm around 330MHz.

This obvious full-range calibration makes me wonder if the particular unit that I got may actually be faulty. But I'll have some difficulty explaining why it's faulty while it performs okay  (-ish) in its specified frequency range. I guess I'm just gonna return it and don't start any arguments at all. Just don't like it...  ;) And maybe go for another one after (if?) Siglent addressed the pauses during parameter changes.

Cheers,
Thomas




Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tautech on September 18, 2018, 10:22:14 pm

This obvious full-range calibration makes me wonder if the particular unit that I got may actually be faulty. But I'll have some difficulty explaining why it's faulty while it performs okay  (-ish) in its specified frequency range. I guess I'm just gonna return it and don't start any arguments at all. Just don't like it...  ;) And maybe go for another one after (if?) Siglent addressed the pauses during parameter changes.
Tom can I ask why you would attempt to evaluate a 200 MHz (stock) or 500 MHz (liberated) AWG with a 70 MHz DSO ?  :-//
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: TurboTom on September 18, 2018, 10:49:33 pm
@tautech -- you've got a completely valid point here, please see the attached screenshot of the system info page of the "DS2072A-S". I got this scope for comparably little money from Rigol EU's clearance sales , not only did it contain the MSO hardware, but was also easily convinced to operate as the MSO2302A-S. Rise time is 1ns and -3dB bandwidth is in the ballpark of 370MHz. If it will make you feel more comfortable, I'll pull the Tek 2465 from the basement and replicate the tests with this one (provided it will still power up without errors... ;)).

Cheers,
Thomas
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tautech on September 18, 2018, 11:16:27 pm
@tautech -- you've got a completely valid point here, please see the attached screenshot of the system info page of the "DS2072A-S". I got this scope for comparably little money from Rigol EU's clearance sales , not only did it contain the MSO hardware, but was also easily convinced to operate as the MSO2302A-S. Rise time is 1ns and -3dB bandwidth is in the ballpark of 370MHz. If it will make you feel more comfortable, I'll pull the Tek 2465 from the basement and replicate the tests with this one (provided it will still power up without errors... ;)).

Cheers,
Thomas
Your reply was as expected  ;) so now I ask just as you have about the SDG6022X and higher BW liberated performance, how do you know performance of your liberated DSO matches a 'factory' MSO2303A ?
Truth is we can't say for absolute sure, just as we can't say 110% the SDG6022X liberated to SDG6052X operates perfectly as expected.
But then we know both your DSO and SDG6022X are BW limited so I don't understand why you would even question 'liberated' performance when using a liberated DSO.  :-//

As to unexplained SDG behavior your video (to me) didn't show the settings well enough for your scope and if Auto triggering was being used so this behavior could be explained if you were using Normal triggering.
Points you have identified in earlier posts have been bought to Siglent's attention so we do expect changes in forthcoming FW to address these. Further, all three X series AWG's have very similar UI's and so improvements to another series will permeate into the other AWG's.

Thanks for your explorations into the SDG6000X series.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: dpenev on September 19, 2018, 07:00:26 am
Hi Thomas,

I have tried to reproduce the issue from your first video (1MHz square wave 60% duty cycle) but it seems the square wave is OK at my side.
Probably you hit a problematic unit? Please let us know how the discussion with the distributor goes.
 
 
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: TurboTom on September 19, 2018, 08:53:28 pm
Today I conducted several more tests with the SDG, among them also an attempt to "liberate" the instrument differently with apparently better results than before. Still I find some peculiar characteristics of which I'm not sure if they are correct. But let's start with a video clip of the instrument in its original configuration. My main objective was to decouple the output waveform from triggering of the oscilloscope. Fortunately, the SDG6000X features an AUXiliary connector at the rear that provides a sync signal if configured that way.  Unfortunately, the disappointment followed almost immediately after connecting it to the scope and powering it up -- there's considerable jitter between sync and the output phase and the sync is only available up to a frequency of 10MHz   ::). Anyway, here's the first clip, me demonstrating the sync / output jitter and some other strange stuff:

http://www.turbinemuseum.de/files/SDG6000X/SDG6000X_org2.mp4 (http://www.turbinemuseum.de/files/SDG6000X/SDG6000X_org2.mp4)

After that I decided to have another go at "liberating" the machine, this time utilizing a different method. I won't go into detail here since I'm still not sure if it's a good idea to try this but whatsoever, apparently it worked a little better this way. At least the malfunctions of the waveform buttons have disappeared. Still, I find considerable "undulation", especially in pulse mode with 1ns rise/fall times and short pulses (< 10ns). At rise/fall times >= 2ns, the undulation almost disappears. I'ld be glad if someone could try to replicate this experiment with a fast scope. Regarding the scope that I use I've got to add (to eliminate any abiguities right from the start) that it's an "improved" Rigol MSO4014. Since Rigol themselves offer these bandwidth upgrades for this model, we can safely assume that the hardware is capable of the "liberated" bandwidth. It's upgraded to the full 500MHz, reporting the improvement as "official" . Here's the clip:

http://www.turbinemuseum.de/files/SDG6000X/SDG6000X_lib3.mp4 (http://www.turbinemuseum.de/files/SDG6000X/SDG6000X_lib3.mp4)

I'ld be really glad for some feedback regarding this test since it will help me to understand if my SDG6022X has got a problem or not.


After that and after having seen all the jitter and wiggles and whatnot, I thought to myself that it's time to pull the HP 53310A Modulation Domain Analyzer from the basement and have a go at the SDG6022x...  >:D

To cut a long story short, in general the SDG is performing quite well IF an external reference gets used. The internal reference -- well, let's put it that way -- could be better...
The MDA basically is a very fast, very accurate frequency counter with integrated digital processing to provide a graphical representation of the measurements (especially histograms). It's primary display mode is frequency vs. time but it can sum up the results (just like a multi-channel analyzer) to provide a histogram that somewhat resembles a spectrum, yet it's not the level on the vertical axis but the quantity of the measurements that fall within the limits of that channel.

Most of the measurements I did are close to the limit of the MDA since the performance of the SDG6000X is quite good. But anyway, it shows some interesting details of the instrument.  Please bear with me for the many large photos I attached:

(http://www.turbinemuseum.de/files/SDG6000X/MDA_Ref10M_Sine.jpg)
Here we start with a measurement of the reference generator itself. It consists of an Efratom LPRO-101 rubidium oscillator, a five channel isolation amplifier and a pulse shaper with three square wave outputs of 2.5, 3.3 and 5V. This reference is fed to the MDA as well as for some of the tests to the SDG6000X. This initial test is meant to show where the limits of the MDA are.

(http://www.turbinemuseum.de/files/SDG6000X/MDA_Ref10M_Square.jpg)
This photo shows the same setup as before but now the 5V square signal output is tested. It's amazing how much better 9.6mHz vs. 23mHz (this is millihertz!) the standard deviation of the frequency is. This basically is the result of the steeper edges of the square wave and hence the lower jitter of the input trigger / digitizing stages. We are right at the edge of the instrument's performance.

(http://www.turbinemuseum.de/files/SDG6000X/MDA_SDG10M_Sine_INT.jpg)
That's the first test of the SDG6000X, utilizing its internal reference oscillator. I decided to adjust amplitude of the sine wave to be 7dBm since the Rb reference outputs the same level. The histrogram looks pretty "how-you-doing" and the standard deviation is almost tenfold of what the RB source provides (this means jitter or phase noise).

(http://www.turbinemuseum.de/files/SDG6000X/MDA_SDG10M_Sine_EXT.jpg)
For this test, I connected the external REF input of the SDG6000X to the RB reference. It's quite amazing how the figures change --  the standard deviation now is only slightly worse than the one of the reference itself. A more than eight-fold improvement...

(http://www.turbinemuseum.de/files/SDG6000X/MDA_SDG10M_Square_EXT.jpg)
For direct comparison with the reference, I also tested the SDG with a 10MHz square -- once again, the difference to the reference is neglible.

In the following tests, I step up with the frequency in 100MHz steps, initially to 300MHz:

(http://www.turbinemuseum.de/files/SDG6000X/MDA_SDG100M_Sine_EXT.jpg)

(http://www.turbinemuseum.de/files/SDG6000X/MDA_SDG200M_Sine_EXT.jpg)

(http://www.turbinemuseum.de/files/SDG6000X/MDA_SDG300M1_Sine_EXT.jpg)
Here the frequency limits of channel A of the MDA are already exceeded, yet it still appears to work okay. Moreover, at 300MHz the SDG cannot sustain a level of 7dBm anymore which may also contribute a little to higher trigger / digitizing jitter. Hence I did the same measurement on channel C of the MDA again:

(http://www.turbinemuseum.de/files/SDG6000X/MDA_SDG300M2_Sine_EXT.jpg)
This channel is equipped with a down converter. Since it requires its own local oscillator (PLL), it adds to the total jitter with some 100mHz in this configuration.

(http://www.turbinemuseum.de/files/SDG6000X/MDA_SDG400M_Sine_EXT.jpg)

(http://www.turbinemuseum.de/files/SDG6000X/MDA_SDG500M_Sine_EXT.jpg)
Finally at the limit of the SDG... It's amazing that at 500MHz -- provided the proper reference is used -- the generator produces less than 5Hz of total peak-to-peak jitter with a standard deviation of just a little more than half a hertz! Center frequency inaccuracy is just about 0.3Hz. For comparison, 500MHz with the internal reference:

(http://www.turbinemuseum.de/files/SDG6000X/MDA_SDG500M_Sine_INT.jpg)
Funny how much worse the SDG's internal reference is: an absolute error of around 240Hz, almost 20Hz Pk-Pk jitter and 4 Hz standard deviation.

Finally, I had to have a look at the internal reference of the SDG. Fortunately, it' got a reference output. Voila:

(http://www.turbinemuseum.de/files/SDG6000X/MDA_SDG_RefOUT.jpg)
I guess that's not bad for a TCXO but the histogram is far from the ideal gauss profile. Probably it's okay for everyday's tasks but for some really accurate jobs, the SDG6000X's performance will improve a lot if a decent external reference is used.

Thanks for reading...that is, if you got that far...  ;)

Cheers,
Thomas


Edit: Corrected link to second video

Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: jhenderson0107 on September 19, 2018, 10:43:45 pm
Turbo -

Can you also measure the phase stability of the trigger output from the SDG on the MDO?  Could be problematic, since it's much lower frequency.  It may allow visualization of the trigger walk that you observed on the scope earlier or highlight jitter on this signal as you manipulate the SDG frequency. 

Jim
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: dpenev on September 20, 2018, 10:42:52 am
Hi Thomas,

I confirm the same behavior as your two videos.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: TurboTom on September 20, 2018, 03:48:24 pm
@dpenev - Thanks a lot for testing that. Your matching result probably confirms that my SDG6022X isn't defective and the observations at the edges of it's operational range are the result of the design and operation principle. It's good to know this since now I don't need to worry about a potentially defective unit and can decide to keep or return it just upon my findings. I guess now we know why Siglent has limited the over/undershoot specs in their datasheet (https://www.batronix.com/files/importiert/Siglent/Funktionsgenerator/SDG6000X_DataSheet.pdf) to rise times of 2ns and above...  :o

By the way, the single AUX In/Out port that is shared between Sync CH1 / CH2 Trigger In CH1 / CH2, Trigger Out CH1 / CH2, Modulation In CH1 / CH2 and Data In in I/Q modulation mode. That's a whole bunch of stuff that's all mutually exclusive. I can very well imagine situations where I would need more than one of these functions. At least combined Sync/Trigger/Modulation ports but separate for CH1 and CH2 would be desirable. I'ld rather do without the frequency counter or have this function shared on one of the ports.

@ Jim - Please have a look at the following photos:

(http://www.turbinemuseum.de/files/SDG6000X/MDA_SDG10M_EXT_SyncOut1.jpg)
This is the freq-vs-time measurement of the Sync output. It appears there are more or less periodic changes between high and low jitter that alter rather abruptly. Since the jitter levels are rather low already, I'm not too sure if this is really something that's present at the SDG's sync output or if it may be some interference picked up from somewhere else. The maximum time base available on the MDA (1s/div) isn't long enough to pick up a complete period of this trace. Since I found that just using a different BNC cable may change the standard deviation of the jitter by 10mHz, I guess we're really searching here the needle in the haystack.

(http://www.turbinemuseum.de/files/SDG6000X/MDA_SDG10M_EXT_Dly_CH1_Sync.jpg)
That's an interesting one: I reconfigured the MDA to operate as an ultrafast timer with high repetition rate. The time delay between input A and B of the MDA is measured and graphically displayed vs. time. Input A is connected to CH1 of the SDG6000X, providing a square wave of 1MHz, and input B is wired to the Sync Out on the rear of the SDG. Now the "walk-through" of the Sync signal vs. the output is clearly shown and also the approx. 3.5ns span of the "jitter" can be directly measured. It also gets obvious that the frequency of the walkthrough depends on the deviation of the output frequency to a multiple of 200kHz.

(http://www.turbinemuseum.de/files/SDG6000X/MDA_SDG1M_EXT_Dly_CH1_CH2.jpg)
Here I tested the phase jitter between CH1 and CH2 of the SDG, outputting the same square wave. As the MDA shows, standard deviation of the phase delay between the two channels is no more than 50ps (since the input / trigger and other circuitry of the MDS also contributes a little to the noise), a pretty good figure.

If Siglent manages to remove the pauses of the output signal when changing parameters like frequency, aspect ratio or pulse width via the rotary encoder, I'ld say the generator is a keeper, despite of the peculiarities when looking very close... I guess there's no piece of test equipment without some quirks. In general, the performance of the instrument is quite good. Bu how can I know if they will address this problem (I guess @tautech does his best to convince them to have a look at the situation. But if the design pertmits the required modifications to sort that out is another question.  Since the SDG6000X is a rather new model, we can probably expect several future firmware updates and maybe some improvements /extensions to its functions as well.

@ Siglent...  ;)  one more thing I wish to have included, and that should be an easy one: Please add in the "Phase" menu besides the existing degrees also a time value. Sometimes it's more comfortable to dial in the phase delay in milli, micro or nanoseconds than having to convert that frequency-dependant to degrees. Maybe also a third option could be added to the channel coupling - phase menu: Degrees offset, degrees ratio and constant time (seconds).

Cheers,
Thomas
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: MrW0lf on September 20, 2018, 06:07:47 pm
Now the "walk-through" of the Sync signal vs. the output is clearly shown and also the approx. 3.5ns span of the "jitter" can be directly measured. It also gets obvious that the frequency of the walkthrough depends on the deviation of the output frequency to a multiple of 200kHz.

That number sounds familiar, I have two SDGs and needed 4 channel sync and some other stuff. There similar number popped up ~3.3ns:
https://www.eevblog.com/forum/testgear/the-siglent-sdg2042x-thread/msg1081666/#msg1081666 (https://www.eevblog.com/forum/testgear/the-siglent-sdg2042x-thread/msg1081666/#msg1081666)
After some hassle it got more less sorted. There are several posts on that page on the subject maybe you get some ideas.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: kerouanton on September 22, 2018, 06:33:34 pm
I upgraded my SDG6022X from 6.01.01.28R1 to 6.01.01.29R10

- I noticed the hardware version was upgraded too (from 02-00-00-a9-30 to 02-00-00-68-38) ?! To what can it refer too? FPGA?
- I would need to revert back to the previous firmware, but I noticed it is not available on any siglent website (siglenteu.com, siglentamerica.com, and siglent.com/old.siglentamerica.com).

Any clue to get this previous firmware, please?

Thanks !
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tautech on September 22, 2018, 08:00:27 pm
I upgraded my SDG6022X from 6.01.01.28R1 to 6.01.01.29R10

- I noticed the hardware version was upgraded too (from 02-00-00-a9-30 to 02-00-00-68-38) ?! To what can it refer too? FPGA?
- I would need to revert back to the previous firmware, but I noticed it is not available on any siglent website (siglenteu.com, siglentamerica.com, and siglent.com/old.siglentamerica.com).

Any clue to get this previous firmware, please?

Thanks !
AFAIK 6.01.01.28R1 was the first product release FW version and it hasn't been released onto the websites.
Siglent sometimes post this original version but in this case they haven't.
Unless they do, presume it's not available.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: TurboTom on September 22, 2018, 08:32:07 pm
May I make a few suggestion for improvements of the user interface?

Since the predefined arbitrary waveforms are a real PITA to access and finding the right one (that may fit a measurement situation best) even more so, wouldn't it be a good idea to have in case of the predefined arbitraries a menu item "Waveform Item" on the right side that can be zapped or scrolled through with the encoder? This would display the waveform in the frame to the left and would make visually finding the proper waveform mach easier and faster. Moreover, tapping on the touchscreen in the predefined arbitrary window should take the user directly back to the arbitrary selection table and not to the waveform selection menu. Even though this would be slightly inconsistent vs. the standard waveform functions, it would make life so much easier. If the user wants to access the basic waveform selection, there's always the hard key for that.

I think Siglent should really make better use of the touchscreen and not only duplicate functions that are already easily accessible via physical buttons. A good example is the output impedance ("Load") setting, here the accessibility via the touch screen is considerably improved.

Oh yes, and I would appreciate a WAV import function in EasyWave. If there already is one, I didn't find it, if not, the road via WAV -> CSV -> EasyWave -> SDG is somewhat uncomfortable. Maybe also include a direct import filter for WAV files int he SDG? Maybe integrate an MP3 player ??  ;)

One thing I don't like is the yellow symbol with the exclamation mark indication for every message. For me a symbol like that indicates a warning. If I insert a USB thumb drive and get a message with this sign, it's somewhat out of place. A blue "i" for information would be much more reasonable in that case.

Edit: Just noticed: The function buttons should, if pressed repeatedly, and the associated menu consists of more than one page, toggle between the pages. This would eliminate the need for a "Page" button and permit faster access to the functions.

These are just a few things that may improve usability a lot and they shouldn't be too difficult to implement.

Cheers,
Thomas

Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tautech on September 29, 2018, 11:28:56 am
@TurboTom
I believe Siglent has sent you some beta firmware to address some issues you found. Have you anything to report ?
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: TurboTom on September 29, 2018, 12:44:40 pm
Indeed, I received a beta firmware from Siglent. I agreed with them not to share it since it's experimental and Siglent don't want it to be "floating" through the web. I also had some good correspondence with them regarding my other ideas for improvements of the AWG and got their confirmation that their engineers will look into each of my points and check them for feasibility and will try to integrate them into future firmware versions. Most of these suggestions for improvement address the "eyes-off" operation of the U/I.

The beta firmware basically takes care of the signal pauses when changing parameters of the "conventional" waveforms. Actually, Siglent got that sorted, the problem is solved in independant channel mode only (that's what I was hoping for -- a big  :-+ for this!), a solution for the phase locked mode is apparently way more complex and will have to be addressed in future. I don't know when to expect the next official firmware update, but Siglent confirmed that the changes that solved the pausing problem will be included.

I'm actually very happy with their fast reaction to my "rants"...  ;), and especially this professional attitude convinced me to keep the SDG6022X.

Cheers,
Thomas
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: kerouanton on September 29, 2018, 05:05:32 pm
Thanks Thomas for the feedback, and a huge thanks to Siglent engineers for their really fast support.

I also was hoping the User Interface would be improved on my SDG6000X on the waveform selection. As you described, the list of waveforms should ideally include a small graphical representation. But more importantly, pressing the "waveform" button should display the *last* menu bar with the currently selected waveform, and not reset to first page with "Sin etc...". That would save a few keypresses and frustration.
Even better: ideally, pressing the "Waveform" button after choosing an arbitrary waveform should bring us back to the precise waveform selection page where we were. It would save also a few keypresses...

Bruno
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: TurboTom on October 06, 2018, 10:10:13 am
It seems that with square (pulse??) output and sweep enabled, the SDG6000X automatically changes rise- and fall time from 2ns to 1ns which results in considerable overshoot and ringing, see attached screenshot. Can somewone confirm this on a stock instrument (my machine is currently "improved")?

Thanks,
Thomas
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: MrW0lf on October 06, 2018, 11:43:30 am
It seems that with square (pulse??) output and sweep enabled, the SDG6000X automatically changes rise- and fall time from 2ns to 1ns which results in considerable overshoot and ringing, see attached screenshot.

Prob switches to DDS mode which is ringy by itself. Maybe worth checking if sweep change is smooth or "stepped" at top end. Sort of rings a bell if you look my issue with DDS square and phase shifts.
Will look sometime later if SDG2000X exibits same. It is of great interest because I sort of need SDG6000X myself but better if good people iron it out a little first... :)
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: Performa01 on October 06, 2018, 01:06:49 pm
It seems that with square (pulse??) output and sweep enabled, the SDG6000X automatically changes rise- and fall time from 2ns to 1ns which results in considerable overshoot and ringing, see attached screenshot. Can somewone confirm this on a stock instrument (my machine is currently "improved")?

Thanks,
Thomas

I can confirm this. When sweep mode is engaged, the transition times decrease to 1ns (measured as some 1.3~1.4ns on the SDS2304X) and overshoot changes from virtually nothing to 10% for the rising edge - interestingly, only some 5% for the falling edge.

(https://www.eevblog.com/forum/testgear/siglent-sdg6000-series-awg_s/?action=dlattach;attach=540359;image)
SDG6052X_Square_Sweep

It reverts back to 2ns and virtually no overshoot as soon as the sweep is switched off again.

Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: MrW0lf on October 06, 2018, 05:01:15 pm
Yep, SDG2000X does square sweep with DDS. What annoying you cannot choose DDS for non-sweep mode, which could be useful in some cases. And of course no oversampled square for sweep currently... Sweeps 17.5-22.5MHz. Just square is 20MHz.

(https://www.eevblog.com/forum/testgear/siglent-sdg6000-series-awg_s/?action=dlattach;attach=540668;image)

Edit: For reference. RFE6GEN 35-45MHz...
(https://www.eevblog.com/forum/testgear/siglent-sdg6000-series-awg_s/?action=dlattach;attach=540848;image)

BTW looking manual for SDG2000X DDS is 300MSa/s => ~3.3ns step. SDG6000X is 1.2GSa/s => ~0.8ns step.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: rf-loop on October 06, 2018, 06:55:49 pm
It seems that with square (pulse??) output and sweep enabled, the SDG6000X automatically changes rise- and fall time from 2ns to 1ns which results in considerable overshoot and ringing, see attached screenshot. Can somewone confirm this on a stock instrument (my machine is currently "improved")?

Thanks,
Thomas

What is this Rigol "DS4000 improved" true risetime.
In your image it looks there is around 0.7ns risetime.
Specified risetime for 500MHz model is 0.7ns and typically most of scopes are bit faster than specs limit.
Now if Siglent SDG risetime is 1ns, how this image is possible.
If rigol rt is 0.7 and Siglent 1ns then it need show 1.2ns
If Rigol risetime is (example) 0.5ns and siglent 0.5ns then we can see around 0.7ns (or what ever others what give: SQR(rtR^2+rtS^2) = 0.7
This can not  be Sinc interpolation "Gibbs" because sampling speed is 4GSa/s
So what is this around 500MHz ringing and where it happen and this same ringing frequency can also see before edge (aka preshoot) but quite low amplitude. Inside Siglent SDG alone or where.

What happen if you add 10dB attenuator to scope input bnc (and scope input 50ohm) and same with say example 10cm different cable length. (is it pure 50ohm impedance for these frequencies what are coming to input in this case)


(https://www.eevblog.com/forum/testgear/siglent-sdg6000-series-awg_s/?action=dlattach;attach=540956;image)
@TurboTom image: Looks like 0.7ns risetime

Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: kerouanton on October 07, 2018, 02:00:04 pm
Anyway, here's the first clip, me demonstrating the sync / output jitter and some other strange stuff:

http://www.turbinemuseum.de/files/SDG6000X/SDG6000X_org2.mp4 (http://www.turbinemuseum.de/files/SDG6000X/SDG6000X_org2.mp4)

I tried to reproduce the 1MHz/1.000.001MHz jitter bug (1st video), but didn't succeed. With the same settings  connecting the output trigger of the SDG on my SDS 1104, the output signal seems stable, in all cases. I'm using the latest firmware on both machines.

Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: rf-loop on October 07, 2018, 02:21:05 pm
Anyway, here's the first clip, me demonstrating the sync / output jitter and some other strange stuff:

http://www.turbinemuseum.de/files/SDG6000X/SDG6000X_org2.mp4 (http://www.turbinemuseum.de/files/SDG6000X/SDG6000X_org2.mp4)

I tried to reproduce the 1MHz/1.000.001MHz jitter bug (1st video), but didn't succeed. With the same settings  connecting the output trigger of the SDG on my SDS 1104, the output signal seems stable, in all cases. I'm using the latest firmware on both machines.

But your trigger is from CH1, and then you look CH1 edge. Of course there is not visible jitter.
Set rising edge trigger to half of output trigger signal level (CH3) and then look CH1 edge. ;)
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: kerouanton on October 07, 2018, 02:24:26 pm
Sure! I just noticed it  :palm:
Setting the trigger source to CH3 where my output trigger lands doesn't seem to change the result anyway. the signal is stable. Btw I forgot to mention I send a stable 10MHz reference clock to the SDG (Leobodnar GPSDO). Maybe it helps.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: TurboTom on October 07, 2018, 02:25:00 pm
@rf-loop -

I did some tests with a 20db (10:1 by voltage) 50 ohm attenuator, here's the result. Please be aware that I dialed in the probe factor at the scope to match the attenuator so the amplitude measurements correspond to the input of the attenuator, not the scope. Both the attenuator (20dB SMA -> SMA) and the cable (90cm RG316 BNC -> SMA) I used are DIY but checked and verified for accuracy and impedance matching up to 2GHz, so in the required frequency range, we can consider them to perform accurately.

The first screeshot (No 14) represents the output signal of Leo Bodnar's fast square wave generator, routed directly through the attenuator to the scope input (no cables whatsoever. The pulser is characterized by Leo to provide rise- and fall times faster than 50ps. You may compare this measurement with the one here (https://www.eevblog.com/forum/testgear/rigol-ds4024-opinions/?action=dlattach;attach=537108) for the same signal without attenuator.

Next screenshot (No 15) corresponds to the square wave output of the SDG6000X without sweep, measured with the cable on the output and the attenuator on the scope input. Clean ("as a whistle"  ;)) 2ns slopes and almost no overshoot and no ringing present.

No. 17 shows the sweep, clearly observing the considerable ringing which is way more pronounced than the overshoot of the scope with the pulser (No 14). Slope is much faster now, if "averaging out" the ringing, it's in the ballpark of 1ns. I also took a reference trace with the cable / attenuator arrangement reversed, i.e. the attenuator is at the SDG6000X's ooutput. No difference was observable whatsoever.

To eliminate the faint possibility that the ringing is produced by the cable, I used a much shorter (length 30cm) RG316 cable in screenshot No 18, this time with the trace of No 17 as reference. The signal appears to have just a tiny bit higher amplitude which can be expected due to the much shorter length.

So I guess this pretty much proves that the ringing is actually present at the SDG6000X's output in square waveform sweep mode and that it's not a result of the scope's input circuitry or signal processing approach.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: kerouanton on October 07, 2018, 02:50:36 pm
Okay I'm just a beginner in measurement...need to train more!
The issue is visible, yes.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: MrW0lf on October 07, 2018, 04:18:11 pm
So I guess this pretty much proves that the ringing is actually present at the SDG6000X's output in square waveform sweep mode and that it's not a result of the scope's input circuitry or signal processing approach.

If take 50% square from Arb wfm built-ins and set generation to DDS (from TrueArb)? Does it look the same?
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: rf-loop on October 07, 2018, 04:28:30 pm
@rf-loop -

I did some tests with a 20db (10:1 by voltage) 50 ohm attenuator, here's the result. Please be aware that I dialed in the probe factor at the scope to match the attenuator so the amplitude measurements correspond to the input of the attenuator, not the scope. Both the attenuator (20dB SMA -> SMA) and the cable (90cm RG316 BNC -> SMA) I used are DIY but checked and verified for accuracy and impedance matching up to 2GHz, so in the required frequency range, we can consider them to perform accurately.

The first screeshot (No 14) represents the output signal of Leo Bodnar's fast square wave generator, routed directly through the attenuator to the scope input (no cables whatsoever. The pulser is characterized by Leo to provide rise- and fall times faster than 50ps. You may compare this measurement with the one here (https://www.eevblog.com/forum/testgear/rigol-ds4024-opinions/?action=dlattach;attach=537108) for the same signal without attenuator.

Next screenshot (No 15) corresponds to the square wave output of the SDG6000X without sweep, measured with the cable on the output and the attenuator on the scope input. Clean ("as a whistle"  ;)) 2ns slopes and almost no overshoot and no ringing present.

No. 17 shows the sweep, clearly observing the considerable ringing which is way more pronounced than the overshoot of the scope with the pulser (No 14). Slope is much faster now, if "averaging out" the ringing, it's in the ballpark of 1ns. I also took a reference trace with the cable / attenuator arrangement reversed, i.e. the attenuator is at the SDG6000X's ooutput. No difference was observable whatsoever.

To eliminate the faint possibility that the ringing is produced by the cable, I used a much shorter (length 30cm) RG316 cable in screenshot No 18, this time with the trace of No 17 as reference. The signal appears to have just a tiny bit higher amplitude which can be expected due to the much shorter length.

So I guess this pretty much proves that the ringing is actually present at the SDG6000X's output in square waveform sweep mode and that it's not a result of the scope's input circuitry or signal processing approach.

Thanks for the deeper tests you have done.
Now, new tests better exclude some possible external factors.
14. show some overshoot but in this context not so bad and only one overshoot without multiple cycle ringing.

Based to your tests here, SDG risetime  is in the class of 0.3ns (sweep mode, pulses)
(LeoBodnar's  average rt  vs SDG /sweep mode pulse rt average.)
But as in image 15, when rt is "normal" it looks better than just good.

Imho, 0.3ns risetime feels bit too fast for its output circuits. And together with this observed ringing, there can perhaps speculate, is it possible, there is bug in output filtering control.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: TurboTom on October 07, 2018, 06:05:43 pm
Things get more an more weird and I get the impression that we're still at the very beginning of understanding and characterizing this instrument (and I'm afraid, Siglent may be as well...  ;)). As suggested by @rf-loop, I checked the overshoot / ringing situation with some ARB waveforms (among them Radar and Square 50%), and it appears that there's still some "controlled slope" managed in this mode, yet advanced to 1ns which results in some pretty ringing. Funny enough, if I additinoally enable sweep, I get the "uncontrolled slope" with rise times basically in the ballpark of my scope's frontend (only slightly slower). Please see the three screenshots. Configuration is the same as in my previous post. The REF trace in No 21 is the unswept square wave from No 20.

I also found that the Beta firmware provided by Siglent to me, fails with reproducing some of the arbitrary waveforms (Radar for instance doesn't work properly) and I also found some other problems so currently I'm back on the stock firmware. I won't got into detail here and discuss this with Siglent directly. It seems there's still some work do be done to sort all the problems completely. Since ringing / overshoot isn't specified for rise times faster than 2ns, these observations cannot be interpreted as bugs. But the customers may ask for a slope limiting function so the overshoot could actually be kept within specs in all operating modes.

Don't get me wrong, I'm not bashing Siglent, in contrary I'm quite pleased of their open communication and the approach to solve the issues in collaboration with the users. I think this is the way to improve the product and finally get a better result than the engineers alone could have ever reached in the same time. Let's see how the journey will continue...
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: rf-loop on October 07, 2018, 10:01:39 pm
Things get more an more weird and I get the impression that we're still at the very beginning of understanding and characterizing this instrument (and I'm afraid, Siglent may be as well...  ;)). As suggested by @rf-loop, I checked the overshoot / ringing situation with some ARB waveforms (among them Radar and Square 50%), and it appears that there's still some "controlled slope" managed in this mode, yet advanced to 1ns which results in some pretty ringing. Funny enough, if I additinoally enable sweep, I get the "uncontrolled slope" with rise times basically in the ballpark of my scope's frontend (only slightly slower). Please see the three screenshots. Configuration is the same as in my previous post. The REF trace in No 21 is the unswept square wave from No 20.

I also found that the Beta firmware provided by Siglent to me, fails with reproducing some of the arbitrary waveforms (Radar for instance doesn't work properly) and I also found some other problems so currently I'm back on the stock firmware. I won't got into detail here and discuss this with Siglent directly. It seems there's still some work do be done to sort all the problems completely. Since ringing / overshoot isn't specified for rise times faster than 2ns, these observations cannot be interpreted as bugs. But the customers may ask for a slope limiting function so the overshoot could actually be kept within specs in all operating modes.

Don't get me wrong, I'm not bashing Siglent, in contrary I'm quite pleased of their open communication and the approach to solve the issues in collaboration with the users. I think this is the way to improve the product and finally get a better result than the engineers alone could have ever reached in the same time. Let's see how the journey will continue...

How you can say
Quote
Funny enough, if I additinoally enable sweep, I get the "uncontrolled slope" with rise times basically in the ballpark of my scope's frontend (only slightly slower).

Due to previous tests including Leo Bodnar pulser test result with your scope, I think Siglent risetime is here in image must be 21 much faster than your scope risetime.
(image 14 LeoBodnar pulser your scope measure risetime average 638ps. Lets think this is your scope risetime. Now image 21 your scope measure 721ps. It mean that Siglent risetime is 336ps. [ (SQR(638ps^2 + 336ps^2) = 721ps ] )

But how ever, it is intersting. And there is now some "dejavu". I believe I have seen this happen somewhere previously somehow but I do not remember where. I mean some Siglent older equipment where I have seen some increase in risetime when change some mode (perhaps just from continuous mode to sweep) but this is now only some weak memory image in my old head also my memory can be wrong. 

So or so.. 
but how it give 0.3ns risetime out...   
Is it same result if you do tests with SDG6022X "out from box" condition (official 200MHz version)?

Quote
I'm not bashing Siglent,...

Do not worry,  careful well done tests and real raw data is not at all like bashing.
Also if there is problem, honest truth wins trumpth (aka alternative truth). Even if truth is worse than alternative truth.

I do not even think if this is real problem or not or borderline but it is technically interesting this phenomena exist and least it is good to know. My opinion is that this is better to fix (hw or sw) in normal order after higher priority things. Siglent also needs to notice this.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: TurboTom on October 07, 2018, 10:43:04 pm
Oh, well, my rise time "statement" refered to the figures indicated on the screen (i.e. the measurement). Of course, I'm aware that the real rise time of the AWG has to be faster than my scope to produce these figures and that the numbers add up geometrically. I guess I didn't express it correctly - that's the problem of two individuals, both communicating in a foreign language  ;).

Cheers,
Thomas
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: rf-loop on October 09, 2018, 07:25:23 am
Previously I told I have some kind of "dejavu" about something like this what I have seen somewhere....
I have checked it and I think I find this what I mean, not exactly same but..

SDG5000

If normal Square wave, (example 10MHz Sqr) rise time is  ~5.7ns

If just turn Sweep on (without any sweep, example start 10MHz and stop 10MHz)  risetime is 1ns more fast,  ~4.7ns and it also add some small detectable  "ringing" after edge but not at all this ringing level amount what we can see in @TurboTom images.
So, with different numbers but roughly same effect.
It looks like sweep mode change filtering.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: MrW0lf on October 09, 2018, 08:30:51 am
It looks like sweep mode change filtering.

I suspect it changes also from oversampling to DDS and you will get decreased frequency resolution also. Width SDG2000X 1.2GSa/s => 300MSa/s, SDG6000X 2.4GSa/s => 1.2GSa/s. This might also explain why on 2000 between channel oversampled (!) square vs sine phase relations are "complicated"*. Some "filtering" gets wfm shape straight but programmers have forgotten to hack phases right also. I'd suggest to check for sine vs square phase issues on 6000. Is it non-sweep square phase messed up in stepped manner depending on phase value (NB! error is also "oversmapled"), and is square sweep discretely stepped by 0.8ns.

Edit: * turns out not complicated at all (https://www.eevblog.com/forum/testgear/the-siglent-sdg2042x-thread/msg1880738/#msg1880738) :P
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: Performa01 on October 09, 2018, 09:50:55 am
Last weekend I’ve had a look at the “undulation” effect at 1ns transition times and sure enough I was able to reproduce it on the SDG6052X, as demonstrated by the following screenshots. Yet it’ll turn out that’s not the whole story…

First the minimum pulse width of 3.4ns with 1ns transition times viewed on a fast scope at a timebase of 5ns/div. The reference traces are just there to demonstrate what this pulse looks like with 200MHz (blue) and 20MHz (orange) 1st order bandwidth limit. This further demonstrates that we really need a fast scope in order to properly characterize a beast like the SDG6052X:

(https://www.eevblog.com/forum/testgear/siglent-sdg6000-series-awg_s/?action=dlattach;attach=543125;image)
Pulse_BWL_SDG6052X_1.5V_3.4ns_1ns


The same scenario at a faster timebase of 1ns/div just for closer inspection. We can see that the rise- and fall times of the SDG6052X are still pretty accurate despite the continuously changing waveform, aka “undulation”:

(https://www.eevblog.com/forum/testgear/siglent-sdg6000-series-awg_s/?action=dlattach;attach=543131;image)
Pulse_BWL_SDG6052X_1.5V_3.4ns_1ns_Z


As we already know, this effect nearly ceases when reverting to the default 2ns transition times:

(https://www.eevblog.com/forum/testgear/siglent-sdg6000-series-awg_s/?action=dlattach;attach=543137;image)
Pulse_BWL_SDG6052X_1.5V_3.4ns_2ns


The same “undulation” effect can be observed with wider pulses, like 10ns in the following example:

(https://www.eevblog.com/forum/testgear/siglent-sdg6000-series-awg_s/?action=dlattach;attach=543143;image)
Pulse_BWL_SDG6052X_1.5V_10ns_1ns


And again, the pulse gets pretty clean with 2ns transition times:

(https://www.eevblog.com/forum/testgear/siglent-sdg6000-series-awg_s/?action=dlattach;attach=543149;image)
Pulse_BWL_SDG6052X_1.5V_10ns_2ns


So far so good (or not), this has been nothing new. But when I needed a narrow pulse with fast transitions again the next day, things looked completely different. As can be seen, all of a sudden the shape of the pulse is now absolutely stable and as expected, average transition times got even faster with less standard deviation:

(https://www.eevblog.com/forum/testgear/siglent-sdg6000-series-awg_s/?action=dlattach;attach=543155;image)
Pulse_SDG6052X_1.5V_A10dB_3.3ns_1ns


The same is true for the wider 10ns pulse:

(https://www.eevblog.com/forum/testgear/siglent-sdg6000-series-awg_s/?action=dlattach;attach=543161;image)
Pulse_SDG6052X_1.5V_A10dB_10ns_1ns


Finally a cursor measurement in order to confirm the automatic rise time measurement of 970ps:

(https://www.eevblog.com/forum/testgear/siglent-sdg6000-series-awg_s/?action=dlattach;attach=543167;image)
Pulse_SDG6052X_RT_1.5V_A10dB_10ns_1ns


So it looks like the SDG6000X behaves differently (depending on its mood) every other day and I suspect some incomplete initialization, which Siglent should be able to fix eventually. At least my test indicates that the issue should be easily fixable.


Btw, I also looked at the Sync to Output jitter and was unable to reproduce it at 1MHz. Yet the ~3.3ns jitter is certainly there at most other frequencies.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: MrW0lf on October 09, 2018, 10:51:10 am
a fast scope

:popcorn:
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: Performa01 on October 09, 2018, 11:44:49 am
a fast scope

:popcorn:

Indeed :)

After all, there are signals much faster than what an SDG6052X can do (and these could use an even faster scope), so your scope can never be too fast ;)

(https://www.eevblog.com/forum/testgear/siglent-sdg6000-series-awg_s/?action=dlattach;attach=543242;image)
Demo_Square_160MHz_10mV


Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: JohnG on October 09, 2018, 01:21:48 pm
so your scope can never be too fast ;)

Agreed :-+
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: egonotto on October 09, 2018, 08:53:38 pm
Hello,

is this a new Siglent scope?

Best regards
egonotto
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tautech on October 09, 2018, 08:58:38 pm
Hello,

is this a new Siglent scope?

Best regards
egonotto
https://www.eevblog.com/forum/testgear/at-last-siglent_s-sds5054x-touchscreen/ (https://www.eevblog.com/forum/testgear/at-last-siglent_s-sds5054x-touchscreen/)
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tv84 on October 09, 2018, 09:01:50 pm
I thought it was a homebrew model...
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: 2N3055 on October 09, 2018, 09:06:29 pm
It seems like a 1GHz model....
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: rf-loop on October 10, 2018, 07:59:18 am
a fast scope

:popcorn:

Indeed :)

After all, there are signals much faster than what an SDG6052X can do (and these could use an even faster scope), so your scope can never be too fast ;)

(https://www.eevblog.com/forum/testgear/siglent-sdg6000-series-awg_s/?action=dlattach;attach=543242;image)
Demo_Square_160MHz_10mV

Risetime  and layout looks like scope is Ding Yang SDS5104X  (1GHz) or better.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: KaneTW on October 10, 2018, 02:25:18 pm
The UI reminds me a bit of my R&S RTB2004.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: TurboTom on November 05, 2018, 01:37:09 pm
Meanwhile more than a month has passed since Siglent's first reaction to my "rants" and the bug reports (and the beta firmware that introduced new bugs so I'm back on the stock version), and since then, it's been rather silent except a short PM round about three weeks ago that their engineers are working on the waveform quality issue (probably the overshoot/undulation problem vs. the option to have a 2ns rise time in all operational modes which should put the instrument overshoot-wise within its specs). Actually, I already regret not to have drawn the option to return the instrument after I thorougly tested it. My current situation is like this: When I'm doing some quick tests (calibration of my turbine engine control units or the like), I use a different generator of which I know that the output signal is reliable.

Just now that I wanted to give the SDG6000X another chance to prove itself useful, I found another bug in the standard firmware that I quickly report here: Phase setting independent, select any built-in arbitrary waveform -- I tested with several --, for simplicity reasons, just use "StairUp". I checked at 2kHz but I think the frequency is not really important. Then toggle the "ArbMode" from DDS to TrueArb (I selected 65.536MSa/s to have the same frequency) and back to DDS -- see how the slopes look funny. Toggling On/Off any of the Mod / Sweep / Burst functions will restore the waveform. In phase locked mode, this doesn't happen.

It's really a shame that instruments of apparetly decent hardware design get crippled by unfinished software. Of course I'm aware that probably 80 to 90% of the complexity and work of an instrument like this lies in software design. Anyway, regardless of the complexity situation, I think a customer can expect to receive an instrument (that's clearly designed towards at least the semi-professional user) that has been thoroughly tested at the manufacturer's QC / engineering department. And then, bugs like these shouldn't have slipped through.

Whatsoever, I really hope for a substantial bug fix / firmware update in due time.

Cheers,
Thomas
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: emax on November 08, 2018, 12:44:26 pm
It took me a lot of picoseconds to (basically) understand all of your screenshots and explanations.

You guys are really awesome!  :-+
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: 2N3055 on January 29, 2019, 11:38:44 am
Any news on new firmware...??
I bought one in meantime for a project I'm working on..

I also confirmed all bugs here mentioned, and found some new ones, connected to output filtering issue.
I found that sometimes changing frequency on CH2 upsets filtering on CH1 so pulses start ringing. Disable and enable CH1 makes it OK again.
Also, once I had problem that I loaded two different AW into two channels, did what I was doing, and when switching back to pulses it also started ringing.
I had to reboot this time to make it ok.

Apart from that (I hope it will be solved soon), powerful little beast.
Amplitude flatness seems excellent, nicely implemented PRBS with preset logic levels and differential driving..
Channel mixing is also very nice feature.

I also have a feature suggestion (request ?): would it be possible to add a waveform sequence mode like Keysight 33500B/33600A (Waveform sequencing) or Rigol DG800/900 (Sequence function)?
That would be enormous usability and capability enhancement.

Regards,

Sinisa
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: janekivi on January 29, 2019, 04:38:54 pm
Some of their generators got today new firmware... but this doesn't mean anything.
May be adds a little bit hope.
SDG1000 Firmware UpdateCurrent Version: V1.01.01.39R7 | Published:2019-01-29
SDG1000X Firmware UpdateCurrent Version: V1.01.01.30R1B2 | Published:2019-01-28
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: jjoonathan on February 12, 2019, 04:20:50 am
I'm having trouble with the memdump technique. I can get a root console and have had good luck with the "move a file" technique, but that only unlocks bandwidth, not IQ. Here's what I have tried:

* Grabbing /dev/mem and running FindKeys on it. It returns many hits. I haven't been able to get TryKeys to work though. These tools look slightly oscilloscope specific?

* Writing a quick program to grab and scan awg.app's memory directly (ptrace, /proc/pid/{mem,maps}). I look for 16-char capital alphanumerics with at most 6 repeats of any single character. I can see two copies of my 200MHz Bandwidth key if it's installed, but if I remove the key from the xml file without touching the serial number, I can't find it in memory anymore. I don't see any other keys. One candidate, but it doesn't work and it doesn't have similar surroundings to the known real key, so I'm pretty sure it's a false positive.

I suspect I am missing a simple trick. Do you have to do something to provoke the other keys to appear in memory?

In any case, I have attached the tool I made. Here's the output. Dots are key candidates. Only one looks sane and it doesn't work. The known good key does not appear unless it is installed.
Code: [Select]
/usr/bin/siglent/usr/mass_storage/U-disk0 # ps -e | grep awg
  667 root       0:13 /usr/bin/siglent/awg.app
  839 root       0:00 grep awg
/usr/bin/siglent/usr/mass_storage/U-disk0 # ./memdump 667 mem2.bin > mem2.txt
SKIP 00008000-005d3000 r-xp 00000000 00:0f 612        /usr/bin/siglent/awg.app
SCAN 005da000-0094c000 rw-p 005ca000 00:0f 612        /usr/bin/siglent/awg.app
SCAN 0094c000-01b21000 rw-p 00000000 00:00 0          [heap]
...
SCAN 28600000-28680000 rw-p 00000000 00:00 0
SCAN 28680000-28700000 rw-s 00000000 00:06 1108       /dev/fb0
SKIP 28700000-28701000 ---p 00000000 00:00 0
SCAN 28701000-28f00000 rw-p 00000000 00:00 0          [stack:746]
SCAN 28f00000-28f80000 rw-s 0ad80000 00:06 15         /dev/mem
SCAN 28f80000-29000000 rw-s 0ad00000 00:06 15         /dev/mem
SCAN 29000000-2b800000 rw-s 0d800000 00:06 15         /dev/mem
SCAN 2b800000-2b880000 rw-s 0ac80000 00:06 15         /dev/mem
SCAN 2b880000-2b900000 rw-s 0ac00000 00:06 15         /dev/mem
SCAN 2b900000-2e100000 rw-s 0b000000 00:06 15         /dev/mem
SKIP 2e100000-2e101000 ---p 00000000 00:00 0
SCAN 2e101000-2e900000 rw-p 00000000 00:00 0          [stack:728]
SKIP 2e900000-2e901000 ---p 00000000 00:00 0
SCAN 2e901000-2f100000 rw-p 00000000 00:00 0          [stack:703]
SKIP 2f100000-2f101000 ---p 00000000 00:00 0
SCAN 2f101000-2f900000 rw-p 00000000 00:00 0          [stack:702]
SKIP 2f900000-2f901000 ---p 00000000 00:00 0
SCAN 2f901000-30100000 rw-p 00000000 00:00 0          [stack:701]
SKIP 30100000-30101000 ---p 00000000 00:00 0
SCAN 30101000-30900000 rw-p 00000000 00:00 0          [stack:700]
SKIP 30900000-30901000 ---p 00000000 00:00 0
SCAN 30901000-31100000 rw-p 00000000 00:00 0          [stack:699]
SKIP 31100000-31101000 ---p 00000000 00:00 0
SCAN 31101000-31900000 rw-p 00000000 00:00 0          [stack:692]
SKIP 31900000-31901000 ---p 00000000 00:00 0
SCAN 31901000-32100000 rw-p 00000000 00:00 0          [stack:691]
SKIP 32100000-32101000 ---p 00000000 00:00 0
SCAN 32101000-32900000 rw-p 00000000 00:00 0          [stack:689]
SKIP 32900000-32901000 ---p 00000000 00:00 0
SCAN 32901000-33100000 rw-p 00000000 00:00 0          [stack:688]
SKIP 33100000-33101000 ---p 00000000 00:00 0
SCAN 33101000-33900000 rw-p 00000000 00:00 0          [stack:687]
SKIP 33900000-33901000 ---p 00000000 00:00 0
SCAN 33901000-34100000 rw-p 00000000 00:00 0          [stack:686]
SKIP 34100000-34101000 ---p 00000000 00:00 0
SCAN 34101000-34900000 rw-p 00000000 00:00 0
SCAN 34900000-34955000 rw-p 00000000 00:00 0
SKIP 34955000-34a00000 ---p 00000000 00:00 0
SCAN 34a40000-34a50000 rw-s 0af00000 00:06 15         /dev/mem
SCAN 34a50000-34a60000 rw-s 0ae00000 00:06 15         /dev/mem
SCAN 34a60000-34a70000 rw-s 40400000 00:06 15         /dev/mem
SCAN 34a70000-34a80000 rw-s 40410000 00:06 15         /dev/mem
SCAN 34a80000-34a90000 rw-s 40600000 00:06 15         /dev/mem
SCAN 34a90000-34aa0000 rw-s 40400000 00:06 15         /dev/mem
SCAN 34aa0000-34ab0000 rw-s 40410000 00:06 15         /dev/mem
SCAN 34ab0000-34ac0000 rw-s 40600000 00:06 15         /dev/mem
SCAN 34ac0000-34ad0000 rw-s 40400000 00:06 15         /dev/mem
SCAN 34ad0000-34ae0000 rw-s 40410000 00:06 15         /dev/mem
SCAN 34ae0000-34af0000 rw-s 40600000 00:06 15         /dev/mem
SKIP 34af0000-34af1000 ---p 00000000 00:00 0
SCAN 34af1000-352f0000 rw-p 00000000 00:00 0          [stack:684]
SKIP 352f0000-352f1000 ---p 00000000 00:00 0
SCAN 352f1000-35af0000 rw-p 00000000 00:00 0          [stack:683]
SKIP 35af0000-35af1000 ---p 00000000 00:00 0
SCAN 35af1000-362f0000 rw-p 00000000 00:00 0          [stack:679]
SKIP 362f0000-362f1000 ---p 00000000 00:00 0
SCAN 362f1000-36af0000 rw-p 00000000 00:00 0          [stack:678]
SKIP 36af0000-36af4000 r-xp 00000000 1f:05 1489472    /lib/libdl-2.11.1.so
SKIP 36af4000-36afb000 ---p 00004000 1f:05 1489472    /lib/libdl-2.11.1.so
SKIP 36afb000-36afc000 r--p 00003000 1f:05 1489472    /lib/libdl-2.11.1.so
SKIP 36afc000-36afd000 rw-p 00004000 1f:05 1489472    /lib/libdl-2.11.1.so
SKIP 36afd000-36c39000 r-xp 00000000 1f:05 739944     /lib/libc-2.13.so
SKIP 36c39000-36c41000 ---p 0013c000 1f:05 739944     /lib/libc-2.13.so
SKIP 36c41000-36c43000 r--p 0013c000 1f:05 739944     /lib/libc-2.13.so
SKIP 36c43000-36c44000 rw-p 0013e000 1f:05 739944     /lib/libc-2.13.so
SCAN 36c44000-36c47000 rw-p 00000000 00:00 0
SKIP 36c47000-36c66000 r-xp 00000000 1f:05 1498276    /lib/libgcc_s.so.1
SKIP 36c66000-36c6d000 ---p 0001f000 1f:05 1498276    /lib/libgcc_s.so.1
SKIP 36c6d000-36c6e000 rw-p 0001e000 1f:05 1498276    /lib/libgcc_s.so.1
SKIP 36c6e000-36cdc000 r-xp 00000000 1f:05 1547208    /lib/libm-2.11.1.so
SKIP 36cdc000-36ce3000 ---p 0006e000 1f:05 1547208    /lib/libm-2.11.1.so
SKIP 36ce3000-36ce4000 r--p 0006d000 1f:05 1547208    /lib/libm-2.11.1.so
SKIP 36ce4000-36ce5000 rw-p 0006e000 1f:05 1547208    /lib/libm-2.11.1.so
SKIP 36ce5000-36da9000 r-xp 00000000 1f:05 9371652    /usr/lib/libstdc++.so.6
SKIP 36da9000-36db0000 ---p 000c4000 1f:05 9371652    /usr/lib/libstdc++.so.6
SKIP 36db0000-36db4000 r--p 000c3000 1f:05 9371652    /usr/lib/libstdc++.so.6
SKIP 36db4000-36db6000 rw-p 000c7000 1f:05 9371652    /usr/lib/libstdc++.so.6
SCAN 36db6000-36dbc000 rw-p 00000000 00:00 0
...
SKIP 36dbc000-36edc000 r-xp 00000000 1f:05 1981724    /lib/libxml2.so.2.7.8
SKIP 36edc000-36ee3000 ---p 00120000 1f:05 1981724    /lib/libxml2.so.2.7.8
SKIP 36ee3000-36ee9000 rw-p 0011f000 1f:05 1981724    /lib/libxml2.so.2.7.8
SKIP 36ee9000-36f04000 r-xp 00000000 1f:05 7050472    /usr/lib/libglog.so.0
SKIP 36f04000-36f0b000 ---p 0001b000 1f:05 7050472    /usr/lib/libglog.so.0
SKIP 36f0b000-36f0c000 rw-p 0001a000 1f:05 7050472    /usr/lib/libglog.so.0
SCAN 36f0c000-36f1c000 rw-p 00000000 00:00 0
SKIP 36f1c000-36f36000 r-xp 00000000 1f:05 3682060    /lib/libz.so.1.2.8
SKIP 36f36000-36f3e000 ---p 0001a000 1f:05 3682060    /lib/libz.so.1.2.8
SKIP 36f3e000-36f3f000 rw-p 0001a000 1f:05 3682060    /lib/libz.so.1.2.8
SKIP 36f3f000-36f46000 r-xp 00000000 1f:05 1967524    /lib/librt-2.11.1.so
SKIP 36f46000-36f4d000 ---p 00007000 1f:05 1967524    /lib/librt-2.11.1.so
SKIP 36f4d000-36f4e000 r--p 00006000 1f:05 1967524    /lib/librt-2.11.1.so
SKIP 36f4e000-36f4f000 rw-p 00007000 1f:05 1967524    /lib/librt-2.11.1.so
SKIP 36f4f000-36f64000 r-xp 00000000 1f:05 1925640    /lib/libpthread-2.13.so
SKIP 36f64000-36f6b000 ---p 00015000 1f:05 1925640    /lib/libpthread-2.13.so
SKIP 36f6b000-36f6c000 r--p 00014000 1f:05 1925640    /lib/libpthread-2.13.so
SKIP 36f6c000-36f6d000 rw-p 00015000 1f:05 1925640    /lib/libpthread-2.13.so
SCAN 36f6d000-36f6f000 rw-p 00000000 00:00 0
SKIP 36f6f000-36f8f000 r-xp 00000000 1f:05 655204     /lib/ld-2.13.so
SCAN 36f90000-36f91000 rw-s f8001000 00:06 15         /dev/mem
SCAN 36f91000-36f96000 rw-p 00000000 00:00 0
SKIP 36f96000-36f97000 r--p 0001f000 1f:05 655204     /lib/ld-2.13.so
SKIP 36f97000-36f98000 rw-p 00020000 1f:05 655204     /lib/ld-2.13.so
SCAN 3e9fe000-3ea1f000 rw-p 00000000 00:00 0          [stack]
SKIP 3eff7000-3eff8000 r-xp 00000000 00:00 0          [sigpage]
SKIP ffff0000-ffff1000 r-xp 00000000 00:00 0          [vectors]

Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: gorillamotors on February 26, 2019, 09:37:43 am
I think that actually helps a lot... thank you tv84! :)
I got the 6022X to 500MHz but how do I upgrade the IQ license?
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: 2N3055 on March 22, 2019, 12:32:58 pm
2 months passed...
Is there ANY news on new firmware for SDG6000X ???

Anybody ?

Thanks.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: TurboTom on March 22, 2019, 07:33:52 pm
Actually more than five (!) month since my last correspondence with Siglent regarding the bugs and possible improvements. Either they are very busy with other equipment and the SDG6000X series is running under low priority or the problems are possibly more severe than anticipated and maybe require a hardware tweak (anti-aliasing-filter?) to get solved properly.

I hope the problems get finally taken care of. Shortly!  :'(
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: 2N3055 on March 22, 2019, 09:34:51 pm
I think they are working, SDG1000x just got upgrade, they gave it Truearb tech and preview of ARB waveforms when selecting...

It seems they are dedicated to do it right, it's just takes a lot of time..
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tautech on May 08, 2019, 03:39:37 am
New firmware for SDG6000X models.

Version 6.01.01.33R2
25.5 MB
https://www.siglentamerica.com/download/8841/ (https://www.siglentamerica.com/download/8841/)


Changelog
1. Removed the warning message when parameter is set to a value beyond the limit
2. Supported to copy/paste/delete folder in Store/Recall file manager
3. Optimized initialization time when the waveform is switched between IQ and other waveforms
4. Supported phase compensation in IQ mode
5. Fixed several bugs:
a) [2018/09/14-924144, 2018/09/14-937446] Signals get interrupted upon timing-related change of the settings in Independent mode
b) Anomaly on square/pulse waveform with some settings
c) [2018/11/06-92208] Anomaly on arb waveform when toggle the "ArbMode" from DDS to TrueArb and back to DDS in Independent mode
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: 2N3055 on May 08, 2019, 06:51:21 am
I will test thoroughly later when I have time..

Update went  without a problem.
On a first view, going into I/Q and out of it to other mode is instantaneous as opposed to 10s of seconds .  :-+
Also they didn't say it in release notes, but they GREATLY improved U/I for choosing built in waveforms.  :-+ :-+

After more testing I will report back.

So far promising..

Thanks to Tautech for heads up...
Regards,
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: janekivi on May 08, 2019, 03:20:44 pm

Changelog
1. Removed the warning message when parameter is set to a value beyond the limit


They have eye on us or can they see by himself this was good idea.
This is lux model, for SDG2000X I must have my own solution....?

SDG2000X_eevblog_edit_23R7.zip - with reduced ".. limit..." message box delay.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tv84 on May 08, 2019, 08:40:36 pm
New upgrades in this new .ADS:

upgrade_uimage "BOOT.bin" "mtd0"
upgrade_uimage "uImage" "mtd1"
upgrade_uimage "devicetree.dtb" "mtd2"
upgrade_uimage "rootfs.cramfs" "mtd11"
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tv84 on May 08, 2019, 08:42:30 pm
They have eye on us or can they see by himself this was good idea.
This is lux model, for SDG2000X I must have my own solution....?

SDG2000X_eevblog_edit_23R7.zip - with reduced ".. limit..." message box delay.

In the next one, the password already comes as "eevblog"...  ;D
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: BillB on May 08, 2019, 10:14:52 pm
They have eye on us or can they see by himself this was good idea.
This is lux model, for SDG2000X I must have my own solution....?

SDG2000X_eevblog_edit_23R7.zip - with reduced ".. limit..." message box delay.

In the next one, the password already comes as "eevblog"...  ;D

That would save everyone a little time, wouldn't it.  :-DD
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: jjoonathan on May 08, 2019, 11:45:43 pm
> 1. Removed the warning message when parameter is set to a value beyond the limit

This alone would make the update worth it!
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: 2N3055 on May 09, 2019, 06:51:09 am
I did a bit of testing last night, didn't have time to do more than quick run through..

As far as I could see, error that filtering (edge control) on one channel would go crazy when you twiddle frequency on other channel seems to be fixed. Or at least seems so from limited testing I did.

Will test more later.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: janekivi on May 09, 2019, 04:47:28 pm
New upgrades in this new .ADS:

upgrade_uimage "BOOT.bin" "mtd0"
upgrade_uimage "uImage" "mtd1"
upgrade_uimage "devicetree.dtb" "mtd2"
upgrade_uimage "rootfs.cramfs" "mtd11"

What you like to say there... most of the files are the same.
BOOT.bin - exactly the same
devicetree.dtb - exactly the same
uImage - is updated
update.sh - has 2 changed rows
awg.app - is much bigger now
rootfs.cramfs - has new file dates inside I think, files are the same
other directories have all the old files with 12 February 2019 date
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: TurboTom on May 10, 2019, 12:02:53 am
It seems Siglent managed to correct some of the major shortcomings of the SDG6000X in the new firmware which are the menu system to access the built-in arbitraries (nice solution btw, yet I would have prefered to get a direct access to the arbitrary waveform selection screen instead of the general waveforms selection menu -- there's a hard button for that already -- when I'm in built-in arbitrary mode and tap the picture of the arbitrary curve on the touchscreen). Maybe that's a possible improvement for the next update...

In phase-independant mode, I really wasn't able to notice any glitches when changing waveform parameters (like frequency, pulse width or rise/fall times). Seems like that problem is solved, at least to tell from my superficial testing tonight.

To eliminate the end-of-range warning with the accompanying delay is also a big improvement.

Yet, I also still found a lot to desire: When changing several parameters in sequence, why doesn't the instrument remember the digit of a parameter that had been modified and returns the cursor to the same digit if the user returns to the parameter after adjusting something different in between. This would improve usability considerably.

Moreover, to improve eyes-off experience (I know, I must seem like an addict to that...  ;)), it would be great to be able to set limits to the parameters (like it's possible to set a limit for the output amplitude). Let's say, I want to generate an old-fashioned PPM radio control signal, set the frequency of a pulse to 50Hz and would like to generate a pulse width between 1 and 2ms. If I could set limits for that, I could adjust the pulse width with the encoder without having to look at the screen while I'm always certain to stay within the valid interval. Come on Siglent, this shouldn't be too difficult to implement.

Signal-quality wise, not too much has happened. To keep the "undulation" and signal overshoot low, be sure to select a minimum rise time of 2ns or higher (where applicable).

I still found a real bug that results in a completely messed up signal. You can replicate it with the following sequence:

- Phase mode independant
- output a 500MHz (or thereabout) sine signal on a channel of choice.
- change the frequency of that channel to 10MHz by entering the new frequency via the keypad (didn't try using the encoder)
- change the waveform to square and observe what you get on an oscilloscope

You can get back the undistorted square wave by toggling burst or sweep on and off.
It seems like the fpga doesn't get initialized properly during the frequency change sequence, or maybe some garbage stays in the waveform memory that should be deleted / overwritten. See the attached screenshots, the first with the distorted "square wave"  ::), the second after toggling "burst".

Seems like we can still expect a few firmware updates...I hope.

Anyway, thanks to Siglent for the fixes so far!

Cheers!
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: TurboTom on May 13, 2019, 02:27:12 pm
New peculiar findings (bugs) with the SDG6X:

Even in independant phase mode, there may still be some glitches when outputting pulses under certain circumstances -- Select waveform pulse, frequency 150MHz and pulse width 3.3ns (I think this is configured automatically like specified when the mentioned frequency is dialed in). Rise/fall times 1ns. Then, select a lower frequency (100kHz for example) and tweak the frequency via the encoder. You can now observe the glitches shown in the first screenshot while adjusting the frequency upwards. When lowering the frequency, the signal doesn't glitch. If the pulse width is altered, the glitch disappears.

Another, very nice finding is how the SDG6X will output a 300MHz sine wave of considerable amplitude (more than supposed to in "real" sine mode at that frequency) in rectangular mode at 0Hz  :o, see the photo. And here's how to get there: Phase mode independant, sine output, frequency 500MHz. Then change waveform to square and dial in frequency 0Hz -- voila. You can tweak the amplitude somewhat, at more than 3.2Vpp into 50 Ohms, the output signal gets distorted/modulated, probably due to an overload of the output amplifier.

After that I experimented with phase coupled mode a little and just for fun generated the "old time" PAL sweep signals (i.e. 50Hz and 15625Hz, triangle with 100% symmetry). In X-Y mode of the scope I wanted to check if I get a proper screen raster. Just for fun, I also viewed both waveforms in Y-t mode to see if I could align the phase -- surprise, surprise, the phase was walking through at a very slow pace. If the math was correct in the SDG, this shouldn't happen and the phase of the waveforms should stay locked against each other, maybe oscillate a tiny bit to and fro but definitely not continuously drift. The last two screenshots show this behavior, once as a still and then as a history plot (don't know why the rigol scope produces the glitch at 0 phase difference -- maybe while the counters roll over).

An then, there's still the substantial ringing in Arbitrary DDS mode after steep slopes. When selecting TrueARB, it's gone due to the slower slopes. I guess this cannot be easily solved in software, somehow there would have to be a "soft slope" mechanism implemented to limit the rise/fall times to slower than 2ns. No screen shot for this, sorry...

So depending on the settings and sequence of inputs, the SDG6X may well produce unexpected signals at the output which still means it's an unreliable instrument that cannot be depended on completely without additional care and checkups. As this, I wouldn't consider it to be a professional instrument with its current firmware. I guess there's some way to go for the Siglent engineers after all. I really hope they will put the effort into the SDG6X to eliminate the problems that are still present, the hardware is really capable and the firmware got improved a lot with the current release, but we're not quite there!

I'll keep on experimenting as time permits and will post new findings as they turn up.

Cheers,
Thomas



Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: electronic_eel on June 18, 2019, 06:31:31 pm
For anyone looking for janekivi's update files with patched root password:
Try the ones posted by tv84 instead:
https://www.eevblog.com/forum/testgear/siglent-ads-firmware-file-format/msg1870091/#msg1870091 (https://www.eevblog.com/forum/testgear/siglent-ads-firmware-file-format/msg1870091/#msg1870091)
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: Performa01 on August 17, 2019, 12:40:48 pm
I finally got some spare time to measure the level accuracy and amplitude flatness of the SDG6052X as a sine signal source for e.g. frequency response measurements.

As a comparison (and as a sanity check for my measurements) I’m including the corresponding results for a high performance signal generator (Anritsu MG3633A), which features excellent phase noise, high output power and good amplitude accuracy, especially if it is operated below 500MHz.

The Siglent SDG6052X can replace an RF signal generator in many situations, if the following limitations are observed:

•   Maximum output level is limited to 0dBm for the full frequency range of 500MHz (Anritsu MG3633A: +19dBm up to >1GHz)
•   Output levels below -56dBm require external attenuators (Anritsu MG3633A: internal attenuator to -140dBm)

So the first test is for the maximum output level of 0dBm:

(https://www.eevblog.com/forum/testgear/siglent-sdg6000-series-awg_s/?action=dlattach;attach=812631;image)
SDG6052X Level Accuracy 0dBm

As we can see, the output level is a little on the low side on my unit with an average error of -0.1dB. There are weird discontinuities of +0.12dB at 1MHz and -0.12dB at 300 and 400MHz, but the overall amplitude flatness is rather decent at +0.08/-0.17dB (0.25dB peak to peak deviation).

Compare this to the Anritsu MG633A:

(https://www.eevblog.com/forum/testgear/siglent-sdg6000-series-awg_s/?action=dlattach;attach=812637;image)
MG3633A Level Accuracy 0dBm

The Output level is spot-on with an average error of just -0.01dB. There are no discontinuities and the amplitude flatness is excellent at +0.09/-0.11dB (0.2dB peak to peak deviation).

When comparing the two devices, we should keep in mind that the Anritsu MG3633A is a 2.7GHz generator, so it can easily give excellent performance in the small subrange of 500MHz, whereas the Siglent SDG 6052X has to approach its absolute bandwidth limits.

Yet there is a sweet spot for the SDG6052X when it is operated at -30dBm:

(https://www.eevblog.com/forum/testgear/siglent-sdg6000-series-awg_s/?action=dlattach;attach=812643;image)
SDG6052X Level Accuracy -30dBm

Once again the output level is a little low with an average error of -0.05dB. The only discontinuity of +0.1dB occurs at 1MHz again and the amplitude flatness is sensational at +0.06/-0.04dB (0.1dB peak to peak deviation).

In the same situation, the Anritsu MG3633A performs slightly worse:

(https://www.eevblog.com/forum/testgear/siglent-sdg6000-series-awg_s/?action=dlattach;attach=812649;image)
MG3633A Level Accuracy -30dBm

Output level is a little high with an average error of +0.11dB. There are no discontinuities and the amplitude flatness is excellent at +0.07/-0.1dB (0.17dB peak to peak deviation).

I’ve tested all output levels from 0dBm down to -50dBm (in 10dB steps), but below -40dBm (100nW) my power meter introduces additional errors. At least all meaurements are very consistent with the results from the MG3633A.

The measurement results are only shown for frequencies above 100kHz because the power sensor is specified for 200kHz to 18GHz. It works well enough down to at least 20kHz, but the additional errors cannot be ignored anymore when we’re expecting accuracies of better than 0.1 decibel.

Here is a table overview of my measurements:

(https://www.eevblog.com/forum/testgear/siglent-sdg6000-series-awg_s/?action=dlattach;attach=813498;image)
SDG6052X Level Accuracy Table

Level is the nominal signal level as it was set on the generator.
Min. is the minimum absolute level over the full measurement bandwidth.
Max. is the maximum absolute level over the full measurement bandwidth.
Err_max is the maximum absolute amplitude error over the full measurement bandwidth.
Mean is the average absolute amplitude level.
Dev+ is the positive peak deviation of the output level relative to Mean.
Dev- is the negative peak deviation of the output level relative to Mean.

Here is an overview of the SDG6052X measurements, starting at 10kHz (which is outside the specification of the power sensor!):

(https://www.eevblog.com/forum/testgear/siglent-sdg6000-series-awg_s/?action=dlattach;attach=812832;image)
SDG6052X Level Accuracy Overview

EDIT: Frequency response overview graph added.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: Performa01 on August 18, 2019, 05:44:59 pm
I’ve mentioned the possible use of the SDG6000X as a substitute for a RF signal generator and demonstrated that amplitude accuracy and flatness up to 500MHz is absolutely adequate for the task.

Yet there are some other considerations, such as frequency accuracy and phase noise.

I’ve measured a 100MHz sine signal as 99.9999729MHz on my sample of the SDG6052X, This is a deviation of 28.1Hz or 0.281ppm. This means that the frequency accuracy is at least on par with most of the cheaper signal generators, unless they have the (usually expensive) OCXO option fitted. Since the SDG6000X accepts an external reference clock, the accuracy can be easily increased to any desired level.

Now for the phase noise, also measured at 100MHz. First the general shape of the noise spectrum, displayed within +/-100kHz of the carrier:

(https://www.eevblog.com/forum/testgear/siglent-sdg6000-series-awg_s/?action=dlattach;attach=813816;image)
SDG6052X SA CF100MHz SP200kHz RBW1Hz

This looks very clean and clearly beats the old analog PLL synthesizers by quite a margin.

Here’s the corresponding phase noise plot for 10Hz to 1MHz carrier offset – which might just show the limits of the spectrum analyzer rather than the SDG6000X – at least for frequency offsets above 1kHz:

(https://www.eevblog.com/forum/testgear/siglent-sdg6000-series-awg_s/?action=dlattach;attach=813822;image)
SDG6052X PN 100MHz

A phase noise of -98 dBc/Hz at 100Hz offset is certainly very competitive.

Most likely these measurements also apply for the SDG2000X.

As a conclusion, the Siglent 16bit SDG generators can replace a RF signal generator and within their limited frequency range they will perform vastly better than most ancient boat anchors from the analog PLL synthesizer era. You just need an external step attenuator (or 3-4 20dB inline attenuators per channel) to be able to get the low level signals required for receiver testing.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tautech on September 25, 2019, 04:49:02 am
Firmware update for SDG6000X models.

Version 6.01.01.35R5B1
25.6 MB
https://int.siglent.com/upload_file/zip/firmware/Signal_generator/SDG6000X_6.01.01.35R5B1_EN.zip

Release notes
1. Changed the upper limit of carrier frequency (sine) in Burst mode from 300 MHz to 500 MHz
2. Added some missing SCPI commands
3. Fixed several bugs:
a) Messed up signal after switching from 500 MHz sine to square in independent mode
b) Glitches when outputting pulses under certain circumstances in independent mode
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: 2N3055 on September 25, 2019, 09:48:11 am
Upgrade went without problems.

I tested only one thing, the one that was most annoying to me: the undulation phenomenon.

And it seems that is gone, at least I cannot reproduce it with previous settings.

Will test more and report.

EDIT:

- Tried bug from post 596 by TurboTom (500 MHz sine> 10 MHz> square) and that is fixed too..
- Dropouts in signal  (few ms long) are still there when you change settings. I see it happening in phase locked mode. It stops to resynchronise channels.
- In phase independent mode (P.I.M.) i don't see glitches, even for current channel. It simply starts with different timing, no glitch.  It does seem to switchover at any time, not at zero..But signal is continuous.
- In P.I.M., on squarewave, duty cycles changes (manual and numeric) are seamless..
- In P.I.M., on pulse mode, duty cycles changes (manual and numeric) are seamless..
- squarewave has fixed 2 ns edges. (SDG6052X). Quite clean.
- In pulse mode, when edges are set to 1 ns, they are actually sub 1 ns. There is ringing on top, but no undulation of any sort. When set to 1.3 ns edges signal gets much better.
Actually my scope measures 1 ns when gen is set to 1,2 ns, which, when you take into account 450ps scope rise time, this ends up around 900 ps.
So at 1.3 ns set at AWG, you get about real 1 ns edges. at AWG set to 1 ns, you get around 800 ps measured, which would be around 660 ps coming from AWG.

Those are 10%/90% times from automated measurements.

I use MSOX3104T (internal 50 Ohm termination) and cables that came with SDG6000X.
Maybe someone with faster scope with clean step response (Gaussian, mine has maximally flat response) should verify if this is not my scope acting up.
I don't have alternative 1 ns flat top signal source at hand to verify scope response.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: 2N3055 on September 25, 2019, 07:22:43 pm
Just wanted to mention something.
And I mean this in a nicest possible way... I really love my SDG6000X. But...
FIX THE ENCODER !!!!. Please!
It is not skipping sometimes. It is skipping all the time...
It's driving me crazy...  |O
Or do I have one with bad encoder??
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: TurboTom on September 27, 2019, 09:57:35 am
I haven't got much of a problem with the encoder on mine, so maybe you've really got a generator with a faulty one. These tiny "twisty-switcherydoodahs" haven't really got a reputation for high quality or long service life. The encoders of the 1990s "name brand" gear are someting else, definitely...

But I've got a different problem (rant mode on):
After the update, which went completely eventless, I had to do some tests of a circuit, outputting a pulse waveform of 18kHz. Everything went well and no problem whatsoever. I noticed short interruptions of the waveform when I changed the parameters, though, which were due to the instrument configured in "phase coupled" mode.

Powered the thing down and up again after the lunch break. Changed phase mode to independent and continued testing, just to find the circuit was behaving completely different from before. Feeling a little awkward about the generator already, I looked at the signal, and see what I found (my apologies for the poor photo quality and the mess in the background -- I guess such is life ;)...). Once again, the memory of the AWG appears not to have been initialized properly.

I expected Siglent to have taken care of these initialization problems with this firmware update. I pointed them to the problem when switching from high frequency sine to "0Hz Square" which has been solved now. But can't they just look at all the situations when a complete initialization of the WF memory is required, especially when there has been an issue with this before? Come on Siglent, do your homework! You are asking definitely professional prices for that instrument, and a professional instrument requires one thing first and this is reliability and dependability (okay, two things...). Finding the instrument to output a waveform that's not configured on the screen is a no-go, period! TBH, right now I prefer a Rigol AWG any time over this crap and I really regret not having returned it while I could. Maybe the problems will get sorted eventually with follow-up updates, but with the experience so far, will I ever trust the instrument to perform as expected? Will I ever use it to simulate drive signals for high-power output stages, containing semiconductors with three- or even four-digit price tags (summed up)?

I have to admit, Siglent as a manufacturer of test gear considerably dropped on my personal "white list" of where to go to when buying new equipment.

And by the way, the undulation issue is still there. Just select pulse mode, minimum rise/fall times and there you go. But I guess that's just a result of the anti-aliasing filter's step respopnse and the steep slope -- when selecting 2ns rise/fall times, everything looks much better.

Cheers,
Thomas
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: 2N3055 on September 27, 2019, 12:39:51 pm
Well, I thought I was crazy then, because I know there wasn't any undulation  when I tried.
So I tried again, and GRRRRRHH it IS THERE......
Then I tried to reproduce how I got it to be clean, an got it...

In phase dependent mode there IS undulation.
In phase independent mode THERE IS NOT...  :-//

Also I managed to reproduce that effect on that 18Khz pulse after restart ONCE. Then 10 times it worked nicely...  :-//

Yep, it's a bit hit and miss......


EDIT:

Investigated a bit more.

By using slow repetition, for instance 1 kHz on a 3,3ns pulse with 1 ns edges, there IS undulation regardless of channel phase coupling.
So undulation is dependent of fastest edges and varies with repetition frequency...
I don't like that.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: TurboTom on September 27, 2019, 02:44:28 pm
Tinkered again a little to understand how to reproduce the weirdness and guess what: I can repeat the fault every time (so far).

The SDG6000 is configured in phase mode independent, power up configuration - last. I select CH1 pulse waveform, 18kHz, 16µs PW, leading/trailing edge 1µs, maximum amplitude (don't know if that's relavant). Output impedance doesn't seem to matter. After configuration, the waveform is usually okay. The I simply power the instrument down and up again after maybe 30 seconds. When it's fully booted, I enable output 1, and voila!  :'(  Looks to me like an incomplete power-up initialization. Toggling modulation on-off restores the correct waveform. Anybody needs an almost better-than-new SDG6000?  >:D

Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: 2N3055 on September 27, 2019, 06:23:13 pm
Tinkered again a little to understand how to reproduce the weirdness and guess what: I can repeat the fault every time (so far).

The SDG6000 is configured in phase mode independent, power up configuration - last. I select CH1 pulse waveform, 18kHz, 16µs PW, leading/trailing edge 1µs, maximum amplitude (don't know if that's relavant). Output impedance doesn't seem to matter. After configuration, the waveform is usually okay. The I simply power the instrument down and up again after maybe 30 seconds. When it's fully booted, I enable output 1, and voila!  :'(  Looks to me like an incomplete power-up initialization. Toggling modulation on-off restores the correct waveform. Anybody needs an almost better-than-new SDG6000?  >:D

I think I found something interesting. I'm still testing in detail.
But, just quickly, it seems that it is either not saving or not reading last state config completely.

I just played with 100MHz pulses. Then I set it the way you said again, rebooted, and it came up with my previous 100 MHz pulse. Like it didn't save it right or didn't  read it all..
I will try to test in more detail..

Steps to reproduce:

pulse, 100MHz repetiton, 1 ns rise/fall, 3,3 ns width. Phase independent.  Then set your 16 kHz pulse and reboot. All data entered by keyboard. Tried changing frequency with encoder, all the same.
What you get after reboot?

If I set AWG to boot to user config file, save state to that config file it will boot right.
So only LAST function doesn't work properly...
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tv84 on September 27, 2019, 07:13:53 pm
Anybody needs an almost better-than-new SDG6000?  >:D

Do you accept a DP811 in exchange?    ;D
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: TurboTom on September 27, 2019, 07:16:00 pm
Anybody needs an almost better-than-new SDG6000?  >:D

Do you accept a DP811 in exchange?    ;D

Sorry, got one already -- also almost better-than-new condition...  8)
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tv84 on September 27, 2019, 07:21:08 pm
Sorry, got one already -- also almost better-than-new condition...  8)

I know ;) but 2 are better than 1 !  ;D
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tautech on September 27, 2019, 08:45:00 pm
Firmware update for SDG6000X models.

Version 6.01.01.35R5B1
25.6 MB
https://int.siglent.com/upload_file/zip/firmware/Signal_generator/SDG6000X_6.01.01.35R5B1_EN.zip

Release notes
1. Changed the upper limit of carrier frequency (sine) in Burst mode from 300 MHz to 500 MHz
2. Added some missing SCPI commands
3. Fixed several bugs:
a) Messed up signal after switching from 500 MHz sine to square in independent mode
b) Glitches when outputting pulses under certain circumstances in independent mode
It seems 6.01.01.35R5B1 is some beta version as some things are fixed but some are broken.  :(

A customer had some problems with IQ usage and SCPI commands that the factory are now aware of and are addressing.
So for now unless you need something from 35R5B1 best advice is to stay with 6.01.01.33R2.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tv84 on September 27, 2019, 09:16:35 pm
It seems 6.01.01.35R5B1 is some beta version as some things are fixed but some are broken.  :(

tautech, don't call it beta just because of the bugs... If it is beta it should have followed the beta members path only.

I think it's an official version that should have been more thoroughly tested, according to previous members! Although I admit it's very difficult to emulate all the tests that the experts here submit their equipments to!  :box:

Let's hope that Siglent is able to correct them in a timely manner.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tautech on September 27, 2019, 09:38:54 pm
It seems 6.01.01.35R5B1 is some beta version as some things are fixed but some are broken.  :(

tautech, don't call it beta just because of the bugs... If it is beta it should have followed the beta members path only.

I think it's an official version that should have been more thoroughly tested, according to previous members!
Yes and no, Siglent is getting lazy not renaming their FW file to drop the B, we have seen this before and it sometimes means the firmware is unfinished.
One time I got emails from DSO beta testers proclaiming surprise that some FW had been uploaded to the websites yet it was still in development. Normally a more secure method is used to share beta FW.

Quote
Let's hope that Siglent is able to correct them in a timely manner.
I have 3 factory confirmed SDG6kX issues in my inbox.

One of which is a new SCPI command to load a users IQ creation: :IQ:WAVE:USER "UserIQ_1.arb"  (for 6.01.01.35R5B1)
This should appear in the next Programming guide revision.
Title: Re: Siglent SDG6000X series 200-500 MHz AWG's
Post by: tv84 on October 13, 2019, 09:25:21 am
So, Siglent China has the FW for SDG6000X-E model:

http://www.siglent.com/upload_file/zip/firmware/Signal_generator/SDG6000X-E__6.01.01.33R2_CN.zip (http://www.siglent.com/upload_file/zip/firmware/Signal_generator/SDG6000X-E__6.01.01.33R2_CN.zip)

It's Product ID: 10900

It's older brother is 10800.

The .ADS package also flashes a BOOT.bin...