The literature is used to list questions, not to borrow success rates. Questions related to the wheeled humanoid teleoperation base unit are: whether the action space equals the publicly stated degrees of freedom of the follower or leader, whether the observation equals the cameras on the checklist, whether the chassis moves, whether end-effector open/close is in the vector, and whether timestamps are agreed separately.
Document Location
ALOHA discusses dual-arm master-slave control and action chunking, Mobile ALOHA discusses mobile dual-arm, Diffusion Policy discusses imitation-learned visuomotor policies, UMI discusses a handheld gripper rather than a full platform, and Open X-Embodiment discusses pooling across robots, where the embodiment must be labeled. These sentences can be written into the "source of questions" section of a proposal. Do not copy the authors' success rates, sample counts, or costs.
The wheeled humanoid teleoperation body can only answer what has already been written on the product page: total active degrees of freedom 21, broken down as dual arms 14, waist 3, legs 2, neck 2. The vision system is listed as binocular depth / RGB optional. Wide-angle cameras: 130° FOV × 3, located at chest / back / chassis. The LiDAR is a single-line laser with detection range greater than 40 m (90% reflectivity). The voice interaction module is a ring of 6 microphones, optional. Depth camera versions: data acquisition version Orbbec 335LG; standard version Intel RealSense D405; optional Intel RealSense D435. A multi-DoF dexterous hand or gripper can be added to the end effector depending on the task. The page states compatibility with grippers and dexterous hands from Aoyi, BrainCo, Zhixing, and others, as well as the RX75, RM75, and RM65 robotic arm platforms. Compatibility is not a standard-configuration list. All other questions remain unanswered until a written configuration is provided.
Do not write "using the system from the above paper." TOBI does not have the equipment list for those experiments, and the wheeled humanoid teleoperation body is not the robot in those papers.

