SIX-COMPONENT SENSING / ENGINEERED TO INTEGRATE

6-axis force sensors.
Feel every direction.

6-axis force/torque sensors and 6-DOF force transducers for robot wrists, humanoid ankles and demanding test rigs.

Three forces in newtons. Three moments in newton-metres. One measurement chain, specified around your robot and your load case.

Fx · Fy · Fz / NMx · My · Mz / NmHXF SERIES
Conceptual thin disc force sensor with three cyan force arrows Fx Fy Fz and three orange torque arrows Mx My Mz
6-DOF load coordinates · conceptual geometry, not a production drawing
HUMANOID ROBOTICSCOLLABORATIVE ARMSPRECISION METROLOGYAEROSPACE & SUBSEA TESTING

01 / CHOOSE THE MECHANICAL ENVELOPE

6-axis force/torque sensors,
from fingertip tooling to test rigs

Start with the load path and space budget. Match the interface after reviewing all six force and moment channels.

Family figures are requested design envelopes, not released SKU specifications. Combined-load limits, weight and resolution require a configuration-specific drawing and calibration review.

02 / SIX AXIS FORCE SENSOR INTEGRATION

Less integration guesswork.
More useful force data.

A 6 dof force sensor is only one part of the chain. Specify the flange, electronic decoupling, frame convention, communication and filtering together.

01 Map simultaneous Fx, Fy, Fz and Mx, My, Mz loads.

02 Check diameter, thickness, bore and complete wrist mass.

03 Confirm digital output, timing and host-side integration.

Plan EtherCAT, CAN-FD, USB or RS485 ↗
Measurement chain from six bridge signals through a calibration matrix to force and moment data

Decoupling and timing architecture concept. 1–4 kHz output is a configuration target; bandwidth and latency require separate confirmation.

03 / ENGINEERING HANDOFF

Bring six-component loads
into your robot software

Define the wrench reference frame before closing a force loop. Changing the reference origin changes measured moments through the tool lever arm.

Review 6-axis load cell calibration ↗
ROS2 · geometry_msgs / WrenchStamped
# Integration target — not an available driver download
# After installing the confirmed firmware-matched package:
ros2 launch hexaforce_ft_driver sensor.launch.py

# Inspect six channels in the sensor reference frame
ros2 topic echo /hexaforce/wrench

Request tested ROS1 / ROS2 Humble or Jazzy support, C++ / Python examples and Windows GUI availability with your quotation. No HXF driver or SDK release has been published here yet.

BEFORE YOU SPECIFY

Six-channel selection questions

Does each family cover every listed range at every size?

No. Values are design targets across a family. The selected configuration needs its own six-channel range, mass, dimensional drawing, output option and calibration record.

Can I replace an ATI, Bota or OnRobot sensor directly?

Send the original part number, drawing and firmware/protocol details. Matching outer diameter alone does not establish bolt-pattern, connector, axis-sign or software compatibility.

How do I specify resolution and crosstalk?

State your minimum detectable force and moment, bandwidth and temperature range. Request per-channel noise, resolution and combined-load residuals at those settings; output bit depth alone is insufficient.

Are the shown diagrams product photographs?

They are original conceptual engineering illustrations. They do not establish a supplied model, hole pattern, physical test result or manufacturing certification.

DEFINE THE COMPLETE LOAD CASE

Send the force. Add the moment arm.

Include your six-channel loads, robot model, space envelope and preferred interface. Request a configuration-specific quotation and STEP drawing.

Start an engineering RFQ ↗