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

Run It Yourself

Start on the simulated arm, where nothing can be hurt. Move to the real arm only with approval, and then one step at a time.

Warning

Run anything on the real arm only with the instructor's approval of this program version, the operating checklist done, and a hand within reach of the emergency stop on the control box12.

Install

  1. Install Python 3.11 or later3.
  2. Install UFACTORY's Python SDK: pip install xarm-python-sdk4.
  3. Get the program's folder, step3/, with its station file and tests3.
  4. Run its tests, which use the simulated arm: python -m unittest discover -s step3/tests -t .3.

On the Simulated Arm

  1. One job: python -m step3.run --no-camera --job variant=black,quantity=353.
  2. Wait for jobs: python -m step3.run --no-camera --serve, then type start black 35.
  3. While it runs, try p to pause, r to resume, status, s to stop, and quit5.

On the Real Arm

  1. In Studio: no error, Manual Mode off, and the Vacuum Gripper tool preset selected67.
  2. Give the arm's address in the XARM_IP environment variable or as an argument, never in a file3.
  3. Dry run, which moves nothing: python -m step3.run --live --no-camera --dry-run3.
  4. Vacuum on and off, with no motion: python -m step3.tools.vacuum_test --live3.
  5. One cycle, one move per press of Enter: python -m step3.run --live --no-camera --step --job variant=black,quantity=135.
  6. One full cycle without --step, then the wait-for-job mode with --serve5.

The program refuses the real arm while a waypoint, the pick area, a stack, the floor, the workspace or a joint range is still a placeholder, and lists what is missing8.

Teaching a Waypoint

  • Jog the arm in Studio, or guide it by hand in Manual Mode, then read the pose with python -m step3.tools.record_waypoint pick --live. The tool reads and never moves the arm3.
  • Switch Manual Mode off before any run: the program refuses to start in it6.

What the Exit Code Means

0: it ended at READY or the job completed. 2: FAULT. 3: STOPPED. 4: it refused to start5.

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

Provenance

References · 8

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

  2. Confidence: Verifiedcomp-024

    The record says

    The 850's emergency stop button is on the control box. Pressing it makes the control box decelerate the arm in software, stop all motion and clear cached commands, then remove power from the arm within 300 ms.

    Evidence · 1 citation

    Quote not shown (over 40 words). See the source at: 2.1.2 Emergency Stop Button (docs site 'UFACTORY 850 硬件手册', English version; names the machine 'UFACTORY 850').

    UFACTORY 850 Hardware Manual (online), 2. Hardware Installation · UFACTORY · 2.1.2 Emergency Stop Button (docs site 'UFACTORY 850 硬件手册', English version; names the machine 'UFACTORY 850')

    © UFACTORY · All rights reserved; quoted briefly as evidence · retrieved 2026-09-21

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

  4. Confidence: Verifiediface-010

    The record says

    The Python SDK (xArm-Python-SDK) is installed from PyPI with 'pip install xarm-python-sdk' and supports Python 3 only.

    Evidence · 2 citations

    pip install xarm-python-sdk

    xArm-Python-SDK README · UFACTORY · Installation, 'Install from pypi'

    © UFACTORY Inc., xArm-Developer/xArm-Python-SDK, BSD 3-Clause License · BSD-3-Clause · retrieved 2026-09-21

    Only Python 3 is supported.

    xArm-Python-SDK README · UFACTORY · Installation

    © UFACTORY Inc., xArm-Developer/xArm-Python-SDK, BSD 3-Clause License · BSD-3-Clause · retrieved 2026-09-21

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

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

  7. Confidence: VerifiedAwaiting cell accessops-210

    The record says

    On 2026-10-22, on firmware 2.8.2, the xArm 850's controller held the TCP preset Vacuum Gripper: a payload of 0.61 kg with its center of gravity 53 mm along z, and a tool point 126 mm along z from the flange, with no other offset or rotation. These are the settings someone entered, not a measurement of the tool.

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

    Reasoning: Verified as a direct reading of the xArm 850's controller on 2026-10-22 (Studio's TCP page, 'Real' selected, firmware 2.8.2). The figures equal UFACTORY's Vacuum Gripper preset (ops-092). Nothing was weighed or measured; no inspection of the tool is recorded.

    Evidence · 5 citations

    Preset selected | Vacuum Gripper

    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, 'Preset selected' row

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

    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

    Roll 0°, Pitch 0°, Yaw 0°

    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, after the tool point

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

    that the preset's figures match the physical tool (a controller setting is what someone entered, not a measurement)

    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, 'Not settled'

    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

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 5 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.
  • UFACTORY 850 Hardware Manual (online), 2. Hardware Installation · UFACTORY (manufacturer)
    © UFACTORY · All rights reserved; quoted briefly as evidence · retrieved 2026-09-21 · cited by 1 record here · Open the source
  • UFACTORY 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.
  • xArm-Python-SDK README · UFACTORY (manufacturer)
    © UFACTORY Inc., xArm-Developer/xArm-Python-SDK, BSD 3-Clause License · BSD-3-Clause · retrieved 2026-09-21 · cited by 1 record here · Open the source

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

All sources and attribution