Bug 1845 - Option to stop acquisition with a NEGATIVE trigger (like a 'watchdog')
Summary: Option to stop acquisition with a NEGATIVE trigger (like a 'watchdog')
Status: CONFIRMED
Alias: None
Product: PulseView
Classification: Unclassified
Component: Acquisition (show other bugs)
Version: unreleased development snapshot
Hardware: All All
: Normal normal
Target Milestone: ---
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-04-28 13:00 CEST by Martyn Hill
Modified: 2023-04-28 13:00 CEST (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martyn Hill 2023-04-28 13:00:55 CEST 
I use Pulseview on Windows, mostly for troubleshooting/analysing digital streams of my own hardware/microcontroller projects.

One feature I miss is the ability to detect when the signal appears to cease changing, and to then review the signal trace in the period leading up to 'lost' signal.

A bit like a 'watchdog' trigger event.

It would require to specify an acceptable 'quiet' period before the watchdog is triggered.

Ideally, it would be in combination with/following a normal positive trigger event such that, once an acquisition is started via a traditional trigger event, any subsequent 'quiet' period is detected causing the acquisition to then stop.

PV is an excellent tool and has proven critical in troubleshooting my own hardware development over the last few years.