Alex,
The trigger *is* producing a steady display, it can't trigger on what isn't there, your repetition rate is simply too low. 5 Hz ...
Thanks for the quick reply. That's what I was assuming.
Yesterday I tried to get a better result by adding waves from my veeery ooooold HP square wave generator trying to use those as a trigger source and 5hz was the value I was playing with and with that low frequency, yes You get flicker that way or the other.
Wrong tool IMO, a cheap and cheerful logic analyzer will do that job very well.
That actually was my first attempt. I got a Hantek 6022 USB scope with integrated logic analyzer, thinking that it would be enough for my entry level needs, but i was wrong.
the Oscilloscope software is either crashing or showing so much noise that it's hard to tell the difference between wave and noise.
But the true piece of crap is the logic analyzer software. The guy who made it should be sentenced to use it himself for the rest of his lifetime.
There is nothing You can set except printer settings - printing is highly important when analyzing data signals... No, sorry, You can do more. You can choose between blue style, black style, silver style and aqua.
The need for renaming channels seems to be completely overrated as well as the idea of matching colors to the used cables or upper and lower threasholds.
But for the price, I could live with that if only I could properly analyze my signals. Unfortunately You can only select
zoom all,
zoom out and
zoom in which perform zooming in steps. You can't select an area by rubberband and when You zoom in, the view jumps almost to the beginning of the measurement. However there are no scrollbars. You have to navigate by swiping.
To make it short, after literally swiping for 15 minutes in a view of 10µs devisions without ever getting to the first data portion, I gave up and returned the Scope.
Or if you have the time and resources, build a I2C monitor that gobbles the I2C data and tosses it out a UART to a PC.
Years ago I built one for another serial protocol and everyone used it after. Mostly because dedicated I2C/SPI sniffers are stupid expensive.
yes I guess it'l bee something like that. From the Tectronix I get enough information about the timings. So I should be able to write a small program with an arduino, that collects the data and writes it out every now and then.
Thanks