Sample rates <= 31250 are currently unsupported from the automation API


I am getting the following error when trying to set analog baudate to 32500Hz to the Automation API:

InvalidRequestError('Invalid supplied sample rate - sample rates <= 31250 are currently unsupported from the automation API

I need to use 32500Hz for the sampling rate of my Analog channels, as the next available sample rate is 625000 , which is too high for my use case, as I need capturing for long periods of time making my captures too large for my case. When will this be available using Automation API? Any workaround?


@albert.caba Sorry for all the issues with our Automation API! I’ll be reviewing this, as well as your other forum posts around automation, and I’ll follow up with you once we know what’s going on.

@albert.caba After reviewing your request, it looks like we have not yet implemented Automation API support for configuring sampling rate values of 31.25 kS/s or lower. I’m not sure at the moment why we left it out, but I’ll bring this up with the team here.

Hi @timreyes , thank you , please let me know once you have some feedback as this is an important issue for us, as it prevents us to use Saleae in production! Thanks

Hi @timreyes any update on this? Thanks!

@albert.caba We were discussing this particular feature fairly recently, and it’s a larger project than we initially thought — not straightforward to implement, but doable. The key difficulty is that the lower sampling rates (below 625 kS/s) are not officially supported by our device in hardware, but is instead downsampled in software. This poses a few challenges when incorporating it with our automation API. We’ve got this feature request internally documented and we have a plan to fix it - but sadly it won’t be right away due to other priorities at the moment.

In the meantime, I wanted to see if we can immediately address your concern below.

One alternative might be to save your captures in binary format rather than in .sal file format, by using the export_raw_data_binary() function below. The downside is that you won’t be able to open the binary file using our software, however, if you plan to analyze your capture via another method (perhaps via a script), this could be an option to save on hard disk space.

Hi Tim, thank you for your answer, unfortunately this solution does not work for us as we need to analyze the captures manually using Logic2.