Program the Real Arm · xArm 850 · Page 1 of 6

The Logic

Write the logic before the code. A state diagram and a sequence table show what the program does, what it checks before each move, and how it stops when something is wrong.

The logic names the start conditions, the states, the inputs and signals, the machine's actions, the timing and parameters, the decision points, the completion conditions, the fault and stop conditions, and the safe recovery1.

States

The Program's States
StateMeaningLeaves By
READYAt home, no job running2START_JOB3
RUNNINGA job's cycle is running2PAUSE, STOP, a fault, or the job's end456
PAUSEDMotion held; the job and the vacuum kept as they are4RESUME or STOP4
FAULTThe run ended on an abnormal condition25Only STATUS and SHUTDOWN; a person recovers2
STOPPEDThe operator stopped the arm24Only STATUS and SHUTDOWN2

Start Conditions

  • Before a job the program reads the arm. It refuses with NOT_READY, sending nothing, if the controller reports an error, the arm is not in position mode (Manual Mode is refused), or the tool point and payload are not the station file's 126 mm and 0.61 kg7.
  • With the real arm it does not even connect while a waypoint, the pick area, a stack, the floor, the workspace or a joint range is still a placeholder8.

One Cycle

  1. Home: a joint move to the home waypoint6.
  2. Room: the job's stack must have room for one more card, or the run ends in STACK_FULL65.
  3. Pick: above the pick pose, straight down, vacuum on; the card must be held, or VACUUM_LOST65.
  4. Carry: lift, then move above the variant's stack with the card still held6.
  5. Place: straight down onto the stack, vacuum off; the card must be released, or RELEASE_FAILED65.
  6. Return: straight up, home, and CYCLE_COMPLETE with the cycle time6.

The cycle repeats until the job's quantity is reached; then the program reports JOB_COMPLETE and returns to READY6. Before every move it checks the target against the station file's bounds and sends nothing if the target is outside them8.

The Sequence Table
One Cycle, Step by Step
StepActionCheckedAgent Command
homeJoint move to the home waypointThe bounds; the controller after the move689MoveToNamedPose
pick_hoverJoint move above the pick poseThe bounds; the controller689Pick
descendStraight down to the pick poseInside the pick area, above the floor, inside the joint ranges689Pick
vacuum_onSwitch the vacuum on and waitThe controller69Pick
verify_holdingRead whether the card is heldHeld, or VACUUM_LOST65Pick
liftStraight upStill held69Pick
stack_hoverJoint move above the variant's stackStill held69Place
stack_placeStraight down onto the stackThe bounds; the controller689Place
vacuum_offSwitch the vacuum off and waitThe controller69Place
verify_releasedRead whether the card is still heldReleased, or RELEASE_FAILED65Place
stack_retreatStraight up above the stackThe controller69Place
return_homeJoint move home; report CYCLE_COMPLETEThe controller69MoveToNamedPose

Faults

Abnormal Conditions
CodeHow It Is DetectedThe Program's ResponseRecovery
VACUUM_LOSTNo card held after the vacuum is switched on (also how an empty corner stop shows), or the card lost while carried5Stops where it is and reports whether a card is on the cup10Wait until the arm has stopped, find the card, check the corner stop and the cup, then start again211
RELEASE_FAILEDThe card is still held after the vacuum is switched off5Stops at the stack; the card stays on the cup10Switch the vacuum off in Studio and take the card off by hand122
STACK_FULLThe stack is already at its maximum5No move toward the card10Empty the stack and start the program again13
OUT_OF_BOUNDSA target outside the station file's bounds5The move is never sent8Check the waypoint against the card's real position; never widen a bound to make a run pass142
ARM_ERRORA controller error, the controller's own stop, a lost connection, or a move not finished in time5Sends nothing more, and does not clear the error or re-enable the arm10As in Abnormal Conditions: the error is cleared by hand and the motion re-planned15
NOT_READYA controller error, Manual Mode on, or a tool point or payload unlike the station file's7Nothing is sent7Fix it in Studio as the message says, then start again2

With the camera extension, four more codes can occur: NO_PART, QC_REJECT, CAMERA_ERROR and VISION_ERROR5.

