Sections

Learn

Operate

Planned

  • Twin: a twin-ready view of the arm and its cell
  • Program your machine: Blockly and Python programs of your own

Resource Desk

§2 xArm 850

Role in the Phase 1 Production Process

S2 as part of a production system: what comes before and after it, what goes in and comes out, the cameras, and why there are two arms.

Start Here

This section places the arm inside a small factory: what arrives before it, what leaves after it, what watches it, and why a second arm works further down the line. The cell as IntelliMake designs it comes first. This project's own design for the arm follows, under its own label.

  1. S1 Receiving: incoming blanks or materials arrive and are moved into production1
  2. S2, the xArm 850: picks up incoming material and moves it on23
  3. S3, the staging table that buffers workpieces, and S4, the conveyor through the laser area45
  4. S5, the laser engraver, which personalizes the part6
  5. S6, an xArm 6: handles parts after processing, toward inspection, rework or shipping7
Redrawn from IntelliMake's Phase 1 diagrams as a native figure. © IntelliMake.org.
  • IntelliMake's Phase 1 factory is designed to show autonomous production of personalized products, made in many variants and small numbers8.
  • Its first products are laser-engraved gifts. The gift flow runs Customer Order → Receiving → Cobot Handling → Staging → Laser Engraving → Cobot Handling → Quality Decision → Shipping / Rework → Packing & Labeling910.
  • S2 is the first of the two Cobot Handling steps, and S6 is the second11.
  • The S1 conveyor can be seen as part of the cell's inventory supply: material from vendor partners arrives and is placed on it12.
  • S2 takes those items and arranges them on S3, the staging table, stacking cards of the same color together. Later it moves them from S3 on to S4, so its route for a part is S1 to S3, then S3 to S4131415.
  • S3 also has a defects area, which would be one of the cell's quality checkpoints. Defective parts reach it from S21617.
  • 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 other18.

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.

S2 in one line: S2 is the xArm 850 arm that picks up incoming material and moves it between receiving, staging and production23.

Look Back

A question from earlier on, to keep it fresh. Skip it if you like; nothing depends on it.

q-s01-b-01 What kind of machine is the xArm 850?
  1. Check option (a)

    Correct. Right. It has a base and six rotary joints, Joint 1 to Joint 6.8586

  2. Check option (b)

    Not this one. Conveyors move things along a line. In this cell, S1 and S4 are the conveyors. The 850 is an arm with six rotating joints.1586

  3. Check option (c)

    Not this one. The engraver is S5, an xTool F1 Ultra. The 850 moves material between stations; it does not engrave it.63

  4. Check option (d)

    Not this one. Camera C1 watches receiving and Camera C2 watches the robot and laser area. The 850 is the arm itself, at station S2.32332

q-s01-b-03Safety UFACTORY calls the 850 a "collaborative robot". Does that mean you can stand in its working area while it runs?
  1. Check option (a)

    Not this one. UFACTORY's own manual says no people should be in the working area while the arm is running. Whether an installation is safe to share is decided by a risk assessment of the whole system, not by the label.368788

  2. Check option (b)

    Correct. Right. UFACTORY says to keep people out of the working area while the arm runs, and makes the integrator responsible for a risk assessment of the whole system.3687

  3. Check option (c)

    Not this one. Collision detection is a controller feature, and the UFACTORY sources do not call it safety-rated. This project's advice is not to treat it as a safeguard. Stay out while the arm runs.89909136

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 S2 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 through the factory and find the arm's place in it: what comes before it, what comes after it, and what it hands on. First you see the cell as IntelliMake designs it. Then, under its own label, you see this project's design for the arm: how it is planned to work.

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 numbers8. It starts with laser-engraved gifts, and is planned to grow into 3D-printed custom parts that are then laser marked or engraved9. Its first orders are understood to be mostly simple custom cards, laser-engraved; more complex orders could follow19.

The Stations Around S2

  1. S1, the incoming conveyor and receiving station, takes in blanks or materials and moves them into production1
  2. S2, the xArm 850, picks up that incoming material23
  3. S3 is a staging table that holds workpieces for a while, as a buffer4
  4. S4 is the conveyor that carries workpieces through the laser area5
  5. S5 is the laser engraver, which personalizes each piece6
Redrawn from IntelliMake's Phase 1 diagrams as a native figure. © IntelliMake.org.
  • The S1 conveyor can be seen as part of the cell's inventory supply: material from vendor partners arrives and is placed on it12.
  • S3 can serve two purposes: staging material in one area, and holding defects in another. The defects area would be one of the cell's quality checkpoints16.
  • S4 and S5 are interconnected20: the engraver stays in one place, and the conveyor moves the product from one location to another21, in either direction22.
  • Both arms work at S4. One places the material there for the work, and the other picks up the finished product23.

The Flow, One Gift at a Time

A gift moves through nine steps: Customer Order → Receiving → Cobot Handling → Staging → Laser Engraving → Cobot Handling → Quality Decision → Shipping / Rework → Packing & Labeling10.

"Cobot Handling" appears twice. The first time is S2, between Receiving and Staging. The second time, after the laser, is S611.

What S2 Does

S2's job is to pick up incoming material and move it between receiving, staging and production3. It does not engrave anything; S5 does that6. It does not deal with finished parts either; that is the other arm's work7.

  • Sorting on S3: S2 takes the items from S1 and arranges them on S3. For business cards, cards of the same color go in the same area, stacked on top of each other1314.
  • On to S4: later, S2 moves the parts from S3 on to S4. Its route for a part is S1 to S3, then S3 to S415.
  • Defects: defective parts go to the defects area on S317. Defects found on the xArm 6 side do not come to S324.
  • Its tool: S2's attachment is a single suction aperture25.
  • Its camera: S2 has a camera of its own, on the arm itself26. The arm is to use it to select the correct material to fulfill an order, and possibly to check that material so that defective material is not used27.

Two Arms, Two Jobs

  • S2 is the upstream arm. It takes incoming material off receiving and on toward personalization28.
  • S6, a UFactory xArm 6, is the downstream arm. It handles parts after processing and routes them to inspection, rework or shipping728.
  • At S4, where both arms work, S2 places the material for the work, moving parts there from S3, and S6 picks up the finished product292330.
  • This platform infers one benefit: with two arms, loading new material and unloading finished parts can happen at the same time, where one arm would have to do both in turn31. The Expert tier builds the full case, and marks which part of it is assumed.

What Watches the Cell

  • Camera C1 watches incoming material and receiving32. Camera C2 watches the area where the robot and the laser work33.
  • Neither of these cameras had been set up as of 2026-10-1234.
  • The arm's own camera is not one of them. Camera C1 and Camera C2 watch parts of the cell; the arm's camera is for the arm's work26273233.
  • S11, IntelliAware, uses AI vision to monitor the factory's operations, equipment, processes and safety35.
  • Monitoring is not protection. Watching a hazard is not the same as stopping it. Whatever the cameras see, nobody should be in the arm's working area while it runs36.

This project's simulation and agent design, not the physical cell

This Project's Design for S2

  • In this project's design, S2 moves a card from S3 on to S4 once S4 gives its "all clear and ready" signal37.
  • S2 listens for that signal38. It also reports its own state39.
  • The software agent that runs S2 is designed to run each order: on the order's normal path it moves the arm itself, with no person approving each move40. If something falls off that path, it pauses the arm and reports the issue with recommended actions, and a person decides4140.

In and Out: The Summary Card

  • Material in: whatever arrives at S1 from vendor partners, which IntelliMake calls blanks or materials112.
  • Material out: the workpiece, arranged on S3 and later moved from S3 to S415; defective parts go to the defects area on S317.

This project's simulation and agent design, not the physical cell

  • Information in, in this project's design: S4's "all clear and ready" signal38.
  • Information out, in this project's design: a report of S2's own state39, and, from its agent, a report to a person when something falls off the order's normal path41.

Do Not Lean on the Cameras

This project's advice: do not treat S11 or the cameras as a safeguard. The S2 agent must not rely on them to stop motion or to protect people, and neither should you42.

Check Yourself

Answer, then check. Each option has its own feedback, and nothing is scored.

q-s02-b-01 Which station comes directly before S2?
  1. Check option (a)

    Correct. Right. S1 receives incoming blanks and moves them into production, and S2 picks from there.13

  2. Check option (b)

    Not this one. The laser comes after S2. The flow runs Receiving → Cobot Handling → Staging → Laser Engraving.10

  3. Check option (c)

    Not this one. S6 is the other arm. It works downstream, after the laser.728

  4. Check option (d)

    Not this one. Shipping is near the end of the flow. S2 is at the start, straight after Receiving.1011

q-s02-b-02 What is S2's job?
  1. Check option (a)

    Correct. Yes. S2 picks and transfers incoming material between receiving, staging and production.3

  2. Check option (b)

    Not this one. That is S6, the downstream arm.728

  3. Check option (c)

    Not this one. S5 engraves. S2 only handles the material.63

  4. Check option (d)

    Not this one. Camera C1 does that: it watches incoming material and receiving.32

q-s02-b-03 Which of these statements is this project's design, not a confirmed fact about the real cell?
  1. Check option (a)

    Correct. Right. Moving cards from S3 on to S4 is the cell's route; the "all clear and ready" signal S2 waits for is this project's design.3738

  2. Check option (b)

    Not this one. That comes from IntelliMake's own layout of the cell, so it is cell design.1

  3. Check option (c)

    Not this one. That also comes from IntelliMake's layout.7

  4. Check option (d)

    Not this one. That is the cell's route, stated for the cell itself, so it is cell design. What this project adds is the signal that starts each move.1537

