Operate: virtual training and commissioning of a simulated arm
Twin: a twin-ready view of the arm and its cell
§9 xArm 6
Limitations and open technical questions
What the machine cannot do, and the figures the UFACTORY sources do not give.
Start here
This section says what the machine cannot do and where it must not be used: the limits you work within, the places where UFACTORY's own documents disagree, and the figures the UFACTORY sources do not give.
A limitation is a stated limit. For example, the xArm manual gives the xArm 6 a maximum payload of 5 kg1, and specifies indoor use, away from direct sunlight3.
A contradiction is where sources disagree. For example, UFACTORY's sources give different joint ranges for the xArm 64. When a figure you need is disputed, the lesson shows both sides.
A gap is a figure the UFACTORY sources do not give. For example, neither the xArm manual nor the product page gives an IP rating, the code for how well a housing keeps out dust and water. The manual speaks only of non-waterproof equipment, and of keeping water and dust out5.
S6 in one line: S6 is the xArm 6 cobot that handles parts after processing, routing them to inspection, rework or shipping6.
Scroll
Look back
A question from earlier on, to keep it fresh. Skip it if you like; nothing depends on it.
Choose your depth
Four depths, one page. Switch at any time: every tier stays open to everyone. What the four tiers mean
1Beginner
The limits a newcomer must know
For: Anyone with no robotics background: a visitor, a new operator, a manager Kind of task: Recognise and recall, with plain-language explanations and pictures
In this part you learn how much the arm can carry, where it may be used, and why the word "cobot" does not make it safe to stand beside. No robotics background is needed.
How much it can carry
The xArm manual gives the xArm 6 a maximum payload of 5 kg1.
That limit covers the tool as well as the part: UFACTORY Studio's payload setting is the mass of the end effector plus the object it holds7.
Where it can work
The xArm manual specifies indoor use, away from direct sunlight3.
It gives an ambient temperature range of 0 °C to 50 °C2.
It gives a humidity range of 25% to 85%, non-condensing8.
Its environment list rules out corrosive gas or liquid, flammable materials, oil mists, salt sprays, and dust or metal powder9.
Keep water and dust out of the arm and the controller, and do not let the arm touch liquid. If water gets in, turn off the power and contact the supplier10.
The manual and the product page give no IP rating, the code that says how well a housing keeps out dust and water, for the arm or its control boxes. The manual says instead to keep non-waterproof equipment dry11.
Is it safe to stand beside?
UFACTORY's product page presents the xArm as a collaborative robot, a "cobot". The xArm manual says no people or other equipment should be in the working area while the arm is in operation. Neither source says how the two fit together12.
This platform infers that calling it collaborative does not make a given installation safe to share with people: the manual requires a safety assessment each time the arm is installed13.
The arm can detect a collision, keep to a safety boundary and run in a reduced mode, but these are controller functions someone configures. This project's advice: do not treat them as validated safeguards14.
So the rule is simple. Stay out of the arm's working area while it runs, and do not rely on a safeguard nobody has confirmed15.
Check yourself
Answer, then check. Each option has its own feedback, and nothing is scored.
2Novice
Operating limits
For: Someone who will work near or with the cell: operator, trainee technician Kind of task: Explain and sequence: put steps in order, match parts to their functions
In this part you learn the space the arm can reach, where it moves badly, the rest of the conditions it is rated for, and the limits on its cables and its software. It is for someone who will work near or with the cell.
The space it can reach
The xArm manual gives one Cartesian range for the xArm 5, 6 and 7 together: X ±700 mm, Y ±700 mm, and Z from -400 mm to 951.5 mm16.
UFACTORY's product page says its working-range diagrams for the xArm series are only for safety assessment17.
The manual says to take the arm's range of motion into account when installing it, so that it does not bump into people or equipment, and notes that the working range it shows does not include the end effector18.
Where it moves badly
UFACTORY Studio says that near a singularity, planned straight-line and circular moves cannot be performed correctly, and the arm stops to avoid a high joint speed; joint moves are not affected. It advises keeping out of the central area near the base19.
Studio also says that moving the wrist close to the space directly above and below the base makes the joints move fast even when the arm moves slowly19.
The rest of the environment rules
The xArm manual gives an altitude limit of below 2000 m20.
Its environment list also rules out mechanical shock and vibration, electromagnetic noise and radioactive materials21.
Its common specifications give ISO Class 5 for cleanroom use22.
Wet, dusty or oily places are another matter. This platform infers that the xArm 6 is not suited to wet, washdown, dusty, oily or outdoor environments, such as machining areas with coolant mist or metal chips, without extra protection that UFACTORY does not specify23.
Cables
Use only the arm's original cable, and do not use the arm where that cable has to bend. For a longer or flexible cable, ask the supplier24.
I/O cables between the control box and other machines must not be longer than 30 m, unless extension testing shows a longer cable works25.
Software
The official xArm Python SDK supports Python 3 only26.
UFACTORY's product page says the robot's API is open source, but that connecting the arm to other products takes custom code: most customers will need to write their own libraries and install software packages that do not ship with the robot27.
Check yourself
Answer, then check. Each option has its own feedback, and nothing is scored.
3Intermediate
Programming and maintenance limits
For: Someone who will set up, program or maintain the arm: technician, student engineer Kind of task: Apply: work through written scenarios that need a decision (which mode, which setting, what to do about this error), with feedback on each choice
In this part you learn the limits you meet when you program and look after the arm: what its precision figure covers, the moves the controller refuses, why the firmware and serial number of a particular arm matter, what the manual gives for maintenance, and where UFACTORY's own documents disagree. It is for someone who will set up, program or maintain the arm.
Taught points against computed points
The xArm manual gives the xArm 5, 6 and 7 a repeatability of ±0.1 mm28.
That is repeatability, not accuracy. The UFACTORY sources give no absolute positioning accuracy for the xArm 6: how closely it reaches a computed coordinate. That matters for offline programming and vision-guided picking, which rely on computed coordinates29.
Moves the controller will not make
A singularity occurs when the axes of any two joints lie on one straight line. Near one, planned Cartesian moves, but not joint moves, stop to avoid high joint speed. UFACTORY advises avoiding it, or passing it with a joint move30.
Straight-line and arc moves are solved by inverse kinematics, so a target may have no solution, several, or only an approximate one. Because joint space and Cartesian space are related non-linearly, the joints may also exceed their speed and acceleration limits during such a move31.
For error code C24, speed exceeds limit, Studio says to check whether the arm is at a singularity, or to reduce the speed and acceleration32.
Why the arm's firmware and serial number matter
On xArm 5/6/7 arms, the joint friction parameters used by collision detection are stored in the arm, and pressing and releasing the emergency stop reloads them. On arms before XX1300 they are stored in the controller. UFACTORY says replacing the control box can leave them mismatched, which may falsely trigger collision detection33.
Firmware V2.7.0 fixed an issue where sending zero speed in joint-speed mode could still cause unintended arm motion34.
UFACTORY's release notes give recommended matching versions; the top row is firmware 2.8.2, Studio 2.8.2, Python SDK 1.18.4 and ROS/ROS2 2.0.035.
What the manual gives for maintenance
The manual's Maintenance and Inspection chapter covers only charging during long-term storage, and cleaning. The manual gives no inspection interval, lubrication schedule, brake test or service life for any part; its safety chapter says only to check the bolts "regularly"36.
The arm has a built-in battery. If the arm is not used for 3 months or more, power it on for 6 hours every 3 months to charge the battery, without enabling the arm37.
Where UFACTORY's documents disagree
The xArm manual gives J2 as -117° to 116° and J3 as -219° to 10°. The Studio manual gives J2 as -118° to 120° and J3 as -255° to 11° for the xArm64.
This project's advice: read the arm's serial number before relying on any disputed figure. UFACTORY tells four xArm 6 versions apart by serial number, and the version decides which mass parameters apply38.
Check yourself
Answer, then check. Each option has its own feedback, and nothing is scored.
4Expert
Limits that shape an integration
For: Someone who designs, integrates or changes the cell: integrator, engineer, agent developer Kind of task: Analyse and decide: weigh trade-offs, resolve contradictions, critique a configuration
In this part you sort the machine's limits by what they constrain: an engineering estimate, a safety argument, or the way a program commands the arm. The interfaces section covers the settings an agent could change and the limits of Studio's simulated arm. It is for someone who designs, integrates or changes the cell.
Figures the UFACTORY sources do not give
Speed at full payload. The UFACTORY sources give no cycle-time data for the xArm 6, and no figure for the speed and acceleration it reaches while carrying its full 5 kg across its reach40.
Payload against tool offset. The manual says the payload is related to the TCP offset, but gives no payload-versus-offset values in its text, so the allowable payload at a given tool offset cannot be read from it41.
Service life. The UFACTORY sources give no design life, MTBF or harmonic-drive service life. The only durability figure is the product page's 15,000-hour stress test42.
Open defects. The UFACTORY sources give no public known-issues list for current firmware. Release notes list fixes only after the fact, such as the V2.7.0 zero-speed fix, so open defects in the installed firmware cannot be checked39.
Limits of the safety functions
Neither the xArm manual, the product page nor the Studio manual states an ISO 13849-1 Performance Level or Category, or an IEC 62061 SIL, for any xArm safety function, and none mentions a TÜV certification. Do not assume any43.
The UFACTORY sources do not say whether the xArm 6 is suitable or validated for power and force limiting. They give no contact force or pressure figures for it, and no torque or force threshold for any collision sensitivity level44.
The UFACTORY sources do not say whether collision detection, the safety boundary and reduced mode are enforced independently of the motion-command path. Studio describes the safety boundary only in terms of the tool centre point45.
The manual's stop data covers only Stop Category 1 and Joints 1 to 3, in one configuration, and the manual does not say which arm model was measured. Any separation-distance calculation needs more46.
This project's advice: do not use those figures for separation distances until UFACTORY confirms which arm and configuration they were measured on, and measure the arm's stopping behaviour if the risk assessment needs it47.
The manual describes the control box emergency stop two ways: arm power removed within 300 ms, and Stop Category 1, a deceleration "with drive power on" taking 521 to 885 ms. It does not explain how the two fit48.
Limits of the command interfaces
In servo mode the control box receives commands at up to 250 Hz, and commands sent faster are lost; below 30 Hz the motion may be discontinuous. The speed, acceleration and time parameters of the SDK's servo functions are reserved and do not work at present49.
In Cartesian online planning mode (mode 7) only the base coordinate system can be the reference, not the tool coordinate system for relative motion50.
Firmware V2.7.0 changed self-collision detection so that it no longer checks the end effector against Joint 6 or its link51.
Torque-sensor collision detection, added in Studio V2.7.0, carries UFACTORY's warning that at end speeds of 100 mm/s or more a collision may damage the sensor52.
Studio's environment simulation, which checks for collisions with modelled cubes, cylinders and tables, arrived in V2.7.0, and UFACTORY says it is still in testing53.
Check yourself
Answer, then check. Each option has its own feedback, and nothing is scored.
Not settled
Open questions · 53
What the sources do not settle for this section. Nothing here is papered over with a plausible number.
Kind: Contradiction
UFACTORY sources give different joint ranges for the xArm 6. The xArm manual (section 8.3 and the Preface) gives J2 as -117° to 116° and J3 as -219° to 10°; the Studio manual's specifications table gives J2 as (-118, 120) and J3 as (-255, 11) for the xArm6.
No chapter of the xArm manual (Preface and chapters 1 to 8) and nothing on the xArm product page gives an IP (ingress protection) rating for the xArm 6 or its Control Boxes. The manual refers only to 'non-waterproof equipment' and to keeping water and dust out.
No IP (ingress protection) rating for the xArm 6 arm or its control boxes was found in the manual or the product page. The manual instead warns that the arm and its hardware must not be in direct contact with liquid, and to keep non-waterproof equipment dry.
UFACTORY's xArm product page presents the xArm as a collaborative robot ('cobot'), while the xArm manual says no people or other equipment should be in the working area when the arm is in operation. Neither source says how the two fit together.
No fetched UFACTORY source gives an absolute positioning accuracy for the xArm 6 (how closely it reaches a computed coordinate, as opposed to its ±0.1 mm repeatability). This matters for offline programming and vision-guided picking, which rely on computed coordinates.
The xArm manual's Maintenance and Inspection chapter covers only long-term storage charging and cleaning. No chapter of the fetched manual gives an inspection interval, a lubrication schedule, a brake test or a service life for any part; chapter 1 says only to check the bolts 'regularly'.
No fetched UFACTORY source gives a public known-issues list for current xArm firmware. Release notes list fixes only after the fact, such as the V2.7.0 zero-speed fix, so open defects in the installed firmware cannot be checked.
No fetched UFACTORY source gives cycle-time data for the xArm 6, or the speed and acceleration it reaches while carrying its full 5 kg payload across its reach; the payload versus TCP offset relationship is published only as a figure.
The xArm manual says the payload is related to the TCP offset, but its text gives no payload-versus-offset values; the xArm 6's allowable payload at a given tool offset could not be taken from the sources as text.
No fetched UFACTORY source gives a design life, MTBF or harmonic-drive service life for the xArm 6; the only durability figure is the product page's 15,000-hour stress test.
No chapter of the xArm manual (Preface and chapters 1 to 8), the xArm product page or the Studio manual states an ISO 13849-1 Performance Level or Category, or an IEC 62061 SIL, for any xArm safety function (emergency stop, EI/SI inputs, collision detection, safety boundary or reduced mode), and none mentions a TÜV certification. Do not assume any.
No fetched UFACTORY source says whether the xArm 6 is suitable or validated for power and force limiting collaborative applications. No fetched UFACTORY source gives contact force or pressure figures for the xArm 6, or a torque or force threshold for any collision sensitivity level.
No fetched UFACTORY source says whether the software safety functions (collision detection, safety boundary, reduced mode) are enforced independently of the motion-command path. Studio's description of the safety boundary mentions only the tool centre point, and no source says whether the arm's links or the tool body are checked against it.
The xArm manual gives stop data only for Stop Category 1 and Joints 1 to 3, in one configuration (fully extended, 100% speed, 5 kg payload), and does not say which arm model was measured. No data was found for Joints 4 to 6, for other speeds or payloads, for Stop Category 2 (the SI safeguard stop), or for stopping after a collision is detected. These are needed for any separation-distance calculation at S6.
The xArm manual describes the Control Box emergency stop in ways that do not fit together. Section 2.1.2 says the arm's power supply is removed within 300 ms and that pressing the button powers off the xArm; section 3.2.2 says the button allows the user to cut off the arm's power in the shortest time possible. Section 7.9 says the same button is Stop Category 1, which decelerates the robot 'with drive power on', and section 7.10 gives Stop Category 1 stopping times of 521 to 885 ms. The manual does not explain how power removal within 300 ms fits a powered deceleration lasting up to 885 ms.
Per-joint component data for the xArm 6 (motor model and rating, harmonic-drive ratio, encoder type and resolution, joint-module sizes) is not published in the xArm manual or the product page; the product page names only harmonic drives and servomotors and, unlike the 850's page, gives no encoder resolution.
No dedicated teach pendant for the xArm 6 is documented in the xArm manual or the product page: they describe programming through the browser-based UFACTORY Studio, the SDKs and hand teaching.
No Ethernet connection, camera port, force-torque sensor interface or user button at the xArm 6's tool end is described in the xArm manual or the product page; the product page lists the end-effector I/O as 2 DI, 2 DO, 2 AI and 1 RS-485.
No specification for the BIO Gripper G2, the 6-axis force/torque sensor or the linear motor (payload, force range, resolution, stroke) was found in the xArm manual or the product page; only their names are listed.
Sources disagree on how the xArm AC control box powers the arm: the manual's controller chapter says its internal supply converts 100-240 V AC into 12 V and 48 V DC for the control box and the arm, while the common specification table gives the arm's input as 24 V DC, 20.8 A and the AC controller's output as 24 V DC, 20.8 A.
What tool inputs TI2-TI4 and outputs TO2-TO4 are on the xArm 6 is not documented: UFACTORY Studio lists TI0-TI4 and TO0-TO4, but the xArm manual's tool connector defines only TI0, TI1, TO0 and TO1.
Whether the xArm 6 has an Ethernet connection at the end flange is not answered by the sources fetched: the xArm manual's Robotic Electrical Interface chapter has an 'End Flange' heading with no text, and its tool I/O pins carry no Ethernet.
Sources disagree on the xArm end-effector communication protocol: the online xArm manual's common specification table (and its Gripper table) say Modbus TCP, while the xArm Developer Manual's common specifications and gripper table say Modbus RTU, and the online manual's own Tool RS485 section configures standard Modbus RTU devices.
The future 3D-printed flow in the IntelliMake diagram has no S2 step (printed parts go from S7 straight to S6), but the owner states S2 will handle material for 3D printing in the future. What S2 does in the future flow is unresolved.
Cycle times for S2's moves (S1 to S4, S1 to S3, S3 to S4) and for the S4/S5 laser step are not documented, so throughput and the benefit of two arms cannot be quantified.
The number and positions of allocated S3 staging slots are not documented. The diagram's illustration shows six pads on the table, but it is a drawing, not a specification.
The layout draws unlabelled return paths from the laser and S6 region back toward S1 and S2. Whether reworked parts re-enter through S1 or S2, and what S2 does in rework, is not documented.
IntelliMake's reason for using two arms, and for putting the 850 at S2 and the xArm 6 at S6, is not documented in any source available to this project (Q14d).
The project specification describes S6 as the downstream arm that handles parts after processing, but IntelliMake's future 3D-printed flow has S6 handling parts before laser engraving (S7 → S6 → S4/S5). S6's role is therefore not simply 'after processing' in the future flow.
S2's current, as-built automation level in the physical cell is not documented. Level 5E is this project's target (int-041), not a description of the cell today (Q14c).
As published, the xArm manual's 'Limitation of Liability' section says safety information 'must be construed as a warranty by UFACTORY' that the xArm will not cause injury or damage even if all safety instructions are complied with. That wording sits under a heading about limiting liability, and no fetched source says what UFACTORY intended. Do not read it as a guarantee of safety.
UFACTORY sources disagree on the collision sensitivity range. Studio's Settings page says levels 1 to 5; Studio's glossary and the Python SDK say 0 to 5, and the glossary says 0 disables collision detection. A learner reading only the Settings page would not learn that the value can switch detection off.
The EMC standards the xArm manual lists do not match the EMC verification it links. Section 7.2 lists EMC 2004/108/EC, EN 61000-6-2:2005 and EN 61000-6-4:2007+A1:2011 as the standards the xArm 6 meets. The linked SGS EMC verification names EN IEC 61000-6-2:2019 and EN IEC 61000-6-4:2019 under Directive 2014/30/EU. Section 7.3 lists both the older editions and the 2019 editions without saying which apply.
The xArm manual's Preface and Hardware Installation chapter say they apply to models XF1305, XI1305 and XS1305, and the linked RoHS certificate lists those numbers among others. The linked SGS machinery and EMC verifications name models XI13 and XI15. No fetched text says whether XI13 and XI15 cover the 1305 models, or which model number is on the S6 xArm 6's label.
The xArm manual says the arm will 'slightly brake and fall' when the emergency stop is pressed, but no fetched source says how far it may fall, at which joints, or how long the brakes take to engage.
No fetched UFACTORY source gives an explicit intended-use or reasonably foreseeable misuse statement for the xArm 6, beyond the environmental conditions and the general warnings in chapter 1.
The EU Declaration of Conformity for the xArm 6 was not found. The manual says the xArm 6 has passed EU CE certification, and both SGS verifications say the CE mark can be affixed or used, under the responsibility of the manufacturer, after completion of a Declaration of Conformity.
The S6 xArm 6's controller type (AC or DC), serial number, firmware, Studio and SDK versions are not confirmed. The serial number matters because UFACTORY treats arms before XX1300 differently for friction parameters and the IMU mounting check, and firmware decides which SDK safety calls are available.
Sources disagree on the xArm 6's weight: 12.5 kg (arm only) in the online hardware manual and the product page's comparison table, but 12.2 kg (body only) in UFACTORY's support article comparing the xArm 5 Lite, 6 and 7. The product page's introduction also says '15kg weight' without naming a model.
Sources disagree on the range of the xArm 6's joint 2 (J2): the online hardware manual (specifications and preface) and the product page give -117° to 116°, but UFACTORY's support article comparing the xArm 5 Lite, 6 and 7 gives -118° to 120°, and the xarm6 URDF's default limits are -2.059 to 2.0944 rad (about -118° to 120°).
Sources disagree on the range of the xArm 6's joint 3 (J3): the online hardware manual (specifications and preface) and the product page give -219° to 10°, but UFACTORY's support article comparing the xArm 5 Lite, 6 and 7 gives -225° to 11°, and the xarm6 URDF's default limits are -3.927 to 0.19198 rad (about -225° to 11°).
The xArm manual disagrees with itself on what the AC control box supplies: its specification table (and the product page) give the AC controller's output as 24 V DC, 20.8 A, but its 3.2.2 Power Supply text says the internal switching power supply converts 100–240 V AC into 12 V and 48 V DC, which powers the control box and the robotic arm.
No dimensioned base or tool-flange drawing values for the xArm 6 (bolt size and count, hole pattern, bolt torque, base height) were captured as text: the manual's 'Robot Base Mounting' section and the product page's 'Robot base mounting (mm)' and 'Robot tool head' drawings are images only.
The xArm 6's working range (workspace envelope) is given only as figures: the manual's 'Define Working Space' section and the product page show drawings, and the product page says its working-range diagrams are only for safety assessment. No workspace dimensions beyond the Cartesian range and the 700 mm reach were captured as text.
The xArm manual gives two lower limits for the AC control box's mains input: 100 V in its specification table and power-supply section, but 110 V in its installation steps ('AC (110V-240V)').
Sources disagree on the xArm's end-effector communication protocol: the manual's common specification table says Modbus TCP, but the product page says Modbus RTU over RS-485, and the manual's own Tool RS485 section configures standard Modbus RTU end effectors. The manual's Gripper table likewise pairs RS-485 communication with a 'Modbus TCP' protocol.
The xArm manual's list of applied standards does not include ISO/TS 15066; no statement of ISO/TS 15066 conformance for the xArm 6 was found in the manual or the product page.
No noise (sound pressure) figure for the xArm 6 arm was found in the manual or the product page; the only noise figure given is for the Vacuum Gripper accessory (under 60 dB at 30 cm).
The product page lists the xArm's 'Base Connector Type' as M5*5 and does not say which connector this is; the manual's specification table does not list a base connector.
UFACTORY sources give different joint ranges for the xArm 6. The xArm manual (section 8.3 and the Preface) gives J2 as -117° to 116° and J3 as -219° to 10°; the Studio manual's specifications table gives J2 as (-118, 120) and J3 as (-255, 11) for the xArm6.
Evidence · 4 citations
Joint Range | J1~J6 (±360°, -117~116°, -219~10°, ±360°, -97~180°, ±360°)
No chapter of the xArm manual (Preface and chapters 1 to 8) and nothing on the xArm product page gives an IP (ingress protection) rating for the xArm 6 or its Control Boxes. The manual refers only to 'non-waterproof equipment' and to keeping water and dust out.
Evidence · 1 citation
Make sure that all the non-waterproof equipment is kept dry.
UFACTORY xArm Hardware Manual (online), 3. Controller Electrical Interface · UFACTORY · 3.1 Electrical Alarms and Cautions, NOTICE [series text: names no single model]
UFACTORY Studio says to set the TCP payload and TCP offset according to the actual situation. The TCP payload is the actual mass of end-effector plus object in kg, with its centre of gravity in mm in the default TCP frame at the flange centre; with virtually no load, both must be set to 0. The TCP offset gives the tool centre point's position (X, Y, Z) and orientation (roll, pitch, yaw) relative to the flange-centre frame.
Evidence · 5 citations
Set TCP Payload and TCP Offset according to the actual situation.
UFACTORY Studio User Manual (online), 7. Settings · UFACTORY · 7.1.2 TCP [general Studio text; the Studio manual says it applies to the xArm6]
TCP Payload: The load weight refers to the actual mass (end-effector + object) in Kg; X/Y/Z-axis represents the position of the centre of gravity of payload in mm
UFACTORY Studio User Manual (online), 7. Settings · UFACTORY · 7.1.2 TCP [general Studio text; the Studio manual says it applies to the xArm6]
The xArm manual says to prevent water or dust getting into the arm or controller, that the arm and its hardware must not be in direct contact with liquid or left in a humid environment for a long time, and that if water enters the product, to turn off the power and contact the supplier.
Evidence · 3 citations
Prevent the ingress of water or dust into the mechanical arm or controller.
UFACTORY xArm Hardware Manual (online), 1. Safety · UFACTORY · 1.4 Personnel Safety, DANGER [series text: names no single model]
The robotic arm and its hardware composition must not be in direct contact with the liquid, and should not be placed in a humid environment for a long time.
No IP (ingress protection) rating for the xArm 6 arm or its control boxes was found in the manual or the product page. The manual instead warns that the arm and its hardware must not be in direct contact with liquid, and to keep non-waterproof equipment dry.
Evidence · 2 citations
The robotic arm and its hardware composition must not be in direct contact with the liquid, and should not be placed in a humid environment for a long time.
Make sure that all the non-waterproof equipment is kept dry.
UFACTORY xArm Hardware Manual (online), 3. Controller Electrical Interface · UFACTORY · 3.1 Electrical Alarms and Cautions, item 1 (manual for the xArm series; this passage names no single model)
UFACTORY's xArm product page presents the xArm as a collaborative robot ('cobot'), while the xArm manual says no people or other equipment should be in the working area when the arm is in operation. Neither source says how the two fit together.
Calling the xArm 6 'collaborative' does not make a given installation safe to share with people: the xArm manual says a safety assessment is required each time the arm is installed, and that a comprehensive safety assessment of the whole system should be performed when the xArm works with other machinery.
Why we infer this:UFACTORY uses 'collaborative' as a product description (app-504, app-509). The xArm manual separately requires a safety assessment for each installation and for the whole system when the arm works with other machinery. So the label describes the arm's features, not a guarantee that a particular cell allows people to work beside it.
Evidence · 2 citations
A safety assessment is required each time installed.
Kind: RecommendationThis project's simulation and agent design, not the physical cellProject design, not the physical cellsafety-594
Project advice
Treat the xArm 6's collision detection, safety boundary and reduced mode as configurable controller functions, not validated safeguards: they must not replace risk-assessed protective devices wired to the EI and SI inputs.
This is advice from this project, based on: safety-578 Gapsafety-559 Verifiedsafety-560 Verifiedsafety-561 Verifiedsafety-564 Verifiedsafety-565 Verifiedsafety-544 Verified
Why:No fetched UFACTORY document gives these functions a Performance Level or SIL. Collision detection is a current-model comparison that UFACTORY says can false-trigger and can be switched off; the safety boundary and reduced mode are settings. A function with no documented rating cannot stand in for a rated protective device.
Kind: RecommendationAwaiting cell accessThis project's simulation and agent design, not the physical cellProject design, not the physical cellsafety-599
Project advice
Until the S6 emergency stops, guarding, Control Box position and risk assessment are confirmed at the cell, act as though none of them exists: stay out of the xArm 6's working area while it runs, and do not rely on a safeguard nobody has confirmed.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
This is advice from this project, based on: safety-586 Gap, awaiting cell accesssafety-587 Gap, awaiting cell accesssafety-588 Gap, awaiting cell accesssafety-589 Gap, awaiting cell accesssafety-511 Verified
Why:The manual says no people should be in the working area during operation, and none of the S6 safety provisions it calls for has been confirmed. Assuming they exist would put people at risk if they do not.
The xArm manual's common specifications for the xArm5, xArm6 and xArm7 give a Cartesian range of X ±700 mm, Y ±700 mm and Z from -400 to 951.5 mm, with roll, pitch and yaw ±180°.
When installing the xArm, the manual says to take its range of motion into account so that it does not bump into people and equipment around it, and notes that the working range it shows does not include the end-effector. The manual gives one working-range figure for the xArm5 and xArm6 together.
Evidence · 2 citations
When installing the robotic arm, make sure the range of motion of the robotic arm is taken into account, so as not to bump into the surrounding people and equipment (the end-effector not included in the working range).
UFACTORY xArm Hardware Manual (online), 2. Hardware Installation · UFACTORY · 2.2.2 Define Working Space [series text: names no single model]
UFACTORY Studio says that near a singularity, planned Cartesian moves (linear, circular, but not joint moves) cannot be performed correctly and the arm stops to avoid a high instantaneous joint speed. It advises avoiding the central area near the base, and, when choosing a mounting place, considering the cylindrical volume directly above and below the base. It says moving the wrist joint close to that volume should be avoided if possible, because it makes the joints move fast even when the arm moves slowly and makes a risk assessment difficult.
Evidence · 4 citations
When the robot performs motion planning (linear, circular, etc., excluding joint movements) near the singularity point, it will stop to avoid high instantaneous speed of the joint when it passes the singularity point.
UFACTORY Studio User Manual (online), 9. Motion Characteristics · UFACTORY · 9.3 Singularity, Characteristics [general Studio text; the Studio manual says it applies to the xArm6]
so the robotic arm should try to avoid passing directly the central area near the base, which is likely to cause 1st Joint speed too high.
UFACTORY Studio User Manual (online), 9. Motion Characteristics · UFACTORY · 9.3 Singularity [general Studio text; the Studio manual says it applies to the xArm6]
It is important to consider the cylindrical volume directly above and directly below the base of the robotic arm when a mounting place for the robotic arm is chosen.
UFACTORY Studio User Manual (online), 9. Motion Characteristics · UFACTORY · 9.3, Note [general Studio text; the Studio manual says it applies to the xArm6]
Quote not shown (over 40 words). See the source at: 9.3, Note [general Studio text; the Studio manual says it applies to the xArm6].
UFACTORY Studio User Manual (online), 9. Motion Characteristics · UFACTORY · 9.3, Note [general Studio text; the Studio manual says it applies to the xArm6]
The xArm 6 is not suited to wet, washdown, dusty, oily or outdoor environments, such as machining areas with coolant mist or metal chips, without extra protection that UFACTORY does not specify.
Why we infer this:Verified: the manual excludes oil mists, dust and metal powder, requires indoor use, and says to keep water and dust out; it gives no IP rating (see the IP gap). Inferred: the listed conditions rule out the example environments unless extra protection is added. No UFACTORY source describes such protection for the xArm 6.
Evidence · 4 citations
No oil mists.
UFACTORY xArm Hardware Manual (online), 7. Production Information · UFACTORY · 7.4 Disposal and Environment [series text: names no single model]
The xArm manual says to use only the arm's original cable and not to use the arm in applications where the cable needs to be bent, and to contact the supplier for a longer or flexible cable.
Evidence · 1 citation
Use only the original cable of the robotic arm. Do not use the robotic arm in applications where the cable needs to be bent. If you need a longer cable or flexible cable, please contact your supplier.
UFACTORY xArm Hardware Manual (online), 3. Controller Electrical Interface · UFACTORY · 3.1 Electrical Alarms and Cautions, NOTICE [series text: names no single model]
The xArm manual says I/O cables between the Control Box and other machines and plant equipment must not exceed 30 m unless extension testing shows a longer cable is feasible.
Evidence · 1 citation
The length of the I/O cable that used to connect the Control Box with other mechanical and plant equipment must not exceed 30 meters unless it is feasible after the extension testing.
UFACTORY xArm Hardware Manual (online), 3. Controller Electrical Interface · UFACTORY · 3.1 Electrical Alarms and Cautions, CAUTION [series text: names no single model]
UFACTORY's xArm product page says its robot API is open source, but that integrating with other products requires custom code: most customers will need to write custom libraries and install software packages that are not shipped with the robot.
Evidence · 1 citation
While all integrations are possible, they all require custom code work i.e. most customers will need to write custom libraries and install software packages that are not shipped with the robot.
UFACTORY xArm product page · UFACTORY · Tech Specs, Compatibility, API Compatibility [page covers xArm 5, 6 and 7]
No fetched UFACTORY source gives an absolute positioning accuracy for the xArm 6 (how closely it reaches a computed coordinate, as opposed to its ±0.1 mm repeatability). This matters for offline programming and vision-guided picking, which rely on computed coordinates.
Evidence · 1 citation
Repeatability | ±0.1mm
UFACTORY xArm Hardware Manual (online), 8. Technical Specifications · UFACTORY · 8.1 Common Specifications: repeatability only [names the xArm 6]
A singularity occurs when the axes of any two joints lie on one straight line; the arm's degrees of freedom are degraded and some joints may turn too fast. Near one, planned Cartesian moves (not joint moves) stop to avoid high joint speed, so UFACTORY advises avoiding it or passing it with a joint move.
Evidence · 2 citations
Quote not shown (over 40 words). See the source at: 9.3 Singularity (manual text not model-specific; the Studio manual's Preface lists the xArm 6 among the models it applies to).
UFACTORY Studio User Manual (online), 9. Motion Characteristics · UFACTORY · 9.3 Singularity (manual text not model-specific; the Studio manual's Preface lists the xArm 6 among the models it applies to)
UFACTORY Studio says Cartesian (linear and arc) moves are solved by inverse kinematics, so they may have no solution, several solutions or only approximate ones, and that because joint space and Cartesian space are related non-linearly, the joints may exceed their maximum speed and acceleration limits during such moves.
Evidence · 1 citation
Quote not shown (over 40 words). See the source at: 4.4 Position & Joint Control, Linear Motion [general Studio text; the Studio manual says it applies to the xArm6].
UFACTORY Studio User Manual (online), 4. Live Control · UFACTORY · 4.4 Position & Joint Control, Linear Motion [general Studio text; the Studio manual says it applies to the xArm6]
For C24 (speed exceeds limit), Studio says to check whether the xArm is at a singularity, or reduce the speed and acceleration. For C37 (abnormal motion in manual mode), it says to check that the TCP payload and installation settings match reality.
Evidence · 2 citations
C24 | Speed Exceeds Limit | Please check if the xArm is at singularity point, or reduce the speed and acceleration values.
UFACTORY Studio User Manual (online), 12. Error Handling · UFACTORY · 12.1, table, C24 [general Studio text; the Studio manual says it applies to the xArm6]
C37 | Abnormal Motion in Manual Mode | Please check whether the TCP payload setting of the robotic arm and the installation method of the robotic arm match the actual settings.
UFACTORY Studio User Manual (online), 12. Error Handling · UFACTORY · 12.1, table, C37 [general Studio text; the Studio manual says it applies to the xArm6]
UFACTORY's support article says that for xArm 5/6/7 arms the joint friction parameters used by collision detection are stored in the arm and are reloaded by pressing and releasing the emergency stop, while for xArm 5/6/7 arms before XX1300 they are stored in the controller and reloading needs technical support. It says replacing the control box can leave the stored parameters mismatched, and that a mismatch may falsely trigger collision detection.
Evidence · 5 citations
xArm 5/6/7 | Robot Arm | Press and release the emergency stop
Collision Detection in UFACTORY Robotic Arms: Current and Dynamic Model-based Feature (UFACTORY support article) · UFACTORY · Section 2.3 Friction Parameters, table [names xArm 5/6/7]
UFACTORY's release-note version list gives recommended matching versions; the top row is firmware 2.8.2, UFACTORY Studio 2.8.2, Python SDK 1.18.4 and ROS/ROS2 2.0.0. The firmware and Studio packages are listed for the 'xarm series, UFactory 850'.
The xArm manual's Maintenance and Inspection chapter covers only long-term storage charging and cleaning. No chapter of the fetched manual gives an inspection interval, a lubrication schedule, a brake test or a service life for any part; chapter 1 says only to check the bolts 'regularly'.
Evidence · 2 citations
If the robotic arm is not used for a long time (≥3 months)
UFACTORY xArm Hardware Manual (online), 5. Maintenance and Inspection · UFACTORY · 5. Maintenance and Inspection (whole chapter: Long-term placement and Clean) [series text: names no single model]
The xArm arm contains a built-in battery: if the arm is not used for 3 months or more, the manual says to power it on for 6 hours every 3 months to charge the battery, without enabling the arm.
Evidence · 2 citations
If the robotic arm is not used for a long time (≥3 months), you need to power on the robotic arm for 6 hours every 3 months to charge the built-in battery of the robotic arm.
UFACTORY xArm Hardware Manual (online), 5. Maintenance and Inspection · UFACTORY · 5. Maintenance and Inspection, 'Long-term placement' (manual for the xArm series; this passage names no single model)
UFACTORY xArm Hardware Manual (online), 5. Maintenance and Inspection · UFACTORY · 5. Maintenance and Inspection, 'Long-term placement' (manual for the xArm series; this passage names no single model)
Read the S6 xArm 6's serial number before relying on any figure the sources disagree on (weight, J2 and J3 ranges): UFACTORY distinguishes four xArm 6 versions by serial number, and the S6 arm's version decides which mass parameters apply.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
This is advice from this project, based on: comp-511 Verified, awaiting cell accessspec-506 Contradiction, awaiting cell accessspec-516 Contradiction, awaiting cell accessspec-517 Contradiction, awaiting cell access
Why:The mass parameters are published per version (comp-511), so the S6 arm's version must be known to use them. The sources that disagree on weight and joint ranges (spec-506, spec-516, spec-517) do not say whether version explains the difference; knowing the version is a cheap first step, not a resolution. The serial number is on the physical arm, so this needs cell access.
Evidence · 2 citations
The purpose of this article is to guide the user to distinguish the model of UFactory xArm by SN.
Kinematic and Dynamic Parameters of xArm Series: telling the model by SN (support article) · UFACTORY · Introduction
No fetched UFACTORY source gives a public known-issues list for current xArm firmware. Release notes list fixes only after the fact, such as the V2.7.0 zero-speed fix, so open defects in the installed firmware cannot be checked.
Evidence · 1 citation
Fixed an issue where sending zero speed in joint-speed mode could still cause unintended arm motion.
UFACTORY Release Note v2.7.0 · UFACTORY · Firmware V2.7.0 list
No fetched UFACTORY source gives cycle-time data for the xArm 6, or the speed and acceleration it reaches while carrying its full 5 kg payload across its reach; the payload versus TCP offset relationship is published only as a figure.
Evidence · 1 citation
The payload is related to the tcp offset.
UFACTORY xArm Hardware Manual (online), 7. Production Information · UFACTORY · 7.11 Max Payload [series text: names no single model]
The xArm manual says the payload is related to the TCP offset, but its text gives no payload-versus-offset values; the xArm 6's allowable payload at a given tool offset could not be taken from the sources as text.
UFACTORY xArm Hardware Manual (online), 7. Production Information · UFACTORY · 7.11 Max Payload (manual for the xArm series; this passage names no single model)
No fetched UFACTORY source gives a design life, MTBF or harmonic-drive service life for the xArm 6; the only durability figure is the product page's 15,000-hour stress test.
Evidence · 1 citation
Stress-tested for at least 15,000 hours of full-time operation.
No chapter of the xArm manual (Preface and chapters 1 to 8), the xArm product page or the Studio manual states an ISO 13849-1 Performance Level or Category, or an IEC 62061 SIL, for any xArm safety function (emergency stop, EI/SI inputs, collision detection, safety boundary or reduced mode), and none mentions a TÜV certification. Do not assume any.
Evidence · 2 citations
All safety I/Os exist in pairs (redundancy) and must be kept in two separate branches.
UFACTORY xArm Hardware Manual (online), 3. Controller Electrical Interface · UFACTORY · 3.4.1 Safety IO(EISI): redundancy described, no PL or Category stated [series text: names no single model]
UFACTORY xArm Hardware Manual (online), 7. Production Information · UFACTORY · 7.12 Certification: only the SGS MD and EMC verifications and a RoHS certificate are linked [series text: names no single model]
No fetched UFACTORY source says whether the xArm 6 is suitable or validated for power and force limiting collaborative applications. No fetched UFACTORY source gives contact force or pressure figures for the xArm 6, or a torque or force threshold for any collision sensitivity level.
Evidence · 1 citation
the smaller the additional torque required for the robotic arm to trigger collision protection
UFACTORY Studio User Manual (online), 7. Settings · UFACTORY · 7.1.1, Collision Detection Sensitivity: levels described only relatively [general Studio text; the Studio manual says it applies to the xArm6]
No fetched UFACTORY source says whether the software safety functions (collision detection, safety boundary, reduced mode) are enforced independently of the motion-command path. Studio's description of the safety boundary mentions only the tool centre point, and no source says whether the arm's links or the tool body are checked against it.
Evidence · 1 citation
If the tool center point (TCP) of the robotic arm exceeds the set safety boundary, the robotic arm will stop moving.
UFACTORY Studio User Manual (online), 7. Settings · UFACTORY · 7.3.1 Safety Boundary [general Studio text; the Studio manual says it applies to the xArm6]
The xArm manual gives stop data only for Stop Category 1 and Joints 1 to 3, in one configuration (fully extended, 100% speed, 5 kg payload), and does not say which arm model was measured. No data was found for Joints 4 to 6, for other speeds or payloads, for Stop Category 2 (the SI safeguard stop), or for stopping after a collision is detected. These are needed for any separation-distance calculation at S6.
Evidence · 2 citations
Stop Category 1 stopping distances and times.
UFACTORY xArm Hardware Manual (online), 7. Production Information · UFACTORY · 7.10 Stop Time and Stop Distance [names no model]
Kind: RecommendationAwaiting cell accessThis project's simulation and agent design, not the physical cellProject design, not the physical cellsafety-597
Project advice
Do not use the xArm manual's Stop Category 1 figures for S6 separation distances until UFACTORY confirms which arm and configuration they were measured on; measure the S6 arm's stopping behaviour at the cell if the risk assessment needs it.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
This is advice from this project, based on: safety-535 Verifiedsafety-534 Inferredsafety-580 Gap
Why:The table names no model, its figures are identical to the 850 manual's, and it covers only Joints 1 to 3 in one configuration. A separation distance built on it would rest on data that may not describe the S6 arm.
The xArm manual describes the Control Box emergency stop in ways that do not fit together. Section 2.1.2 says the arm's power supply is removed within 300 ms and that pressing the button powers off the xArm; section 3.2.2 says the button allows the user to cut off the arm's power in the shortest time possible. Section 7.9 says the same button is Stop Category 1, which decelerates the robot 'with drive power on', and section 7.10 gives Stop Category 1 stopping times of 521 to 885 ms. The manual does not explain how power removal within 300 ms fits a powered deceleration lasting up to 885 ms.
Evidence · 7 citations
the power supply for the robotic arm will be removed within 300ms.
In servo mode the Control Box receives commands at up to 250 Hz, and commands sent faster are lost; below 30 Hz the arm's motion may be discontinuous. The speed, acceleration and time parameters of the SDK's servo functions are reserved and do not work at present.
Evidence · 4 citations
In servoj mode, the maximum receiving frequency of the control box is 250 Hz
UFACTORY Studio User Manual (online), 10. Robotic Arm Motion Mode and State · UFACTORY · 10.1 Mode 1: Servo(ServoJ) Mode [general Studio text; the Studio manual says it applies to the xArm6]
If the frequency of sending commands exceeds 250 Hz, the redundant commands will be lost.
UFACTORY Studio User Manual (online), 10. Robotic Arm Motion Mode and State · UFACTORY · 10.1 Mode 1 [general Studio text; the Studio manual says it applies to the xArm6]
If the frequency is lower than 30 Hz, the motion of the robotic arm may be discontinuous.
UFACTORY Studio User Manual (online), 10. Robotic Arm Motion Mode and State · UFACTORY · 10.1 Mode 1, Servo Cartesian Motion [general Studio text; the Studio manual says it applies to the xArm6]
The xArm-Python-SDK interface function we provide also reserves the speed, acceleration and time settings, but they will not work at present.
UFACTORY Studio User Manual (online), 10. Robotic Arm Motion Mode and State · UFACTORY · 10.1 Mode 1 [general Studio text; the Studio manual says it applies to the xArm6]
In Cartesian online planning mode (mode 7), UFACTORY says only the base coordinate system can be used as the reference, not the tool coordinate system for relative motion.
Evidence · 1 citation
Cartesian online planning mode can only use the base coordinate system as the reference coordinate system, not the tool coordinate system for relative motion.
UFACTORY Studio User Manual (online), 10. Robotic Arm Motion Mode and State · UFACTORY · 10.1 Mode 7: Cartesian online planning Mode, Note [general Studio text; the Studio manual says it applies to the xArm6]
Torque-sensor-based collision detection, added in Studio V2.7.0, carries UFACTORY's warning that at end speeds of 100 mm/s or more the sensor may be damaged by a collision.
Evidence · 2 citations
Added torque sensor collision detection.
UFACTORY Studio V2.7.0 New Feature · UFACTORY · Settings - Externals - Torque Sensor
UFACTORY Studio's environment simulation, which checks for collisions with modelled cubes, cylinders and tables, was added in V2.7.0 and UFACTORY says it is still in testing.
Evidence · 2 citations
Enable the environment simulation option in Settings - General. (This feature is still in testing)
UFACTORY Studio V2.7.0 New Feature · UFACTORY · Settings - Assistive Features - Environment Simulation (Beta)
Kind: RecommendationThis project's simulation and agent design, not the physical cellProject design, not the physical cellsafety-595
Project advice
Deny the S6 agent the SDK calls that change collision sensitivity, collision detection, collision rebound, reduced mode or the safety boundary, or gate them behind human approval.
This is advice from this project, based on: safety-593 Inferredsafety-509 Verifiedsafety-558 Verified
Why:UFACTORY says a modified safety configuration makes a new system needing updated risk assessments, and its own SDK notes say not to use set_collision_sensitivity unless required. An agent that can change these settings could invalidate the risk assessment without anyone noticing.
An autonomous agent driving the S6 xArm 6 through the Python SDK could change collision sensitivity (to 0, which disables collision detection), collision rebound, reduced mode and the safety boundary. Under the xArm manual's own warning, changing the controller safety configuration makes the robot system a new system whose safety reviews, such as risk assessments, must be updated.
Why we infer this:Verified: the SDK exposes these calls and the glossary says sensitivity 0 disables detection; the manual says modifying the controller safety configuration creates a new system needing updated safety reviews. Inferred: an agent with SDK access could make such changes, and the manual's warning would then apply. Whether the Python SDK calls change the same 'configuration file' the manual refers to is not stated in any fetched source.
Evidence · 6 citations
:param value: sensitivity value, 0~5
xArm-Python-SDK API documentation (doc/api/xarm_api.md) · UFACTORY · def set_collision_sensitivity [SDK text for the xArm API; names no single model]
When it is set to 0, it means that collision detection is not enabled.
UFACTORY Studio User Manual (online), 2. Glossary · UFACTORY · Glossary, Collision Sensitivity [general Studio text; the Studio manual says it applies to the xArm6]
If parameters in the configuration file are modified, the entire robot system shall be deemed a new system, which necessitates the update of all safety review processes, such as risk assessments.
UFACTORY xArm Hardware Manual (online), 1. Safety · UFACTORY · 1.4 Personnel Safety, WARNING [series text: names no single model]
The xArm manual says the integrity of the device and system must be checked before each use, and that preliminary testing and inspection of both the arm and the peripheral protection system before production is essential.
Evidence · 2 citations
The integrity of the device and system must be checked before each use (e. g. the operational safety and the possible damage of the robotic arm and other device systems).
UFACTORY xArm Hardware Manual (online), 1. Safety · UFACTORY · 1.3, DANGER list [series text: names no single model]
This robot arm has 6 axes, with 5kg payload and 1m/s speed.
The difference between UFACTORY xArm5, UFACTORY xArm6 and UFACTORY xArm7 (Help Center article) · UFACTORY · Section 1 'Main difference in brief', xArm 6 entry
The online hardware manual and the product page give the xArm 6 arm's weight (arm only) as 12.5 kg; another UFACTORY source differs (see the contradiction).
Per-joint component data for the xArm 6 (motor model and rating, harmonic-drive ratio, encoder type and resolution, joint-module sizes) is not published in the xArm manual or the product page; the product page names only harmonic drives and servomotors and, unlike the 850's page, gives no encoder resolution.
Related: comp-504 Verified
Evidence · 2 citations
Industrial-grade harmonic drive and servomotors guarantee 24/7 working without stop.
UFACTORY xArm product page · UFACTORY · Overview, 'Durable Collaborative robots for your automation' (xArm product page, which covers the xArm 5, 6 and 7)
No dedicated teach pendant for the xArm 6 is documented in the xArm manual or the product page: they describe programming through the browser-based UFACTORY Studio, the SDKs and hand teaching.
Evidence · 2 citations
Web-based technology compatible with all major browsers.
UFACTORY xArm product page · UFACTORY · Overview, 'Graphical interface for beginner-friendly programming' (xArm product page, which covers the xArm 5, 6 and 7)
No Ethernet connection, camera port, force-torque sensor interface or user button at the xArm 6's tool end is described in the xArm manual or the product page; the product page lists the end-effector I/O as 2 DI, 2 DO, 2 AI and 1 RS-485.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Evidence · 2 citations
End Effector I/O 2*DI/2*DO/2*AI/1*RS485
UFACTORY xArm product page · UFACTORY · Tech Specs > Hardware, 'End Effector I/O' row (xArm product page, which covers the xArm 5, 6 and 7)
No specification for the BIO Gripper G2, the 6-axis force/torque sensor or the linear motor (payload, force range, resolution, stroke) was found in the xArm manual or the product page; only their names are listed.
Evidence · 2 citations
Gripper Vacuum Gripper BIO Gripper G2 6 Axis Force Torque Sensor Linear motor
UFACTORY xArm product page · UFACTORY · Overview, 'Seamless integration with official accessories' (xArm product page, which covers the xArm 5, 6 and 7)
Sources disagree on how the xArm AC control box powers the arm: the manual's controller chapter says its internal supply converts 100-240 V AC into 12 V and 48 V DC for the control box and the arm, while the common specification table gives the arm's input as 24 V DC, 20.8 A and the AC controller's output as 24 V DC, 20.8 A.
Evidence · 3 citations
its internal switching power supply converts 100V-240V AC into 12V, 48V DC, which supplies power to the load of the control box and the robotic arm.
UFACTORY xArm Hardware Manual (online), 3. Controller Electrical Interface · UFACTORY · 3.2.2 Power Supply (chapter text is not split by model)
What tool inputs TI2-TI4 and outputs TO2-TO4 are on the xArm 6 is not documented: UFACTORY Studio lists TI0-TI4 and TO0-TO4, but the xArm manual's tool connector defines only TI0, TI1, TO0 and TO1.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Evidence · 2 citations
Digital Input: TI0, TI1, TI2, TI3, TI4, low level by default
UFACTORY Studio User Manual (online), 7. Settings · UFACTORY · 7.2.1 End Effector IO
Whether the xArm 6 has an Ethernet connection at the end flange is not answered by the sources fetched: the xArm manual's Robotic Electrical Interface chapter has an 'End Flange' heading with no text, and its tool I/O pins carry no Ethernet.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Sources disagree on the xArm end-effector communication protocol: the online xArm manual's common specification table (and its Gripper table) say Modbus TCP, while the xArm Developer Manual's common specifications and gripper table say Modbus RTU, and the online manual's own Tool RS485 section configures standard Modbus RTU devices.
Evidence · 5 citations
End Effector Communication Protocol | Modbus TCP
UFACTORY xArm Hardware Manual (online), 8. Technical Specifications · UFACTORY · 8.1 xArm5/xArm6/xArm7 Common Specifications, 'End Effector Communication Protocol' row
The future 3D-printed flow in the IntelliMake diagram has no S2 step (printed parts go from S7 straight to S6), but the owner states S2 will handle material for 3D printing in the future. What S2 does in the future flow is unresolved.
Cycle times for S2's moves (S1 to S4, S1 to S3, S3 to S4) and for the S4/S5 laser step are not documented, so throughput and the benefit of two arms cannot be quantified.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
The number and positions of allocated S3 staging slots are not documented. The diagram's illustration shows six pads on the table, but it is a drawing, not a specification.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
The layout draws unlabelled return paths from the laser and S6 region back toward S1 and S2. Whether reworked parts re-enter through S1 or S2, and what S2 does in rework, is not documented.
IntelliMake's reason for using two arms, and for putting the 850 at S2 and the xArm 6 at S6, is not documented in any source available to this project (Q14d).
The project specification describes S6 as the downstream arm that handles parts after processing, but IntelliMake's future 3D-printed flow has S6 handling parts before laser engraving (S7 → S6 → S4/S5). S6's role is therefore not simply 'after processing' in the future flow.
S2's current, as-built automation level in the physical cell is not documented. Level 5E is this project's target (int-041), not a description of the cell today (Q14c).
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
As published, the xArm manual's 'Limitation of Liability' section says safety information 'must be construed as a warranty by UFACTORY' that the xArm will not cause injury or damage even if all safety instructions are complied with. That wording sits under a heading about limiting liability, and no fetched source says what UFACTORY intended. Do not read it as a guarantee of safety.
Evidence · 1 citation
Any safety information provided in this manual must be construed as a warranty by UFACTORY, that the xArm will not cause injury or damage even if all safety instructions are complied with.
UFACTORY xArm Hardware Manual (online), 1. Safety · UFACTORY · 1.2 Limitation of Liability [series text: names no single model]
UFACTORY sources disagree on the collision sensitivity range. Studio's Settings page says levels 1 to 5; Studio's glossary and the Python SDK say 0 to 5, and the glossary says 0 disables collision detection. A learner reading only the Settings page would not learn that the value can switch detection off.
Evidence · 3 citations
The collision sensitivity range is 1 to 5 levels.
UFACTORY Studio User Manual (online), 7. Settings · UFACTORY · 7.1.1, Collision Detection Sensitivity [general Studio text; the Studio manual says it applies to the xArm6]
The collision sensitivity range is from 0 to 5 level. When it is set to 0, it means that collision detection is not enabled.
UFACTORY Studio User Manual (online), 2. Glossary · UFACTORY · Glossary, Collision Sensitivity [general Studio text; the Studio manual says it applies to the xArm6]
The EMC standards the xArm manual lists do not match the EMC verification it links. Section 7.2 lists EMC 2004/108/EC, EN 61000-6-2:2005 and EN 61000-6-4:2007+A1:2011 as the standards the xArm 6 meets. The linked SGS EMC verification names EN IEC 61000-6-2:2019 and EN IEC 61000-6-4:2019 under Directive 2014/30/EU. Section 7.3 lists both the older editions and the 2019 editions without saying which apply.
Evidence · 7 citations
The product meets the relevant requirements of the EU CE directive:
UFACTORY xArm Hardware Manual (online), 7. Production Information · UFACTORY · 7.2 Applied Standards [names the xArm 6]
SGS Verification of Compliance No. GZEM2403001755MDVR (EMC; UFACTORY Robotic Arm, Model No. XI13, XI15), as linked from the xArm manual section 7.12 · SGS-CSTC Standards Technical Services Co., Ltd. (published by UFACTORY) · Standard(s) field
SGS verification document, published by UFACTORY · All rights reserved; quoted briefly as evidence · retrieved 2026-09-25
The xArm manual's Preface and Hardware Installation chapter say they apply to models XF1305, XI1305 and XS1305, and the linked RoHS certificate lists those numbers among others. The linked SGS machinery and EMC verifications name models XI13 and XI15. No fetched text says whether XI13 and XI15 cover the 1305 models, or which model number is on the S6 xArm 6's label.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Evidence · 6 citations
Apply to Model: XF1305, XI1305, XS1305 (1305 Model).
UFACTORY xArm Hardware Manual (online), 2. Hardware Installation · UFACTORY · 2. Hardware Installation, header [names model numbers, not a model name]
SGS Verification of MD Compliance No. MD GZES2403005468MD (UFACTORY Robotic Arm, Model No. XI13, XI15), as linked from the xArm manual section 7.12 · SGS-CSTC Standards Technical Services Co., Ltd. (published by UFACTORY) · Model No. field
SGS verification document, published by UFACTORY · All rights reserved; quoted briefly as evidence · retrieved 2026-09-25
SGS Verification of Compliance No. GZEM2403001755MDVR (EMC; UFACTORY Robotic Arm, Model No. XI13, XI15), as linked from the xArm manual section 7.12 · SGS-CSTC Standards Technical Services Co., Ltd. (published by UFACTORY) · Model No. field
SGS verification document, published by UFACTORY · All rights reserved; quoted briefly as evidence · retrieved 2026-09-25
DTI Certificate of Conformity for RoHS No. DTIBW20220028C (UFACTORY xArm), as linked from the xArm manual section 7.12 · Shenzhen Deesev Testing International Corporation (DTI) (published by UFACTORY) · Model No. field
DTI certificate, published by UFACTORY · All rights reserved; quoted briefly as evidence · retrieved 2026-09-25
DTI Certificate of Conformity for RoHS No. DTIBW20220028C (UFACTORY xArm), as linked from the xArm manual section 7.12 · Shenzhen Deesev Testing International Corporation (DTI) (published by UFACTORY) · Model No. field
DTI certificate, published by UFACTORY · All rights reserved; quoted briefly as evidence · retrieved 2026-09-25
The xArm manual says the arm will 'slightly brake and fall' when the emergency stop is pressed, but no fetched source says how far it may fall, at which joints, or how long the brakes take to engage.
Evidence · 1 citation
the posture of the robotic arm will slightly brake and fall.
No fetched UFACTORY source gives an explicit intended-use or reasonably foreseeable misuse statement for the xArm 6, beyond the environmental conditions and the general warnings in chapter 1.
The EU Declaration of Conformity for the xArm 6 was not found. The manual says the xArm 6 has passed EU CE certification, and both SGS verifications say the CE mark can be affixed or used, under the responsibility of the manufacturer, after completion of a Declaration of Conformity.
Evidence · 3 citations
has passed the EU CE certification
UFACTORY xArm Hardware Manual (online), 7. Production Information · UFACTORY · 7.2 Applied Standards [names the xArm 6]
The S6 xArm 6's controller type (AC or DC), serial number, firmware, Studio and SDK versions are not confirmed. The serial number matters because UFACTORY treats arms before XX1300 differently for friction parameters and the IMU mounting check, and firmware decides which SDK safety calls are available.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Sources disagree on the xArm 6's weight: 12.5 kg (arm only) in the online hardware manual and the product page's comparison table, but 12.2 kg (body only) in UFACTORY's support article comparing the xArm 5 Lite, 6 and 7. The product page's introduction also says '15kg weight' without naming a model.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
The difference between UFACTORY xArm5, xArm6 and xArm7 (support article) · UFACTORY · Section 1 Specifications, 'Weight(kg, body only)' row (columns xArm 5 Lite, xArm 6, xArm 7; value read from the xArm 6 column)
Crafted from Carbon fiber, 15kg weight makes it possible for easier deployment.
UFACTORY xArm product page · UFACTORY · Overview, 'Durable Collaborative robots for your automation' (xArm product page, which covers the xArm 5, 6 and 7)
Sources disagree on the range of the xArm 6's joint 2 (J2): the online hardware manual (specifications and preface) and the product page give -117° to 116°, but UFACTORY's support article comparing the xArm 5 Lite, 6 and 7 gives -118° to 120°, and the xarm6 URDF's default limits are -2.059 to 2.0944 rad (about -118° to 120°).
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Sources disagree on the range of the xArm 6's joint 3 (J3): the online hardware manual (specifications and preface) and the product page give -219° to 10°, but UFACTORY's support article comparing the xArm 5 Lite, 6 and 7 gives -225° to 11°, and the xarm6 URDF's default limits are -3.927 to 0.19198 rad (about -225° to 11°).
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
The xArm manual disagrees with itself on what the AC control box supplies: its specification table (and the product page) give the AC controller's output as 24 V DC, 20.8 A, but its 3.2.2 Power Supply text says the internal switching power supply converts 100–240 V AC into 12 V and 48 V DC, which powers the control box and the robotic arm.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Related: spec-539 Verifiedcomp-516 Verified
Evidence · 3 citations
Output 24V DC , 20.8A 24V DC 672Wmax
UFACTORY xArm Hardware Manual (online), 8. Technical Specifications · UFACTORY · AC Controller / DC Controller table, 'Output' row (section '8.1 xArm5/xArm6/xArm7 Common Specifications': applies to all three models)
its internal switching power supply converts 100V-240V AC into 12V, 48V DC, which supplies power to the load of the control box and the robotic arm.
UFACTORY xArm Hardware Manual (online), 3. Controller Electrical Interface · UFACTORY · 3.2.2 Power Supply (AC Controller) (manual for the xArm series; this passage names no single model)
No dimensioned base or tool-flange drawing values for the xArm 6 (bolt size and count, hole pattern, bolt torque, base height) were captured as text: the manual's 'Robot Base Mounting' section and the product page's 'Robot base mounting (mm)' and 'Robot tool head' drawings are images only.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Evidence · 2 citations
2.2.3.1 Robot Base Mounting
UFACTORY xArm Hardware Manual (online), 2. Hardware Installation · UFACTORY · 2.2.3.1 heading (followed only by figures) (chapter says 'Apply to Model: XF1305, XI1305, XS1305 (1305 Model)')
The xArm 6's working range (workspace envelope) is given only as figures: the manual's 'Define Working Space' section and the product page show drawings, and the product page says its working-range diagrams are only for safety assessment. No workspace dimensions beyond the Cartesian range and the 700 mm reach were captured as text.
The xArm manual gives two lower limits for the AC control box's mains input: 100 V in its specification table and power-supply section, but 110 V in its installation steps ('AC (110V-240V)').
Related: spec-551 Verified
Evidence · 3 citations
Input 100-240V AC 50/60 Hz 24-72V DC
UFACTORY xArm Hardware Manual (online), 8. Technical Specifications · UFACTORY · AC Controller / DC Controller table, 'Input' row (section '8.1 xArm5/xArm6/xArm7 Common Specifications': applies to all three models)
The control box is powered by 100V-240V AC (the input frequency is 47-63HZ)
UFACTORY xArm Hardware Manual (online), 3. Controller Electrical Interface · UFACTORY · 3.2.2 Power Supply (AC Controller) (manual for the xArm series; this passage names no single model)
Sources disagree on the xArm's end-effector communication protocol: the manual's common specification table says Modbus TCP, but the product page says Modbus RTU over RS-485, and the manual's own Tool RS485 section configures standard Modbus RTU end effectors. The manual's Gripper table likewise pairs RS-485 communication with a 'Modbus TCP' protocol.
Related: comp-551 Verified
Evidence · 4 citations
End Effector Communication Protocol Modbus TCP
UFACTORY xArm Hardware Manual (online), 8. Technical Specifications · UFACTORY · 'End Effector Communication Protocol' row (section '8.1 xArm5/xArm6/xArm7 Common Specifications': applies to all three models)
The xArm manual's list of applied standards does not include ISO/TS 15066; no statement of ISO/TS 15066 conformance for the xArm 6 was found in the manual or the product page.
Related: spec-566 Verified
Evidence · 1 citation
MD 2006/42/EC EMC 2004/108/EC EN ISO 10218-1:2011 EN 60204-1:2018 EN ISO 12100:2010 EN 61000-6-2:2005 EN 61000-6-4:2007+A1:2011
UFACTORY xArm Hardware Manual (online), 7. Production Information · UFACTORY · 7.2 Applied Standards, list (the full list)
No noise (sound pressure) figure for the xArm 6 arm was found in the manual or the product page; the only noise figure given is for the Vacuum Gripper accessory (under 60 dB at 30 cm).
Evidence · 1 citation
Noise Level(30cm away) <60dB
UFACTORY xArm Hardware Manual (online), 8. Technical Specifications · UFACTORY · Vacuum Gripper(AS1200) table (section '8.1 xArm5/xArm6/xArm7 Common Specifications': applies to all three models)
The product page lists the xArm's 'Base Connector Type' as M5*5 and does not say which connector this is; the manual's specification table does not list a base connector.
Evidence · 1 citation
Base Connector Type M5*5
UFACTORY xArm product page · UFACTORY · Tech Specs > Hardware, 'xArm Robot Specs' table (xArm product page, which covers the xArm 5, 6 and 7)
CODE_SESSION 01 — xArm 850 Interactive Learning Platform (project specification) · Derek Stringfellow (project owner) Derek Stringfellow, project record · Project-internal record · retrieved 2026-09-21 · cited by 1 record here · Project copy; not published on this site.
DTI Certificate of Conformity for RoHS No. DTIBW20220028C (UFACTORY xArm), as linked from the xArm manual section 7.12 · Shenzhen Deesev Testing International Corporation (DTI) (published by UFACTORY) (manufacturer) DTI certificate, published by UFACTORY · All rights reserved; quoted briefly as evidence · retrieved 2026-09-25 · cited by 1 record here · Open the source
Owner statements, 2026-09-21 (verbatim) · Derek Stringfellow (project owner) Derek Stringfellow, project record · Project-internal record · retrieved 2026-09-21 · cited by 3 records here · Project copy; not published on this site.
SGS Verification of Compliance No. GZEM2403001755MDVR (EMC; UFACTORY Robotic Arm, Model No. XI13, XI15), as linked from the xArm manual section 7.12 · SGS-CSTC Standards Technical Services Co., Ltd. (published by UFACTORY) (manufacturer) SGS verification document, published by UFACTORY · All rights reserved; quoted briefly as evidence · retrieved 2026-09-25 · cited by 3 records here · Open the source
SGS Verification of MD Compliance No. MD GZES2403005468MD (UFACTORY Robotic Arm, Model No. XI13, XI15), as linked from the xArm manual section 7.12 · SGS-CSTC Standards Technical Services Co., Ltd. (published by UFACTORY) (manufacturer) SGS verification document, published by UFACTORY · All rights reserved; quoted briefly as evidence · retrieved 2026-09-25 · cited by 2 records here · Open the source