Author Topic: Rigol MSO4000 triggering/holdoff question  (Read 996 times)

0 Members and 1 Guest are viewing this topic.

Offline omegahacker

  • Newbie
  • Posts: 1
  • Country: us
Rigol MSO4000 triggering/holdoff question
« on: May 02, 2017, 07:07:41 pm »
I just got a new Rigol MSO4024 for work, and so far it's not really working all that great.  Immediately I ran into a bug where the serial decode (CAN) would just spontaneously drop off the screen while scrolling horizontally, and not come back without retriggering.

But the biggest bummer for me right now is that it's not showing the most recent trigger after holdoff.  Specifically, the signal I'm looking at right now consists of a low pulse for ~2mSec caused by the reset of the generating microcontroller, then ~160mSec later a CAN packet being transmitted.  The scope is in Normal mode with the min 100nS holdoff.

On my previous scope (Keysight MSOX2014), it would trigger on the boot pulse, then trigger on the CAN leading edge, and stop on the CAN leading edge.  Alternately, if I had the timebase zoomed in enough, it would actually trigger several times and show me the last one (the retrigger window seemed to be the width of the screen).

On the Rigol unit, all it shows me is the boot pulse, unless I go through many extra steps to either do segmented record and find the right edge, or set up Nth edge which only works until it doesn't.  However, if I hit the reset button on the MCU a couple times ~250mSec apart, I can see the scope showing me the 1st boot pulse, then the 2nd, then *usually* stopping at the 2nd-boot CAN packet.

Am I missing anything here?  I've been through all the options, and nothing seems conceptually different from the Keysight scope (or even my really old Tek TDS224), but the Rigol just isn't matching behavior with what I expect (and need).


Offline Teuobk

  • Contributor
  • Posts: 26
  • Country: us
Re: Rigol MSO4000 triggering/holdoff question
« Reply #1 on: May 03, 2017, 01:36:06 am »
Do you have your memory depth set to "auto" (or at least a relatively low value)? If not, it's possible the scope isn't triggering on the CAN leading edge because it's still recording the waveform from the trigger on the boot pulse. Try changing the memory depth to "auto" and then zooming in so the span is well under 160 ms.

Online jjoonathan

  • Frequent Contributor
  • **
  • Posts: 542
  • Country: us
Re: Rigol MSO4000 triggering/holdoff question
« Reply #2 on: May 03, 2017, 05:00:15 am »

My Rigol DS4014 has 30ms of dead time in a similar, simulated setup. Not great, but I really don't think that should be a show-stopper for your particular use case. Is your scope behaving differently from mine? Or do I just not understand the problem?

Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo