Public BOM audited. This is a source-bound system evidence record, not an independent rebuild.
Desktop arm · Seeed Studio reBot project
reBot B601 DM v1.1 production files
Versioned repository file tree · 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
reBot B601 DM v1.1 production files
reBot_B601_DM directory at reBot-DevArm commit a0c709638a341d6b12b005f22f5592c4b1579f56; selected file tree includes the v1.1 assemblies present at that commit.
Version state
Addressable source snapshot
The selected engineering surface is immutable at the cited commit or release asset. It is not a serial-numbered as-built robot manifest.
Lifecycle boundary
Changes remain attached to the source.
The responsibility-party changelog distinguishes v1.0 and v1.1. The profile does not treat the commercial shipping version as identical to this open-source developer boundary.
Responsibility party
Seeed Studio reBot project
RCI maps the named public responsibility party; inclusion does not imply endorsement, partnership or unit-level verification.
2 bounded lifecycle or procurement relations.
Replacement, upgrade, EOL and regional procurement signals remain separate from current availability and as-built identity.
revision-separation
reBot B601 DM / Damiao motor boundary → reBot B601 RS / RobStride motor boundary
The responsibility-party repository publishes separate DM and RS hardware directories and BOM links.
System impact: Motor, joint-interface, purchased-part and geometry identities cannot be assumed interchangeable across the two branches.
Open: RCI has not compared all same-named geometry files or performed a motor-branch conversion.
version-upgrade
reBot B601 DM v1.0 → reBot B601 DM v1.1
The responsibility-party changelog states v1.1 adds cable restraints, corrects Joint 1 model identity and adds a base reinforcement part.
System impact: Cable retention, base rigidity and exact joint-motor identity change within the DM branch.
Open: The file tree also contains two v1.1 assembly-date filenames; RCI has not measured their geometric delta.
Strongest supported conclusion
Versioned DM geometry plus four DM4310(V4), three DM4340P(V4), one generic CAN-to-USB board and four quantity-bounded XT30 2+2 harness variants, separated from the RobStride branch.
Largest rebuild gap: The source does not bind motors to joint numbers, publish the CAN board identity, freeze connector pinout/termination/IDs or provide wiring acceptance data, as-built serials or an RCI rebuild.
Editorial boundary: RCI normalizes only responsibility-party file identity, revision, engineering role and unresolved boundaries. The record is not a procurement BOM, unit manifest, successful rebuild, compatibility proof, endorsement or RCI hardware test.
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 | Partial | Useful information exists, but exactness, completeness or version binding remains incomplete. |
| Manufacturer part numbers | Partial | Useful information exists, but exactness, completeness or version binding remains incomplete. |
| Supplier links | Partial | Useful information exists, but exactness, completeness or version binding remains incomplete. |
| 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 | Partial | Useful information exists, but exactness, completeness or version binding remains incomplete. |
| 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. |
B601 DM production files plus selected motor, CAN-interface and XT30 2+2 harness rows
The count below preserves the responsibility party's publication structure; it is not silently flattened into unique purchasable components.
Selected count
65 rows / list items
Sixty-five responsibility-party records: 58 immutable production-file paths and seven selected purchased motor, controller and harness rows. File presence is not an installed quantity; table quantities remain responsibility-party claims rather than an as-built manifest.
Format
Versioned repository file tree
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.
6 bounded nodes and 5 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 for the DM CAN-to-USB path
The DM branch publishes a CAN-to-USB driver board, which establishes an external USB-host boundary without identifying one computer.
Identity boundary: Computer model, operating system, USB controller, SDK/ROS/LeRobot version, CAN software stack and physical host are not frozen.
Source rows: rebot-b601-dm-v11-item-03
control node
One generic DM CAN-to-USB driver board
One CAN-to-USB driver board in the fixed DM purchased-parts table.
Identity boundary: The table leaves the model blank; PCB revision, transceiver, firmware, USB identity, CAN bitrate, termination and connector pinout are not published.
Source rows: rebot-b601-dm-v11-item-03
actuation node
Four Damiao DM4310(V4) actuator positions
Four exact DM4310(V4) rows in the B601 DM purchased-parts table.
Identity boundary: Joint assignment, serials, firmware, CAN IDs, calibration, thermal state and physical installation are not published.
Source rows: rebot-b601-dm-v11-item-01
actuation node
Three Damiao DM4340P(V4) actuator positions
Three exact DM4340P(V4) rows in the B601 DM purchased-parts table.
Identity boundary: The source does not bind these positions to joint numbers or isolate the gripper motor; serials, firmware, CAN IDs, calibration and installed state are unknown.
Source rows: rebot-b601-dm-v11-item-02
power node
24 V DM input and seven XT30 2+2 harness boundary
The DM specification names 24 V supply and publishes seven XT30 2+2 cables across four length/end-orientation rows.
Identity boundary: Pinout, conductor gauge, polarity, connector ratings, branch-to-joint mapping, fuse/protection, termination and one installed cable set are not frozen; the separate supply subsystem remains a different RCI record.
Source rows: rebot-b601-dm-v11-item-04, rebot-b601-dm-v11-item-05, rebot-b601-dm-v11-item-06, rebot-b601-dm-v11-item-07
assembly node
Optional wrist-camera mounting surfaces
The root README presents UVC32, D435i, D405/Gemini 305 and Gemini 2 as optional camera-mount choices, with three selected DM STEP identities covering those mount surfaces.
Identity boundary: A mount filename is not an installed sensor record. In particular, D435_Gemini2_Mount.step supports two named options and does not prove that either a D435i or Gemini 2 was purchased, fitted, connected, calibrated or tested.
Source rows: rebot-b601-dm-v11-file-020, rebot-b601-dm-v11-file-021, rebot-b601-dm-v11-file-028
| From → to | Relation | Published support | Still unresolved |
|---|---|---|---|
| External host for the DM CAN-to-USB path → One generic DM CAN-to-USB driver boardbidirectional | data-controlUSB host to one generic CAN-to-USB driver board | The fixed DM purchased-parts table publishes one CAN-to-USB driver board; its named role supports a host-side USB to motor-side CAN boundary without identifying one board.Seeed-Projects/reBot-DevArm commit a0c709638a341d6b12b005f22f5592c4b1579f56 | Host, USB connector/mode, board SKU/revision, firmware, driver, CAN channel/bitrate, termination and captured traffic are not published. RCI has not enumerated the board or observed CAN frames.Physical validation: none. |
| One generic DM CAN-to-USB driver board → Four Damiao DM4310(V4) actuator positionsbidirectional | data-controlDM motor CAN/control path over published XT30 2+2 harnesses | The responsibility-party DM table jointly publishes the CAN-to-USB board, four DM4310(V4) motors and XT30 2+2 harness rows for the arm branch.Seeed-Projects/reBot-DevArm commit a0c709638a341d6b12b005f22f5592c4b1579f56 | The README does not freeze bus order, node IDs, bitrate, termination, pinout, cable-to-joint assignment, firmware or feedback configuration. RCI has not commanded or read a DM4310(V4).Physical validation: none. |
| One generic DM CAN-to-USB driver board → Three Damiao DM4340P(V4) actuator positionsbidirectional | data-controlDM motor CAN/control path over published XT30 2+2 harnesses | The responsibility-party DM table jointly publishes the CAN-to-USB board, three DM4340P(V4) motors and XT30 2+2 harness rows for the arm branch.Seeed-Projects/reBot-DevArm commit a0c709638a341d6b12b005f22f5592c4b1579f56 | Joint/gripper allocation, bus order, node IDs, bitrate, termination, pinout, cable assignment, firmware and feedback configuration are not frozen. RCI has not commanded or read a DM4340P(V4).Physical validation: none. |
| 24 V DM input and seven XT30 2+2 harness boundary → Four Damiao DM4310(V4) actuator positionssource-to-target | power24 V branch through XT30 2+2 arm harnesses | The DM specification names a 24 V supply and the purchased table publishes the DM4310(V4) motor bank plus the XT30 2+2 harness set.Seeed-Projects/reBot-DevArm commit a0c709638a341d6b12b005f22f5592c4b1579f56 | No pinout, gauge, fuse, branch map, load budget, voltage-drop, inrush, thermal or fault data is published or measured. RCI has not applied power.Physical validation: none. |
| 24 V DM input and seven XT30 2+2 harness boundary → Three Damiao DM4340P(V4) actuator positionssource-to-target | power24 V branch through XT30 2+2 arm harnesses | The DM specification names a 24 V supply and the purchased table publishes the DM4340P(V4) motor bank plus the XT30 2+2 harness set.Seeed-Projects/reBot-DevArm commit a0c709638a341d6b12b005f22f5592c4b1579f56 | No joint/gripper branch allocation, pinout, gauge, fuse, load budget, voltage-drop, inrush, thermal or fault data is published or measured. RCI has not applied power.Physical validation: none. |
65 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 |
|---|---|---|---|---|
| 01_Arm_Handle.stephardware/reBot_B601_DM/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/01_Arm_Handle.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 01_BASE_Link.stephardware/reBot_B601_DM/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/01_BASE_Link.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 01_BASE_Plate.stephardware/reBot_B601_DM/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/01_BASE_Plate.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 01_Finger.stephardware/reBot_B601_DM/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/01_Finger.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 01_Joint5_Cable Restraint_A.stephardware/reBot_B601_DM/3D_Printed_Parts | controlAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/01_Joint5_Cable Restraint_A.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 01_Joint6_7_Cable Restraint_A.stephardware/reBot_B601_DM/3D_Printed_Parts | controlAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/01_Joint6_7_Cable Restraint_A.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 01_Joint6_7_Cable Restraint_B.stephardware/reBot_B601_DM/3D_Printed_Parts | controlAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/01_Joint6_7_Cable Restraint_B.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 01_Lower_Arm_Cover.stephardware/reBot_B601_DM/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/01_Lower_Arm_Cover.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 01_Lower_Arm_Filler_L.stephardware/reBot_B601_DM/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/01_Lower_Arm_Filler_L.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 01_Lower_Arm_Filler_M.stephardware/reBot_B601_DM/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/01_Lower_Arm_Filler_M.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 01_Lower_Arm_Filler_R.stephardware/reBot_B601_DM/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/01_Lower_Arm_Filler_R.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 01_Lower_Arm_Limit.stephardware/reBot_B601_DM/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/01_Lower_Arm_Limit.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 01_Motor_Cover.stephardware/reBot_B601_DM/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/01_Motor_Cover.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 01_Rail_Bracket.stephardware/reBot_B601_DM/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/01_Rail_Bracket.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 01_Upper_Arm_Cover.stephardware/reBot_B601_DM/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/01_Upper_Arm_Cover.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 01_Upper_Arm_Fuller_L.stephardware/reBot_B601_DM/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/01_Upper_Arm_Fuller_L.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Assembly-level engineering definitionFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 01_Upper_Arm_Fuller_M.stephardware/reBot_B601_DM/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/01_Upper_Arm_Fuller_M.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Assembly-level engineering definitionFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 01_Upper_Arm_Fuller_R.stephardware/reBot_B601_DM/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/01_Upper_Arm_Fuller_R.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Assembly-level engineering definitionFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 01_Upper_Arm_Limit.stephardware/reBot_B601_DM/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/01_Upper_Arm_Limit.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| D405_305_Mount.stephardware/reBot_B601_DM/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/D405_305_Mount.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| D435_Gemini2_Mount.stephardware/reBot_B601_DM/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/D435_Gemini2_Mount.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| DM-power-Bottom Cover.stphardware/reBot_B601_DM/3D_Printed_Parts | controlAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/DM-power-Bottom Cover.stp | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| DM-power-Top Cover-Sliding Cover.stphardware/reBot_B601_DM/3D_Printed_Parts | controlAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/DM-power-Top Cover-Sliding Cover.stp | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| DM-power-Top Cover.stphardware/reBot_B601_DM/3D_Printed_Parts | controlAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/DM-power-Top Cover.stp | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| DM_Motor1_wiring_harness_clip.stphardware/reBot_B601_DM/3D_Printed_Parts | controlAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/DM_Motor1_wiring_harness_clip.stp | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| Soft_Gripper_Finger.stephardware/reBot_B601_DM/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/Soft_Gripper_Finger.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| Soft_Gripper_Mount.stephardware/reBot_B601_DM/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/Soft_Gripper_Mount.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| UVC32_mount.stephardware/reBot_B601_DM/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/3D_Printed_Parts/UVC32_mount.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 02-RACK.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/02-RACK.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 02_Arm_Yaw_Limit.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/02_Arm_Yaw_Limit.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 02_Base_Motor_Shim.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/02_Base_Motor_Shim.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 02_Base_Reinforcement_Part.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/02_Base_Reinforcement_Part.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 02_FLANGE.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/02_FLANGE.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 02_Gear_Connector.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/02_Gear_Connector.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 02_Gripper_Connector_A.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/02_Gripper_Connector_A.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 02_Gripper_Connector_B.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/02_Gripper_Connector_B.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 02_Lower_Upper_Link_L.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/02_Lower_Upper_Link_L.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 02_Lower_Upper_Link_R.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/02_Lower_Upper_Link_R.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 02_Lower_Wrist_Link_L.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/02_Lower_Wrist_Link_L.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 02_Lower_Wrist_Link_R.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/02_Lower_Wrist_Link_R.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 02_Motor_Back_Spacer.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/02_Motor_Back_Spacer.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 02_Motor_Front_Spacer.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/02_Motor_Front_Spacer.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 02_Rack.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/02_Rack.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 02_Slider_Bracket.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/02_Slider_Bracket.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 02_Slider_Extension.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/02_Slider_Extension.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 02_Wrist_Bracket.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/02_Wrist_Bracket.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 03-Link1.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/03-Link1.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 03-Link2.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/03-Link2.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 03-Link3_L.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/03-Link3_L.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 03-Link3_R.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/03-Link3_R.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 03-Link5.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/03-Link5.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 03_Link1.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/03_Link1.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 03_Link2.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/03_Link2.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 03_Link3_L.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/03_Link3_L.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 03_Link3_R.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/03_Link3_R.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| 03_Link5.stephardware/reBot_B601_DM/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/Metal_Parts/03_Link5.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| reBot_B601_DM_v1.1_20260425.stephardware/reBot_B601_DM | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/reBot_B601_DM_v1.1_20260425.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| reBot_B601_DM_v1.1_20260625.stephardware/reBot_B601_DM | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_DM/reBot_B601_DM_v1.1_20260625.step | Not publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity. | Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system. |
| Damiao DM4310(V4) brushless motorB601 DM purchased parts and XT30 2+2 harness rows | actuationInstalled / build item | variant-namedDM4310(V4) | 4 unitFour DM4310(V4) motors are published in the responsibility-party DM table. | DM-branch joint actuationNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot. |
| Damiao DM4340P(V4) brushless motorB601 DM purchased parts and XT30 2+2 harness rows | actuationInstalled / build item | variant-namedDM4340P(V4) | 3 unitThree DM4340P(V4) motors are published; the selected table does not bind each motor model to a numbered joint. | DM-branch joint and gripper actuationNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot. |
| DM CAN-to-USB driver boardB601 DM purchased parts and XT30 2+2 harness rows | controlInstalled / build item | generic-descriptionNo exact identity published | 1 unitOne CAN-to-USB driver board is published without an exact board model or revision in the table. | External-host to DM motor-bus interfaceNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot. |
| XT30 2+2 harness — 350 mm, both ends angledB601 DM purchased parts and XT30 2+2 harness rows | cableInstalled / build item | variant-namedXT30 2+2 / 350 mm / two angled ends | 2 unitTwo cables are published for this exact length and end-orientation row. | Combined motor power and communication harnessNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot. |
| XT30 2+2 harness — 350 mm, one angled and one straight endB601 DM purchased parts and XT30 2+2 harness rows | cableInstalled / build item | variant-namedXT30 2+2 / 350 mm / mixed ends | 1 unitOne cable is published for this exact length and end-orientation row. | Combined motor power and communication harnessNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot. |
| XT30 2+2 harness — 200 mm, both ends angledB601 DM purchased parts and XT30 2+2 harness rows | cableInstalled / build item | variant-namedXT30 2+2 / 200 mm / two angled ends | 3 unitThree cables are published for this exact length and end-orientation row. | Combined motor power and communication harnessNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot. |
| XT30 2+2 harness — 200 mm, both ends straightB601 DM purchased parts and XT30 2+2 harness rows | cableInstalled / build item | variant-namedXT30 2+2 / 200 mm / two straight ends | 1 unitOne cable is published for this exact length and end-orientation row. | Combined motor power and communication harnessNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot. |
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.
reBot B601 DM production-file tree ↗
58 STEP/STL production files plus seven selected purchased-interface and harness rows from the fixed DM README
reBot_B601_DM directory at reBot-DevArm commit a0c709638a341d6b12b005f22f5592c4b1579f56; selected file tree includes the v1.1 assemblies present at that commit.Correction 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 →