Pressing start at the same time is not a shared clock. If the wheeled humanoid teleoperation unit is used together with a head-mounted device, primary arm, and gripper, the configuration form must specify the master clock, alignment error, and frame-drop markers. The page makes no promise that PPS or serial-port time synchronization has been implemented. Powering on the wrist camera and the light ring at the same time is also not time synchronization.
Time alignment
Each sampling rate is copied from its own page. The recording frequencies of the glove, head-mounted imagery, and arm are not the same number, and do not invent a body frequency in this article. The vision system is written 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 (reflectivity 90%). 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. Here we only determine which sensors are on the list; do not rewrite the list into a single synchronization Hz.
The consequence of misalignment is that a visuomotor policy learns a misaligned causal relationship: in the image the hand has already closed, but the joint angles are still from the previous frame. Such samples are worse than missing samples, because they look complete.
Before the clock alignment scheme is written, fill the synchronization column of the recording sheet with "Not committed." Do not fill in "Aligned." /product-body-humanoid.html can be used to verify which devices the body has; the clock alignment protocol is not on that page.

How to Use This Page in This Version
The synchronization plan is a separate document, not written into the specification sheet of the wheeled humanoid teleoperation robotic platform, because the specification sheet does not commit to clock alignment. The document must contain six lines: who is the master clock; which slave devices are included; what signal is used for alignment; the maximum allowed misalignment; how dropped frames are marked; and who signs the record sheet. If the six lines cannot be written, the synchronization column remains "not committed."
Pressing start simultaneously only proves that a person wants them to go together; it does not prove that the time bases are the same. The wrist camera, light ring, head-mounted display, main arm, gripper, and chassis can share a single operator yet still each have their own clock. The vision system is listed as stereo depth \ / RGB optional. Wide-angle cameras: 130° FOV × 3, positioned on the chest \ / back \ / chassis. 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 capture edition Orbbec 335LG; standard edition Intel RealSense D405; optional Intel RealSense D435. This sentence only states which sensors are present; it does not state that they share a sampling instant.
Do not invent a sampling frequency for the base unit in this article. Gloves and head-mounted images have their own spec-sheet frequencies, and those frequencies must not be filled into the base unit row. The base unit row's frequency follows the written interface specification; if it is not on the page, leave it blank.
The handling rules for misaligned samples should be written down in advance: segments exceeding the allowed misalignment are discarded entirely, rather than truncated and still treated as aligned samples. Truncation creates training data that appears continuous but is actually causally incorrect. The rules go in the experiment plan, not into /product-body-humanoid.html, to avoid being mistaken for a factory commitment.
Line-by-Line Verification
Degrees of freedom. The full-body active degree-of-freedom count is 21, broken down as 14 for the two arms, 3 for the waist, 2 for the legs, and 2 for the neck. This line only states the number of joints and body segments that have been publicly disclosed. 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 building the action vector, create channels only for the body segments listed in this line; leave segments that are absent blank. Do not write blanks as 0, because 0 would be treated by the training script as a real angle. Do not fill in the degree-of-freedom integer from another device after this line 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; do not number it yourself. When the frequency of the joint channels is not given on the page, leave it blank; do not substitute the degree-of-freedom count for the frequency. Build action-vector channels only for the body segments named in this line; leave unnamed segments blank and do not fill in 0.
Load and mass. Single-arm load 5 kg. Total unit weight is approximately 125 kg, not the single-arm load. The numbers in this row must be read aloud 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 provided on the page be performed. If the actual object on site is heavier, this does not retroactively change the specification; a larger specification also does not prove that every grasping method reaches that limit. The tool mass is undetermined, so do not write the arm's rated load as the graspable object mass. The acceptance form retains the original units. Load is unrelated to the clock. During acceptance, read the subject first and then the number; if the subjects are inconsistent, split them into two rows.
Form and scale. Overall dimensions 570 × 465 × 1680 mm. Chassis width and shoulder width are kept within 465 mm. This line is about form or structural scale, used to check doors, elevators, tabletops, or transport; it is not operating height, nor is it reach. Do not add it to the vertical range. If the diagram shows protrusions, antennas, or a person's standing position not present in this line, 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. Form is unrelated to alignment error. Doors, elevators, and transport are checked only against form; do not treat this line as operating height.
Operating range. Vertical reach 2100 mm. Horizontal reach 1818 mm, excluding the end-effector. This line 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 caption. If the original text does not mark units, keep the note "units not specified"; do not delete it for tidiness. The range does not provide sampling timestamps. The caption retains the range definition from the original sentence, as well as the words "excluding end-effector" or "units not specified."
Motion. Movement speed 0.1–1.5 m/s. Turning radius 690 mm, specified as in-place turning. This line describes how the ground or 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 substitute for each other. The published speed is a capability, not a recommended teaching speed; teaching can be slower, but the slower speed is written into the experimental conditions, not written back as a specification. If the page does not mention slope climbing or positioning, do not borrow from another page. If both chassis and arm are recorded, they still need their own timestamps; do not assume they are already aligned. The teaching speed can be lower, but the lower speed is written into the conditions, not changing the published capability in this line.
Power. Battery 40 Ah (BMS). Charging time approximately 2 hours. Approximately 2 hours is charging, not battery life; the page does not specify battery life in hours. This line only retains the electrical terms that appear on the page: voltage, capacity, battery life, charging, current, or power. If there are no "hours," write battery life as not specified; do not fill in the blank with hours from a neighboring page. Do not rename charging time as battery life. Rated and maximum values must be listed separately. Preserve "approximately" for approximate values. Do not sum the amp-hours of multiple devices and claim it as one device's battery. Power-on time is not the master clock. Hours, charging, or current that do not appear remain as not specified; do not copy them in from a neighboring page.
Perception and computing. The vision system is written 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 (reflectivity 90%). 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 line takes inventory of the items explicitly stated in perception, computing, or communication, and preserves the words standard, included, optional, and optional-order. Unchecked options do not count. When the cover conflicts with the list, cite the list, but do not pretend the cover sentence does not exist. Head-mounted and glove do not enter this line. Processors, hard drive capacity, or camera channel counts not written out must not be drawn into the system diagram. Cameras on the list being turned on simultaneously does not equal a shared clock. Optional sensors not purchased do not enter this data dictionary.
End-effector. A multi-degree-of-freedom dexterous hand or gripper can be added to the end according to the task. The page states compatibility with Aoyi, BrainCo, Zhixing, and other grippers and dexterous hands, as well as the RX75, RM75, RM65 robotic arm platforms. Compatibility is not the standard configuration list. This line states where contact or gripping happens. Quick-change, compatible, and recommended are not models already in the box. The ring gripper on the main arm is not an end gripper. Force, stroke, and payload remain as-is in their respective rows; they are not merged into a single system metric because they are installed on a particular body. Flange and protocol mappings not specified are written as "to be confirmed," not "plug and play." Gripper open/close timestamps must be marked separately; do not merge them into image frame numbers unless the synchronization document already specifies it. "Supports" or "compatible" without a model number cannot be treated as delivered.
Boundary. The upper body and the wheeled chassis are a modular structure. How to connect to other chassis after separation is confirmed according to the project interface; do not write it in the public table as if it is 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 description; it is to prevent verbally buying two pages as one page. When writing a proposal, copy the boundary into "Not included in this order". If equipment not included is added later, open a new configuration sheet; do not go back and change the platform name in old samples. The head-mounted display is not on this page's list, and even less should it be assumed to be time-synchronized with this unit. 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 both have optional rows. Options are not written into the deliverables when unchecked. The end-effector brand must be named in the configuration sheet; do not write "compatible means already included." This line distinguishes standard, recommended, and optional. Recommended and optional items are not delivered if unchecked. When 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. Price and lead time are not written into this line's restatement. Sensors not purchased do not participate in the synchronization scheme. Unchecked recommended and optional items are written as not delivered on the order.
Quotable. 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 line is the type 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 and keep only the result. If the same number has different meanings on two pages, write it as two lines in the appendix. Do not mix test protocols into specification excerpts. If the synchronization document cannot be written in six lines, fill the synchronization column in the appendix as "Not committed." When pasting into the appendix, paste the words "approximately," "excluding," and "optional" along with the numbers.
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 lifting model's 900 mm as this unit's lifting stroke. This line is a negative statement for review. It does not describe what the equipment can do; it only prevents hours, degrees of freedom, load subjects, or cover slogans from neighboring pages from being written in. If a negative statement is hit, revert to the product page's original sentence; do not interpret it as "close enough." Do not write in success rates from external papers or total hours not published on this site. It is prohibited to write that PPS alignment with E6 or E2 has been completed, unless there is a separate written agreement. If manuscript retrieval hits a negative statement, revert to the product page's original sentence.
| 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
Pressing start on multiple devices at the same time does not mean the clocks are aligned. The head-mounted unit, master arm, slave arm, gripper, and chassis each have their own sampling clock. Without a common time base, it is impossible afterward to pair "the frame the human saw" with "the joint angles the arm actually reached" into a training sample. When frames are misaligned, the visuomotor policy learns misaligned causality.
The product page does not guarantee that the base unit and E6 or E2 have been synchronized via PPS plus serial port. The wrist camera and ring locator are accessories; powering them on together is not time synchronization. If a project requires synchronization, it must be listed separately in the configuration sheet: who is the master clock, what signal is used, the allowed alignment error, and how dropped frames are marked. If these sentences cannot be written, do not write "synchronized" in the proposal.
Do not mix sampling rates either. The control frequencies of the glove, head-mounted unit, and arm are not the same number. G7 is 120 Hz, G2-L transmits at 50 Hz, and E6 raw imagery can reach 60 Hz. The recording frequency of platform joints follows the actual controller and the written interface; do not invent a frequency that is not written on the page.
This article explains how timestamps should be required when this embodiment is listed alongside the head-mounted device and main arm, and which parts the page has not yet committed to.
Before handing off to a colleague
If the sync sheet has six blank rows, capture can still proceed, but the file name must include "clock not synchronized." Training scripts do not read directories with this marker by default. Do not backfill "it was aligned at the time" after capture ends. A misalignment value may only be used to execute a discard rule if it appears in a written protocol; without a protocol, keep the entire segment as unaligned raw data rather than cutting it into fragments that look continuous. The timestamp field names for head-mounted device, main arm, gripper, and embodiment are separated in advance to avoid overwriting by identical names. The read script for the clock-not-synchronized directory must have an assertion: refuse if the marker is not present in the path. Do not rely on human memory alone. The marker is written in two places: the directory name and the file header. The file header reads "no committed common clock." If a sync protocol is added later, new captures go into a new directory; old directories are not retroactively relabeled as aligned. Retroactive relabeling would make the misalignment at the time appear as though the later protocol had already taken effect.
First, lack of time synchronization must be written into the directory name and the file header.
Second, the script rejects misreadings that are not labeled.
Third, do not relabel as aligned after the fact.
Fourth, a new protocol only covers new directories.
Fifth, keep the timestamp field names of each device separate.
Sixth, without an agreement, do not cut segments into continuous samples.
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.