Back to News & Insights
Product Insights

Isomorphic teleoperation kit | Simultaneous recording is not a shared clock: the time-sync method must be written into the configuration sheet

Pressing start at the same time is not a shared clock. If an isomorphic teleoperation kit and a head-mounted device, leader arm, and gripper are used together, the configuration sheet must specify the master clock, alignment error, and dropped-frame marking. The page does not guarantee that PPS or serial-port time synchronization has been implemented. Powering on the wrist camera and ring locator together is also not time synchronization.

2026-10-03
TOBI
Product Insights
Isomorphic teleoperation kit | Simultaneous recording is not a shared clock: the time-sync method must be written into the configuration sheet
Product InsightsIsomorphic teleoperation kit2026-10-03

Pressing start at the same time is not a shared clock. If an isomorphic teleoperation kit and a head-mounted device, leader arm, and gripper are used together, the configuration sheet must specify the master clock, alignment error, and dropped-frame marking. The page does not guarantee that PPS or serial-port time synchronization has been implemented. Powering on the wrist camera and ring locator together is also not time synchronization.

Time alignment

Sampling rates are copied from their respective pages. The recording frequencies of the glove, head-mounted imaging, and arm are not the same number, and do not invent an intrinsic frequency in this article. Angular resolution: the first two columns ±0.003°, the local column 0.088°. Motors: the first two columns integrated joints, the local column bus servos. Communication: the first two columns RJ45, the local column RJ45 / 10-pin aviation connector. This only determines which sensors are in the inventory; do not rewrite the inventory as a single synchronized Hz.

The consequence of misalignment is that a visuomotor policy learns a misaligned causal relationship: in the image the hand has already closed, but the joint angles are still from the previous frame. Such samples are worse than missing samples, because they look complete.

Before the clock alignment scheme is written out, the synchronization column of the recording sheet is filled with "not committed." Do not fill in "already aligned." /product-teleop-kit.html can be used to check which devices the body has; the clock alignment protocol is not on that page.

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

The synchronization scheme is a separate sheet of paper, not written in the isomorphic teleoperation kit's specification table, because the specification table makes no commitment to clock alignment. The paper must have six rows: who the master clock is; which slave devices there are; what signal is used for alignment; the maximum allowed misalignment; how dropped frames are marked; who signs the recording sheet. If the six rows cannot be written, the synchronization column remains "not committed."

Pressing start simultaneously only proves that a person wants them to go together; it does not prove that the time bases are the same. The wrist camera, light ring, head-mounted device, master arm, gripper, and chassis can share one operator and still each have their own clock. Angular resolution: the first two columns ±0.003°, the local column 0.088°. Motors: the first two columns integrated joints, the local column bus servos. Communication: the first two columns RJ45, the local column RJ45 / 10-pin aviation connector. This sentence only states which sensors exist; it does not state that they share sampling instants.

Do not invent a sampling frequency for the base unit in this article. Gloves and head-mounted images have their own spec-sheet frequencies, and those frequencies must not be filled into the base unit row. The base unit row's frequency follows the written interface specification; if it is not on the page, leave it blank.

The handling rule for misaligned samples is recommended to be written in advance: segments exceeding the allowed misalignment are discarded in their entirety, rather than truncated and still treated as aligned samples. Truncation creates training data that appears continuous but is actually causally wrong. The rule is written in the experiment plan, not in /product-teleop-kit.html, to avoid being mistaken for a factory commitment.

Line-by-Line Verification

Degrees of freedom. All three columns have 7 degrees of freedom, but they must not be merged into a single unit on that basis. The column names are GLN-RX75, GLN-RX71, and local isomorphic kit. This row only states the number and locations of joints that have already been made public. It does not evaluate intelligence, and it does not automatically include the waist, legs, neck, or whole-machine total that are not named on the page. When writing into the action vector, only body parts present in this row get channels; 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 degrees-of-freedom integer from another device after this row to make the numbers add up. If the master-slave joint order is not given on the page, mark it as pending written configuration confirmation; do not number it yourself. When the joint channel frequency is not given on the page, keep it blank; do not substitute the number of degrees of freedom for the frequency. The action vector creates channels only for the body parts named in this row; unnamed body parts remain blank and are not filled with 0.

Payload and mass. Master 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 slave-side rated payload. The numbers in this row must be read with their subject: rated, self-weight, whole-machine mass, envelope, friction, or gripping force. Different subjects cannot be merged into a single number, nor can conversions not given on the page be performed. If field objects are heavier, that cannot be used to revise the specification in reverse; 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 the original units. Payload is unrelated to the clock. During acceptance, read the subject first and then the number; if the subjects do not match, split into two rows.

Dimensions and scale. Operating radius: 709 mm, 474 mm, 599 mm. This is the master arm scale, not the outline of the slave-side 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 reach. Do not add it to the vertical range. If the diagram shows protrusions, antennas, or human standing positions 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. Outline is unrelated to alignment error. Doors, elevators, and transport are checked only against the outline; do not treat this row as operating height.

Operating range. Configuration: the first two columns are humanoid configuration, the local column is the same as the slave arm. Grip: the first two columns are handles, the local column is a rail-type ring fixture. This row describes the range that the hand or lift can reach; the definition must follow the original sentence: vertical working range, arm reach, operating radius, or stroke—these cannot be added to each other or renamed. If "excluding end effector" is written, it must remain in the figure caption. When the original text does not mark units, retain the note "units not marked"; do not delete it for tidiness. Range does not provide sampling instants. The figure caption retains the range definition from the original sentence, as well as the words "excluding end" or "units not marked."

Motion. Maximum operating speed: the first two columns 30 RPM, the local column 110 RPM. The drag force row for all three columns states zero-force drag. Zero-force drag is not force feedback. This row describes how the ground or master arm moves. Four-wheel four-drive, differential, in-place rotation radius, and rotational speed are terms for different mechanisms and cannot substitute for each other. Published speed is a capability, not a recommended teaching speed; teaching can be slower, but the slower speed is written into the experimental conditions, not written back as a specification. For pages that do not state slope climbing or positioning, do not borrow from other pages. If both the chassis and arm are recorded, they still need their own timestamps; do not assume they are already aligned. Teaching speed can be lower, but the lower speed is written into the conditions and does not change the published capability in this row.

Power. Operating voltage: first two columns DC24V, local column DC12V. Power: ≤200 W, ≤100 W, rated 84 W. The spec table has no battery row, so do not write battery life. This line only retains electrical terms that appear on the page: voltage, capacity, battery life, charging, current, or power. If there are no "hours," write "battery life not specified"; do not fill in with hours from adjacent pages. Do not rename charging time as battery life. Rated and maximum must be listed in separate columns. Keep "approximately" for approximate values. Do not sum the amp-hours of multiple devices and attribute them to a single device's battery. Power-on time is not the master clock. Hours, charging, or current that do not appear should remain unspecified and not be copied from adjacent pages.

Perception and computing. Angular resolution: the first two columns ±0.003°, the local column 0.088°. Motors: the first two columns integrated joints, the local column bus servos. Communication: the first two columns RJ45, the local column RJ45 / 10-pin aviation connector. This row inventories the items already specified in perception, computing, or communication, and retains the words standard, included, optional, and selectable. An optional item that is not checked does not count. When the cover and the inventory conflict, cite the inventory while not pretending the cover sentence does not exist. The head-mounted device and glove do not enter this row. Processors, hard drive capacity, or camera channel counts that are not written out should not be drawn into the system diagram. Cameras in the inventory, even if turned on simultaneously, do not equal a common clock. Optional sensors 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 master arm, not the slave-side RMG22-65. The slave-side 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 slave-side 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 that are not given are written as pending confirmation, not plug-and-play. The gripper open/close instants must be marked separately and not merged into image frame numbers unless the synchronization paper already states it. "Supports" or "compatible" without a model number cannot be treated as delivered.

