Bus display and continuous trigger

[joe_garrison]

Hi Bear, thanks for the help!

@Bear

The first one is Bus display.
I often have to look at state machine and there is actually no convenient way of displaying them.
Maybe it could be interesting to split the signals that are display vs the one that are selected for capture.
So that you can select what you want to display and display them as stand alone signal or bus or even protocol decoder.

Agreed. Both ‘protocol-only channel’ and ‘bus view’ are on the roadmap. This probably will change but they currently are on the board for Q1 2020.

@Bear

The second one is continuous trigger.
In one use case I have an heartbeat every minute and I’m interested by the last one that happen when my code crash. So instead of capturing the first heartbeat pulse with a One-time trigger, i will need a continuous trigger to re-trigger on each an so getting the last occurrence of it.
Bonus point if I can configure pre-trigger buffer duration and post-trigger duration independently.

Do you mean that you want to trigger on, and save a capture for every single heartbeat?

What do you think about recording in “Looping” mode - where the application continually holds on to the most recent N GB of data, and allows you to stop at any time, such as after you see a crash? Right now the Alpha software mostly works for this, although it’s hard-wired for a 2GB limit.

Thanks Bear!