EEVblog Electronics Community Forum
Products => Test Equipment => Topic started by: eyal on April 11, 2018, 05:54:44 am
-
This did not happen to me before (for a few years) so it may be some setting I accidentally changed.
Or it can be a problem with the DSO.
I am running a trace where the device cycles every 6 seconds. A proper trace looks like this:
(https://www.eevblog.com/forum/testgear/rigol-ds1074z-trigger-issue/?action=dlattach;attach=411386)
However, it often fails to trigger, as in here
(https://www.eevblog.com/forum/testgear/rigol-ds1074z-trigger-issue/?action=dlattach;attach=411384)
To be sure, I changed the trigger level to 60mA but I still often get
(https://www.eevblog.com/forum/testgear/rigol-ds1074z-trigger-issue/?action=dlattach;attach=411382)
Note how it seems to trigger on the end of the waveform, and it missed the leading edge.
I even introduced a hold-off of 10ms to ensure the end of the wave does not trigger but it did not help.
Any help appreciated, and it is may very well be a stupid thing I am doing - just tell me anyway.
BTW, the preview does not show the images, I hope they will show once it is posted...
Regards
-
How is your trigger mode set Normal or Auto?
If in Auto, considering your signal cycles each 6 seconds and the scale of your scope is now set to 6 seconds it means it will auto-trigger every 6 seconds, once triggered it will not re-trigger on the input signal.
Try Normal or Single triggering mode and it should "fix" your problem.
-
As the images show the mode is "Sweep: Normal". Naturally, in Auto I would not expect alignment with a trigger level.
cheers
-
It might be worth limiting the B/W to 20 M as a fast spike might have an impact. You may of course already have that selected.
-
Yes, I have 20MHz BW limit.
-
Is it the same behaviour on the other channels 1-3?
-
Tried ch3 with same results.
ch2 same...
-
Not surprising, the trigger circuitry is separate and shared by all channels.
If it used to work then there must be a setting you're missing somewhere.
Try pressing "Auto".
If that fails you could do a reset of all parameters and see if that fixes it.
Press the magic button during power up:
(https://www.jackenhack.com/wp-content/uploads/2015/09/rigol_ds1054z_reset-400x300.jpg)
-
First time I hear about a "magic button" reset. I will keep it as a last resort...
-
I still get unusual triggering. I now tried:
- set "Utility - Settings - Power Set" to "Default". This restores system defaults on restart.
- installed the latest firmware.
- done a calibration pass.
- finally, done a factory reset (magic button).
I now seem to not get random triggers, but I do get some cases where the trigger fires on the trailing edge of the trace.
Maybe it is time for bed to sleep on it.
-
10mS holdoff for an over 600mS wide pulse? I wouldn't expect that to have an effect for the pulse you show. Even the small dip at the beginning of the pulse looks to be 100mS after the start of the pulse.
-
I still get unusual triggering. I now tried:
- set "Utility - Settings - Power Set" to "Default". This restores system defaults on restart.
- installed the latest firmware.
- done a calibration pass.
- finally, done a factory reset (magic button).
I now seem to not get random triggers, but I do get some cases where the trigger fires on the trailing edge of the trace.
Maybe it is time for bed to sleep on it.
10mS holdoff for an over 600mS wide pulse? I wouldn't expect that to have an effect for the pulse you show. Even the small dip at the beginning of the pulse looks to be 100mS after the start of the pulse.
This ^^. Try setting the Trigger Holdoff to something greater than the total pulse width, like 700 ms. This should prevent triggering on the TE of the trace. Also, even the rising edges of this pulse aren't all that fast. I'd also recommend boosting the sample rate (Acquire>Mem Depth up to 24M points) if possible.
-
oops, I mis-read holdoff as delay after the trigger condition passes. I now set it to 4s (the cycle varies between 550mms and 3.5s).
I have now seen more cases where a trace has the trigger in a random place, e.g.
(https://www.eevblog.com/forum/testgear/rigol-ds1074z-trigger-issue/?action=dlattach;attach=411380)
And also still get some cases where the trigger is at the training edge. Holdoff is set to 4s (longer than the longest trace) so this should not happen.
-
I have now seen more cases where a trace has the trigger in a random place, e.g.
Is it always in the wrong place or just every now and again?
Does it do that when you do a single capture? What happens if you change the horizontal timebase?
You're not giving many clues.
-
How about the possibility that there is a very fast glitch that you just can't see at 200 ms/div? It could be that the scope is doing just fine.
Maybe change the time/div to see what is actually triggering the scope.
-
How about the possibility that there is a very fast glitch that you just can't see at 200 ms/div? It could be that the scope is doing just fine.
That wouldn't explain this:
(https://www.eevblog.com/forum/testgear/rigol-ds1074z-trigger-issue/?action=dlattach;attach=411382)
(although a tiny spike in combination with a weird trigger holdoff could explain it)
-
Enable Peak Detect acquisition mode... That will show you fast spikes....
It may explain funny triggering
There is also Trigger noise reject menu, in case there are fast spikes present...
-
Trigger off the falling edge, ...and noise reject.