# Looking for some support? **URL:** \ **Category:** Support\ **Created:** [March 29, 2020, 3:18pm UTC](https://discuss.saleae.com/t/looking-for-some-support/401 "2020-03-29T15:18:10Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![shira](https://avatars.discourse-cdn.com/v4/letter/s/aeb1de/32.png) [@shira](https://discuss.saleae.com/u/shira)\ **Post date:** [March 29, 2020, 3:18pm UTC](https://discuss.saleae.com/t/looking-for-some-support/401/1 "2020-03-29T15:18:10Z")
Do you have a question? Our community has answers. Got stuck and you need someone to take a fresh look? Our community is here just for that. This is a safe place, there’s no such thing as dumb questions. ---
**Author:** ![harin.nair](https://avatars.discourse-cdn.com/v4/letter/h/d07c76/32.png) [@harin.nair](https://discuss.saleae.com/u/harin.nair)\ **Post date:** [June 28, 2022, 10:32am UTC](https://discuss.saleae.com/t/looking-for-some-support/401/2 "2022-06-28T10:32:12Z")
segmentation fault on launching Saleae with 1.2.xx(tried 18 and 29) Platform details: Linux : Debian 11.3.0, Debian 11.2.0 Dell :5090 mini pc. Attached the crash dump [Errors.zip](https://discuss.saleae.com/uploads/short-url/7SVcN76PFTQFqu6yrZbMhXmVoj7.zip) (4.7 KB) ---
**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 28, 2022, 6:03pm UTC](https://discuss.saleae.com/t/looking-for-some-support/401/3 "2022-06-28T18:03:48Z")
You can find the solution on your other post here: > [@Looking for some support?](https://discuss.saleae.com/t/looking-for-some-support/401/2): > > segmentation fault on launching Saleae with 1.2.xx(tried 18 and 29) Platform details: Linux : Debian 11.3.0, Debian 11.2.0 Dell :5090 mini pc. Attached the crash dump [Errors.zip](https://discuss.saleae.com/uploads/short-url/7SVcN76PFTQFqu6yrZbMhXmVoj7.zip) (4.7 KB) ---
**Author:** ![kenjustken42](https://avatars.discourse-cdn.com/v4/letter/k/6bbea6/32.png) [@kenjustken42](https://discuss.saleae.com/u/kenjustken42)\ **Post date:** [January 25, 2024, 10:32pm UTC](https://discuss.saleae.com/t/looking-for-some-support/401/4 "2024-01-25T22:32:20Z")
> [@shira](#): > > Do you have a question? Our community has answers. > Got stuck and you need someone to take a fresh look? > Our community is here just for that. > > This is a safe place, there’s no such thing as dumb questions. Version 2.4.8 PMBUS Decode is showing an invalid PEC Error. I have a trace that shows an issue with the PEC calculation but have no way of posting it since I don’t have the privilege yet. What do I do? ---
**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:** [January 29, 2024, 10:03pm UTC](https://discuss.saleae.com/t/looking-for-some-support/401/5 "2024-01-29T22:03:27Z")
@kenjustken42 Sorry for the trouble with that! I just saw that you made another post about this issue below. I’ll share my reply there later today. > [@Invalid PMBUS PEC Error plus other issues](https://discuss.saleae.com/t/invalid-pmbus-pec-error-plus-other-issues/2694): > > I am running version 2.4.8 and I am seeing two issues with the PMBUS decode. The biggest issue is the PEC calculation is intermittently wrong and says the PEC value that we send is invalid. This mainly seems to occur on a Read where the PEC includes the entire transaction. In the attached trace, the very last transaction is doing Read from Address 0xD6 which returns a byte return value of 0x00, so the PEC calculation should use the values 0x78 0xD6 0x79 0x00 PEC value should be 0xCF but the… ---
**Author:** ![johndorian830](https://avatars.discourse-cdn.com/v4/letter/j/e95f7d/32.png) [@johndorian830](https://discuss.saleae.com/u/johndorian830)\ **Post date:** [November 24, 2025, 1:37pm UTC](https://discuss.saleae.com/t/looking-for-some-support/401/6 "2025-11-24T13:37:15Z")
Is there a way to STOP recording once no edges are detected on a channel ? ---
**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:** [November 25, 2025, 12:52am UTC](https://discuss.saleae.com/t/looking-for-some-support/401/7 "2025-11-25T00:52:42Z")
@johndorian830 Thanks for writing in! This is a request that we’re currently tracking in the idea post below. > **[Trigger on signal state](https://ideas.saleae.com/b/feature-requests/trigg-on-signal-state-low-high-after-x-time/)** > > Hardware logic analyzers have the option to trigger on a logic state being stuck for a certain period of time either low or high. > > Currently Logic 2 supports "Pulse Trigger" which you need to specify both the minimum and maximum time before it Sorry we don’t have an immediate solution for that. For now, I’ve added a comment for you to track your need for this feature to be implemented. We’ll continue keeping an eye on interest in this feature request before we commit it to the roadmap.