MAGATOM DYNAMICS / FORCE SENSING DIVISIONShenzhen, China · Worldwide engineering inquiries

TECH NOTE 02 / Robotics and acquisition

Tendon tension sensing: Bowden friction, sensor location and calibration

Measure at the location relevant to the controlled force; motor-side tension can differ from distal tension.

Use the page RFQ ↓
Direct application engineeringSend both interfaces, capacity and output. Your email opens with an engineering checklist.

Quote, drawing & calibration review

01

Measure at the location relevant to the controlled force; motor-side tension can differ from distal tension.

02

Use capstan arithmetic as a sliding-friction screening model, not a complete reversal or dynamic calibration.

03

Validate posture, motion direction, pretension and channel timing together.

01 / ENGINEERING DECISION

Choose which tension you need to observe.

A tendon tension load cell for robotics observes force at its own location. Between that location and the contact point, sheath friction, pulleys, compliant tendons and joints can change the relationship to the desired force. A good sensor reading is not automatically a measurement of fingertip contact force.

Start with a free-body sketch of the controlled structure. Decide whether the variable is proximal cable tension, distal tendon tension, joint torque or contact force. Converting among them needs the relevant routing, moment arms and other forces; moving a sensor does not remove that modeling requirement.

Two local tension observations separated by a frictional transmission. Neither is automatically fingertip contact force.Original educational schematic. Refer to the adjoining equations, assumptions and accessible data tables.Proximal tensionT_inDistal tensionT_outSheath: curvature, friction, historyLocal tension depends on sensing positionA static screen does not calibrate a reversal
Two local tension observations separated by a frictional transmission. Neither is automatically fingertip contact force.
Sensing location changes observability and packaging.
LocationDirectly observesTradeoff to evaluate
Before the sheathProximal tendon tensionDistal force needs a transmission model or reference.
After the sheathLocal distal tendon tensionPackaging, cable reaction and attachment mass.
Both ends during developmentTransmission difference under the testExtra channels and synchronized reference acquisition.

Supporting scope: Wagner & Emmanouil (2018): tendon-sheath transmission ↗ · Zhou et al. (2024): tension sensor array for cable-driven robots ↗

02 / ENGINEERING DECISION

Use the capstan model only within its assumptions.

For a simple sliding-friction screen, define a proximal pulling tension T_in, positive total wrap angle theta in radians and an assumed effective friction coefficient mu. A corresponding distal estimate is T_out = T_in × exp(−mu × theta). This gives a direction-specific estimate under the model assumptions.

Wagner and Emmanouil analyze tendon-sheath transmission with explicit assumptions. The equation does not establish a constant friction coefficient for an actual moving hand. At rest or reversal, friction can support a range of tensions; a single exponential equality does not describe that history. Compliance, acceleration and changing routing add further limitations.

MODEL / DEFINED ASSUMPTIONS

T_out / T_in = exp(−mu × theta), for the stated pulling/sliding case

Direction-specific sliding-friction screen with theta in radians. Reversal, stiction and dynamic effects require further modeling.Original educational schematic. Refer to the adjoining equations, assumptions and accessible data tables.Proximal tensionT_inDistal tensionT_outSheath: curvature, friction, historyT_out / T_in = exp(−mu × theta)A static screen does not calibrate a reversal
Direction-specific sliding-friction screen with theta in radians. Reversal, stiction and dynamic effects require further modeling.

Supporting scope: Wagner & Emmanouil (2018): tendon-sheath transmission ↗ · Single tendon-sheath system with time-varying parameters (2025) ↗

03 / ENGINEERING DECISION

Worked example: a good proximal reading can miss distal loss.

Assume mu = 0.10 and T_in = 20 N for an idealized sliding case. The values below are calculated, not measured. At a total angle of pi radians, the estimate is 14.61 N distally even while the proximal sensor reads 20 N. A controller that needs distal tension cannot treat those values as equivalent.

These are sensitivity checks for an assumed coefficient. Do not enter mu = 0.10 as an identified material property or extrapolate this table through a direction reversal. Compare it with measured local references for the intended routing.

Synthetic capstan calculation, rounded to two decimals.
Total wrap angleTransmission ratioEstimated distal tension
0 rad1.00020.00 N
pi / 2 rad0.85517.09 N
pi rad0.73014.61 N
2 × pi rad0.53310.67 N

Supporting scope: Wagner & Emmanouil (2018): tendon-sheath transmission ↗

04 / ENGINEERING DECISION

Select range from pretension, useful increment and assembly load.

A tendon can have a substantial baseline tension while the desired control increment is small. The useful signal is the increment on top of that baseline, not the entire nominal range. Include cable forces and fixture mass when testing the smallest observable change.

Do not solve an assembly overload problem only by increasing capacity. A larger range may reduce the force signal per volt; a protected attachment procedure or an appropriate mechanical stop may be the more relevant change. The proposed sensor’s actual range, noise and directional overload evidence govern the choice.

Inputs for a subminiature tendon measurement request.
InputSpecifyWhy it matters
PretensionMinimum and maximum across postureConsumes range before external contact.
Useful incrementSmallest force change and bandwidthDefines an input-referred noise target.
Transient / assembly loadMagnitude, direction and durationCan exceed the operating cycle.
Mechanical attachmentThread, eyelet or clevis and moving massChanges the local force path.
Cable routingBend, restraint and temperatureCan add force or zero changes.

Supporting scope: Zhou et al. (2024): tension sensor array for cable-driven robots ↗

