Operate: virtual training and commissioning of a simulated arm
Twin: a twin-ready view of the arm and its cell
§2 xArm 6
Role in the Phase 1 production process
S6 as part of a production system: what comes before and after it, what goes in and comes out, and why there are two arms.
Start here
This section places the second arm in the factory: what reaches it, where its parts go next, how it shares the work with the first arm, and how it fits a factory built to run itself. The cell as IntelliMake draws it comes first. What this project advises for the arm's agent follows, under its own label.
S4, the conveyor that carries workpieces through the laser area1
S5, the laser engraver, which personalises the part. The layout draws an arrow from S5 into S623
S6, an xArm 6: handles parts after processing and routes them to inspection, rework or shipping4
S8, the outbound conveyor, which moves completed products toward packing and shipment5
S10, Packing / Labeling, the last station in the layout6
IntelliMake's Phase 1 factory is designed to demonstrate autonomous production of high-mix, low-volume personalised products7.
The gift flow has two Cobot Handling steps. S2 takes the first, before staging; S6 takes the second, straight after Laser Engraving89.
S2, the xArm 850, is the upstream arm that takes incoming material toward personalisation. S6 is the downstream arm10.
The planned outcome for the cell is a working autonomous production run: accepting orders, personalising the parts, then sending them for shipping, all done by the agents interacting with each other11.
An agent, here, is software that runs a station: it reads what is happening around it and decides what to do next, within limits people set. The Novice level of this section explains how much it may decide.
S6 in one line: S6 is the xArm 6 arm that handles parts after processing, routing them to inspection, rework or shipping4.
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
What does S6 do, and where?
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 follow one gift past the laser to the second arm. You find what comes before the arm, what comes after it, what it does, and why the cell has a second arm at all. You also learn how to behave near it.
What the factory is for
IntelliMake's Phase 1 factory is designed to demonstrate autonomous production of personalised products: many different items, each made in small numbers7. Its first products are laser-engraved gifts. Later it is to make 3D-printed custom parts that are then laser marked or engraved12.
The stations around S6
S4 is the conveyor that carries workpieces through the laser area1
A gift passes through nine steps: Customer Order → Receiving → Cobot Handling → Staging → Laser Engraving → Cobot Handling → Quality Decision → Shipping / Rework → Packing & Labeling8.
Look for "Cobot Handling". It comes twice. The first is S2, the other arm, between Receiving and Staging. The second, right after Laser Engraving, is S69. Straight after S6's step comes the Quality Decision89.
What S6 does
S6 handles parts after processing and routes each one to inspection, rework or shipping4. It does not engrave; S5 does that2. It does not take in new material either; that is S2's job1310.
UFACTORY says the xArm 6 is designed for manufacturing and assembly-line automation, including load and unload and pick and place. This platform reads S6's job as a task of that kind14.
Two arms, two jobs
S2, the xArm 850, is the upstream arm. It takes incoming material off receiving toward personalisation10.
S6, the xArm 6, is the downstream arm. It handles parts after processing10.
This platform infers one benefit: with two arms, loading new material and unloading finished parts can happen at the same time. With one arm, both handling steps for every part would run one after the other15.
What watches the cell, and how to behave
Watching a hazard is not the same as stopping it. Do not rely on a safeguard nobody has confirmed.
Camera C2 watches the area where the robot and the laser work16.
S11, IntelliAware, uses AI vision to monitor the factory's operations, equipment, processes and safety17.
Stay out of the xArm 6's working area while it runs. The xArm manual says no people should be in the working area when the arm is in operation18.
An arm that seems to have stopped may be waiting for a signal and about to act. Treat it as moving19.
Check yourself
Answer, then check. Each option has its own feedback, and nothing is scored.
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 run both production flows and find the second arm in each, trace where a finished part goes after the arm, and meet IntelliMake's scale for how much a machine decides. It is for someone who will work near or with the cell.
S6 is the step between the laser and the Quality Decision. What comes out of S6 is a part on its way to inspection, rework or shipping84.
The future flow: printed parts
IntelliMake plans a second flow: Customer Order → Custom 3D Design → S7 3D Printing → S6 Robot Handling → S4/S5 Laser Engraving or Marking → Inspection → S8 Shipping → Packing. It joins a custom shape to surface personalisation23.
S7 is a Prusa 3D printer, a future extension of the factory24.
In that flow S6 takes parts from the printer and passes them to the laser. So S6 serves both flows25.
Where a finished part goes
S8, the outbound conveyor, moves completed products toward packing and shipment5.
This platform infers that S8 is probably where S6 places parts it routes to shipping26.
The last station in the layout is S10, Packing / Labeling, which prepares, labels and packs the product6.
This platform infers that the cameras feed S11's monitoring27. S11 monitors operations, equipment, processes and safety17.
This project's simulation and agent design, not the physical cell
Monitoring is not a safeguard
This project's advice to learners: do not treat S11 or the cameras as a safeguard, and do not rely on them to stop motion or to protect people28.
Stay out while it runs
Stay out of the xArm 6's working area while it runs. The xArm manual says no people or other equipment should be in the working area when the arm is in operation18.
Do not rely on a safeguard nobody has confirmed.
How much does the machine decide? IntelliMake's levels
The factory is built to demonstrate autonomous production7. IntelliMake grades how much a machine decides on six levels:
L2, Programmable: the programmer decides, through PLC recipes and programs31.
L3, Flexible: the automation system picks one of its predefined modes32.
L4, Intelligent/Adaptive: an algorithm adjusts what happens33.
L5, Agentic/Autonomous: an AI agent executes toward an objective34.
Inside level five
5A, Observe: collects data such as speed, product location, queue length and upstream and downstream status35.
5B, Understand & Determine: forms a view of the operating situation from that data36.
5C, Recommend: proposes an action; the human still decides37.
5D, Act with Human Approval: acts only after a specific authorisation38.
5E, Limited Autonomous Control: makes certain decisions alone within safety and process limits, with a person supervising and handling exceptions39.
5F, Full Autonomy: receives objectives rather than instructions, then decides, acts, learns and replans40.
IntelliMake frames the shift this way: traditional automation tells a machine what to do and how. Agentic automation gives it a goal, awareness of its situation, reasoning, tools and the authority to decide what should be done41.
This project's simulation and agent design, not the physical cell
Where the arms are heading
Both arms, the xArm 850 at S2 and the xArm 6 at S6, are planned to be run by software agents that work with the other stations42.
Check yourself
Answer, then check. Each option has its own feedback, and nothing is scored.
3Intermediate
Hand-offs and shared information
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 read IntelliMake's drawing around the second arm closely, follow the arm through both of the factory's flows, and see how the stations are expected to share what they know. It is for someone who will set up, program or maintain the cell.
What the drawing shows around S6
The layout draws S6 directly after S5, the laser, with a flow arrow from S5 into S6. The laser station is S6's immediate upstream neighbour3.
S8, the outbound conveyor, is one of the stations after S6. It moves completed products toward final packing and shipment5.
This platform infers that S8 is probably where S6 places parts it routes to shipping26.
One arm, two flows
In the gift flow, S6 is the downstream arm: it handles parts after processing10.
In the future printed-parts flow, S6 takes parts coming from S7, the 3D printer, and passes them to laser engraving or marking2325.
So S6 serves both production flows: in one it works after the laser, in the other before it1025.
How the stations share information
IntelliMake's current working assumption is that the agents do not talk to each other directly. They exchange information, and may collaborate, through a central shared knowledge space, a hub43.
At IntelliMake's sub-level 5A, Observe, a machine gathers data from various sources: speed, current, vibration, product location, queue length, schedules and upstream and downstream status35.
This platform infers that the factory's cameras feed S11, IntelliMake's monitoring layer27.
This project's simulation and agent design, not the physical cell
Monitoring is not a safeguard
This project's advice to learners: do not treat S11 or the cameras as a safeguard28.
Advice for an agent that drives S6
This project's 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 approval44.
Check yourself
Answer, then check. Each option has its own feedback, and nothing is scored.
4Expert
Why two arms, and what S6's agent must not do
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 test the case for two arms against the records, keeping track of how firm each link in it is, and you reason about what an agent driving the second arm would need to decide and what it must not be allowed to change. It is for someone who designs, integrates or changes the cell.
The case for two arms, and how firm each link is
Two handling steps. The gift flow has one Cobot Handling step before staging and the laser, and one after. The first is S2's; the second is S6's89.
Overlap. This platform infers that with two arms, loading at S2 and unloading and routing at S6 can run at the same time, where one arm would do both in turn. It also infers that the laser step may be the real bottleneck15.
Reach. This platform assumes S2 and S6 sit on opposite sides of the laser stations, so one arm probably could not reach both the receiving and staging area and the post-processing area47.
The arms themselves. UFACTORY publishes 850 mm reach for the 850, against 700 mm for its xArm 5/6/7 line, with payloads from 3 kg to 5 kg across that line48.
One arm in two flows
In the gift flow, S6's handling step comes after laser engraving9.
In the future printed flow, S6 takes parts from S7 and passes them to laser engraving or marking, so it serves both flows25.
So S6 receives parts from the laser in one flow and from the printer in the other925.
What makes a station agentic
IntelliMake separates three questions: does the machine know what should be done, is it allowed to do it, and can it keep operating and adapting without repeated human help? It holds that true autonomous manufacturing needs the right combination of all three49.
This platform infers that a policy fixed rules alone could carry out sits at IntelliMake levels 1 to 3, not level 550.
At 5E, limited autonomous control, a machine makes certain decisions independently within established safety and process limits, then monitors the outcome, with a person supervising and handling exceptions39.
IntelliMake's current working assumption is that the agents exchange information through a central shared hub rather than talking to each other directly43.
This project's simulation and agent design, not the physical cell
Guardrails for S6's agent
This project's 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 approval44.
This project's advice: do not use UFACTORY Studio's simulated-arm mode as the simulation substrate for S6 agent work. It needs a real arm connected, its settings apply to the real arm, and its unlock-joint button unlocks the real joints51.
Why those calls matter
This platform infers that an agent driving the S6 arm through the Python SDK could change collision sensitivity, collision rebound, reduced mode and the safety boundary. Setting sensitivity to 0 disables collision detection52.
Under the xArm manual's own warning, changing the controller's safety configuration makes the robot system a new system, whose safety reviews, such as risk assessments, must be updated52.
The xArm manual says a complete safety assessment must be recorded each time the arm is re-installed and debugged53.
Check yourself
Answer, then check. Each option has its own feedback, and nothing is scored.
Not settled
Open questions · 36
What the sources do not settle for this section. Nothing here is papered over with a plausible number.
Kind: Contradiction
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.
The IP address of the xArm 6 control box at S6, and how the S6 network is laid out (direct PC link, router or switch), are not in the sources; the manuals give only the default range 192.168.1.xxx and the reset address 192.168.1.111.
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.
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.
What S2 publishes to the other agents or the hub is not defined: placement confirmations, S3 slot updates, faults and error codes, its own ready or busy state, and whether any work-order or traceability data passes through S2 (Q9, Q14).
Whether S11 IntelliAware has any authority to stop or slow S2, whether it is a safety-rated protective device, and who owns S11 are not documented (Q14f). The diagram calls S11 'monitoring of ... safety', which does not make it a safeguard.
IntelliMake's flow and layout route incoming material through staging (Receiving → Cobot Handling → Staging → Laser Engraving; S2 → S3 → S4), but this project's S2 design places directly on S4 and uses S3 only when S4 is busy. Whether the physical cell also skips staging, or IntelliMake's diagram is out of date for S2, is unresolved (Q14b).
Whether business cards are the physical Phase 1 cell's workpiece, or only the workpiece in this project's simulation, is not recorded. IntelliMake's diagram speaks of 'blanks' and 'personalized laser-engraved gifts' (Q14a).
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).
Where S6 puts a part for each of its three routes (inspection, rework, shipping) is not documented. The layout has no labelled inspection station (the topic mapping's S9 does not appear; int-037), the rework return path is unlabelled (int-039), and no source names S6's drop-off point for shipping.
Where S6 picks parts up after the laser step is not documented: from S5's bed, from the end of the S4 conveyor, or from a transfer table. The layout's S6 illustration shows the arm beside a small table holding a part, but it is a drawing, not a specification.
IntelliMake's layout draws the station row with an arrow from S6 into S7 (the 3D printer), but the future 3D-printed flow banner puts S7 before S6 (S7 3D Printing → S6 Robot Handling), and the initial gift flow has no printing step at all. The arrow's direction is drawn, not worded; the banner's wording is the only textual statement of the order between S6 and S7.
Camera C2 monitors 'the robot–laser work area', but the layout does not say which robot: S2, S6 or both. Whether any camera covers S6's work area is not documented.
Who or what makes the Quality Decision that follows S6's handling step, and how S6 learns the result (inspection, rework or shipping), is not documented. The topic mapping mentions camera-based inspection and an S9 QC decision pathway, but no S9 station appears in the layout.
What S6 consumes from the other stations or the shared hub (for example, that a part is ready after the laser step) and what it publishes are not defined in any source. The physical I/O between stations is undefined for S2 as well (int-022).
Cycle times for S6's handling (picking a part after the laser step and routing it to inspection, rework or shipping) are not documented, so S6's share of the cell's throughput cannot be quantified.
The end effector fitted to S6 is not documented. The 2026-09-24 site-photo record notes a tool at the 850's flange and says nothing about the second arm's flange.
The S6 arm's serial number, firmware version and controller type (AC or DC control box) are not recorded. The site-photo record lists these as still open for the next visit.
S6's physical layout is not documented: where the xArm 6 is mounted relative to S5 and S8, what it can reach, and what separates it from people. The arms are not yet in their final layout.
No IntelliMake automation-level target has been recorded for S6. The level 5 'limited autonomous control' target (int-041) was stated for S2's agent; whether S6's agent shares it is not recorded.
No risk assessment for the S6 xArm 6 application has been confirmed: whether one exists for the complete application (arm, gripper, workpieces and the stations it hands parts to and from), who performed and signed it, and whether it was redone after installation as the xArm manual requires.
The S6 emergency stops are not confirmed: whether any emergency stop buttons beyond the Control Box button are wired to EI, where they are, and whether S6 shares an emergency stop circuit with S2 or other stations.
The final position of the S6 Control Box is not confirmed: whether it is outside the arm's working range, at 0.6 to 1.5 m height, with its emergency stop reachable.
S6's guarding and protective devices are not confirmed: whether fences, interlocked doors, light curtains, safety mats or laser scanners are wired to the SI protective stop input, whether any safety signal passes through a PLC (and if so whether it is a safety PLC), or whether SI is still in its default state with no additional safety equipment.
The S6 xArm 6's safety-related settings are not confirmed: collision detection on or off, collision sensitivity level, collision rebound, self-collision detection and tool model, safety boundary and its limits, reduced mode and its limits, TCP payload, mounting direction, which CI inputs are configured as Stop Moving, Safeguard Reset, Reduced Mode or Manual Mode, and whether the documented default Advanced Settings password has been changed.
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.
It is not confirmed whether people will enter the S6 xArm 6's working area during automatic operation, whether S6's working range (including the gripper) is marked, whether S6 operators are trained as the manual requires, or what the S6 gripper does to a held part on power loss or emergency stop.
S4, the Laser Engraver Conveyor, transfers workpieces through the laser processing area.
Evidence · 1 citation
Transfers workplaces through the laser processing area.
IntelliMake Phase 1 Factory: Autonomous Production Demonstrator (infographic) · IntelliMake.org · S4 station description (the diagram prints 'workplaces'; read as workpieces)
In IntelliMake's Phase 1 layout, S6 (the UFactory xArm 6 cobot) is drawn directly after S5, the xTool F1 Ultra laser engraver, with a flow arrow from S5 into S6. S5 performs personalization through laser engraving or marking, so in the drawing the laser station is S6's immediate upstream neighbour.
Evidence · 2 citations
S5 xTool F1 Ultra Laser Engraver Performs personalization through laser engraving or marking.
IntelliMake Phase 1 Factory: Autonomous Production Demonstrator (infographic) · IntelliMake.org · S5 station label and description
S8, the Outbound Conveyor, moves completed products toward final packing and shipment. It is one of the stations after S6 in IntelliMake's layout; the diagram labels it both 'QC Hold' and 'Shipping' (see int-038).
Evidence · 2 citations
S8 Outbound Conveyor / QC Hold Moves completed products toward final packing and shipment.
IntelliMake Phase 1 Factory: Autonomous Production Demonstrator (infographic) · IntelliMake.org · Upper S8 panel, label and description
S10, Packing / Labeling, carries out final product preparation, identification, labeling and packing. It is the last station in IntelliMake's layout, and 'Packing & Labeling' is the last step of the initial gift production flow.
Evidence · 2 citations
S10 Packing / Labeling Final product preparation, identification, labeling, and packing.
IntelliMake Phase 1 Factory: Autonomous Production Demonstrator (infographic) · IntelliMake.org · S10 label and description
IntelliMake Phase 1 Factory: Autonomous Production Demonstrator (infographic) · IntelliMake.org · Initial Personalized Gift Production Flow banner, last steps
The project specification places S2 at the first Cobot Handling step of IntelliMake's gift flow, between Receiving and Staging; the second Cobot Handling step, after laser engraving, is S6's. IntelliMake's layout draws the stations in the matching order (see observation).
Evidence · 3 citations
Where it sits in the Initial Personalized Gift Production Flow (Receiving → **Cobot Handling** → Staging → Laser Engraving → …)
The cell uses two collaborative arms: the xArm 850 at S2 is the upstream arm that takes incoming material off receiving toward personalization, and the xArm 6 at S6 is the downstream arm that handles parts after processing.
Evidence · 2 citations
The xArm 850 at S2 is the **upstream** arm: it takes incoming material off receiving and hands it off toward personalization
The planned outcome for the IntelliMake cell is a working autonomous production run: accepting orders, personalising the parts, then sending them for shipping, all done by the agents interacting with each other.
Evidence · 2 citations
The goal is a working autonomous production run of the system accepting orders and printing then sending over for shipping, all done by the agents interacting with each other.
The factory's initial production scenario is personalized laser-engraved gifts; it is to expand in the future to additively manufactured (3D-printed) custom parts that are laser marked or engraved.
Evidence · 1 citation
Initial production scenario focuses on personalized laser-engraved gifts, expanding in the future to additively manufactured custom parts (laser marked/engraved).
UFACTORY describes the xArm 6 as designed for manufacturing and assembly-line automation, including more complex actions such as load and unload, and pick and place. S6's IntelliMake role, handling parts after processing and routing them onward, is a task of that kind.
Why we infer this:UFACTORY's article names load and unload and pick and place among the xArm 6's intended tasks; IntelliMake's S6 description (handling and routing parts) is a pick-and-place task. The match is this project's reading; neither source refers to the other.
Evidence · 2 citations
The 6 axis robot arm is designed for manufacturing and assembly line automation, including more complex actions, for example, load and unload, pick and place
The difference between UFACTORY xArm5, UFACTORY xArm6 and UFACTORY xArm7 (Help Center article) · UFACTORY · Section 1, 'Main difference in brief', xArm 6 entry
With two arms, loading incoming material (S2) and unloading and routing finished parts (S6) can happen at the same time. With one arm, both handling steps for every part would run one after the other on the same arm. How much this helps throughput is unknown, because no cycle times are documented (int-033), and the laser step may be the real bottleneck.
Why we infer this:Verified: the gift flow has two separate Cobot Handling steps, one before staging and laser engraving and one after (int-028), assigned to S2 and S6 (int-029). One arm would have to perform both in series; two arms let them overlap. This shows the steps can overlap, not that one arm would be the bottleneck: that depends on cycle times, which are undocumented (int-033).
The xArm manual says that while the device is running, an arm that seems to have stopped may be waiting for a signal and about to act, and that it should be considered to be in action even in that state.
Evidence · 1 citation
Quote not shown (over 40 words). See the source at: 1.4 Personnel Safety, CAUTION [series text: names no single model].
UFACTORY xArm Hardware Manual (online), 1. Safety · UFACTORY · 1.4 Personnel Safety, CAUTION [series text: names no single model]
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.
S3, the Inbound Staging Table, provides temporary storage and buffering for incoming workpieces.
Evidence · 1 citation
Provides temporary storage/buffering for incoming workplaces.
IntelliMake Phase 1 Factory: Autonomous Production Demonstrator (infographic) · IntelliMake.org · S3 station description (the diagram prints 'workplaces'; read as workpieces)
S7, a Prusa 3D printer, is a future production extension that produces customized 3D-printed parts and supports a future hybrid additive-plus-laser workflow.
In IntelliMake's future 3D-printed flow, S6 handles parts coming from S7 (3D printing) and passes them to laser engraving or marking, so S6 serves both production flows.
Evidence · 1 citation
S7 3D Printing → S6 Robot Handling → S4/55 Laser Engraving or Marking
S8 is probably where S6 places parts it routes to shipping: S6 routes parts to inspection, rework or shipping, and S8 is the station that moves completed products toward packing and shipment. No source says S6 places parts on S8, or where S6 puts parts bound for inspection or rework.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Why we infer this:S6's description names shipping as one of its three routes, and S8 is the only station whose description mentions shipment. The layout draws S8 after S6. Neither description names the other station, so the handoff is inferred, not stated.
Evidence · 2 citations
Handles parts after proces. routing them to inspection, rework, or shipping.
IntelliMake Phase 1 Factory: Autonomous Production Demonstrator (infographic) · IntelliMake.org · S6 station description
The factory cameras, including C1, feed the S11 IntelliAware monitoring layer.
Why we infer this:The mapping table groups cameras C1–C3 with S11 under AI vision for safety, and the layout draws dotted connectors from the camera icons to S11. The data path itself (protocol, what is sent) is not documented.
Evidence · 1 citation
AI Vision – Safety | Cameras C1–C3 + S11 IntelliAware
IntelliMake Phase 1 Factory: Autonomous Production Demonstrator (infographic) · IntelliMake.org · HW2 SME topic mapping table
Kind: RecommendationThis project's simulation and agent design, not the physical cellProject design, not the physical cellint-053
Project advice
Until S11's safety function is documented and verified, neither learners nor the S2 agent should treat S11 or the cameras as a safeguard. The S2 agent must not rely on them to stop motion or to protect people.
This is advice from this project, based on: int-024 Verifiedint-050 Gap, awaiting cell access
Why:S11 is described only as monitoring that includes safety (int-024). Nothing establishes a safety rating, stop authority or response time (int-050). Treating an unrated monitoring system as a safeguard is the failure the Q3 disposition warns against: an Assumed safeguard mistaken for a confirmed one.
IntelliMake automation level 3 is 'Flexible': the conveyor action is 'Selects predefined modes', and the primary decision maker is the automation system.
IntelliMake automation level 4 is 'Intelligent/Adaptive': the conveyor action is 'Algorithm-driven adjustments', and the primary decision maker is the algorithm.
IntelliMake automation level 5 is 'Agentic/Autonomous': the conveyor action is 'Objective-driven execution', and the primary decision maker is the AI agent.
Evidence · 1 citation
Level 5 | Agentic/Autonomous | Objective-driven execution | AI Agent
The Progression Cheat Sheet: 6 stages of manufacturing automation · IntelliMake.org · Level 5 row
IntelliMake sub-level 5B, 'Understand & Determine': it interprets information, forming an interpretation of the operating situation from observed data.
Evidence · 1 citation
Forms an interpretation of the operating situation based on observed data.
Level 5. Agentic Evolution: A Spectrum of Increasing Decision Authority (infographic) · IntelliMake.org · Panel #5B
IntelliMake sub-level 5C, 'Recommend': it advises the human operator, determining an appropriate action and recommending it while the human keeps decision authority (human in the loop).
Evidence · 1 citation
Determine an appropriate action and recommend it, but human retains decision authority.
Level 5. Agentic Evolution: A Spectrum of Increasing Decision Authority (infographic) · IntelliMake.org · Panel #5C
IntelliMake sub-level 5D, 'Act with Human Approval': it authorizes machine action: the machine can act, but only after specific authorization, and the human keeps final authority.
Evidence · 1 citation
The machine can act, but only after specific authorization.
Level 5. Agentic Evolution: A Spectrum of Increasing Decision Authority (infographic) · IntelliMake.org · Panel #5D
IntelliMake sub-level 5E, 'Limited Autonomous Control': it operates within guardrails, with permission to make certain decisions independently within established safety and process limits and then monitor the outcome (human on the loop: supervision and exception handling).
Evidence · 1 citation
Permission to make certain decisions independently within established safety and process limits.
Level 5. Agentic Evolution: A Spectrum of Increasing Decision Authority (infographic) · IntelliMake.org · Panel #5E
IntelliMake sub-level 5F, 'Full Autonomy': it achieves objectives: given objectives rather than instructions, it perceives, understands, decides, acts, observes the result, learns and adapts, and replans.
Evidence · 1 citation
Given objectives, not instructions.
Level 5. Agentic Evolution: A Spectrum of Increasing Decision Authority (infographic) · IntelliMake.org · Panel #5F
IntelliMake frames the shift to agentic automation as follows: traditional automation tells the machine what to do and how, while agentic automation gives it a goal, situational awareness, reasoning capability, tools and the authority to determine what should be done.
Evidence · 1 citation
Agentic automation gives the machine a goal, situational awareness, reasoning capability, tools, and authority to determine what should be done.
Level 5. Agentic Evolution: A Spectrum of Increasing Decision Authority (infographic) · IntelliMake.org · Panel 'The fundamental shift'
The current assumption for the IntelliMake agents is that they do not talk to each other directly: they exchange information, and may collaborate, through a central shared knowledge space (a hub). IntelliMake leadership has not finalised this.
How this would be checked:IntelliMake team leadership's design for the shared knowledge space: its protocol, schema and hosting (open question Q9).
Evidence · 1 citation
The agents will not talk directly to each other, rather will exchange information in a central hub and possibly colloborate in that space. That has not been fully fleshed out by the iIntelliMake team leadership.
Derek Stringfellow, project record · Project-internal record · retrieved 2026-09-21
Project copy; not published on this site.
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.
The xArm manual says the Control Box must be placed outside the arm's working range so that the emergency stop button can be pressed in an emergency.
Evidence · 1 citation
The Control Box must be placed outside the working range of the robotic arm to ensure the emergency stop button can be pressed once an emergency occurs.
UFACTORY xArm Hardware Manual (online), 1. Safety · UFACTORY · 1.3, CAUTION list [series text: names no single model]
The xArm manual says the controller should be placed at a height of 0.6 m to 1.5 m.
Evidence · 1 citation
The controller should be placed at a height of 0.6m to 1.5m.
UFACTORY xArm Hardware Manual (online), 7. Production Information · UFACTORY · 7.6 Controller Placement Height (manual for the xArm series; this passage names no single model)
The S2 and S6 stations sit on opposite sides of the laser processing stations (S4/S5), so a single arm probably could not reach both the receiving and staging area and the post-processing area.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
How this would be checked:Measure the as-built positions of S1, S3, S4 and S6 relative to each arm's base and compare them with the published reach of each arm.
Evidence · 2 citations
S2 UFactory xArm 850 Cobot
IntelliMake Phase 1 Factory: Autonomous Production Demonstrator (infographic) · IntelliMake.org · S2 station label
UFACTORY publishes a longer reach for the 850 (850 mm, maximum payload 5 kg) than for its xArm 5/6/7 line (700 mm, with payloads from 3 kg to 5 kg across the line). No xArm 6-specific figure is cited here, and no source says whether reach decided which arm went to S2.
IntelliMake distinguishes intelligence (does the machine know what should be done?), authority (is the machine allowed to do it?) and autonomy (can it keep operating and adapting without repeated human intervention?), and holds that true autonomous manufacturing needs the right combination of all three.
Evidence · 1 citation
True autonomous manufacturing requires the appropriate combination of all three.
Level 5. Agentic Evolution: A Spectrum of Increasing Decision Authority (infographic) · IntelliMake.org · Panel 'Understanding the differences'
A placement policy that fixed rules alone could carry out would sit at IntelliMake levels 1–3, not level 5. S2's level 5E claim therefore depends on decisions the rules do not cover, made within guardrails.
Why we infer this:Level 1 is hard-coded logic and level 3 selects among predefined modes (lvl-002, lvl-004). If S2's behaviour were fully specified by the rules in int-014 to int-016, it would be level 3 at most. Level 5E requires the machine to make decisions within guardrails (lvl-011), so the 5E claim must rest on decisions beyond the base rules, such as anticipation, sequencing, and handling missing or conflicting signals.
Kind: RecommendationThis project's simulation and agent design, not the physical cellProject design, not the physical cellsafety-598
Project advice
Do not use UFACTORY Studio's simulated-arm mode as the simulation substrate for S6 agent work: it needs a real arm connected, its settings apply to the real arm, and its unlock-joint button unlocks the real joints.
This is advice from this project, based on: safety-528 Verified
Why:Studio's own text says both modes need a real arm and that simulation-mode settings and joint unlocking act on it, so it does not isolate an agent from the machine.
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 a complete safety assessment must be recorded each time the arm is re-installed and debugged, and that a safety assessment is required each time it is installed.
Evidence · 2 citations
A complete safety assessment must be recorded each time the robotic arm is re-installed and debugged.
UFACTORY xArm Hardware Manual (online), 1. Safety · UFACTORY · 1.3, DANGER list [series text: names no single model]
The xArm arm consists of a base and rotary joints, each joint a degree of freedom, numbered from the bottom as Joint 1, Joint 2 and so on; the last joint is the tool side, where end effectors such as a gripper connect. The xArm 6 has six such joints.
Evidence · 3 citations
The xArm robotic arm system consists of a base and rotary joints, and each joint represents a degree of freedom. From the bottom to the top, in order, Joint 1, Joint 2, Joint 3, etc.
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 xArm manual makes the integrators of the xArm responsible for complying with the country's safety laws and regulations, including making a risk assessment for the complete system and making sure there is a safe distance between people and the xArm when they interact with it.
Evidence · 2 citations
The integrators of xArm are responsible for the compliance of applicable safety laws and regulations in the country, to prevent any hazards in the operating environment. This includes, but is not limited to:
UFACTORY xArm Hardware Manual (online), 1. Safety · UFACTORY · 1.1 Validity and Responsibility [series text: 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.
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.
The IP address of the xArm 6 control box at S6, and how the S6 network is laid out (direct PC link, router or switch), are not in the sources; the manuals give only the default range 192.168.1.xxx and the reset address 192.168.1.111.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Evidence · 2 citations
The default IP of robotic arm is 192.168.1.xxx
UFACTORY Studio User Manual (online), 3. Connection · UFACTORY · 3.2 Software Connection
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.
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.
What S2 publishes to the other agents or the hub is not defined: placement confirmations, S3 slot updates, faults and error codes, its own ready or busy state, and whether any work-order or traceability data passes through S2 (Q9, Q14).
Whether S11 IntelliAware has any authority to stop or slow S2, whether it is a safety-rated protective device, and who owns S11 are not documented (Q14f). The diagram calls S11 'monitoring of ... safety', which does not make it a safeguard.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
IntelliMake's flow and layout route incoming material through staging (Receiving → Cobot Handling → Staging → Laser Engraving; S2 → S3 → S4), but this project's S2 design places directly on S4 and uses S3 only when S4 is busy. Whether the physical cell also skips staging, or IntelliMake's diagram is out of date for S2, is unresolved (Q14b).
Whether business cards are the physical Phase 1 cell's workpiece, or only the workpiece in this project's simulation, is not recorded. IntelliMake's diagram speaks of 'blanks' and 'personalized laser-engraved gifts' (Q14a).
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Related: int-013 Verified
Evidence · 1 citation
Receives incoming blanks or materials, moves them into production.
IntelliMake Phase 1 Factory: Autonomous Production Demonstrator (infographic) · IntelliMake.org · S1 station description
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.
Where S6 puts a part for each of its three routes (inspection, rework, shipping) is not documented. The layout has no labelled inspection station (the topic mapping's S9 does not appear; int-037), the rework return path is unlabelled (int-039), and no source names S6's drop-off point for shipping.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Where S6 picks parts up after the laser step is not documented: from S5's bed, from the end of the S4 conveyor, or from a transfer table. The layout's S6 illustration shows the arm beside a small table holding a part, 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.
Transfers workplaces through the laser processing area.
IntelliMake Phase 1 Factory: Autonomous Production Demonstrator (infographic) · IntelliMake.org · S4 station description (the diagram prints 'workplaces'; read as workpieces)
IntelliMake's layout draws the station row with an arrow from S6 into S7 (the 3D printer), but the future 3D-printed flow banner puts S7 before S6 (S7 3D Printing → S6 Robot Handling), and the initial gift flow has no printing step at all. The arrow's direction is drawn, not worded; the banner's wording is the only textual statement of the order between S6 and S7.
Camera C2 monitors 'the robot–laser work area', but the layout does not say which robot: S2, S6 or both. Whether any camera covers S6's work area is not documented.
Who or what makes the Quality Decision that follows S6's handling step, and how S6 learns the result (inspection, rework or shipping), is not documented. The topic mapping mentions camera-based inspection and an S9 QC decision pathway, but no S9 station appears in the layout.
What S6 consumes from the other stations or the shared hub (for example, that a part is ready after the laser step) and what it publishes are not defined in any source. The physical I/O between stations is undefined for S2 as well (int-022).
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Cycle times for S6's handling (picking a part after the laser step and routing it to inspection, rework or shipping) are not documented, so S6's share of the cell's throughput cannot be quantified.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
The end effector fitted to S6 is not documented. The 2026-09-24 site-photo record notes a tool at the 850's flange and says nothing about the second arm's flange.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
The S6 arm's serial number, firmware version and controller type (AC or DC control box) are not recorded. The site-photo record lists these as still open for the next visit.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Related: int-513 Assumed, awaiting cell access
Evidence · 1 citation
AC or DC controller (cell question 8); serial numbers and firmware
Site photos, 2026-09-24: what they show, and what they do not (OBSERVATIONS.md) · Derek Stringfellow · 'Not settled' list
Derek Stringfellow, project record · Project-internal record · retrieved 2026-09-25
S6's physical layout is not documented: where the xArm 6 is mounted relative to S5 and S8, what it can reach, and what separates it from people. The arms are not yet in their final layout.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Derek Stringfellow, project record · Project-internal record · retrieved 2026-09-25
Project copy; not published on this site.
Kind: GapThis project's simulation and agent design, not the physical cellProject design, not the physical cellint-519
Not known
No IntelliMake automation-level target has been recorded for S6. The level 5 'limited autonomous control' target (int-041) was stated for S2's agent; whether S6's agent shares it is not recorded.
No risk assessment for the S6 xArm 6 application has been confirmed: whether one exists for the complete application (arm, gripper, workpieces and the stations it hands parts to and from), who performed and signed it, and whether it was redone after installation as the xArm manual requires.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
The S6 emergency stops are not confirmed: whether any emergency stop buttons beyond the Control Box button are wired to EI, where they are, and whether S6 shares an emergency stop circuit with S2 or other stations.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
The final position of the S6 Control Box is not confirmed: whether it is outside the arm's working range, at 0.6 to 1.5 m height, with its emergency stop reachable.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
The Control Box must be placed outside the working range of the robotic arm to ensure the emergency stop button can be pressed once an emergency occurs.
UFACTORY xArm Hardware Manual (online), 1. Safety · UFACTORY · 1.3, CAUTION list [series text: names no single model]
S6's guarding and protective devices are not confirmed: whether fences, interlocked doors, light curtains, safety mats or laser scanners are wired to the SI protective stop input, whether any safety signal passes through a PLC (and if so whether it is a safety PLC), or whether SI is still in its default state with no additional safety equipment.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
The S6 xArm 6's safety-related settings are not confirmed: collision detection on or off, collision sensitivity level, collision rebound, self-collision detection and tool model, safety boundary and its limits, reduced mode and its limits, TCP payload, mounting direction, which CI inputs are configured as Stop Moving, Safeguard Reset, Reduced Mode or Manual Mode, and whether the documented default Advanced Settings password has been changed.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
You must enter password to access this page, the default password:
UFACTORY Studio User Manual (online), 7. Settings · UFACTORY · 7.4.3 Advanced Settings (the quote stops before the default value, which this corpus does not print) [general Studio text; the Studio manual says it applies to the xArm6]
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.
It is not confirmed whether people will enter the S6 xArm 6's working area during automatic operation, whether S6's working range (including the gripper) is marked, whether S6 operators are trained as the manual requires, or what the S6 gripper does to a held part on power loss or emergency stop.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
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 3 records here · Project copy; not published on this site.
Owner statements, 2026-09-21 (verbatim) · Derek Stringfellow (project owner) Derek Stringfellow, project record · Project-internal record · retrieved 2026-09-21 · cited by 5 records here · Project copy; not published on this site.
Owner statements, 2026-09-24 (verbatim; S40-S47) · Derek Stringfellow (project owner) Derek Stringfellow, project record · Project-internal record · retrieved 2026-09-25 · cited by 3 records here · Project copy; not published on this site.
Site photos, 2026-09-24: what they show, and what they do not (OBSERVATIONS.md) · Derek Stringfellow (project owner) Derek Stringfellow, project record · Project-internal record · retrieved 2026-09-25 · cited by 2 records here · Project copy; not published on this site.