9
Read Measurement (and Extensions) via Automation API
- Open
- Subscribe
|
L |
Lane |
It would be very useful to be able to access common measurement (1.x) and measurement extension (2.x) parameters via the socket API. File I/O is a bottleneck and it would be great to avoid writing then reading and post-processing data for simple things like peak-to-peak or dBV analog measurement (extension for dBV conversion via the flexible python extension capabilities in 2.x).
Activity Newest / Oldest
Tim
(#87397)
"What I would like to do is to implement a measurement on an analog channel using an extension for Logic.
I saw the “add_high_level_analyzer” API, but I think it can handle only the “HighLevelAnalyzer” extension types. It seems that there isn’t an equivalent API for “AnalogMeasurer” or “DigitalMeasurer” extension types.
What I really would like to do is to setup a Vrms and clock frequency measurement using Automation API."
Tim
discuss.saleae.com/t/create-and-export-analog-measurements/2371
"Currently I create the analog measurements manually using Ctrl-G but I would like to do this automated.
Either based on some threshold (i.e. >100 mV) or based on a digital channel (maybe with chopping ~5µsec on start and end of that pulse).
I did not find any extensions or built in options to do that.
Is there some mechanism available to support that?"
Tim
(#81637)
"I want to mesure the duty cycle in a python script (automation). I can capture a trace but how can I use the measure functions. There is a class measure, but I can not find the python file"
Tim
(#81523)
"Hi, How can I measure the delta time between two signals using automation IP
I can not find any documentation regarding power sequencingmeasurment using autmation IP
I can do it manually on the software by using markers pair"
Tim
(#80172)
"I would like to capture the signals and check their frequencies via Saleae Automation APIs (Python)
By following the Python Automation API documentation, I was able to do a basic capture from the example code given, but inorder for me to check the frequency of a signal post capturing of a signal is what I am trying to achieve."
Tim
(#79703)
"Hi, a feature request: ability to name the channels, and to add notes. Adding autonomous measurements would also be great, but I assume that's a lot more complex than just adding the ability to name a channel.
This is super helpful software though. Makes integrating with a larger test setup much more manageable."
Tim
discuss.saleae.com/t/advice-to-create-a-test-system-with-logic-pro/2159
"I’m wondering what is the best way to count edges/periods from Python. Is it possible to do with the Automation Script only or I should be using the Automation Script + a custom Analyzer that would count edges+time?"
Tim
github.com/saleae/logic2-automation/issues/15
"Hi there.
I'd like to see an API where I can get data via a measurement extension, not just an HLA."
Michael Leonard
Hi Lane, I have created a High Level analyzer which opens a socket and streams data out (and accepts data) containing AnalyzerFrames.
I think the AnalyzerFrame and Measurements API are different so this might have to be done as a separate extension, but perhaps it would be possible to extend to cover measurements as well?
github.com/LeonardMH/SaleaeSocketTransportHLA
Michael
Hi Michael,
thank you very much for sharing, I tried it out and it looks really pretty good! And opens additional options!
I consider also to feed the data toward a Server with REST API, but that would have needed to import the "request" package, what is not in standard Saleae - Python packages.
The import via the workaround (sys-path, etc) failed, due to the further dependency on urllib3, that uses some special init steps, which are not covered by the Saleae package handling.
I will then retry with plain socket package, since you provided such an excellent example. :-)
Best Regards
Michael
Tim
Thanks for posting this! I added a comment for you in our idea post for automation:
ideas.saleae.com/b/feature-requests/application-api/
Though, I didn't merge your idea entirely since it's technically not the same request, but instead, a feature add-on to automation.
Lane
Thanks Tim! I did not post it as a comment in the 2.x API thread as I would be happy if the functionality were available for 1.x--no need to wait for 2.x. Of course, extensions need to wait for 2.x (unless these are getting added to 1.x).
Tim
We would no longer extend functionality for the 1.x version. Instead, all updates related to automation would be specifically for the 2.x app.
Lane
I will need to wait for the 2.x API then. I will follow the thread on that. Any idea when that will be? I didn't see a projected release date. Please point me to this as I missed it. Thanks!
Tim
We unfortunately don't have a release date to share right now. We'll be sure to update the idea post for it as soon as we commit to one.