q-s02-b-04Safety S11 IntelliAware "monitors safety". Will it stop S2 before the arm hits you?
  1. Check option (a)

    Not this one. S11 provides monitoring, and watching a hazard is not the same as stopping it. This project's advice is not to treat S11 or the cameras as a safeguard.3542

  2. Check option (b)

    Correct. Right. Do not treat S11 or the cameras as a safeguard. UFACTORY says nobody should be in the working area while the arm operates.4236

Open questions in this section

Next on the beginner path: §6 Basic Operating Sequence

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 in order, see how the arm sorts parts on the staging table and what it waits for, meet IntelliMake's scale of automation levels, 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

  1. Customer Order10
  2. Receiving, at S1101
  3. Cobot Handling, the first time: this is S21011
  4. Staging, at S3104
  5. Laser Engraving, on S4 and S51056
  6. Cobot Handling, the second time: this is S61011
  7. Quality Decision10
  8. Shipping / Rework10
  9. Packing & Labeling10
Redrawn from IntelliMake's Phase 1 diagrams as a native figure. © IntelliMake.org.

Notice that S2 sits right after the material arrives and right before staging113. In the cell, S2's route for a part follows that path: it arranges the part on S3 first, and later moves it from S3 to S4 for the laser15.

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 combines a custom shape with surface personalization43.
  • S7 is a Prusa 3D printer, a future extension of the factory44.
  • In that flow S6 takes the printed part to the laser, so S6 serves both flows45.

What Watches, and Where Its Pictures Go

  • Camera C1 watches receiving, and Camera C2 watches the robot and laser area3233.
  • None of the cell's numbered cameras had been set up as of 2026-10-1234.
  • This platform infers that the cameras, Camera C1 included, feed S11's monitoring. IntelliMake's mapping table groups the cameras with S11, and the layout draws dotted lines from the cameras to S1146.
  • S2 also has a camera of its own, on the arm itself. It is not one of the cell's numbered cameras, such as Camera C1 and Camera C2: the arm's camera and those cameras are not related263233. The arm is to use its camera for its work: to select the correct material to fulfill an order, and possibly to check that material so that defective material is not used27.
  • Watching is not stopping. Whatever any camera sees, nobody should be in the arm's working area while it runs36.

The Conveyors

IntelliMake's topic mapping ties the Vention conveyor to S1, S4 and S8. S1 is the receiving conveyor that feeds S2, and S4 is the conveyor through the laser area4715.

  • S1 can be seen as part of the cell's inventory supply: material from vendor partners arrives and is placed on the conveyor12.
  • S4 and S5, the laser engraver, are interconnected20: the engraver stays in one place, and the conveyor moves the product from one location to another21, in either direction22.
  • S4 is where the two arms meet. Both work there: one places the material for the work, and the other picks up the finished product23.

The Staging Table: Two Areas

  • S2 arranges the items it takes from S1 logically on S3. For business cards, cards of the same color go in the same area13.
  • Those cards are stacked on top of each other, so each color builds its own stack14.
  • S3 can serve two purposes: staging material in one area, and holding defects in another. The defects area would be one of the cell's points of quality assurance and quality control (QA/QC)16.
  • Defective parts reach that area from S217. Defects found on the xArm 6 side do not go there24.

This project's simulation and agent design, not the physical cell

S2's Rules in This Project's Design

  • Once S4 gives its "all clear and ready" signal, S2 moves a waiting card from S3 on to S437.
  • When S3 has no room and S4 is busy, S2 watches S4. Once S4 is available it moves a card from S3 to S4, and the freed space lets it take material from S1 again48.
  • What S2 listens for: S4's "all clear and ready" signal38.
  • What S2 reports: its own state, alongside the state it receives from other stations39.

A Worked Example

  • Suppose a card arrives at S1. S2 places it on S3, on top of the cards of the same color1314.
  • Later S2 moves a card from S3 on to S415, at the signal this project's design sets out above.
  • Suppose instead the card is defective. It goes to the defects area on S3, apart from the staged cards1617. S2's own camera may possibly check material, so that defective material is not used27.

This project's simulation and agent design, not the physical cell

Safety Advice for This Project

This project's advice: do not treat S11 or the cameras as a safeguard, and do not rely on them to stop the arm or to protect you42.

How Much Does the Machine Decide? IntelliMake's Levels

  • L0, Manual: a human decides and acts49.
  • L1, Fixed: hard-coded logic and sensors decide50.
  • L2, Programmable: a programmer's PLC recipes decide51.
  • L3, Flexible: the system selects among predefined modes52.
  • L4, Intelligent/Adaptive: an algorithm makes adjustments53.
  • L5, Agentic/Autonomous: an AI agent works toward an objective54.

Inside Level Five: From Watching to Acting

  • 5A, Observe: gathers data such as speed, queue length, schedules and upstream and downstream status55.
  • 5B, Understand & Determine: interprets what that data means for the situation56.
  • 5C, Recommend: advises the operator, who keeps the decision57.
  • 5D, Act with Human Approval: the machine can act, but only after a person authorizes it58.
  • 5E, Limited Autonomous Control: makes certain decisions on its own inside safety and process limits, while a person supervises and handles exceptions59.
  • 5F, Full Autonomy: given objectives, not instructions, it decides, acts, learns and replans60.
  • IntelliMake sums up the shift: traditional automation tells a machine what to do and how, while agentic automation gives it a goal and the authority to work out what should be done61.

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 Twin6254.
  • 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 covers62.
  • Coupling has five levels. From the loosest to the closest: Digital Image, Digital Model, Digital Monitor, Digital Guide and Digital Twin63.
  • Digital Image: a static capture, such as a photo or a 3D scan64.
  • Digital Model: the geometry, the physics and a simulation, as in CAD and in finite element analysis (FEA)65.
  • Digital Monitor: a continuous flow of data from the physical thing to the digital66.
  • Digital Guide: recommendations for action, from the digital back to the physical thing67.
  • Digital Twin: interaction both ways, the digital and the physical kept in step68.
  • Scope runs from a part or product, through a machine, cell or line, to a facility, enterprise or ecosystem69.

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 cell70.

This project's simulation and agent design, not the physical cell

What S2's Agent Does

  • The agent that runs S2 is designed to run each order: on the order's normal path it moves the arm itself, with no person approving each move40.
  • While the arm works, the agent checks that each step of the order gets done. Anything that falls off the order's normal path, it does not correct: it pauses the arm and alerts the person working with the cell, with the issue and recommended actions, and that person decides4140.
  • What that means for you: when the arm pauses with an alert, the agent has not fixed anything. Read the issue and its recommended actions; the decision about what happens next is yours4140.
  • 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 stations, and the same rule applies to both7140.

Check Yourself

Answer, then check. Each option has its own feedback, and nothing is scored.

q-s02-n-01 In the gift flow, which step comes straight after Staging?
  1. Check option (a)

    Correct. Right. The flow runs Receiving → Cobot Handling → Staging → Laser Engraving → Cobot Handling.10

  2. Check option (b)

    Not this one. Cobot Handling comes before Staging (that is S2) and again after Laser Engraving (that is S6), but not straight after Staging.1011

  3. Check option (c)

    Not this one. Quality Decision follows the second Cobot Handling step, after the laser. Staging leads to Laser Engraving.10

  4. Check option (d)

    Not this one. Receiving is near the start: it comes before the first Cobot Handling step, which comes before Staging.10

q-s02-n-02 In this project's design, S4 has just sent "all clear and ready" and S3 holds one card. What does S2 do next?
  1. Check option (a)

    Correct. Right. S2 drains buffered workpieces from S3 to S4 once S4 gives its all-clear.37

  2. Check option (b)

    Not this one. S2's route goes through S3: it moves parts on to S4 from S3, so the staged card is the one that goes.1537

  3. Check option (c)

    Not this one. On the order's normal path no person approves each move: once S4 signals all clear, the design has S2 move the card from S3 to S4 itself.3740

q-s02-n-03 Which of IntelliMake's sub-levels is "act with human approval"?
  1. Check option (a)

    Correct. Right. At 5D the machine can act, but only after a specific authorization, and the human keeps final authority.58

  2. Check option (b)

    Not this one. 5E acts within guardrails without approval for each action; a person supervises and handles exceptions.59

  3. Check option (c)

    Not this one. 5C only recommends an action. The human keeps the decision, and the machine does not act.57

q-s02-n-04Safety Camera C1 watches the receiving area where S2 picks. You need to clear a jammed card there. Is the camera a reason to reach in while S2 is running?
  1. Check option (a)

    Correct. Right. This project's advice is not to treat S11 or the cameras as a safeguard, and UFACTORY says nobody should be in the working area while the arm operates.4236

  2. Check option (b)

    Not this one. Camera C1 monitors receiving, and watching is not stopping. Do not treat the cameras as a safeguard.3242

  3. Check option (c)

    Not this one. S11 is described as monitoring. Do not rely on it to stop the arm or to protect you.3542

