# Analyser for quadrature encoder

**URL:** <https://discuss.saleae.com/t/analyser-for-quadrature-encoder/2556>\
**Category:** Extensions\
**Created:** [November 24, 2023, 6:55am UTC](https://discuss.saleae.com/t/analyser-for-quadrature-encoder/2556 "2023-11-24T06:55:22Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![wolfgang.kopp](https://avatars.discourse-cdn.com/v4/letter/w/4491bb/32.png) [@wolfgang.kopp](https://discuss.saleae.com/u/wolfgang.kopp)\
**Post date:** [December 5, 2023, 2:59pm UTC](https://discuss.saleae.com/t/analyser-for-quadrature-encoder/2556/17 "2023-12-05T14:59:05Z")

</div>

you have it right now, your analyzer is definitely not correct. I only know X4 quadrature encoders and they are very common. I do not care too much about “Position” and “rate”, because I can convert it externally, so I would focus on a basic X4 implementation.  
also check out the other request:

> [@Quadrature Encoder Analyser](https://discuss.saleae.com/t/quadrature-encoder-analyser/877):
>
> Hi, I was wondering if I could get some advice on how best to interface with my Saleae Logic 16 for a project I am working on. Basically I have a stepper motor with a quadrature encoder and I am looking to characterise that motor within a mechanical system. The quadrature encoder outputs two square wave signals as shown below: [image] Basically the number of rising edges gives you the distance moved, the time between the rising edges gives you the velocity, and finally the phase of the two s…

---

_[View the full topic](https://discuss.saleae.com/t/analyser-for-quadrature-encoder/2556)._
