Best scope for 5-6k

[KungFuJosh]

USB sticks formatted in Windoze then used to save anything from any Siglent instrument that all run Linux will be reported as needing fixing when next fitted to a Windoze PC.
Normal and ignore it.

I am not sure what you mean. It never gave any errors plugging the drive into the Windows computer after it was in the scope. That printout was me just trying to figure out the allocation units

He means that sometimes (not always, depends on whatever) after you use a flash drive formatted on a Windows computer on your Linux TE, Windows might complain the next time you insert in your computer.

I have a DMM on my computer desk, so it's easy to recreate that annoyance.

[resonant_frequency]

Ahhh thanks for the explanation. I haven't encounter that yet with the Siglent scope and my Windows 11 PC.

[BillyO]

So, I got to try the non-update anomaly on my SDS2504XP and my SDS824XHD.  I could not reproduce on either, so the anomaly might be limited to the SDS3000XHD

In the pictures below image A was taken at:
 - CH 3, 4 on
- event that triggers scope

And image B was taken at:
- measure CH 3 - no immediate update

But I also added CH4 measure.  It also updated.

[asmi]

USB sticks formatted in Windoze then used to save anything from any Siglent instrument that all run Linux will be reported as needing fixing when next fitted to a Windoze PC.
Normal and ignore it.

No, it's NOT normal. This message indicates that a volume was not unmounted properly.

[asmi]

He means that sometimes (not always, depends on whatever) after you use a flash drive formatted on a Windows computer on your Linux TE, Windows might complain the next time you insert in your computer.

That means your non-Windows system is not unmounting volume properly, it's not Windows fault, but problem with that other system. I use Windows and Linux together all the time and use USB sticks to pass data around, and I can't remember last time I've seen a message like that.

[KungFuJosh]

That means your non-Windows system is not unmounting volume properly, it's not Windows fault, but problem with that other system. I use Windows and Linux together all the time and use USB sticks to pass data around, and I can't remember last time I've seen a message like that.

I know what you're saying, but there is no "unmount hw" option in any piece of TE that I've seen for safely removing a USB drive. I yank the drives out at any time without shutting off the host devices.

[asmi]

I know what you're saying, but there is no "unmount hw" option in any piece of TE that I've seen for safely removing a USB drive. I yank the drives out at any time without shutting off the host devices.

I do the same, and yet I never had this issue. So there is something wrong with your TE - they are supposed to bring volume to "ready to disconnect" state after completing any IO operation with that device.

[BillyO]

... they are supposed to bring volume to "ready to disconnect" state after completing any IO operation with that device.

I've had this occur sometimes.  Not always though.  There may be a pattern, but I've not noticed it yet.

[asmi]

I've had this occur sometimes.  Not always though.  There may be a pattern, but I've not noticed it yet.

Normally this happens when you remove a device while IO operation was still in progress, and/or some of the writes were cached but weren't actually written to a drive yet. Nowadays most OSes disable write caching for removable drives for that exact reason, but some TM vendors might not have gotten the memo yet, which leads to these problems.

[KungFuJosh]

That could certainly be the issue. Somebody send them the memo.

[tautech]

I've had this occur sometimes.  Not always though.  There may be a pattern, but I've not noticed it yet.

Normally this happens when you remove a device while IO operation was still in progress, and/or some of the writes were cached but weren't actually written to a drive yet. Nowadays most OSes disable write caching for removable drives for that exact reason, but some TM vendors might not have gotten the memo yet, which leads to these problems.

Interesting, thanks for the discussion.
Like Bill I don't see it all the time but I get to use so so many models and there might be a pattern I haven't noticed yet. 

It sounds like a lot of testing is required to possibly identify model ranges that initiate the warning in a Windoze formatted USB stick.
Too much on currently to go down this rabbit hole.....

[asmi]

It sounds like a lot of testing is required to possibly identify model ranges that initiate the warning in a Windoze formatted USB stick.
Too much on currently to go down this rabbit hole.....

There is no rabbit hole. There are sloppy manufacturers who can't read documentation: https://learn.microsoft.com/en-us/windows/win32/fileio/exfat-specification#31132-volumedirty-field It's a single bit in the filesystem's boot structure with very clear semantics.

[tautech]

It sounds like a lot of testing is required to possibly identify model ranges that initiate the warning in a Windoze formatted USB stick.
Too much on currently to go down this rabbit hole.....

There is no rabbit hole. There are sloppy manufacturers who can't read documentation: https://learn.microsoft.com/en-us/windows/win32/fileio/exfat-specification#31132-volumedirty-field It's a single bit in the filesystem's boot structure with very clear semantics.

There is where I sit.

Some development teams might be more diligent than others.....just saying.
Not all models will be affected....this needs extensive testing and we can help by identifying them and then HQ can do the hard yards to ensure all products no longer have these issues.

[KungFuJosh]

The new DMM firmwares have this issue, probably across the board. My SDM3055X-E and SDM3065X both exhibit this behavior with flash drives. I've not tried formatting it on a different computer; I don't know if that's relevant or not.

[tautech]

The new DMM firmwares have this issue, probably across the board. My SDM3055X-E and SDM3065X both exhibit this behavior with flash drives. I've not tried formatting it on a different computer; I don't know if that's relevant or not.

