1.22 trigger bug chart

yclee126

The firmware is buggy, but still there is no other choice yet..
Instead of just waiting for eternally, I thought this chart would be useful for (at least)avoiding trigger bugs.

I measured this with square wave signal, but as it turns out the bug depends on idling trigger time.(the time it waits for the next trigger signal)
The chart is idling trigger time versus time scale.
I've tried to scroll the screen while in hold state, but it only returned wrong waveform.

Trigger position : Second leftmost
(Moving the trigger position to the right causes more defect combos inward the chart)
"defect" means the waveform is distorted on norm trigger screen or disappears on single trigger screen.
x = norm, single defect
* = norm defect

time

freq

100ns

200ns

500ns

1us

2us

5us

10us

20us

50us

100us

200us

500us

1ms

2ms

5ms

10ms

20ms

50ms

100ms

200ms

500ms

1s

125ns

8MHz

x

x

x

x

x

166.7ns

6MHz

x

x

x

x

x

250ns

4MHz

x

x

x

x

x

500ns

2MHz

x

x

x

x

x

1us

1MHz

x

x

x

x

x

2us

500kHz

x

x

x

x

x

5us

200kHz

x

x

10us

100kHz

x

x

20us

50kHz

x

x

50us

20kHz

x

100us

10kHz

x

x

x

200us

5kHz

x

x

x

x

500us

2kHz

x

x

x

x

x

1ms

1kHz

x

x

x

x

x

x

2ms

500Hz

x

x

x

x

x

x

x

5ms

200Hz

x

x

x

x

x

x

x

x

10ms

100Hz

x

x

x

x

x

x

x

x

x

20ms

50Hz

x

x

x

x

x

x

x

x

x

x

50ms

20Hz

x

x

x

x

x

x

x

x

x

x

x

100ms

10Hz

x

x

x

x

x

x

x

x

x

x

x

x

*

1s

1Hz

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

*

*

*

*

*

inf.s

1Pulse

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

Note that those large time scales on the single pulse row take some idle time to take defect, but it really happens.
That means within short time of idling trigger time, the chance it will get triggered increases.
My technique here to get it triggered is to push K1 first from the hold state, then quickly trigger the signal source with the other hand.


haha..

caykroyd

yclee126,

I'm not sure I understand your chart.  Are you providing a single shot pulse using single shot trigger? Based on your chart is it showing that 8MHz-500kHz pulses trigger properly with time scale of 100ns to 20ms.  However, I see the exact opposite.  I only get a single mode trigger to work with time scale > 20ms.

And if you are saying that you can avoid trigger bug by quickly pushing K1 and then quickly sending signal, I agree I can get that to work, too.  But my real applications don't have an option to define when I send my signal.

I hope we don't have to wait eternally for the fix!!

Note to miniDSO.... Can you put this bug as a very high priority?  It really is a useless tool until the trigger works.

yclee126

caykroyd 发表于 2019-8-7 22:38
yclee126,

I'm not sure I understand your chart.  Are you providing a single shot pulse using single ...

I did this with square wave signal and normal mode rising edge trigger. Only the bottom row is a single pulse.(single rising edge to be exact)
The trigger bug depends on idling trigger time, so maybe that's why you got it work on those slow time base with more idling trigger time "tolerance".

Yes indeed the tecnique here is useless to trigger on irregular pulse, but it has some applications like microcontroller debugging.
It's a temporary solution to avoid it, they shoud fix it asap seriously.

And I just found this chart is misleading thanks to your reply!
I'll add cycle time next to those frequency numbers.

minidso

caykroyd 发表于 2019-8-7 22:38
yclee126,

I'm not sure I understand your chart.  Are you providing a single shot pulse using single ...

Thank you!
We are work on the new firmware, And will fix this bug.

Kabron

minidso posted on 2019-8-8 09:16
Thank you!
We are work on the new firmware, And will fix this bug.

You spent almost half a year!
When the result will be?The device soon will be morally expired

davidos

Any updates on the fixed version?

minidso

davidos 发表于 2020-3-4 04:02
Any updates on the fixed version?

we have made more than 90% progress in bug repair of FPGA. The new upgrade firmware will now be released after the A / D has been repaired. It is expected to be within one month.

minidso

Already fix the bug, Please download APP 2.14 here:
http://www.minidso.com/forum.php?mod=viewthread&tid=3357