Encoders and high-speed counters measure motion that ordinary PLC scans cannot reliably observe. They support length measurement, position tracking, speed calculation and registration. Problems arise when engineers treat them like normal digital inputs. A missed pulse may be only microseconds long yet become millimetres of product error. Reliable applications coordinate electrical signal quality, hardware configuration and mathematically safe logic.
Using standard inputs for fast pulses
If pulse width is shorter than input filter or scan time, the PLC may miss it entirely. Faster logic cannot recover a pulse that never enters the input image.
Calculate maximum pulse frequency from encoder resolution and machine speed, including overspeed. Select a high-speed counter, encoder module or motion controller with margin. Configure input filters and electrical levels for that frequency.
Confusing PPR and counts per revolution
Encoder specifications may state pulses per revolution for one channel, while quadrature decoding counts one, two or four edges. A 1,024 PPR encoder can produce 4,096 counts per revolution in x4 mode.
Document the complete conversion: pulses, decode mode, mechanical ratio, circumference and engineering units. Verify by rotating a known distance rather than trusting one parameter.
Reversing A and B channels
Swapped quadrature channels reverse direction. Noise or phase problems can produce direction chatter and count errors. Check channel waveforms, phase relationship and module diagnostics.
Correct wiring or configured direction intentionally. Do not simply multiply by −1 until the physical interface is proven, because missing phase information may remain.
Ignoring signal type and termination
Single-ended, differential line-driver, push-pull and open-collector encoders require compatible receivers, power and wiring. Long high-speed runs need proper cable, shielding and sometimes termination.
Follow encoder and module requirements. Differential signals offer better noise rejection when supported. Inspect waveforms at the receiver under actual speed; a clean stationary voltage test does not prove high-frequency integrity.
Reset race conditions
Software may read a count while another task resets it, producing a discontinuity. A reset triggered by a noisy sensor can occur multiple times. Use hardware capture or synchronized reset features where available.
Treat registration as an event with identifier, captured count and acknowledgement. Debounce the physical marker appropriately without delaying precision. Keep an absolute accumulated position separate from cycle-relative zero when possible.
Counter rollover and data type overflow
Finite counters wrap from maximum to minimum or zero. Simple subtraction then creates a huge false movement. Signed and unsigned interpretations can worsen the error.
Use a data type with adequate range and compute differences with rollover-aware arithmetic. Estimate time to overflow at maximum frequency. Test values near both boundaries, not only near zero.
Inaccurate speed calculation
Speed can be calculated from counts during a fixed interval or time between pulses. Fixed-window methods become coarse at low speed; period measurement becomes sensitive at high speed and requires precise timestamps.
Choose or blend methods for the operating range. Use a stable sampling interval and filter only enough to control jitter. Distinguish zero speed from a timeout waiting for the next pulse.
Scaling with integer truncation
Counts-to-distance calculations can lose fractions if integer division occurs early. Small movements then accumulate error or appear as steps.
Use floating point or fixed-point arithmetic with adequate width, multiply before dividing when safe and preserve a remainder for cumulative conversions. Express constants from physical calibration, not only nominal geometry.
Mechanical slip and compliance
Perfect counting does not guarantee product position. A measuring wheel can slip, belts stretch and gear backlash changes direction response. An encoder on the motor measures motor motion, not necessarily material motion.
Place feedback where it represents the controlled quantity. Use registration sensors or secondary measurement to correct drift. Diagnose mechanical slip separately from lost electrical pulses.
Index pulse mistakes
The Z or index channel marks one encoder position per revolution. Resetting at every index can create jumps if the pulse is noisy or direction changes. Some applications need homing, not continuous reset.
Use hardware latching, validate expected position and accept index only in an authorized homing state. Alarm if the index is absent or appears outside tolerance.
Poor diagnostics
Store current count, captured count, frequency, direction, rollover count, marker events and module status. Add plausibility checks against commanded speed and travel limits. A sudden impossible acceleration may indicate noise or reset rather than mechanics.
Commission from low speed to maximum while observing diagnostics and waveforms. Test reverse direction, rollover, power cycle, marker loss and cable disturbance. High-speed counting becomes reliable when every layer agrees: the encoder creates a valid waveform, hardware captures every edge, software handles time and rollover, and scaling reflects real mechanics. Any shortcut in that chain turns invisible microseconds into visible production errors.
Commissioning calculations
Before motion, calculate maximum pulse frequency, minimum pulse width, counts per mechanical revolution, distance per count, maximum counter value and time to rollover. Confirm the module supports electrical interface, decode mode and frequency with margin. Record these values beside the configured parameters.
Then move a known mechanical distance in both directions and compare expected, captured and independently measured position. Test at slow speed, normal speed and maximum safe speed. A discrepancy that grows with speed suggests signal capture; a fixed ratio suggests scaling; direction-dependent error suggests backlash, slip or quadrature problems. This pattern-based approach prevents endless parameter guessing.
Inspect installation details before tuning software. Confirm encoder coupling, shaft runout, connector retention, cable bend radius, shield termination and separation from drive output leads. Verify that the counter module remains powered and referenced correctly during machine transients. Mechanical vibration or intermittent power can imitate a mathematical defect, while changing scale constants only makes the resulting position wrong in a less obvious way.
No comments:
Post a Comment