I love the trigger functionality you added!
Is there going to be:
- stop / single trigger?
- force trigger?
- a display for time since last trigger event? Maybe also an equivalent of the oscilloscope LED that blinks upon trigger event?
- complex trigger conditions
I think that connecting several channels to a single channel’s trigger event is a must. It’s much more useful than the ability to trigger different channels independently. If I had to choose, I would prefer a single trigger module for all channels (allows for more advance trigger patterns too), rather than one per channel.
Something that you have the opportunity to do, which oscilloscopes typically don’t do, is listing all trigger events in a recording. On a scope you would try to trigger on an interesting event, then watch the last one of these.
Here you can go on with the recording, mark all of them on the display, and let the user browse through hundreds of events of this type, they’re all recorded anyway. Does that make sense? Wouldn’t it be awesome?