The site-entry checklist contains only publicly available conditions and the written configuration for this engagement. Overall dimensions: 570 × 465 × 1680 mm. Chassis width and shoulder width are kept within 465 mm. Locomotion speed: 0.1–1.5 m/s. Turning radius 690 mm; the specification refers to in-place rotation. Battery 40 Ah (BMS). Charging time is approximately 2 hours. The ~2 hours refers to charging, not runtime; no runtime in hours is given on the page. The vision system is listed as binocular depth / RGB, optional. Wide-angle cameras: 130° FOV × 3, located on the chest / back / chassis. LiDAR is a single-line laser with detection range greater than 40 m (at 90% reflectivity). The voice interaction module is a ring of 6 microphones, optional. Depth camera versions: data-capture version uses Orbbec 335LG; standard version uses Intel RealSense D405; optional Intel RealSense D435. Check off each item for door width, voltage, camera channel count, emergency stop, and personnel positioning. If an item cannot be checked off, stop and complete the configuration before beginning data capture.
On-Site Deployment
Communications follow the table: if Ethernet, Wi-Fi, RS485, RJ45, 6-pin aviation connector, or Modbus-RTU is written, implement per that page. If no register address is written, do not invent addresses on site. Joint brakes are executed only on arm tables that specify both hard brakes and soft brakes.
Record roles separately: operator, recorder, safety officer. They can be the same person, but the recording sheet has three columns to avoid confusion afterward about who confirmed the emergency stop.
The first power-on is not for building a training dataset. First verify direction and open/close. Only after the wheeled humanoid teleoperation body has passed verification may you proceed to the data acquisition discussion supported by /product-body-humanoid.html.

