Voters 1
1
Automation API - Set a timeout when looking for trigger
- Open
- Subscribe
 |
Tim |
(Original request in ticket 77203) Implement a way to call wait() with a timeout, or set a timeout trigger in addition to the digital trigger.
That way, a trigger-mode capture can stop if a certain amount of time has passed by.
Workaround (Untested): Call the stop() function from within a separate timer thread. Perhaps something like shown in the image attached.
Activity Newest / Oldest
Tim
discuss.saleae.com/t/check-if-trigger-happened-without-wait/3011/3
"I’ll support/repeat the request for an ‘abort’ method, what would be nice if ‘wait()’ could accept a ‘timeout=Xms’ parameter and then return a success/failure value - maybe just an empty capture object.
I guess it is (also) possible for user interaction on the GUI to cancel a capture, but that’s not helpful when you are attempting automation of 1000’s of cycles.
I recently had an overnight run stall waiting for a trigger…"
Tim
discuss.saleae.com/t/detect-saleae-run-state-for-failed-trigger/2718
"Is there a way via the API to detect when the Saleae is still capturing data/waiting for trigger?
I’ve been using Capture.wait() to detect when a measurement has finished without any issue so far, but have come across an instance where due to a DUT failure, a trigger never occurs and so the Saleae just runs and runs whilst my software waits potentially infinitely for a return from the method."
Tim
github.com/saleae/logic2-automation/issues/19
"1. Add a facultative max_wait_seconds argument to the wait() function to set a max wait time, after which the capture would be stopped
2. Add a method to query for the capture status (is it still running or has it completed)"