# Looking for some support?

**URL:** <https://discuss.saleae.com/t/looking-for-some-support/401>\
**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:** 1\
**Showing post:** 5

<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:** [January 29, 2024, 10:03pm UTC](https://discuss.saleae.com/t/looking-for-some-support/401/5 "2024-01-29T22:03:27Z")

</div>

@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…

---

_[View the full topic](https://discuss.saleae.com/t/looking-for-some-support/401)._
