Count vision and computing channels from the list, not from cover slogans. Vision system: binocular depth / RGB, optional. Wide-angle cameras: 130° FOV × 3, located at the chest / back / chassis. LiDAR: single-line laser, detection range greater than 40 m (at 90% reflectivity). Voice interaction module: ring of 6 microphones, optional. Depth camera versions: data-acquisition edition Aobi 335LG; standard edition Intel RealSense D405; optional Intel RealSense D435. Retain the three terms: standard, included as standard, and optional. An optional item not selected is not treated as already present.
Perception & Compute
Head-mounted E6 and E2 are a separate image stream worn on the human body and are not included in the sensor list of the wheeled humanoid teleoperation robotic platform. The human first-person view and the platform cameras must be kept in separate files. E2 has no on-board SLAM; the pose is reconstructed offline. E6 training reads the raw frame rate, not the preview. These constraints belong to the head-mounted page; here they are only noted to prevent them from being counted toward the platform's sensor streams.
The depth, lidar, and ultrasonic used for navigation are not the same set as the head or hand cameras. When writing them into a dataset, use different topic names. Identical names will cause the training script to treat the obstacle-avoidance image as an in-hand image.
Copy only the rows that exist for the computing platform. Having Orin 64G does not mean having a 1 TB solid-state drive; having 1 TB does not mean all adjacent pages have it. For products where the processor is not stated, do not draw a default compute board in the system diagram. The original text on the page is at /product-body-humanoid.html.

