# Discrepancies between analog and digital readings

**URL:** <https://discuss.saleae.com/t/discrepancies-between-analog-and-digital-readings/139>\
**Category:** Logic 1.x  (Legacy) Software\
**Created:** [October 3, 2019, 11:16pm UTC](https://discuss.saleae.com/t/discrepancies-between-analog-and-digital-readings/139 "2019-10-03T23:16:41Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ari](https://avatars.discourse-cdn.com/v4/letter/a/5f8ce5/32.png) [@ari](https://discuss.saleae.com/u/ari)\
**Post date:** [October 3, 2019, 11:16pm UTC](https://discuss.saleae.com/t/discrepancies-between-analog-and-digital-readings/139/1 "2019-10-03T23:16:41Z")

</div>

I’m using Logic 8 with software 1.2.18 on Linux . Sometimes, I see different results for analog and digital representations of the same channel. Here’s an example. The pulses appear of equal length in Analog, but the high pulses are longer than low in digital. Same channel.

 ![a-d-discrepancy](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/952709044ba4a809277d85623b8442f68055e10a.png)

Another issue that’s been coming up is a kind of glitch, or a piece of noise. This screenshot is a zoom into the same capture as above. The analog is smooth at 0V, but the digital shows a 10ns (one-sample) dip.

 ![gpitch](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/7c2b407e3ceee447754ffaa0b01aad79f151e9b9.png)

I assume that analog is the more accurate in this case, mostly because it shows what I want to see :=) Seriously, though, looking at the capture, I can’t tell if my DUT is generating correct signals and Logic displays them funny, or if the DUT is glitching.

Ari.

---

<div class="post-metadata">

**Author:** ![ari](https://avatars.discourse-cdn.com/v4/letter/a/5f8ce5/32.png) [@ari](https://discuss.saleae.com/u/ari)\
**Post date:** [October 4, 2019, 2:38pm UTC](https://discuss.saleae.com/t/discrepancies-between-analog-and-digital-readings/139/2 "2019-10-04T14:38:21Z")

</div>

![a-d-discrepancy-beta](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/21427b302adb3ab8630d46eec368961d15657765.png)  
It looks the same in 2.0.7

---

<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:** [October 4, 2019, 9:36pm UTC](https://discuss.saleae.com/t/discrepancies-between-analog-and-digital-readings/139/3 "2019-10-04T21:36:41Z")

</div>

Hi Ari,

Sorry about this, and thanks for posting! I suspect there are two things at play.

1. Our Logic 8’s voltage threshold is fixed at the following levels

- Voltage input LOW: 0.6 volts
- Voltage input HIGH: 1.2 volts  
Regarding your first image, it looks like it takes some time before the digital channel will recognize it as a LOW signal. At what analog voltage reading does the digital transition from HIGH to LOW?

1. For your second image, although the digital channels have an adequate sampling rate to capture the glitches, the analog channel’s sampling rate is unfortunately unable to keep up. Each dot in the analog capture represents the sample points, and the line that is drawn between them is a mathematical interpolation. In addition, the digital and analog on a single channel take different paths internally in the hardware.

More information here: [https://support.saleae.com/troubleshooting/digital-and-analog-appear-different](https://support.saleae.com/troubleshooting/digital-and-analog-appear-different)

Our eventual goal is to support higher bandwidths in the next generation hardware.

---

<div class="post-metadata">

**Author:** ![cameron.hay](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@cameron.hay](https://discuss.saleae.com/u/cameron.hay)\
**Post date:** [October 10, 2019, 3:56pm UTC](https://discuss.saleae.com/t/discrepancies-between-analog-and-digital-readings/139/4 "2019-10-10T15:56:48Z")

</div>

You could always throw it on a scope. I have done that a bit to verify signals that the Saleae device has captures, especially the analog signals since it does sometimes lag/struggle to keep up.

---

<div class="post-metadata">

**Author:** ![ari](https://avatars.discourse-cdn.com/v4/letter/a/5f8ce5/32.png) [@ari](https://discuss.saleae.com/u/ari)\
**Post date:** [October 16, 2019, 12:07am UTC](https://discuss.saleae.com/t/discrepancies-between-analog-and-digital-readings/139/5 "2019-10-16T00:07:32Z")

</div>

Here’s what I’m taking away from this conversation and others offline.

1. Our low-level signal is above 0V, as a result of a board layout quirk.
2. This messes up Logic’s notion of high-to-low and low-to-high transitions, so that 50% duty cycle appears to have shorter positive than negative pulses.
3. The one-sample glitch is hysteresis. It will probably go away if the signal goes all the way to ground instead of flattening out at the positive offset.

Thank you to Tim, Mark, Jonathan and others who helped decipher these observations.