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

The Agent Interface

The program does not need an agent, but it is built so one can call it: an agent sends the same commands a person types, and reads the same events the program prints.

The course asks for the commands an agent could issue, the task parameters, the status it could report, the completion and failure messages, the communication methods, and the current limitations1. It suggests a start command, job parameters, a machine state, a completion event and a fault message2.

Commands

Commands in the Wait-for-Job Mode
CommandTyped by a PersonEffect
START_JOBstart black 3Runs a job; refused, never queued, when it cannot run now3
PAUSEpHolds the arm mid-move; keeps the job and the vacuum34
RESUMErContinues34
STOPsStops the arm; reports whether a card is held34
STATUSstatusReports the state3
SHUTDOWNquitStops if moving, then ends the program3

No command clears a fault: after FAULT or STOPPED only STATUS and SHUTDOWN are accepted, and a person recovers5.

Task Parameters

  • variant: which card it is. Without the camera this is the caller's word, and it chooses the stack67.
  • quantity: from 1 to the room left on that variant's stack. The stack counts last for the whole session38.
  • Everything else, the waypoints, speeds and bounds, is fixed in the station file for an approved version: an agent chooses what to make, not how the arm moves9.

Status and Messages

Events
EventWhen
STATEREADY, RUNNING, PAUSED, FAULT or STOPPED5
STEPEach step of the cycle, with its agent command10
CYCLE_COMPLETE, JOB_COMPLETEA cycle with its time; the job's end11
FAULTThe code, the step, and whether a card is on the cup1213
STOPPEDA controlled stop, and whether a card is held4
COMMAND_REFUSEDA command that cannot run now, and why3

Communication Methods

  • Commands in: one JSON line per command on standard input, or the short forms a person types3.
  • Events out: one JSON line per event on standard output, and the same lines in the run's log file3.
  • To the arm: UFACTORY's Python SDK, from one module only; an agent never talks to the arm directly1410.
  • To other agents: connecting the program to an agent, and through it to the factory's systems, is the next course step15.

Each step maps onto a command of this project's planned agent: MoveToNamedPose for the moves home, Pick at the pick and Place at the stack10.

Current Limitations

  • Without the camera the program cannot tell which card it holds, or whether the card is damaged16.
  • One card per cycle, placed by hand in the corner stop while the arm is home16.
  • No command recovers from a fault: every fault needs a person16.
  • Commands come from one local operator. Taking them over a network would need authentication and approval of the changed program16.

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

Provenance

