Select a hydraulic motor speed sensor together with its receiving input and RPM conversion. The signal format, counted events per revolution and shaft reference need to match across that chain. Include the measurement location in the RPM label, especially where a gearbox separates motor and machine output.
An old scaling value can survive a hardware replacement. The new installation may then produce a steady, plausible RPM number based on the wrong conversion. Before treating a screen value as evidence of motor performance, trace the measurement that produced it.
The examples below are desk calculations for this review, with invented inputs. They are separate from manufacturer specifications and reported measurements. Actual wiring, installation and control changes require the documentation and qualified procedures for the machine.
Establish which speed the machine needs to know
Start with the shaft named on the drawing. A sensor built into a motor may report a motor-related rotational signal. An external pickup may observe a sprocket, coupling, drum or gearbox output. The controller needs a defined relationship between the observed rotation and the RPM being displayed. Without it, the label “motor speed” can hide an assumption made years earlier.
For a hypothetical fixed reduction drive, the reference record could read:
Location or relationship
Assumed value
Motor shaft
150 rpm
Reduction ratio
5 motor turns per output turn
Output shaft
150 ÷ 5 = 30 rpm
The table assumes no additional transmission or slip. It accounts for an output tachometer reading of 30 alongside a motor-RPM display of 150. For a real assembly, obtain the actual ratio and label both locations before comparing their readings.
Required information
Measurement location to consider
Remaining interpretation
Motor running speed
A documented motor-speed pickup
Convert its signal using the selected motor and sensor data
Gearbox output speed
Output pickup, or a validated conversion from the input shaft
Identify the actual transmission ratio and its direction convention
Conveyor movement
The shaft or moving element relevant to the process
A drive-shaft reading alone may not establish material movement
Direction of the driven mechanism
A signal and mechanical reference that distinguish direction
Define the viewing end and how the transmission changes direction
Position or travel
A measurement arrangement designed for that requirement
An RPM value alone does not provide a referenced position
Decide the measurement's job before specifying its response. Local indication, an underspeed alarm and automatic regulation have different acceptance requirements. The later sections address those functions separately, including the additional review required for a safety-related use.
Identify the signal before interpreting its wires
There is no universal hydraulic motor sensor pinout. A connector that fits may carry a different supply, a different output type or a different assignment of pins. The required evidence is the documentation for the installed sensor and motor configuration, followed by the receiving controller's input specification.
Danfoss's Orbital Motor EMD Speed Sensor technical information, June 2021 illustrates why identification comes first. That product documentation distinguishes pulse, quadrature and CAN operating versions. Its pulse mode provides speed pulses and a separate direction signal; its quadrature mode uses phase-related outputs. Those are examples from the named Danfoss product, not a wiring or compatibility specification for a BLINCE motor.
“Digital” leaves the receiving interface undecided. A counter expects defined pulse transitions; a communication input expects the specified network and data format. A monitor's evaluated limit output has another purpose again. The signal description in the data sheet has to resolve which one is offered.
For an external measuring arrangement, ifm describes compact inductive speed monitors that detect passing metal targets and evaluate the intervals between detections. This is a different arrangement from assuming that every motor contains a prepared internal pickup. The target, mounting and evaluation method are part of the measurement system.
Documentation item
What to establish for the offered configuration
Supply and reference
Permitted supply range, reference connection and protection requirements
Output function
Raw pulse, direction state, phase-related channels, evaluated limit or communication data
Electrical interface
Output type, voltage/current conditions and compatible receiving input
Connection
Exact connector, mating part, pin numbering and cable assignment
Mechanical sensing
Prepared motor, target or other arrangement required by that sensor
Interpretation
Events per revolution, direction convention and any configurable settings
PNP, NPN, push-pull and differential belong in that interface review alongside the receiver specification. Keep the qualified electrical work tied to the documented pin assignments. Connector fit and wire colour leave the required electrical checks unresolved; experimental supply connections are inappropriate.
Convert pulses to RPM with a defined counting basis
Use f for the measured event rate in events per second and K for the number of the same events per measured-shaft revolution:
Measured-shaft speed, rpm = 60 × f ÷ K
For C counted events in a T-second observation:
Measured-shaft speed, rpm = 60 × C ÷ (K × T)
Use matching event definitions in the numerator and divisor, with valid timing and correctly acquired counts. The edge-counting section below shows how the divisor changes with the evaluation method.
Apply the first equation to this hypothetical single-cycle-counting arrangement:
Assumed quantity
Value
Role in the calculation
Complete pulse cycles per measured-shaft revolution
60
Sensor resolution as defined for this example
Count convention
One event per cycle
Makes K equal to 60 events/rev
Frequency at that convention
360 events/s
Input to the speed calculation
Correct calculated shaft speed
60 × 360 ÷ 60 = 360 rpm
Uses the actual example's 60 events/rev
Display with an incorrect divisor of 24
60 × 360 ÷ 24 = 900 rpm
Same incoming signal, incorrect configuration
The last two rows differ only in their software divisor. The incorrect result is 2.5 times the example's correct speed. In an investigation, that sort of fixed factor is a reason to inspect scaling while keeping other explanations open until the measurements resolve them.
For hydraulic sizing, use the separate motor speed-formula guide. It relates flow, displacement and efficiency to mechanical RPM. Pulse measurement instead asks what the shaft is doing; even a correctly calculated flow command is not a measurement of that motion.
Keep pulse resolution separate from edge counting
PPR, CPR and “counts” need definitions beside the numbers. A data sheet may specify complete cycles, while the receiving channel counts selected transitions. K is the divisor for the events actually entering the RPM calculation. It therefore depends on how that channel is configured.
ifm's incremental encoder explanation defines resolution in pulse cycles per shaft revolution and describes phase-offset A and B channels for determining direction. That provides useful terminology; the actual sensor and controller manuals still determine the supported counting mode and its configuration.
With an idealized 60-cycle/revolution signal on each of two quadrature channels, the following receiver choices have different event counts. These are conditional examples; the receiver has to support the chosen method.
Hypothetical evaluation method
Events assigned to one cycle period
Effective K for 60 cycles/rev
One selected edge on one channel
1
60 events/rev
Both edges on one channel, if supported
2
120 events/rev
Four-edge quadrature decoding, if supported
4
240 events/rev
The correct divisor follows the selected row. A frequency taken as complete cycles on one channel and a four-edge decoded count can both yield the correct RPM, but they require their corresponding divisors. The rows cannot be applied to a pulse-plus-direction interface as though its direction-state wire supplied quadrature pulses.
For a persistent twofold or fourfold discrepancy, compare the count convention and the software conversion. A library may already account for the decoding factor. Applying it again in the display calculation would scale an otherwise correct measurement a second time.
The configuration record should state the sensor's pulse-cycle definition, the input decoding mode and the effective divisor used for RPM. “PPR = 60” alone leaves too much interpretation to the next person who replaces the controller or restores a program backup.
Slow rotation changes the time available for measurement
At slow rotation, a screen can refresh several times between new events. Its current number depends on the evaluator's observation method and treatment of the last result. Screen refresh and fresh rotational information are separate rates.
The next worksheet assumes 12 evenly spaced recognized events per revolution at a steady 6 rpm. Its simple evaluator collects integer counts in separate quarter-second windows.
Low-speed worksheet
Hypothetical result
Actual steady shaft speed
6 rpm
Effective events per revolution
12
Mean event frequency
12 × 6 ÷ 60 = 1.2 Hz
Nominal interval for evenly spaced events
1 ÷ 1.2 ≈ 0.833 s
Window used by the simple example counter
0.25 s
Mean events per window
1.2 × 0.25 = 0.3
RPM represented by one event in one window
60 ÷ (12 × 0.25) = 20 rpm
With fewer than one event per window on average, the example produces empty windows between counted events. A zero-and-20 RPM indication is therefore possible with that evaluator at steady 6 rpm. The numerical jumps do not, on their own, establish changing mechanical speed.
Interval-based evaluation behaves differently from this window-counting example. ifm's frequency-to-speed overview describes pulse-interval evaluation and frequency or RPM output. For a selected receiver, examine its own algorithm and response specification.
A longer window contains more events but represents a longer observation. Increasing events per revolution is another possibility within the sensor, target and receiver limits. The review has to relate those choices to the response the machine needs, rather than choosing a PPR or window length in isolation.
Distinguish no new pulse from a confirmed stopped shaft
Revisit the low-speed worksheet before assigning a no-event timeout. Its nominal interval is 0.833 seconds, so a hypothetical half-second timer would expire while waiting for the next normal event. The hardware could be working as intended and still trigger that poorly matched decision.
A useful requirement names the allowed detection delay, the evaluation method and the expected result through reversal or creep. The selected method has to work with the new events available at those speeds. A smoother screen value alone does not demonstrate the required detection response.
The EMD manual includes a failure warning: sensor outputs may misrepresent rotation speed or direction. Its application-risk requirement belongs in the system review. Access and load restraint must follow the machine's assessed safety arrangements; a zero on an ordinary RPM display does not establish a safe access condition.
Alarm terminology needs the same care. An underspeed decision during a run command, a no-event indication and a detected signal fault are different observations. The proposed evaluator may distinguish some of them and leave others unresolved. Ask for that behaviour to be documented, particularly if both a stationary target and a disconnected signal would produce the same frequency value.
Match the receiving input to the entire speed range
The highest expected event rate belongs beside the input-channel specification. “Digital input” and a nominal voltage leave its pulse acquisition capability undecided. Use the actual channel, mode and filter documentation for the comparison.
For a hypothetical maximum-speed calculation:
Input or result
Assumed value
Recognized events per shaft revolution
72
Highest shaft speed for this example
900 rpm
Event rate to evaluate
72 × 900 ÷ 60 = 1,080 events/s
That result is a receiver requirement for the stated event basis. Including additional edges would require revisiting the rate and divisor together. It supplies no frequency rating for a particular sensor or input.
Beside the calculated rate, retain the configured channel's limits for pulse width, signal level and filtering. Also identify how the program obtains its count. A hardware counter read by the program and a program attempting to sample each transition are different acquisition arrangements; the relevant documentation must establish which one is in use.
Receiver review item
Evidence to put beside the requirement
Lowest useful speed
Expected event intervals and the evaluation method's response there
Highest useful speed
Calculated event rate and input capability in the chosen mode
Signal level and shape
Sensor output specification and receiver acceptance conditions
Filtering
Configured input filtering and its effect on legitimate pulses
Update and timeout
Actual parameter definitions, rather than a screen refresh rate alone
Counting and scaling
Hardware count mode, software conversion and mechanical ratio
If the discrepancy appears only at higher speed, the useful comparison is between the documented incoming signal measurement and the receiver count. Agreement leads the investigation onward to conversion and display. Disagreement leaves acquisition unresolved, and the display is not yet a verified measurement of hydraulic-drive speed.
Compare speed and direction using one physical reference
The direction reference belongs on the drawing: named viewing end, an arrow and the sign intended on the display. Viewing the same rotation from opposite ends reverses its clockwise description. A transmission adds another relationship to verify between the sensed shaft and machine movement.
A repeated single-channel pulse pattern can look the same in either direction. The receiver therefore needs the documented direction information, whether an additional state, a phase relationship or communication data. Labelling pulses with the command's sign only records what was requested. It leaves actual direction unmeasured when the mechanism moves differently from that command.
For the selected sensor, determine whether direction is a separate state, decoded from channels or supplied in communication data. The receiving function must interpret the documented format. A change in channel assignment or sign convention can reverse the displayed direction while the mechanism continues to move exactly as before.
A direction record needs the motor and sensor identification, viewing end, reference arrow, command, observed movement and reported sign or state. Acceptance under the machine's qualified procedure can then establish that mapping in each required direction. Retain the record with the control configuration.
Where a downstream process depends on direction, retain the mechanical ratio and direction relationship with the control configuration. A replacement motor, gearbox, controller program or sensor mode can change part of that chain. The assembly record needs to show which relationship was rechecked after the change.
Trace a wrong reading through the measurement path
Work from observations rather than from a presumed failed part. “Screen stays at zero” is an observation. “Sensor failed” is one possible explanation. The distinction keeps the investigation open to a missing power supply, an incompatible input, a configuration change or a shaft that is genuinely stationary.
The relevant test points follow the path: physical rotation at the defined location, sensor output, received electrical or communication signal, input interpretation and displayed engineering value. Qualified personnel should use approved access, instruments and isolation procedures for the machine. This guide does not prescribe live probing or require removing guards to obtain a speed reading.
Observation
Next comparison to document
What remains unproven
Shaft rotation confirmed, display zero
Signal at the permitted measurement point versus receiver status
Which part of the path is losing or misinterpreting information
Stable display differs by a fixed factor
Effective events/rev, software scaling and measurement locations
Whether the factor comes from counting or the transmission
Display fluctuates at slow steady rotation
Event intervals, count window and evaluation behaviour
Whether the mechanical speed itself fluctuates
Display drops at higher speed
Valid sensor signal versus counted events and receiver limits
A hydraulic or electrical cause until the measurements separate them
Direction indication disagrees with observation
Viewing convention and documented direction format
A reversal fault versus an interpretation error
Fault began after replacement
Old and new configuration, sensor mode, wiring documentation and program revision
Compatibility merely from similar housings or connectors
Identify the independent instrument's location and limitations in the record. In the earlier 5:1 example, an output tachometer cannot be compared directly with the unconverted motor RPM. During changing speed, the observation intervals also need to be comparable.
The record needs the readings before correction, the change made and the result under the same relevant condition. Several simultaneous adjustments leave the cause ambiguous even when the screen subsequently looks right. Keep protective functions effective and use the approved procedure; altering a hydraulic relief setting cannot resolve a numerical scaling error.
If a suitable reference confirms loaded slowdown, continue with the hydraulic and mechanical investigation using measurements appropriate to flow, pressure difference, oil condition and load. The RPM signal identifies the motion being investigated, while those further measurements help explain it.
Evaluate sensor mounting before buying a retrofit kit
An internal pickup depends on the motor configuration intended to work with it. A sensor shown in another manufacturer's catalogue is not evidence that it can read a similarly named BLINCE motor. The prepared housing, sensing feature and installation instructions have to match the exact product. An unused opening in a casting does not establish that preparation.
For an external pickup, the assembly drawing needs the target, its speed relationship to the named shaft and the permitted sensing arrangement. The bracket, target and protection from contact or damage belong to one proposed installation. Quoting the pickup alone leaves those mechanical functions outside the offered scope.
The moving assembly drawing should include the cable route and service access throughout travel. Keep the selected connector, sealing and strain relief in the installation specification. Acceptance then checks the assembled connection in its intended service, rather than assuming a component's rating covers the whole installation.
Installation dimensions and adjustments belong to the applicable sensor instructions. A gap copied from an unrelated pickup may prevent detection despite an electrical match. Housing modifications require an approved design, with a photograph of a different motor providing insufficient evidence for drilling a new sensing hole.
For procurement, compare the entire supplied package: prepared motor or external target arrangement, sensor, mating connector, cable, signal evaluation and drawings. A low sensor-only quotation may leave the target or receiver unanswered. An included sensor may still use a signal format the existing machine cannot accept. A parts list tied to the offered configuration makes those omissions visible before installation.
Keep speed feedback separate from automatic speed control
Feedback adds a measurement to the drive. A regulation project also needs a defined control strategy, a means of changing hydraulic flow or displacement and enough supply capacity for the specified load. The supplier's proposal must cover that whole function. A sensor quotation alone leaves the means of correcting a measured speed error undecided.
For a project brief, distinguish the requested outputs. “Show motor speed on the HMI” describes indication. “Alarm below a stated speed after the approved start sequence” adds a monitoring requirement. “Maintain a target speed while the specified load changes” asks for control performance. The last request needs a review of the hydraulic and control system, rather than a sensor selection alone.
The low-speed worksheet belongs in that system review. Its nominal 0.833-second event interval limits the arrival of new rotational information. Any proposed response needs to account for the selected evaluation method and that information rate; increasing the screen refresh rate leaves the physical event rate unchanged.
Speed feedback also differs from position feedback. Integrating or counting movement may provide useful information in a designed system, but a displayed RPM does not establish a referenced absolute angle or a safe holding function. Define those requirements separately if the machine needs them. The speed-sensor purchase should not silently acquire a positioning or load-support promise.
The acceptance plan follows the requested function: reference comparison for indication, defined operating and fault states for an alarm, and agreed behaviour under load changes for regulation. The machine designer needs to establish the safe test procedure and limits before commissioning.
Send a motor-and-feedback brief with the inquiry
BLINCE's hydraulic motor category is a starting point for identifying a motor family. It is not confirmation that every listed motor has a speed-sensor option. Request evidence for the exact motor configuration and any proposed feedback arrangement before making a replacement or integration decision.
An inquiry for this task can be compact:
Field
Information that helps the review
Existing or proposed motor
Full code, identification photos and relevant drawing
Measurement job
Indication, process alarm, regulation or another defined function
Reference location
Motor shaft, gearbox output or the relevant machine element
Motion
Minimum and maximum speed, required directions and changes during the cycle
Mechanical relationship
Transmission ratio, direction convention and target arrangement where applicable
Existing signal path
Sensor identification, output documentation, cable/connector and receiving input
Interpretation
Pulse/count definition, effective events/rev, conversion, update and timeout requirements
Observed issue
Reference measurement and displayed value under the same identified condition
Send that information through BLINCE's contact page. Ask for the proposed motor configuration, drawing, supported sensor arrangement if available, signal specification and any remaining compatibility questions. Where feedback capability cannot be confirmed from the current product data, a request for further documentation is the appropriate next result.
Keep the agreed signal definition and scaling with the machine's records after the purchase. The next replacement should be checked against that record, including controller settings and the measurement location, so that a motor change does not inherit an unexplained RPM conversion from the old installation.
This article is a general engineering guide. Final component selection should be based on machine drawings, measured hydraulic data, working conditions, safety requirements, and confirmation from a qualified hydraulic engineer or supplier.
Blince Hydraulic Team
Blince Hydraulic is an industry-leading company dedicated to precision-engineered fluid power manufacturing and custom hydraulic solutions. Backed by decades of deep field expertise in industrial machinery and thousands of successful global deployments, our engineering team focuses entirely on high-performance hydraulic component manufacturing, including specialized orbital motors, high-pressure travel drives motor, and robust directional control valves. Our production infrastructure utilizes state-of-the-art multi-axis CNC machining systems and is fully ISO 9001 certified to guarantee repeatable volumetric accuracy across every single manufacturing run.
We deliver fast, highly dependable, and cost-efficient hydraulic solutions to heavy industry distributors, machinery OEMs, and maintenance crews across more than 150 countries. Whether your active project calls for a small-volume batch of customized shaft profiles or a large-scale production run of severe-duty cast iron gear pump, we configure our flexible production schedules to meet your target lead times with total pricing predictability. Partnering with Blince means securing maximum system efficiency, elite material quality, and uncompromised fluid power professionalism.
To learn more about our complete product lineup, visit our official website: www.blince.com.
