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 demonstration. The public sentences available for verifying the isomorphic teleoperation kit are: Configuration: the first two columns are humanoid configurations; the local column is a slave arm. Gripping: the first two columns are handles; the local column is a rail-type ring fixture. Main arm self-weight: GLN-RX75 is 7.8 kg, GLN-RX71 is 3.8 kg, the local isomorphic kit is approximately 1.5 kg (including fixture). Self-weight is not the slave-side rated payload. Maximum operating speed: the first two columns are 30 RPM, the local column is 110 RPM. All three columns list zero-force dragging. Zero-force dragging is not force feedback. The three sentences correspond to height, mass, and ground respectively. If any sentence does not cover the field conditions, do not write this device as the default platform for that task on the proposal cover.
Task scope
Where the motion comes from is another task sentence. The isomorphic teleoperation kit is one layer of the slave side or master side, not the entire chain. Force feedback is listed as supported only for GLN-RX75 and GLN-RX71. The local isomorphic kit is listed as not supported. The main arm models are RX75, RX71, YDS-DAP-75/65/RX75S respectively. The fixture in the local column is a rail-type ring fixture, used to grip the main arm; it is not the slave-side RMG22-65. The slave-side gripper is ordered separately. If a person uses a glove or head-mounted device to record their own hand, that is human motion, not joint commands for this device. Both recordings can be done simultaneously, but the file roles must be kept separate.
In published methods, ALOHA puts master-slave dual-arm demonstration and action chunk learning on one pipeline, Mobile ALOHA extends the problem to a mobile base, and UMI deliberately uses a handheld gripper rather than a full unit. These works show that task definition changes the action space. They did not test the isomorphic teleoperation kit; success rates and durations from the papers cannot be written into the task specification.
Therefore, the deliverable of this article is not a "recommended purchase," but a task boundary sentence: only assess operations that fall within the above public scope; for height, mass, mobility, or end effector outside the scope, open a separate configuration line or switch to a different product card. The entry point remains the product center; the parameter page is /product-teleop-kit.html.

