# I2C analyzer seems messed up

**URL:** <https://discuss.saleae.com/t/i2c-analyzer-seems-messed-up/1103>\
**Category:** Logic 2 Software\
**Created:** [July 27, 2021, 11:50am UTC](https://discuss.saleae.com/t/i2c-analyzer-seems-messed-up/1103 "2021-07-27T11:50:30Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![inevitableavoidance](https://avatars.discourse-cdn.com/v4/letter/i/77aa72/32.png) [@inevitableavoidance](https://discuss.saleae.com/u/inevitableavoidance)\
**Post date:** [July 27, 2021, 11:50am UTC](https://discuss.saleae.com/t/i2c-analyzer-seems-messed-up/1103/1 "2021-07-27T11:50:31Z")

</div>

I’m completely baffled by the results I’m getting on the I2C analyzer, please see the attached picture:

 ![Untitled](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/18be0f99e9b0fb3804dfdecadb20d18c53403d77.png)

Data stays equal, analyzer results are not.

I’m at the most recent version. Does anyone know what could be up?

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![P.Jaquiery](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/p.jaquiery/32/289_2.png) [@P.Jaquiery](https://discuss.saleae.com/u/P.Jaquiery)\
**Post date:** [July 27, 2021, 9:06pm UTC](https://discuss.saleae.com/t/i2c-analyzer-seems-messed-up/1103/2 "2021-07-27T21:06:16Z")

</div>

Best guess? You have glitches on the clock edges. Try turning on a 150ns or even longer glitch filter on the SCL channel. If you zoom in on the first couple of clock edges you will be able to see multiple edges if glitching is the problem. Note that usually the device under test works fine - it’s just the analyser that is seeing the glitches.

---

<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 27, 2021, 9:12pm UTC](https://discuss.saleae.com/t/i2c-analyzer-seems-messed-up/1103/3 "2021-07-27T21:12:53Z")

</div>

@inevitableavoidance Sorry for the trouble with the I2C analyzer. I agree with @P.Jaquiery.

Here is a support article below that explains it in a bit more detail, as well as how to enable the glitch filter.

- [Issues with Noise Around Clock Edges](https://support.saleae.com/protocol-analyzers/analyzer-user-guides/using-i2c#issues-with-noise-around-clock-edges)

In case that doesn’t help, feel free to upload your .sal capture file and I can take a closer look on my end. Instructions below:

> **[Capture & Preset File Management](https://support.saleae.com/user-guide/using-logic/saving-loading-and-exporting-data)**

---

<div class="post-metadata">

**Author:** ![inevitableavoidance](https://avatars.discourse-cdn.com/v4/letter/i/77aa72/32.png) [@inevitableavoidance](https://discuss.saleae.com/u/inevitableavoidance)\
**Post date:** [July 28, 2021, 8:36am UTC](https://discuss.saleae.com/t/i2c-analyzer-seems-messed-up/1103/4 "2021-07-28T08:36:48Z")

</div>

You guys are absolute hero’s! Zooming all the way in revealed teeny tiny double edges, easily mitigated by the glitch filter.

Thanks a bunch,  
Kind regards,  
David