How to Use This Page in This Version
Archive the sensor list into four categories: standard / included as standard / optional / cover. Vision system: binocular depth / RGB, optional. Wide-angle cameras: 130° FOV × 3, located at the chest / back / chassis. LiDAR: single-line laser, detection range greater than 40 m (at 90% reflectivity). Voice interaction module: ring of 6 microphones, optional. Depth camera versions: data-acquisition edition Aobi 335LG; standard edition Intel RealSense D405; optional Intel RealSense D435. When archiving, remove optional and cover items from the standard category. Where the cover conflicts with the list, cite the list externally while retaining the note "the cover states it differently; it does not constitute delivery." Do not pretend the conflict does not exist, and do not let the cover win.
The computation row is archived separately. If "Orin 64G" is written, one must ask whether there is a solid-state drive capacity. Only if "1T" is written can "1T" be stated. For products where neither row is present, no computation board is drawn in the system block diagram. The processor in the head-mounted unit is not the processor of the embodiment itself.
Camera topic names must be decided before acquisition: head, hand, wide-angle, depth, and LiDAR must not share a single name. Navigation depth and hand RGBD are two separate channels even though both are called depth. When the wheeled humanoid teleoperation body page does not provide topic strings, mark the topic name as "project-defined, but must match the channel count in the list" — do not change the channel count to a number that is convenient for topic naming.
Head-mounted devices and gloves do not enter this list. They may be present in the same experiment, but the list should state "parallel human-side devices" to prevent training scripts from treating human images as body cameras. Synchronization is not resolved at this level; this level only prevents miscounting channels. Source: /product-body-humanoid.html.
Line-by-Line Verification
Degrees of freedom. The total active degrees of freedom for the whole body is 21, broken down as 14 for the two arms, 3 for the waist, 2 for the legs, and 2 for the neck. 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 named on the page. When writing the action vector, create channels only for the body parts present in this row; leave body parts that are absent blank. Do not write blanks as 0, because 0 would be treated by the training script as a real angle. Also do not fill in the degrees-of-freedom integer from another device after this row to make the numbers add up. If the master-slave joint order is not given on the page, mark it as pending written configuration confirmation and do not number it yourself. The joint count is not the camera stream count. The action vector creates channels only for the body parts named in this row; body parts not named are left blank and are not filled with 0.
Load and mass. Single-arm payload: 5 kg. Total unit weight: approximately 125 kg — this is not the single-arm payload. Every number in this row must be read together with its subject: rated, self-weight, total unit mass, envelope, friction, or gripping force. Numbers with different subjects must not be merged into a single figure, nor converted using any conversion not provided on the page. If field objects are heavier, do not retroactively change the specification; a larger specification also does not prove that every grasping method reaches that limit. Tool mass is undetermined — do not write the arm's rated payload as the graspable object mass. The acceptance sheet retains the original units. Load does not determine the vision configuration. During acceptance, read the subject first and then the number; if the subjects differ, split into two rows.
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 verify doorways, elevators, tabletops, or transport — it is not operating height, nor is it arm reach. Do not add it to the vertical range. If the diagram shows protrusions, antennas, or a human standing position not present in this row, note separately that these are not part of the specification. If weight appears in an adjacent row, do not write it into the dimension sentence. The form factor does not include the number of sensor installations. Doorways, elevators, and transport are verified against form factor only; do not treat this row as 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 wording: vertical working range, arm reach, motion radius, or stroke — these cannot be added together or renamed. If "excluding the end effector" is stated, it must remain in the figure caption. If the original text does not specify units, retain the "units not specified" note; do not delete it for tidiness. Field of view is not arm reach. The figure caption retains the range definition from the original sentence, as well as the phrases "excluding the end" or "units not specified."
Motion. Motion speed 0.1–1.5 m/s. Turning radius 690 mm, specified as in-place rotation. This row describes how the ground or the main arm moves. Four-wheel steering, four-wheel drive, differential drive, in-place turning radius, and rotational speed are terms for different mechanisms and cannot be substituted for one another. Published speed is a capability, not a recommended teaching speed; teaching can be slower, but a slower speed is recorded under experimental conditions and is not written back into the specification. Do not borrow slope climbing or positioning data from other pages if it is not written on this page. Chassis speed is not the sampling rate. Teaching speed can be lower, but a lower speed is recorded under operating conditions and does not change the published capability in this row.
Power. Battery: 40 Ah (with BMS). Charging time: approximately 2 hours. Approximately 2 hours refers to charging, not runtime; the page does not state runtime in hours. This row retains only the electrical terms that appear on the page: voltage, capacity, runtime, charging, current, or power. If "hours" is not stated, write that runtime is not provided; do not fill in from an adjacent page's hours. Do not rename charging time as runtime. Rated and maximum values must be listed separately. Approximate values retain "approximately." Do not sum the ampere-hours of multiple units and present it as one unit's battery. Computing platform power consumption does not belong in the battery row unless that row states it. Hours, charging, or current that do not appear remain as not provided; do not copy them in from an adjacent page.
Perception and computing. The vision system specifies binocular depth / RGB as optional. Wide-angle cameras: 130° FOV × 3, positioned on the chest / back / chassis. The LiDAR is a single-line laser with a detection range greater than 40 m (90% reflectivity). The voice interaction module is a ring of 6 microphones, optional. Depth camera versions: the data capture version uses Orbbec 335LG; the standard version uses Intel RealSense D405; Intel RealSense D435 is optional. This row inventories items already specified in the sensors, computing, or communications sections, and retains the terms standard, included, optional, and optional add-on. An unchecked optional item does not count. If the cover conflicts with the checklist, cite the checklist, while not pretending the cover statement does not exist. Head-mounted devices and gloves do not belong in this row. Do not draw processors, hard drive capacity, or camera channel counts into the system diagram if they are not specified. This is the primary row for channel counts and computing; standard and optional items must be established as separate topics. Optional sensors that have not been purchased do not enter this data dictionary.
End effector. 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 Aoyi, Qiangnao, Zhixing, and others, as well as the RX75, RM75, and RM65 robotic arm platforms. Compatibility is not a standard-configuration list. This row specifies where contact or grasping occurs. Quick-change, compatible, and recommended are not models included in the box. The ring fixture on the main arm is not an end-effector gripper. Force, stroke, and payload remain as written in their respective rows and are not merged into a single system metric because they are installed on a particular body. Flange and protocol mappings not provided should be marked as to be confirmed, not as plug-and-play. If the hand camera is included as standard or optional, do not write it as an attribute of the end-effector gripper. "Supports" or "compatible" without a model number cannot be treated as delivered.
Boundary. The upper body and wheeled chassis are a modular structure. How to connect after disassembly to other chassis is confirmed per project interface, and is not written in the public table as already connected. This line is a deliberately separated 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 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; do not go back and change the body name in old samples. The extra path on the cover goes in the remarks, not into the standard topic. Equipment within the boundary must be ordered separately; do not rename old samples to say it is already included.
Configuration column. The voice module and depth-camera version each have optional rows. Unchecked optional items are not included in the deliverable. The end-effector brand must be named explicitly in the configuration sheet; do not write "compatible, therefore included." This row distinguishes standard, recommended, and optional. Recommended and optional items are not delivered unless checked. If a standard row conflicts with a 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 sign-off. Price and lead time are not written into this row's paraphrase. If an optional depth-camera version or microphone is unchecked, no topic is created. Unchecked recommended and optional items are written as "not delivered" on the order.
Excerptable. Values that may 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 is the type of row that can be pasted into an appendix: it has a subject, has units, and can be traced back to the original sentence on the product page. When pasting, preserve "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 rows in the appendix. Do not mix test protocols into specification excerpts. The appendix should quote the original list sentence, not write "several cameras." When pasting into the appendix, paste the words "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 device. Do not write the lift model's 900 mm as this unit's lift stroke. This line is a negative statement for review purposes. It does not describe what the device can do; it only prevents hours, degrees of freedom, payload subjects, or cover slogans from adjacent pages from being written in. If a negative statement is hit, revert to the original sentence on the product page and do not interpret it as "close enough." Success rates from external papers and total hours not published on this site should likewise not be written in. It is prohibited to write "3-channel depth" as delivered unless the checklist's original sentence says exactly that. If manuscript retrieval hits 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
The perception configuration determines what the visuomotor policy can see, and also determines what the article cannot claim. The standard configuration, recommended configuration, and cover schematic are often not the same sentence. The lift model's cover once showed "3 depth + 2 wide-angle," while the standard configuration lists one D435 depth camera and two wide-angle cameras. In case of conflict, the standard configuration list prevails, and the conflict note is retained, to prevent sales from verbally presenting the cover number as delivered.
Chassis navigation sensing is a separate group: depth cameras, inertial measurement with encoders, LiDAR, safety bumpers, ultrasonic. They serve chassis obstacle avoidance and localization, not the in-hand camera at the wrist. If a wrist camera is included in the accessories, it must be listed on a separate line and must not be counted into the standard vision path. The compute platform likewise only lists what appears on the page. The folding model lists the core processor as Nvidia Jetson AGX Orin 64G, with no mention of a 1T solid-state drive. The lift model lists Nvidia Jetson AGX Orin 64G and explicitly states an additional 1T solid-state drive. The spec tables for the wheeled humanoid, kit, and gripper do not have this processor line; you cannot write "Orin across the entire series," nor copy the 1T solid-state drive to the folding model.
Head-mounted E6 and E2 are a separate visual pathway, worn on the human body, and are not part of the rig's standard checklist. The human-eye viewpoint and the rig camera viewpoint must be recorded in separate files. The nominal SLAM accuracy in the E6 spec sheet is not ground truth proven by public samples.
This article only inventories the sensing and compute listed on that product page, and points out which line is standard and which line is only a cover claim.
Before handing off to a colleague
Post the sensor list next to the capture computer. One topic name per channel, with "standard," "included," or "optional" copied next to each topic name. Optional topics that have not arrived should be removed from the capture configuration rather than left as empty topics. The extra channel count on the cover is written on a sticky note titled "not delivered." Next to the compute board, note whether the words "SSD capacity" exist; if not, do not attach a 1T label. If the head-mounted camera is recording at the same time, use a separate list to prevent the operator from inserting human images into the base unit topics. Run a diff between the topic configuration file and the product page list. Extra topics in the configuration file must be deleted or marked as project additions; they cannot remain under the standard list's name. Missing standard topics in the configuration file must either be added back or documented in the data notes as not captured, with the reason. Optional topics may only appear if they are checked off on the packing list. When the compute platform's disk capacity is not written on the page, the configuration file must not contain a capacity field, so it is not mistaken for a specification.
First, perform a gap check between the topic and the checklist.
Second, mark extra topics as additional or delete them.
Third, missing standard topics must be noted as not captured.
Fourth, do not create a topic for an unchecked optional item.
Fifth, do not write unavailable disk capacity into the configuration.
Sixth, use a separate checklist for head-mounted.
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.