K |
Kevin |
1. Waiting for trigger.(Showing waveform in realtime like now. including pre/post capture after trigger.)
2. When trigger hit, capture/save/show.(save waveform with sequence number or current date, time.)
3. Go to #1 until stop.
It will enable to capture the last trigger for overnight testing.
I used to run overnight testing for the one happens very rarely.
The use case is that if it rarely and randomly crashes then it won't generate the next triggering condition. So, we can see the last moment of signals which caused the crash next morning.
But, with current trigger mode in Saleae, none of mode support for this situation.
I am not sure if Automation API can do it or not.
Anyway, my suggestion is how about to make it as one of regular mode rather than API.
Thanks,
-Kevin
Activity Newest / Oldest
Tim
Merged with: Auto-save data after trigger
Ben
Hi guys,
Been trying to catch a random and very rare issue on a circuit since early March and it finally occured once last Friday.
What I've been doing on my test bench every afternoon before returning home is to start the Logic software (using Logic Pro 16) so that if the problem occurs overnight, I will see it the next morning. After 2+ months doing this, finally, Friday the error occured while I was home and I was happy because I'd finally be able to see it Monday upon returning to work.
Of course, Murphy's law came into the picture and we were hit by a terrible storm Saturday afternoon which caused major power outages therefore my whole setup powered-off and I lost all my data so I now have to restart and wait (days? weeks? months?).
My suggestion to you is that since the analyzer will trigger on a certain event with x minutes of pre-trigger and post trigger, you guys should add an option in the trigger menu to so that when the post-trigger delay is met, let's say 10 seconds, all data from the pre-trigger start time to post-trigger stop time will be saved automatically to disk.
In my case, all data would have been saved (timestamped file) on Friday if that option would have been available.... that would have been total awesomeness. Thanks. Ben
Tim
Oh no... Murphy's Law in full effect! I'm so sorry to hear that... I completely agree about this. We're tracking another similar feature in another idea post. I'll go ahead and merge them together.
Tim
discuss.saleae.com/t/scripting-socket-api/108/13
"Just an idea for some basic built-in automation could be very useful in your cases (and also in mine) without the need for complex capture segmentation:
Save and repeat: if the trigger occurs, the software will finish the current capture (post-trigger capture and pre-trigger trim), then save the capture to pre-configured file (adding counter to avoid overwriting the last file), and start the capture again.
Restart after failure: if the capture is stopped by any other means than the user clicking the stop button (buffer overflow, timeout, USB error, system reboot), the software will save the current capture (if possible), and try it’s best to start the capture again (if USB error, try to reset the hardware, if everything fails, try to reboot the system).
This would allow running the captures for weeks and months without the need for a human checking every few hours."
Tim
(#68070)
"What I want to know is the following :
* Is it possible to develop a custom analyzer that can catch at the same time SPI data and GPIO states ?
* Is it possible to start the capture and analyze on the fly the data with the custom script, reject some, get only what we are interested in, and write a file on harddrive to store results ?"
---
This use case could be solved In combination with the idea post below:
ideas.saleae.com/b/feature-requests/more-complex-triggering/
Tim
discuss.saleae.com/t/utilities-for-sal-files/725/16
"Auto-Record: bring the device into a mode where it auto-triggers and saves (block by block)"
Tim
(#67175)
"I am working with Saleae to capture some data from my product, I would like to retrig the signal to capture the communication during a day. But the mode trig in Saleae is only single and I don't know how to set the retrig mode mode.
Could you help me to configure the Saleae ?
It is nice to have that I can save the capture in the file on each trigger."
Kevin
Oh, I meant I wish to have above new feature from Saleae. As you mentioned, Saleae does not have this trigger mode. So, I am suggesting to have this trigger mode. I also could not capture signals. instead, I used normal mode with regular scope.