Public BOM audited. This is a source-bound system evidence record, not an independent rebuild.
Desktop arm · Seeed Studio reBot project
reBot B601 RS v1.0 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 RS v1.0 production files
reBot_B601_RS directory at reBot-DevArm commit a0c709638a341d6b12b005f22f5592c4b1579f56.
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 RobStride and Damiao motor versions remain separate platform boundaries; shared-looking part names are not asserted equivalent.
Responsibility party
Seeed Studio reBot project
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
Commit-addressable RS geometry plus four RS00, three RS06, one generic CAN-to-USB board, one power-separation board, four minimum-quantity harness variants and one explicitly optional LRS-600-48 source.
Largest rebuild gap: The source does not bind motors to joint numbers, identify the CAN board, freeze power-separation circuitry/pinout, resolve every “+” harness quantity or provide supplier lots, an as-built manifest or RCI physical 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 RS production files plus selected motor, CAN-interface, power-separation, harness and optional-supply rows
The count below preserves the responsibility party's publication structure; it is not silently flattened into unique purchasable components.
Selected count
54 rows / list items
Fifty-four responsibility-party records: 45 immutable production-file paths and nine selected motor, controller, power-separation, harness and optional-supply rows. Minimum “1+” and “4+” quantities stay minimums, and the supply remains optional rather than installed-by-default.
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 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 for the RS CAN-to-USB path
The RS 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, software stack and physical host are not frozen.
Source rows: rebot-b601-rs-v10-item-03
control node
One generic RS CAN-to-USB driver board
One CAN-to-USB driver board in the fixed RS purchased-parts table.
Identity boundary: The table leaves the model blank; PCB revision, firmware, USB identity, transceiver, CAN bitrate, termination and connector pinout are not frozen.
Source rows: rebot-b601-rs-v10-item-03
actuation node
Four RobStride RS00 actuator positions
Four exact RobStride RS00 rows in the B601 RS purchased-parts table.
Identity boundary: Joint assignment, serials, firmware, CAN IDs, calibration, thermal state and physical installation are not published.
Source rows: rebot-b601-rs-v10-item-01
actuation node
Three RobStride RS06 actuator positions
Three exact RobStride RS06 rows in the B601 RS 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-rs-v10-item-02
power node
XT30 2+2 power-separation board and RS harness boundary
One power-separation board and four minimum-quantity XT30 2+2 cable variants in the fixed RS table.
Identity boundary: Board circuitry/revision, pinout, protection, connector ratings, branch-to-joint map and final quantities behind “1+” or “4+” remain unresolved.
Source rows: rebot-b601-rs-v10-item-04, rebot-b601-rs-v10-item-05, rebot-b601-rs-v10-item-06, rebot-b601-rs-v10-item-07, rebot-b601-rs-v10-item-08
power node
Optional LRS-600-48 external supply path
The RS arm ships without a power supply by default; the selected README presents one 48 V / 12.5 A LRS-600-48 path, while the root README separately mentions a stronger 48 V / 25 A option.
Identity boundary: This is an optional source selection, not standard installed equipment. Mains region, wiring, safety acceptance, output setting, protection coordination, 25 A alternative and physical identity are not validated.
Source rows: rebot-b601-rs-v10-item-09
| From → to | Relation | Published support | Still unresolved |
|---|---|---|---|
| External host for the RS CAN-to-USB path → One generic RS CAN-to-USB driver boardbidirectional | data-controlUSB host to one generic CAN-to-USB driver board | The fixed RS purchased-parts table publishes one CAN-to-USB driver board, supporting a host-side USB to motor-side CAN boundary without fixing one board identity.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 RS CAN-to-USB driver board → Four RobStride RS00 actuator positionsbidirectional | data-controlRobStride control/feedback path over the RS XT30 2+2 harness surface | The responsibility-party RS table jointly publishes the CAN-to-USB board, four RS00 motors and four XT30 2+2 harness variants.Seeed-Projects/reBot-DevArm commit a0c709638a341d6b12b005f22f5592c4b1579f56 | Bus order, joint allocation, node IDs, bitrate, termination, pinout, cable assignment, firmware and feedback configuration are not frozen. RCI has not commanded or read an RS00.Physical validation: none. |
| One generic RS CAN-to-USB driver board → Three RobStride RS06 actuator positionsbidirectional | data-controlRobStride control/feedback path over the RS XT30 2+2 harness surface | The responsibility-party RS table jointly publishes the CAN-to-USB board, three RS06 motors and four XT30 2+2 harness variants.Seeed-Projects/reBot-DevArm commit a0c709638a341d6b12b005f22f5592c4b1579f56 | Bus order, joint/gripper allocation, node IDs, bitrate, termination, pinout, cable assignment, firmware and feedback configuration are not frozen. RCI has not commanded or read an RS06.Physical validation: none. |
| Optional LRS-600-48 external supply path → XT30 2+2 power-separation board and RS harness boundarysource-to-target | powerOptional 48 V source into the XT30 2+2 separation/harness surface | The RS README says the arm ships without a supply, presents one optional 48 V / 12.5 A source, and publishes one XT30 2+2 power separation board.Seeed-Projects/reBot-DevArm commit a0c709638a341d6b12b005f22f5592c4b1579f56 | Mains assembly, output adjustment, XT60/XT30 chain, polarity, protection, connector ratings, 25 A alternative and board circuitry are not frozen or measured. This optional path must not be represented as standard installed equipment.Physical validation: none. |
| XT30 2+2 power-separation board and RS harness boundary → Four RobStride RS00 actuator positionssource-to-target | power48 V-class RS branch through separation board and XT30 2+2 harnesses | The RS table publishes the separation board, RS00 motor bank and combined XT30 2+2 harness surface under the 48 V RS configuration.Seeed-Projects/reBot-DevArm commit a0c709638a341d6b12b005f22f5592c4b1579f56 | Branch topology, pinout, gauge, connector ratings, current allocation, fuse, inrush, voltage drop, thermal and fault behavior are not published or measured. RCI has not applied power.Physical validation: none. |
| XT30 2+2 power-separation board and RS harness boundary → Three RobStride RS06 actuator positionssource-to-target | power48 V-class RS branch through separation board and XT30 2+2 harnesses | The RS table publishes the separation board, RS06 motor bank and combined XT30 2+2 harness surface under the 48 V RS configuration.Seeed-Projects/reBot-DevArm commit a0c709638a341d6b12b005f22f5592c4b1579f56 | Joint/gripper branch topology, pinout, gauge, connector ratings, current allocation, fuse, inrush, voltage drop, thermal and fault behavior are not published or measured. RCI has not applied power.Physical validation: none. |
54 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 |
|---|---|---|---|---|
| 1-BASE-PLATE.stephardware/reBot_B601_RS/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/3D_Printed_Parts/1-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. |
| 1-CLIP.stephardware/reBot_B601_RS/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/3D_Printed_Parts/1-CLIP.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. |
| 1-COVER.stephardware/reBot_B601_RS/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/3D_Printed_Parts/1-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. |
| 1-DOWN-DL.stephardware/reBot_B601_RS/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/3D_Printed_Parts/1-DOWN-DL.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. |
| 1-DOWN-DR.stephardware/reBot_B601_RS/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/3D_Printed_Parts/1-DOWN-DR.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. |
| 1-HANDLE.stephardware/reBot_B601_RS/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/3D_Printed_Parts/1-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. |
| 1-RAIL-BASE-2.stephardware/reBot_B601_RS/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/3D_Printed_Parts/1-RAIL-BASE-2.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. |
| 1-RSM1-STATOR-1.stephardware/reBot_B601_RS/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/3D_Printed_Parts/1-RSM1-STATOR-1.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. |
| 1-SPACE-UP.stephardware/reBot_B601_RS/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/3D_Printed_Parts/1-SPACE-UP.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. |
| 1-STOPPER-1.stephardware/reBot_B601_RS/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/3D_Printed_Parts/1-STOPPER-1.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. |
| 1-UP-DL.stephardware/reBot_B601_RS/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/3D_Printed_Parts/1-UP-DL.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. |
| 1-UP-DR.stephardware/reBot_B601_RS/3D_Printed_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/3D_Printed_Parts/1-UP-DR.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. |
| RS-power-Bottom Cover.stphardware/reBot_B601_RS/3D_Printed_Parts | controlAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/3D_Printed_Parts/RS-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. |
| RS-power-Top Cover-Sliding Cover.stphardware/reBot_B601_RS/3D_Printed_Parts | controlAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/3D_Printed_Parts/RS-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. |
| RS-power-Top Cover.stphardware/reBot_B601_RS/3D_Printed_Parts | controlAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/3D_Printed_Parts/RS-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. |
| RS_Motor1_wiring_harness_clip.stphardware/reBot_B601_RS/3D_Printed_Parts | controlAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/3D_Printed_Parts/RS_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. |
| 1-O-CLIP.stephardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/1-O-CLIP.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. |
| 2-CD.stephardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/2-CD.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. |
| 2-LINK-2_3.stephardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/2-LINK-2_3.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. |
| 2-LINK-3_4-L.stephardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/2-LINK-3_4-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. |
| 2-LINK-3_4-R.stephardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/2-LINK-3_4-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. |
| 2-LINK-4_5-L.stephardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/2-LINK-4_5-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. |
| 2-LINK-4_5-R.stephardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/2-LINK-4_5-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. |
| 2-M6-ROTOR.stephardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/2-M6-ROTOR.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. |
| 2-M7-ROTOR.stephardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/2-M7-ROTOR.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. |
| 2-Motor_Back_Spacer.stephardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/2-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. |
| 2-RACK-1M.stephardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/2-RACK-1M.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. |
| 2-RAIL-BASE-1.stephardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/2-RAIL-BASE-1.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. |
| 2-RSM-ROTOR-L.stephardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/2-RSM-ROTOR-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. |
| 2-RSM-ROTOR-R.stephardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/2-RSM-ROTOR-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. |
| 2-RSM1-ROTOR-1.stephardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/2-RSM1-ROTOR-1.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. |
| 2-RSM1-STATOR-2.stephardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/2-RSM1-STATOR-2.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. |
| 2-RSM2-STATOR-1.stephardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/2-RSM2-STATOR-1.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. |
| 2-RSM2-STATOR-2.stephardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/2-RSM2-STATOR-2.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. |
| 2-RSM3-ROTATOR-L.stephardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/2-RSM3-ROTATOR-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. |
| 2-RSM3-ROTATOR-R.stephardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/2-RSM3-ROTATOR-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. |
| 2-RSM5-STATOR.stephardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/2-RSM5-STATOR.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. |
| 2-RSM6-RORATOR-1.stephardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/2-RSM6-RORATOR-1.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. |
| 2-RSM6-RORATOR-2.stephardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/2-RSM6-RORATOR-2.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. |
| 2-SLIDER-FIX.stephardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/2-SLIDER-FIX.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. |
| 2-SPACE-M4-STATOR.stephardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/2-SPACE-M4-STATOR.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. |
| 2-SPACE-UP-2.stephardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/2-SPACE-UP-2.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. |
| 2-Upper-Limit_L.stphardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/2-Upper-Limit_L.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. |
| 2-Upper-Limit_R.stphardware/reBot_B601_RS/Metal_Parts | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/Metal_Parts/2-Upper-Limit_R.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. |
| reBot_B601_RS_v1.0_20260625.stephardware/reBot_B601_RS | custom-mechanicalAlternative / not simultaneously installed | file-identifiedhardware/reBot_B601_RS/reBot_B601_RS_v1.0_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. |
| RobStride RS00 brushless motorB601 RS purchased parts, power separation and XT30 2+2 harness rows | actuationInstalled / build item | variant-namedRobStride RS00 | 4 unitFour RS00 motors are published in the responsibility-party RS table. | RS-branch joint actuationNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot. |
| RobStride RS06 brushless motorB601 RS purchased parts, power separation and XT30 2+2 harness rows | actuationInstalled / build item | variant-namedRobStride RS06 | 3 unitThree RS06 motors are published; the selected table does not bind each motor model to a numbered joint. | RS-branch joint and gripper actuationNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot. |
| RS CAN-to-USB driver boardB601 RS purchased parts, power separation 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 RS motor-bus interfaceNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot. |
| XT30 2+2 power separation boardB601 RS purchased parts, power separation and XT30 2+2 harness rows | powerInstalled / build item | generic-descriptionNo exact identity published | 1 unitOne power separation board is published; circuit revision, protection and connector pinout are not fixed by the row. | RS-branch power and communication distribution boundaryNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot. |
| XT30 2+2 harness — 320 mm, both ends angledB601 RS purchased parts, power separation and XT30 2+2 harness rows | cableInstalled / build item | variant-namedXT30 2+2 / 320 mm / two angled ends | 1 unitThe row publishes 1+ and requires custom fabrication; RCI records one minimum source quantity, not a final as-built count. | 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 RS purchased parts, power separation and XT30 2+2 harness rows | cableInstalled / build item | variant-namedXT30 2+2 / 200 mm / two angled ends | 4 unitThe row publishes 4+ and requires custom fabrication; RCI records four as the minimum source quantity. | 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 — 300 mm, one angled endB601 RS purchased parts, power separation and XT30 2+2 harness rows | cableInstalled / build item | variant-namedXT30 2+2 / 300 mm / one angled end | 1 unitThe row publishes 1+ and requires custom fabrication; the other end geometry is not stated. | 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 — both ends straightB601 RS purchased parts, power separation and XT30 2+2 harness rows | cableInstalled / build item | variant-namedXT30 2+2 / two straight ends | 1 unitThe row publishes 1+ without a cable length; RCI records one as the minimum source quantity. | Combined motor power and communication harnessNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot. |
| Optional Mean Well LRS-600-48 supplyB601 RS purchased parts, power separation and XT30 2+2 harness rows | powerAlternative / not simultaneously installed | variant-namedLRS-600-48 | 1 unitThe arm ships without a supply by default; the responsibility-party README presents one LRS-600-48 as an optional build path. | Optional 48 V / 12.5 A external sourceNo 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 RS production-file tree ↗
45 STEP/STL production files plus nine selected purchased-interface, harness and optional-power rows from the fixed RS README
reBot_B601_RS directory at reBot-DevArm commit a0c709638a341d6b12b005f22f5592c4b1579f56.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 →