| Products > Test Equipment |
| GW Instek MDO-2302A delayed trigger bug? |
| << < (2/2) |
| evgus:
--- Quote from: 2N3055 on March 08, 2021, 09:10:53 am --- You shouldn't have such a large holdoff value. Try setting holdoff to time just bigger than pulse burst , say 12-15 usec. With pulse trigger you use you shouldn't need holdoff at all. Also you use rising pulse as trigger start, you should use falling edge, so it's not triggering on first falling pulse and count from there but from somewhere else. I don't have that scope, but it seems to me that this particular trigger works a bit different than you''re trying to use it. --- End quote --- Thanks for your reply! I've tried to vary holdoff time and even set it to minimum value (effectivly disable it at all). Nothing have changed. Setting edge to falling also doesen't help - trigger still happens randomly if "delay count" set to 2. I completely agree that "this particular trigger works a bit different than you''re trying to use it" :) This is definitly not the first scope throughout my career, but this is the first time I put so much effort (in vain so far) trying to make such simple function (trigger on N-th pulse in packet) work :-// |
| 2N3055:
--- Quote from: evgus on March 08, 2021, 09:18:00 pm --- --- Quote from: 2N3055 on March 08, 2021, 09:10:53 am --- You shouldn't have such a large holdoff value. Try setting holdoff to time just bigger than pulse burst , say 12-15 usec. With pulse trigger you use you shouldn't need holdoff at all. Also you use rising pulse as trigger start, you should use falling edge, so it's not triggering on first falling pulse and count from there but from somewhere else. I don't have that scope, but it seems to me that this particular trigger works a bit different than you''re trying to use it. --- End quote --- Thanks for your reply! I've tried to vary holdoff time and even set it to minimum value (effectivly disable it at all). Nothing have changed. Setting edge to falling also doesen't help - trigger still happens randomly if "delay count" set to 2. I completely agree that "this particular trigger works a bit different than you''re trying to use it" :) This is definitly not the first scope throughout my career, but this is the first time I put so much effort (in vain so far) trying to make such simple function (trigger on N-th pulse in packet) work :-// --- End quote --- I tried to look into manual, but it is not well written. You should definitely write mail to Instek support. Even if it's not a bug per se, it is really not explained well how it works.. Regards, |
| armandine2:
I'm keen to recreate this test for my GW Instek MDO-2302A will need to recreate OP's original pulse packet on my Keysight EDU33212A arbitrary waveform gen evgus was explicit about how he used the scope - but I guess for the arb the assumption is this is a simple waveform to recreate - I think I could do something like it with a square wave high 3.3V low 0V say 60% duty cycle and 1/1.4 us frequency in a 8 cycle 1 second burst ; not as pulse though? [Ed.1 may be: offset +3.3V, high level 0V, and low -3.3V] :palm: |
| armandine2:
I didn't manage to get a dc offset in burst with my Keysight EDU waveform generator - but I can (with no dc offset), nonetheless confirm that for my GW Instek MDO-2302A: a one second burst of eight 3.3V, 1.4us, and 60% duty cycle pulses, I only caught on event delays 1, 3, and 7 :palm: so if you do the same thing you will likely get the same result - which is kinda obvious. Whether this really is a bug - not exactly sure. :-BROKE |
| armandine2:
Bumped up, in case some further light can be shown on the problem. |
| Navigation |
| Message Index |
| Previous page |