Author Topic: Rigol DG1022 sends double pulse in burst mode!  (Read 3256 times)

0 Members and 1 Guest are viewing this topic.

Offline dsokollTopic starter

  • Contributor
  • Posts: 10
  • Country: us
Rigol DG1022 sends double pulse in burst mode!
« on: February 18, 2012, 08:35:51 pm »
So i needed a pulse with a width of 1ns, which my DG1022 can not do. So i decided to use the DG1002 as an external trigger to an HP 1900A which will get me close enough. During the 16 pulse test, my frequency counter showed we were getting 17 pulses. After play around and blaming it on the HP's age, we discovered the Rigol DG1022 being used as an external trigger was sending an extra trigger pulse. After the first pulse, it was sending a second pulse 1ms behind it followed by the remaining 15 100ms apart making the 10Hz rep rate. Anyone else seen this problem? Attached are photos using a 5 pulse burst as an example. The first looks to be 5 pulses...a closer look proves different.
 

Offline Thomas

  • Regular Contributor
  • *
  • Posts: 131
  • Country: no
Re: Rigol DG1022 sends double pulse in burst mode!
« Reply #1 on: February 19, 2012, 10:49:09 am »
Mine does the same thing when using Manual trigger.
Looks fine when using Internal or External trigger  ???

Not good  :(
 

Offline dsokollTopic starter

  • Contributor
  • Posts: 10
  • Country: us
Re: Rigol DG1022 sends double pulse in burst mode!
« Reply #2 on: February 21, 2012, 07:21:03 pm »
I notified Rigol Tech Support and they never responded. Very disappointed. I have a scope, DVM and power supply from them as well.
 

Offline Fender123

  • Newbie
  • Posts: 6
  • Country: mt
Re: Rigol DG1022 sends double pulse in burst mode!
« Reply #3 on: August 20, 2014, 08:28:59 pm »
I recently encountered the same problem with manual trigger of pulses or bursts - it only happens from the second manual trigger event onward. A single long pulse will have a leading glitch, a short fast burst will appear twice, and a long fast burst will be extended (by about 1.8ms).

Setting Burst->Delay to 2ms solved the problem for me in all cases.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf