Back to News & Insights
Product Insights

Two-finger gripper RMG22-65 | Perception counts channels per the spec sheet: the cover slogan doesn't change the camera count

Count vision and compute channels by the checklist, not by cover slogans. Communication interface: 6-pin aviation connector. Communication protocol: RS485 / Modbus-RTU. Operating environment: 0–50 ℃, relative humidity ≤85%. The page does not list a camera. Standard, included, and optional — these three words must be preserved. An unchecked optional item is not treated as…

2026-10-03
TOBI
Product Insights
Two-finger gripper RMG22-65 | Perception counts channels per the spec sheet: the cover slogan doesn't change the camera count
Product InsightsTwo-Finger Parallel Gripper RMG22-652026-10-03

Count vision and computing channels according to the list, not the cover slogan. 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. Preserve the three terms: standard, included by default, and optional. An optional item that is not checked is not treated as already present.

Perception & Compute

Head-mounted E6 and E2 are another image stream on the human body, not in the sensor list of the two-finger parallel gripper RMG22-65. The human's first-person view and the platform camera must be stored in separate files. E2 has no on-board SLAM, with pose reconstructed offline; E6 training reads the raw frame rate, not the preview. These constraints belong to the head-mounted page; here we only prevent counting them into the platform's channel count.

The depth, lidar, and ultrasonic used for navigation are not the same set as the head or hand cameras. When writing them into a dataset, use different topic names. Identical names will cause the training script to treat the obstacle-avoidance image as an in-hand image.

Copy only the rows that exist for the compute platform. Having Orin 64G does not mean having a 1 TB solid-state drive, and having 1 TB does not mean every adjacent page has one. For products that do not state a processor, do not draw a default compute board in the system diagram. The original text on the page is at /product-gripper-2f.html.

Two-Finger Parallel Gripper RMG22-65
Figure 1 | Two-finger parallel gripper RMG22-65. 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

File the sensor list into four categories: "standard / included by default / optional / cover." 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. When filing, move optional and cover items out of the standard category. Where the cover conflicts with the list, cite the list externally while retaining the sentence "the cover states it differently; it does not constitute delivery." Do not pretend the conflict does not exist, and do not let the cover win.

The computation row is archived separately. If "Orin 64G" is written, one must ask whether there is a solid-state drive capacity. Only if "1T" is written can "1T" be stated. For products where neither row is present, no computation board is drawn in the system block diagram. The processor in the head-mounted unit is not the processor of the embodiment itself.

Camera topic names should be finalized before capture: head, hand, wide-angle, depth, and LiDAR must not share a single name. Navigation depth and hand RGBD are two separate streams even if both are called "depth." When the page for the two-finger parallel gripper RMG22-65 does not provide a topic string, mark the topic name as "project-defined, but must match the number of streams in the inventory"—do not change the stream count to a number that is convenient for writing topic names.

The head-mounted unit and the glove are not included in this list. They may be present in the same experiment, but the list should state "parallel human-side devices" so that training scripts do not treat human images as the robot's own camera. Synchronization is not resolved at this dimension; this dimension only prevents selecting the wrong channel count. The source is /product-gripper-2f.html.

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 a single "degrees of freedom" integer; do not invent one to align with other embodiments. This row only states the number and locations of joints that have been made public. It does not evaluate intelligence, and it does not automatically include waist, legs, neck, or whole-machine totals that are not named on the page. When writing the action vector, create channels only for the parts listed in this row; parts not listed remain blank. Do not write blank as 0, because 0 would be treated by training scripts as a real angle. Do not fill in a degrees-of-freedom integer from another device to complete this row. If the master–slave joint order is not given on the page, mark it as pending written configuration confirmation; do not number it yourself. Joint count is not camera channel count. The action vector creates channels only for the parts named in this row; parts not named remain blank and are not filled with 0.

Load and mass. Maximum envelope grasp load 5 kg. Recommended maximum friction load 2 kg. Maximum gripping force 130 N. The three numbers cannot all be written as the same 5. The numbers on this line must be read with their subjects: rated, self-weight, whole-machine mass, envelope, friction, or gripping force. If the subjects differ, they cannot be merged into one 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. Tool mass is undetermined; do not write the arm's rated value as the graspable object mass. The acceptance table retains original units. During acceptance, read the subject first, then the number; if the subjects do not match, split into two lines.

