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.