I'm having the same problems as Ben. Triggers don't work apart from in AUTO mode. NORM and SIGN/SING mostly don't display the triggered signal at all.
Sometimes in NORM mode, when the R/S button is pressed and HOLD is displayed on the screen, I can see the waveform moving.
Sometimes it does trigger, but only after HOLDing, and possibly only after holding while the signal level is low if you're looking for a rising edge. It appears to work better at longer time bases.
SIGN mode doesn't work at all for me, unless I press the R/S button and immediately get a trigger. Could it be that these are triggering further along the horizontal axis and are therefore out of view?
I'm using firmware version 2.21. To test SIGN and NORM modes I was manually triggering the signal level rather than putting a waveform through it.
Hope that helps, and I look forward to the next update!
...please feedback the issue that in your use.
- I see no improvement related to triggers. As for now - triggers are not working whatsoever (basic waveform synchronization only).
- A few pixels on the vertcal time window axis will flicker and/or become partially transparent (upper right/lower left).
- After using the DSO for a while (trying different options with active input) a few pixels will get stuck and a restart is needed to clear.
- The battery level indicator is unstable (flickering back and forth) at some levels and there appears to be a very short time for the final 70%.
- I don't like the transparency - it just makes the signal more difficult to view.
- Frequency calculation is unreliable (looking at AC mains frequency on a near perfect square wave jumps a full Hz between readings).
- When frequency is displayed, the "H" in "Hz" fickers an so does the "m" in delta time "mS" vertically below.
- The abbreviation "SIGN" doesn't make sense to me (do you mean "SINGle"?)
Why not work on fixing basic issues (triggers in particular) rather than "polishing" the user interface?