Public BOM audited. This is a source-bound system evidence record, not an independent rebuild.
Desktop arm · AM-ARM project / Yi-Teng Li
AM-ARM200 leader / follower pair
Markdown table · commit-addressable.
No complete rebuild evidence package found.
The robot name is not the version boundary.
RCI preserves the exact source surface and revision conditions instead of applying one prototype or current product page to every unit.
Platform boundary
AM-ARM200 leader / follower pair
AM-ARM200 follower arm, leader arm and optional camera rows at repository commit 5b03af1ef6c80595bd988e0137cf8e7c35811eb6; the source describes an upgrade path from SO-100/SO-101 but does not establish drop-in compatibility for every prior build.
Version state
Addressable source snapshot
The BOM is pinned to a repository commit but not to a numbered AM-ARM200 hardware release or a serialised unit manifest.
Lifecycle boundary
Changes remain attached to the source.
The responsibility party says existing SO-100/SO-101 users can upgrade by adding missing parts; RCI records this as a project statement, not independently verified compatibility or a complete upgrade delta.
Responsibility party
AM-ARM project / Yi-Teng Li
RCI maps the named public responsibility party; inclusion does not imply endorsement, partnership or unit-level verification.
No structured lifecycle relation selected yet.
Replacement, upgrade, EOL and regional procurement signals remain separate from current availability and as-built identity.
No positive lifecycle claim.
Absence here means the selected source set does not yet support one, not that the platform has no revisions or supply risk.
Strongest supported conclusion
Exact servo voltage and gear variants, quantities, regional procurement links, follower/leader separation, and linked STL/STP production-file directories under an Apache-2.0 repository license.
Largest rebuild gap: No release-tagged as-built manifest, wiring/net definition, controller firmware binding, validated upgrade delta or independent physical rebuild closes the published list.
Responsibility-source conflict: The leader-arm heat-set-insert row publishes Qty 4 while its note says “total 36 pcs (Servo Mount×24, Side Panel×12)”. RCI preserves both statements and does not choose one.
Editorial boundary: The record establishes what the selected project BOM publishes. It does not establish retailer availability, price currency, electrical safety, upgrade compatibility, or that a physical leader/follower pair was built from this exact snapshot.
Twelve gates separate a parts list from a rebuild package.
Partial means a source contains useful material but does not close the exact revision, quantity, part identity or unit-level boundary.
| Evidence dimension | State | What the state means here |
|---|---|---|
| Exact platform revision | Published | The selected responsibility-party surface publishes this dimension inside the recorded boundary. |
| Versioned BOM snapshot | Partial | Useful information exists, but exactness, completeness or version binding remains incomplete. |
| Line-item quantities | Published | The selected responsibility-party surface publishes this dimension inside the recorded boundary. |
| Manufacturer part numbers | Partial | Useful information exists, but exactness, completeness or version binding remains incomplete. |
| Supplier links | Published | The selected responsibility-party surface publishes this dimension inside the recorded boundary. |
| Custom-part production files | Published | The selected responsibility-party surface publishes this dimension inside the recorded boundary. |
| Electrical interconnect definition | Partial | Useful information exists, but exactness, completeness or version binding remains incomplete. |
| Software / firmware binding | Not published | The selected sources do not publish this evidence dimension. |
| License boundary | Published | The selected responsibility-party surface publishes this dimension inside the recorded boundary. |
| Change, EOL and substitution history | Partial | Useful information exists, but exactness, completeness or version binding remains incomplete. |
| Unit-level as-built manifest | Not published | The selected sources do not publish this evidence dimension. |
| Independent rebuild evidence | Not published | The selected sources do not publish this evidence dimension. |
AM-ARM200 Bill of Materials: Follower Arm, Leader Arm and Optional tables
The count below preserves the responsibility party's publication structure; it is not silently flattened into unique purchasable components.
Selected count
18 rows / list items
Nine follower-arm rows, six leader-arm rows and three optional-camera rows. Source totals are price totals, not installed-unit totals. The optional rows remain separate from the base leader/follower boundary.
Format
Markdown table
RCI did not treat the publication format as a normalized database table.
Next evidence gate
Normalize without inventing.
Resolve exact part identity, quantity scope, placement, revision and substitution state while retaining nested assemblies, alternatives and generic groups as explicit boundaries.
As-built state
Not published
A public list does not establish what one serialised unit actually contained.
No manufacturer identity is safely linked from the selected rows.
These are responsibility-party BOM mentions, not partnership, endorsement, verified supply or exact-component equivalence.
Generic or unregistered identities remain unlinked.
RCI will add a relationship only after the source publishes a manufacturer identity that maps unambiguously to the directory.
7 bounded nodes and 6 source-supported interface relations.
RCI publishes a connection only when the selected responsibility-party source explicitly supports the endpoints or architecture. A BOM co-occurrence, component capability or engineering convention is not enough.
external-host node
External host computer
Computer used to configure and operate the AM-ARM200 pair; no exact host is listed in the selected BOM.
Identity boundary: Host SKU, operating system, USB controller, software environment and physical identity are not frozen by the hardware BOM.
Source rows: Architecture text only; no BOM row.
control node
Follower Waveshare Bus Servo Controller
One Bus Servo Adapter (A) assigned to the 12 V follower arm.
Identity boundary: Controller hardware revision, firmware, USB descriptor, cable construction and serial are not published.
Source rows: am-arm200-follower-controller, am-arm200-follower-usbc
actuation node
Seven-servo 12 V follower bus
Four STS3215 plus three STS3095 servos, joint IDs 1–7, at the pinned hardware revision.
Identity boundary: Servo serials, calibrated offsets, exact daisy-chain order, individual cable placement and loaded-voltage behavior are not frozen.
Source rows: am-arm200-follower-sts3215, am-arm200-follower-sts3095, am-arm200-follower-servo-extension
power node
Follower 12 V / 4 A / 48 W supply
Follower-only external supply selected by the pinned BOM.
Identity boundary: The BOM gives electrical headline values but does not independently freeze connector polarity, protection, regulatory variant or observed output.
Source rows: am-arm200-follower-power
control node
Leader Waveshare Bus Servo Controller
One Bus Servo Adapter (A) assigned to the 5 V leader arm.
Identity boundary: Controller hardware revision, firmware, USB descriptor, cable construction and serial are not published.
Source rows: am-arm200-leader-controller, am-arm200-leader-usbc
actuation node
Seven-servo 5 V leader bus
Seven STS3215 5 V 1/147 servos, IDs 1–7; responsibility-party instructions require phase 12 to reset factory multi-turn configuration to single-turn.
Identity boundary: Servo serials, EEPROM state, calibrated offsets, exact daisy-chain order, cables and physical phase confirmation are not frozen.
Source rows: am-arm200-leader-sts3215
power node
Leader 5 V external supply
Leader-only external supply; the detailed BOM does not publish a current rating.
Identity boundary: Supply SKU, current rating, connector, polarity, protection, regulatory variant and observed output are not published.
Source rows: am-arm200-leader-power
| From → to | Relation | Published support | Still unresolved |
|---|---|---|---|
| External host computer → Follower Waveshare Bus Servo Controllerbidirectional | data-controlUSB Type-C host link to follower Bus Servo Controller | The pinned assembly guide requires the servo controller to be connected to a computer by USB-C for ID configuration and mounts a dedicated controller on the follower base.liyiteng/AM-ARM commit 5b03af1ef6c80595bd988e0137cf8e7c35811eb6 | Host and USB port, cable data capability, device path, controller descriptor, permissions, firmware and communication latency are not frozen. RCI has not enumerated this controller.Physical validation: none. |
| Follower Waveshare Bus Servo Controller → Seven-servo 12 V follower busbidirectional | data-controlFeetech STS bus to seven follower servos, IDs 1–7; typical setup baud 1,000,000 | The pinned guide configures servo IDs one-by-one through the Waveshare controller, publishes a typical 1,000,000 baud setup and identifies seven follower joints; the pinned README fixes four STS3215 plus three STS3095 roles.liyiteng/AM-ARM commit 5b03af1ef6c80595bd988e0137cf8e7c35811eb6 | The guide calls 1,000,000 a typical baud, not an as-built readback; exact bus order, per-servo EEPROM, offsets, cable topology, packet errors and timing remain unverified. RCI has not scanned or moved this bus.Physical validation: none. |
| Follower 12 V / 4 A / 48 W supply → Seven-servo 12 V follower bussource-to-target | power12 V / 4 A / 48 W follower supply through servo controller | The pinned README assigns a 12 V 4 A supply and dedicated controller to the follower, while the detailed BOM identifies 12 V STS3215/STS3095 actuator variants.liyiteng/AM-ARM commit 5b03af1ef6c80595bd988e0137cf8e7c35811eb6 | Connector dimensions/polarity, distribution layout, protection, grounding, current margin, startup transient and measured loaded voltage are not independently fixed. The 12 V branch must not be joined to the 5 V leader branch; RCI has not energized it.Physical validation: none. |
| External host computer → Leader Waveshare Bus Servo Controllerbidirectional | data-controlUSB Type-C host link to leader Bus Servo Controller | The pinned assembly guide explicitly connects the leader controller to a PC by USB-C during configuration and mounts a dedicated controller on the leader base.liyiteng/AM-ARM commit 5b03af1ef6c80595bd988e0137cf8e7c35811eb6 | The pinned hardware repository points software setup to a separate moving repository; no software commit is silently bound to this hardware snapshot. Host, device path, cable, descriptor, permissions, firmware and actual enumeration remain unverified.Physical validation: none. |
| Leader Waveshare Bus Servo Controller → Seven-servo 5 V leader busbidirectional | data-controlFeetech STS bus to seven leader servos, IDs 1–7; phase 12 single-turn reset | The pinned guide publishes the leader IDs 1–7, says the 5 V 1/147 servos ship in multi-turn mode and instructs setting phase to 12 before checking states.liyiteng/AM-ARM commit 5b03af1ef6c80595bd988e0137cf8e7c35811eb6 | No per-servo readback, serial, phase/EEPROM capture, ordered cable map, calibration offsets, packet timing or state log is published for one assembled pair. RCI has not configured or scanned this bus.Physical validation: none. |
| Leader 5 V external supply → Seven-servo 5 V leader bussource-to-target | powerDedicated 5 V leader supply through servo controller | The pinned guide labels the leader arm 5 V and requires its 5 V supply at the controller; the selected BOM fixes seven STS3215 5 V 1/147 units.liyiteng/AM-ARM commit 5b03af1ef6c80595bd988e0137cf8e7c35811eb6 | The detailed BOM omits current rating; supply SKU, connector, polarity, protection, ground relationship, current margin and loaded voltage remain unknown. This branch must remain electrically distinct from the follower 12 V branch; RCI has not energized it.Physical validation: none. |
18 source items converted into claim-bounded records.
Identity, quantity and installed-hardware boundaries remain separate fields; a generic source label is never promoted to an exact orderable model.
| Source item | Class | Identity | Quantity boundary | Role + unresolved evidence |
|---|---|---|---|---|
| Servo motor — Feetech STS3215AM-ARM200 Bill of Materials / Follower Arm | actuationInstalled / build item | variant-namedFeetech · STS3215 · 12 V · 1/345 | 4 unit4 units published inside the Follower Arm table. This is a source-row quantity, not an as-built count. | Follower-arm actuationNo unit-level as-built manifest or independent rebuild record confirms this item on one physical AM-ARM200 pair. |
| Servo motor — Feetech STS3095AM-ARM200 Bill of Materials / Follower Arm | actuationInstalled / build item | variant-namedFeetech · STS3095 · 12 V · 1/345 | 3 unit3 units published inside the Follower Arm table. This is a source-row quantity, not an as-built count. | Higher-load follower-arm actuationNo unit-level as-built manifest or independent rebuild record confirms this item on one physical AM-ARM200 pair. |
| Hex socket screw M3×10AM-ARM200 Bill of Materials / Follower Arm | fastenerInstalled / build item | variant-namedM3×10 · Follower Arm | 74 unit74 units published inside the Follower Arm table. This is a source-row quantity, not an as-built count. | Follower-arm structural fasteningNo unit-level as-built manifest or independent rebuild record confirms this item on one physical AM-ARM200 pair. |
| Heat-set insert M3×5×4AM-ARM200 Bill of Materials / Follower Arm | fastenerInstalled / build item | variant-namedM3×5×4 · Follower Arm | 4 unit4 units published inside the Follower Arm table. This is a source-row quantity, not an as-built count. | Follower-arm threaded insertThe row does not explain whether quantity 4 means units, packs or another purchase boundary. |
| Servo extension cable SCS 3-pinAM-ARM200 Bill of Materials / Follower Arm | cableInstalled / build item | variant-namedSCS 3-pin cable · 26 cm | 6 unit6 units published inside the Follower Arm table. This is a source-row quantity, not an as-built count. | Follower servo-bus extensionNo unit-level as-built manifest or independent rebuild record confirms this item on one physical AM-ARM200 pair. |
| DC 12 V 4 A 48 W AC adapterAM-ARM200 Bill of Materials / Follower Arm | powerInstalled / build item | variant-namedDC 12 V 4 A 48 W AC adapter · 12 V · 4 A · 48 W | 1 unit1 unit published inside the Follower Arm table. This is a source-row quantity, not an as-built count. | Follower-arm external powerConnector dimensions and polarity are represented only by a selected retailer target, not by an RCI-verified electrical specification. |
| USB Type-C cableAM-ARM200 Bill of Materials / Follower Arm | cableInstalled / build item | generic-descriptionFollower Arm | 1 unit1 unit published inside the Follower Arm table. This is a source-row quantity, not an as-built count. | Follower controller-to-host cableConnector pair, data capability, length and current rating are not published in the row. |
| Waveshare Bus Servo ControllerAM-ARM200 Bill of Materials / Follower Arm | controlInstalled / build item | variant-namedWaveshare · Bus Servo Adapter (A) · Follower Arm | 1 unit1 unit published inside the Follower Arm table. This is a source-row quantity, not an as-built count. | Follower host-to-servo interfaceThe BOM row does not bind a hardware revision, firmware version or electrical configuration. |
| 3D-printed partsAM-ARM200 Bill of Materials / Follower Arm | custom-mechanicalInstalled / build item | file-identifiedam-arm200/stl/ and am-arm200/stp/ · PLA / PETG / ABS alternatives | 1 unitOne aggregate printed-parts row is published. It is not a flattened count of individual printable parts. | Follower-arm custom structureMaterial is an alternative, not a selected as-built value. Per-file quantity, print orientation, process and revision manifest are not published in the BOM table. |
| Servo motor — Feetech STS3215AM-ARM200 Bill of Materials / Leader Arm | actuationInstalled / build item | variant-namedFeetech · STS3215 · 5 V · 1/147 | 7 unit7 units published inside the Leader Arm table. This is a source-row quantity, not an as-built count. | Leader-arm actuationNo unit-level as-built manifest or independent rebuild record confirms this item on one physical AM-ARM200 pair. |
| Heat-set insert M3×5×4AM-ARM200 Bill of Materials / Leader Arm | fastenerInstalled / build item | variant-namedM3×5×4 · Leader Arm | 4 unitThe Qty column publishes 4, while the same row note says “total 36 pcs (Servo Mount×24, Side Panel×12)”. RCI preserves the conflict and does not convert either value. | Leader-arm threaded insertResponsibility-source quantity conflict: Qty 4 versus note total 36 pcs. It is unresolved whether 4 represents packs, a stale value or another procurement boundary. |
| DC 5 V AC adapterAM-ARM200 Bill of Materials / Leader Arm | powerInstalled / build item | variant-namedDC 5 V AC adapter · 5 V | 1 unit1 unit published inside the Leader Arm table. This is a source-row quantity, not an as-built count. | Leader-arm external powerCurrent rating, connector dimensions and polarity are not published in the row. |
| USB Type-C cableAM-ARM200 Bill of Materials / Leader Arm | cableInstalled / build item | generic-descriptionLeader Arm | 1 unit1 unit published inside the Leader Arm table. This is a source-row quantity, not an as-built count. | Leader controller-to-host cableConnector pair, data capability, length and current rating are not published in the row. |
| Waveshare Bus Servo ControllerAM-ARM200 Bill of Materials / Leader Arm | controlInstalled / build item | variant-namedWaveshare · Bus Servo Adapter (A) · Leader Arm | 1 unit1 unit published inside the Leader Arm table. This is a source-row quantity, not an as-built count. | Leader host-to-servo interfaceThe BOM row does not bind a hardware revision, firmware version or electrical configuration. |
| 3D-printed partsAM-ARM200 Bill of Materials / Leader Arm | custom-mechanicalInstalled / build item | file-identifiedam-arm200/stl/ and am-arm200/stp/ · PLA / PETG / ABS alternatives | 1 unitOne aggregate printed-parts row is published. It is not a flattened count of individual printable parts. | Leader-arm custom structureMaterial is an alternative, not a selected as-built value. Per-file quantity, print orientation, process and revision manifest are not published in the BOM table. |
| USB cameraAM-ARM200 Bill of Materials / Optional | sensorAlternative / not simultaneously installed | variant-namedUSB camera · 720p · 36×36 mm form factor | 1 unit1 unit published inside the Optional table. This is a source-row quantity, not an as-built count. | Optional visual sensingNo exact camera manufacturer, model, sensor, lens, interface mode or mounting calibration is published. |
| M2×12 Phillips screwAM-ARM200 Bill of Materials / Optional | fastenerAlternative / not simultaneously installed | variant-namedM2×12 · Optional | 2 unit2 units published inside the Optional table. This is a source-row quantity, not an as-built count. | Optional camera-mount fasteningNo unit-level as-built manifest or independent rebuild record confirms this item on one physical AM-ARM200 pair. |
| Bearing 12×18×4 mmAM-ARM200 Bill of Materials / Optional | bearingAlternative / not simultaneously installed | variant-named6701-2RS class / 12×18×4 mm · Optional | 2 unit2 units published inside the Optional table. This is a source-row quantity, not an as-built count. | Optional camera-mount bearingThe row dimensions are published, but the generic item name does not independently bind a manufacturer or exact tolerance class. |
Every conclusion returns to a selected source.
Links point to the responsibility party's material. RCI does not republish third-party BOM rows, CAD or retailer content through this profile.
AM-ARM200 Bill of Materials ↗
Follower Arm, Leader Arm and Optional line items, quantities, variants, regional links and printed-part directories
Commit 5b03af1 · verified 2026-08-13AM-ARM hardware repository ↗
Project identity, AM-ARM200 hardware tree, STL/STP files and repository license
Commit 5b03af1 · Apache-2.0Correction path
Know a newer revision or an exact as-built record?
Corrections must identify the platform revision, source location and the exact field affected. Manufacturer or project-party clarification is displayed alongside independently sourced evidence without replacing the original boundary.
Send a documented correction →