We need check AWG's, PSU's and analyzers too.
Any chance I can task you with this.....too busy selling equipment here. 

[asmi]

This is what surprises me. As I understand,  most of those devices run some version of Linux,  and over there it's a solved problem for at least a decade. So all developers need to do is to set this up properly and don't screw it up in userland by doing something stupid like not closing handles...

[KungFuJosh]

The new DMM firmwares have this issue, probably across the board. My SDM3055X-E and SDM3065X both exhibit this behavior with flash drives. I've not tried formatting it on a different computer; I don't know if that's relevant or not.

We need check AWG's, PSU's and analyzers too.
Any chance I can task you with this.....too busy selling equipment here. 

My PSU doesn't have a USB A port. I'll check what does though.

[resonant_frequency]

What does the GA mean when zooming the time axis out?

Also a couple questions I posted earlier that go buried: is there a way to have the measurement gated on the zoom? Is there a way two have more than 5 measurements at the same time across multiple channels? It seems like I can only add 5 in the Advanced measure mode.

[Martin72]

What does the GA mean when zooming the time axis out?

It's in the manual, starting on page 221...

https://www.siglenteu.com/wp-content/uploads/2026/04/SDS3000X_HD_UserManual_EN01B.pdf

[Performa01]

Also a couple questions I posted earlier that go buried: is there a way to have the measurement gated on the zoom? Is there a way two have more than 5 measurements at the same time across multiple channels? It seems like I can only add 5 in the Advanced measure mode.

Martin already answered the Gate question, so there's only the number of measurements left: you can have up to 12 advanced measurements across channels if you switch to M2 Display Mode in the Measurement Config.

You cannot get histograms in this mode, but all other displayed information is the same as with M1.

If the empty measurement slots bother you (when you have less than 12 measurements), then you can check the "Hide Null" box to get a compact view of the active measurements.

[resonant_frequency]

Thanks! I don't see the hide null box and its not in the manual. Under which menu is it located?

Probably should have looked at the manual for the GA but thanks for the page #. Is there a way to have the gate automatically set to the zoom or is the only way to adjust the gate manually to be the zoom?

Edit: is there way to hide the top and bottom bars to get more screen real estate?

[tautech]

...............
Edit: is there way to hide the top and bottom bars to get more screen real estate?

No.
But you can get more display size via using a PC in 2 ways:

Connect the scope to your LAN and use the webrowser where you can also use a fullscreen setting and/or use the PC mouse to drive the scope remotely.

Additional features are also available with the SigScopeLab SW but there is memory depth limitations when using this free SW.
https://www.siglent.com/int/software/sigscopelab/

[Performa01]

Thanks! I don't see the hide null box and its not in the manual. Under which menu is it located?

It's not under any menu but in the top left of the measurement table. The first two attached screenshots demonstrate the effect of "Hide Null".

Probably should have looked at the manual for the GA but thanks for the page #. Is there a way to have the gate automatically set to the zoom or is the only way to adjust the gate manually to be the zoom?

Easy: you just select the corresponding zoom channel as source for these measurements, e.g. Z4 instead of C4.

This even has the advantage, that you can mix measurements over the full record with zoom-gated measurements. For instance you want to use the full record length for measurements that benefit from a high number of samples, such as Mean, RMS, Stdev or also frequency and period. Rise time measurements on the other hand would benefit from the better time resolution on short time bases in zoom mode, when the x-interpolation or sinc-reconstruction kicks in.
 

Edit: is there way to hide the top and bottom bars to get more screen real estate?

The layout is pretty efficient in providing the maximum functionality while using minimal screen space, hence these two bars cannot be hidden.

If you have a lot of measurements, you can change the result style from "Embedded" to "Floating", see third screenshot attached.

[resonant_frequency]

It's not under any menu but in the top left of the measurement table. The first two attached screenshots demonstrate the effect of "Hide Null".

Thanks for the pics, I didn't have statistics on so it wasn't showing up before.

Easy: you just select the corresponding zoom channel as source for these measurements, e.g. Z4 instead of C4.

This even has the advantage, that you can mix measurements over the full record with zoom-gated measurements. For instance you want to use the full record length for measurements that benefit from a high number of samples, such as Mean, RMS, Stdev or also frequency and period. Rise time measurements on the other hand would benefit from the better time resolution on short time bases in zoom mode, when the x-interpolation or sinc-reconstruction kicks in.

Great that works perfect.

The layout is pretty efficient in providing the maximum functionality while using minimal screen space, hence these two bars cannot be hidden.

Darn, okay. The screen feels a little cramped with four waveforms compared to our tek scope that is larger vertically.

One thing that makes it feel smaller too is that the trigger doesn't seem to fire when the waveform is zoomed out too much. With a 1.4Vpp sine wave at 10V/div with a DC rising edge trigger at 0V it doesn't fire. The same settings to fire the trigger on the Tek scope we're evaluating. Any ideas what's going on here?

[KungFuJosh]

One thing that makes it feel smaller too is that the trigger doesn't seem to fire when the waveform is zoomed out too much. With a 1.4Vpp sine wave at 10V/div with a DC rising edge trigger at 0V it doesn't fire. The same settings to fire the trigger on the Tek scope we're evaluating. Any ideas what's going on here?

Minimizing vertical scale isn't the same thing as zooming out. Your vertical scale is relative to your scope's processing power.