Pause, Stop and Safe Recovery

  • PAUSE holds the arm mid-move and keeps the job and the vacuum as they are; RESUME continues4.
  • STOP stops the arm and switches nothing off, so a held card stays held; the program reports whether it is4.
  • On any fault the program stops sending motion and reports. It never clears an error, re-enables the arm, changes a safety setting or retries a step10.
  • Every run starts again from home; after a fault or a stop a person deals with the cause first102.

Warning

PAUSE and STOP are software stops that leave the arm powered. Neither is an emergency stop4.

Printed from https://www.anotherplace.com/learn/en/xarm-850/program/logic. Every line cites its source on that page.

Provenance

References · 15

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 design (its simulation, agent and arm program), not the physical cell
This project's design (its simulation, agent and arm program), not the physical cell.
  1. Confidence: Verifiedint-638

    The record says

    The course asks for a flowchart, state diagram or sequence table made before programming, identifying the start conditions, operating states, inputs and sensor signals, machine actions, timing and parameter requirements, decision points, completion conditions, fault and stop conditions, and safe recovery behavior.

    Evidence · 10 citations

    Create a flowchart, state diagram, or sequence table before programming.

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · '2. Develop the Program Logic'

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

    Start conditions

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · '2. Develop the Program Logic', the list under 'The logic should identify'

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

    Operating states

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · '2. Develop the Program Logic', the list under 'The logic should identify'

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

    Inputs and sensor signals

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · '2. Develop the Program Logic', the list under 'The logic should identify'

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

    Machine actions

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · '2. Develop the Program Logic', the list under 'The logic should identify'

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

    Timing and parameter requirements

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · '2. Develop the Program Logic', the list under 'The logic should identify'

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

    Decision points

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · '2. Develop the Program Logic', the list under 'The logic should identify'

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

    Completion conditions

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · '2. Develop the Program Logic', the list under 'The logic should identify'

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

    Fault and stop conditions

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · '2. Develop the Program Logic', the list under 'The logic should identify'

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

    Safe recovery behavior

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · '2. Develop the Program Logic', the list under 'The logic should identify'

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

  2. Confidence: VerifiedThis project's design (its simulation, agent and arm program), not the physical cellint-647

    The record says

    This project's program reports one of five states: READY (at home, no job running), RUNNING, PAUSED, FAULT and STOPPED. After FAULT or STOPPED it accepts only STATUS and SHUTDOWN: it never recovers by itself, and a person deals with the cause and starts the program again.

    Reasoning: The sentence on the program states the state of the program's own repository (~/projects/ie6000-lab, step3/), not something the cited source says: step3/program.py defines the five states and refuses every command but STATUS and SHUTDOWN after FAULT or STOPPED, at commit 130b203 (2026-11-19), and docs/course-step3/ in this repository describes the same version. The corpus cites only sources kept under corpus/sources/ or at a public address (corpus/README.md, Source entries), so it cannot cite that repository; it cites the course's suggested states, which the program's extend.

    Evidence · 2 citations

    Machine state | Status | Reports current operating condition | Ready, Running, Paused, Fault

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · 'Suggested Program Interface Table', 'Machine state' row

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

    Safe recovery behavior

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · '2. Develop the Program Logic', the list

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

  3. Confidence: VerifiedThis project's design (its simulation, agent and arm program), not the physical cellint-654

    The record says

    In its wait-for-job mode (--serve) this project's program moves home, reports READY and reads one command per line from standard input, as a JSON line or a short form a person types: START_JOB with a variant and a quantity from 1 to the room left on that variant's stack (typed as start black 3), PAUSE (p), RESUME (r), STOP (s), STATUS (status) and SHUTDOWN (quit). A command that cannot run in the current state is refused with a COMMAND_REFUSED event, never queued. Every event is one JSON line on standard output and in the run's log file. It exits with 0 at READY or a completed job, 2 at FAULT, 3 at STOPPED and 4 when it refuses to start.

    Reasoning: The sentence on the program states the state of the program's own repository (~/projects/ie6000-lab, step3/), not something the cited source says: step3/run.py (--serve, the exit codes) and step3/events.py (the JSON lines on standard output and in runs/<stamp>/events.jsonl), at commit 130b203 (2026-11-19), and docs/course-step3/ in this repository describes the same version. The corpus cites only sources kept under corpus/sources/ or at a public address (corpus/README.md, Source entries), so it cannot cite that repository; it cites S277, where waiting for the next order was asked for, and the course's suggested interface.

    Evidence · 4 citations

    vacumm triggered, gripper moved, piece released, arm goes back to starting position waiting for next order

    Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S277 (2026-11-19)

    Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04

    ok, I agree. Please move forward

    Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S277 (2026-11-19), his answer to the recommendation

    Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04

    Start task | Command | Initiates the approved program | START_JOB

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · 'Suggested Program Interface Table', 'Start task' row

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

    Task completion | Event | Confirms successful completion | JOB_COMPLETE

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · 'Suggested Program Interface Table', 'Task completion' row

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

  4. Confidence: VerifiedThis project's design (its simulation, agent and arm program), not the physical cellint-653

    The record says

    In this project's program PAUSE pauses the controller mid-move (the SDK's set_state(3)) and keeps the job and the vacuum as they are; RESUME continues. STOP stops the arm (set_state(4)), switches nothing off, so a held card stays held, and reports whether a card is held. Both are software stops that leave the arm powered; neither is an emergency stop.

    Reasoning: The sentence on the program states the state of the program's own repository (~/projects/ie6000-lab, step3/), not something the cited source says: step3/arm.py sends set_state(3) to pause, set_state(0) to resume and set_state(4) to stop, at commit 130b203 (2026-11-19), and docs/course-step3/ in this repository describes the same version. The corpus cites only sources kept under corpus/sources/ or at a public address (corpus/README.md, Source entries), so it cannot cite that repository; it cites the course's request for a controlled pause or stop.

    Evidence · 2 citations

    Demonstration of a controlled pause or stop

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · 'Required Demonstration'

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

    Fault and stop conditions

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · '2. Develop the Program Logic', the list

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

  5. Confidence: VerifiedThis project's design (its simulation, agent and arm program), not the physical cellint-651

    The record says

    Without the camera this project's program ends a run in FAULT with one of six codes: VACUUM_LOST (no card held after the vacuum is switched on, which is also how an empty corner stop shows, or the card lost while carried), RELEASE_FAILED (the card still held after the vacuum is switched off), STACK_FULL (the stack already at its maximum), OUT_OF_BOUNDS (a target outside the bounds; nothing is sent), ARM_ERROR (a controller error, the controller's own stop, a lost connection, or a move not finished in its allowed time) and NOT_READY. The camera extension adds NO_PART, QC_REJECT, CAMERA_ERROR and VISION_ERROR.

    Reasoning: The sentence on the program states the state of the program's own repository (~/projects/ie6000-lab, step3/), not something the cited source says: step3/program.py raises each code where the cycle checks for it, at commit 130b203 (2026-11-19), and docs/course-step3/ in this repository describes the same version. The corpus cites only sources kept under corpus/sources/ or at a public address (corpus/README.md, Source entries), so it cannot cite that repository; it cites the course's request for fault messages and abnormal conditions.

    Evidence · 2 citations

    Fault message | Event | Reports why execution stopped | Obstruction or position error

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · 'Suggested Program Interface Table', 'Fault message' row

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

    Likely errors or abnormal conditions

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · '1. Define the Manufacturing Task', the list under 'Describe'

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

  6. Confidence: VerifiedThis project's design (its simulation, agent and arm program), not the physical cellint-648

    The record says

    In one cycle this project's program moves home; checks that the job's stack has room; moves above the pick pose and descends straight down; switches the vacuum on and confirms the card is held; lifts; moves above the variant's stack, confirming the card is still held; lowers it straight down onto the stack; switches the vacuum off and confirms the release; retreats straight up and returns home. It then reports CYCLE_COMPLETE with the cycle time, and after the job's quantity JOB_COMPLETE, and returns to READY. Joint moves go between waypoints; straight-line moves are only the short descents, lifts and retreats.

    Reasoning: The sentence on the program states the state of the program's own repository (~/projects/ie6000-lab, step3/), not something the cited source says: step3/program.py runs these steps in this order (the STEP events name them: home, pick_hover, descend, vacuum_on, verify_holding, lift, stack_hover, stack_place, vacuum_off, verify_released, stack_retreat, return_home), at commit 130b203 (2026-11-19), and docs/course-step3/ in this repository describes the same version. The corpus cites only sources kept under corpus/sources/ or at a public address (corpus/README.md, Source entries), so it cannot cite that repository; it cites S277, the sequence the program was built to.

    Evidence · 2 citations

    vacumm triggered, gripper moved, piece released, arm goes back to starting position waiting for next order

    Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S277 (2026-11-19)

    Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04

    Machine actions

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · '2. Develop the Program Logic', the list

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

  7. Confidence: VerifiedThis project's design (its simulation, agent and arm program), not the physical cellint-650

    The record says

    Before a job this project's program reads the arm's readiness, and refuses with FAULT NOT_READY, sending nothing, if the controller reports an error, the arm is not in position mode (Studio's Manual Mode is refused), or the controller's tool point and payload differ from the station file's 126 mm and 0.61 kg.

    Reasoning: The sentence on the program states the state of the program's own repository (~/projects/ie6000-lab, step3/), not something the cited source says: step3/arm.py reads the error, the mode, the tool point and the payload, and step3/stations/s2-850.json holds 126 mm and 0.61 kg read from the controller on 2026-10-22 (ops-210), at commit 130b203 (2026-11-19), and docs/course-step3/ in this repository describes the same version. The corpus cites only sources kept under corpus/sources/ or at a public address (corpus/README.md, Source entries), so it cannot cite that repository; it cites the controller's reading those figures were taken from.

    Evidence · 3 citations

    Start conditions

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · '2. Develop the Program Logic', the list

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

    Weight 0.61 kg; centre of gravity CX 0, CY 0, CZ 53 mm

    UFACTORY Studio screens and a control-box photo for the xArm 850, 2026-10-22: what they show (OBSERVATIONS.md) · Derek Stringfellow · TCP after the update, table, 'Payload' row

    Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-22

    X 0, Y 0, Z 126 mm

    UFACTORY Studio screens and a control-box photo for the xArm 850, 2026-10-22: what they show (OBSERVATIONS.md) · Derek Stringfellow · TCP after the update, table, 'Offset' row, first part

    Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-22

  8. Confidence: VerifiedThis project's design (its simulation, agent and arm program), not the physical cellint-649

    The record says

    This project's program takes every waypoint, speed, wait and bound from a station file, never from its code, and labels each value with its status (placeholder, taught, measured or read from the controller) and its source. Before every move it checks the target against the station file's bounds (the pick area, a floor height, the workspace and the joint ranges) and sends nothing if the target is outside them. With the real arm it refuses to connect while a waypoint, the pick area, a stack, the floor, the workspace or a joint range is still a placeholder.

    Reasoning: The sentence on the program states the state of the program's own repository (~/projects/ie6000-lab, step3/), not something the cited source says: step3/stations/s2-850.json and its schema hold every value with a status and a source, step3/program.py checks each target before sending it (OUT_OF_BOUNDS), and step3/run.py lists the placeholders and does not connect, at commit 130b203 (2026-11-19), and docs/course-step3/ in this repository describes the same version. The corpus cites only sources kept under corpus/sources/ or at a public address (corpus/README.md, Source entries), so it cannot cite that repository; it cites the course's requirement to stay within the approved limits.

    Evidence · 2 citations

    The program must be developed and tested within the machine’s approved operating limits.

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · '3. Create or Modify the Machine Program', last line

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

    Review the program for unsafe motion, excessive speed, improper power, invalid parameters, and potential collisions.

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · 'Safety Requirements'

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

  9. Confidence: VerifiedThis project's design (its simulation, agent and arm program), not the physical cellint-657

    The record says

    Each step of this project's program maps onto a command of this project's planned agent for S2: MoveToNamedPose for the moves home, Pick for the moves and the vacuum at the pick, and Place for those at the stack. The wait-for-job mode's commands and its JSON-line events are the interface a future agent would call; the program today takes commands only from its local standard input.

    Reasoning: The sentence on the program states the state of the program's own repository (~/projects/ie6000-lab, step3/), not something the cited source says: each STEP event carries its agent command (step3/program.py), and step3/run.py reads commands only from standard input, at commit 130b203 (2026-11-19), and docs/course-step3/ in this repository describes the same version. The corpus cites only sources kept under corpus/sources/ or at a public address (corpus/README.md, Source entries), so it cannot cite that repository; it cites the course's request to name the agent's commands and the communication methods.

    Evidence · 2 citations

    Commands the Machine Agent could issue

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · '6. Identify the Agentification Interface', the list under 'Document'

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

    Available communication methods, such as digital I/O, PLC tags, MQTT, API, SDK, file transfer, or operator-interface actions

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · '6. Identify the Agentification Interface', the list under 'Document'

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

  10. Confidence: VerifiedThis project's design (its simulation, agent and arm program), not the physical cellint-652

    The record says

    On any fault this project's program stops sending motion and reports the code, the step and whether a card is on the cup. It never clears a controller error, re-enables the arm, changes a safety setting or saves the controller's configuration, and never retries a step; every run starts again from home.

    Reasoning: The sentence on the program states the state of the program's own repository (~/projects/ie6000-lab, step3/), not something the cited source says: step3/arm.py is the only module that calls the SDK and calls no error-clearing, enabling or safety setter, which a unit test checks in its source, at commit 130b203 (2026-11-19), and docs/course-step3/ in this repository describes the same version. The corpus cites only sources kept under corpus/sources/ or at a public address (corpus/README.md, Source entries), so it cannot cite that repository; it cites the course's safety requirements it was built to.

    Evidence · 3 citations

    Never bypass safety functions or exceed approved machine limits.

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · 'Safety Requirements'

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

    Stop testing immediately if the machine behaves unexpectedly.

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · 'Safety Requirements'

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

    Safe recovery behavior

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · '2. Develop the Program Logic', the list

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

  11. Confidence: VerifiedThis project's design (its simulation, agent and arm program), not the physical cellint-644

    The record says

    This project's program for the xArm 850 runs one task without the arm's camera. For each card of a job it moves home, picks the card at a taught pick pose with the vacuum gripper, places it on the staging stack for the job's variant, releases it and returns home; when the job is done the arm waits at home for the next job. Each card is pushed into an L-shaped corner stop of tape on the pick surface, so it lies under the taught pick pose.

    Reasoning: The sentence on the program states the state of the program's own repository (~/projects/ie6000-lab, step3/), not something the cited source says: step3/program.py and step3/run.py run this cycle with --no-camera, and the station file step3/stations/s2-850.json describes the corner stop (pick.fixture), at commit 130b203 (2026-11-19), and docs/course-step3/ in this repository describes the same version. The corpus cites only sources kept under corpus/sources/ or at a public address (corpus/README.md, Source entries), so it cannot cite that repository; it cites S277, the statement the task was taken from, and his agreement to it.

    Evidence · 2 citations

    vacumm triggered, gripper moved, piece released, arm goes back to starting position waiting for next order

    Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S277 (2026-11-19)

    Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04

    ok, I agree. Please move forward

    Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S277 (2026-11-19), his answer to the recommendation

    Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04

  12. Confidence: VerifiedAwaiting cell accessops-209

    The record says

    On 2026-10-22 (Studio 2.6.0, before the update) UFACTORY Studio's Live Control for the xArm 850 had the Vacuum Gripper selected as its end effector, with OPEN and CLOSE buttons; its speed slider was at 12 % and Manual Mode was off.

    Awaiting cell access: this could be confirmed or corrected once the physical S2 cell can be observed.

    Reasoning: Verified as a direct reading of UFACTORY Studio connected to the real xArm 850 ('Real' selected) on 2026-10-22, before the firmware update that day (int-608). It is what the screen showed that day and no further: a slider position and a selected preset can be changed at any time. No inspection of the tool is recorded.

    Evidence · 4 citations

    End effector selected | Vacuum Gripper (OPEN / CLOSE buttons)

    UFACTORY Studio screens and a control-box photo for the xArm 850, 2026-10-22: what they show (OBSERVATIONS.md) · Derek Stringfellow · Live Control table, 'End effector selected' row

    Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-22

    Speed slider | 12 %

    UFACTORY Studio screens and a control-box photo for the xArm 850, 2026-10-22: what they show (OBSERVATIONS.md) · Derek Stringfellow · Live Control table, 'Speed slider' row

    Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-22

    Manual Mode | Off

    UFACTORY Studio screens and a control-box photo for the xArm 850, 2026-10-22: what they show (OBSERVATIONS.md) · Derek Stringfellow · Live Control table, 'Manual Mode' row

    Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-22

    Firmware Version 2.6.0; Software Version 2.6.0

    UFACTORY Studio screens and a control-box photo for the xArm 850, 2026-10-22: what they show (OBSERVATIONS.md) · Derek Stringfellow · Live Control table, 'Product Information' row

    Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-22

  13. Confidence: VerifiedThis project's design (its simulation, agent and arm program), not the physical cellint-655

    The record says

    In this project's program the count of cards on each stack lasts for the whole session, so a second job of the same variant places on top of the first, and a job larger than the room left is refused. No command resets the counts: a person empties the stack and starts the program again.

    Reasoning: The sentence on the program states the state of the program's own repository (~/projects/ie6000-lab, step3/), not something the cited source says: step3/program.py keeps the counts for the session and refuses START_JOB beyond the room left, at commit 130b203 (2026-11-19), and docs/course-step3/ in this repository describes the same version. The corpus cites only sources kept under corpus/sources/ or at a public address (corpus/README.md, Source entries), so it cannot cite that repository; it cites S278, where the behavior was agreed.

    Evidence · 2 citations

    in `--serve` the stack counts last for the session; no command resets them; empty a stack by restarting

    Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S278 (2026-11-19), the decision he was answering (the session's words, not his)

    Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04

    Agreed with 8 and 9 decisions

    Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S278 (2026-11-19)

    Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-04

  14. Confidence: Verifiedint-643

    The record says

    The course's safety requirements for programming: get approval before running a new or modified program; review it for unsafe motion, excessive speed, improper power, invalid parameters and potential collisions; use simulation, dry runs, reduced speed or reduced power whenever possible; confirm that the required guards, interlocks, emergency stops and safety zones are active; never bypass safety functions or exceed approved machine limits; keep access to the emergency stop during initial testing; stop testing at once if the machine behaves unexpectedly; and back up the approved working program before changing it.

    Evidence · 8 citations

    Obtain approval before executing a new or modified program.

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · 'Safety Requirements'

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

    Review the program for unsafe motion, excessive speed, improper power, invalid parameters, and potential collisions.

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · 'Safety Requirements'

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

    Use simulation, dry runs, reduced speed, or reduced power whenever possible.

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · 'Safety Requirements'

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

    Confirm that required guards, interlocks, emergency stops, and safety zones are active.

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · 'Safety Requirements'

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

    Never bypass safety functions or exceed approved machine limits.

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · 'Safety Requirements'

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

    Maintain access to the emergency stop during initial testing.

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · 'Safety Requirements'

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

    Stop testing immediately if the machine behaves unexpectedly.

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · 'Safety Requirements'

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

    Back up the approved working program before making further changes.

    'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course · 'Safety Requirements'

    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12

  15. Confidence: Verifiedops-071

    The record says

    When an error occurs, the arm stops at once and discards cached commands; the error must be cleared manually and the motion re-planned before normal operation continues.

    Evidence · 1 citation

    After the above error occurs, the robotic arm will stop working immediately and discard the Control Box cache command. Users need to clear these errors manually to allow normal operation.

    UFACTORY Studio User Manual (online), 12. Error Handling · UFACTORY · 12.1

    © UFACTORY · All rights reserved; quoted briefly as evidence · retrieved 2026-10-13

Sources for This Page

  • 'Program Your Machine': the course's Step 3 assignment for the Phase 1 Factory machines (course text as attached by Derek, 2026-11-12) · IntelliMake Phase 1 Factory course (IntelliMake)
    IntelliMake course text, as attached by Derek Stringfellow · Project-internal record · retrieved 2026-11-12 · cited by 11 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 4 records here · Project copy; not published on this site.
  • UFACTORY Studio screens and a control-box photo for the xArm 850, 2026-10-22: what they show (OBSERVATIONS.md) · Derek Stringfellow (project owner)
    Derek Stringfellow, project record · Project-internal record · retrieved 2026-10-22 · cited by 2 records here · Project copy; not published on this site.
  • UFACTORY Studio User Manual (online), 12. Error Handling · UFACTORY (manufacturer)
    © UFACTORY · All rights reserved; quoted briefly as evidence · retrieved 2026-10-13 · 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