The task should first be written as three verifiable sentences: where the operating height falls, whether the object mass is covered by the rated envelope, and whether the base moves or stays still during teleoperation. The publicly verifiable sentences for the two-finger parallel gripper RMG22-65 are: the 65 mm stroke is the finger opening distance, not the robot arm reach, nor the vertical working range of the unit itself. Maximum envelope grasp payload 5 kg. Recommended maximum friction payload 2 kg. Maximum gripping force 130 N. These three numbers must not be written as the same 5. Opening / closing time 2 s. Positional repeatability ±0.05 mm. The 2 seconds is the time specification for opening or closing, not the control frequency. The three sentences correspond to height, mass, and ground respectively. If any one sentence does not cover the actual site, do not write this device as the default platform for that task on the proposal cover.
Task scope
Where the motion comes from is a separate task statement. The two-finger parallel gripper RMG22-65 is one layer within the slave or master side, not the entire chain. The standard quantity table for the lift model does not include this gripper. The folding model lists quick-change capability, not that the RMG22-65 is already in the box. The recommended item CTAG2F90-D is also not this model. It is itself the end effector. Whether it directly matches the flange, wiring harness, and protocol of the robotic platform must be confirmed in the configuration sheet; the page states that plug-and-play is not assumed by default. If a person records their own hand using a glove or head-mounted device, 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 public literature, ALOHA places bimanual leader-follower teleoperation and action chunk learning in one pipeline, Mobile ALOHA extends the problem to a mobile base, and UMI deliberately uses a handheld gripper instead of a full system. These works show that task definition changes the action space. They did not test the two-finger parallel gripper RMG22-65, and the success rates and durations in the papers must not be written into the task specification.
Therefore, the deliverable of this article is not a "recommended purchase," but a task boundary: only evaluate operations that fall within the above public specifications; heights, masses, mobility, or end-effectors outside the range require a separate configuration line or a different product card. The entry point remains the product center, and the parameter page is /product-gripper-2f.html.

