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

Performance

A program that works once is not finished. Run it for several cycles and judge it on what the logs show, not on what it looked like.

What Is Evaluated

  • Run the task for multiple cycles, when that makes sense, and evaluate task completion, repeatability, cycle time, output quality, positioning accuracy, the operator intervention needed, the response to safe stops and expected errors, and readiness for the factory1.

Where the Figures Come From

  • Each CYCLE_COMPLETE carries the cycle's time, and JOB_COMPLETE closes the job2.
  • Every event is kept, one JSON line each, in the run's log file: results are taken from those logs3.
  • Each stop and fault is an event with its code and the step it happened in, so interventions can be counted456.

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

Provenance

References · 6

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

    The record says

    The course asks for the programmed task to be run for multiple cycles, when appropriate, and evaluated for task completion, repeatability, cycle time, output quality, positioning or process accuracy, the operator intervention required, the response to safe stops or expected errors, and readiness for integration into the Phase 1 Factory.

    Evidence · 9 citations

    Run the programmed task for multiple cycles, when appropriate, and evaluate:

    '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 · '5. Verify Program Performance'

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

    Task completion

    '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 · '5. Verify Program Performance', the list

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

    Repeatability

    '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 · '5. Verify Program Performance', the list

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

    Cycle time

    '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 · '5. Verify Program Performance', the list

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

    Output quality

    '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 · '5. Verify Program Performance', the list

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

    Positioning or process accuracy

    '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 · '5. Verify Program Performance', the list

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

    Operator intervention required

    '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 · '5. Verify Program Performance', the list

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

    Response to safe stops or expected errors

    '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 · '5. Verify Program Performance', the list

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

    Readiness for integration into the Phase 1 Factory

    '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 · '5. Verify Program Performance', the list

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

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

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

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

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