Siglent SDS800X HD 12 bit DSO's

[tautech]

With the probe shorted, nothing. With the probe open on the table even the orientation matters.

Yep this, 100 % !
Yet in the RF world we use this to our advantage. 

[watchmaker]

The main culprit was a bad mat ground and my USB hubs.

I find that strange because an ESD mat has a very high resistance. Depending on the type of mat you have the top of the mat measures over a GOhm and the bottom on most mats will measure around 80...100 K while a scope input is 10MOhm, forming a voltage divider.

I found this for you made by Dave:

But now I would like to know what is an acceptable level of noise when the probe is unloaded? Much of my confusion (?) is that I have no idea of the proper expectations.

With the probe shorted, nothing. With the probe open on the table even the orientation matters.

Most noise problems in measurements are caused by noise coupled trough Y type capacitors present in switching power supplies between rectified GND and the output GND of a switching power supply.

To give you an idea, FesZ Electronics has this nice presentation:

Because of this I use power supplies with "normal transformers" when switching power supplies generate to much noise. Other sources of noise are computers (especially if you connect some debugging tool to your circuit), LED lighting power supplies, or just any other switching power supply in your lab. Some of those low cost power bricks can be "seen" at the other side of the room.

Thank you.  I also use linear power supplies for this reason.  Billy O just suggested I am chasing a non issue.

AS for the ESD, indeed there was an objective improvement in the floating probe noise once I securely attached the mat lead to the metal power strip housing.  I guess there is a point where the resistanc e is too high for the mat to be effective.  Certainly, infinite resistance does not work.

But, you hit and clarified (for me anyway) my central question. At what level (for an amateur) is a work area noisy (impacts non-specialist scope measurements at 20MHz and below)?  How is this objectively measured?

THANKS!

[temperance]

But, you hit and clarified (for me anyway) my central question. At what level (for an amateur) is a work area noisy (impacts non-specialist scope measurements at 20MHz and below)?  How is this objectively measured?

If the signal to noise ratio is to high to make meaningful measurements. If the scope triggers for example on the noise instead of on the the signal in question. But you have options if this happens. Under trigger options you will find something called Hf and Lf reject.

Maybe this can help you to get an idea on how to quantify noise: https://download.tek.com/document/LowLevelHandbook_7Ed.pdf

[gamalot]

But, you hit and clarified (for me anyway) my central question. At what level (for an amateur) is a work area noisy (impacts non-specialist scope measurements at 20MHz and below)?  How is this objectively measured?

If the signal to noise ratio is to high to make meaningful measurements. If the scope triggers for example on the noise instead of on the the signal in question. But you have options if this happens. Under trigger options you will find something called Hf and Lf reject.

Maybe this can help you to get an idea on how to quantify noise: https://download.tek.com/document/LowLevelHandbook_7Ed.pdf

They changed the color of the cover of the book, now it looks more TEK and less Keithley.

[Furna]

They changed the color of the cover of the book, now it looks more TEK and less Keithley.

Nevertheless seems to be a great resource!

[eTobey]

The siglent clears the bloody screen (rollmode), when i take a screenshot. Thats not what i understand of a "screenshot".

I guess i have missed something?

[2N3055]

The siglent clears the bloody screen (rollmode), when i take a screenshot. Thats not what i understand of a "screenshot".

I guess i have missed something?

You are in a roll mode. You see something. You stop scope. Press save. Is that it?
This works fine for me.

Maybe I misunderstood.

[KungFuJosh]

The siglent clears the bloody screen (rollmode), when i take a screenshot. Thats not what i understand of a "screenshot".

I guess i have missed something?

You are in a roll mode. You see something. You stop scope. Press save. Is that it?
This works fine for me.

Maybe I misunderstood.

I assume from his description that he didn't stop the scope.

[rssdev]

Hi everyone!

Is there any real proof that the unlocked 70 and 100 MHz models can actually use a 100 Mpts memory depth, like the SDS824X HD?
Has anyone saved a real signal and exported it as a CSV file for analysis? Ideally, there would be two cases: one CSV with the initial model and one more after switching to the SDS824X HD model.

Sorry if this is a repeated question, but I couldn't find the answer anywhere.

[2N3055]

Hi everyone!

Is there any real proof that the unlocked 70 and 100 MHz models can actually use a 100 Mpts memory depth, like the SDS824X HD?
Has anyone saved a real signal and exported it as a CSV file for analysis? Ideally, there would be two cases: one CSV with the initial model and one more after switching to the SDS824X HD model.

Sorry if this is a repeated question, but I couldn't find the answer anywhere.

You couldn't find specific answer because it is redundant question.
Scope will show you on the screen at any time what amount of memory is used.
And in acquisition menu if 100Mpts is available then it is available.

Procedure to do the changes is not some kind of hacking and messing with actual scope code and filesystem (like they do with Rigol DHO scopes). There are no tricks involved.
You are applying a legit license to upgrade scope.

Difference is only if you legally bought the license or you got it different way..

[bateau020]

Has anyone saved a real signal and exported it as a CSV file for analysis?

I can confirm that my upgraded 814 does 100Mpts. But with 100Mpts it won't let you save to CSV. You will have to save to binary format (which will be 200MB), and then use the windows exe "fileconverter.exe" to extract the data to other formats.

[tautech]

Has anyone saved a real signal and exported it as a CSV file for analysis?

I can confirm that my upgraded 814 does 100Mpts. But with 100Mpts it won't let you save to CSV. You will have to save to binary format (which will be 200MB), and then use the windows exe "fileconverter.exe" to extract the data to other formats.