Boundary. Force feedback is only listed as supported 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. 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 description; it is to prevent verbally merging two pages into one when purchasing. When writing a proposal, copy the boundary into "not included in this scope." If a device not included is later added, open a new configuration sheet; do not go back and change the robotic platform name in the old sample. The head-mounted device is not on this page's list, and even less should it be assumed to be time-synchronized with this device. Devices within the boundary must be ordered separately; do not rename old samples to imply they already include it.

Configuration column. The contract must write the column names. Purchasing the body does not by default include the kit. For remote operation, look at the first two columns; for local data acquisition, look at the third column; ordering is still done cell by cell. This row distinguishes standard, recommended, and optional. Recommended and optional items that are not checked are not delivered. When the standard row and the parameter table row conflict, keep both rows and use "locked for this session" to indicate which one is actually delivered, rather than crossing out one of the rows in the order without signing. Prices and lead times are not written into this row's restatement. Sensors not purchased do not participate in the synchronization scheme. Recommended and optional items not checked are written as not delivered on the order.

Excerptable. Accessories are copied 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 row is the type that can be pasted into an attachment: with subject, with units, and traceable back to the original sentence on the product page. When pasting, retain approximately, excluding, 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. Test protocols are not mixed into specification excerpts. If the six rows of the synchronization paper cannot be written, the synchronization column in the attachment is filled with not committed. When pasting into the attachment, paste the words approximately, excluding, and optional along with it.

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 purposes. It does not describe what the equipment can do; it only prevents hours, degrees of freedom, load subjects, or cover slogans from adjacent pages from being written in. If this negative statement is matched, revert to the original product-page sentence and do not interpret it as "approximately." Success rates from external papers and total hours not published on this site must likewise not be written in. It is forbidden to write that PPS alignment with E6 or E2 has been completed unless there is a separate written agreement. If manuscript retrieval matches this negative statement, revert to the original product-page sentence.

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

Pressing start on multiple devices at the same time does not mean the clocks are aligned. The head-mounted unit, master arm, slave arm, gripper, and chassis each have their own sampling clock. Without a common time base, it is impossible afterward to pair "the frame the human saw" with "the joint angles the arm actually reached" into a training sample. When frames are misaligned, the visuomotor policy learns misaligned causality.

The product page does not guarantee that the base unit and E6 or E2 have been synchronized via PPS plus serial port. The wrist camera and ring locator are accessories; powering them on together is not time synchronization. If a project requires synchronization, it must be listed separately in the configuration sheet: who is the master clock, what signal is used, the allowed alignment error, and how dropped frames are marked. If these sentences cannot be written, do not write "synchronized" in the proposal.

Do not mix sampling rates either. The control frequencies of the glove, head-mounted unit, and arm are not the same number. G7 is 120 Hz, G2-L transmits at 50 Hz, and E6 raw imagery can reach 60 Hz. The recording frequency of platform joints follows the actual controller and the written interface; do not invent a frequency that is not written on the page.

This article explains how timestamps should be required when this embodiment is listed alongside the head-mounted device and main arm, and which parts the page has not yet committed to.

Before handing off to a colleague

If the sync sheet has six blank rows, capture can still proceed, but the file name must include "clock not synchronized." Training scripts do not read directories with this marker by default. Do not backfill "it was aligned at the time" after capture ends. A misalignment value may only be used to execute a discard rule if it appears in a written protocol; without a protocol, keep the entire segment as unaligned raw data rather than cutting it into fragments that look continuous. The timestamp field names for head-mounted device, main arm, gripper, and embodiment are separated in advance to avoid overwriting by identical names. The read script for the clock-not-synchronized directory must have an assertion: refuse if the marker is not present in the path. Do not rely on human memory alone. The marker is written in two places: the directory name and the file header. The file header reads "no committed common clock." If a sync protocol is added later, new captures go into a new directory; old directories are not retroactively relabeled as aligned. Retroactive relabeling would make the misalignment at the time appear as though the later protocol had already taken effect.

First, lack of time synchronization must be written into the directory name and the file header.

Second, the script rejects misreadings that are not labeled.

Third, do not relabel as aligned after the fact.

Fourth, a new protocol only covers new directories.

Fifth, keep the timestamp field names of each device separate.

Sixth, without an agreement, do not cut segments into continuous samples.

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.