# Logic 2.3.1

**URL:** <https://discuss.saleae.com/t/logic-2-3-1/594>\
**Category:** Downloads / Releases\
**Created:** [June 19, 2020, 12:25am UTC](https://discuss.saleae.com/t/logic-2-3-1/594 "2020-06-19T00:25:56Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![markgarrison](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/markgarrison/32/23_2.png) [@markgarrison](https://discuss.saleae.com/u/markgarrison)\
**Post date:** [June 19, 2020, 12:25am UTC](https://discuss.saleae.com/t/logic-2-3-1/594/1 "2020-06-19T00:25:56Z")

</div>

# Logic 2.3.1

## [Download Links](https://ideas.saleae.com/f/changelog/)

**Check out the Saleae Logic 2 Extension Marketplace!**  
Read more about the Marketplace on the [Saleae blog](https://blog.saleae.com/introducing-logic-2-marketplace/)!

## What’s New

- Added a “reset to default” button to the presets manager

## Improvements

- When saving HLA settings, restart the analyzer if there was a change
- Updated the terminal library to the latest
- Reset analog zoom & pan settings when changing between different device types
- HLA error message now makes it clear when not subclassing HighLevelAnalyzer

## Bug fixes

- Fixed serious crash for Logic 4 users
- Handle loading a file with missing extensions
- Handle loading a file with disabled extensions
- Detect graphic cards that don’t supported webGL
- Fixed terminal hangup when writing too many characters at once from HLAs
- (Hopefully) fixed error related to missing device IDs
- Fixed bug where sometimes extension installs would fail on the first attempt
- Fixed bug where changing between the original Logic and a new device could break the analog display
- Improved reporting and handling of internal errors after system sleep/resume

---

<div class="post-metadata">

**Author:** ![markgarrison](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/markgarrison/32/23_2.png) [@markgarrison](https://discuss.saleae.com/u/markgarrison)\
**Post date:** [June 19, 2020, 12:26am UTC](https://discuss.saleae.com/t/logic-2-3-1/594/2 "2020-06-19T00:26:04Z")

</div>



---

<div class="post-metadata">

**Author:** ![rei\_vilo](https://avatars.discourse-cdn.com/v4/letter/r/0ea827/32.png) [@rei\_vilo](https://discuss.saleae.com/u/rei_vilo)\
**Post date:** [June 19, 2020, 8:33am UTC](https://discuss.saleae.com/t/logic-2-3-1/594/3 "2020-06-19T08:33:26Z")

</div>

Here are some ideas for the **Marketplace**

- Curate the list with recommended extensions.

![Capture 2020-06-19 à 10.28.19](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/1cc59364381336f14af22b421ceebb1bf6106c69.png)

Have a look at the implementation of the [Visual Studio Code marketplace](https://marketplace.visualstudio.com/vscode). Atom list is confused and ultimately

- Provide tags to group the extensions.

For example, the protocol the extension relies on (`I²C`, `SPI`). Also, categories or collections like in the [Visual Studio Code marketplace](https://marketplace.visualstudio.com/vscode).

- Allow users to rate the extensions.

The [Visual Studio Code marketplace](https://marketplace.visualstudio.com/vscode) and the [Node-RED library](https://flows.nodered.org) have implemented users’ rating.

- Provide clear information about licensing.

Apart for open source, some developers may want to charge for an extension. Is the marketplace ready for that option?

- Explain what the `PRO` label means!

![Capture 2020-06-19 à 10.36.35](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/8fbcfd264cc8ca5de38f9d773c67246f807d9283.png)

---

<div class="post-metadata">

**Author:** ![andre.kjellstrup](https://avatars.discourse-cdn.com/v4/letter/a/da6949/32.png) [@andre.kjellstrup](https://discuss.saleae.com/u/andre.kjellstrup)\
**Post date:** [July 7, 2020, 6:41am UTC](https://discuss.saleae.com/t/logic-2-3-1/594/4 "2020-07-07T06:41:06Z")

</div>

Please add an option to search for consecutive bytes , mabe like this:

 ![Screenshot from 2020-07-07 08-32-29](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/e552ee0e6c7a400bdd7c084d170dcd1ab621ef4d.png)

Also, the link to documentation does not work (do not open browser, at least not on Linux)  
 ![Screenshot from 2020-07-07 08-34-15](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/4783603c3a6cb5913796c7a49a151fa89d30215c.png)  
same goes for the “blog-link” in release notes, and links like “repository” and “report” in extensions.

---

<div class="post-metadata">

**Author:** ![gabriel.sallum](https://avatars.discourse-cdn.com/v4/letter/g/ea5d25/32.png) [@gabriel.sallum](https://discuss.saleae.com/u/gabriel.sallum)\
**Post date:** [July 10, 2020, 6:45pm UTC](https://discuss.saleae.com/t/logic-2-3-1/594/5 "2020-07-10T18:45:40Z")

</div>

Any ideas on how to open “.bin” (former .logicdata) capture files ?  
I just did a capture on this new version and I see the file on the file system, but when it comes time to open it, I guess its being filtered out

---

<div class="post-metadata">

**Author:** ![rani](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/rani/32/343_2.png) [@rani](https://discuss.saleae.com/u/rani)\
**Post date:** [July 10, 2020, 6:51pm UTC](https://discuss.saleae.com/t/logic-2-3-1/594/6 "2020-07-10T18:51:25Z")

</div>

Hey @gabriel.sallum, welcome to our forum!  
Are you trying to open the capture back in the app?

---

<div class="post-metadata">

**Author:** ![gabriel.sallum](https://avatars.discourse-cdn.com/v4/letter/g/ea5d25/32.png) [@gabriel.sallum](https://discuss.saleae.com/u/gabriel.sallum)\
**Post date:** [July 10, 2020, 7:09pm UTC](https://discuss.saleae.com/t/logic-2-3-1/594/7 "2020-07-10T19:09:26Z")

</div>

YES! it does not even display the file it just created.  
its a new extension \*.bin (I just upgraded to this newer version from the older style application)

---

<div class="post-metadata">

**Author:** ![rani](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/rani/32/343_2.png) [@rani](https://discuss.saleae.com/u/rani)\
**Post date:** [July 10, 2020, 7:27pm UTC](https://discuss.saleae.com/t/logic-2-3-1/594/8 "2020-07-10T19:27:14Z")

</div>

I think that you exported the capture instead of saving it. You can only load a saved capture, and we should be more clear about it 🙂

Can you try saving the capture?

---

<div class="post-metadata">

**Author:** ![gabriel.sallum](https://avatars.discourse-cdn.com/v4/letter/g/ea5d25/32.png) [@gabriel.sallum](https://discuss.saleae.com/u/gabriel.sallum)\
**Post date:** [July 10, 2020, 7:29pm UTC](https://discuss.saleae.com/t/logic-2-3-1/594/9 "2020-07-10T19:29:02Z")

</div>

yeah somehow I did something and its gone.

it was a pretty long (~30G) capture… would be nice to have a idiot check before wiping data off…

anyways I’ve restarted again. Duly noted regarding the save vs export.

Anyways, love how I can click to scroll feature…

thanks!

---

<div class="post-metadata">

**Author:** ![rani](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/rani/32/343_2.png) [@rani](https://discuss.saleae.com/u/rani)\
**Post date:** [July 10, 2020, 7:33pm UTC](https://discuss.saleae.com/t/logic-2-3-1/594/10 "2020-07-10T19:33:12Z")

</div>

Sorry about that 🙁  
We’ll make sure that it’s clear!

> love how I can click to scroll feature…

Thanks, but click where exactly?

---

<div class="post-metadata">

**Author:** ![gabriel.sallum](https://avatars.discourse-cdn.com/v4/letter/g/ea5d25/32.png) [@gabriel.sallum](https://discuss.saleae.com/u/gabriel.sallum)\
**Post date:** [July 10, 2020, 7:35pm UTC](https://discuss.saleae.com/t/logic-2-3-1/594/11 "2020-07-10T19:35:22Z")

</div>

when using a data analyzer, there is an option to control+click a certain value (in blue above the digital signal) to go to that point on the analyzer data tab…  
“click to scroll to data row”

---

<div class="post-metadata">

**Author:** ![rani](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/rani/32/343_2.png) [@rani](https://discuss.saleae.com/u/rani)\
**Post date:** [July 10, 2020, 7:40pm UTC](https://discuss.saleae.com/t/logic-2-3-1/594/12 "2020-07-10T19:40:34Z")

</div>

Oh, great!  
I don’t know if you noticed but it was a bit buggy on 2.3.1 (jumping around a bit). We just released a fix on 2.3.2

Thanks for the feedback!

---

<div class="post-metadata">

**Author:** ![gabriel.sallum](https://avatars.discourse-cdn.com/v4/letter/g/ea5d25/32.png) [@gabriel.sallum](https://discuss.saleae.com/u/gabriel.sallum)\
**Post date:** [July 10, 2020, 7:43pm UTC](https://discuss.saleae.com/t/logic-2-3-1/594/13 "2020-07-10T19:43:55Z")

</div>

no I didn’t notice.  
I jumped to .2 already

BTW, when starting the application on Fedora , it gave me a gnarly error and it didn’t start,  
reading the NODE trace I noticed it was trying to load a library  
libnsl  
After I’ve installed that it worked fine.

should be more obvious…  
other than that looks great!  
thanks

---

<div class="post-metadata">

**Author:** ![rani](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/rani/32/343_2.png) [@rani](https://discuss.saleae.com/u/rani)\
**Post date:** [July 10, 2020, 7:46pm UTC](https://discuss.saleae.com/t/logic-2-3-1/594/14 "2020-07-10T19:46:29Z")

</div>

Thanks for letting us know, we’ll look into this.  
Unfortunately, it’s really hard to support all Linux distros and to make sure that the app runs smoothly on them…

---

<div class="post-metadata">

**Author:** ![gabriel.sallum](https://avatars.discourse-cdn.com/v4/letter/g/ea5d25/32.png) [@gabriel.sallum](https://discuss.saleae.com/u/gabriel.sallum)\
**Post date:** [July 10, 2020, 7:51pm UTC](https://discuss.saleae.com/t/logic-2-3-1/594/15 "2020-07-10T19:51:28Z")

</div>

I get it! but it would be pretty simple to add a message regarding a missing lib rather than crawling the app traces, and the having some sort of idea what the top 1 or 2 distros need to run would be nice, its not like Fedora (redhat) is an obscure distro…  
anyways thanks.

---

<div class="post-metadata">

**Author:** ![huffman](https://avatars.discourse-cdn.com/v4/letter/h/71e660/32.png) [@huffman](https://discuss.saleae.com/u/huffman)\
**Post date:** [July 10, 2020, 7:54pm UTC](https://discuss.saleae.com/t/logic-2-3-1/594/16 "2020-07-10T19:54:26Z")

</div>

Hi @gabriel.sallum - What version of Fedora are you using? I can try reproducing the issue on my end. Thanks!

Ryan

---

<div class="post-metadata">

**Author:** ![gabriel.sallum](https://avatars.discourse-cdn.com/v4/letter/g/ea5d25/32.png) [@gabriel.sallum](https://discuss.saleae.com/u/gabriel.sallum)\
**Post date:** [July 10, 2020, 7:56pm UTC](https://discuss.saleae.com/t/logic-2-3-1/594/17 "2020-07-10T19:56:01Z")

</div>

Hi, I’m on 29 (slightly old, I know)

---

<div class="post-metadata">

**Author:** ![rani](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/rani/32/343_2.png) [@rani](https://discuss.saleae.com/u/rani)\
**Post date:** [July 15, 2020, 4:03am UTC](https://discuss.saleae.com/t/logic-2-3-1/594/18 "2020-07-15T04:03:55Z")

</div>


