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

Testing and Revisions

Test in order, from no motion to the full sequence, and write down every failure and what you changed. Faults that could damage the arm, the tool or a card are tried only on the simulated arm.

The Seven Steps

How Each Step Is Done
Course StepHow This Program Is Tested
Review the logicEvery state, step and fault code checked against the code; speeds, bounds and waypoints reviewed for unsafe motion and collisions123
Simulate or dry-runThe whole program on the simulated arm; then --dry-run on the real arm, which connects and reads but moves nothing14
Individual steps at reduced speed--step: one move per press of Enter14
Verify inputs, outputs, positions and parametersvacuum_test with no motion; each waypoint reached in step mode; Manual Mode left on must give NOT_READY145
The complete sequenceOne full cycle, a controlled pause and resume, a controlled stop, then two jobs in the wait-for-job mode167
Record errors and revisionsOne row per failure, with its cause, the change and the commit that made it1
Repeat for consistencyA job of several cycles, with the cycle times recorded18

Warning

Do not create a fault on the real arm to test the program. Faults that could damage equipment, materials or people are tested only on the simulated arm1.

Logged Results

Only results logged from a run or from the program's tests appear below. A test with no logged result is not listed.

The Program's Tests
#TestOn WhatResultDate
T8A no-camera job of three cyclesFake armPass (199 tests)2026-11-19
T9Wait-for-job mode: two jobs with READY between; START_JOB while running refused; pause and stop mid-job; only STATUS and SHUTDOWN after FAULT or STOP; SHUTDOWN while movingFake armPass (199 tests)2026-11-19
The Camera Extension's Tests
#TestOn WhatResultDate
V1Vision on drawn images (each color, rotated, at the edges, two cards, fold, tear, mark, depth)Lab unit testsPass (part of the 199)2026-11-19
Errors and Revisions
DateWhat FailedCauseCommit
2026-11-12The arm module's tests printed SDK_VERSION: 1.18.4 on standard output. On the arm it would have been the first line of the event stream, which must hold only JSON eventsThe SDK prints its version when it is imported (xarm/x3/base.py, line 55)67133ee
2026-11-12run.py --job variant=green,quantity=1 (no such variant) ended in FAULT CAMERA_ERROR, exit 2, not a refusalThe stand-in inspection for the variant was looked up before the job was checked67133ee
2026-11-12First run with package 03's vision on saved images: a two-card result was reported as NO_PART. The program logic says two cards is QC_REJECTThe program read present: false as "no card", whatever the reasons9b3f864
2026-11-12Writing the second lab visit's commands showed --live could never startIt refused every placeholder in the waypoints, pick, stacks and bounds, including program choices (the speed caps, the move timeout, the 1 mm press) that no visit makes taught or measureda69647f
2026-11-19Not a failure in a run: the camera works only on its 1 m cable, which would hang in the arm's way while it moves; longer cables will not arrive in timeHardware: no long camera cable130b203
2026-11-19Loading the xArm 6's file showed that, run on the xArm 6 without --station, the program would send it the 850's waypointsNothing compared the controller's model with the station file; the tool point and payload checks pass on both arms (same preset)b8cc423
2026-11-19The xArm 6's tool point and payload are assumptions (its five-cup tool is not documented), but --live did not list themOnly waypoints, pick area, stacks and bounds blocked --liveb8cc423
2026-11-19Pointed at the xArm 6's file, 77 of the suite's tests failedThe tests assumed the 850's stacks, joint ranges and positions, and a scan waypoint in every filefba734e, e9c8f77

Printed from https://www.anotherplace.com/learn/en/xarm-850/program/testing. 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-639

    The record says

    The course's testing process has seven steps: review the logic before enabling motion; simulate or dry-run the program; test individual steps at reduced speed or power; verify inputs, outputs, positions and parameters; test the complete sequence; record errors and program revisions; and repeat the operation to evaluate consistency. Faults that could damage equipment, materials or people are not introduced.

    Evidence · 8 citations

    Review the logic before enabling machine motion or processing.

    '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

    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

    Verify inputs, outputs, positions, and 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 · '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 the complete sequence.

    '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

    Record errors and program revisions.

    '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

    Repeat the operation to evaluate consistency.

    '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

    Do not introduce faults that could damage equipment, materials, or personnel.

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

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

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

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

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

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

  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

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

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

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 8 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 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 1 record 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