The site-entry checklist contains only publicly disclosed conditions and the written configuration for this engagement. Working radius: 709 mm, 474 mm, 599 mm. This is the scale of the primary arm, not the outline of the slave unit. Maximum operating speed: 30 RPM in the first two columns, 110 RPM in the local column. All three columns list zero-force gravity compensation for the dragging force. Zero-force gravity compensation is not force feedback. Operating voltage: DC24V in the first two columns, DC12V in the local column. Power: ≤200 W, ≤100 W, rated 84 W. The specification table has no battery row, so do not state battery life. Angular resolution: ±0.003° in the first two columns, 0.088° in the local column. Motor: integrated joints in the first two columns, bus servos in the local column. Communication: RJ45 in the first two columns, RJ45 / 10-pin aviation connector in the local column. Check off door width, voltage, camera channel count, emergency stop, and personnel standing positions one by one. If an item cannot be checked off, stop and complete the configuration before collecting any data.
On-Site Deployment
Communications follow the table: if Ethernet, Wi-Fi, RS485, RJ45, 6-pin aviation connector, or Modbus-RTU is written, implement per that page. If no register address is written, do not invent addresses on site. Joint brakes are executed only on arm tables that specify both hard brakes and soft brakes.
Record roles separately: operator, recorder, safety officer. They can be the same person, but the recording sheet has three columns to avoid confusion afterward about who confirmed the emergency stop.
Do not build a training set on the first power-up. First verify direction and open/close motion. Only after the isomorphic teleoperation kit passes verification should you proceed to the data capture discussion supported by /product-teleop-kit.html.

