# Realtime HLA frame inspection when using Automation api

**URL:** <https://discuss.saleae.com/t/realtime-hla-frame-inspection-when-using-automation-api/2957>\
**Category:** Support\
**Created:** [July 9, 2024, 6:12pm UTC](https://discuss.saleae.com/t/realtime-hla-frame-inspection-when-using-automation-api/2957 "2024-07-09T18:12:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bjoneal](https://avatars.discourse-cdn.com/v4/letter/b/74df32/32.png) [@bjoneal](https://discuss.saleae.com/u/bjoneal)\
**Post date:** [July 9, 2024, 6:12pm UTC](https://discuss.saleae.com/t/realtime-hla-frame-inspection-when-using-automation-api/2957/1 "2024-07-09T18:12:21Z")

</div>

Hello, I’m currently attempted to use the Logic 2 Automation Interface to inspect data in real time (or near real time). I understand this is not supported out of the box, so I have attempted to use a HLA to stream data over a socket. When running a capture directly in Logic 2 I see the HLA performing as expected and data being processed in near realtime. However, when using the Automation API to start a capture it does not appear that the HLA is run until after the capture is stopped, at which point the entire session is then immediately processed by the HLA. Is this expected behavior? Is it possible to have an HLA process frames at the same frequency when using Automation to capture a session as happens when using Logic 2 directly?

When using Automation I’m currently performing 5 second timed captures.

---

<div class="post-metadata">

**Author:** ![timreyes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/timreyes/32/108_2.png) [@timreyes](https://discuss.saleae.com/u/timreyes)\
**Post date:** [July 11, 2024, 1:34am UTC](https://discuss.saleae.com/t/realtime-hla-frame-inspection-when-using-automation-api/2957/2 "2024-07-11T01:34:29Z")

</div>

@bjoneal Our Automation API unfortunately does not have the capability to add LLAs (C++ low level analyzers) or HLAs (Python high level analyzers) while a capture is ongoing. Because of this, your proposed solution would not be possible given the limitations of our Automation API.

Feel free to post your request to add this capability to our Automation API via our ideas site below. We’re unfortunately unable to work on this anytime soon due to other priority projects, but we’d love to start tracking user interest in this in the meantime before we commit it to the roadmap.  
[https://ideas.saleae.com/b/feature-requests/](https://ideas.saleae.com/b/feature-requests/)

As an alternative, one feature request we are currently tracking however is the ability to perform automation functions on pre-existing sessions. The link for this is below, and this may work in your use case as well.

> **[Automation API - Execute automation script on pre-existing session - Logic 2...](https://ideas.saleae.com/b/feature-requests/automation-api-start-capture-on-pre-existing-session/)**
>
> I'd like a way to trigger a 'start' command in the app through the API, without changing the session settings.
> 
> I often use the Saleae logic analyzer for interactively debugging a program. The original API was great for this because I could

Apologies we don’t have an immediate solution for you.