S4, the Laser Engraver Conveyor, transfers workpieces through the laser processing area.
Evidence · 1 citation
Transfers workplaces through the laser processing area.
IntelliMake Phase 1 Factory: Autonomous Production Demonstrator (infographic) · IntelliMake.org · S4 station description (the diagram prints 'workplaces'; read as workpieces)
In IntelliMake's Phase 1 layout, S6 (the UFactory xArm 6 cobot) is drawn directly after S5, the xTool F1 Ultra laser engraver, with a flow arrow from S5 into S6. S5 performs personalization through laser engraving or marking, so in the drawing the laser station is S6's immediate upstream neighbor.
Evidence · 2 citations
S5 xTool F1 Ultra Laser Engraver Performs personalization through laser engraving or marking.
IntelliMake Phase 1 Factory: Autonomous Production Demonstrator (infographic) · IntelliMake.org · S5 station label and description
S8, the Outbound Conveyor, moves completed products toward final packing and shipment. It is one of the stations after S6 in IntelliMake's layout; the diagram labels it both 'QC Hold' and 'Shipping' (see int-038).
Evidence · 2 citations
S8 Outbound Conveyor / QC Hold Moves completed products toward final packing and shipment.
IntelliMake Phase 1 Factory: Autonomous Production Demonstrator (infographic) · IntelliMake.org · Upper S8 panel, label and description
S10, Packing / Labeling, carries out final product preparation, identification, labeling and packing. It is the last station in IntelliMake's layout, and 'Packing & Labeling' is the last step of the initial gift production flow.
Evidence · 2 citations
S10 Packing / Labeling Final product preparation, identification, labeling, and packing.
IntelliMake Phase 1 Factory: Autonomous Production Demonstrator (infographic) · IntelliMake.org · S10 label and description
IntelliMake Phase 1 Factory: Autonomous Production Demonstrator (infographic) · IntelliMake.org · Initial Personalized Gift Production Flow banner, last steps
The project specification places S2 at the first Cobot Handling step of IntelliMake's gift flow, between Receiving and Staging; the second Cobot Handling step, after laser engraving, is S6's. IntelliMake's layout draws the stations in the matching order (see observation).
Evidence · 3 citations
Where it sits in the Initial Personalized Gift Production Flow (Receiving → **Cobot Handling** → Staging → Laser Engraving → …)
The cell uses two collaborative arms: the xArm 850 at S2 is the upstream arm that takes incoming material off receiving toward personalization, and the xArm 6 at S6 is the downstream arm that handles parts after processing.
Evidence · 2 citations
The xArm 850 at S2 is the **upstream** arm: it takes incoming material off receiving and hands it off toward personalization
S3 can serve two purposes: staging material in one area, and placing defects in another. That would be one point of quality assurance and quality control (QA/QC) in the cell.
Evidence · 1 citation
S3 can serve two purposes, staging material in one area, and placing defects in another. This would be one point of QAQC.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S145 (2026-10-07)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
In a Phase 1 layout drawing, S2, S4, S6 and S8 stand in one row, in that order, so S4 lies between the two arms' stations. S3 is beside S2 and S7 beside S6, on the same side of the row; S1 is beside S2 on the other side.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Evidence · 7 citations
S2
Phase 1 layout drawing, sent by Derek (2026-09-30) · Derek Stringfellow · The drawing's labels
Derek Stringfellow, project record · Project-internal record · retrieved 2026-09-30
Project copy; not published on this site.
S4
Phase 1 layout drawing, sent by Derek (2026-09-30) · Derek Stringfellow · The drawing's labels
Derek Stringfellow, project record · Project-internal record · retrieved 2026-09-30
Project copy; not published on this site.
S6
Phase 1 layout drawing, sent by Derek (2026-09-30) · Derek Stringfellow · The drawing's labels
Derek Stringfellow, project record · Project-internal record · retrieved 2026-09-30
Project copy; not published on this site.
S8
Phase 1 layout drawing, sent by Derek (2026-09-30) · Derek Stringfellow · The drawing's labels
Derek Stringfellow, project record · Project-internal record · retrieved 2026-09-30
Project copy; not published on this site.
S3
Phase 1 layout drawing, sent by Derek (2026-09-30) · Derek Stringfellow · The drawing's labels
Derek Stringfellow, project record · Project-internal record · retrieved 2026-09-30
Project copy; not published on this site.
S1
Phase 1 layout drawing, sent by Derek (2026-09-30) · Derek Stringfellow · The drawing's labels
Derek Stringfellow, project record · Project-internal record · retrieved 2026-09-30
Project copy; not published on this site.
S7 Repurposed Defect Table - Proposed location for Phase 1. Known as S7 3D Printer
Phase 1 layout drawing, sent by Derek (2026-09-30) · Derek Stringfellow · The box drawn above S6
Derek Stringfellow, project record · Project-internal record · retrieved 2026-09-30
Defects found on the xArm 6 side do not end up in S3's defects area at this time. The plan is to add another area for them ('another area or something'), which is to be determined (int-539).
Evidence · 4 citations
whether S154's first answer means the xArm 6 side's defects no longer go to S3's defects area
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S155 (2026-10-07), question (1) as given in the bracket
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
xArm 6 defects does not end up in S3 at this time
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S155 (2026-10-07), first answer
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
we plan on adding another area or something
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S155 (2026-10-07), first answer, continued
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
sArm 6 does not reach s3, another area for defects has to be determined. It is currently unknown.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S154 (2026-10-07), first line of the answer
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
The planned outcome for the IntelliMake 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 other.
Evidence · 2 citations
The goal is a working autonomous production run of the system accepting orders and printing then sending over for shipping, all done by the agents interacting with each other.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S47
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
The IntelliMake cell's planned outcome; 'printing' means personalising the part (engraving now, 3D printing later).
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S50, first answer (option text chosen)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
The factory's initial production scenario is personalized laser-engraved gifts; it is to expand in the future to additively manufactured (3D-printed) custom parts that are laser marked or engraved.
Evidence · 1 citation
Initial production scenario focuses on personalized laser-engraved gifts, expanding in the future to additively manufactured custom parts (laser marked/engraved).
The cell's initial orders are currently understood to be more geared to simple custom printed cards, where 'printed' means engraved by the cell's laser: there is no separate printing step. Depending upon progress, more complex orders could be taken on.
Evidence · 3 citations
initial orders are more geared to simple custom printed cards, however, depending upon progress, more complex orders could be entertained.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S145 (2026-10-07)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Laser-engraved
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S149 (2026-10-07), answer (3)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
"Printed" means engraved by the S4 laser; there is no separate printing step.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S149 (2026-10-07), the option answer (3) matches (the option's words)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
S5, the xTool F1 Ultra laser engraver, and the S4 conveyor are interconnected systems. The Phase 1 layout drawing has a box for S4 and none of its own for S5.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Evidence · 4 citations
S4 conveye and engraver are interconnected systems.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S97, first sentence (unchanged by S172; rule 7, the earlier citation kept)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Yes, it is S5
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S102, answer (2), to whether the engraver travelling along the S4 conveyor is the course's S5, the xTool F1 Ultra
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
S5 xTool F1 Ultra Laser Engraver
IntelliMake Phase 1 Factory: Autonomous Production Demonstrator (infographic) · IntelliMake.org · S5 station label
The S5 laser engraver stays in one place, and the S4 conveyor moves the product from one location to another.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Evidence · 2 citations
S4 engrave will remain stationary and the conveyer swill be the means of moving the product from one location to another.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S172 (2026-10-09), IntelliMake Notes
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Yes, it is S5
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S102, answer (2), to whether the engraver travelling along the S4 conveyor is the course's S5, the xTool F1 Ultra
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Reasoning:Verified as a statement of the design, on how the conveyor can run. No reversal of the belt has been observed or recorded. What commands the belt and chooses its direction is not known. 'mode' is read as 'move', the project's reading of a typing slip; the sentence answers whether the belt runs one way only.
Evidence · 1 citation
The conveyer can mode in either direction.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S176 (2026-10-11), on the order along the S4 conveyor
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
The S4 conveyor is part of S4, so S6 picks up from S4, however the item's final placement is met.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Evidence · 1 citation
The Conveyer is part of S4 so S6 picks up from S4 regardless of how the item's final placement is met.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S119, to whether S6 still picks up at S4 or the conveyor carries the product to S6
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
No camera is installed on the xArm 6 at S6 as of 2026-10-12. Whether there will be one, or whether the xArm 6 will use location only, is unknown (int-544).
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Reasoning:Verified as a statement of the lab's state on the date given (S182, 2026-10-12); no inspection is recorded here.
Evidence · 2 citations
The xArm 6's camera: is it installed, is it on the arm, and is it also separate from C1 and C2?
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S182 (2026-10-12), question (3) as given in the bracket
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Currently it is not installed and it is unknown if there will be one or if x6 will use location only.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S182 (2026-10-12), answer 3
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
UFACTORY describes the xArm 6 as designed for manufacturing and assembly-line automation, including more complex actions such as load and unload, and pick and place. S6's IntelliMake role, handling parts after processing and routing them onward, is a task of that kind.
Why we infer this:UFACTORY's article names load and unload and pick and place among the xArm 6's intended tasks; IntelliMake's S6 description (handling and routing parts) is a pick-and-place task. The match is this project's reading; neither source refers to the other.
Evidence · 2 citations
The 6 axis robot arm is designed for manufacturing and assembly line automation, including more complex actions, for example, load and unload, pick and place
The difference between UFACTORY xArm5, UFACTORY xArm6 and UFACTORY xArm7 (Help Center article) · UFACTORY · Section 1, 'Main difference in brief', xArm 6 entry
With two arms, loading incoming material (S2) and unloading and routing finished parts (S6) can happen at the same time. With one arm, both handling steps for every part would run one after the other on the same arm. The two steps meet at S4, where both arms work (int-062); how the arms share S4 is not documented. How much two arms help throughput is unknown, because no cycle times are documented (int-033), and the laser step may be the real bottleneck.
Why we infer this:Verified: the gift flow has two separate Cobot Handling steps, one before staging and laser engraving and one after (int-028), assigned to S2 and S6 (int-029). One arm would have to perform both in series; two arms let them overlap. This shows the steps can overlap, not that one arm would be the bottleneck: that depends on cycle times, which no available source documents (int-033). Verified: both arms work at S4, one placing the material and the other picking up the finished product (int-062), so the two handling steps meet at one station; no source says how the arms share it (int-612).
None of the cell's numbered cameras had been set up as of 2026-10-12.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Reasoning:Stated twice, in answer to questions. Asked about the whole-cell view's S10, C1, C2 and S11 (S138, 2026-10-05): 'Camera placement is currently unknown and not set up in the lab.' Asked whether 'Cx' includes a C3 or only C1 and C2 (S182, 2026-10-12): 'Cx includes all of them. No cameras have been set up yet.' Whether 'No cameras' there means every camera or the Cx cameras only, the cell's numbered cameras are inside it, so this statement does not depend on that reading and takes no position on it. S183 (2026-10-13) says the Cx cameras are the station cameras and not the xArm 850's arm camera; it does not say which cameras 'No cameras' covered. The xArm 850's own camera is not this record's subject: int-114 stands on S172 and S181. S182's answer was given to a question about 'Cx' and does not name the arm's camera; whether its 'No cameras' reaches that camera is the reading this record takes no position on. Verified as a statement of the lab's state on the dates given; no inspection is recorded here.
Evidence · 5 citations
'Cx': does that include a C3, or only C1 and C2?
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S182 (2026-10-12), question (4) as given in the bracket
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Cx includes all of them. No cameras have been set up yet.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S182 (2026-10-12), answer 4
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Camera placement is currently unknown and not set up in the lab.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S138 (2026-10-05), answer 10a, to a question about the whole-cell view's S10, C1, C2 and S11
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
I confirm that the Cx are for all the station cameras
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S183 (2026-10-13), second clause, its beginning
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
and not the x850 arm camera.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S183 (2026-10-13), second clause, its end; the words between this and its beginning, an example he gave and hedged, are not quoted
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
The xArm manual says that while the device is running, an arm that seems to have stopped may be waiting for a signal and about to act, and that it should be considered to be in action even in that state.
Evidence · 1 citation
Quote not shown (over 40 words). See the source at: 1.4 Personnel Safety, CAUTION [series text: names no single model].
UFACTORY xArm Hardware Manual (online), 1. Safety · UFACTORY · 1.4 Personnel Safety, CAUTION [series text: names no single model]
Kind: RecommendationAwaiting cell accessThis project's simulation and agent design, not the physical cellProject design, not the physical cellsafety-599
Project advice
Until the S6 emergency stops, guarding, Control Box position and risk assessment are confirmed at the cell, act as though none of them exists: stay out of the xArm 6's working area while it runs, and do not rely on a safeguard nobody has confirmed.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
This is advice from this project, based on: safety-586 Gap, awaiting cell accesssafety-587 Gap, awaiting cell accesssafety-588 Gap, awaiting cell accesssafety-589 Gap, awaiting cell accesssafety-511 Verified
Why:The manual says no people should be in the working area during operation, and none of the S6 safety provisions it calls for has been confirmed. Assuming they exist would put people at risk if they do not.
S3, the Inbound Staging Table, provides temporary storage and buffering for incoming workpieces.
Evidence · 1 citation
Provides temporary storage/buffering for incoming workplaces.
IntelliMake Phase 1 Factory: Autonomous Production Demonstrator (infographic) · IntelliMake.org · S3 station description (the diagram prints 'workplaces'; read as workpieces)
S7, a Prusa 3D printer, is a future production extension that produces customized 3D-printed parts and supports a future hybrid additive-plus-laser workflow.
In IntelliMake's future 3D-printed flow, S6 handles parts coming from S7 (3D printing) and passes them to laser engraving or marking, so S6 serves both production flows.
Evidence · 1 citation
S7 3D Printing → S6 Robot Handling → S4/55 Laser Engraving or Marking
On the xArm 6 side of the cell, material for the 3D printer may come through S4, either as an enhancement or as part of several processes between the engraver and the 3D printer.
Evidence · 1 citation
on the x6 side of the house, it is possible material can come through S4 that is for the 3d printer, either as an enhancement or part of multiple processes between the engraver and the 3d printer.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S145 (2026-10-07)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
A camera on the xArm 6 was to be used to collect the finished product and to check it, deciding whether the product goes to shipping, is a defect, or can be sent back for a redo; the redo route is a future state. That was said when the xArm 6 was expected to have a camera. None is installed, and whether there will be one is unknown (int-543), so whether the xArm 6 will do these things with a camera is not known.
Evidence · 4 citations
The camera on the 6 is used to both collect the finished product as well as perform qaqc on the finished product
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S91 (2026-09-30), what the camera on the xArm 6 is used for, which S182 does not restate; the earlier citation kept (rule 7)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
determine should the product go out for shipping, is considered a defect, and can a product be sent back for a redo - the redo one is a future state at the moment
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S91 (2026-09-30), continued
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Both will have a camera that they will use as part oof their function set
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S90 (2026-09-30); the earlier citation kept (rule 7)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Currently it is not installed and it is unknown if there will be one or if x6 will use location only.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S182 (2026-10-12), answer 3
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
The factory cameras, including C1, feed the S11 IntelliAware monitoring layer.
Why we infer this:The mapping table groups cameras C1–C3 with S11 under AI vision for safety, and the layout draws dotted connectors from the camera icons to S11. The data path itself (protocol, what is sent) is not documented.
Evidence · 1 citation
AI Vision – Safety | Cameras C1–C3 + S11 IntelliAware
IntelliMake Phase 1 Factory: Autonomous Production Demonstrator (infographic) · IntelliMake.org · HW2 SME topic mapping table
Kind: RecommendationThis project's simulation and agent design, not the physical cellProject design, not the physical cellint-053
Project advice
Until S11's safety function is documented and verified, neither learners nor the S2 agent should treat S11 or the cameras as a safeguard. The S2 agent must not rely on them to stop motion or to protect people.
This is advice from this project, based on: int-024 Verifiedint-050 Gap, awaiting cell access
Why:S11 is described only as monitoring that includes safety (int-024). Nothing establishes a safety rating, stop authority or response time (int-050). Treating an unrated monitoring system as a safeguard is the failure the Q3 disposition warns against: an Assumed safeguard mistaken for a confirmed one.
IntelliMake automation level 3 is 'Flexible': the conveyor action is 'Selects predefined modes', and the primary decision maker is the automation system.
IntelliMake automation level 4 is 'Intelligent/Adaptive': the conveyor action is 'Algorithm-driven adjustments', and the primary decision maker is the algorithm.
IntelliMake automation level 5 is 'Agentic/Autonomous': the conveyor action is 'Objective-driven execution', and the primary decision maker is the AI agent.
Evidence · 1 citation
Level 5 | Agentic/Autonomous | Objective-driven execution | AI Agent
The Progression Cheat Sheet: 6 stages of manufacturing automation · IntelliMake.org · Level 5 row
IntelliMake sub-level 5B, 'Understand & Determine': it interprets information, forming an interpretation of the operating situation from observed data.
Evidence · 1 citation
Forms an interpretation of the operating situation based on observed data.
Level 5. Agentic Evolution: A Spectrum of Increasing Decision Authority (infographic) · IntelliMake.org · Panel #5B
IntelliMake sub-level 5C, 'Recommend': it advises the human operator, determining an appropriate action and recommending it while the human keeps decision authority (human in the loop).
Evidence · 1 citation
Determine an appropriate action and recommend it, but human retains decision authority.
Level 5. Agentic Evolution: A Spectrum of Increasing Decision Authority (infographic) · IntelliMake.org · Panel #5C
IntelliMake sub-level 5D, 'Act with Human Approval': it authorizes machine action: the machine can act, but only after specific authorization, and the human keeps final authority.
Evidence · 1 citation
The machine can act, but only after specific authorization.
Level 5. Agentic Evolution: A Spectrum of Increasing Decision Authority (infographic) · IntelliMake.org · Panel #5D
IntelliMake sub-level 5E, 'Limited Autonomous Control': it operates within guardrails, with permission to make certain decisions independently within established safety and process limits and then monitor the outcome (human on the loop: supervision and exception handling).
Evidence · 1 citation
Permission to make certain decisions independently within established safety and process limits.
Level 5. Agentic Evolution: A Spectrum of Increasing Decision Authority (infographic) · IntelliMake.org · Panel #5E
IntelliMake sub-level 5F, 'Full Autonomy': it achieves objectives: given objectives rather than instructions, it perceives, understands, decides, acts, observes the result, learns and adapts, and replans.
Evidence · 1 citation
Given objectives, not instructions.
Level 5. Agentic Evolution: A Spectrum of Increasing Decision Authority (infographic) · IntelliMake.org · Panel #5F
IntelliMake frames the shift to agentic automation as follows: traditional automation tells the machine what to do and how, while agentic automation gives it a goal, situational awareness, reasoning capability, tools and the authority to determine what should be done.
Evidence · 1 citation
Agentic automation gives the machine a goal, situational awareness, reasoning capability, tools, and authority to determine what should be done.
Level 5. Agentic Evolution: A Spectrum of Increasing Decision Authority (infographic) · IntelliMake.org · Panel 'The fundamental shift'
IntelliMake's two-dimensional digital twin framework classifies a digital representation along two axes: its physical-digital coupling, which is how deeply the digital and the physical interact, and the scope of the physical world it represents.
Evidence · 3 citations
Classifying digital representations by their connection strength and physical scope.
The Two-Dimensional Digital Twin Framework (class slide) · IntelliMake.org · The slide's subtitle
On its coupling axis the framework names five levels, from the least coupled to the most: Digital Image, Digital Model, Digital Monitor, Digital Guide and Digital Twin.
Evidence · 1 citation
DIGITAL TWIN DIGITAL GUIDE DIGITAL MONITOR DIGITAL MODEL DIGITAL IMAGE
The Two-Dimensional Digital Twin Framework (class slide) · IntelliMake.org · The left column, top to bottom, beside the 'Increasing Coupling' arrow
In the framework, a Digital Twin, the highest level of coupling, has synchronized interaction both ways, from the physical to the digital and from the digital to the physical. Its verb is 'Optimize'.
Evidence · 1 citation
DIGITAL TWIN Optimize Synchronized interaction. Physical ⇄ Digital.
The Two-Dimensional Digital Twin Framework (class slide) · IntelliMake.org · The left column, the Digital Twin row
On its scope axis the framework names three scopes: a part or product (parts, subassemblies, assemblies and products); a machine, cell or line, the production-system level (machines, cells and production lines); and a facility, enterprise or ecosystem (large-scale systems).
Evidence · 3 citations
PART / PRODUCT At the smallest scale: Parts, Subassemblies, Assemblies, Products
The Two-Dimensional Digital Twin Framework (class slide) · IntelliMake.org · Under the horizontal axis, the first scope
Confidence: InferredThis project's simulation and agent design, not the physical cellProject design, not the physical celllvl-025
The record says
On IntelliMake's framework, this site's simulator (Practice in the Simulator) is a simplified Digital Model: its bench page is a machine-level one, and each station page a cell-level one. It simulates the arm's motion against the scene's limits, and no data flows between it and a real arm in either direction.
Why we infer this:Verified: a Digital Model is geometry, physics and simulation (lvl-019), and each level of coupling above it adds a flow of data: from the physical to the digital for a Digital Monitor (lvl-020), from the digital to the physical for a Digital Guide (lvl-021), and both ways for a Digital Twin (lvl-022). That the simulator has had no such flow since it went live on 2026-10-12 (the gate's pushed head, commit e2bd438) is the repository's state, not something a cited source says (corpus/README.md, Records About This Project's Own Simulation, rule 2): the bench and station pages load their scene from the site's own file (the site's learn/_app/operate/operate.js:45), the whole-cell view likewise (whole.js:14); every request these pages make is for one of the site's own files, the scene and the arm's 3D model (learn/_app/3d/arm.js:179, cellview.js:45), and operate.js's header says nothing in it talks to a machine or a server; by this project's design no web page can command real hardware (docs/specs/operate-twin-design-brief.md §2.4). Each page labels its model simplified. So the simulator sits at the Digital Model level: machine scope for the bench, one arm on a table, and cell scope for a station page, the arm at its station among the cell's cabinets and conveyors (lvl-023). This is the project's own reading of where its pages sit; the framework does not name them.
Evidence · 2 citations
DIGITAL MODEL Understand Geometry, physics & simulation (CAD, FEA).
The Two-Dimensional Digital Twin Framework (class slide) · IntelliMake.org · The left column, the Digital Model row
make it our working vocabulary and turn it into teaching content on Operate and Twin pages.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S167 (2026-10-08), how to use the framework
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Confidence: VerifiedThis project's simulation and agent design, not the physical cellProject design, not the physical cellint-527
The record says
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.
Evidence · 2 citations
S6 automation too — The agent work extends to the xArm 6 at S6, not just the 850 at S2.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S43, the option chosen
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
'Both arms are planned to be run by software agents that work with the other stations.'
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S50, second answer (option text chosen)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Confidence: VerifiedThis project's simulation and agent design, not the physical cellProject design, not the physical cellint-095
The record says
Each arm's agent is designed to run the order and report problems. 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. This project names that design level 5E. The same level and the same report-don't-correct rule apply to both arms' agents: the xArm 850's at S2 and the xArm 6's at S6.
Evidence · 5 citations
Runs the order, reports problems
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S148 (2026-10-07), answer (1)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
On the normal path the agent moves the arm by itself, with no person approving each move. Anything off the path: it pauses and reports with a recommendation, and a person decides.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S148 (2026-10-07), the option answer (1) chose (the option's words, not his)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
(This is our current design, called 5E.)
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S148 (2026-10-07), the same option's name for the design (the option's words, not his)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Both arms
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S148 (2026-10-07), answer (2)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
The same level and the same report-don't-correct rule for both agents.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S148 (2026-10-07), the option answer (2) chose (the option's words)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Confidence: VerifiedThis project's simulation and agent design, not the physical cellProject design, not the physical cellint-091
The record says
While an arm works an order, its agent watches that the steps it is supposed to do are completed. Anything that falls outside the order's processing paths, it reports instead of correcting: if an issue arises, it pauses and alerts the person working with the cell, giving the issue and recommended actions. The same rule applies to both arms' agents.
Evidence · 4 citations
the agent is monitoring the arm and making sure the skills that are supposed to be done are being completed, if an issue arises, the agent will pause and alert the human collaborator with the issue and recommended actions.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S145 (2026-10-07)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
the agent observes and reports any deltas that falls outside of the order processing paths and reports the issue, instead of taking direct corrective actions.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S146 (2026-10-07), answer (1)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Both arms
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S148 (2026-10-07), answer (2)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
The same level and the same report-don't-correct rule for both agents.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S148 (2026-10-07), the option answer (2) chose (the option's words)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
The current assumption for the IntelliMake agents is that they do not talk to each other directly: they exchange information, and may collaborate, through a central shared knowledge space (a hub). IntelliMake leadership has not finalized this.
How this would be checked:IntelliMake team leadership's design for the shared knowledge space: its protocol, schema and hosting (open question Q9).
Evidence · 1 citation
The agents will not talk directly to each other, rather will exchange information in a central hub and possibly colloborate in that space. That has not been fully fleshed out by the iIntelliMake team leadership.
Derek Stringfellow, project record · Project-internal record · retrieved 2026-09-21
Project copy; not published on this site.
Kind: RecommendationThis project's simulation and agent design, not the physical cellProject design, not the physical cellsafety-595
Project advice
Deny the S6 agent the SDK calls that change collision sensitivity, collision detection, collision rebound, reduced mode or the safety boundary, or gate them behind human approval.
This is advice from this project, based on: safety-593 Inferredsafety-509 Verifiedsafety-558 Verified
Why:UFACTORY says a modified safety configuration makes a new system needing updated risk assessments, and its own SDK notes say not to use set_collision_sensitivity unless required. An agent that can change these settings could invalidate the risk assessment without anyone noticing.
The xArm manual says the Control Box must be placed outside the arm's working range so that the emergency stop button can be pressed in an emergency.
Evidence · 1 citation
The Control Box must be placed outside the working range of the robotic arm to ensure the emergency stop button can be pressed once an emergency occurs.
UFACTORY xArm Hardware Manual (online), 1. Safety · UFACTORY · 1.3, CAUTION list [series text: names no single model]
The xArm manual says the controller should be placed at a height of 0.6 m to 1.5 m.
Evidence · 1 citation
The controller should be placed at a height of 0.6m to 1.5m.
UFACTORY xArm Hardware Manual (online), 7. Production Information · UFACTORY · 7.6 Controller Placement Height (manual for the xArm series; this passage names no single model)
Both arms work at S4 (int-062), but the stations only one arm serves lie on opposite sides of it: receiving and staging (S1 and S3), served by S2, and the stations after S6, such as S8, where S6 sends parts for shipping by default. So a single arm probably could not reach both receiving and staging and the stations after S6.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
How this would be checked:Measure the as-built positions of S1, S3, S4, S6 and S8 relative to each arm's base and compare them with the published reach of each arm.
Evidence · 5 citations
S2 UFactory xArm 850 Cobot
IntelliMake Phase 1 Factory: Autonomous Production Demonstrator (infographic) · IntelliMake.org · S2 station label
UFACTORY publishes a longer reach for the 850 (850 mm, maximum payload 5 kg) than for its xArm 5/6/7 line (700 mm, with payloads from 3 kg to 5 kg across the line). No xArm 6-specific figure is cited here, and no source says whether reach decided which arm went to S2.
IntelliMake distinguishes intelligence (does the machine know what should be done?), authority (is the machine allowed to do it?) and autonomy (can it keep operating and adapting without repeated human intervention?), and holds that true autonomous manufacturing needs the right combination of all three.
Evidence · 1 citation
True autonomous manufacturing requires the appropriate combination of all three.
Level 5. Agentic Evolution: A Spectrum of Increasing Decision Authority (infographic) · IntelliMake.org · Panel 'Understanding the differences'
A placement policy that fixed rules alone could carry out would sit at IntelliMake levels 1–3, not level 5. S2's level 5E claim therefore depends on decisions the rules do not cover, made within guardrails.
Why we infer this:Level 1 is hard-coded logic and level 3 selects among predefined modes (lvl-002, lvl-004). If S2's behavior were fully specified by its route and rules (int-081, int-015, int-016), it would be level 3 at most. Level 5E requires the machine to make decisions within guardrails (lvl-011), so the 5E claim must rest on decisions beyond the base rules, such as anticipation, sequencing, and handling missing or conflicting signals.
When S6's work is tested against IntelliMake's levels, the case to weigh is the judgment of each finished product: whether it goes to shipping, is a defect, or, in future, can be sent back for a redo. Following the cell's fixed route does not make that decision; if S6's agent makes it within set limits rather than by fixed rules, it is the kind of decision level 5E rests on. By what means the judgment will be made is not known: a camera on the xArm 6 was to make it (int-545), and none is installed (int-543). Whether S6's agent, S11 or a person will make the judgment is not stated (int-509).
Why we infer this:Verified: a camera on the xArm 6 was to check each finished product and decide between shipping, a defect and, in future, a redo (int-545); none is installed, and whether there will be one is unknown (int-543); S6 routes parts to inspection, rework or shipping (int-009); and the cell's route is fixed (int-081, int-071). Inferred already: a policy fixed rules alone could carry out sits at levels 1 to 3, so a level 5E claim rests on decisions the rules do not make, taken within limits (lvl-011, lvl-015). Of S6's steps, the judgment of the finished product is the one the route does not settle, so it is the one that could carry such a claim, by whatever means it comes to be made. No source says how the judgment is made, by fixed criteria or by the agent within limits, or who will make it: S6's agent, S11 or a person (int-509). So this record does not place it at a level.
Evidence · 3 citations
perform qaqc on the finished product and determine should the product go out for shipping, is considered a defect, and can a product be sent back for a redo - the redo one is a future state at the moment
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S91
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Permission to make certain decisions independently within established safety and process limits.
Level 5. Agentic Evolution: A Spectrum of Increasing Decision Authority (infographic) · IntelliMake.org · Panel #5E
Currently it is not installed and it is unknown if there will be one or if x6 will use location only.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S182 (2026-10-12), answer 3
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Kind: RecommendationThis project's simulation and agent design, not the physical cellProject design, not the physical cellsafety-598
Project advice
Do not use UFACTORY Studio's simulated-arm mode as the simulation substrate for S6 agent work: it needs a real arm connected, its settings apply to the real arm, and its unlock-joint button unlocks the real joints.
This is advice from this project, based on: safety-528 Verified
Why:Studio's own text says both modes need a real arm and that simulation-mode settings and joint unlocking act on it, so it does not isolate an agent from the machine.
An autonomous agent driving the S6 xArm 6 through the Python SDK could change collision sensitivity (to 0, which disables collision detection), collision rebound, reduced mode and the safety boundary. Under the xArm manual's own warning, changing the controller safety configuration makes the robot system a new system whose safety reviews, such as risk assessments, must be updated.
Why we infer this:Verified: the SDK exposes these calls and the glossary says sensitivity 0 disables detection; the manual says modifying the controller safety configuration creates a new system needing updated safety reviews. Inferred: an agent with SDK access could make such changes, and the manual's warning would then apply. Whether the Python SDK calls change the same 'configuration file' the manual refers to is not stated in any fetched source.
Evidence · 6 citations
:param value: sensitivity value, 0~5
xArm-Python-SDK API documentation (doc/api/xarm_api.md) · UFACTORY · def set_collision_sensitivity [SDK text for the xArm API; names no single model]
When it is set to 0, it means that collision detection is not enabled.
UFACTORY Studio User Manual (online), 2. Glossary · UFACTORY · Glossary, Collision Sensitivity [general Studio text; the Studio manual says it applies to the xArm6]
If parameters in the configuration file are modified, the entire robot system shall be deemed a new system, which necessitates the update of all safety review processes, such as risk assessments.
UFACTORY xArm Hardware Manual (online), 1. Safety · UFACTORY · 1.4 Personnel Safety, WARNING [series text: names no single model]
The xArm manual says a complete safety assessment must be recorded each time the arm is re-installed and debugged, and that a safety assessment is required each time it is installed.
Evidence · 2 citations
A complete safety assessment must be recorded each time the robotic arm is re-installed and debugged.
UFACTORY xArm Hardware Manual (online), 1. Safety · UFACTORY · 1.3, DANGER list [series text: names no single model]
The xArm arm consists of a base and rotary joints, each joint a degree of freedom, numbered from the bottom as Joint 1, Joint 2 and so on; the last joint is the tool side, where end effectors such as a gripper connect. The xArm 6 has six such joints.
Evidence · 3 citations
The xArm robotic arm system consists of a base and rotary joints, and each joint represents a degree of freedom. From the bottom to the top, in order, Joint 1, Joint 2, Joint 3, etc.
This robot arm has 6 axes, with 5kg payload and 1m/s speed.
The difference between UFACTORY xArm5, UFACTORY xArm6 and UFACTORY xArm7 (Help Center article) · UFACTORY · Section 1 'Main difference in brief', xArm 6 entry
The xArm manual makes the integrators of the xArm responsible for complying with the country's safety laws and regulations, including making a risk assessment for the complete system and making sure there is a safe distance between people and the xArm when they interact with it.
Evidence · 2 citations
The integrators of xArm are responsible for the compliance of applicable safety laws and regulations in the country, to prevent any hazards in the operating environment. This includes, but is not limited to:
UFACTORY xArm Hardware Manual (online), 1. Safety · UFACTORY · 1.1 Validity and Responsibility [series text: names no single model]
UFACTORY's xArm product page presents the xArm as a collaborative robot ('cobot'), while the xArm manual says no people or other equipment should be in the working area when the arm is in operation. Neither source says how the two fit together.
Kind: RecommendationThis project's simulation and agent design, not the physical cellProject design, not the physical cellsafety-594
Project advice
Treat the xArm 6's collision detection, safety boundary and reduced mode as configurable controller functions, not validated safeguards: they must not replace risk-assessed protective devices wired to the EI and SI inputs.
This is advice from this project, based on: safety-578 Gapsafety-559 Verifiedsafety-560 Verifiedsafety-561 Verifiedsafety-564 Verifiedsafety-565 Verifiedsafety-544 Verified
Why:No fetched UFACTORY document gives these functions a Performance Level or SIL. Collision detection is a current-model comparison that UFACTORY says can false-trigger and can be switched off; the safety boundary and reduced mode are settings. A function with no documented rating cannot stand in for a rated protective device.
The IP address of the xArm 6 control box at S6, and how the S6 network is laid out (direct PC link, router or switch), are not in the sources; the manuals give only the default range 192.168.1.xxx and the reset address 192.168.1.111.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Evidence · 2 citations
The default IP of robotic arm is 192.168.1.xxx
UFACTORY Studio User Manual (online), 3. Connection · UFACTORY · 3.2 Software Connection
The future 3D-printed flow in the IntelliMake diagram has no S2 step (printed parts go from S7 straight to S6), but 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.
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.
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).
The project specification describes S6 as the downstream arm that handles parts after processing, but IntelliMake's future 3D-printed flow has S6 handling parts before laser engraving (S7 → S6 → S4/S5). S6's role is therefore not simply 'after processing' in the future flow.
What S2 publishes to the other agents or the hub is not defined: placement confirmations, S3 slot updates, faults and error codes, its own ready or busy state, and whether any work-order or traceability data passes through S2. IntelliMake says this will be developed as the simulation is created.
Related: int-020 Verifiedint-048 Inferred
Evidence · 1 citation
This will be developed as we create the simulation.
xArm 850 S2 Project: Open Questions for IntelliMake, Batch 01 responses · IntelliMake.org · Question 10, Answer column
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.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
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.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
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.
Related: int-014 Superseded by int-081 Verifiedint-051 Superseded by int-081 Verifiedint-081 Verifiedint-013 Superseded by int-081 Verified
Evidence · 5 citations
S2 can place either on s3 or s4 depending upon availablitity or fit could even pause if neither are available.
xArm 850 S2 Project: Open Questions for IntelliMake, Batch 01 responses · IntelliMake.org · Question 2, Answer column
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.
Related: int-017 Superseded by int-084 Verifiedint-080 Verifiedint-084 Verified
Evidence · 3 citations
It can not simply stack or break the allocatied space the system will have in place.
Derek Stringfellow, project record · Project-internal record · retrieved 2026-09-21
Project copy; not published on this site.
Our safety rules today forbid stacking: one card per spot on S3. Do you mean cards placed on top of each other, or side by side in the same area?
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S146 (2026-10-07), question (3) as asked
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
On top of each other
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S146 (2026-10-07), answer (3)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Kind: ContradictionThis project's simulation and agent design, not the physical cellProject design, not the physical cellint-092
Sources disagree
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.
Derek Stringfellow, project record · Project-internal record · retrieved 2026-09-21
Project copy; not published on this site.
the agent is not expected to work semiautonomous
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S146 (2026-10-07), answer (1)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Runs the order, reports problems
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S148 (2026-10-07), answer (1)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
On the normal path the agent moves the arm by itself, with no person approving each move. Anything off the path: it pauses and reports with a recommendation, and a person decides.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S148 (2026-10-07), the option answer (1) chose (the option's words, not his)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
(This is our current design, called 5E.)
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S148 (2026-10-07), the same option's name for the design (the option's words, not his)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Both arms
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S148 (2026-10-07), answer (2)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
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).
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
S3 can serve two purposes, staging material in one area, and placing defects in another.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S145 (2026-10-07)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
On top of each other
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S146 (2026-10-07), answer (3)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Kind: GapThis project's simulation and agent design, not the physical cellProject design, not the physical cellint-097
Not known
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).
Kind: GapThis project's simulation and agent design, not the physical cellProject design, not the physical cellint-098
Not known
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).
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.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
How this would be checked:Measuring at the cell from the floor to the top of each cabinet, conveyor and mount plate would settle it.
Phase 1 measurements table, sent by Derek with the layout drawing (2026-09-30) · Derek Stringfellow · Table, header row
Derek Stringfellow, project record · Project-internal record · retrieved 2026-09-30
Project copy; not published on this site.
S1 Conveyer 32 18.5 51.5
Phase 1 measurements table, sent by Derek with the layout drawing (2026-09-30) · Derek Stringfellow · Table, 'S1 Conveyer' row (Height, Width, length)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-09-30
Project copy; not published on this site.
S4 Engraver conveyer 3.5 38.5
Phase 1 measurements table, sent by Derek with the layout drawing (2026-09-30) · Derek Stringfellow · Table, 'S4 Engraver conveyer' row (Height, then length)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-09-30
Project copy; not published on this site.
S2 Mount Plate 1
Phase 1 measurements table, sent by Derek with the layout drawing (2026-09-30) · Derek Stringfellow · Table, 'S2 Mount Plate' row (Height)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-09-30
Project copy; not published on this site.
Kind: GapThis project's simulation and agent design, not the physical cellProject design, not the physical cellint-105
Not known
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.
When a camera judges a card defective (S2's checking incoming material, or S6's after the engraver), what should the agent do?
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S152 (2026-10-07), the question as asked
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Not decided yet
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S152 (2026-10-07)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Leave it open; the simulation pauses and reports until you decide.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S152 (2026-10-07), the option chosen (the option's words, not his)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
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.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S146 (2026-10-07), answer (4)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Defects found after the engraver or printer also end up in S3's defects area.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S146 (2026-10-07), the option answer (4) matches (the option's words, not his)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Rework is its own flow; defects go to S3.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S149 (2026-10-07), the option answer (2) chose (the option's words, not his)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
whether S154's first answer means the xArm 6 side's defects no longer go to S3's defects area
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S155 (2026-10-07), question (1) as given in the bracket
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
xArm 6 defects does not end up in S3 at this time
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S155 (2026-10-07), first answer
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
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.
Reasoning:This project's reading, not one either statement gives: S97's "can travel" names a capability of the engraver; S172's "will remain stationary" names the plan for the cell. A plan stated later is taken for how the cell runs, which is what the lessons and the agents' configurations describe.
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).
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
IntelliMake's layout draws the station row with an arrow from S6 into S7 (the 3D printer), but the future 3D-printed flow banner puts S7 before S6 (S7 3D Printing → S6 Robot Handling), and the initial gift flow has no printing step at all. The arrow's direction is drawn, not worded; the banner's wording is the only textual statement of the order between S6 and S7.
Camera C2 monitors 'the robot–laser work area', but the layout does not say which robot: S2, S6 or both. 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.
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.
What S6 consumes from the other stations or the shared hub (for example, that a part is ready after the laser step) and what it publishes are not defined in any source. The physical I/O between stations is undefined for S2 as well (int-022).
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Cycle times for S6's handling (picking a part after the laser step and routing it to inspection, rework or shipping) are not documented, so S6's share of the cell's throughput cannot be quantified.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
The 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.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S46
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
I mounted the x6 last night on the S6 cabinet.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S107 (2026-10-02); 'x6' read as the xArm 6
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Kind: GapThis project's simulation and agent design, not the physical cellProject design, not the physical cellint-519
Not known
No IntelliMake 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).
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.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
The xArm 6's camera: is it installed, is it on the arm, and is it also separate from C1 and C2?
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S182 (2026-10-12), question (3) as given in the bracket
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Currently it is not installed and it is unknown if there will be one or if x6 will use location only.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S182 (2026-10-12), answer 3
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
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.
Both will have a camera that they will use as part oof their function set
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S90 (2026-09-30)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
The camera on the 6 is used to both collect the finished product as well as perform qaqc on the finished product
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S91 (2026-09-30)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
The xArm 6's camera: is it installed, is it on the arm, and is it also separate from C1 and C2?
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S182 (2026-10-12), question (3) as given in the bracket
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Currently it is not installed and it is unknown if there will be one or if x6 will use location only.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S182 (2026-10-12), answer 3
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
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).
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Not stated for S4: what the engraver carriage's 465 mm height is measured from (the belt, the table or the floor; int-611); the engraver's width across the belt, and whether any of it reaches past the belt's sides; where the unit stands in the cell; whether and how it would be interlocked; whether the conveyor may move while an arm places or picks at S4; and how the two arms share S4: whether both may work there at the same time, and if not, in what order and on whose signal. The carriage area's extent along the conveyor and its height were given on 2026-10-22 (S222, S224, S226; int-611), final for the engraver but not for the station.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Reasoning:What the earlier gap on S4 (named in related) left unstated and the 2026-10-22 figures do not answer, with the one new question no record answers: how the two arms share S4 in time (int-011, int-062). This record keeps that gap's citations (rule 7). It replaces that gap when the run of s2-agent/tools/set_carriage_area.py marks it superseded; until then both stand, and the earlier gap's "Not stated" on the carriage's height is answered in part by int-611: a figure, 465 mm, with no datum.
Quote not shown (over 40 words). See the source at: Statement S194 (2026-10-14, about 10:50), the S4 conveyor's areas.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S194 (2026-10-14, about 10:50), the S4 conveyor's areas
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
S4 engrave will remain stationary and the conveyer swill be the means of moving the product from one location to another.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S172 (2026-10-09), IntelliMake Notes
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
We have not determined what functionality will be used since the conveyer is an attachment to the engraver and the conveyer may be the only location to location movement for the product. So this is TBD for now.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S118, answer (2), to whether the engraver travelling along S4 enters the arms' place and pick zones and is interlocked
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
The engrave actually can travel along the length of the conveer.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S97
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Yes, it is S5
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S102, answer (2), to whether the engraver travelling along the S4 conveyor is the course's S5, the xTool F1 Ultra
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
both arms work at S4. one places the material to perform the work, the other picks up the finished product
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S84, answering Q55(1)
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Each arm has its own stretch of the conveyor, the xArm 850's from its end to the carriage area at 360 mm, the xArm 6's from the area's end at 600 mm to the other end (int-611, as the project reads the 2026-10-22 figures). Where within each an arm places or picks is not stated, nor where the printed flow places.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
Reasoning:That each arm has its own side of the conveyor is S194's ("on the 850 side", "on the x6 side"), which the 2026-10-22 figures do not restate, so its citation is kept (rule 7). The stretches' boundaries are int-611's figures, as the project reads them (all three in cm, along the conveyor from its xArm 850 end). Where the simulation puts each arm's place, at the middle of its stretch, is the project's rule, not his (docs/planning/2026-10-25-s4-carriage-script-design-note.md §4). This record replaces the earlier gap on where each arm works on S4 (named in related) when the run of s2-agent/tools/set_carriage_area.py marks it superseded.
The engraver conveyer on the 850 side has 7.5 inches of area before the carridge area of the engraver ... the remaining side of the convery is also about 7 inches long on the x6 side
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S194 (2026-10-14, about 10:50), the S4 conveyor's areas
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
1.4.a. Yes, use them now
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S196 (2026-10-14), first line, answering the 10-14 decisions file's §1.4 (a), use his figures now
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
6. The carriage area begins at 36mm and ends at 60mm, height46.5mm
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S222 (2026-10-22, from the lab), item 6, answering the cell-access checklist's item on where along the S4 conveyor the engraver's carriage area stands and its height
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
Typo on the measurement. I meant to type cm for centimeter
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S224 (2026-10-22, from the lab, after S223), second line, correcting the units in S222 item 6 after the session asked whether he meant cm
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
engraver was measured from the 850 end. THese are final measurements for the engraver but not the station. The engraver is on a different table and n ot sittng on the final station cabinent yet.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S226 (2026-10-22, from the lab, after S225), answering which end of the belt the carriage area was measured from and whether the figures are final
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
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." S226 is taken as current for where the engraver stood on 2026-10-22, because it is later and specific; that is the project's reading, and item 1 may restate the design ("as expressed previousilly"). It is asked (Question 7 of the carriage design note). Either way the engraver's place in the cell stays a placeholder.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
1. It is mounted on station cabinet, like x6, engraver and 3d printer, as expressed previousilly.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S222 (2026-10-22, from the lab), item 1, on how the xArm 850 is mounted
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
Project copy; not published on this site.
engraver was measured from the 850 end. THese are final measurements for the engraver but not the station. The engraver is on a different table and n ot sittng on the final station cabinent yet.
Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S226 (2026-10-22, from the lab, after S225), answering which end of the belt the carriage area was measured from and whether the figures are final
Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04
No risk assessment for the S6 xArm 6 application has been confirmed: whether one exists for the complete application (arm, gripper, workpieces and the stations it hands parts to and from), who performed and signed it, and whether it was redone after installation as the xArm manual requires.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
The S6 emergency stops are not confirmed: whether any emergency stop buttons beyond the Control Box button are wired to EI, where they are, and whether S6 shares an emergency stop circuit with S2 or other stations.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
The final position of the S6 Control Box is not confirmed: whether it is outside the arm's working range, at 0.6 to 1.5 m height, with its emergency stop reachable.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
The Control Box must be placed outside the working range of the robotic arm to ensure the emergency stop button can be pressed once an emergency occurs.
UFACTORY xArm Hardware Manual (online), 1. Safety · UFACTORY · 1.3, CAUTION list [series text: names no single model]
S6's guarding and protective devices are not confirmed: whether fences, interlocked doors, light curtains, safety mats or laser scanners are wired to the SI protective stop input, whether any safety signal passes through a PLC (and if so whether it is a safety PLC), or whether SI is still in its default state with no additional safety equipment.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
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).
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
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.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
The S6 xArm 6's safety-related settings are not confirmed: collision detection on or off, collision sensitivity level, collision rebound, self-collision detection and tool model, safety boundary and its limits, reduced mode and its limits, 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.
Awaiting cell access: this could be confirmed or corrected once the physical S6 cell can be observed.
You must enter password to access this page, the default password:
UFACTORY Studio User Manual (online), 7. Settings · UFACTORY · 7.4.3 Advanced Settings (the quote stops before the default value, which this corpus does not print) [general Studio text; the Studio manual says it applies to the xArm6]
CODE_SESSION 01 — xArm 850 Interactive Learning Platform (project specification) · Derek Stringfellow (project owner) Derek Stringfellow, project record · Project-internal record · retrieved 2026-09-21 · cited by 3 records here · Project copy; not published on this site.
Owner statements 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 48 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 6 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 2 records here · Project copy; not published on this site.
Site photos, 2026-09-24: what they show, and what they do not (OBSERVATIONS.md) · Derek Stringfellow (project owner) Derek Stringfellow, project record · Project-internal record · retrieved 2026-09-25 · cited by 1 record here · Project copy; not published on this site.
This site keeps what the courses need to work in this browser: the tier you chose, the questions you answered correctly, whether you have visited before, and your filter and display settings. It stays on this device, and nothing you choose here changes it.
This site uses no third-party analytics. No analytics script, tracking pixel or tracker from another company loads by itself on any page, so there is nothing here to allow or refuse. A lesson video loads from YouTube only when you press Play, as its note says. If analytics is ever added, it will be named here, and it will load only after you allow it.
What each one records
Who
What
When
This site
The tier you chose, the questions you answered correctly, whether you have visited before, your filter and display settings
Always, in this browser only
You can change this at any time from “Analytics choices” at the foot of every page.