Ideas Test

57 VOTE

Add a Rolling Capture mode

Add a capture mode that keeps the last "X" samples or "X" seconds worth of data, and discards any data before this period.

I am watching an I2C line, and if everything goes well, there will be traffic every 1 second. I am interested in this traffic immediately before and after my device crashes, at which point no more data is communicated on the I2C lines. In order to catch this, I need to constantly be capturing, until I run out of memory, and restart the capture. There is no good way to trigger or script this using the socket API, but I'm open to suggestions...

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jun 26 2018
  • Planned
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 26, 2018 19:08

    All I can say is yes, please! I'm currently trying to debug a very intermittent problem possibly with I2C. Without this feature I can't really track it down as it takes multiple hours to happen. Something along the lines of trigger after X.XXX secs of no-start or no-data condition would be a huge help!

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 26, 2018 19:08

    I agree fully with robgee1964. I need to run a test over several days to catch a sporadic error, and this would work only with a circular buffer...

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 26, 2018 19:08

    Totally agree with this, what's needed is a circular buffer that stores whatever pre or post trigger samples have been specified, this is how oscilloscopes and many other logic analysers work. Currently, if you are capturing whilst waiting for an infrequent error trigger, it *looks* as though it just gathers all samples, albeit to some temporary buffer.
    To be honest I see the lack of this feature as a significant limitation in otherwise very decent product.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 26, 2018 19:08

    This would be very useful for overnight tests. Let the system run and acquire as many triggered events as there are instead of only one. The triggered event could be saved into a tab and/or to the disk before restarting the trigger.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 26, 2018 19:08

    Gunther,
    You might be able to do that right now with the socket API: https://github.com/saleae/SaleaeSocketApi
    You can automate the start -> save to disk -> restart operation. If you have more questions about it, please contact support.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 26, 2018 19:08

    Sounds similar to what I could use right now. Additionally I would like the option to save each capture to file with a simple index number appended to the filename. Wait trigger->triggered->capture data->save to disk-> rearm trigger.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 26, 2018 19:08

    Got a really tough problem to track here that requires this particular function. It's the only way to find problems that happen once in awhile...

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 26, 2018 19:08

    For me it would be useful to have all the communication on I2C or SPI up to the Crash. With the oscilloscope, to measure that, I use the normal Trigger mode. Same time I sniff the Serial bus (only the transferred data are saved). With this two tools I'm sure to have the capture on the last sequence and to memories the flow up to the Crash. It would be fine to have both on the Saleae tool.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 26, 2018 19:08

    This would be very useful for me too. Being able to trigger multiple captures and only record X amount of information before and Y amount of information after would make my testing easy.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 26, 2018 19:08

    I would like the "max amount of memory" idea.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 26, 2018 19:08

    Or set a maximum amount of memory to use and handle it as a circular buffer. I would use this 'mode' more than any other.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 26, 2018 19:08

    I'd like to see this feature, where x amount of data is captured and capturing stops on a trigger event