Back to News & Insights
Product Insights

Lifting dual-arm teleoperation body | Define task boundaries first: height, load, whether the base moves — confirm these three points before capture

The task must first be written as three verifiable sentences: where the operating height falls, whether the object mass is covered by the rated payload, and whether the chassis moves or stays still during teaching. The public sentences available to verify the wheeled lift dual-arm teleoperation platform are: lift stroke 900 mm, vertical working range 0–2.4 m (also written as 0–240…

2026-10-03
TOBI
Product Insights
Lifting dual-arm teleoperation body | Define task boundaries first: height, load, whether the base moves — confirm these three points before capture
Product InsightsWheeled dual-arm teleoperation robot with lift2026-10-03

The task must first be written as three verifiable sentences: where the operating height falls, whether the object mass is covered by the rated capacity, and whether the chassis moves during teaching. The publicly verifiable statements for the wheeled lift dual-arm teleoperation platform are: lift travel 900 mm, vertical working range 0–2.4 m (also written as 0–2400 mm in the table). Single-arm reach 633 mm. Single-side overhang beyond the chassis 790 mm; the original text does not specify a unit at this point, and it appears alongside millimeters in the same sentence, so it is written externally as 790 mm with this note retained. Single-arm rated payload 5 kg. The 8 kg in the parameter table is the weight of a single arm. The dual-arm rated 8 kg previously written on the cover conflicts with the parameter table; the parameter table takes precedence. The whole-machine mass is approximately 80 kg. Two-wheel differential drive, speed 1.5 m/s, climbing slope 5°. Positioning accuracy ±10 mm / ±3°. The three sentences correspond to height, mass, and ground respectively. If any one sentence does not cover the field conditions, do not write this device as the default platform for the task on the proposal cover.

Task scope

Where the motion comes from is a separate task statement. The wheeled lift dual-arm teleoperation robotic platform is one layer within the slave or master side, not the entire chain. The standard configuration lists the robotic arm as RM65-B-V ×2, while the robotic arm spec sheet lists the model as RM75-B-V. Keep both model numbers and lock them in before ordering; do not collapse them into one. The recommended configuration lists gripper CTAG2F90-D ×2. The standard configuration quantity list does not include a gripper. RMG22-65 is a separate product page. If a person uses a data glove or head-mounted device to record their own hand, that is human motion, not joint commands for this device. Both records can be captured simultaneously, but their file roles must be kept separate.

In the published methods, ALOHA combines leader-follower dual-arm teaching and block-wise motion learning in a single pipeline, Mobile ALOHA extends the problem to a mobile base, and UMI deliberately uses a handheld gripper rather than the whole machine. These works show that the task definition changes the action space. They did not test the wheeled lift dual-arm teleoperation platform, and the success rates and durations in the papers cannot be written into the task specification.

Therefore, the deliverable of this article is not a "recommended purchase" but a task boundary: only evaluate manipulation that falls within the above publicly stated range; for heights, masses, mobility, or end-effectors outside the range, open a separate configuration line, or switch to a different product card. The entry point remains the product center, and the parameter page is /product-body-lift.html.

Wheeled lifting dual-arm teleoperation platform RMC-AIDAL
Figure 1 | Wheeled lifting dual-arm teleoperation platform. The caption only states that this is a device photo from the product page; the appearance is not interpreted as parameters not present in the table.

How to Use This Page in This Version

Write the task boundary as the first paragraph of the experimental plan, not in an appendix. The first paragraph may only cite publicly stated sentences about the wheeled lift dual-arm teleoperation platform; do not write subject-less statements such as "the platform's capabilities cover common manipulation." Verify height with this sentence: lift travel 900 mm, vertical working range 0–2.4 m (also written as 0–2400 mm in the table). Single-arm reach 633 mm. Single-side overhang beyond the chassis 790 mm; the original text does not specify a unit at this point, and it appears alongside millimeters in the same sentence, so it is written externally as 790 mm with this note retained. Verify mass with this sentence: single-arm rated payload 5 kg. The 8 kg in the parameter table is the weight of a single arm. The dual-arm rated 8 kg previously written on the cover conflicts with the parameter table; the parameter table takes precedence. The whole-machine mass is approximately 80 kg. Verify ground with this sentence: two-wheel differential drive, speed 1.5 m/s, climbing slope 5°. Positioning accuracy ±10 mm / ±3°. Only when all three sentences are covered can the task proceed to cameras and personnel; if any one sentence is not covered, stop at the first paragraph and either revise the task or switch to a different product page.

The second paragraph describes where the actions come from. The recommended configuration lists gripper CTAG2F90-D ×2. The standard configuration quantity table does not include a gripper. RMG22-65 is a separate product page. The standard configuration lists robotic arm RM65-B-V ×2, while the robotic arm parameter table lists model RM75-B-V. Keep both model sets; lock them in before ordering and do not collapse them into one. If this paragraph requires a primary arm, open the kit page and write out the column names; do not include the primary arm in the price or weight of the wheeled lifting dual-arm teleoperation robotic platform. If this paragraph requires a gripper, write the gripper model; do not treat "quick-change" or "compatible" as a model. A person wearing a headset or gloves only indicates how the human moves; do not write it into the filename as a robotic action.

The third paragraph covers what not to do. Do not state 17 degrees of freedom for the whole machine, do not state 650×512×1700 mm, approximately 120 kg, lifting 0.3 m, vertical 0–2.1 m, speed 0.1–1.0 m/s. Do not present 8 kg as rated load. Do not state battery life in hours. These negative statements and task statements belong on the same page so reviewers do not have to reach the end of the document to discover that the hours figure or degrees of freedom were borrowed from a neighboring page. The negative statements are not disparaging the device; they define the verifiable scope.

The fourth paragraph describes sample expectations. A single evaluation first collects trajectories that can be replayed: joint or leader-follower correspondence, open/close, and whether the chassis moves. Do not commit to a success rate before the task boundary is frozen. Success rates in published papers belong to the original authors' robots, tasks, and success definitions; they cannot be written as expectations after using the wheeled lift dual-arm teleoperation platform.

The fifth paragraph states the exit conditions. Stop capture and change the configuration if any of the following occurs: the object mass exceeds the rated load and there is no written overload test; the operating height is not within the defined vertical range or reach; the required end effector is not listed on the configuration sheet; the required battery life in hours does not exist in the power row. Exiting is not failure — it prevents non-comparable trajectories from being written into the same training set.

Line-by-Line Verification

Degrees of freedom. In the robotic arm parameter table, the single-arm degrees of freedom for model RM75-B-V is 7. The product page does not publish the whole-machine degrees of freedom; do not fill in 17 or 20. 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 task specification only promises that these published joints can be recorded; it does not promise joints outside the page. 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 rated load 5 kg. The 8 kg in the parameter table is the single-arm self-weight. The dual-arm rated 8 kg once written on the cover conflicts with the parameter table; the parameter table takes precedence. Approximately 80 kg for the whole unit is the overall mass. The numbers in this line must be read with their subjects: rated load, self-weight, overall mass, envelope, friction, or gripping force. Different subjects cannot be merged into a single number, nor can conversions not given on the page be performed. If field objects are heavier, the specification cannot be changed retroactively; a larger specification also does not prove that every grasping method reaches that limit. If the tool mass is undetermined, do not write the arm's rated load as the graspable object mass. The acceptance table retains the original units. If an object exceeds the rated or recommended load in this line, change the object, not the specification. During acceptance, read the subject first and then the number; if the subjects do not match, split into two lines.

Dimensions and scale. Model RMC-AIDAL. Stowed dimensions 640 × 450 × 1780 mm. Chassis 640 × 450 × 250 mm. This row describes form factor or structural scale, used to verify doors, elevators, tabletops, or transport; it is not operating height, nor is it arm reach. Do not add it to the vertical range. If the figure shows protrusions, antennas, or a person's standing position not present 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. The doors and elevators at the task site must first pass this row; if they do not, do not schedule that task for this device. Doors, elevators, and transport are verified only against form factor; do not treat this row as operating height.

Operating range. Lift travel 900 mm, vertical working range 0–2.4 m (also written as 0–2400 mm in the table). Single-arm reach 633 mm. Single-side overhang beyond the chassis 790 mm; the original text does not specify a unit at this point, and it appears alongside millimeters in the same sentence, so it is written externally as 790 mm with this note retained. This row describes the range that the hand or lift can reach; the definitions must follow the original sentences: vertical working range, arm reach, motion radius, or travel — these cannot be added together or renamed. If "excluding end-effector" is written, it must remain in the figure caption. When the original text does not specify a unit, retain the note "unit not specified"; do not delete it for the sake of tidiness. If the operating height or depth falls outside the definitions in this row, it is not a default task for this device. The figure caption retains the range definitions from the original sentences, as well as terms such as "excluding end-effector" or "unit not specified."

Motion. Two-wheel differential drive, speed 1.5 m/s, slope climbing 5°. Positioning accuracy ±10 mm / ±3°. 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. Published speed is a capability, not a recommended teaching speed; teaching may be slower, but the slower speed is recorded under experimental conditions and is not written back into the specifications. Do not borrow slope climbing or positioning figures from other pages that do not list them. Whether a task requires a mobile base or a main arm, first check whether the mechanism terms in this row match. Teaching speed may be lower, but the lower speed is recorded under operating conditions and does not change the published capability in this row.

Power. The battery is lithium iron phosphate DC 48V 20Ah. This 2026-08-03 document does not state battery life in hours. Do not fill in approximately 6 hours, and do not rewrite it as 48V 31Ah or approximately 4 hours. This line should only retain the electrical terms that appear on the page: voltage, capacity, battery life, charging, current, or power. If there are no "hours", write that battery life is not given; do not fill in the blank with hours from an adjacent page. Do not rename charging time as battery life. Rated and maximum values must be listed in separate columns. Keep "approximately" for approximate values. Amp-hours for multiple devices must not be summed and presented as one device's battery. Task duration may only be written into the plan if hours or charging are stated on this line. If hours, charging, or current do not appear, keep them as not given; do not copy them from an adjacent page.

Perception and computing. Main controller Nvidia Jetson AGX Orin 64G, plus a 1T solid-state drive. Standard vision configuration is D435 ×1, wide-angle cameras ×2, voice module ×1. If the cover states 3 depth cameras plus 2 wide-angle cameras, this conflicts with the list; the specification follows the list. D435 row: ideal ranging 0.3–3 m; depth ≤1280×720, ≤90 fps; RGB 1920×1080, 30 fps; field of view 69°×42°; rolling shutter. Navigation separately lists depth camera ×1, IMU + encoder ×1, LiDAR ×1, safety edge ×1, ultrasonic ×2. This row inventories the items explicitly stated in perception, computing, or communications, and retains the terms standard, included, optional, and selectable. Optional items not selected do not count. When the cover conflicts with the list, cite the list, but do not pretend the cover statement does not exist. Headsets and gloves do not belong in this row. Processors, drive capacities, or camera channel counts not written out must not be drawn into the system diagram. The number of camera channels for task video follows this row, not verbally added cameras. Optional sensors not purchased do not enter this data dictionary.

End effector. The recommended configuration specifies two CTAG2F90-D grippers. The standard configuration quantity table does not include a gripper. RMG22-65 is a separate product page. This row describes which end the contact or grasping occurs at. Quick-change, compatible, and recommended are not models already included in the box. The ring fixture on the main arm is not an end-effector gripper. Force, stroke, and payload remain as-is on their respective rows and are not merged into a single system metric just because they are mounted on a particular robotic platform. For flange and protocol mappings that have not been specified, write "to be confirmed" rather than "plug and play." Grasping tasks must specify the end-effector model separately and cannot stop at the interface description in this row. "Supports" or "compatible" without a model number cannot be treated as delivered.

Boundary. The standard configuration lists the robotic arm as RM65-B-V ×2, while the robotic arm parameter table lists the model as RM75-B-V. Both model numbers are retained; lock them in before placing the order, and do not collapse them into one. This line is a deliberate 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 disclosure; it is to prevent verbally buying two pages as one. When writing the 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 robotic platform name in the old sample. When a task depends on equipment on the other side of the boundary, add a procurement line to the plan. Equipment within the boundary must be ordered separately; do not rename the old sample to imply it already includes it.

Configuration column. Recommended configuration is RM75-B-V ×2, two-wheel differential chassis ×1, gripper CTAG2F90-D ×2. Teleoperation options are servo teleoperation, backpack teleoperation, and mobile teleoperation; these are not in the standard configuration quantity table. This row distinguishes standard, recommended, and optional. Recommended and optional items not selected are not delivered. 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. Prices and lead times are not written into this row's restatement. Only check this row after the task review passes; unchecked items do not enter the experiment. Unchecked recommended and optional items are written as not delivered on the order.

Excerptable. Attachment may copy: RMC-AIDAL; 640×450×1780 mm; approximately 80 kg; lift/lower 900 mm; vertical 0–2.4 m; reach 633 mm; rated 5 kg; self-weight 8 kg; repeatability ±0.05 mm; differential drive 1.5 m/s; gradeability 5°; positioning ±10 mm / ±3°; Orin 64G + 1T SSD; lithium iron phosphate DC 48V 20Ah, hours not specified. This is the type of line that can be pasted into an attachment: 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", "not included", "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 lines in the attachment. Do not mix test protocols into specification excerpts. After the task is frozen, paste the original excerptable sentences into the attachment to avoid the meeting minutes rewriting units. When pasting into the attachment, include words like "approximately", "not included", and "optional" as well.

Do not write. Do not write 17 degrees of freedom for the whole machine, do not write 650×512×1700 mm, approximately 120 kg, lift 0.3 m, vertical 0–2.1 m, speed 0.1–1.0 m/s. Do not write 8 kg as rated payload. Do not write battery life in hours. This row is a negative checklist for review. 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 item is hit, revert to the original sentence from the product page; do not interpret it as "close enough." Success rates from external papers and total hours not published on this site likewise must not be written in. Before finalizing the task specification, search using the negative checklist; if there is a hit, send it back for rewriting. If the manuscript hits a negative item, revert to the original sentence from the product page.

ProjectsPublic-Facing Positioning of This Page
Degrees of FreedomIn the robotic arm parameter table, model RM75-B-V has 7 degrees of freedom per arm. The product page does not publish the total degrees of freedom for the whole unit; do not fill in 17 or 20.
Load and MassSingle-arm rated payload 5 kg. The 8 kg in the parameter table is the single-arm self-weight. The cover previously stated a dual-arm rated payload of 8 kg, which conflicted with the parameter table; the parameter table takes precedence. The total unit weight of approximately 80 kg is the overall mass.
Form Factor and ScaleModel RMC-AIDAL. Folded dimensions 640 × 450 × 1780 mm. Chassis 640 × 450 × 250 mm.
Operating RangeLifting stroke 900 mm, vertical working range 0–2.4 m (also written as 0–2400 mm in the table). Single-arm reach 633 mm. Single-side overhang beyond the chassis is 790 mm; the original text did not specify a unit at that point, but since it appears alongside millimeters in the same sentence, it is written externally as 790 mm with this note retained.
MotionTwo-wheel differential drive, speed 1.5 m/s, climbing slope 5°. Positioning accuracy ±10 mm / ±3°.
PowerThe battery is lithium iron phosphate DC 48V 20Ah. This document dated 2026-08-03 does not state battery life in hours. Do not add approximately 6 hours, and do not rewrite it as 48V 31Ah or approximately 4 hours.
Perception & ComputeMain controller Nvidia Jetson AGX Orin 64G, with an additional 1T solid-state drive. Standard vision configuration is D435 ×1, wide-angle cameras ×2, voice module ×1. If the cover states 3 depth channels plus 2 wide-angle channels, this conflicts with the list; the specifications follow the list. D435 row: ideal ranging 0.3–3 m; depth ≤1280×720, ≤90 fps; RGB 1920×1080, 30 fps; field of view 69°×42°; rolling shutter. Navigation separately lists depth camera ×1, IMU + encoder ×1, LiDAR ×1, safety edge ×1, ultrasonic ×2.
End EffectorThe recommended configuration lists gripper CTAG2F90-D ×2. The standard configuration quantity table does not include a gripper. RMG22-65 is a separate product page.
BoundaryThe standard configuration lists the robotic arm as RM65-B-V ×2, while the robotic arm parameter table lists the model as RM75-B-V. Both model numbers are retained; lock one before placing the order — do not collapse them into a single number.
Configuration PanelRecommended configuration is RM75-B-V ×2, two-wheel differential chassis ×1, gripper CTAG2F90-D ×2. Teleoperation options are servo teleoperation, backpack teleoperation, and mobile teleoperation; these are not included in the standard configuration quantity table.
ExcerptableAttachment copy: RMC-AIDAL; 640×450×1780 mm; approximately 80 kg; lifting 900 mm; vertical 0–2.4 m; reach 633 mm; rated 5 kg; self-weight 8 kg; repeatability ±0.05 mm; differential drive 1.5 m/s; slope climbing 5°; positioning ±10 mm / ±3°; Orin 64G + 1T SSD; lithium iron phosphate DC 48V 20Ah, hours not specified.
Do not writeDo not write 17 degrees of freedom for the whole unit, and do not write 650×512×1700 mm, approximately 120 kg, lifting 0.3 m, vertical 0–2.1 m, speed 0.1–1.0 m/s. Do not write 8 kg as the rated payload. Do not write battery life in hours.
Wheeled lifting dual-arm teleoperation platform; the product page currently publishes only this one main image.
Figure 2 | The same main image as at the beginning of the article. The product page does not have a second publicly available angle of the chassis, so no photo of a different model is substituted here.

Relationship to Public Methods and Adjacent Pages

Teleoperation data capture requires separating three layers first, rather than first choosing an "all-in-one platform." The first layer is the master side where the operator issues actions — it can be an isomorphic master arm, a glove, or a controller. The second layer is the slave-side rig that executes the actions — this is the equipment discussed in this article series. The third layer is the recorded data written to disk: timestamps, master-side commands, slave-side joint or chassis state, images, and end-effector open/close state. When the three layers come from different pages, the order, acceptance, and training set must all be written separately.

Published work has already explained this split clearly. Zhao et al.'s ALOHA places low-cost dual-arm master-slave teleoperation and Action Chunking with Transformers in the same pipeline: the human demonstrates through the master arm, the slave arm executes, and the policy learns action chunks consistent with that slave arm. The later Mobile ALOHA puts dual-arm demonstration on a mobile base, discussing how the task distribution changes after mobility, rather than copying the numbers from a fixed base to a mobile base. Chi et al.'s Diffusion Policy shows that demonstrations can train visuomotor policies, but the action representation must match the robot used during capture. Chi et al.'s UMI uses a hand-mounted gripper to capture in-the-wild manipulation, explicitly not an entire humanoid or mobile dual-arm. Open X-Embodiment combines data from multiple robots, on the premise that embodiment differences are labeled, rather than averaging parameters from different embodiments into a single row.

These references only provide methodological positioning. They have not tested any embodiment sold by Hunan TOBI Technology. The success rates, data durations, and camera configurations in the papers cannot be written up as TOBI's own measured results. What TOBI's product pages publish are device boundaries and specification tables. Egocentric video captured by a person wearing a head-mounted device or a glove is also not an action label for this embodiment.

So the "task boundary" article answers only one question: which classes of operator actions can this base unit handle, and which actions the product page never promised. Once the boundary is clear, degrees of freedom, payload, cameras, and battery will not be read as marketing adjectives.

Before handing off to a colleague

Before handing it off to a colleague, read the task boundary out loud.

The first sentence retains only the original definition of height or range, the second sentence retains only the load subject, and the third sentence retains only the mobility mechanism. Do not connect the three sentences with "and the combined capability is sufficient". Then check whether the end device and the master device are already on separate lines; if not, write "end device and master device not included" on the cover of the task sheet. Finally, check for hours or degrees of freedom borrowed from a neighboring page. Delete the borrowed sentences, and only then can the task sheet enter review. The review does not discuss model architecture; it only discusses whether these three sentences cover the site. If they do not cover it, change the product page or change the task; do not change numbers during the review. The second page of the task sheet contains only failure conditions, not vision. Failure conditions include: height not within the original sentence's definition, object mass without a corresponding subject, chassis or main arm mechanism terms that do not match the site, no model number for the end device, no column name for the master device, hours written into the schedule that are not in the power row. After each failure condition, write "stop and change the configuration", not "collect a little first and see". "Collect a little first and see" will put non-comparable trajectories into the same directory, and they will be difficult to separate later. The review signature signs only this page of failure conditions, not a paragraph describing capabilities.

First, the task specification cover must not contain capability adjectives without a subject.

Second, height, load, and mobility each get their own row.

Third, the end device and the master device either have a model number or are written as not included.

Fourth, hours and degrees of freedom from adjacent pages do not appear.

Fifth, the reviewer signs only the failure conditions.

Sixth, if it fails, change the configuration first — do not start collecting.

Continue Reading

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.