Back to News & Insights
Product Insights

Isomorphic teleoperation kit | How to read conflicting specs: nice-sounding slogans give way, the parameter table decides

When specifications conflict, present the original text side by side; do not pick the more flattering one. Sentences that need to be listed separately on this isomorphic teleoperation kit page include: main arm self-weight: GLN-RX75 is 7.8 kg, GLN-RX71 is 3.8 kg, local isomorphic kit approximately 1.5 kg (including fixture). Self-weight is not the rated load of the slave end…

2026-10-03
TOBI
Product Insights
Isomorphic teleoperation kit | How to read conflicting specs: nice-sounding slogans give way, the parameter table decides
Product InsightsIsomorphic teleoperation kit2026-10-03

When specifications conflict, present the original text side by side; do not pick the more flattering one. Sentences that need to be separated into columns on this Isomorphic Teleoperation Kit page include: Master arm self-weight: 7.8 kg for GLN-RX75, 3.8 kg for GLN-RX71, approximately 1.5 kg for the local isomorphic kit (including the fixture). Self-weight is not the rated payload at the end effector. 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. Working voltage: DC24V for the first two columns, DC12V for the local column. Power: ≤200 W, ≤100 W, rated 84 W. The specification table has no battery row, so do not write battery life. They look like they are describing "capability," but they are actually different rows. Once merged into one sentence, each party will cite a different number at acceptance.

Specification basis

Units follow the numbers. Millimeters, kilograms, newtons, seconds, revolutions per minute, volts, and ampere-hours must not be dropped when paraphrasing. Configuration: the first two columns are humanoid configurations, the local column is a co-located arm. Grip: the first two columns are handles, the local column is a rail-type ring fixture. If the source material does not state units at certain points, retain the note "unit not specified in the original" externally rather than deleting it to make the numbers look cleaner.

Standard rows, recommended rows, and optional rows are also part of the specifications, not a matter of copywriting tone. 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. When the cover slogan, parameter table, and quantity list are inconsistent, the Isomorphic Teleoperation Kit product page has already chosen to present them side by side rather than collapse them into one. Write the article following this discipline.

A relay summary written for a colleague can be short, but each short phrase must point back to a row in the table. Adjectives that cannot be traced back — such as "high load," "long battery life," or "fully equipped cameras" — do not enter the spec summary. The authoritative table is at /product-teleop-kit.html.

GLN-RX75 main arm, working radius 709 mm
Figure 1 | Isomorphic teleoperation kit. 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

Read the specifications of the Isomorphic Teleoperation Kit by row, not by adjective. It is recommended to copy the product page table onto a check sheet, keeping the subject for each row. The following rows are the most likely to be merged, so mark them in different colors on the check sheet. Load and mass: Master arm self-weight: 7.8 kg for GLN-RX75, 3.8 kg for GLN-RX71, approximately 1.5 kg for the local isomorphic kit (including the fixture). Self-weight is not the rated payload at the end effector. Geometry: Operating radius: 709 mm, 474 mm, 599 mm. This is the scale of the master arm, not the outline of the end-effector body. Configuration: The first two columns are humanoid configuration; the local column is a follower-arm configuration. Grip: The first two columns use a handle; the local column uses a rail-type ring fixture. Motion: Maximum operating speed: 30 RPM for the first two columns, 110 RPM for the local column. All three columns list zero-force drag. Zero-force drag is not force feedback. Power: Working voltage: DC24V for the first two columns, DC12V for the local column. Power: ≤200 W, ≤100 W, rated 84 W. The specification table has no battery row, so do not write battery life. Sensing and computing: Angular resolution: ±0.003° for the first two columns, 0.088° for the local column. Motors: Integrated joints for the first two columns, bus servos for the local column. Communication: RJ45 for the first two columns, RJ45 / 10-pin aviation connector for the local column. End effector and missing items: The fixture in the local column is a rail-type ring fixture used to grip the master arm; it is not the RMG22-65 end-effector. The end-effector 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 master arm models are RX75, RX71, and YDS-DAP-75/65/RX75S respectively.

There is only one rule for color: different subjects must not be painted the same color. Rated load and self-weight are not the same color. Envelope load and friction load are not the same color. Charging time and runtime are not the same color. Standard list and cover slogan are not the same color. Parameter-table model and standard-configuration model are not the same color. Force feedback and zero-force gravity compensation are not the same color.

The second column of the check sheet asks "Can this be written in the same sentence?" The answer is often no. For example, you cannot write "rated 8 kg, 6 hours of battery life," because 8 kg is the self-weight of the lift-type model, 6 hours appears only on the folding-type model, and the two machines cannot be combined into one sentence. The mergeable relationships of the Isomorphic Teleoperation Kit itself follow its own table; do not reference the customary phrasing of another card.