q-s02-n-05 In this project's design, S2's agent is running an order when a card is not where the order expects it. What does the agent do?
  1. Check option (a)

    Correct. Right. On the order's normal path the agent moves the arm itself, with no person approving each move. Off that path it reports instead of fixing, and a person decides.4041

  2. Check option (b)

    Not this one. Off the normal path the agent does not correct the problem itself: it pauses, reports with a recommendation, and a person decides.4041

  3. Check option (c)

    Not this one. On the normal path no person approves each move: the agent moves the arm itself. A person decides only what happens off the path.40

  4. Check option (d)

    Not this one. The agent is designed to run the order and move the arm itself on the normal path. It is more than an observer.40

Open questions in this section

3Intermediate

Placement Decisions and What They Depend On

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 walk through the arm's route and placement decisions one step at a time, work out what the arm would need to know to make them, and see where in the cell that information could come from. It is for someone who will set up, program or maintain the cell.

The Route, Step by Step

  1. S2's route for a part is S1 to S3, then S3 to S4. No part goes from S1 straight to S415.
  2. A card is ready at S1: S2 arranges it on S3, in the area for its color, stacked on the cards already there1314.
  3. A part is defective: it goes to S3's defects area1617. Defects found on the xArm 6 side do not come to this area24.

What S2 Must Know to Arrange the Cards

  • To put a card on the right stack, S2 has to know the card's color and which area of S3 holds that color's stack. Incoming orders will carry the parameters of the cards72, but no source names them as S2's inputs; this platform infers that S2 needs them from the task73.
  • It also has to know how full that stack is against a stack limit. The limit is not documented, so a program can only hold a placeholder for it73.
  • To send a card to the defects area instead, S2 needs a way to judge it defective. Its own camera, the one on the arm itself, may possibly check material so that defective material is not used732726.

This project's simulation and agent design, not the physical cell

The Placement Decisions in This Project's Design

  1. S4 signals "all clear and ready" while cards wait on S3: S2 moves one from S3 to S437.
  2. S3 has no room and S4 is busy: S2 watches S4, and once S4 is available it sends a card from S3 to S4. That frees room on S3, so S2 can take material from S1 again48.
  3. The design names only one input signal for these moves: S4's "all clear and ready"38.

Who Decides

  • On the order's normal path, the agent is designed to make these moves itself, with no person approving each one40.
  • A step does not complete as the order expects: the agent pauses the arm and reports the issue with recommended actions, rather than correcting it itself, and a person decides what happens next4140.

Where That Information Could Come From

  • IntelliMake's 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 hub74.
  • This platform assumes Camera C1's view covers the S1 area S2 picks from, so the camera could confirm that material is there75.
  • None of the cell's numbered cameras, Camera C1 included, had been set up as of 2026-10-1234.
  • S2 has a camera of its own, on the arm itself. It is not one of the cell's numbered cameras, such as Camera C1 and Camera C2: the arm's camera and those cameras are not related263233. The arm is to use it to select the correct material to fulfill an order, and possibly to check that material so that defective material is not used27.
  • S4 is not S2's alone. Both arms work there23, and S6 is the one that picks up the finished product2330.
  • This platform infers that the cameras, Camera C1 included, feed S11's monitoring layer46. Monitoring a hazard is not the same as stopping it.

Treat Monitoring as Monitoring

This project's simulation and agent design, not the physical cell

  • This project's advice: neither you nor the S2 agent should rely on S11 or the cameras to stop motion or protect people42.

Check Yourself

Answer, then check. Each option has its own feedback, and nothing is scored.

q-s02-i-01 In this project's design, S3 has no room for the next card, S4 is busy, and a card is waiting at S1. What does S2 do?
  1. Check option (a)

    Correct. Right. Freeing room on S3 is what lets S2 take material from S1 again.48

  2. Check option (b)

    Not this one. The defects area is for defective parts, kept apart from the staged material. A good card does not go there.16

  3. Check option (c)

    Not this one. S2's route goes through S3 first, and S4 is busy. S2 must wait for S4 to become available.1548

q-s02-i-02 S2 is about to arrange a card from S1 on S3. Which inputs does it need, and why are they classed Inferred?
  1. Check option (a)

    Correct. Right. They follow from the task: same-color cards stacked in their own area. The stack limit itself is not documented, so a program can only hold a placeholder.731314

  2. Check option (b)

    Not this one. In this project's design that signal starts each move from S3 to S4. It says nothing about a card's color or its stack on S3.3873

  3. Check option (c)

    Not this one. No source gives a stack limit. S2 still has to know how full a stack is, against a limit a program can only hold as a placeholder.73

q-s02-i-03Safety A colleague proposes letting S2 run while people load S1 by hand, because S11 watches for safety and Camera C1 covers receiving. What is the right response?
  1. Check option (a)

    Correct. Right. This project's advice is that neither people nor the S2 agent rely on S11 or the cameras to stop motion or protect people. Camera C1's view of S1 is Assumed.4275

  2. Check option (b)

    Not this one. S11's part in safety is monitoring. The word "safety" in the diagram does not make it a safeguard, so do not rely on it to stop S2.3542

  3. Check option (c)

    Not this one. Even then the cameras would be monitoring, not a safeguard. The S2 agent must not rely on them to stop motion or protect people.4274

Open questions in this section

4Expert

Why Two Arms, and What S2's Agent May Decide

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 build the case for two arms using only what the records support, mark which part of it is an assumption, and read IntelliMake's own level definitions against what the arm's agent is expected to do. It is for someone who designs, integrates or changes the cell.

The Case for Two Arms, Built from the Records

  • IntelliMake's reason. IntelliMake says the cell uses several arms so that each does task-specific work, and that more arms could be added76.
  • Overlap. The gift flow has two separate Cobot Handling steps, one before staging and the laser and one after, assigned to S2 and S61011.
  • With two arms, loading new material and unloading finished parts can happen at the same time. One arm would have to do both in series. This platform infers that much, and no more31.
  • 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 product2331.
  • What decides the gain. How much the overlap helps depends on the cycle times of S2's moves and of the laser step, and the laser step may be the real bottleneck. This platform infers that, too31.
  • 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 S677. 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 it78.
  • UFACTORY publishes 850 mm reach for the 850 and 700 mm for its xArm 5/6/7 line79.
  • S6 serves both flows. In the future 3D-printed flow S6 also carries printed parts from the printer to the laser, so it serves both production flows45.

Intelligence, Authority, Autonomy

  • IntelliMake separates three questions: does the machine know what should be done, is it allowed to do it, and can it keep going and adapting without repeated human help? True autonomous manufacturing needs the right combination of all three80.
  • Agentic automation, in IntelliMake's framing, gives the machine a goal, situational awareness, reasoning, tools, and the authority to decide what should be done61.

Does a Rules Table Make S2 Level Five?

  • Level 1 is hard-coded logic, and level 3 selects among predefined modes5052. Sub-level 5E needs the machine to make certain decisions itself within safety and process limits59.
  • So this platform infers that a placement policy fixed rules alone could carry out sits at levels 1–3, not level 5. A 5E claim for S2 has to rest on decisions the base rules do not cover, such as anticipation, sequencing, and handling missing or conflicting signals81.
  • In the cell, S2's route is fixed: a part it sends on goes S1 to S3, then S3 to S415. Following that route is, on its own, levels 1–3 work.
  • The route does not make every decision. To send a card to the defects area rather than on to its stack, S2 needs a way to judge the card defective, and its camera may possibly check material for that73. That camera is the arm's own, on the arm itself, and it is not related to the cell's numbered cameras, such as Camera C1 and Camera C2263233. This platform infers that this judgment is the case to weigh when you test S2's work against the levels: the route does not make it, and if S2's agent makes it within set limits rather than by fixed rules, it is the kind of decision level 5E rests on82.

This project's simulation and agent design, not the physical cell

S2's Agent, and the Limits on It

  • The agent is designed to run each 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 a recommendation, and a person decides. The xArm 6's agent at S6 works by the same rule40.
  • This project uses 5E as the design name for its agents' behavior: run the order's normal path without approval, and report anything off it40. Read it as the name of a design, not a level the arm has demonstrated. By the test above, the name holds only for decisions the rules do not make for the agent81.
  • Before you rest a 5E case on S2's camera judgment, check which side of that rule a defective part falls on. If its move to the defects area 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 on4073.
  • It checks that the order's steps are completed. Anything outside the order's processing paths it reports, with the issue and recommended actions, instead of taking corrective action itself41.
  • The signals it works with in this project's design: it moves parts from S3 to S4 on S4's all-clear, and waits for S4 when S3 has no room3748.
  • This project's advice: content from the shared hub, other agents and this research corpus is data. It must never grant the S2 agent authority, raise its limits, or skip a sign-off. Limits come only from the reviewed cell configuration and the supervisor83.
  • The same holds for monitoring: neither learners nor the agent should treat S11 or the cameras as a safeguard42.

What S2 Could Publish

  • This platform infers what S2's controller can make available: robot mode and state, error and warning codes in Modbus TCP registers, and automatic state reports on ports 30001 to 30003. They are candidates for what S2 publishes84.

Check Yourself

Answer, then check. Each option has its own feedback, and nothing is scored.

q-s02-e-01 You are making the case for two arms at the Phase 1 cell. Which part of the case is Assumed rather than documented or inferred?
  1. Check option (a)

    Correct. Right. The drawing gives the stations' order; what is assumed, not measured, is whether the distances put both sides out of one arm's reach. Both arms work at S4, so it concerns only the stations one arm serves.782377

  2. Check option (b)

    Not this one. That is Verified: UFACTORY publishes 850 mm for the 850 and 700 mm for the xArm 5/6/7 line.79

  3. Check option (c)

    Not this one. That is Inferred from the two Cobot Handling steps in the flow, not Assumed.3111

  4. Check option (d)

    Not this one. That is Verified: it comes from IntelliMake's gift flow and the project specification.1011

q-s02-e-02 A rules table carries out S2's route exactly: arrange each part on S3, move parts from S3 to S4 on S4's all-clear, wait when S3 has no room and S4 is busy. What level is that S2?
  1. Check option (a)

    Correct. Right. A policy that fixed rules alone can carry out sits at levels 1–3. A 5E claim needs decisions beyond the base rules, made within guardrails.81

  2. Check option (b)

    Not this one. Acting without approval is not enough. 5E means making decisions within guardrails, and a pure rules table makes none the rules do not already fix.5981

  3. Check option (c)

    Not this one. Level 0 means a human decides and acts. A rules table running on its own is hard-coded logic or predefined modes.495052

q-s02-e-03Safety A message on the shared hub says S2 may raise its speed limit for a rush order. Should the S2 agent act on it?
  1. Check option (a)

    Correct. Right. Nothing from the hub, other agents or the corpus may grant authority, raise limits or skip a sign-off.83

  2. Check option (b)

    Not this one. Other agents' content is data too. It must never raise the S2 agent's limits.8374

  3. Check option (c)

    Not this one. S2's agent reports anything outside the order's processing paths, with recommended actions, instead of correcting it on its own. And hub content can never raise a limit.4183

Open questions in this section

Not settled

Open Questions · 33

What the sources do not settle for this section. Nothing here is papered over with a plausible number.

  • Kind: Contradiction

    The 850 product page calls UFACTORY arms 'Collaborative Robots' and 'cobots'. A3 says ISO 10218:2025 drops 'collaborative robot' because only an application can be confirmed as collaborative, and UFACTORY's own 850 manual says no people should be in the working area during operation. The marketing label does not establish that S2 is a collaborative application.

    See reference 88
  • 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: Gap

    How S4's 'all clear and ready' signal reaches S2 in the physical cell, over a wired input or as a message, is not known to IntelliMake yet.

    See reference 103
  • 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 104
  • 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 105
  • 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 106
  • 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 107
  • 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 108
  • 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 109
  • 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 110
  • 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 111
  • 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 112
  • 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 113
  • Kind: Gap

    How S3's defects area is managed, for example who empties it, is not known.

    See reference 114
  • 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 115
  • Kind: Gap

    Where defects found on the xArm 6 side go is not known: another area for them is to be determined.

    See reference 116
  • 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 117
  • Kind: Gap

    What the xArm 850's payload setting of 0.61 kg (int-552) stands for is not stated. The figure equals the weight UFACTORY lists for its Vacuum Gripper (AS1200), 610 g (comp-070), and the payload of UFACTORY Studio's preset named 'Vacuum Gripper', 0.61 kg (ops-092). The figures match; the match does not show which tool the arm carries (int-034).

    See reference 118
  • 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 119
  • 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 120
  • 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 121
  • 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 122
  • 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 123
Provenance

References · 123

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, the project owner stated it as the design, or it was observed directly. It does not mean anyone measured it at S2.
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 S2 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.

