# Welcome to Logic 2 community!

**URL:** <https://discuss.saleae.com/t/welcome-to-logic-2-community/7>\
**Category:** Uncategorized\
**Created:** [April 8, 2019, 7:24pm UTC](https://discuss.saleae.com/t/welcome-to-logic-2-community/7 "2019-04-08T19:24:16Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![joe\_garrison](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/joe_garrison/32/12_2.png) [@joe\_garrison](https://discuss.saleae.com/u/joe_garrison)\
**Post date:** [April 8, 2019, 7:24pm UTC](https://discuss.saleae.com/t/welcome-to-logic-2-community/7/1 "2019-04-08T19:24:16Z")

</div>

## Changelog and Download Links - [Click here](https://ideas.saleae.com/f/changelog/)

## We love feedback!

- All feedback is read by the entire development team.
- We take it very seriously
- Not all feedback will be incorporated by the very next release (or few releases) – but it **is** on the radar

## What to give feedback on

Something:

- isn’t obvious
- is overwhelming (even just initially)
- doesn’t work
- is hard to read
- is cumbersome
- could be improved
- could be easier

Ideas:

- For providing more value
- For wow factor 🤩

---

<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:** [January 30, 2020, 2:07am UTC](https://discuss.saleae.com/t/welcome-to-logic-2-community/7/4 "2020-01-30T02:07:30Z")

</div>



---

<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:** [January 30, 2020, 2:07am UTC](https://discuss.saleae.com/t/welcome-to-logic-2-community/7/5 "2020-01-30T02:07:33Z")

</div>



---

<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:** [January 30, 2020, 2:07am UTC](https://discuss.saleae.com/t/welcome-to-logic-2-community/7/6 "2020-01-30T02:07:54Z")

</div>



---

<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:** [January 30, 2020, 2:08am UTC](https://discuss.saleae.com/t/welcome-to-logic-2-community/7/7 "2020-01-30T02:08:03Z")

</div>



---

<div class="post-metadata">

**Author:** ![jack.lix](https://avatars.discourse-cdn.com/v4/letter/j/4491bb/32.png) [@jack.lix](https://discuss.saleae.com/u/jack.lix)\
**Post date:** [August 31, 2022, 4:12pm UTC](https://discuss.saleae.com/t/welcome-to-logic-2-community/7/8 "2022-08-31T16:12:50Z")

</div>

The online manual is for Ver 1 - even if i go there from logic2 help menu.

How do I change the size of the pre-trigger data buffer? I need to see what happened before the trigger

---

<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:** [August 31, 2022, 7:11pm UTC](https://discuss.saleae.com/t/welcome-to-logic-2-community/7/9 "2022-08-31T19:11:40Z")

</div>

@jack.lix Here is the section of the User Guide that mentions how to set the pre-trigger data length.

> **[Capture Modes](https://support.saleae.com/user-guide/using-logic/capture-modes#capture-duration-before-and-after-trigger)**

Specifically, you’ll find it under the section called “Capture Duration Before and After Trigger”. Hope that was what you were looking for!

---

<div class="post-metadata">

**Author:** ![jack.lix](https://avatars.discourse-cdn.com/v4/letter/j/4491bb/32.png) [@jack.lix](https://discuss.saleae.com/u/jack.lix)\
**Post date:** [August 31, 2022, 7:32pm UTC](https://discuss.saleae.com/t/welcome-to-logic-2-community/7/10 "2022-08-31T19:32:07Z")

</div>

Thanks,

Got it figured out. Whatever buffer space is not used by the post trigger yields the pre-trigger.

I got fooled by a trigger that came before the pre-trigger buffer was filled.

---

<div class="post-metadata">

**Author:** ![danergo](https://avatars.discourse-cdn.com/v4/letter/d/d9b06d/32.png) [@danergo](https://discuss.saleae.com/u/danergo)\
**Post date:** [December 4, 2024, 1:48pm UTC](https://discuss.saleae.com/t/welcome-to-logic-2-community/7/11 "2024-12-04T13:48:36Z")

</div>

Folks, this software is great! I used PulseView before, and this is much better, thank you!

One limitation of PulseView is also present in Logic 2 (or I could not find out how to do):

I have two signals (MOSI and SCK). I wish to decode these as SPI. All great. However, I have some “garbage” at the beginning of the SCK line, and it ruins the SPI decoder.

I know I can delete everything before the cursor, which partially solves my problem. But what can I do if I don’t want to delete these data. Just I wish the SPI decoder to start “later” (let’s say from my marker)?

Thank you

---

<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:** [December 6, 2024, 9:16pm UTC](https://discuss.saleae.com/t/welcome-to-logic-2-community/7/12 "2024-12-06T21:16:45Z")

</div>

@danergo Thanks for writing in! Unfortunately, it’s not currently possible to set a manual starting point for protocol analyzers. We’re currently tracking this request in the feature request post below, and I’ve added a comment for you to track your need for this to be implemented.

> **[Manually set start / end points of analyzer decoding - Logic 2 - Ideas and...](https://ideas.saleae.com/b/feature-requests/manually-set-start-point-of-analysis-with-marker/)**
>
> In 1.x it was possible to manually set the start point of an analysis with a marker (see support.saleae.com/user-guide/using-logic/using-protocol-analyzers). In 2.x the only way to define the analysis range or start point is by trimming data (which...

You’ll want to delete the “junk” part of the beginning of the recording. In case you don’t want to delete the data for future reference, you can save the original copy of the capture file with the beginning data intact, while saving a new copy of the capture file with the beginning data deleted (I understand this is unfortunately quite clunky, since you need to save 2 captures).