How to Use This Page in This Version
The deployment-day checklist starts with power and doors, not with the model. Working radius: 709 mm, 474 mm, 599 mm. This is the scale of the primary arm, not the form factor of the end-effector platform. Can it fit through the door. Operating voltage: the first two columns are DC24V, the local column is DC12V. Power: ≤200 W, ≤100 W, rated 84 W. The spec sheet has no battery row, so do not write endurance. Check whether on-site power matches; do not include nonexistent endurance in the commissioning schedule. Maximum operating speed: the first two columns are 30 RPM, the local column is 110 RPM. All three columns list zero-force gravity compensation for drag force. Zero-force gravity compensation is not force feedback. Check whether the floor and speed are within published capabilities; on site, slower speeds are acceptable. Angular resolution: the first two columns are ±0.003°, the local column is 0.088°. Motors: 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. Check whether the cameras and compute match the inventory list; if optional items have not arrived, update the data dictionary.
Network and storage use only the interfaces explicitly listed. RJ45, Wi-Fi, RS485, aviation connectors, and Modbus-RTU are wired according to the corresponding page. Do not assume 5G is available on site unless the page lists 5G as a selected option. Do not assume a 1 TB hard drive is available on site unless the page states 1 TB.
Personnel in three columns: operation, recording, safety. The emergency stop is confirmed by the safety column. The first power-on script is a direction check, and its output is a checklist, not an episode. Data collection begins only after the checklist passes, and only according to the written configuration. The fixture in the local column is a rail-type ring fixture used to hold the primary arm; it is not the slave unit's RMG22-65. The slave gripper is ordered separately. When the end effector has not arrived, the check may include unloaded motion, but the filename must be marked as having no end effector, and such data must not be mixed into datasets containing grasping data.
The last line of the deployment record should state the product page version date or the checklist date and point to /product-teleop-kit.html. This way, when specifications are corrected later, it is possible to know which version of the public table the deployment was based on that day. Do not write "one teleoperation kit, approximately 5 kg, with force feedback." Do not combine 30 RPM and 110 RPM into a single speed, and do not combine DC24V and DC12V into a single voltage.
Line-by-Line Verification
Degrees of freedom. All three columns show 7 degrees of freedom, but that does not mean they can be merged into a single unit. The column names are GLN-RX75, GLN-RX71, and a local isomorphic kit. 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 explicitly named on the page. When writing the action vector, create channels only for body parts listed in this row; leave unlisted body parts blank. Do not write blanks as 0, because 0 would be treated by training scripts as a real angle. Also do not fill in the integer degrees of freedom from another device to make this row 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. The joint list for power-on verification is limited to this row. The action vector creates channels only for body parts named in this row; unlisted body parts remain blank and are not filled with 0.
Load and mass. Main arm self-weight: GLN-RX75 is 7.8 kg, GLN-RX71 is 3.8 kg, and the local isomorphic kit is approximately 1.5 kg (including the fixture). Self-weight is not the end-effector rated load. The numbers on this line must be read with their subject: rated, self-weight, overall machine mass, envelope, friction, or gripping force. If the subjects differ, they must not be merged into a single number, nor may any conversion not given on the page be performed. If field objects are heavier, the specification must not be revised accordingly; conversely, a larger specification does not prove that every grasping mode reaches that limit. The tool mass is undetermined — do not write the arm's rated value as the graspable object mass. The acceptance checklist retains the original units. Passing the no-load check does not mean the rated value has been reached. During acceptance, read the subject first and then the number; if the subjects are inconsistent, split them into two lines.
Outline and scale. Working radius: 709 mm, 474 mm, 599 mm. This is the scale of the primary arm, not the outline of the slave unit. This row describes the outline or structural scale, used to check doors, elevators, tabletops, or transport; it is not the operating height, nor is it the arm span. Do not add it to the vertical range. If the diagram shows protrusions, antennas, or personnel 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 include it in the dimension sentence. The first site-entry item is whether this row can pass through doors and elevators. Doors, elevators, and transport are checked only against the outline; do not treat this row as the operating height.
Operating range. Configuration: the first two columns are humanoid configurations, the local column is the same-side arm. Gripping: 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 span, motion radius, or stroke — these cannot be added together or renamed. If "excluding end-effector" is written, it must remain in the figure caption. When the original text does not specify units, keep the note "units not specified" and do not delete it for the sake of tidiness. Net height and shelving are checked against this row during verification, without changing the wording on the spot. The figure caption retains the range definition from the original sentence, as well as phrases such as "excluding end-effector" or "units not specified".
Motion. Maximum operating speed: 30 RPM in the first two columns, 110 RPM in the local column. All three columns list zero-force gravity compensation for the dragging force. Zero-force gravity compensation is not force feedback. This row describes how the ground unit or primary 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. The 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 gradeability or positioning, do not borrow from another page. Chassis front/back orientation and the emergency stop are checked before any speed test. The 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. Operating voltage: DC24V in the first two columns, DC12V in the local column. Power: ≤200 W, ≤100 W, rated 84 W. The specification table has no battery row, so do not state battery life. This row retains only the electrical terms that appear on the page: voltage, capacity, battery life, charging, current, or power. If there is no "hours," state that battery life is not given; 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" for approximate values. Do not sum the ampere-hours of multiple devices and present the total as the battery of a single device. If the power supply does not match, stop; do not collect data first and add a power supply explanation afterward. Hours, charging, or current that do not appear remain as not given; do not copy them in from an adjacent page.
Perception and computing. Angular resolution: ±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 inventories the items already specified in sensors, computing, or communication, and retains the terms standard, included, optional, and optional-order. Unchecked optional items do not count. When the cover conflicts with the checklist, 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 should not be drawn into the system diagram. Topic names are finalized on deployment day; channel counts are not added on the fly. 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 hold the primary arm; it is not the slave unit's RMG22-65. The slave gripper is ordered separately. This row states at which end contact or gripping occurs. Quick-change, compatible, and recommended are not models included in the box. The ring fixture on the primary arm is not the slave gripper. Force, stroke, and payload remain as they are in their respective rows and are not merged into a single system metric because they are installed on a particular unit. Flanges and protocol mappings that are not given should be marked as to be confirmed, not as plug-and-play. When the end effector has not arrived, the filename must be marked as having no end effector. "Supports" or "compatible" without a model number cannot be treated as delivered.
Boundary. Force feedback is write-supported only for GLN-RX75 and GLN-RX71. The local isomorphic suite does not support writes. The primary arm models are RX75, RX71, and YDS-DAP-75/65/RX75S respectively. This line is a deliberate boundary 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 statement; it is to prevent verbally purchasing two pages as one. When writing a proposal, copy the boundary into "Not included in this scope." If a device that is not included is added later, open a new configuration sheet; do not go back and change the robotic platform name in the old sample. Primary arms that have not been ordered must not appear in the wiring table. Devices within the boundary must be ordered separately; do not rename the old sample to imply that it already includes them.
Configuration column. The contract must specify column names. Purchasing the robotic platform does not include the kit by default. For remote operation, look at the first two columns; for local data capture, look at the third column; in either case, order by cell. 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 disagree, 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 summary. Deployment is based on the signed three columns, not the union of all options on the product page. Unchecked recommended and optional items are written as not delivered on the order.
Excerptable. Copy the attachments column by column; do not merge them. 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: it has a subject, includes units, and can be traced back to the original sentence on the product page. When pasting, preserve "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. The deployment record should state the product page it is based on. When pasting into an attachment, paste the words "approximately," "not included," and "optional" along with the content.
Do not write. Do not write "one teleoperation kit, approximately 5 kg, with force feedback". Do not write 30 RPM and 110 RPM as a single rotational speed, and do not write DC24V and DC12V as a single voltage. This line is a negative sentence for review purposes. It does not describe what the equipment can do; it only prevents hours, degrees of freedom, payload subjects, or cover slogans from adjacent pages from being written in. If a negative sentence is hit, revert to the original product-page sentence and do not interpret it as approximately equivalent. Success rates from external papers and total hours not published on this site are likewise not to be written in. Capabilities added verbally on site are not to be entered in the specification column of the deployment record. If manuscript retrieval hits a negative sentence, revert to the original product-page sentence.
| Projects | Public-Facing Positioning of This Page |
|---|---|
| Degrees of Freedom | All three columns have 7 degrees of freedom, but this does not mean they can be merged into a single unit. The column names are GLN-RX75, GLN-RX71, and local isomorphic kit. |
| Load and Mass | Main arm self-weight: GLN-RX75 is 7.8 kg, GLN-RX71 is 3.8 kg, the local isomorphic kit is approximately 1.5 kg (including the fixture). Self-weight is not the rated payload at the end-effector. |
| Form Factor and Scale | Working radius: 709 mm, 474 mm, 599 mm. These are the dimensions of the main arm, not the outline of the end unit. |
| Operating Range | Configuration: the first two columns are anthropomorphic configurations; the local column is the same as the follower arm. Gripping: the first two columns use handles; the local column uses a rail-mounted finger-ring fixture. |
| Motion | Maximum operating speed: the first two columns are 30 RPM, the local column is 110 RPM. All three columns list zero-force gravity compensation. Zero-force gravity compensation is not force feedback. |
| Power | Operating voltage: the first two columns are DC24V, the local column is DC12V. Power: ≤200 W, ≤100 W, rated 84 W. The specification table has no battery row, so do not state battery life. |
| Perception & Compute | Angular resolution: the first two columns are ±0.003°, the local column is 0.088°. Motor: the first two columns use integrated joints, the local column uses bus servos. Communication: the first two columns use RJ45, the local column uses RJ45 / 10-pin aviation connector. |
| End Effector | The fixture in the local column is a rail-type ring fixture used to hold the main arm; it is not the RMG22-65 end-effector. The end-effector gripper is ordered separately. |
| Boundary | Force feedback is listed as supported only for GLN-RX75 and GLN-RX71. The local isomorphic kit is listed as not supported. The main arm models are RX75, RX71, and YDS-DAP-75/65/RX75S. |
| Configuration Panel | The contract must specify column names. Purchasing the platform does not include the kit by default. For remote operation, refer to the first two columns; for local data capture, refer to the third column; in either case, order by the individual cell. |
| Excerptable | Transcribe the attachments column by column; do not merge. Example: GLN-RX75, force feedback supported, 709 mm, 7.8 kg, handle, ±0.003°, 30 RPM, integrated joint, RJ45, DC24V, ≤200 W. |
| Do not write | Do not write "one teleoperation kit, approximately 5 kg, with force feedback." Do not write 30 RPM and 110 RPM as a single speed, and do not write DC24V and DC12V as a single voltage. |