05 / ENGINEERING DECISION

Build a validation matrix, not one fitted curve.

Use a local force reference at the quantity you intend to infer, and record its calibration scope and uncertainty. Compare at multiple sheath shapes and both motion directions, with held loads and the intended speed range. Keep fitting data separate from validation data.

The sensor-array research by Zhou and colleagues reports different loading and unloading behavior in a tendon-sheath setup. It motivates testing direction history; its measured coefficients and results do not characterize a different hand or MT-ILC sensor.

A starting test matrix; choose actual values for the mechanism.
DimensionIncludeRetain in the record
RoutingRepresentative low/high curvature and transitionsPose, bend geometry and sensor location.
DirectionPulling, releasing and reversalsSeparate trajectories and dwell history.
TensionPretension plus useful incrementsLocal reference, zero and loading order.
SpeedHeld and intended moving conditionsVelocity, timestamps and filtering.
ValidationUnseen posture / cycle conditionsResiduals against a reference, not only fit error.

Supporting scope: Zhou et al. (2024): tension sensor array for cable-driven robots ↗ · Single tendon-sheath system with time-varying parameters (2025) ↗

06 / ENGINEERING DECISION

Worked example: check an increment in electrical units.

Assume a hypothetical 50 N sensor produces 2 mV/V at rated force and uses 5 V excitation. Its nominal full-range change is 10 mV, or 200 microvolts per newton. A 0.20 N increment produces 40 microvolts under a linear approximation. If the complete chain has 4 microvolts RMS noise in the stated measurement bandwidth, its input-referred force noise is 0.02 N RMS.

That is not an accuracy or pass/fail claim. Calibration uncertainty, friction, attachment loading and zero drift remain separate. Record the bandwidth and observation interval with the noise number; an ADC bit count alone cannot substantiate the result.

Illustrative signal budget; no hardware result is claimed.
Assumption / calculationValue
Nominal sensor range / output50 N / 2 mV/V
Excitation / full-range change5 V / 10 mV
Increment / signal change0.20 N / 40 microvolts
Assumed in-band noise / force equivalent4 microvolts RMS / 0.02 N RMS

Supporting scope: NI-DAQmx: Bridge Sensor Scaling ↗

07 / ENGINEERING DECISION

Preserve independent measurements and useful timing.

Independent tendons need independently recoverable measurements. A multiplexed converter can provide separate values without simultaneous sampling or electrical isolation. Request per-channel sample rate, scan order, timing skew, timestamps, filtering, latency and dropout behavior, rather than only the converter’s aggregate rate.

For illustration, 16 channels × 1,000 samples/s × 3 bytes/sample require 48,000 bytes/s of sample payload before headers, timestamps and transport overhead. This arithmetic does not establish a board’s usable throughput or a controller update rate.

Independent values can preserve channel identity. Multiplexing, timing skew and electrical isolation are separate specifications.Original educational schematic. Refer to the adjoining equations, assumptions and accessible data tables.Sensor 1Local force 1Measurement 1Calibration + timestampF1Sensor 2Local force 2Measurement 2Calibration + timestampF2Sensor 3Local force 3Measurement 3Calibration + timestampF3
Independent values can preserve channel identity. Multiplexing, timing skew and electrical isolation are separate specifications.
  1. Calibrate the channel with its actual sensor and cable association.
  2. Align reference and sensor timestamps before comparing moving trajectories.
  3. Test channel skew with a shared time-varying input appropriate to the hardware.
  4. Test missing samples, saturation and stale-data handling before closing the loop.

Supporting scope: NI-DAQmx: Bridge Sensor Scaling ↗

08 / ENGINEERING DECISION

Request the sensor and acquisition chain as one defined system.

Send the measurement location, pretension and peak load, minimum increment, attachment sketch and available envelope. Include channel count, per-channel rate, acceptable latency and the controller interface. Ask for model-specific noise, calibration, overload and cable evidence.

The existing tendon/actuator application page covers the broader system request; this guide supplies a transmission-model and validation method. Neither page establishes clinical suitability or a validated robot safety function.

Resolve the fit, signal and calibration questions.

Can proximal tendon tension be used as fingertip force?

Only through a validated model of transmission, joint geometry and other forces. Friction and changing moment arms can make a local tension reading differ from the desired contact force.

Can I identify friction from one held load?

One held value does not identify direction history, curvature dependence or dynamic behavior. Include several loads, postures and both motion directions, then validate on separate conditions.

Should the exponential be inverted when the tendon releases?

Do not apply one pulling-case equality blindly. Stick-slip, preload and direction reversal can produce history-dependent behavior; establish the applicable model from the mechanism and test data.

Does pretension count against sensor capacity?

Yes. The sensor sees the total local force, including pretension and transients. Range and directional protection must cover the actual load case.

Does a 16-channel ADC sample all tendons simultaneously?

Not necessarily. It may scan channels sequentially. Confirm per-channel rate and skew, as well as whether simultaneous conversion or hardware synchronization is required.

Are the calculated force and noise examples measured MT-ILC results?

No. They are explicitly assumed examples for planning a measurement budget. Request the supplied configuration’s verified specifications and sample data.

ENGINEERING RFQ / SAMPLE REQUEST

Send the load case.
Define the interfaces.

Include both thread ends, working and peak force, available space and the signal your controller expects.

Company and university email domains are preferred. Prototype and research inquiries are welcome.

By submitting, you agree to processing this request under our privacy policy.