The Bin to CSV convertor tool is available from the scope in the Utility Save/Recall menu.

[Yuriy V.]

Hi All!
At what horizontal scan time does the SDS800X HD switch to scan mode?

[2N3055]

Hi All!
At what horizontal scan time does the SDS800X HD switch to scan mode?

I presume you think of Roll mode?

You need to enable Roll mode with a button.  And then it will roll (scan) if your timebase is 50ms/div or slower.

P.S. No need to ask twice.

[Yuriy V.]

I presume you think of Roll mode?

I'm trying to figure out the differences with my old TEK1002B. At 100ms/div it switches to scanning without a trigger (scan mode), which causes some inconvenience. At what horizontal scanning time does the same thing happen on the SDS800X HD (if don't turn on the roll mode)?

[2N3055]

I presume you think of Roll mode?

I'm trying to figure out the differences with my old TEK1002B. At 100ms/div it switches to scanning without a trigger (scan mode), which causes some inconvenience. At what horizontal scanning time does the same thing happen on the SDS800X HD (if don't turn on the roll mode)?

It will never switch to Roll mode until you activate it with button.
You can set to 100s/div and it will do normal triggering, unless in Roll mode.

[Yuriy V.]

There's an unexpected and slightly annoying artifact (unnecessary information) in the screenshot. I haven't yet found a way to disable it. I believe this artifact can be considered a minor firmware bug, which I'd like to see fixed.

[tautech]

There's an unexpected and slightly annoying artifact (unnecessary information) in the screenshot. I haven't yet found a way to disable it. I believe this artifact can be considered a minor firmware bug, which I'd like to see fixed.

The Acquiring flag is present until the memory buffer fills at all timebases slower than 20ms.
It's not a bug but a message to the user that the scope is in auto Roll mode.

[Yuriy V.]

It's not a bug but a message to the user that the scope is in auto Roll mode.

This is indeed a bug, since this message also appears on the screenshot image (save function).

[2N3055]

It's not a bug but a message to the user that the scope is in auto Roll mode.

This is indeed a bug, since this message also appears on the screenshot image (save function).

Let's agree to disagree.
Screenshot by definition is that: a snapshot of a screen. An equivalent to taking a photograph of a screen while working.
So it is literally working perfectly, even to the annoying details... 

[tautech]

It's not a bug but a message to the user that the scope is in auto Roll mode.

This is indeed a bug, since this message also appears on the screenshot image (save function).

No it's a flag to inform you are in auto Roll mode.

Whereas if you select dedicated Roll mode there is no Acquiring flag and instead Roll mode in red is displayed where Arm/Trig would normally be.

[MathWizard]

There's an unexpected and slightly annoying artifact (unnecessary information) in the screenshot. I haven't yet found a way to disable it. I believe this artifact can be considered a minor firmware bug, which I'd like to see fixed.

I've never seen those overlapping color patterns before, is that some options ??

[Performa01]

There's an unexpected and slightly annoying artifact (unnecessary information) in the screenshot. I haven't yet found a way to disable it. I believe this artifact can be considered a minor firmware bug, which I'd like to see fixed.

As has been stated already, not everything you don't like is a bug. In this particular case, it's a less desirable feature.

As I'm sure you've found out by yourelf already, this indicator appears at time bases slower than 50 ms/div when you have roll mode disabled (Roll button not illuminated).

I agree that it would be nice to have indicators like this positioned somewhere outside the trace area, but there is no free space for it, hence this is a topic for some GUI redesign, which might come eventually.

Just to be clear: eventually is not the same as soon.

As a workaround, just stop the acquisition before taking the screenshot.

[tautech]

There's an unexpected and slightly annoying artifact (unnecessary information) in the screenshot. I haven't yet found a way to disable it. I believe this artifact can be considered a minor firmware bug, which I'd like to see fixed.

I've never seen those overlapping color patterns before, is that some options ??

Display/Color grading.
Have a play with it.

[crysti]

SDS800X HD — Bode Interface Does Not Validate AWG Connection Over LAN; Only mDNS/NTP Traffic Seen. Network Reset Needed?

Context:
Equipment: Siglent SDS800X HD, firmware 1.6.5; FY6900 AWG; ESP-01 configured according to https://github.com/sq6sfo/espBode.
Network: Local LAN with 3 devices — SDS800X HD, FY6900, Windows 11 PC.
Connectivity: From Windows 11, both oscilloscope and AWG are visible.

Problem:
In the SDS800X HD, under Bode Plot > AWG over LAN, the Test button is unstable: UI either freezes, and no TCP/UDP traffic is sent to the AWG.
Wireshark capture shows that pressing Test generates only mDNS and NTP packets from the oscilloscope, with no packets sent to the AWG IP.

Reproduction steps:
   In the Bode configuration interface
   Enter the AWG LAN IP in SDS800X HD.
   Press Test for LAN to AWG IP Connectivity Check.
   No packets are transmitted from the DSO to the AWG IP address, and sometimes the UI freezes after several test attempts.

Attempts made:
   Full reboot
   Factory reset
   Security Erase
   Firmware update to 1.6.5

Result: no effect, issue persists.

Questions:
Is there a procedure to fully reset network settings or to restore partitions preserving critical files for SDS800X HD?

Notes:
PC communication with FY6900 and SDS800X HD over LAN works fine. The problem lies between SDS800X HD and FY6900 in the Bode interface.

I sincerely appreciate your support!