How to Use This Page in This Version
Write the task boundary as the first paragraph of the experimental plan, not in the appendix. The first paragraph may only cite sentences already published for the two-finger parallel gripper RMG22-65, and must not include subject-less statements like "platform capabilities cover common operations." Verify height with this sentence: the 65 mm stroke is the finger opening distance, not the robot arm reach, nor the vertical working range of the unit itself. Verify mass with this sentence: maximum envelope grasp payload 5 kg. Recommended maximum friction payload 2 kg. Maximum gripping force 130 N. These three numbers must not be written as the same 5. Verify ground with this sentence: opening / closing time 2 s. Positional repeatability ±0.05 mm. The 2 seconds is the time specification for opening or closing, not the control frequency. 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 revise the task or switch product pages.
The second paragraph describes where the motion comes from. It is itself the end-effector. Whether it directly matches the flange, wiring harness, and protocol of the host unit must be confirmed in the configuration form; the page states it is not plug-and-play by default. The standard quantity table for the lift version does not include this gripper. The folding version describes quick-change capability, not that RMG22-65 is already in the box. The recommended item CTAG2F90-D is also not this model. If this paragraph requires a primary arm, open the kit page and write the column name; do not include the primary arm in the price and weight of the two-finger parallel gripper RMG22-65. If this paragraph requires a gripper, write the gripper model; do not treat "quick-change" or "compatible" as a model. A human wearing a headset or gloves only indicates how the human moves; do not write it as a robot action in the file name.
The third paragraph covers what not to do. Do not convert 130 N into 5 kg and delete the original line. Do not write ±0.05 mm as the repeatability accuracy of the attached robotic arm. Do not mention battery life. These negative statements and task statements 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 statements are not meant to disparage the equipment; they are meant to delineate the acceptable scope of verification.
The fourth paragraph should describe sample expectations. A single evaluation should first collect trajectories that can be reproduced: joint or master-slave correspondence, opening and closing, and 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' robot, task, and success definition; they cannot be written as the expected rate after using the two-finger parallel gripper RMG22-65.
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. This is an end-effector gripper, not a multi-joint arm. The public table does not give the gripper an integer "degree of freedom" value; do not invent one just to align with other robotic platforms. 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 totals that are not named on the page. When writing the action vector, only build channels for the body parts listed in this row; body parts not listed remain blank. Do not write blanks as 0, because 0 will be treated by the training script as a real angle. Also do not fill in the degree-of-freedom integer from another device into this row to make it look complete. 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 only builds channels for the body parts named in this row; unnamed body parts remain blank and are not filled with 0.
Payload and mass. Maximum envelope grasp payload 5 kg. Recommended maximum friction payload 2 kg. Maximum gripping force 130 N. These three numbers cannot be written as the same 5. The numbers on this line must be read aloud with their subject: rated, self-weight, full-machine 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 the object in the field is heavier, the specification cannot be changed retroactively; 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 checklist retains the original units. If the 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 and then the number; if the subjects are inconsistent, split into two lines.
Dimensions and scale. Overall dimensions 112 × 60 × 167 mm. Stroke 65 mm. Finger height 80 mm. Platform weight 745 g. This row describes form factor or structural scale, used to verify doors, elevators, tabletops, or transport—not operating height, and not arm reach. Do not add it to the vertical range. If the diagram shows protrusions, antennas, or human standing positions 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 dimensions sentence. Doors and elevators at the task site are checked against this row first; if it does not fit, do not schedule that task for this device. Doors, elevators, and transport are checked only against form factor—do not treat this row as operating height.
Operating range. The 65 mm stroke is the finger opening distance, not the robot arm reach, nor the vertical working range of the unit itself. This row describes the range the hand or lift can reach; the definition must follow the original wording: vertical working range, arm reach, motion radius, and stroke cannot be added together or renamed. If "excluding end-effector" is written, it must remain in the caption. If the original text does not specify units, retain the note "units not specified" rather than deleting it for tidiness. If the operating height or depth falls outside the definition in this row, it is not the default task for this device. The caption retains the range definition from the original sentence, as well as terms like "excluding end-effector" or "units not specified."
Motion. Opening / closing time 2 s. Positional repeatability ±0.05 mm. The 2 seconds is the time specification for opening or closing, not the control frequency. This row describes how the ground or primary arm moves. Four-wheel four-drive, differential drive, in-place rotation radius, and rotational speed are terms for different mechanisms and cannot be substituted for each other. Published speed is a capability, not a recommended teleoperation speed; teleoperation can be slower, but the slower speed is written into the experimental conditions and not written back as a specification. Do not borrow slope climbing or positioning data from other pages if the page does not specify them. Whether the task requires moving the base or primary arm should first be checked against whether the mechanism terms in this row match. Teleoperation speed can be lower, but the lower speed is written into the conditions and does not change the published capability in this row.
Power. Rated voltage 24 V. Rated / maximum current 1.9 / 5.7 A. Rated / maximum power 45.6 / 136.8 W. No battery capacity, no endurance in hours. This row retains only the electrical terms that appear on the page: voltage, capacity, endurance, charging, current, or power. If there is no "hours," write that endurance is not specified; do not fill in the blank with hours from an adjacent page. Do not rename charging time as endurance. Rated and maximum values must be listed in separate columns. Preserve "approximately" where it appears. Do not sum the ampere-hours of multiple devices and present the total as the battery of a single device. Task duration may only be entered into the plan if hours or charging are stated in this row. Hours, charging, or current that do not appear remain unspecified; do not copy them in from an adjacent page.
Perception and computing. Communication interface: 6-pin aviation connector. Communication protocol: RS485 / Modbus-RTU. Operating environment: 0–50 ℃, relative humidity ≤85%. There is no camera on the page. This row inventories the items already specified under sensors, computing, or communications, and retains the terms standard, included, optional, and configurable. Unchecked optional items do not count. When the cover conflicts with the list, cite the list, while not pretending the cover statement does not exist. Head-mounted and glove devices do not enter this row. Processors, storage capacity, or camera channel counts that are not written out must not be drawn into the system diagram. The channel count for task videos follows this row, not verbally added cameras. Sensors that are optional but not purchased do not enter this data dictionary.
End-effector. It is itself the end-effector. Whether it directly matches the flange, wiring harness, and protocol of the host unit must be confirmed in the configuration form; the page states it is not plug-and-play by default. This row describes where contact or gripping occurs. Quick-change, compatible, and recommended are not models already in the box. The ring fixture on the primary arm is not a from-end gripper. Force, stroke, and payload remain as-is in their respective rows and are not merged into a single system metric because they are mounted on a certain host unit. Flange and protocol mappings that are not provided should be written as "to be confirmed," not as "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 cannot be treated as delivered.
Boundary. The standard quantity table for the lift version does not include this gripper. The folding version describes quick-change capability, not that RMG22-65 is already in the box. The recommended item CTAG2F90-D is also not this model. This row is a boundary deliberately separated on the page: another model, another column, another product page, or an interface that still requires project confirmation after modularization. The boundary is not a defect note; it prevents 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 form rather than going back to change the unit name in the old sample. When the 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 say it already includes it.
Configuration column. The order specifies model RMG22-65, and states which host unit it is mounted on, the quantity, and whether it replaces other gripper models in that host unit's recommended column. This row distinguishes standard, recommended, and optional. Recommended and optional items are not delivered unless checked. When the standard row and the parameter table row are inconsistent, 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 row's restatement. Check this row only 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. Copy into the attachment line by line: envelope 5 kg; friction recommendation 2 kg; maximum gripping force 130 N; stroke 65 mm; finger height 80 mm; 745 g; opening / closing 2 s; repeatability ±0.05 mm; 24 V; 1.9/5.7 A; 45.6/136.8 W; RS485 / Modbus-RTU. This row is the type that can be pasted into an attachment: with a subject, with units, and traceable to the original sentence on the product page. When pasting, retain words like "approximately," "excluding," "not provided," "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 the specification excerpt. After the task is frozen, paste the excerptable original sentences into the attachment to avoid the memo altering units. When pasting into the attachment, paste words like "approximately," "excluding," and "optional" along with the numbers.
Do not write. Do not convert 130 N into 5 kg and delete the original line. Do not write ±0.05 mm as the repeatability accuracy of the attached robotic arm. Do not write battery life. This line is a negative sentence for review purposes. It does not describe what the device can do; it only prevents writing in hours, degrees of freedom, payload subjects, or cover slogans from adjacent pages. If a negative sentence is hit, revert to the original product page sentence and do not interpret it as "close enough". Do not write in external papers' success rates or total hours not publicly disclosed on this site. Before finalizing the task brief, search using negative sentences; if any are hit, send back for rewriting. If the manuscript search hits a negative sentence, revert to the original product page sentence.
| Projects | Public-Facing Positioning of This Page |
|---|---|
| Degrees of Freedom | This is an end-effector gripper, not a multi-joint arm. The public table does not give the gripper a "degree of freedom" integer; do not fabricate one to align with other platforms. |
| Load and Mass | Maximum envelope grasp payload 5 kg. Recommended maximum friction payload 2 kg. Maximum clamping force 130 N. These three numbers cannot all be written as the same 5. |
| Form Factor and Scale | Overall dimensions 112 × 60 × 167 mm. Stroke 65 mm. Finger height 80 mm. Body weight 745 g. |
| Operating Range | The 65 mm stroke is the finger opening distance, not the robotic arm reach, nor the platform's vertical working range. |
| Motion | Open / close time 2 s. Positional repeatability ±0.05 mm. The 2 seconds is the specification for the open or close time, not the control frequency. |
| Power | Rated voltage 24 V. Rated / maximum current 1.9 / 5.7 A. Rated / maximum power 45.6 / 136.8 W. No battery capacity, no battery life in hours. |
| Perception & Compute | Communication interface: 6-pin aviation connector. Communication protocol: RS485 / Modbus-RTU. Operating environment: 0–50 °C, relative humidity ≤85%. There is no camera on the page. |
| End Effector | It is itself the end-effector. Whether it directly matches the flange, wiring harness, and protocols of the platform must be confirmed on the configuration sheet; the page states that plug-and-play is not the default. |
| Boundary | The standard quantity table for the lift model does not include this gripper. The folding model lists quick-change capability, not that the RMG22-65 is already in the box. The recommended item CTAG2F90-D is also not this model. |
| Configuration Panel | The order should specify model RMG22-65, and state which platform it is mounted on, the quantity, and whether it replaces other gripper models listed in that platform's recommended column. |
| Excerptable | Attachment specifications listed line by line: envelope 5 kg; recommended friction 2 kg; maximum gripping force 130 N; stroke 65 mm; finger height 80 mm; 745 g; open/close time 2 s; repeatability ±0.05 mm; 24 V; 1.9/5.7 A; 45.6/136.8 W; RS485 / Modbus-RTU. |
| Do not write | Do not convert 130 N to 5 kg and then delete the original row. Do not write ±0.05 mm as the repeatability of the attached robotic arm. Do not state battery life. |

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.