All insights
XINDAR INSIGHT

An Encoder Resolution Number Needs a Counting Convention

Read PPR and CPR using the manufacturer definition, then separate encoder cycles, decoded counts and receiver configuration.

A buyer asks for an incremental encoder with 2,048 pulses per revolution. The supplier's English table lists 2,048 CPR. The controller documentation asks for pulses per revolution and provides an X4 decoding setting. Multiplying the wrong field by four can leave the displayed position wrong even though every device is operating as configured.

Start with the manufacturer's definitions. PPR and CPR are not safe substitutes for an explicit statement of cycles, counted edges and decoder behavior. Identify what the encoder outputs, what the receiver counts and what the software expects in its configuration field.

That distinction belongs in an English supplier catalogue. A comparison that ranks encoders by the largest resolution number can combine unlike quantities, then turn a counting convention into an unsupported claim of better angular accuracy.

Read the acronym before using the number

US Digital's Pulses Per Revolution glossary entry gives an important counterexample to assumptions about these abbreviations. The company uses PPR for the count after fourfold quadrature multiplication and CPR for the resolution before that decoding. It explicitly notes that other vendors use the acronyms differently.

Its resolution entry explains the relationship between the encoder's output resolution and quadrature decoding. Those definitions apply to the terminology in that source. They should not be copied over another manufacturer's contrary, explicitly defined convention.

When a datasheet says CPR, ask whether it means cycles per revolution or counts per revolution and how those counts were obtained. When it says PPR, ask what the publisher means by a pulse. If the document does not define the term, get a source-linked clarification rather than choose the convention that produces the higher number.

Separate the output cycles from the decoder's counted events

A quadrature incremental encoder provides two channels, commonly called A and B, with a phase relationship that a suitable receiver can use to distinguish direction. A receiver's selected decoding determines which transitions contribute to its count.

NI's technical explanation of quadrature encoder interfaces describes X1, X2 and X4 decoding in its measurement context. These modes count different edges. They do not mean that the physical encoder suddenly produces four times as many cycles on one output channel.

For an invented idealized example, define the encoder explicitly as producing 2,048 complete cycles on channel A per mechanical revolution, with suitable quadrature signals. The following table concerns decoder counts, not a manufacturer's claimed angular accuracy:

Defined decoding caseCount events per revolutionNominal angle per counted event
One count per cycle2,048360 / 2,048 = 0.17578125°
Two counts per cycle4,096360 / 4,096 = 0.087890625°
Four counts per cycle8,192360 / 8,192 = 0.0439453125°

The numbers are our own calculation for the stated teaching case. They do not specify how every encoder, counter or software field defines its resolution.

Do not multiply a configuration field twice

Knowing that the final decoder count can be four times the cycle count is not enough to fill a configuration dialog. The software may already perform that multiplication internally.

NI's cited support article states that its DAQmx encoder PPR property remains a property of the encoder, while the software accounts for the selected X2 or X4 mode. It instructs users not to multiply that property by the decoding factor. That is a product-specific configuration rule, not a universal convention for all controllers.

A buyer comparing an encoder with a receiving device should therefore identify three values: output cycles per mechanical revolution, count events per revolution under the chosen decoding, and the value the receiver documentation requires in its field. Keep the field name and documentation revision with the configuration record.

A product page that collapses those three values into one “resolution” cell makes it easier to apply a correct multiplier to the wrong quantity.

Treat resolution and angular accuracy separately

The nominal angle per counted event describes the spacing implied by the counting model. It does not establish that every counted edge is positioned at exactly that ideal angle or that a mechanism's actual angle has the same error limit.

Encoder accuracy, mounting, mechanical transmission and receiving-system behavior belong to a fuller position-measurement assessment. A finer nominal count spacing does not independently establish better absolute angular accuracy.

Likewise, an incremental count is not automatically an absolute position after power loss. A reference or homing arrangement may be part of the system. If the encoder has an index channel, identify the actual specified behavior and how the receiver uses it. Do not turn the presence of a Z output into a universal promise that the machine always knows its position.

The English catalogue should retain the manufacturer's distinct performance fields. If the source provides only resolution, do not invent an accuracy specification to make the comparison table look complete.

Check frequency definitions at the intended speed

Output frequency and receiver count rate can also use different units. Continue the fictional 2,048-cycle example at 600 revolutions per minute. That speed is ten revolutions per second, so channel A produces 20,480 cycles per second in the idealized model. Fourfold decoding produces 81,920 count events per second.

Those quantities are related but different. A frequency limit in a datasheet needs its own definition: channel cycles, accepted transitions, a counter's event rate or another specified quantity. Do not compare a “kHz” limit with a count rate without checking which events it describes.

The signal interface and receiving requirements also matter. Matching a count convention does not establish compatible voltage levels, wiring, input timing or noise performance. Use the actual product documentation and qualified system review for that assessment. This article does not provide a wiring or motion-control safety procedure.

Publish a record that survives a short comparison

A useful English specification row can identify the exact model, manufacturer-defined acronym, explicit cycles or events per revolution, output channels, relevant interface, applicable speed or frequency conditions and source revision. If the row gives a decoded count, state the assumed decoding.

Keep order options visible. Some encoders allow a selected or programmable resolution; a product family's broad range does not establish the setting supplied for an individual order. The quotation, label and configuration record should identify the agreed option.

For AI-assisted supplier research, place the definition beside the resolution number. A summary that extracts only the row should still have a chance to distinguish output cycles from decoded counts. Do not put the only explanation in an unrelated general glossary that contradicts the model's own datasheet.

Xindar's manufacturing website and technical-content work can help present approved supplier information in English. The encoder's performance and receiving-system configuration remain technical decisions supported by the actual product evidence. A publishing example is not a physical encoder test or an endorsement of a control-system design.

Accept the content with a defined interpretation exercise

Give a reviewer the approved source row and ask for the output cycles, decoder count and required receiver setting. Include a second source using a different definition of the same acronym. The reviewer should preserve both definitions rather than normalize them silently.

Then ask for a count-rate calculation at a stated speed. The answer should name its units and event type. A correct numerical value with the wrong event label is still an incorrect interpretation.

If an AI assistant is used as another reading test, retain the exact question, complete response and source passage. Check whether it changed the manufacturer's terminology, multiplied an already decoded number or converted count spacing into accuracy. A correct answer once is evidence about that answer, not certification of the equipment or a guarantee of later recommendations.

Questions to resolve in a procurement review

Does CPR always mean counts per revolution?

No. A manufacturer may define it as cycles per revolution or use another explicitly documented convention. Read the actual definition before comparing numbers.

Does X4 decoding make the encoder four times as accurate?

It can provide four counted events per defined quadrature cycle in the applicable decoding scheme. That changes nominal counting resolution; it does not independently establish a fourfold improvement in angular accuracy.

Should the controller's resolution setting always be multiplied by four?

No. Follow the receiving software's field definition. Some systems account for the selected decoding internally. An extra multiplication can create a scale error.

Before approving the next English encoder table, replace each unexplained acronym with its full, source-defined counting meaning in the review copy. If the supplier and controller documentation then disagree, resolve that configuration question before reducing the record back to a short catalogue label.

Back to insightsMarkdown version