References · 16

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-641

    The record says

    The course asks how a future Machine Agent could interact with the program: the commands it could issue, the required task parameters, the machine status it could report, the completion and failure messages, the available communication methods (such as digital I/O, PLC tags, MQTT, an API, an SDK, file transfer or operator-interface actions), and the current limitations or integration gaps. Building the agent is not part of this step.

    Evidence · 7 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

    Required task parameters

    '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

    Machine status information that could be reported

    '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

    Completion and failure messages

    '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

    Current limitations or integration gaps

    '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

    You are not required to build the Machine Agent in this assignment.

    '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', last line

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

  2. Confidence: Verifiedint-642

    The record says

    The course's suggested program interface has a START_JOB command that starts the approved program, job parameters as an input (such as the part type), the machine state as a status (Ready, Running, Paused, Fault), JOB_COMPLETE as the completion event, and a fault message event that reports why execution stopped.

    Evidence · 5 citations

    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

    Job parameters | Input | Defines task-specific settings | Part type or engraving file

    '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', 'Job parameters' row

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

    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

    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

    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

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

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

    The record says

    Without the camera, this project's program does not check the card: the job names its variant, which chooses the stack, and every completed cycle reports that no inspection ran. The camera's check of the card's variant and defects before the pick is built as an extension of the same program, tested on still images the arm's camera took with the arm standing still.

    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 CYCLE_COMPLETE and JOB_COMPLETE event carries "inspection": "none (no camera)" and "variant_source": "job" (step3/program.py), and the extension is step3/camera.py, step3/vision.py and step3/tools/check_capture.py, 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 the camera was taken out of the loop and the extension agreed.

    Evidence · 3 citations

    I do not think we can test with the camera for the assignment at this point.

    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

    the camera as a documented extension tested offline on real arm-camera captures, a `--no-camera` mode and a mode that waits for the next job

    Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S277 (2026-11-19), the recommendation he agreed to (the session's words, not his)

    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

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

    The record says

    The cards the xArm 850 handles are black and other primary colors, all with a metallic gleam. This project's program has one variant per card color, and the job's variant chooses the staging stack the card goes to.

    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: the station file step3/stations/s2-850.json lists the variants under 'variants', each naming its stack; their ids and stacks are labeled placeholders until the cards are named, 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 S276, the statement the colors were taken from.

    Evidence · 1 citation

    Card colors will be black and 0ther primary colors. They all seem to have a metallic gleam to it.

    Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S276 (2026-11-17, from the lab)

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

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

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

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

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

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

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

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

    The record says

    This project's program is split so the same logic drives a simulated arm and the real one: arm.py (the only module that imports UFACTORY's Python SDK), fake_arm.py (the same interface without the SDK), program.py (the state machine), events.py (the events and the run log), run.py (the command line) and a station file per arm; its unit tests run on the simulated arm. It needs Python 3.11 or later. With --live it drives the real arm, whose address is given as an argument or the XARM_IP environment variable, never in a file; --dry-run connects and reads but moves nothing; --step makes one move per press of Enter. Two tools move nothing: vacuum_test switches the vacuum on and off, and record_waypoint reads the arm's pose for a waypoint.

    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: the files named are in step3/, with step3/tools/vacuum_test.py, step3/tools/record_waypoint.py, step3/tests/ and step3/README.md (install and run instructions), 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 testing steps and S172, the decision to program in Python.

    Evidence · 3 citations

    Simulate or dry-run the program when 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 · '4. Test and Debug the Program', the numbered process

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

    Test individual steps at reduced speed or power.

    '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 · '4. Test and Debug the Program', the numbered process

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

    Blockly will not be used due to the freedom of programming we will need, so our coding will be in Python.

    Owner statements from 2026-09-24 onward (verbatim; S40 and later) · Derek Stringfellow · Statement S172 (2026-10-09)

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

  15. Confidence: Verifiedint-636

    The record says

    IntelliMake's course step 'Program Your Machine' asks each learner to program their assigned Phase 1 Factory machine to perform a defined manufacturing task safely and repeatably, with a deterministic machine-level program that may accept defined inputs and report status. Connecting the machine to an AI agent and to MIX belongs to the next step, 'Agentify Your Machine'.

    Evidence · 3 citations

    The purpose of this assignment is to develop the ability to program your assigned Phase 1 Factory machine to perform a defined manufacturing task safely and repeatably.

    '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 · 'Purpose', first paragraph

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

    The program may accept defined inputs and report status, but it does not need to interpret higher-level production goals, coordinate through MIX, or make autonomous decisions.

    '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 · 'Scope Boundary'

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

    Connecting the machine to an AI Agent and MIX will be addressed in Step 4

    '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 · 'Purpose', second paragraph

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

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

    The record says

    Limits of this project's program as built: without the camera it cannot tell which card it holds or whether the card is damaged; it handles one card per cycle, placed by hand in the corner stop while the arm is home; no command recovers from a fault; and it takes commands from one local operator, so accepting them over a network would need authentication and approval of the changed program.

    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 and step3/program.py, 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 the current limitations and S277, which took the camera out of the loop.

    Evidence · 2 citations

    Current limitations or integration gaps

    '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

    I do not think we can test with the camera for the assignment at this point.

    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

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 13 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 7 records here · Project copy; not published on this site.

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

All sources and attribution