Dimensions and scale. Overall dimensions 112 × 60 × 167 mm. Stroke 65 mm. Finger height 80 mm. Body weight 745 g. This row describes form-factor or structural scale, used to check doorways, elevators, tabletops, or transport; it is not operating height and not reach. Do not add it to vertical range. If the figure shows protrusions, antennas, or a human 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. The form factor does not include the number of sensor mounts. Doorways, elevators, and transport are checked against form factor only; do not treat this row as operating height.

Operating range. The stroke 65 mm is the finger opening/closing distance, not the robotic arm's reach, nor the platform's vertical working range. This line describes the range that a hand or lift can reach; the definition must follow the original sentence: vertical working range, reach, motion radius, or stroke — these cannot be added together or renamed. If "excluding end effector" is written, it must remain in the figure caption. When the original text does not specify units, keep the "units not specified" note; do not delete it for the sake of tidiness. Field of view is not robotic arm reach. The figure caption retains the range definition from the original sentence, as well as the phrases "excluding end effector" or "units not specified".

Motion. Open / close time 2 s. Position repeatability ±0.05 mm. The 2 seconds is the time basis for opening or closing, not the control frequency. This row describes how the ground base or master arm moves. Four-wheel drive, differential drive, in-place turning 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 in the experimental conditions and is not written back as a specification. If the page does not state slope climbing or positioning, do not borrow from another page. Chassis speed is not sampling rate. Teaching speed may be lower, but the lower speed is recorded in 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. There is no battery capacity and no runtime in hours. This row retains only the electrical terms that appear on the page: voltage, capacity, runtime, charging, current, or power. If there are no "hours," write that runtime is not given; do not fill in hours from an adjacent page. Do not rename charging time as runtime. Rated and maximum must be listed in separate columns. Keep "approximately" where the value is approximate. Do not sum the ampere-hours of multiple devices and present the total as one device's battery. Computing-platform power consumption does not belong in the battery row unless that row states it. Hours, charging, or current that do not appear remain as not given; 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 items already specified in sensors, computing, or communications, and retains the words standard, included, optional, and configurable. Optional items not checked do not count. When the cover and the checklist conflict, cite the checklist while not pretending the cover statement does not exist. Headsets and gloves do not enter this row. Processors, storage capacity, or camera channel counts not written out must not be drawn into the system diagram. This is the main row for channels and computing; standard and optional must be built as separate topics. Optional sensors not purchased do not enter this data dictionary.

End effector. It is itself the end effector. Whether it directly matches the robotic platform's flange, wiring harness, and protocol must be confirmed on the configuration sheet; the page states explicitly that plug-and-play is not assumed by default. This row states which end the contact or gripping occurs at. Quick-change, compatible, and recommended are not models already in the box. A ring fixture on the main arm is not an end-effector gripper. Force, stroke, and load 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. Flange and protocol mappings not given should be written as "to be confirmed," not "plug-and-play." If the hand camera is standard or optional, do not write it as an attribute of the end-effector gripper. "Supports" or "compatible" without a model number cannot be treated as delivered.

Boundary. The standard quantity table for the lift model does not include this gripper. The folding model states quick-change capability, not that RMG22-65 is already in the case. 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 a proposal, copy the boundary into "not included in this order." 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. Extra channel counts on the cover go in the remarks, not into the standard topic. Devices within the boundary must be ordered separately; do not rename old samples to say they already include it.

Configuration column. The order specifies model RMG22-65, and states which robotic platform it is installed on, the quantity, and whether it replaces other gripper models listed in that platform's recommended column. This row distinguishes standard, recommended, and optional. Unchecked recommended and optional items are not delivered. When the standard row conflicts with the parameter table row, both rows are retained, and "locked for this order" indicates which one is actually delivered, rather than striking out one row in the order without a signature. Price and lead time are not written into this row's summary. Unchecked optional depth camera versions or microphones do not create topics. Unchecked recommended and optional items are marked as not delivered on the order.