How to Use This Page in This Version
Write the task boundary as the first paragraph of the experiment plan, not in an appendix. The first paragraph may only quote sentences already published for the isomorphic teleoperation kit; do not write subject-less statements like "the platform's capabilities cover common operations." Verify the height with this sentence: Configuration: the first two columns are humanoid configurations, and the local column is a co-axial arm. Gripping: the first two columns use handles, and the local column uses a rail-type finger-ring fixture. Verify the mass with this sentence: Main arm self-weight: GLN-RX75 is 7.8 kg, GLN-RX71 is 3.8 kg, and the local isomorphic kit is approximately 1.5 kg (including the fixture). Self-weight is not the rated payload of the follower end. Verify the ground with this sentence: Maximum operating speed: the first two columns are 30 RPM, and the local column is 110 RPM. All three columns list zero-force dragging for the dragging force. Zero-force dragging is not force feedback. Only when all three sentences are covered may the task proceed to describe cameras and personnel; if any one sentence cannot be covered, stop at the first paragraph and revise the task or switch to a different product page.
The second paragraph describes where the motion comes from. The fixture in the local column is a rail-type ring fixture, used to grip the main arm; it is not the slave-side RMG22-65. The slave-side gripper is ordered separately. Force feedback is listed as supported only for GLN-RX75 and GLN-RX71. The local isomorphic kit is listed as not supported. The main arm models are RX75, RX71, YDS-DAP-75/65/RX75S respectively. If this paragraph requires a main arm, open the kit page and write the column name; do not count the main arm into the price and weight of the isomorphic teleoperation kit. If this paragraph requires a gripper, write the gripper model; do not treat "quick-change" or "compatible" as a model. A person wearing a head-mounted device or glove only indicates how the human moves; do not write it as robot motion in the file name.
The third paragraph describes what not to do. Do not write "one teleoperation kit, approximately 5 kg, with force feedback." Do not write 30 RPM and 110 RPM as a single speed, and do not write DC24V and DC12V as a single voltage. These negative sentences and task sentences are placed on the same page so that reviewers do not have to flip to the end of the document to discover that the hours or degrees of freedom were borrowed from an adjacent page. The negative sentences are not disparaging the equipment; they are drawing the acceptable scope.
The fourth paragraph states sample expectations. An evaluation first collects trajectories that can be verbally reproduced: joint or master-slave correspondence, opening/closing, whether the chassis moves. Do not promise a success rate before the task boundary is frozen. Success rates in published papers belong to the original authors' robots, tasks, and success definitions, and cannot be written as expectations after using an isomorphic teleoperation kit.
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. All three columns have 7 degrees of freedom; they cannot be merged into one unit because of this. The column names are GLN-RX75, GLN-RX71, and the local isomorphic kit. This line only states the number and locations of joints that have already been published. It does not evaluate intelligence, and it does not automatically include waist, legs, neck, or an overall unit total not named on the page. When writing the action vector, create channels only for the body parts present on this line; body parts not present remain blank. Do not write blanks as 0, because 0 would be treated by training scripts as a real angle. Do not fill in the integer degrees of freedom of another device after this line to make up the count. 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 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 on this line; unnamed body parts remain blank and are not filled with 0.
Load and mass. Main arm self-weight: GLN-RX75 is 7.8 kg, GLN-RX71 is 3.8 kg, the local isomorphic kit is approximately 1.5 kg (including fixture). Self-weight is not the slave-side rated payload. Every number on this line must be read aloud with its subject: rated, self-weight, overall unit mass, envelope, friction, or gripping force. If the subjects differ, they cannot be merged into a single number, nor can any conversion not given on the page be performed. If field objects are heavier, you cannot change the specification in reverse; a larger specification also does not prove that every grasping method reaches that limit. The tool mass is undetermined; do not write the arm's rated payload as the graspable object mass. The acceptance table retains the original units. If an object exceeds the rated or recommended payload on this line, change the object for the task, not the specification. During acceptance, read the subject first, then the number; if the subjects do not match, split into two lines.
Shape and dimensions. Motion radius: 709 mm, 474 mm, 599 mm. This is the scale of the main arm, not the shape of the end-side platform. This row is a shape or structural dimension, used to check doors, elevators, tabletops, or transport; it is not an operating height, nor is it an arm reach. Do not add it to the vertical range. If the diagram shows protrusions, antennas, or a person's standing position that are not 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. Check doors and elevators at the task site against this row first; if they do not pass, do not schedule that task for this device. Doors, elevators, and transport are checked only against the shape; do not treat this row as an operating height.
Operating range. Configuration: the first two columns are humanoid configurations; the local column is a slave arm. Gripping: the first two columns are handles; the local column is a rail-type ring fixture. This line describes the range that the hand or lift can reach; the definition must follow the original sentence: vertical working range, arm span, motion radius, or stroke — these cannot be added together or renamed. If "excluding end effector" is written, it must remain in the figure caption. If the original text does not mark units, retain the note "units not specified"; do not delete it for tidiness. If the operating height or depth falls outside the definition on this line, it is not the default task for this device. The figure caption retains the range definition from the original sentence, as well as the phrases "excluding end effector" or "units not specified."
Motion. Maximum operating speed: first two columns 30 RPM, local column 110 RPM. All three columns list zero-force gravity compensation for towing force. Zero-force gravity compensation is not force feedback. This row describes how the base or main arm moves. Four-wheel steering, four-wheel drive, differential drive, in-place rotation radius, and rotational speed are terms for different mechanisms and cannot be substituted for one another. Published speed is a capability, not a recommended teaching speed; teaching can be slower, but the slower speed is recorded in the experimental conditions, not written back into the specification. If a page does not state slope climbing or positioning, do not borrow from another page. Whether a task requires a mobile base or a main arm, first check whether the mechanism terms in this row match. Teaching speed can be lower, but the lower speed is recorded in the conditions and does not change the published capability in this row.
Power. Operating voltage: the first two columns are DC24V, the local column is DC12V. Power: ≤200 W, ≤100 W, rated 84 W. The specification table has no battery line; do not write battery life. This line retains only 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 with hours from an adjacent page. Do not rename charging time as battery life. Rated and maximum must be in separate columns. Approximate values retain "approximately." Do not sum the amp-hours of multiple devices and claim it as one device's battery. Task duration can only be written into the plan if hours or charging are written on this line. Hours, charging, or current that do not appear remain as not given; do not copy them in from an adjacent page.
Perception and computing. Angular resolution: the first two columns are ±0.003°, the local column is 0.088°. Motors: the first two columns are integrated joints, the local column is bus servos. Communication: the first two columns are RJ45, the local column is RJ45 / 10-pin aviation connector. This line takes inventory of the items already specified in sensors, computing, or communication, and retains the terms standard, included, optional, and selectable. Optional items that are not checked do not count. If the cover conflicts with the list, cite the list while not pretending the cover sentence does not exist. Head-mounted devices and gloves do not enter this line. Processors, hard drive capacity, or camera channel counts not written out must not be drawn into the system diagram. The number of task video channels is governed by this line, not by verbally added cameras. Sensors that are optional and not purchased do not enter this data dictionary.
End effector. The fixture in the local column is a rail-type ring fixture, used to grip the main arm; it is not the slave-side RMG22-65. The slave-side gripper is ordered separately. 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 a slave-side gripper. Force, stroke, and payload remain as written on their respective lines; they are not merged into a single system metric because they are mounted on a particular body. For flanges and protocol mappings not given, write "to be confirmed," not "plug and play." Grasping tasks must specify the end-effector model separately; they cannot stop at the interface description on this line. "Supports" or "compatible" without a model number cannot be treated as delivered.
Boundary. Force feedback is listed as supported only for GLN-RX75 and GLN-RX71. The local isomorphic kit is listed as not supported. The master arm models are RX75, RX71, and YDS-DAP-75/65/RX75S respectively. This line is a boundary deliberately separated 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 prevents verbally buying two pages as one. When writing a proposal, copy the boundary into "Not included in this scope." If a device not included is added later, open a new configuration sheet; do not go back and change the body name in old samples. When a task depends on a device on the other side of the boundary, add a procurement line to the plan. Devices within the boundary must be ordered separately; do not rename old samples to say they already include it.
Configuration column. The contract must state the column name. Purchasing the body does not include the kit by default. For remote operation, refer to the first two columns; for local data acquisition, refer to the third column; in either case, order by cell. This line distinguishes standard, recommended, and optional. Recommended and optional items are not delivered unless checked. When 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 signing off. Prices and lead times are not written into this line's restatement. Check this line only after the task review has passed; unchecked items do not enter the experiment. Unchecked recommended and optional items are written as not delivered on the order.
Excerptable. Copy the attachment column by column; do not merge. Example: GLN-RX75, force feedback supported, 709 mm, 7.8 kg, handle, ±0.003°, 30 RPM, integrated joint, RJ45, DC24V, ≤200 W. This is the type of line that can be pasted into an attachment: with a subject, with units, and traceable back to the original sentence on the product page. When pasting, preserve "approximately," "not included," "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 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 minutes altering units. When pasting into the attachment, paste words like "approximately," "not included," and "optional" along with them.
Do not write. Do not write "one teleoperation kit, approximately 5 kg, with force feedback." Do not merge 30 RPM and 110 RPM into a single speed, and do not merge DC24V and DC12V into a single voltage. This line is a negative statement for review use. It does not describe what the equipment can do; it only prevents bringing in hours, degrees of freedom, load subjects, or cover slogans from adjacent pages. If a negative statement is hit, revert to the original sentence on the product page; do not interpret it as "close enough." Success rates from external papers and total hours not published on this site must likewise not be written in. Before finalizing the task document, run a search using the negative statements; if any are hit, send it back for rewriting. If the manuscript hits a negative statement in search, revert to the original sentence on the product page.
| Projects | Public-Facing Positioning of This Page |
|---|---|
| Degrees of Freedom | All three columns have 7 degrees of freedom, but this does not mean they can be merged into a single unit. The column names are GLN-RX75, GLN-RX71, and local isomorphic kit. |
| Load and Mass | Main arm self-weight: GLN-RX75 is 7.8 kg, GLN-RX71 is 3.8 kg, the local isomorphic kit is approximately 1.5 kg (including the fixture). Self-weight is not the rated payload at the end-effector. |
| Form Factor and Scale | Working radius: 709 mm, 474 mm, 599 mm. These are the dimensions of the main arm, not the outline of the end unit. |
| Operating Range | Configuration: the first two columns are anthropomorphic configurations; the local column is the same as the follower arm. Gripping: the first two columns use handles; the local column uses a rail-mounted finger-ring fixture. |
| Motion | Maximum operating speed: the first two columns are 30 RPM, the local column is 110 RPM. All three columns list zero-force gravity compensation. Zero-force gravity compensation is not force feedback. |
| Power | Operating voltage: the first two columns are DC24V, the local column is DC12V. Power: ≤200 W, ≤100 W, rated 84 W. The specification table has no battery row, so do not state battery life. |
| Perception & Compute | Angular resolution: the first two columns are ±0.003°, the local column is 0.088°. Motor: the first two columns use integrated joints, the local column uses bus servos. Communication: the first two columns use RJ45, the local column uses RJ45 / 10-pin aviation connector. |
| End Effector | The fixture in the local column is a rail-type ring fixture used to hold the main arm; it is not the RMG22-65 end-effector. The end-effector gripper is ordered separately. |
| Boundary | Force feedback is listed as supported only for GLN-RX75 and GLN-RX71. The local isomorphic kit is listed as not supported. The main arm models are RX75, RX71, and YDS-DAP-75/65/RX75S. |
| Configuration Panel | The contract must specify column names. Purchasing the platform does not include the kit by default. For remote operation, refer to the first two columns; for local data capture, refer to the third column; in either case, order by the individual cell. |
| Excerptable | Transcribe the attachments column by column; do not merge. Example: GLN-RX75, force feedback supported, 709 mm, 7.8 kg, handle, ±0.003°, 30 RPM, integrated joint, RJ45, DC24V, ≤200 W. |
| Do not write | Do not write "one teleoperation kit, approximately 5 kg, with force feedback." Do not write 30 RPM and 110 RPM as a single speed, and do not write DC24V and DC12V as a single voltage. |

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
- 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.