Siglent SDG6000X series 200-500 MHz AWG's

[Martin72]

Hi,

F = 1 MHz

Waveform, amplitude?

And what output type did you used ? Pulse or 50%

[Detlev]

Hi,

F = 1 MHz

Waveform, amplitude?

And what output type did you used ? Pulse or 50%

Waveform: 50% square wave
Level: 0 dBm

I’ve added this above.

[Martin72]

Thanks, Detlev.
And how did you set the sync signal (trigger out) on the SDG?
There are options for “Pulse” and “50%.”

[Detlev]

Hi Martin,

I couldn't find the settings for the trigger output. Can you tell me how to find them?   

The SDG outputs a pulse.

[Martin72]

Hi Detlev,

You can find the settings in "Utilities", Page2, Sync....

[Detlev]

All right, I don't have that option since I used square instead of pulse.

[Martin72]

What firmware version do you have on your device?

[2N3055]

All right, I don't have that option since I used square instead of pulse.

no, no...

It has nothing to do with the waveform.

(Utility button) -> 2nd page (Synch) -> (Out Type) 50%/Pulse

[Martin72]

I had shown and written that, after all....
....and yet I still didn't recognize his picture...

Edit:
The manual doesn't “recognize” the 50% either... maybe it's because of new firmware after all?

[2N3055]

I had shown and written that, after all....
....and yet I still didn't recognize his picture...

Edit:
The manual doesn't “recognize” the 50% either... maybe it's because of new firmware after all?

Yeah it could be that he does not latest FW, but I am under impression he misunderstood "which" Pulse is being talked about. I might be wrong but still it cannot hurt to try to explain...

[2N3055]

I had some time to look into this.

There is a slight phase drift (that is basically just frequency difference) from Opt Out.
After some time AWG makes bulk correction.
At 10kHz Max error is 3,373ns.
Because of this the skew between Opt OUT and Ch1 looks like a sawtooth.

I will try to inquire with Siglent if this is known limitation of architecture or something that could be made better.

[Detlev]

I have now updated the firmware from 37R6 to 38R3, and I can now see the "Out Type" option. 

[Martin72]

Yes, along with a few other things, it was implemented in the latest firmware update.

[Martin72]

So what exactly is the problem? Can't you use the device anymore?

[KungFuJosh]

I dunno. Seems like you want it to do something very niche, which maybe it can or can't do.

I'm more annoyed because wiggling the cables only temporarily cured the touchscreen. That's a little more basic, and shouldn't have been a problem in the first place, or again now.

[mawyatt]

Anyone know if the SDG2042X experiences this "phase correction" issue?

We are too lazy at this time to look into this, but figured someone would already know

Best

[KungFuJosh]

I dunno. Seems like you want it to do something very niche, which maybe it can or can't do.

I'm not looking for anything specific or fancy from this unit. I simply don't see why I should be forced to use an external attenuator just to change the amplitude.

I hear that, I just don't know if it is capable of doing what you want or not. If it isn't, maybe it can be improved via firmware if there isn't a hardware limitation.

I'm more annoyed because wiggling the cables only temporarily cured the touchscreen. That's a little more basic, and shouldn't have been a problem in the first place, or again now.

I haven't experienced that issue myself. Does the touchpad stop working when you wiggle the output connectors?

No, the touchscreen stopped working on its own. Some other people have experienced this. I opened it up, and wiggled the wires from the front panel to see if anything was loose, and the touchscreen started working again. Then I tried using the SDG again a couple days later and the touchscreen was dead again.

Thanks,
Josh

[KungFuJosh]

No, the touchscreen stopped working on its own. Some other people have experienced this. I opened it up, and wiggled the wires from the front panel to see if anything was loose, and the touchscreen started working again. Then I tried using the SDG again a couple days later and the touchscreen was dead again.

I took a look inside. It’s a simple resistive touch sensor controlled by a TSC2046. It would be a good idea to check the 4-pin connector — the issue might just be a cold solder joint. If the connection drops when you wiggle it, the defect should be fairly easy to find since the IC is easily accessible (you could even hook up a logic analyzer to its output).

I know, I'm just annoyed that I will need to open it again. It could be the header or the cable.

I'll wait until I replace the fan, unless the lack of touch annoys me enough sooner than that. It annoys me more that this is shit quality control, and I expect better from them.

[BillCRM]

Anyone met this bug before? I tried to enable the I/Q option of my SDG6052X-E, using the python script, the generator accepted the option key, but when pressed save, it back to the menu to ask me for the key, and then fall into a endless loop, the key seems OK as a random key the generator won't accept, but I don't know why the key can't be saved. Is that a software bug? Or the E version just can't support the I/Q feature?

[Martin72]

Exactly, the E-series doesn't have I/Q modulation.
You can see that when you compare the front panels of the 6000 series.
Or in the data sheets...

[Le_Bassiste]

Similar to your observations: while setting up a PWM signal to test a DC/DC power stage i dared to change the PWM frequency 'on the fly'. can't recommend doing that. after all the years they still haven't managed to get smooth transitions when changing the frequency with the tuning knob.

[tautech]

When any issue is found it is necessary to state the firmware version in use.
Only then are Siglent engineers able to attempt to replicate any faults to address them.

Current is V6.01.01.38R3

[Le_Bassiste]

... Yes, that is exactly the version I have (V6.01.01.38R3).

Same here: SW V6.01.01.38R3. Hardware is 02-00-00-81-41

[KungFuJosh]

Moving this conversation here, where it's more relevant...

Here it is using a ProbeMaster 250MHz 10x probe with a BNC adapter direct to the SDG6000X.

Those plots look really bad, unacceptable for any serious use!!

The probe and DSO don't seem to be properly compensated and/or are incompatible, or the signal source is defective.

I wasn't expecting it to look good, as the setup was not very smart. Tell me what you think of these results.

The first two images are ProbeMaster 250MHz (old and most frequently used probe).

The second two images are a brand new TestTec 500MHz probe that came with my scope (never used except for compensation).

Each pair shows compensation on the scope (1kHz), then the stupid connection to the SDG6000X (1MHz).

The fifth image is a 50Ω BNC cable direct from the scope to the SDG6000X properly set to 50Ω on both ends.

The photo is of the stupid setup.

Thanks,
Josh

[mawyatt]

Much better, the 3rd images looks really good!!

What caused the large "hump" in the previous images?

Best