Verify that the third column of the checklist states the source: the product page path /product-teleop-kit.html, and whether that row is standard, recommended, or optional. The contract must specify the column names. Purchasing the robotic platform does not include the kit by default. For teleoperation, look at the first two columns; for local data capture, look at the third column. Orders must still be placed per cell. Numbers without a source are erased from the checklist. Erasing is closer to acceptance than keeping an "approximate" value.

Finally, hand the check sheet to the person writing the contract, not to the person writing the poster to rewrite first. The poster can be short, but every short sentence must be traceable to a full row on the check sheet. If it cannot be found, it should not appear in external text. Copy 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. This is the type of sentence that can be kept, not raw material that can be freely converted.

Line-by-Line Verification

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. This row only states the number of joints and body parts that have been publicly disclosed. It does not evaluate intelligence, nor does it automatically include the waist, legs, neck, or total whole-body count that are not explicitly named on the page. When writing the action vector, channels are created only for 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. Do not fill in the integer degrees of freedom from another device after this row just 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 rather than numbering it yourself. In the specification summary, degrees of freedom are bound to body parts and are not left as a standalone integer. The action vector creates channels only for the body parts named in this row; unnamed body parts are left blank and not filled with 0.

Load and mass. Master arm self-weight: 7.8 kg for GLN-RX75, 3.8 kg for GLN-RX71, approximately 1.5 kg for the local isomorphic kit (including the fixture). Self-weight is not the rated payload at the end effector. The numbers in this row must be read aloud with their subject: rated, self-weight, total 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 objects in the field are heavier, this does not allow the specification to be changed retroactively; a larger specification does not prove that every grasping method reaches that limit. The tool mass is undetermined; do not write the arm's rated value as the graspable object mass. The acceptance table retains the original units. In the specification summary, every mass number retains its subject from the table. At acceptance, read the subject first and then the number; if the subjects do not match, split into two rows.

Outline and dimensions. Operating radius: 709 mm, 474 mm, 599 mm. This is the scale of the master arm, not the outline of the end-effector body. This row is an outline or structural dimension, used to check doors, elevators, tabletops, or transport; it is not operating height, nor is it arm span. Do not add it to the vertical range. If the diagram 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. When restating outline numbers, do not round to phrases like "about 1.7 meters" that lose the millimeter precision. For doors, elevators, and transport, check only the outline; do not treat this row as operating height.

Operating range. Configuration: the first two columns are humanoid configurations, the local column is a same-side arm. Grip: the first two columns are handles, the local column is a rail-type ring fixture. This row describes the range that a 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 caption. When the original text does not mark units, keep the "units not specified" note; do not delete it for tidiness. When restating range figures, do not merge them with the overall height into a single "height". The caption retains the range definition from the original sentence, as well as the phrases "excluding end" or "units not specified".

Motion. Maximum operating speed: the first two columns 30 RPM, the local column 110 RPM. The dragging force column states zero-force dragging for all three columns. Zero-force dragging is not force feedback. This row describes how the ground or the 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 specification. Do not borrow slope-climbing or positioning data from other pages for pages where they are not specified. Mechanism terms shall remain in their original wording and not be translated into more fluent synonyms. 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. 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 write battery life. This line only retains the electrical terms that appear on the page: voltage, capacity, battery life, charging, current, or power. If there is no "hours", write "battery life not specified" — do not fill in hours from an adjacent page. Do not rename charging time as battery life. Rated and maximum values must be listed in separate columns. Preserve "approximately" where approximations appear. Do not sum amp-hours across multiple devices and present the total as one device's battery. When restating electrical rows, do not add hours or amp-hours not present in the table. Hours, charging, or current that do not appear remain "not specified" — do not copy them in from an adjacent page.

Sensing and computing. Angular resolution: ±0.003° for the first two columns, 0.088° for the local column. Motors: Integrated joints for the first two columns, bus servos for the local column. Communication: RJ45 for the first two columns, RJ45 / 10-pin aviation connector for the local column. This row takes inventory of the items explicitly listed in sensing, computing, or communication, and retains the terms standard, included, optional, and selectable. Optional items do not count unless checked. When the cover and the list conflict, cite the list, but do not pretend the cover sentence does not exist. Headsets and gloves do not enter this row. Processors, hard drive capacity, or camera channel counts not written out must not be drawn into the system diagram. When restating sensors, preserve the distinctions between standard, optional, and cover. Optional sensors not purchased do not enter the data dictionary for this order.

