Contact Us 
7-DOF Force-Controlled Robot Arm for Humanoid and Embodied AI Platforms
This product is a 7‑DOF force‑controlled robot arm built for humanoid robots and embodied‑AI platforms. It features lightweight construction, joint‑level force sensing, a cross‑axis wrist, plus SDK and ROS2 developer interfaces. Target use cases include research, data collection and application development. Configurations must be validated project‑by‑project.
Core Advantages
- Joint‑level force sensing and collision detection Joint torque sensors enable collision detection. Power‑off holding brakes prevent uncontrolled motion. These are safety‑related components only. A full application‑level risk assessment is still mandatory for complete safety implementation.
- Lightweight design with high payload‑to‑weight ratio Compact integrated joints reduce arm mass. Lower arm weight helps preserve mass budget, balance and runtime for host humanoid or mobile platforms. Overall system performance depends on the full system setup, not arm weight alone.
- 7‑DOF humanoid configuration with cross‑axis wrist Kinematically similar to a human arm. The cross‑axis wrist expands end‑effector orientation range. Actual reachable poses are constrained by mounting geometry, self‑collision limits and host‑platform structure.
- Full‑joint force control High‑precision force sensing on every joint supports contact‑sensitive tasks such as precision assembly. Force‑control performance varies with configuration and test conditions.
- Open developer ecosystem Native SDK and ROS2 support, plus built‑in camera cabling for vision integration. Software compatibility must be verified against the customer’s existing software environment.
Photo
Application Scenarios
The following scenarios describe how buyers use the arm and what conditions apply to each application.
Humanoid Robot Development
- Tasks: Dual‑arm or single‑arm manipulation, tool and object interaction, upper‑body integration on humanoid platforms.
- Required configuration: Mounting interface, self‑collision margins, center of gravity, power budget, communication latency, payload profile.
- Verification: Payload capability across required poses and platform‑level stability under the target duty cycle.
Embodied AI Research
- Tasks: Policy validation, teleoperation and demonstration, multimodal data collection, model deployment.
- Required configuration: Control modes, data frequency and timestamping, SDK and ROS2 environment, sensor synchronization.
- Verification: Data quality, control loop latency, and reproducibility of recorded trajectories for the training pipeline.
Dual‑Arm Mobile Platform Integration
- Tasks: Mobile‑base‑mounted dual‑arm operations, coordinated manipulation, shared workspace tasks.
- Required configuration: Overall system stability, power budget, emergency stop, safety zones, dual‑arm coordination logic.
- Verification: Dynamic stability during manipulation and emergency stop response under the target operating conditions.
Precision Assembly Test Cell
- Tasks: Insertion, alignment, contact‑based assembly operations.
- Required configuration: Fixtures, vision system, force‑control strategy, process force thresholds, cycle time targets.
- Verification: Process force profiles, insertion success rate, and cycle time against application targets.
Evaluation Process
| Step | Activities |
| 1. Requirements review | Collect host‑platform layout, required payload, end‑effector concept, target tasks, power supply, controller environment, and preferred ROS2 or API workflow |
| 2. Interface review | Assess mechanical mounting, electrical, control, vision, EOAT, and safety compatibility |
| 3. Simulation and testing | Evaluate reachable poses, force‑control performance, and application feasibility |
| 4. Configuration confirmation | Define final arm configuration, accessories, and integration scope |
| 5. Delivery and support | FAT/SAT as applicable, documentation, training, and remote or on‑site support |
Deliverables
| Deliverable | Availability |
| Product datasheet | Available after configuration confirmation |
| CAD / URDF files | Available after confirmation |
| SDK and documentation | Available for confirmed compatible environments |
| Wiring and interface documentation | Available after configuration confirmation |
| Test records | Per project scope and agreed acceptance criteria |
| Warranty and after‑sales support | 12‑month warranty; support scope confirmed per project |
FAQ
Q1: What information is needed to evaluate platform compatibility?
Share your host‑platform CAD or layout, mounting surface, power supply, controller environment, target tasks, payload and EOAT details, required workspace, cable routing, and safety requirements. Our team can coordinate a technical fit review covering mechanical, electrical, control, vision, and application requirements.
Q2: Is the 5 kg payload available throughout the full workspace?
Final payload capability must be checked against the EOAT mass, load center, inertia, required poses, acceleration, and motion profile. Payload may vary with arm configuration, joint angles, and end‑effector characteristics. A payload assessment should be conducted for the specific application before confirming feasibility.
Q3: Which ROS2 versions and operating systems are supported?
Specific ROS2 distributions, operating systems, API languages, and communication protocols should be confirmed against the customer’s software environment during integration planning. General SDK and ROS2 support is available; verified compatibility details are provided after reviewing the target system.
Q4: What control modes and data interfaces are available?
Control modes are confirmed based on the selected controller configuration and application requirements. Common force‑control arm modes include position, velocity, and torque control. Specific modes, data frequencies, and API details should be confirmed during technical review.
Q5: Can cameras and end effectors be integrated?
The arm includes integrated camera cabling and supports vision sensor integration. Camera and EOAT compatibility depends on mounting interface, power, communication, weight, and form factor. Specific sensor and gripper models should be reviewed during integration planning.
Q6: Can the arm be used around people?
Joint torque sensing and collision detection support contact detection and force‑limited control strategies. However, these features do not automatically mean the application is safe for human‑robot collaboration without additional measures. The final safety concept must be determined through an application‑level risk assessment that accounts for the end‑effector, workpiece, speed, force, environment, and applicable local safety requirements.
Q7: How are force‑control accuracy and bandwidth defined?
Force‑control accuracy of ≤ 0.15 N / ≤ 0.05 N·m and bandwidth of > 10 Hz are based on the arm’s joint‑level force sensing architecture. Detailed definitions, including measurement positions, test conditions, configurations, and validation data, should be confirmed during technical review. These values should not be used as application‑critical specifications without understanding the test conditions and applicable configurations.
Q8: What is included in evaluation, delivery, and support?
Evaluation includes a technical fit review of mechanical, electrical, control, vision, and application requirements. Delivery scope includes the configured arm, agreed accessories, and documentation. Support includes a 12‑month warranty, with training, remote, or on‑site support available per project agreement. Specific deliverables and exclusions are confirmed during order processing.
