TESOLLO fingertip F/T option
Optional fingertip configuration, not a claim about the shipped bill of materials.
6-axis option; part number unspecified
TESOLLO ↗TESOLLO DG-5F-M
Separate the direct ROS control path from the x86-64 SDK bridge, and specify optional fingertip sensing and wrist configuration before ordering.
DROID RESEARCH · SOURCES CHECKED
Does a ROS 2 label mean every DG-5F-M software path runs on a Jetson?
No. TESOLLO documents a precompiled SDK bridge for x86-64 only and says to exclude it on ARM64. The direct ros2_control path uses separate hardware and TCP packages. That offers a different integration route, but this review does not establish a tested Jetson configuration.
TESOLLO ↗ TESOLLO ↗Hardware and interface evidence
Original units and conditions are retained. A published interface does not establish a completed or independently tested integration.
| Field | Reported value | Conditions and source |
|---|---|---|
| Actuation | 20 independently actuated joints | Four per finger, with one integrated actuator per joint. TESOLLO ↗ |
| Input supply | 24 V | Nominal specification; confirm allowable tolerance, wiring and transients in the delivered manual. TESOLLO ↗ |
| Maximum current consumption | 10 A | Manufacturer maximum, not typical operating current or average energy consumption. TESOLLO ↗ |
| Reported mass | 1,763 g | Product-page figure; selected wrist and sensor options must be confirmed. TESOLLO ↗ |
| Communication | Modbus RTU/TCP; Ethernet TCP/IP | The ROS hardware driver requires Developer Mode and its custom Ethernet protocol, not the Operator Mode Modbus path. TESOLLO ↗ |
| Reported control frequency | 250 Hz | Product control-frequency claim, not measured glove-to-actuator latency. TESOLLO ↗ |
| Fingertip options | 6-axis F/T, 3-axis force or tactile | Optional configurations; do not assume these sensors are included in the quoted base hand. TESOLLO ↗ |
| ROS 2 software | Humble and Jazzy listed; Lyrical experimental | The repository says Lyrical is not validated on hardware. Pin model and common-package submodules. TESOLLO ↗ |
What this means for the control loop
Droid’s analysis of the cited documentation:
- Choose the software path before buying the host. Excluding the x86-only bridge removes one documented binary dependency; it does not prove that the remaining controller is validated on your ARM64 board.
- Specify the fingertip sensor and wrist as line items. Optional sensing changes the data available for contact feedback, and the Short Wrist variant does not inherit every peripheral feature.
- The manufacturer's MANUS example maps ergonomic glove values into joint commands. Its rule-based scaling needs operator and task calibration; it is not evidence of autonomous grasp success.
Documented components and software paths
Included sensing, optional hardware and software dependencies are different relationship types. These records do not infer undisclosed suppliers or part numbers.
TESOLLO fingertip tactile option
Confirm the model-specific tactile hardware and software interface.
Model-specific configuration to confirm
TESOLLO ↗TESOLLO SDK-to-ROS bridge
Optional SDK bridge uses an x86-64 library. The direct ROS hardware path is distinct.
Workspace 1307f7d; x86-64 precompiled library
TESOLLO ↗MANUS ROS stream → DG-5F-M
TESOLLO publishes a ROS 2 retargeting node that maps MANUS ergonomic data into DG5F joint references. The model-specific package is identified as DG-5F-M by its parent workspace.
The example does not identify an exact MANUS glove or firmware combination. It is a rule-based mapping with calibration factors, not evidence of a tested production deployment or autonomous task success.
Inspect the retargeting evidence →Still to establish
- Exact hardware, wrist, fingertip and firmware configuration
- Validated ARM64 host and controller build
- Mounting pattern and arm payload margin for the complete tool
- Delivered price and measured task performance
Before enabling the full workflow
- Match the physical hand and wrist variant to the model files.
- Verify Developer Mode and Ethernet for the direct ROS driver.
- Confirm optional sensors are fitted and exposed by the selected API.
- Measure timing, contact behavior and recovery with the real task.
Source record
- TESOLLO ROS 2 workspace and architecture limits ↗TESOLLO · Commit 1307f7d; pinned per-model submodules · Checked 2026-11-10
- DG-5F-M model packages ↗TESOLLO · Submodule commit 9e9af12 selected by workspace 1307f7d · Checked 2026-11-10
- ROS 2 connection and device-mode prerequisites ↗TESOLLO · Developer Mode + Ethernet path; model-specific panel differences · Checked 2026-11-10
- MANUS stream to DG5F retargeting ↗TESOLLO · Commit 9e9af12; glove model and firmware unspecified · Checked 2026-11-10
- DG-5F-M product specification ↗TESOLLO · DG-5F-M; Short Wrist is a separate option · Checked 2026-11-10
START WITH THE WORKFLOWBring us the task.
Request a project review Bring us the task.
Let’s find the fit.
Share your environment, the job to be done, and the outcome you need to measure.