How to Use This Page in This Version
The literature section of the proposal uses a question checklist, not a scorecard. The checklist has five questions: Is the action space equal to the degrees of freedom or the master–slave mapping published for the wheeled humanoid teleoperation platform? Are the observations equal to the cameras listed in the checklist? Is the chassis included in the action space? Is the end-effector open/close listed separately? Are timestamps handled separately? For any of the five questions that can be answered from the product page, the answer must be the original sentence. Total active degrees of freedom: 21, split as 14 for the dual arms, 3 for the waist, 2 for the legs, and 2 for the neck. The vision system is listed as binocular depth / RGB optional. Wide-angle cameras: 130° FOV × 3, located on the chest / back / chassis. The LiDAR is a single-line laser with a detection range greater than 40 m (at 90% reflectivity). The voice interaction module is an optional ring of 6 microphones. Depth camera versions: the data-capture version uses Orbbec 335LG; the standard version uses Intel RealSense D405; Intel RealSense D435 is optional. A multi-degree-of-freedom dexterous hand or gripper can be added to the end effector depending on the task. The page states compatibility with grippers and dexterous hands from AYI, BrainCo, Zhixing, and others, as well as with the RX75, RM75, and RM65 robotic arm platforms. Compatibility is not a standard-configuration list. Locomotion speed: 0.1–1.5 m/s. Turning radius 690 mm, specified as in-place rotation.
For anything that cannot be answered, write "not published." Do not fill in blanks with the experimental setups of ALOHA, Mobile ALOHA, Diffusion Policy, UMI, or Open X-Embodiment. Those works use their own robots and their own success definitions. TOBI is not the author of those experiments, and the wheeled humanoid teleoperation body is not the platform in those papers.
The only connections that can be written are methodological: leader-follower teleoperation requires the leader and follower to share the same action space; mobile manipulation requires recording the chassis; the handheld gripper route is deliberately not a whole-machine; cross-robot aggregation requires annotating embodiment differences. These are research questions derived from reading the literature, not performance guarantees.
The last sentence of the literature section is fixed as: "Success rates, data duration, and cost are per the original papers and are not transcribed to this product." Then direct the reader back to /product-body-humanoid.html, not to an external PDF as if it were a specification sheet.
Line-by-Line Verification
Degrees of freedom. Total active degrees of freedom 21, broken down as dual arms 14, waist 3, legs 2, neck 2. This row only states the number of joints and body parts that have already been made public. It does not evaluate intelligence, and it does not automatically include the waist, legs, neck, or whole-machine total that are not explicitly named on the page. When writing the action vector, only build channels for body parts listed in this row; body parts not listed remain blank. Do not write blanks as 0, because 0 would be treated by training scripts as a real angle. Do not fill in degrees of freedom from another device to make this row add up. If the master-slave joint order is not given on the page, mark it as pending written configuration confirmation; do not number it yourself. For action space questions in the literature, answer using this row, not using the joint count of the robot in the paper. Build action vector channels only for body parts named in this row; leave unnamed body parts blank, not 0.
Payload and mass. Single-arm payload 5 kg. Total unit weight is approximately 125 kg, which is not the single-arm payload. The numbers on this line must be read with their subject: rated, self-weight, total unit mass, envelope, friction, or gripping force. If the subjects differ, they cannot be merged into a single number, nor can conversions not given on the page be performed. If objects in the field are heavier, the specification cannot be changed retroactively; a larger specification also does not prove that every grasping method reaches that limit. The tool mass is undetermined; do not write the arm's rated payload as the graspable object mass. The acceptance checklist retains the original units. Object weights from papers cannot be written as already verified on this line. During acceptance, read the subject first and then the number; if the subjects do not match, split into two lines.
Dimensions and scale. Overall dimensions 570 × 465 × 1680 mm. Chassis width and shoulder width are within 465 mm. This row describes form factor or structural scale, used to check doorways, elevators, tabletops, or transport; it is not an operating height and not a reach. Do not add it to the vertical range. If the diagram shows protrusions, antennas, or a person's standing position not listed in this row, note separately that they are not part of the specification. If weight appears in an adjacent row, do not write it into the dimension sentence. Dimensions from a paper's platform cannot replace this row. Doorways, elevators, and transport are checked against form factor only; do not treat this row as an operating height.
Operating range. Vertical reach 2100 mm. Horizontal reach 1818 mm, excluding the end effector. This row describes the range the hand or lift can reach; the definition must follow the original sentence: vertical working range, reach, motion radius, or stroke—these cannot be added together or renamed. If "excluding end effector" is written, it must remain in the figure caption. If the original text does not specify units, keep the note "units not specified"; do not delete it for tidiness. Workspace definitions from a paper cannot replace this row's definition. The figure caption retains the range definition from the original sentence, as well as words like "excluding end effector" or "units not specified."
Motion. Motion speed 0.1–1.5 m/s. Rotation radius 690 mm; the specification refers to in-place rotation. This row describes how the ground base or main arm moves. Four-wheel steering, four-wheel drive, differential drive, in-place rotation radius, and rotational speed are terms for different mechanisms and cannot be substituted for one another. The published speed is a capability, not a recommended demonstration speed; demonstration can be slower, but the slower speed is recorded under experimental conditions and is not written back into the specification. Do not borrow slope-climbing or positioning figures from other pages for pages that do not list them. Whether mobile manipulation is viable is determined first by whether this row includes ground motion, not by whether the paper used a mobile base. Demonstration speed can be lower, but the lower speed is recorded under the operating conditions and does not change the published capability in this row.
Power. Battery 40 Ah (BMS). Charging time approximately 2 hours. Approximately 2 hours refers to charging, not runtime; the page does not specify runtime in hours. This line retains only the electrical terms that appear on the page: voltage, capacity, runtime, charging, current, or power. If there is no "hours," write runtime not specified; do not fill in the blank with hours from a neighboring page. Do not rename charging time as runtime. Rated and maximum values must be listed in separate columns. Keep "approximately" for approximate values. Do not sum the ampere-hours of multiple devices and state it as one device's battery. The paper does not provide runtime for this line. Hours, charging, or current that do not appear should remain as not specified; do not copy them in from a neighboring page.
Sensing and computing. The vision system is listed as binocular depth / RGB optional. Wide-angle cameras: 130° FOV × 3, located at chest / back / chassis. The LiDAR is a single-line laser with detection range greater than 40 m (90% reflectivity). The voice interaction module is a ring of 6 microphones, optional. Depth camera versions: data acquisition version Orbbec 335LG; standard version Intel RealSense D405; optional Intel RealSense D435. This row inventories the items already specified in sensing, computing, or communication, and preserves words like standard, standard configuration, optional, and selectable. An optional item that is not checked does not count. If the cover conflicts with the list, cite the list while not pretending the cover statement does not exist. Headsets and gloves do not enter this row. Processors, storage capacity, or camera channel counts that are not written out must not be drawn into the system diagram. The number of cameras in a paper is not this row's channel count. Optional sensors not purchased do not enter this data dictionary.
End effector. A multi-DoF dexterous hand or gripper can be added to the end effector depending on the task. The page states compatibility with grippers and dexterous hands from Aoyi, BrainCo, Zhixing, and others, as well as the RX75, RM75, and RM65 robotic arm platforms. Compatibility is not a standard-configuration list. This row describes where contact or grasping occurs. Quick-change, compatible, and recommended are not models included in the box. The ring gripper on the main arm is not an end-effector gripper. Force, stroke, and payload remain as stated in their respective rows and are not merged into a single system metric because they are mounted on a particular body. Flange and protocol mappings that are not specified should be marked as pending confirmation, not plug-and-play. A gripper from a paper is not an end effector already delivered in this row. "Supports" or "compatible" without a model name cannot be treated as delivered.
Boundaries. The upper body and wheeled chassis are a modular structure. How to connect them to other chassis after disassembly is confirmed per the project interface; do not state in the public table that they are already connected. This line is a deliberate boundary on the page: another model, another column, another product page, or an interface that still requires project confirmation after modularization. The boundary is not a defect note; it is there to prevent verbally buying two pages as one. When writing a proposal, copy the boundary into "Not included in this scope." If equipment not included is added later, open a new configuration sheet instead of going back to change the body name in the old sample. Embodied differences are exactly the boundary to preserve; do not delete them for the sake of "unification." Equipment within the boundary must be ordered separately; do not rename the old sample to say it already includes it.
Configuration column. Both the voice module and depth camera version have optional rows. Optional items are not written into the delivery if not checked. The end-effector brand must be named in the configuration sheet; do not write "compatible means already included." This row distinguishes standard, recommended, and optional. Recommended and optional items are not delivered if not checked. If the standard row conflicts with the parameter table row, keep both rows and use "locked for this order" to indicate which one is actually delivered, rather than striking out one row in the order without signing off. Prices and lead times are not written into this row's paraphrase. Unchecked configurations must not be written as the same system as in the paper. Unchecked recommended and optional items are written as not delivered on the order.
Excerptable. The following can be copied into an appendix: 21 (14+3+2+2); 570×465×1680 mm; approximately 125 kg; 465 mm width limit; vertical reach 2100 mm; horizontal reach 1818 mm (excluding end effector); in-place turning radius 690 mm; 0.1–1.5 m/s; single arm 5 kg; 40 Ah; charging approximately 2 hours. This row is the type of content that can be pasted into an appendix: it has a subject, includes units, and can be traced back to the original sentence on the product page. When pasting, preserve words like "approximately," "excluding," "not specified," "optional," and "recommended." Do not convert units and keep only the result. If the same number has different meanings on two pages, write it as two separate rows in the appendix. Do not mix test protocols into specification excerpts. A proposal may state the source of a question but must not state a paper's success rate. When pasting into an appendix, include words like "approximately," "excluding," and "optional" along with the values.
Do not write. Do not write "charging approximately 2 hours" as "battery life 2 hours." Do not write the folding model's 20 DoF or approximately 6 hours onto this unit. Do not write the lift model's 900 mm as this unit's lift stroke. This row is a negative statement for review purposes. It does not describe what the equipment can do; it only prevents hours, degrees of freedom, payload subjects, or cover slogans from neighboring pages from being written in. If a negative statement is triggered, revert to the original sentence on the product page; do not interpret it as "close enough." Do not write in success rates from external papers or total hours not published on this site. Sentences of the form "using the system from that paper" are prohibited. If a draft search triggers a negative statement, revert to the original sentence on the product page.
| Projects | Public-Facing Positioning of This Page |
|---|---|
| Degrees of Freedom | Total active degrees of freedom: 21, broken down as dual arms 14, waist 3, legs 2, neck 2. |
| Load and Mass | Single-arm payload 5 kg. Total unit weight is approximately 125 kg, which is not the single-arm payload. |
| Form Factor and Scale | Overall dimensions 570 × 465 × 1680 mm. The chassis width and shoulder width are kept within 465 mm. |
| Operating Range | Vertical reach 2100 mm. Horizontal reach 1818 mm, excluding the end effector. |
| Motion | Motion speed 0.1–1.5 m/s. Turning radius 690 mm; the specification refers to in-place rotation. |
| Power | Battery 40 Ah (BMS). Charging time approximately 2 hours. The approximately 2 hours refers to charging, not runtime; the page does not state runtime in hours. |
| Perception & Compute | The vision system is listed as binocular depth / RGB optional. Wide-angle camera 130° FOV ×3, located on the chest / back / chassis. The LiDAR is a single-line laser with detection range greater than 40 m (90% reflectivity). The voice interaction module is a ring-shaped 6-microphone array, optional. Depth camera versions: data collection version Orbbec 335LG; standard version Intel RealSense D405; optional Intel RealSense D435. |
| End Effector | A multi-degree-of-freedom dexterous hand or gripper can be added to the end effector depending on the task. The page explicitly states compatibility with grippers and dexterous hands from Aoyi, Qiangnao, Zhixing, and others, as well as the RX75, RM75, and RM65 robotic arm platforms. Compatibility is not a standard configuration list. |
| Boundary | The upper body and wheeled chassis are modular. How to connect to other chassis after separation must be confirmed per the project interface; do not state in the public table that it is already connected. |
| Configuration Panel | Both the voice module and depth camera versions have optional rows. Optional items are not included in unchecked deliveries. The end-effector brand must be specified by name in the configuration sheet; do not write "compatible means already included." |
| Excerptable | Attachment copy: 21 (14+3+2+2); 570×465×1680 mm; approximately 125 kg; 465 mm maximum width; vertical reach 2100 mm; horizontal reach 1818 mm (excluding end-effector); in-place rotation radius 690 mm; 0.1–1.5 m/s; single arm 5 kg; 40 Ah; approximately 2 hours of charging. |
| Do not write | Do not write "approximately 2 hours of charging" as "2 hours of battery life." Do not attribute the folding model's 20 DoF or approximately 6 hours of battery life to this unit. Do not write the lifting model's 900 mm as this unit's lifting stroke. |

