§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 personalizes 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 personalized 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 personalization. S6 is the downstream arm10.
- S3, the staging table beside S2, has a defects area for S2's defective parts111213. Defects found on the xArm 6 side do not go there14. Rework is handled separately, in its own place15.
- The planned outcome for the cell is a working autonomous production run: accepting orders, personalizing the parts, then sending them for shipping, all done by the agents interacting with each other16.
An agent, here, is software that runs a station within limits people set: it works through the steps of each order and watches what happens around it. The Novice level of this section explains what it does when something goes wrong.
S6 in one line: S6 is the xArm 6 arm that handles parts after processing, routing them to inspection, rework or shipping4.
Look Back
A question from earlier on, to keep it fresh. Skip it if you like; nothing depends on it.
Choose your depth
1Beginner
What Does S6 Do, and Where?
For: Anyone with no robotics background: a visitor, a new operator, a manager
Kind of task: Recognize 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 personalized 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 engraved17. Its first orders are understood to be mostly simple custom cards, laser-engraved; more complex orders could follow18.
The Stations Around S6
- S4 is the conveyor that carries workpieces through the laser area1
- S5, the laser engraver, personalizes each piece2
- S6, the xArm 6, is drawn directly after S5, with an arrow from the laser into it34
- S8, the outbound conveyor, moves completed products toward packing and shipment. It is one of the stations after S65
- S10, Packing / Labeling, prepares, labels and packs the finished product. It is the last station in the layout6
- In the cell, S4 and S5 are interconnected19: the engraver stays in one place, and the conveyor moves the product from one location to another20, in either direction21.
- Both arms work at S4. One places the material there for the work, and the other picks up the finished product22. S6 is the one that picks up23.
The Flow, One Gift at a Time
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 job2410.
- Its tool: S6 uses an attachment with five suction cups25.
- A camera: none is installed on S6's arm at present26.
- Defects: S3, the staging table beside S2, has a defects area for S2's defective parts111213. Defects found on the xArm 6 side do not go there14.
- Rework: rework is handled separately, in its own place15.
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 kind27.
Two Arms, Two Jobs
- S2, the xArm 850, is the upstream arm. It takes incoming material off receiving toward personalization10.
- 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 other28.
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 work29.
- That camera had not been set up as of 2026-10-12: none of the cell's numbered cameras had30.
- S11, IntelliAware, uses AI vision to monitor the factory's operations, equipment, processes and safety31.
- 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 operation32.
- An arm that seems to have stopped may be waiting for a signal and about to act. Treat it as moving33.
Check Yourself
Answer, then check. Each option has its own feedback, and nothing is scored.
2Novice
The Flow in Motion
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, meet IntelliMake's scale for how much a machine decides, and see where this site's simulator sits on IntelliMake's twin framework. It is for someone who will work near or with the cell.
The Gift Flow, Step by Step
- Customer Order8
- Receiving, at S1834
- Cobot Handling, the first time: S289
- Staging, at S3836
- Laser Engraving, on S4 and S5812
- Cobot Handling, the second time: S689
- Quality Decision8
- Shipping / Rework8
- Packing & Labeling8
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.
Where S6 Picks Up
- S4 and S5, the laser engraver, are interconnected19: the engraver stays in one place, and the conveyor moves the product from one location to another20, in either direction21.
- Both arms work at S4: one places the material for the work, and the other picks up the finished product22. S6 is the one that picks up23. S2 is the one that places, moving parts there from S337.
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 personalization38.
- S7 is a Prusa 3D printer, a future extension of the factory39.
- In that flow S6 takes parts from the printer and passes them to the laser. So S6 serves both flows40.
- On the xArm 6 side, material for the 3D printer may also come through S4, either as an enhancement or as part of several processes between the engraver and the printer41.
Where a Finished Part Goes
- S8, the outbound conveyor, moves completed products toward packing and shipment5.
- Parts that S6 routes to shipping go to S8, the outbound conveyor, by default42.
- The last station in the layout is S10, Packing / Labeling, which prepares, labels and packs the product6.
- A defective part is not meant to go on to shipping: a camera on the arm was to check each finished product43.
- S3, the staging table beside S2, has a defects area for S2's defective parts. That area would be one of the cell's points of quality assurance and quality control (QA/QC)111213. Defects found on the xArm 6 side do not go there14.
- Rework is handled separately, in its own place15.
What Watches S6's Corner
- Camera C2 watches the robot–laser work area29.
- None of the cell's numbered cameras had been set up as of 2026-10-1230.
- This platform infers that the cameras feed S11's monitoring44. S11 monitors operations, equipment, processes and safety31.
- S6's arm has no camera of its own installed at present. Whether it will have one, or will use location only, is not known26. A camera on the arm was to be used for the arm's work: to collect the finished product and to check it, deciding whether the product goes to shipping or is a defect43.
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 people45.
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 operation32.
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:
- L0, Manual: the human decides and acts46.
- L1, Fixed: hard-coded logic and sensors decide47.
- L2, Programmable: the programmer decides, through PLC recipes and programs48.
- L3, Flexible: the automation system picks one of its predefined modes49.
- L4, Intelligent/Adaptive: an algorithm adjusts what happens50.
- L5, Agentic/Autonomous: an AI agent executes toward an objective51.
Inside Level Five
- 5A, Observe: collects data such as speed, product location, queue length and upstream and downstream status52.
- 5B, Understand & Determine: forms a view of the operating situation from that data53.
- 5C, Recommend: proposes an action; the human still decides54.
- 5D, Act with Human Approval: acts only after a specific authorization55.
- 5E, Limited Autonomous Control: makes certain decisions alone within safety and process limits, with a person supervising and handling exceptions56.
- 5F, Full Autonomy: receives objectives rather than instructions, then decides, acts, learns and replans57.
- 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 done58.
How Closely Is the Digital Tied to the Arm? IntelliMake's Twin Framework
- This is a different framework from the levels above it. L0 to L5 and 5A to 5F grade how much a machine decides; the twin framework grades a digital version of a physical thing. Level 5 is not a Digital Twin5951.
- IntelliMake sorts any digital version of a physical thing on two separate scales: coupling, how closely the digital version is tied to the thing, and scope, how much of the physical world it covers59.
- Coupling has five levels. From the loosest to the closest: Digital Image, Digital Model, Digital Monitor, Digital Guide and Digital Twin60.
- Digital Image: a static capture, such as a photo or a 3D scan61.
- Digital Model: the geometry, the physics and a simulation, as in CAD and in finite element analysis (FEA)62.
- Digital Monitor: a continuous flow of data from the physical thing to the digital63.
- Digital Guide: recommendations for action, from the digital back to the physical thing64.
- Digital Twin: interaction both ways, the digital and the physical kept in step65.
- Scope runs from a part or product, through a machine, cell or line, to a facility, enterprise or ecosystem66.
This project's simulation and agent design, not the physical cell
Where This Site's Simulator Sits
- The simulator is a simplified Digital Model. In Practice in the Simulator, the simulator's bench page is a machine-level Digital Model and each station page a cell-level one. They simulate the arm's motion against the scene's limits, and no data flows between them and a real arm in either direction, so nothing you do there reaches the cell67.
This project's simulation and agent design, not the physical cell
What the Arms' Agents Do
- 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 stations68.
- Each agent is designed to run its order: on the order's normal path it moves the arm itself, with no person approving each move. Anything off that path, it pauses and reports with recommended actions, and a person decides. The same rule applies to both arms69.
- While the arm works, the agent checks that each step of the order gets done. Anything outside the order's processing paths it reports rather than corrects: it pauses and alerts the person working with the cell, with the issue and recommended actions70.
- What that means for you: when the xArm 6 pauses with an alert, its agent has not fixed anything. Read the issue and its recommended actions; the decision about what happens next is yours7069.
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 S63.
- S6 works at a shared station. S6 picks up at S423, where S2 also works22. The engraver there stays in one place and the S4 conveyor moves the product from one location to another20, in either direction21.
- S8, the outbound conveyor, is one of the stations after S6. It moves completed products toward final packing and shipment5.
- Parts that S6 routes to shipping go to S8, the outbound conveyor, by default42.
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 marking3840.
- So S6 serves both production flows: in one it works after the laser, in the other before it1040.
- Material for the printer may also come through S4 on the xArm 6 side, either as an enhancement or as part of several processes between the engraver and the 3D printer41.
Defects and Rework
- S3, beside S2, has a defects area as well as its staging area. It would be one of the cell's QA/QC points1311.
- Defects found on the xArm 6 side do not go to that area14.
- Rework is not that area either: it is its own flow, in a different place15.
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 hub71.
- 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 status52.
- This platform infers that the factory's cameras feed S11, IntelliMake's monitoring layer44.
- None of the cell's numbered cameras had been set up as of 2026-10-1230.
- No camera is installed on the xArm 6 at present, and whether it will have one, or will use location only, is not known26. A camera there was to collect the finished product and to check it, deciding whether the product goes to shipping or is a defect43.
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 safeguard45.
What S6's Agent Does
- The agent is designed to run the order: on the order's normal path it moves the arm itself, with no person approving each move69.
- When something falls outside the order's processing paths, it pauses and alerts a person with the issue and recommended actions, instead of correcting it on its own, and the person decides7069.
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 approval72.
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: Analyze 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
- IntelliMake's reason. IntelliMake says the cell uses several arms so that each does task-specific work, and that more arms could be added75.
- 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 bottleneck28.
- A shared station. The two handling steps meet at S4. Both arms work there: one places the material for the work, and the other picks up the finished product2228.
- Reach. Both arms reach S4, so the reach argument is about the stations only one arm serves. The layout drawing puts them on opposite sides of S4: S1 and S3 beside S2, and S8 after S613. What is not measured is the distance: this platform assumes that a single arm probably could not reach both, and the as-built positions compared with each arm's published reach would settle it76.
- 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 line77.
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 flows40.
- So S6 receives parts from the laser in one flow and from the printer in the other940.
- Material for the printer may also come through S4, as an enhancement or as one of several processes between the engraver and the printer41.
- S3's defects area takes S2's defective parts and would be one of the cell's QA/QC points1112. Defects found on the xArm 6 side do not go there14.
- Rework is its own flow, in a different place from S3's defects area15.
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 three78.
- This platform infers that a policy fixed rules alone could carry out sits at IntelliMake levels 1 to 3, not level 579.
- 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 exceptions56.
- In the cell, the parts' route is fixed: S2 arranges them on S3 and moves them on to S4, and S6 picks up at S48023. Following a fixed route is, by the inference above, levels 1 to 3 work.
- The route does not say what becomes of each finished product, though: whether it goes to shipping, is a defect, or, in future, can be sent back for a redo. A camera on the xArm 6 was to make that judgment43; none is installed, and whether there will be one, or whether the xArm 6 will use location only, is not known26. This platform infers that this judgment, by whatever means it comes to be made, is the case to weigh when you test S6's work against the levels: the route does not make it, and if S6's agent makes it within set limits rather than by fixed rules, it is the kind of decision level 5E rests on81.
- IntelliMake's current working assumption is that the agents exchange information through a central shared hub rather than talking to each other directly71.
This project's simulation and agent design, not the physical cell
Guardrails for S6's Agent
- The agent is designed to run the order's normal path itself, with no person approving each move. Anything outside the order's processing paths it pauses and reports, with recommended actions, instead of correcting it, and a person decides6970.
- This project uses 5E as the design name for its agents' behavior: run the order's normal path without approval, and report anything off it69. Read it as the name of a design, not a level either arm has demonstrated. By the inference above, the name holds only for decisions the rules do not make for the agent79.
- Before you rest a 5E case on that judgment, check which side of that rule a defective part falls on. If routing it as a defect is part of the order's normal path, the agent acts on its own judgment; if it is off the path, the agent pauses and reports, and a person decides, so the judgment becomes a recommendation to that person rather than a decision the agent acts on6981.
- 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 approval72.
- 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 joints82.
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 detection83.
- 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 updated83.
- The xArm manual says a complete safety assessment must be recorded each time the arm is re-installed and debugged84.
Check Yourself
Answer, then check. Each option has its own feedback, and nothing is scored.
Not settledOpen Questions · 53
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.
See reference 89 - Kind: Gap
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.
See reference 91 - Kind: Gap
The physical I/O that will carry signals between S2 and S4 (and the other stations) is not defined. It may differ from the simulation's signals.
See reference 92 - Kind: Contradiction
The future 3D-printed flow in the IntelliMake diagram has no S2 step (printed parts go from S7 straight to S6), but S2's stated role includes handling material for 3D printing in the future. What S2 does in the future flow is unresolved: IntelliMake says it could be S3, S4 or S7, that this is subject to change, and that the cell is not locked into any configuration.
See reference 93 - Kind: Gap
The topic mapping lists cameras C1–C3, but the layout labels only C1 and C2. Where C3 is and what it covers are not documented.
See reference 94 - Kind: Gap
The topic mapping refers to an S9 QC decision pathway, but no S9 station appears in the layout.
See reference 95 - Kind: Contradiction
The same diagram labels S8 two ways: 'Outbound Conveyor / QC Hold' and 'Outbound Conveyor / Shipping'.
See reference 96 - Kind: Gap
The layout draws unlabeled 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.
See reference 97 - Kind: Gap
IntelliMake's reason for putting the 850 at S2 and the xArm 6 at S6 is not documented. IntelliMake says only that the cell uses several arms for task-specific work and could add more (int-057).
See reference 98 - Kind: Contradiction
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.
See reference 99 - Kind: Gap
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. IntelliMake says this will be developed as the simulation is created.
See reference 100 - Kind: Gap
Whether camera C1's or S11's output reaches S2 or the shared hub, and in what form, is not documented, and IntelliMake does not yet know.
See reference 101 - Kind: Gap
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, and IntelliMake does not yet know. The diagram calls S11 'monitoring of ... safety', which does not make it a safeguard.
See reference 102 - Kind: Contradiction
S97 says the cabinet sizes are all the same, while the measurements table gives the S4 cabinet as 32.5 in high and 50 in long, against 32.25 in high and 25.5 in long for S2, S3, S6 and S8. The height difference is settled by int-099: S4 was 32.5 in high when the table was taken, and every station's height is adjustable. The length difference is not settled by any statement: the project reads S97 as covering the 25.5 in cabinets (S2, S3, S6, S7 and S8), and that reading is unconfirmed.
See reference 103 - Kind: Contradiction
IntelliMake's written answer (Batch 01, Question 2) and the project's earlier statements have S2 place a part on S4, or on S3 when S4 is busy or the part does not fit there, so that parts need not pass through staging; this project's simulation was specified from that reading, moving cards from one conveyor to another (int-013, int-014, int-051). The project's later statement S146, answering which is right now, gives the route as S1 to S3, and S3 to S4: S2 arranges parts on S3 first, then later moves them from S3 to S4 (int-081). The later statement is the current reading; the earlier records are kept as history, marked as superseded.
See reference 104 - Kind: Contradiction
The project's earlier statement says S2 'can not simply stack' workpieces (int-017), which this project's S2 design read as one card per place on S3. Asked whether same-color cards are placed on top of each other or side by side, the later statement S146 answers 'On top of each other': real stacks on S3 (int-084). The later statement is the current reading for S3, and int-017 is kept as history, marked as superseded. Whether the rest of the earlier rule, not breaking the space the system allocates, still holds is not stated.
See reference 105 - Kind: Contradiction
The earlier target for the S2 agent is level 5E, limited autonomous control, with the goal of not needing human approval (int-041). A later statement says the agent operates the real arm in fulfilling orders but is not expected to work semi-autonomously: it reports deviations instead of correcting them (int-090, int-091). That answer took none of the options on whether 5E stays the goal. The later statement S148 settles it: 'Runs the order, reports problems', for 'Both arms'. On the order's normal path the agent moves the arm with no person approving each move; anything off the path, it pauses and reports with a recommendation, and a person decides; the option chosen names this the current design, 5E (int-095). So 5E stays the design for both arms' agents, the goal of not needing human approval holds on the normal path, and int-041 is kept as history, marked as superseded.
See reference 106 - Kind: Gap
How S3 is divided between its staging and defects areas, how many colour areas staging holds, and how many cards a stack may hold are not documented. Whether S3 can hold both kinds of material is itself open: a separate defects station could be added if it cannot (int-087).
See reference 107 - Kind: Gap
Which decisions on the order's normal path remain the agent's own is not stated. The parts' route is fixed, S1 to S3 and S3 to S4 (int-081), and a defective part takes its own move, to the defects area on S3 (int-107), so the choice between S4 and S3 that the earlier design gave S2 no longer arises, while level 5E rests on decisions within limits that fixed rules do not make (lvl-011, lvl-015).
See reference 108 - Kind: Gap
How this project's simulation keeps to the cell's route is not fully settled. Since its configuration's schema 0.5.0 (2026-10-07), the simulation is configured to take each card from S1 to S3, then from S3 to S4 (int-081), and S3 has a staging area and a defects area whose stacks each hold up to 10 cards, a labelled placeholder (int-104; one card until 2026-10-18). Since 2026-10-09 the simulation's motion process refuses to place a card anywhere its route does not take it from the place it was picked, and refuses any pick or place in the defects area, which a person must decide (the way for a person to decide is not yet built). Keeping one colour to each stack, and which stack a card goes to, are designed but not enforced: they rest on labels the simulation cannot check. Before 0.5.0 the simulation placed each card on S4, or on S3 when S4 was busy (int-014).
See reference 109 - Kind: Gap
The measurements table does not say what its 'Height' column is measured from. The cabinets' heights (32.25 and 32.5 in) and the S1 conveyor's (32 in) read as heights above the floor, and the S4 engraver conveyor's (3.5 in) and the S2 and S6 mount plates' (1 in) as each item's own height; this project's Operate scenes draw them that way (the agent's simulation configurations keep placeholder surfaces), and that reading is unconfirmed.
See reference 110 - Kind: Gap
Whether a card a camera judges defective is on the order's normal path, so that the agent sends it to a defects area itself (for S2, S3's defects area, int-107; where the xArm 6 side's defects go is not known, int-539), or off it, so that the agent pauses and a person decides, is not decided. Until it is, the simulation is designed to pause and report; that behavior is not yet built.
See reference 111 - Kind: Contradiction
The earlier statement S146 says defective parts reach S3's defects area from S2 and from the xArm 6 side, including defects found after the engraver or the printer (int-086), and the option chosen in S149 repeats that defects go to S3 (int-535). Asked whether S154's first answer means the xArm 6 side's defects no longer go to S3's defects area, the later statement S155 answers that they do not end up in S3 at this time. The later statements are the current reading for the xArm 6 side (int-538); where those defects go instead is a gap (int-539). S154 and S155 leave S2's half of int-086 and int-535's rework half unchanged: int-107 and int-540 carry them, keeping the earlier citations (S146, S149), which the later statements do not restate. int-086 and int-535 are kept as history, marked as superseded.
See reference 112 - Kind: Contradiction
The earlier statement S97 says the engraver can travel along the length of the S4 conveyor (int-068). The later statement S172 says the engraver will remain stationary and the conveyor will move the product from one location to another (int-111). This project reads S172 as replacing S97, and int-111 as the current reading: S97 says what the engraver can do, a capability, and S172 how the cell will run, the plan, so the cell is described as running with a fixed engraver. Whether the two statements conflict at all, or the engraver can still travel and will not be used that way, is not settled: only the person who made both statements can settle it. S97's other half, that the engraver and the conveyor are interconnected systems, is unchanged; int-112 carries it with S97's citation. int-068 is kept as history, marked as superseded.
See reference 113 - Kind: Gap
Where S6 puts a part on each route is only partly settled: shipping goes to S8 by default (int-504), defects found on the xArm 6 side do not go to S3's defects area at this time, and another area for them is to be determined (int-538, int-539); and rework is its own flow, in a different place from S3's defects area (int-540). A defect table at S7 was proposed for Phase 1 (int-531); whether that proposal stands is not stated. Where a part for inspection or for a redo goes is not documented; the layout has no labeled inspection station (int-037), and the redo route is a future state (int-530).
See reference 114 - Kind: Contradiction
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.
See reference 115 - Kind: Gap
Camera C2 monitors 'the robot–laser work area', but the layout does not say which robot: S2, S6 or both. The xArm 6 has no camera of its own installed, and whether it will have one is unknown (int-543), so whether such a camera would be C2 or an additional one does not arise at present.
See reference 116 - Kind: Gap
How the Quality Decision after S6's handling step will be made is not documented. A camera on the xArm 6 was to check the finished product and decide shipping, defect or redo (int-545), but none is installed and whether there will be one is unknown (int-543). S11, 'using one of the cameras will likely participate' in inspection; how the decision would be split between the two is not stated. A defect table at S7 was proposed for Phase 1 (int-531); defects found on the xArm 6 side do not go to S3's defects area at this time, and another area for them is to be determined (int-538, int-539); whether the S7 proposal stands is not stated. The topic mapping also names an S9 QC decision pathway, but no S9 station appears in the layout.
See reference 117 - Kind: Gap
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).
See reference 118 - Kind: Gap
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.
See reference 119 - Kind: Gap
The make, model and weight of S6's five-cup suction tool are not documented.
See reference 120 - Kind: Gap
The xArm 6 is mounted on the S6 cabinet, and a Phase 1 layout drawing places S6 between S4 and S8, with S7 beside it (int-067), but where on the cabinet it sits, what the arm can reach and what separates it from people are not documented. The arms are not yet in their final layout, and whether this mounting is the arm's final position is not documented.
See reference 121 - Kind: Gap
No IntelliMake document sets an automation level for S6. This project's design gives both arms' agents the same level, 5E, and the same report-don't-correct rule (int-095); for S2 the level was first given as a target in IntelliMake's terms (int-041).
See reference 122 - Kind: Gap
How a redo will be managed, and whether S6 will have a redo bin, is not decided.
See reference 123 - Kind: Gap
Whether S7 is still proposed as the defect table beside S6 is not stated. Defects found on the xArm 6 side do not go to S3's defects area at this time, and another area for them is to be determined (int-538, int-539); this course labels S7 as the 3D printer, but neither says whether the drawing's proposal stands.
See reference 124 - Kind: Gap
Where defects found on the xArm 6 side go is not known: another area for them is to be determined.
See reference 125 - Kind: Gap
Which conveyor would carry defects identified at S6 back to S2, if that route were used (int-541), is not stated.
See reference 126 - Kind: Gap
Whether the xArm 6 will have a camera, or will use location only, is unknown. What using location only would involve is not stated.
See reference 127 - Kind: Contradiction
The earlier statement S90 says both arms will have a camera, and S91 says what the camera on the xArm 6 is used for: to collect the finished product and to check it (int-529). Asked whether the xArm 6's camera is installed, the later statement S182 answers that it is not installed at present, and that it is unknown whether there will be one or whether the xArm 6 will use location only. S182 is the current reading (int-543); whether the xArm 6 will have a camera is a gap (int-544). S182 does not say that the xArm 6 will never have a camera, and it does not restate what a camera there would be used for: int-545 carries S91's account as what was planned, keeping the earlier citations. What S90 and S91 say of the xArm 850's camera is not affected. int-529 is kept as history.
See reference 128 - Kind: Gap
The S6 xArm 6's controller type (AC or DC control box) is not recorded, and its serial number is not recorded (shown in the 2026-10-16 screenshot, withheld; decisions file 10-16 §1.3). The site-photo record lists these as still open for the next visit. Its firmware version was read on 2026-10-16 (int-553).
See reference 129 - Kind: Contradiction
The statements of 2026-10-22 disagree on where the engraver stood that day. S222, item 1, about the xArm 850, says "It is mounted on station cabinet, like x6, engraver and 3d printer, as expressed previousilly." S226, later the same day, says "The engraver is on a different table and n ot sittng on the final station cabinent yet." S251 (2026-10-26) settles it: "Engraver was still on a practice table and not on intellimake designated cabinet station"; S226 is the current reading, carried by int-615. The sources still disagree, so this record stays (README, Superseded records, rule 6). The engraver's place in the cell stays a placeholder until it is on its cabinet.
See reference 130 - Kind: Contradiction
The cell's measurements table (2026-09-30) gives the S4 engraver conveyor as 38.5 in (97.8 cm) long; the measurement of 2026-11-05 gives its belt as 97 cm. The 2026-11-05 measurement is the current reading (int-617); int-101 is kept as history, and its height, which the later measurement does not restate, is carried by int-619. Whether the two measured the same extent (the belt, or the conveyor's frame) is not stated.
See reference 131 - Kind: Contradiction
The measurements of 2026-10-22 put the S4 engraver's carriage area from 36 cm to 60 cm along the conveyor from its xArm 850 end, with the carriage 46.5 cm high above the belt; those of 2026-11-05 give 37 cm of belt before the area (so 37 cm to 60 cm) and the engraver 49 cm high above the belt, including the extra clearance of its plastic shield. The 2026-11-05 figures are the current reading (int-621, int-622); int-615 is kept as history. Whether the shield was on the engraver on 2026-10-22 is not stated.
See reference 132 - Kind: Contradiction
The cell's measurements table (2026-09-30) gives the S4 cabinet as 25.5 in (64.8 cm) wide and 50 in (127 cm) long; the statements of 2026-11-05 give it as 59 cm wide and 127.5 cm long, and choose 59 cm over the table's width. The 2026-11-05 figures are the current reading (int-626); int-075 is kept as history, and its height, which the later statements do not restate, is carried by int-628.
See reference 133 - Kind: Gap
Not stated for S4: the third arm that is to push the conveyor's pad (int-633): its model, where it stands and what it can reach; where the pad is; what a push does (how long or how far the belt runs, in which direction, and whether it stops under the engraver on its own); whether and how the engraver would be interlocked; whether the conveyor may move while an arm places or picks; and how the arms share S4: whether both may work there at the same time, and if not, in what order and on whose signal. The engraver's width and its place across the belt are given (int-623), and where the station is to stand is planned (int-631).
See reference 134 - Kind: Gap
Each arm has its own stretch of the belt, the xArm 850's from its end to the carriage area at 37 cm, the xArm 6's from the area's end at 60 cm to the other end at 97 cm (int-621). Where within each an arm places or picks is not stated, nor where the printed flow places.
See reference 135 - Kind: Gap
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.
See reference 136 - Kind: Gap
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.
See reference 137 - Kind: Gap
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.
See reference 138 - Kind: Gap
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.
See reference 139 - Kind: Gap
It is not confirmed whether people will enter the S6 xArm 6's working area during automatic operation, whether S6's working range (including its suction tool) is marked, whether S6 operators are trained as the manual requires, or what S6's suction tool does to a held part on power loss or emergency stop (whether the suction keeps holding it or it drops).
See reference 140 - Kind: Gap
The S6 xArm 6's controller type (AC or DC) and SDK version are not confirmed, and its serial number is not recorded (shown in the 2026-10-16 screenshot, withheld; decisions file 10-16 §1.3). Its firmware and Studio versions, both 2.7.0, were read on 2026-10-16 (int-553, int-554). 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.
See reference 141 - Kind: Gap
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, the TCP payload's centre of gravity, which CI inputs are configured as Stop Moving, Safeguard Reset, Reduced Mode or Manual Mode, whether the documented default Advanced Settings password has been changed, and whether the controller's mounting setting matches how the arm is installed. Its payload and mounting settings were read on 2026-10-16 (int-556, int-555): they are the controller's settings, not a weighing or an inspection of how the arm is fixed.
See reference 142
ProvenanceReferences · 142
Each number in the text points here. Every entry states its confidence class in words and keeps its evidence one click away. How to read the labels.
Key to the badges
- Confidence: Verified
- A manufacturer or IntelliMake document says so, or it was observed directly. It does not mean anyone measured it at S6.
- Confidence: Inferred
- Reasoned from Verified facts. The reasoning is printed with the record.
- Confidence: Assumed
- Plausible but untested. The record says how it would be checked.
- Kind: Gap
- Not known. No figure or answer is given in its place.
- Kind: Contradiction
- Sources disagree. Both sides are shown, and the site does not pick one silently.
- Kind: Recommendation
- Project advice drawn from the records it cites. Not a fact about the machine and not a confidence class, so the filter never hides it.
- Awaiting cell access
- Awaiting cell access: could be confirmed or corrected once the physical S6 cell can be observed.
- This project's simulation and agent design, not the physical cell
- This project's simulation and agent design, not the physical cell.
Image Credits
- 3D model: © 2018 UFACTORY Inc., BSD-3-Clause, from UFACTORY Inc. (xArm-Developer/xarm_ros2). License text · Source
Sources for This Section
- CODE_SESSION 01 — xArm 850 Interactive Learning Platform (project specification) · Derek Stringfellow (project owner)
- Collision Detection in UFACTORY Robotic Arms: Current and Dynamic Model-based Feature (UFACTORY support article) · UFACTORY (manufacturer)
- IntelliMake Phase 1 Factory: Autonomous Production Demonstrator (infographic) · IntelliMake.org (IntelliMake)
- Level 5. Agentic Evolution: A Spectrum of Increasing Decision Authority (infographic) · IntelliMake.org (IntelliMake)
- Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow (project owner)
- Owner statements, 2026-09-21 (verbatim) · Derek Stringfellow (project owner)
- Phase 1 layout drawing, sent by Derek (2026-09-30) · Derek Stringfellow (project owner)
- Phase 1 measurements table, sent by Derek with the layout drawing (2026-09-30) · Derek Stringfellow (project owner)
- Site photos, 2026-09-24: what they show, and what they do not (OBSERVATIONS.md) · Derek Stringfellow (project owner)
- The difference between UFACTORY xArm5, UFACTORY xArm6 and UFACTORY xArm7 (Help Center article) · UFACTORY (manufacturer)
- The Progression Cheat Sheet: 6 stages of manufacturing automation · IntelliMake.org (IntelliMake)
- The Two-Dimensional Digital Twin Framework (class slide) · IntelliMake.org (IntelliMake)
- UFACTORY 850 product page · UFACTORY (manufacturer)
- UFACTORY Studio User Manual (online), 2. Glossary · UFACTORY (manufacturer)
- UFACTORY Studio User Manual (online), 3. Connection · UFACTORY (manufacturer)
- UFACTORY Studio User Manual (online), 7. Settings · UFACTORY (manufacturer)
- UFACTORY xArm Hardware Manual (online), 1. Safety · UFACTORY (manufacturer)
- UFACTORY xArm Hardware Manual (online), 2. Hardware Installation · UFACTORY (manufacturer)
- UFACTORY xArm Hardware Manual (online), 3. Controller Electrical Interface · UFACTORY (manufacturer)
- UFACTORY xArm Hardware Manual (online), 4. Robotic Electrical Interface · UFACTORY (manufacturer)
- UFACTORY xArm Hardware Manual (online), 7. Production Information · UFACTORY (manufacturer)
- UFACTORY xArm Hardware Manual (online), 8. Technical Specifications · UFACTORY (manufacturer)
- UFACTORY xArm product page · UFACTORY (manufacturer)
- xArm 850 S2 Project: Open Questions for IntelliMake, Batch 01 responses · IntelliMake.org (IntelliMake)
- xArm-Python-SDK API documentation (doc/api/xarm_api.md) · UFACTORY (manufacturer)
IntelliMake diagrams are redrawn as native figures, © IntelliMake.org. UFACTORY does not endorse this platform.