# Can an HLA determine the LLA type its working with? **URL:** \ **Category:** Extensions\ **Created:** [March 27, 2022, 10:18pm UTC](https://discuss.saleae.com/t/can-an-hla-determine-the-lla-type-its-working-with/1517 "2022-03-27T22:18:34Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![P.Jaquiery](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/p.jaquiery/32/289_2.png) [@P.Jaquiery](https://discuss.saleae.com/u/P.Jaquiery)\ **Post date:** [March 27, 2022, 10:18pm UTC](https://discuss.saleae.com/t/can-an-hla-determine-the-lla-type-its-working-with/1517/1 "2022-03-27T22:18:35Z")
I have an HLA I’d like to be able to work with various LLAs. I need to be able to decode frames based on the LLA type - a I2C “address” is different than an async serial “address”. So, can the HLA determine what type of LLA it’s being used with and perhaps even what options may have been selected for the LLA? ---
**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:** [March 29, 2022, 1:07am UTC](https://discuss.saleae.com/t/can-an-hla-determine-the-lla-type-its-working-with/1517/2 "2022-03-29T01:07:36Z")
Hmm… you have a good point given that both cases are designated as an “address.” In this specific example, Async Serial addresses are of “bool” type while I2C addresses are of “bytes” type, so you could take action depending on the address type. > **[Async Serial - Frame Format](https://support.saleae.com/extensions/analyzer-frame-types/serial-analyzer)** > **[I2C - Frame Format](https://support.saleae.com/extensions/analyzer-frame-types/i2c-analyzer)** It would differ on a case by case basis though, and this is sort of a messy way of checking this. I’ll double check this with the software team to see if there’s a cleaner way. ---
**Author:** ![P.Jaquiery](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/p.jaquiery/32/289_2.png) [@P.Jaquiery](https://discuss.saleae.com/u/P.Jaquiery)\ **Post date:** [March 29, 2022, 1:15am UTC](https://discuss.saleae.com/t/can-an-hla-determine-the-lla-type-its-working-with/1517/3 "2022-03-29T01:15:03Z")
I do the type thing already, but that doesn’t scale well across LLAs. Ideal would be a member on HighLevelAnalyzer that provided the name(s) of the host analyzer(s). That works in the future when the host may be another HLA. 😃 ---
**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:** [April 9, 2022, 3:12am UTC](https://discuss.saleae.com/t/can-an-hla-determine-the-lla-type-its-working-with/1517/4 "2022-04-09T03:12:27Z")
@P.Jaquiery I went ahead and posted your feature request here: > **[HLA - Determine the LLA type it's working with - Logic 2 - Ideas and Feature...](https://ideas.saleae.com/b/feature-requests/hla-determine-the-lla-type-its-working-with/)** > > Original idea post here: > discuss.saleae.com/t/can-an-hla-determine-the-lla-type-its-working-with/1517 > > "I have an HLA I’d like to be able to work with various LLAs. I need to be able to decode frames based on the LLA type - a I2C “address” i I got to speak with Mark and Neel about this, and we agree this idea is great. Thanks again! ---
**Author:** ![KurtE](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/kurte/32/189_2.png) [@KurtE](https://discuss.saleae.com/u/KurtE)\ **Post date:** [April 9, 2022, 4:46pm UTC](https://discuss.saleae.com/t/can-an-hla-determine-the-lla-type-its-working-with/1517/5 "2022-04-09T16:46:08Z")
Some of this sounds similar to some of the stuff we discussed back in the thread: > [@Release HLA's that depend on LLA's that are not part of the install?](https://discuss.saleae.com/t/release-hlas-that-depend-on-llas-that-are-not-part-of-the-install/1476/3): > > Thanks @KurtE, that’s a great question and something we’ve been thinking about since we launched the marketplace. The same problem applies to HLAs that depend on other HLAs, once we add support for that. Today, in order to use a HLA, the user must first manually add the HLA and set all the settings. Some of those settings. Then, the user needs to manually add the HLA, select which LLA that wish to use, then set more settings. We would like to streamline that as much as possible. For example…