Search found 21 matches

by gyro
Fri Dec 08, 2017 9:38 pm
Forum: DSO138
Topic: Triggering at 50ms per division and below
Replies: 33
Views: 51636

Re: Triggering at 50ms per division and below

Thanks very much JYE. Yes the LED and slow timebase are now working well for me too. A "Holdoff" indication (as you mentioned) would still be helpful, as it is very difficult to judge how soon triggering becomes available at the lower timebases. By the way, I also a support MNTech's 'Roll ...
by gyro
Tue Dec 05, 2017 8:53 pm
Forum: DSO138
Topic: Follow ups
Replies: 2
Views: 4715

Re: Follow ups

We really don't want to spend time to help counterfeiter to get sale. To solve this problem we will release a new model - DSO138mini - very soon. The existing DSO138 will be discontinued gradually. It would be rather nice if you finished correcting and debugging the "Triggering at 50ms per div...
by gyro
Sun Oct 01, 2017 8:44 pm
Forum: DSO138
Topic: Triggering at 50ms per division and below
Replies: 33
Views: 51636

Re: Triggering at 50ms per division and below

Thanks MNTech, glad it helped.

I hadn't checked - using the same filename is a problem, I hope JYE are keeping track their changes properly.

Nice tip on the mosfet.

I'll be interested to see what issues you find that I have missed, it's nice to have some company!
by gyro
Sun Oct 01, 2017 6:18 pm
Forum: DSO138
Topic: Triggering at 50ms per division and below
Replies: 33
Views: 51636

Re: Triggering at 50ms per division and below

Are you using the second version posted in this thread - a few posts ago (Sun 03 Sept)?

I had exactly the same problem with the buttons with the first one. JYE added the above one to fix it.
by gyro
Sat Sep 30, 2017 6:16 pm
Forum: DSO138
Topic: Triggering at 50ms per division and below
Replies: 33
Views: 51636

Re: Triggering at 50ms per division and below

The latest of the two test versions in this thread doesn't appear to crash (the first one did). On very slow timebases it can appear to freeze of Normal and Single trigger modes simply because it takes a long time in pre-trigger and post trigger. JYE still need to fix the trigger LED and implement t...
by gyro
Thu Sep 07, 2017 11:08 am
Forum: DSO138
Topic: Triggering at 50ms per division and below
Replies: 33
Views: 51636

Re: Triggering at 50ms per division and below

Thank you.

The "Holdoff" solution sounds good. I'm not sure if it would still be worth clearing the buffer (0V) and measurements to further indicate that a new run has started, just a thought.
by gyro
Sun Sep 03, 2017 4:36 pm
Forum: DSO138
Topic: Triggering at 50ms per division and below
Replies: 33
Views: 51636

Re: Triggering at 50ms per division and below

Thank you for the revised version, _much_ better. I can confirm that the button crash issue and the red measurements at fast timebase are fixed. Now that I am able to use it without crashing I see two issues: - At slow timebase settings it takes a long time before the unit will trigger (single trigg...
by gyro
Sat Sep 02, 2017 9:41 am
Forum: DSO138
Topic: Triggering at 50ms per division and below
Replies: 33
Views: 51636

Re: Triggering at 50ms per division and below

I've also noticed that it now takes several seconds for the trace to appear after the rest of the screen, even on fast timebase settings. I'm not sure if this is relevant to the above problem, but it is an observed difference in behaviour from the previous version. P.S. I did perform factory reset a...
by gyro
Fri Sep 01, 2017 11:39 am
Forum: DSO138
Topic: Triggering at 50ms per division and below
Replies: 33
Views: 51636

Re: Triggering at 50ms per division and below

Hi jye, Thanks very much for finding the time to make this release. Triggering now seems to work on slower timebase settings but I think you have introduced a bug... Repeated pressing or holding of buttons seems to crash the s/w. This can happen during selecting different settings and changing them,...
by gyro
Fri Jul 21, 2017 7:48 pm
Forum: DSO138
Topic: Triggering at 50ms per division and below
Replies: 33
Views: 51636

Re: Triggering at 50ms per division and below

Unfortunately it is a software limitation that we need JYE to fix, not hardware.