Ideas Test

27 VOTE

More triggers

More triggering options. Let's say I want to decode on a I2C protocol. A very handy trigger will be by Address or Address & Data (like most MSO have). Let's say I have more than one I2C devices on bus, and I'm interested to see only one device (address) communication, writing or reading to a particular register or command. I should expect to see only that particular event captured. Look at the most real time logic analyzers and try to implement those triggers, cause without them we will end up searching the capture, and be limited by duration of that capture.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Aug 2 2018
  • Planned
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    02 Aug 17:05

    Also add a feature like trace before, trace around to the current "trace after" feature.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    02 Aug 17:05

    Or simpler triggers, trigger on pulse duration

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    02 Aug 17:05

    Yes, Triggering on and address, block header or even more complex Head-Tail block.