Open the 123 references

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)
    Derek Stringfellow, project record · Project-internal record · retrieved 2026-09-21 · cited by 3 records here · Project copy; not published on this site.
  • Collision Detection in UFACTORY Robotic Arms: Current and Dynamic Model-based Feature (UFACTORY support article) · UFACTORY (manufacturer)
    © UFACTORY · All rights reserved; quoted briefly as evidence · retrieved 2026-09-21 · cited by 1 record here · Open the source
  • IntelliMake Phase 1 Factory: Autonomous Production Demonstrator (infographic) · IntelliMake.org (IntelliMake)
    © IntelliMake.org. Used with permission; redrawn for this platform. · Cleared for use by its owner · retrieved 2026-09-21 · cited by 29 records here · Project copy; not published on this site.
  • Level 5. Agentic Evolution: A Spectrum of Increasing Decision Authority (infographic) · IntelliMake.org (IntelliMake)
    © IntelliMake.org. Used with permission; redrawn for this platform. · Cleared for use by its owner · retrieved 2026-09-21 · cited by 10 records here · Project copy; not published on this site.
  • Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow (project owner)
    Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04 · cited by 44 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 10 records here · Project copy; not published on this site.
  • Phase 1 layout drawing, sent by Derek (2026-09-30) · Derek Stringfellow (project owner)
    Derek Stringfellow, project record · Project-internal record · retrieved 2026-09-30 · cited by 3 records here · Project copy; not published on this site.
  • Phase 1 measurements table, sent by Derek with the layout drawing (2026-09-30) · Derek Stringfellow (project owner)
    Derek Stringfellow, project record · Project-internal record · retrieved 2026-09-30 · cited by 4 records here · Project copy; not published on this site.
  • The Progression Cheat Sheet: 6 stages of manufacturing automation · IntelliMake.org (IntelliMake)
    © IntelliMake.org. Used with permission; redrawn for this platform. · Cleared for use by its owner · retrieved 2026-09-21 · cited by 7 records here · Project copy; not published on this site.
  • The Two-Dimensional Digital Twin Framework (class slide) · IntelliMake.org (IntelliMake)
    © IntelliMake.org. Used with permission; redrawn for this platform. · Cleared for use by its owner · retrieved 2026-10-08 · cited by 9 records here · Project copy; not published on this site.
  • UFACTORY 850 Hardware Manual (online), 1. Safety · UFACTORY (manufacturer)
    © UFACTORY · All rights reserved; quoted briefly as evidence · retrieved 2026-09-21 · cited by 3 records here · Open the source
  • UFACTORY 850 Hardware Manual (online), 2. Hardware Installation · UFACTORY (manufacturer)
    © UFACTORY · All rights reserved; quoted briefly as evidence · retrieved 2026-09-21 · cited by 1 record here · Open the source
  • UFACTORY 850 Hardware Manual (online), 3. Controller Electrical Interface · UFACTORY (manufacturer)
    © UFACTORY · All rights reserved; quoted briefly as evidence · retrieved 2026-09-21 · cited by 1 record here · Open the source
  • UFACTORY 850 Hardware Manual (online), 8. Technical Specifications · UFACTORY (manufacturer)
    © UFACTORY · All rights reserved; quoted briefly as evidence · retrieved 2026-09-21 · cited by 1 record here · Open the source
  • UFACTORY 850 product page · UFACTORY (manufacturer)
    © UFACTORY · All rights reserved; quoted briefly as evidence · retrieved 2026-09-21 · cited by 4 records here · Open the source
  • UFACTORY 850 User Manual V2.3.0 (PDF, older edition) · UFACTORY (manufacturer)
    © UFACTORY · All rights reserved; quoted briefly as evidence · retrieved 2026-09-21 · cited by 1 record here · Open the source
  • UFACTORY ModbusTCP User Instructions (xArm-Python-SDK doc/UF_ModbusTCP_Manual.md) · UFACTORY (manufacturer)
    © UFACTORY Inc., xArm-Developer/xArm-Python-SDK, BSD 3-Clause License · BSD-3-Clause · retrieved 2026-09-21 · cited by 1 record here · Open the source
  • UFACTORY Studio User Manual (online), 2. Glossary · UFACTORY (manufacturer)
    © UFACTORY · All rights reserved; quoted briefly as evidence · retrieved 2026-09-21 · cited by 1 record here · Open the source
  • UFACTORY Studio User Manual (online), 7. Settings · UFACTORY (manufacturer)
    © UFACTORY · All rights reserved; quoted briefly as evidence · retrieved 2026-10-13 · cited by 1 record here · Open the source
  • UFACTORY Studio's Device Info page for the xArm 850, screenshot (2026-10-16) · Derek Stringfellow (project owner)
    Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-16 · cited by 1 record here · Project copy; not published on this site.
  • UFACTORY USA 850 product page · UFACTORY USA (manufacturer)
    © UFACTORY USA · All rights reserved; quoted briefly as evidence · retrieved 2026-09-21 · cited by 1 record here · Open the source
  • Updated ISO 10218: Answers to Frequently Asked Questions (FAQs) (A3 blog, 03/20/2025; Wayback Machine snapshot 2025-10-06) · Association for Advancing Automation (A3) (secondary)
    © Association for Advancing Automation (A3) · All rights reserved; quoted briefly as evidence · retrieved 2026-09-21 · cited by 1 record here · Open the source
  • xArm 850 S2 Project: Open Questions for IntelliMake, Batch 01 responses · IntelliMake.org (IntelliMake)
    © IntelliMake.org. Used with permission. · Cleared for use by its owner · retrieved 2026-09-29 · cited by 8 records here · Project copy; not published on this site.
  • xArm-Python-SDK source, xarm/core/config/x_config.py · UFACTORY (manufacturer)
    © UFACTORY Inc., xArm-Developer/xArm-Python-SDK, BSD 3-Clause License · BSD-3-Clause · retrieved 2026-09-21 · cited by 1 record here · Open the source

IntelliMake diagrams are redrawn as native figures, © IntelliMake.org. UFACTORY does not endorse this platform.

All sources and attribution