Relationship to Public Methods and Adjacent Pages
Placing the product in the literature is to illustrate what data capture problems look like, not to borrow the paper's experimental conclusions. Public works that can be explicitly cited include: dual-arm master-slave teleoperation and action-chunked imitation learning as represented by ALOHA; mobile dual-arm demonstration as represented by Mobile ALOHA; learning visuomotor policies from demonstrations as represented by Diffusion Policy; handheld gripper capture as represented by UMI, which is deliberately not a full robot; and cross-robot data aggregation as represented by Open X-Embodiment, provided the embodiment is labeled.
These works each use their own robots, tasks, and success definitions. TOBI did not participate in those experiments. This article does not transcribe their success rates, number of data records, or dollar costs. When readers need those figures, they should read the original papers.
What is useful for this product is only the checklist: whether the action space matches the slave end, which camera the observation comes from, whether the chassis moves, whether end-effector open/close is in the action vector, whether timestamps are aligned, and whether the robot unit identifier is written into the samples. Items on the checklist that the product page does not answer remain unanswered.
This article uses the literature to lay out the questions, then answers the ones that can be answered using the product's public specifications.
Before handing off to a colleague
When finalizing the literature section, delete all percentages and hours unless the sentence explicitly states "the following figures belong to the original paper and are not measured values of this product", and do not place the figures next to this product's specifications. Only the question list is retained. Questions that can be answered from the product page have their answers rewritten as the original sentences; questions that cannot be answered are left blank. Check the last sentence for an erroneous statement such as "the system adopted from that paper". If such a sentence exists, delete the section rather than adding a footnote to justify it. The literature section is limited to one page. Exceeding one page usually means experiment details have started to be restated. Delete the experiment details and keep only the questions. Questions are answered with original sentences from the product page or left blank. The footer is fixed with one sentence: the success rates, data scale, and costs of external papers belong to the original authors, are not measured values of this company, and do not constitute a test of the equipment in this document. A literature section without this footer sentence is not published.
First, the literature section should not exceed the question list.
Second, do not copy success rates.
Third, use the original sentence when it can answer the question.
Fourth, leave blank what cannot be answered.
Fifth, delete "adopts the system from that paper."
Sixth, the footer states that the figures belong to the original authors.
Continue Reading
- 01 Task Boundaries
- 02 Specification Standards
- 03 Degrees of Freedom
- 04 Payload & Self-Weight
- 05 Workspace
- 06 Locomotion Method
- 07 Perception and Computing
- 08 Power Specifications
- 09 Data Recording
- 10 Time Alignment
- 11 End-Effector Boundaries
- 12 Site Constraints
- 13 Configuration Sheet
- 14 Three-Way Comparison
- 15 Literature References
- 16 Master-Slave Workstation
- 17 Acceptable Deliverable Statements
- 18 Prohibited Conflations
- 19 On-Site Deployment
- 20 Evaluation Path
Back to Product Center View this product page
This article was written on October 3, 2026, for selection and specification verification purposes. Device parameters are subject to the product page tables and do not constitute a supply commitment. External papers only illustrate how problems are framed in the industry; their success rates and data scales belong to the original authors' experiments and are not TOBI's measured results. Phone: +86 137 5502 0164.