Relationship to Public Methods and Adjacent Pages
Deployment describes site-entry conditions, not slogans. At a minimum it includes: floor load capacity and slope; whether doors and elevators are larger than the unit's dimensions; whether the operating height falls within the vertical range; whether the power supply matches the voltage on the page; who provides the network; where the primary-side workstation is placed; emergency stop and personnel positions; and which computer the recorded files are stored on. The compute platform appears only for products where it is written on the page. The folding model is Nvidia Jetson AGX Orin 64G, with no solid-state drive capacity stated. The lift model is Nvidia Jetson AGX Orin 64G plus a 1T solid-state drive. The wheeled humanoid, kits, and grippers do not default to having the same compute board.
Communication is copied from the table. The recommended arm table for the lifting model lists Ethernet, Wi-Fi, RS485; joints 1–4 have hard brakes, 5–7 have soft brakes. The gripper is RS485 / Modbus-RTU. The kit's main arm is RJ45, and the local column may also be 10-pin. Where no protocol mapping is written, do not invent register addresses in the deployment document.
On personnel, the operator, recorder, and safety officer can be the same person, but the roles must be recorded separately on the log sheet. For the first evaluation, it is recommended to start with a motion check without capturing training data: joint directions, gripper open/close, chassis forward/backward, emergency stop. Only after the check passes should you discuss samples.
This article presents the product intake checklist as short, printable statements.
Before handing off to a colleague
Execute the deployment day checklist in order: doors and power, emergency stop, unloaded direction check, whether the end effector is on the packing list, topic names, and whether file names mistakenly use "episode." If any step fails, stop. Failure records do not enter the training set directory. The specification column of the deployment record may only contain pasted original sentences from the product page; wishes added on site go in the "Not Accepted" column. At the end, photograph the labels: power label, end-effector label, packing list. The photos are part of the deployment record. Deployment photos are named by label type, not with names like IMG_0001. The name must contain power, end effector, or packing list. A deployment record without these three types of photos is not closed. Before closing, review the file names once more; unloaded verification files containing "episode" or "demo" are moved out of the training directory. The move action is written into the deployment record. A verbal claim that files were moved, with no record, is treated as not moved.
First, name photos according to label type.
Second, the record must not be closed if three types of photographs are missing.
Third, move episode files out of the training directory.
Fourth, write the removal action into the record.
Fifth, paste only the original sentence in the specification column.
Sixth, record on-site wishes in the Not Accepted column. Before closing a deployment record, check the Safety column once more to confirm that the emergency stop has been written into the record. A record without an emergency stop entry must not be closed. Once closed, no further specification sentences may be appended to the record.
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.