End effector. The fixture in the local column is a rail-type ring fixture used to grip the master arm; it is not the RMG22-65 end-effector. The end-effector gripper is ordered separately. This row states at which end contact or gripping occurs. Quick-change, compatible, and recommended are not models already in the box. The ring fixture on the master arm is not the end-effector gripper. Force, stroke, and payload are still retained as-is in their respective rows; they are not merged into a single system metric just because they are mounted on a particular body. Flanges and protocol mappings not given are written as "to be confirmed," not "plug and play." When restating the end-effector row, do not write capability as a list. "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. Keep conflicting rows side by side; do not pick the one that looks more complete. 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. In the summary, standard, recommended, and optional are split into three sentences, not merged into "configured." Unchecked recommended and optional items are written as not delivered on the order.

Excerptable. Copy 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. This is the type of line that can be pasted into an attachment: with subject, with units, and traceable to the original sentence on the product page. When pasting, retain words like approximately, not included, not given, 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 rows in the attachment. Do not mix test protocols into specification excerpts. Only short sentences traceable to the table belong in an external specification summary. When pasting into an attachment, paste words like approximately, not included, and optional along with the numbers.

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 publishing the summary, run a full-text search using the negative statements. If the manuscript hits a negative statement in search, revert to the original sentence on the product page.

ProjectsPublic-Facing Positioning of This Page
Degrees of FreedomAll 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 MassMain 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 ScaleWorking radius: 709 mm, 474 mm, 599 mm. These are the dimensions of the main arm, not the outline of the end unit.
Operating RangeConfiguration: 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.
MotionMaximum 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.
PowerOperating 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 & ComputeAngular 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 EffectorThe 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.
BoundaryForce 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 PanelThe 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.
ExcerptableTranscribe 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 writeDo 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.
Local isomorphic kit, working radius 599 mm, no force feedback support
Figure 2 | Local isomorphic kit. It forms three columns with GLN-RX75 and GLN-RX71; it does not support force feedback, and the grip is a rail-type ring fixture.

Relationship to Public Methods and Adjacent Pages

The specification table is the acceptance criterion; the cover slogan is not. If a slogan and a parameter table conflict on the same page, the parameter table and configuration list take precedence, and the conflict itself must be stated in the article — not quietly resolved by picking a better-sounding number. Copying numbers across pages is even more dangerous: the battery life written for the folding model cannot be written onto the lift model just because the voltages are similar; the repeatability of positioning from the lift model's arm table cannot be written as the whole-body accuracy of the wheeled humanoid.

When reading a table, hold to three rules. First, units follow the numbers. Millimeters, kilograms, newtons, seconds, and degrees must not disappear from the sentence. When the source sentence has no unit, note "the source text did not state a unit; recorded here as millimeters based on context" rather than pretending the original wrote one. Second, adjacent rows cannot be merged. Rated load, self-weight, gripping force, and travel are four different things. Third, standard quantity, recommended configuration, and optional items go in three columns. Recommended is not the same as factory standard.

Data aggregation efforts like Open X-Embodiment illustrate the same point from the opposite direction: cross-embodiment training requires the action space and sensor configuration of each robot to be explicitly recorded. Merging the heights or batteries of three embodiments into a single "company parameter" means the training metadata is wrong from day one.

This article separates the numbers on the product page that are easily merged into a single sentence, and provides wording that can be placed into the configuration sheet. Separating them is not nitpicking wording; it is to avoid each side holding a different number at acceptance.

Before handing off to a colleague

After completing the specification checklist, have another person review only the checklist (not the product page) and trace every line back to the table. Delete any line that cannot be traced back. If two lines have the same color but different subjects, split them. If a cover sentence is parallel to the checklist, keep both sentences, but only cite the checklist in the external summary. Before publishing the summary, search for "left/right," "approximately," "fully equipped," and "standard includes." If these words are not followed by an original sentence, delete them down to the original sentence only. Write the verification date in the corner of the sheet, because the product page may be corrected later and the old summary must match the table at that time. The fourth column of the checklist sheet reads "Can this sentence stand on its own?" Sentences that cannot usually do so because they borrowed the subject of the next line. Split the two lines and read them again. If one of the split lines has no numbers, the numbers came from the other line and the merged sentence should be deleted. External briefs are limited to three lines, one subject per line. If more than three lines are needed, convert to a table; do not chain multiple numbers into one sentence with commas. Chaining numbers into one sentence is a common form of specification failure.

First, every number can be traced back to a table.

Second, if the subject differs, split the sentence.

Third, keep both the cover sheet and the checklist; the abstract only cites the checklist.

Fourth, "approximately", "not included", and "not specified" are not deleted.

Fifth, the verification date is written in the corner of the page.

Sixth, sentences that cannot be traced back are deleted, not polished.

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.