How to Use This Page in This Version
The deployment-day checklist starts with power and doors, not with the model. Overall dimensions 570 × 465 × 1680 mm. Chassis width and shoulder width are within 465 mm. Can it fit through the door? Battery 40 Ah (BMS). Charging time approximately 2 hours. Approximately 2 hours is charging, not endurance; the page does not state endurance in hours. Whether on-site power matches. Do not write endurance that is not provided into the duty schedule. Movement speed 0.1–1.5 m/s. Rotation radius 690 mm, specified as in-place rotation. Whether the floor and speed are within the published capabilities; on site it can go slower. The vision system is listed as binocular depth / RGB optional. Wide-angle cameras: 130° FOV × 3, located at the chest / back / chassis. The LiDAR is a single-line laser with a detection range greater than 40 m (reflectivity 90%). The voice interaction module is a ring of 6 microphones, optional. Depth camera versions: data acquisition edition Aobi 335LG; standard edition Intel RealSense D405; optional Intel RealSense D435. Whether the cameras and computing match the specification list; if optional items have not arrived, update the data dictionary.
Network and storage use only the interfaces explicitly listed. RJ45, Wi-Fi, RS485, aviation connectors, and Modbus-RTU are wired according to the corresponding page. Do not assume 5G is available on site unless the page lists 5G as a selected option. Do not assume a 1 TB hard drive is available on site unless the page states 1 TB.
Personnel are divided into three roles: operation, recording, and safety. The emergency stop is confirmed by the safety role. The first power-on script is for direction verification, and its output is a verification sheet, not an episode. Only after the verification sheet passes should data be collected according to the written configuration. A multi-degree-of-freedom dexterous hand or gripper can be attached to the end effector as required by 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 does not mean a standard configuration list. When the end effector has not yet arrived, verification can include unloaded motion, but the file name must be marked as having no end effector and must not be mixed into datasets containing grasping data.
The last line of the deployment record should write the product page version date or verification date, and point to /product-body-humanoid.html. When specs are corrected later, you can know which version of the public table this deployment was based on. 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.
Line-by-Line Verification
Degrees of freedom. Full-body active degrees of freedom: 21, broken down as both arms 14, waist 3, legs 2, neck 2. This line 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 waist, legs, neck, or a whole-body total that is not named on the page. When writing into the action vector, only create channels for body parts listed in this line; 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 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. The joint list for power-on verification is limited to this line. The action vector only creates channels for body parts named in this line; body parts not named are left blank, not filled with 0.
Payload and mass. Single-arm payload 5 kg. Overall weight approximately 125 kg, which is not the single-arm payload. The numbers in this line must be read with their subject: rated, self-weight, overall 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 an object on site is heavier, this does not retroactively change the specification; a larger specification 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 checklist retains the original units. Passing a no-load check does not mean the rated payload is achieved. During acceptance, read the subject first, then the number; if the subjects differ, split into two lines.
Dimensions and scale. Overall dimensions 570 × 465 × 1680 mm. Chassis width and shoulder width are within 465 mm. This line describes external or structural dimensions, used to verify 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 listed in this line, note separately that these are not part of the specification. If weight appears in an adjacent line, do not write it into the dimension sentence. The first item for site entry is whether this line can pass through doors and elevators. Doors, elevators, and transport are verified against external dimensions only; 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 that 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 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 the sake of tidiness. Ceiling height and shelving are checked against this line during verification; do not change the definition on site. The figure caption retains the range definition from the original sentence, as well as the terms "excluding end" or "units not specified."
Motion. Movement speed 0.1–1.5 m/s. Rotation radius 690 mm, referring to in-place rotation. This row describes how the ground platform 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 teleoperation speed; teleoperation can be slower, but a slower speed is recorded under experimental conditions and is not written back as a specification. On pages that do not state slope climbing or positioning, do not borrow from other pages. Chassis front/back orientation and emergency stop take priority before any speed test. Teleoperation speed can be lower, but a lower speed is recorded under operating conditions and does not change the published capability in this row.
Power supply. Battery 40 Ah (BMS). Charging time approximately 2 hours. Approximately 2 hours is charging, not endurance; the page does not state endurance in hours. This line only retains the electrical terms that appear on the page: voltage, capacity, endurance, charging, current, or power. If there are no "hours," write endurance as not provided; do not fill in with hours from an adjacent page. Do not rename charging time as endurance. Rated and maximum values must be listed separately. Approximate values retain "approximately." Do not sum the amp-hours of multiple devices and claim it as one device's battery. If the power supply does not match, stop; do not collect data first and add a power supply note later. 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 is listed as binocular depth / RGB optional. Wide-angle cameras: 130° FOV × 3, located at the chest / back / chassis. The LiDAR is a single-line laser with a detection range greater than 40 m (reflectivity 90%). The voice interaction module is a ring of 6 microphones, optional. Depth camera versions: data acquisition edition Aobi 335LG; standard edition Intel RealSense D405; optional Intel RealSense D435. This line itemizes the items explicitly stated in sensing, computing, or communications, and retains the terms standard, included as standard, optional, and optional configuration. An optional item that is not checked does not count. When the cover conflicts with the specification list, cite the list, but do not pretend the cover statement does not exist. Headsets and gloves do not belong in this line. Do not draw processors, hard drive capacity, or camera channel counts that are not stated into the system diagram. Topic names are finalized on deployment day; channel counts are not increased on the fly. 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 according to 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 line describes where contact or gripping occurs. Quick-change, compatible, and recommended are not models already in the box. The ring fixture on the main arm is not an end-effector gripper. Force, stroke, and payload remain as stated in their respective lines and are not merged into a single system metric just because they are mounted on a particular body. For flange and protocol mappings that are not provided, write "to be confirmed," not "plug and play." When the end effector has not arrived, mark the filename as "no end effector." "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 to other chassis after separation is confirmed per project interface; do not state in the public table that it is already connected. This row is a deliberately separated boundary on the page: a different model, a different column, a different product page, or an interface that still requires project confirmation after modularization. The boundary is not a defect note; it is to prevent verbally merging two pages into one when purchasing. 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 the old sample. A main arm that has not been ordered must not appear in the wiring table. Equipment within the boundary must be ordered separately; do not rename an old sample to say it already includes it.
Configuration column. The voice module and depth camera versions each have optional rows. Optional items are not written into unchecked deliverables. The end-effector brand must be named explicitly in the configuration sheet; do not write "compatible means included." This column distinguishes standard, recommended, and optional. Recommended and optional items are not delivered unless 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 a signature. Prices and lead times are not written into this row's summary. Deployment is based on the signed three columns, not the union of all options on the product page. Unchecked recommended and optional items are written as not delivered on the order.
Excerptable. Attachments may copy: 21 (14+3+2+2); 570×465×1680 mm; approximately 125 kg; 465 mm width limit; vertical arm reach 2100 mm; horizontal arm reach 1818 mm (excluding end effector); turning radius in place 690 mm; 0.1–1.5 m/s; single arm 5 kg; 40 Ah; charging approximately 2 hours. This is the type of line that can be pasted into an attachment: it has a subject, has units, and can be traced back to the original sentence on the product page. When pasting, keep words like approximately, excluding, not specified, optional, and recommended. Do not convert and keep only the result. If the same number means different things on two pages, write it as two lines in the attachment. Do not mix test protocols into specification excerpts. Deployment records should note which product page they are based on. When pasting into an attachment, paste words like approximately, excluding, and optional along with them.
Do not write. Do not write the approximately 2-hour charge time as 2 hours of battery life. 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 line is a negative statement for editorial review. It does not describe what the device can do; it only prevents hours, degrees of freedom, load 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." Likewise, do not write in success rates from external papers or total hours not published on this site. Capabilities added verbally in the field must not be written into the specification column of the deployment record. 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
Deployment describes site-entry conditions, not slogans. At a minimum it includes: floor load capacity and slope; whether doors and elevators are larger than the unit's dimensions; whether the operating height falls within the vertical range; whether the power supply matches the voltage on the page; who provides the network; where the primary-side workstation is placed; emergency stop and personnel positions; and which computer the recorded files are stored on. The compute platform appears only for products where it is written on the page. The folding model is Nvidia Jetson AGX Orin 64G, with no solid-state drive capacity stated. The lift model is Nvidia Jetson AGX Orin 64G plus a 1T solid-state drive. The wheeled humanoid, kits, and grippers do not default to having the same compute board.
Communication is copied from the table. The recommended arm table for the lifting model lists Ethernet, Wi-Fi, RS485; joints 1–4 have hard brakes, 5–7 have soft brakes. The gripper is RS485 / Modbus-RTU. The kit's main arm is RJ45, and the local column may also be 10-pin. Where no protocol mapping is written, do not invent register addresses in the deployment document.
On personnel, the operator, recorder, and safety officer can be the same person, but the roles must be recorded separately on the log sheet. For the first evaluation, it is recommended to start with a motion check without capturing training data: joint directions, gripper open/close, chassis forward/backward, emergency stop. Only after the check passes should you discuss samples.
This article presents the product intake checklist as short, printable statements.
Before handing off to a colleague
Execute the deployment day checklist in order: doors and power, emergency stop, unloaded direction check, whether the end effector is on the packing list, topic names, and whether file names mistakenly use "episode." If any step fails, stop. Failure records do not enter the training set directory. The specification column of the deployment record may only contain pasted original sentences from the product page; wishes added on site go in the "Not Accepted" column. At the end, photograph the labels: power label, end-effector label, packing list. The photos are part of the deployment record. Deployment photos are named by label type, not with names like IMG_0001. The name must contain power, end effector, or packing list. A deployment record without these three types of photos is not closed. Before closing, review the file names once more; unloaded verification files containing "episode" or "demo" are moved out of the training directory. The move action is written into the deployment record. A verbal claim that files were moved, with no record, is treated as not moved.
First, name photos according to label type.
Second, the record must not be closed if three types of photographs are missing.
Third, move episode files out of the training directory.
Fourth, write the removal action into the record.
Fifth, paste only the original sentence in the specification column.
Sixth, record on-site wishes in the Not Accepted column. Before closing a deployment record, check the Safety column once more to confirm that the emergency stop has been written into the record. A record without an emergency stop entry must not be closed. Once closed, no further specification sentences may be appended to the record.
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.