# Parallel analyzer

**URL:** <https://discuss.saleae.com/t/parallel-analyzer/1692>\
**Category:** Logic 2 Software\
**Created:** [July 8, 2022, 11:53pm UTC](https://discuss.saleae.com/t/parallel-analyzer/1692 "2022-07-08T23:53:14Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![przemek.klosowski](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/przemek.klosowski/32/538_2.png) [@przemek.klosowski](https://discuss.saleae.com/u/przemek.klosowski)\
**Post date:** [July 8, 2022, 11:53pm UTC](https://discuss.saleae.com/t/parallel-analyzer/1692/1 "2022-07-08T23:53:14Z")

</div>

I was fooling with the demo Logic 16 device and noticed that the parallel decoder that decodes channels 0-4 with clock on 5 shows weird blackouts: normally it shows a transition on ascending clock edge and then displays a value on a colored field, but every once in a while the field is truncated and black after an initial fragment. This happens in 2.3.55 as well as 2.3.47 on Fedora 36. Is that a bug or does it actually miean something that I am missing?

---

<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 14, 2022, 7:23pm UTC](https://discuss.saleae.com/t/parallel-analyzer/1692/2 "2022-07-14T19:23:44Z")

</div>

@przemek.klosowski My sincerest apologies for our late reply! I’m happy to look into this for you.

I’m not quite sure what you mean by this behavior, and I’m unable to reproduce the issue you are seeing. Could you provide the following for me?

1. A copy of your [capture file](https://support.saleae.com/user-guide/using-logic/saving-loading-and-exporting-data) (in .sal file format)
2. A screenshot showing the issue
3. The exact steps you take to reproduce the issue using your provided capture file

---

<div class="post-metadata">

**Author:** ![przemek.klosowski](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/przemek.klosowski/32/538_2.png) [@przemek.klosowski](https://discuss.saleae.com/u/przemek.klosowski)\
**Post date:** [July 15, 2022, 3:35am UTC](https://discuss.saleae.com/t/parallel-analyzer/1692/3 "2022-07-15T03:35:41Z")

</div>

I don’t have a capture file—it’s the "Try the demo device’ option and I am doing a brief capture of Logic 16 simulated data. OK, I can save the capture — here it is  
[Session 0.sal](https://discuss.saleae.com/uploads/short-url/g845XuPHUkFyY79gi1DLYazd9XJ.sal) (2.2 MB)

and the screenshot showing the gap in the analyzer right after 40ms

 ![saleae](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/2X/d/d9a7f1ecff9acd44a2cbb91d04a4e8e2dc541c5e.png)

---

<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 15, 2022, 9:57pm UTC](https://discuss.saleae.com/t/parallel-analyzer/1692/4 "2022-07-15T21:57:49Z")

</div>

@przemek.klosowski Aha! I think I know what’s happening here. By default, the Logic 2 app doesn’t generate analyzer-specific data when using a Demo device. However, we have instructions on how enable this feature by launching Logic 2 from the command line:

> **[Demo Mode](https://support.saleae.com/user-guide/using-logic/demo-mode#generating-analyzer-simulation-data)**

Specifically, you’ll want to launch it like so, assuming the AppImage file is on your desktop (replace 2.x.xx with your specific version).

```auto
export ENABLE_SIMULATION=1
cd Desktop
./Logic-2.x.xx-master.AppImage

```

---

<div class="post-metadata">

**Author:** ![przemek.klosowski](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/przemek.klosowski/32/538_2.png) [@przemek.klosowski](https://discuss.saleae.com/u/przemek.klosowski)\
**Post date:** [July 17, 2022, 4:14am UTC](https://discuss.saleae.com/t/parallel-analyzer/1692/5 "2022-07-17T04:14:03Z")

</div>

AH, I see… it works of course. I see that the decoder works fine when you load the simulation file—sorry I didn’t even check that, but just looked at the random/incorrect simulation data.

I don’t even want to ask what does ENABLE\_SIMULATION do and why it’s off initially when Logic clearly invitesto run the simulator on the opening screen 🙂  
p

---

<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 18, 2022, 9:19pm UTC](https://discuss.saleae.com/t/parallel-analyzer/1692/6 "2022-07-18T21:19:08Z")

</div>

@przemek.klosowski Glad to hear that worked! Long story short, we simply have not fully tested the feature yet with the ENABLE\_SIMULATION variable on. I’ve set aside some time to review it with the team to see if we can just enable it by default. I personally have not run into any bugs or issues with it so far so it may be safe to do so.