Excerptable. Copy 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. A line that can be pasted into the attachment has this form: with a subject, with units, and traceable back to the original sentence on the product page. When pasting, keep words such as "approximately", "excluding", "not specified", "optional", and "recommended". Do not convert and keep only the result. If the same number has different meanings on two pages, write it as two lines in the attachment. Do not mix test protocols into the specification excerpt. The attachment should list the original sentences verbatim, not "several cameras". When pasting into the attachment, include words such as "approximately", "excluding", and "optional" along with them.

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 of the attached robotic arm. Do not write battery life. This line is a negative statement for editorial review. It does not describe what the device can do; it only prevents pulling in hours, degrees of freedom, payload subjects, or cover slogans from adjacent pages. If a negative statement is hit, revert to the original product page sentence and do not interpret it as "close enough". Do not bring in success rates from external papers or total hours not published on this site. Do not write 3-channel depth as delivered unless the checklist's original sentence says so. If manuscript retrieval hits a negative statement, revert to the original product page sentence.

ProjectsPublic-Facing Positioning of This Page
Degrees of FreedomThis 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 MassMaximum 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 ScaleOverall dimensions 112 × 60 × 167 mm. Stroke 65 mm. Finger height 80 mm. Body weight 745 g.
Operating RangeThe 65 mm stroke is the finger opening distance, not the robotic arm reach, nor the platform's vertical working range.
MotionOpen / 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.
PowerRated 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 & ComputeCommunication 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 EffectorIt 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.
BoundaryThe 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 PanelThe 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.
ExcerptableAttachment 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 writeDo 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.
Two-finger parallel gripper RMG22-65 product image
Figure 2 | The same product image as at the beginning of the article. The gripper page does not have a second structural exploded view; no unpublished internal structure is added here.

Relationship to Public Methods and Adjacent Pages

The perception configuration determines what the visuomotor policy can see, and also determines what the article cannot claim. The standard configuration, recommended configuration, and cover schematic are often not the same sentence. The lift model's cover once showed "3 depth + 2 wide-angle," while the standard configuration lists one D435 depth camera and two wide-angle cameras. In case of conflict, the standard configuration list prevails, and the conflict note is retained, to prevent sales from verbally presenting the cover number as delivered.

Chassis navigation sensing is a separate group: depth cameras, inertial measurement with encoders, LiDAR, safety bumpers, ultrasonic. They serve chassis obstacle avoidance and localization, not the in-hand camera at the wrist. If a wrist camera is included in the accessories, it must be listed on a separate line and must not be counted into the standard vision path. The compute platform likewise only lists what appears on the page. The folding model lists the core processor as Nvidia Jetson AGX Orin 64G, with no mention of a 1T solid-state drive. The lift model lists Nvidia Jetson AGX Orin 64G and explicitly states an additional 1T solid-state drive. The spec tables for the wheeled humanoid, kit, and gripper do not have this processor line; you cannot write "Orin across the entire series," nor copy the 1T solid-state drive to the folding model.

Head-mounted E6 and E2 are a separate visual pathway, worn on the human body, and are not part of the rig's standard checklist. The human-eye viewpoint and the rig camera viewpoint must be recorded in separate files. The nominal SLAM accuracy in the E6 spec sheet is not ground truth proven by public samples.

This article only inventories the sensing and compute listed on that product page, and points out which line is standard and which line is only a cover claim.

Before handing off to a colleague

Post the sensor list next to the capture computer. One topic name per channel, with "standard," "included," or "optional" copied next to each topic name. Optional topics that have not arrived should be removed from the capture configuration rather than left as empty topics. The extra channel count on the cover is written on a sticky note titled "not delivered." Next to the compute board, note whether the words "SSD capacity" exist; if not, do not attach a 1T label. If the head-mounted camera is recording at the same time, use a separate list to prevent the operator from inserting human images into the base unit topics. Run a diff between the topic configuration file and the product page list. Extra topics in the configuration file must be deleted or marked as project additions; they cannot remain under the standard list's name. Missing standard topics in the configuration file must either be added back or documented in the data notes as not captured, with the reason. Optional topics may only appear if they are checked off on the packing list. When the compute platform's disk capacity is not written on the page, the configuration file must not contain a capacity field, so it is not mistaken for a specification.

First, perform a gap check between the topic and the checklist.

Second, mark extra topics as additional or delete them.

Third, missing standard topics must be noted as not captured.

Fourth, do not create a topic for an unchecked optional item.

Fifth, do not write unavailable disk capacity into the configuration.

Sixth, use a separate checklist for head-mounted.

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.