And in measurements you also have CH Delay page... For inter-channel measurements.Lots to play with. But for now, i stay a cursor fanboy. I like to see what i actually measure.
I have more good news for you.
You still use measurements, and enable cursors, but enable Measurement cursors.
Those follow automatic measurements and show where is measurement performed at...
Yes, that should work. Note that setting up a measurement in advanced mode is a bit finicky:
Edit: That actually appears to be a little glitch in the UI. There are nice explanatory texts for each measurement item. But there is no way to see them without actually selecting that item (before you see its explanation) and auto-closing the dialog. Well, you can re-open the dialog afterwards, to see explained what you just did...
I have more good news for you.
I have more good news for you.
That is awesome.
I stumbled upon an issue:
Switching from percent to count in the histogram window is sometimes quite unresponsive. First i thought i had to really hit the dot, but its not the case. It works for a few seconds, then it wont, then it works again. Without doing anything to it.
Find attached the setupfile.
I will check but it might not be unresponsive but recalculating......
But will check and if something is fishy will be reported...
I will check but it might not be unresponsive but recalculating......
But will check and if something is fishy will be reported...
Save your time:
I just found out, that it is just hard to hit! That needs a bit of tweaking id say. Because i am not drunk, und i dont have big fingers. Still i fail quite a lot in hitting those.
Suggestion:
Restart/continue mask test when hitting run/stop.
An inactive operation is easily missed after it has been stopped from a fail. Hitting the run/stop button alone does not restart the fail test. No indication visible.
Edit: That actually appears to be a little glitch in the UI. There are nice explanatory texts for each measurement item. But there is no way to see them without actually selecting that item (before you see its explanation) and auto-closing the dialog. Well, you can re-open the dialog afterwards, to see explained what you just did...
When I STOP/START it restarts from 0.
When I STOP/START it restarts from 0.Not if it has stopped from a failure, or its operation has not been activated in the first place. I have written this in my post: "An inactive operation is easily missed after it has been stopped from a fail."
Coupling two functions with some auto type of reaction is not welcome here.
Coupling two functions with some auto type of reaction is not welcome here.I am OK with that, but then it should be clearly visible, that it is currently not activated.
Coupling two functions with some auto type of reaction is not welcome here.I am OK with that, but then it should be clearly visible, that it is currently not activated.
With many analysis packages there is enabled or disabled. Like decoding for instance.
For some analysis packages you have two separate states: analysis package activated and separate testing progress on/off.
That is like that for Bode plot, Power analysis etc.
This is so for Mask test also.
If you enable Show statistics, it shows it is not counting. If you enable [Stop on fail] it will not exit Mask mode but only stop testing.
We might have some additional message somewhere that would mean "testing in progress".
But in reality it is counting up the number tests performed as it works, as an indicator it is working.
We might ask for something obvious in addition to Info lines (something like "Collecting/Paused"), but basic indicators are already there.
I also keep side menu folded out all the time when doing Mask test, so I see it there.
If you enable Show statistics, it shows it is not counting. If you enable [Stop on fail] it will not exit Mask mode but only stop testing.
If you enable Show statistics, it shows it is not counting. If you enable [Stop on fail] it will not exit Mask mode but only stop testing.
It shows counting, but what if an event takes a dozend of seconds to appear? Than you wait that long?
Efficient would be you just beeing able to tell with a quick glimpse, if it is activated.
I have more good news for you.
You still use measurements, and enable cursors, but enable Measurement cursors.
Those follow automatic measurements and show where is measurement performed at...
Maybe we should rename the thread into "Bugs/Wanted/Available Features".
Firstly, siglent is more concerned about bugs, and it is Siglent's obligation to modify them,
Actually, I have an idea to split this thread into two threads, one is bugs+firmwares, and the other is wanted features (Current thread),
if this thread is too long, which may give people the illusion that there are many product problems.
Firstly, siglent is more concerned about bugs, and it is Siglent's obligation to modify them,
Then another wanted features thread(Current thread) can provide good ideas for all manufacturers, allowing everyone to speak freely and leverage their professional advantages.
In the bugs+firmwares thread, can standardize the problem description, mainly referring to the form of ebastler. Everyone can also supplement it to see if there is any missing information:
Coupling two functions with some auto type of reaction is not welcome here.I am OK with that, but then it should be clearly visible, that it is currently not activated.
With many analysis packages there is enabled or disabled. Like decoding for instance.
For some analysis packages you have two separate states: analysis package activated and separate testing progress on/off.
That is like that for Bode plot, Power analysis etc.
This is so for Mask test also.
If you enable Show statistics, it shows it is not counting. If you enable [Stop on fail] it will not exit Mask mode but only stop testing.
We might have some additional message somewhere that would mean "testing in progress".
But in reality it is counting up the number tests performed as it works, as an indicator it is working.
We might ask for something obvious in addition to Info lines (something like "Collecting/Paused"), but basic indicators are already there.
I also keep side menu folded out all the time when doing Mask test, so I see it there.That can be remedied by using the other menu setting and compressing the active display and grid so to not hide anything under the dropdown menu bar.
I have more good news for you.
You still use measurements, and enable cursors, but enable Measurement cursors.
Those follow automatic measurements and show where is measurement performed at...
Maybe we should rename the thread into "Bugs/Wanted/Available Features".
Actually, I have an idea to split this thread into two threads, one is bugs+firmwares, and the other is wanted features(Current thread),
if this thread is too long, which may give people the illusion that there are many product problems.
Firstly, siglent is more concerned about bugs, and it is Siglent's obligation to modify them,
Then another wanted features thread(Current thread) can provide good ideas for all manufacturers, allowing everyone to speak freely and leverage their professional advantages.
Although manufacturers are not obligated to implement features that are not included in the datasheet, when ideas that are beneficial to all products appear, manufacturers will prioritize their implementation.
In the bugs+firmwares thread, can standardize the problem description, mainly referring to the form of ebastler. Everyone can also supplement it to see if there is any missing information:
Version: 1.1.3.3
Problem description: Trigger holdoff fails (or When holdoff is turned on, waveform acquisition stops)
Test signal:
-SDG2042X, connected via BNC into 50 Ohm terminator
-Square wave, 1 Vpp
-Frequency sweep 10 kHz 100 kHz over 100 ms
Scope settings: (If the settings are more complex, the current oscilloscope setup.xml can be attached, Try to start from "Default" as much as possible)
-Start from Default settings
-Connect signal to CH1
-Edge trigger, positive edge, 3 ms holdoff
-Leave timebase at default 1 µ s/div (but 5, 10, 50 µ s/div also show the problem)
-Leave memory at default 10 MPt (but other settings also show the problem)
Observed behavior:
-Leave scope in RUN mode, wait up to a minute or so (but some of the problem occurrences within seconds)
-In AUTO trigger mode, the scope will stop rendering new waveforms entirely Trigger status shows READY, trigger frequency counter is still updated, waveform is frozen Operation restarts after any user interaction
-In NORMAL trigger mode, the error seeds puller, but occurrence events Before it does, I noticed sporadic "hickups", where the trigger status switches to "Arm" and the waveform is not updated for a few months of a second
What do you think? We can discuss it.
...
We should "allow" such partial reports and not reject posts which don't include fully reproducible steps.
...
Actually, I have an idea to split this thread into two threads, one is bugs+firmwares, and the other is wanted features (Current thread),
if this thread is too long, which may give people the illusion that there are many product problems.
Firstly, siglent is more concerned about bugs, and it is Siglent's obligation to modify them,
Then another wanted features thread(Current thread) can provide good ideas for all manufacturers, allowing everyone to speak freely and leverage their professional advantages.
I can see the benefits of having a more focused bugs-only thread. Besides avoiding a wrong perception of "too many bugs", it also makes sure that the real bugs get proper attention and are not lost in the noise.