Initial thoughts

[SparkyNZ]

I'm quite impressed with this overall. I have used Salae Logic quite a bit in the past but what's always put me off is of course the 16 channel limitation.

What I feel is missing is the support of a clock signal. Right now I have a slow-stepping 6502 system and I only get to see 1 transition when I use the pattern trigger. Because the fixed sampling frequency is so high, I see nothing else. Will you be adding support for a clock signal in the future?

The only other thing for me is the need for a protocol analyser that would show an 16-bit address and 8-bit data bus as hex. I get the feeling I could write a custom one (I am more a software dev than an electronics guru anyway) but I wouldn't go down that path without the support of a clock signal.

[gusmanb]

Sorry, what do you mean with "fixed sampling frequency"? The frequency is configurable from 3Khz~ to 100Mhz (and up to 400Mhz in V6).

In any case, you can emulate the clock behavior with the burst mode, configure an edge trigger, set the post-capture to 2-4 samples (base it on your real clock), enable the burst mode and that's it, you get the same behavior as having a clock signal.

Regarding protocols, in V6.0 you will have every analyzer from Sigrok and you could even write your own ones in Python.

Cheers.

[gusmanb]

Hi.

The frequency on that version is correct, my bad, I missed one zero, the minimum is around 30Khz, but in the V6.0 it can go down up to 3Khz~ with the non-turbo version.

Regarding the burst, are you sure that not all samples are captured? That version does not show the total ammount computed with the bursts, check if the end of the capture reaches to 4608 samples. If your clock is so slow then is possible that the trigger gets rearmed and detects immediatelly the trigger condition again and continues the capture.

Try this: download the V6.0 version from here and update the firmware to the non-turbo one. You will be able to set now the frequency to 3103 samples if I recall it right. Then configure the presamples to 10, postsamples to 3200, the burst count to 20, enable the burst mode and the burst measure. With that it will capture the full "ON" of the clock and a bit of the off, it will stop and on the next ON it will trigger again. Also, it will have a marker telling you how much time passed since it re-triggered each burst (you will have a marker atop the sample marker bar).

[SparkyNZ]

Thanks again for the quick response. I just ducked out of my job to give this a try :-) Just having a few issues setting up the capture. I couldn't set the Frequency to 3,000 - it changes it to 31,000 but I managed to get 3,100 to stay there. Only snag now is that I'm being told "Total samples cannot exceed 32768".

[gusmanb]

Well, you are telling the device to capture 10 + (3,200 * 20), that's 64,010 samples, so it's more than 32,768... (my bad, when you told me what you wanted to capture didn't noticed how many channels you were using, you are using the 24 channel mode so the max samples is 128k / 4, you can check the limits of your device if you push the "i" near the device name)😄

Reduce the burst count to 10 or try to use one less channel and use only the first 16, that will place the device in 16 channel mode.

Cheers.

[SparkyNZ]

Yay! That seems to work. Its a shame we couldn't lower the sample frequency even more so I could get more total samples. If I turn my clock frequency up then I get loads of data (which is what we'd expect on "real" computer system :-) ) Is it not possible to allow a really low sampling frequency perhaps in a later version? Something silly like 10Hz would do the trick.

The only other observation I have is that on my 4k monitor I'm having to use the entire screen height to see the 24 channels. It would be great to be able to alter the heights of each channel row - either by dragging (more effort) or by having a setting somewhere to set the size as "half, quarter, eighth or whatever"... 1/x would be good - and you'd have to watch out for some silly user putting in a 0 ;-)

[SparkyNZ]

I just reloaded the saved .lac file and had an exception too. Probably something you're already aware of. Let me know you want a copy of the .lac file or if you'd like me to create a separate issue or whatever. I know v6 is still work in progress so no worries from me - just FYI: