Quadruped · Q8bot / ZeroWire Robotics

Q8bot hardware v2.5 release

Record state

Public BOM audited. This is a source-bound system evidence record, not an independent rebuild.

Publication surface

Versioned release archive · commit-addressable.

Rebuild conclusion

No complete rebuild evidence package found.

IDENTITY + REVISION

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

Q8bot hardware v2.5 release

GitHub release v1.2.1 asset hw-v2.5.zip, published 2025-11-11.

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 release binds software v1.2.1 to hardware archive v2.5; prior hardware v2.2/v2.4 assets remain historical alternatives.

Responsibility party

Q8bot / ZeroWire Robotics

RCI maps the named public responsibility party; inclusion does not imply endorsement, partnership or unit-level verification.

VERSION & SUPPLY

1 bounded lifecycle or procurement relations.

Replacement, upgrade, EOL and regional procurement signals remain separate from current availability and as-built identity.

version-upgrade

Q8bot hardware v2.4 → Q8bot hardware v2.5

GitHub releases v1.1.0/v1.2.0 carry hw-v2.4.zip while v1.2.1 carries hw-v2.5.zip.

System impact: CAD/print, PCB design, placement, fabrication and BOM artifacts must remain attached to the selected hardware archive version.

Open: RCI has not computed a file-level v2.4-to-v2.5 semantic delta or built either revision.

Strongest supported conclusion

Release-addressable CAD, printable files, PCB design sources, fabrication outputs, placement and BOM artifacts.

Largest rebuild gap: RCI has not parsed the spreadsheet line items, ordered the PCB, built the robot or verified the archive against one physical unit.

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.

DISCLOSURE MATRIX

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 dimensionStateWhat the state means here
Exact platform revisionPublishedThe selected responsibility-party surface publishes this dimension inside the recorded boundary.
Versioned BOM snapshotPartialUseful information exists, but exactness, completeness or version binding remains incomplete.
Line-item quantitiesNot publishedThe selected sources do not publish this evidence dimension.
Manufacturer part numbersPartialUseful information exists, but exactness, completeness or version binding remains incomplete.
Supplier linksNot publishedThe selected sources do not publish this evidence dimension.
Custom-part production filesPublishedThe selected responsibility-party surface publishes this dimension inside the recorded boundary.
Electrical interconnect definitionPartialUseful information exists, but exactness, completeness or version binding remains incomplete.
Software / firmware bindingPartialUseful information exists, but exactness, completeness or version binding remains incomplete.
License boundaryPublishedThe selected responsibility-party surface publishes this dimension inside the recorded boundary.
Change, EOL and substitution historyPartialUseful information exists, but exactness, completeness or version binding remains incomplete.
Unit-level as-built manifestNot publishedThe selected sources do not publish this evidence dimension.
Independent rebuild evidenceNot publishedThe selected sources do not publish this evidence dimension.
BOM SURFACE

hw-v2.5.zip archive file manifest

The count below preserves the responsibility party's publication structure; it is not silently flattened into unique purchasable components.

Selected count

38 rows / list items

38 distinct responsibility-party file paths in the selected immutable source boundary. A file path is an engineering evidence record, not an installed quantity or a unique procured component.

Format

Versioned release archive

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.

RELATION GRAPH

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.

ASSEMBLY + INTERFACE TOPOLOGY

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.

compute node

Seeed Studio XIAO ESP32C3 main controller

U1 on the Q8_V2.5 schematic inside release v1.2.1 hw-v2.5.zip.

Identity boundary: The release binds the schematic and PCB source, but not one assembled board serial, flashed firmware hash, radio identity or observed pin state.

Source rows: q8bot-v25-file-031, q8bot-v25-file-038

control node

SN74LVC2G241 DYNAMIXEL TTL direction buffer

U2 and its TXD/RXD/TX_EN nets on the Q8_V2.5 schematic.

Identity boundary: Schematic identity does not prove the populated component lot, logic levels under load, direction timing or measured bus waveform.

Source rows: q8bot-v25-file-031, q8bot-v25-file-038

control node

Eight three-pin TTL/power robot connectors

J1–J8 on the Q8_V2.5 schematic; four use DXL_P2 and four use DXL_PWR while sharing TTL and ground.

Identity boundary: The eight ports are PCB endpoints, not proof of eight attached actuators, connector population, cable polarity or one robot wiring map.

Source rows: q8bot-v25-file-030, q8bot-v25-file-033, q8bot-v25-file-034, q8bot-v25-file-035, q8bot-v25-file-038

power node

Two-cell battery-holder input domain

BT1/BT2 series holder representation and VBAT net on the Q8_V2.5 schematic.

Identity boundary: Cell chemistry, exact cell model, series/holder assembly state, protection, polarity, capacity, charge state and measured VBAT are not frozen.

Source rows: q8bot-v25-file-013, q8bot-v25-file-014, q8bot-v25-file-015, q8bot-v25-file-016, q8bot-v25-file-017, q8bot-v25-file-038

power node

Dual TPS610333 boost paths: DXL_PWR and DXL_P2

U3/U5, L1/L2 and the two switched output nets on the Q8_V2.5 schematic.

Identity boundary: Output setpoints, current sharing, switch state, protection, efficiency, thermal behavior and measured rail voltages are not published.

Source rows: q8bot-v25-file-030, q8bot-v25-file-033, q8bot-v25-file-034, q8bot-v25-file-035, q8bot-v25-file-038

control node

MAX17043 battery fuel-gauge path

U4 on VBAT with SDA/SCL pull-ups to 3.3 V in the Q8_V2.5 schematic.

Identity boundary: Gauge population, configuration/model data, I²C address/readback, alert behavior and state-of-charge accuracy are not observed.

Source rows: q8bot-v25-file-031, q8bot-v25-file-038

From → toRelationPublished supportStill unresolved
Seeed Studio XIAO ESP32C3 main controller → SN74LVC2G241 DYNAMIXEL TTL direction bufferbidirectionaldata-controlTXD, RXD and TX_EN direction-control path at 3.3 V logicThe Q8_V2.5 schematic connects XIAO ESP32C3 TXD/RXD/TX_EN nets to SN74LVC2G241 and states that TX_EN switches between transmit and receive.Q8bot GitHub release v1.2.1 / hw-v2.5.zipFirmware pin configuration, baud, enable timing, populated buffer identity, logic margins and measured waveforms are not frozen. RCI has not powered or probed the board.Physical validation: none.
SN74LVC2G241 DYNAMIXEL TTL direction buffer → Eight three-pin TTL/power robot connectorsbidirectionaldata-controlShared half-duplex DYNAMIXEL TTL net to J1–J8The v2.5 schematic fans the TTL net from the direction buffer to eight three-pin robot connectors and cites the DYNAMIXEL request-response scheme.Q8bot GitHub release v1.2.1 / hw-v2.5.zipConnector population, attached-device count, cable mapping, actuator IDs, termination, bus loading, errors and observed traffic are not frozen. Eight PCB ports do not prove eight installed actuators.Physical validation: none.
Two-cell battery-holder input domain → Dual TPS610333 boost paths: DXL_PWR and DXL_P2source-to-targetpowerVBAT through two switched TPS610333 boost convertersThe Q8_V2.5 schematic connects VBAT through separately switched U3/U5 boost paths that generate DXL_PWR and DXL_P2.Q8bot GitHub release v1.2.1 / hw-v2.5.zipCell identity, series-holder wiring, enable state, output setpoints, protection, current limits, efficiency and thermal behavior are not frozen. RCI has not energized either converter.Physical validation: none.
Dual TPS610333 boost paths: DXL_PWR and DXL_P2 → Eight three-pin TTL/power robot connectorssource-to-targetpowerDXL_P2 on J1–J4 and DXL_PWR on J5–J8The v2.5 schematic assigns DXL_P2 to four robot connectors and DXL_PWR to the other four while sharing TTL and ground.Q8bot GitHub release v1.2.1 / hw-v2.5.zipRail voltage, port current allocation, switch behavior, connector polarity, fuse/protection and loaded droop are not published. RCI has not measured any port.Physical validation: none.
Two-cell battery-holder input domain → MAX17043 battery fuel-gauge pathsource-to-targetdata-controlMAX17043 CELL input observes VBATThe Q8_V2.5 schematic connects MAX17043 CELL to VBAT through R5 and publishes the gauge support network.Q8bot GitHub release v1.2.1 / hw-v2.5.zipGauge configuration/model, cell chemistry match, sense accuracy, alert threshold and physical population are not frozen. RCI has no voltage or state-of-charge trace.Physical validation: none.
MAX17043 battery fuel-gauge path → Seeed Studio XIAO ESP32C3 main controllerbidirectionaldata-controlSDA/SCL fuel-gauge path with 10 kΩ pull-ups to 3.3 VThe v2.5 schematic connects U4 SDA/SCL to the XIAO controller and shows R6/R7 pull-ups to 3.3 V.Q8bot GitHub release v1.2.1 / hw-v2.5.zipI²C address/readback, bus rate, firmware driver, alert handling, pull-up population and observed data are not frozen. The included PCBWay workbook title says Q8_V2.3 despite the v2.5 archive; RCI does not silently equate that BOM title to v2.5.Physical validation: none.
NORMALIZED BOM

38 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 itemClassIdentityQuantity boundaryRole + unresolved evidence
Q8bot_rev2_5_FDM.STEPhw-v2.5/CADcustom-mechanicalAlternative / not simultaneously installedfile-identifiedhw-v2.5/CAD/Q8bot_rev2_5_FDM.STEPNot 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.
Q8bot_rev2_5_MJF.STEPhw-v2.5/CADcustom-mechanicalAlternative / not simultaneously installedfile-identifiedhw-v2.5/CAD/Q8bot_rev2_5_MJF.STEPNot 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.
PLA_Lower_Leg_Left_PRINT4.STLhw-v2.5/CAD/Q8_V2.5_FDMcustom-mechanicalAlternative / not simultaneously installedfile-identifiedhw-v2.5/CAD/Q8_V2.5_FDM/PLA_Lower_Leg_Left_PRINT4.STLNot 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.
PLA_Lower_Leg_Right_PRINT4.STLhw-v2.5/CAD/Q8_V2.5_FDMcustom-mechanicalAlternative / not simultaneously installedfile-identifiedhw-v2.5/CAD/Q8_V2.5_FDM/PLA_Lower_Leg_Right_PRINT4.STLNot 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.
PLA_Upper_Leg_Short_PRINT4.STLhw-v2.5/CAD/Q8_V2.5_FDMcustom-mechanicalAlternative / not simultaneously installedfile-identifiedhw-v2.5/CAD/Q8_V2.5_FDM/PLA_Upper_Leg_Short_PRINT4.STLNot 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.
PLA_Upper_Leg_Tall_PRINT4.STLhw-v2.5/CAD/Q8_V2.5_FDMcustom-mechanicalAlternative / not simultaneously installedfile-identifiedhw-v2.5/CAD/Q8_V2.5_FDM/PLA_Upper_Leg_Tall_PRINT4.STLNot 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.
Q8bot_Frame_FDM_PRINT2.STLhw-v2.5/CAD/Q8_V2.5_FDMcustom-mechanicalAlternative / not simultaneously installedfile-identifiedhw-v2.5/CAD/Q8_V2.5_FDM/Q8bot_Frame_FDM_PRINT2.STLNot 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.
MJF_Frame_PRINT2.STLhw-v2.5/CAD/Q8_V2.5_MJFcustom-mechanicalAlternative / not simultaneously installedfile-identifiedhw-v2.5/CAD/Q8_V2.5_MJF/MJF_Frame_PRINT2.STLNot 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.
MJF_Lower_Leg_Left_PRINT4.STLhw-v2.5/CAD/Q8_V2.5_MJFcustom-mechanicalAlternative / not simultaneously installedfile-identifiedhw-v2.5/CAD/Q8_V2.5_MJF/MJF_Lower_Leg_Left_PRINT4.STLNot 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.
MJF_Lower_Leg_Right_PRINT4.STLhw-v2.5/CAD/Q8_V2.5_MJFcustom-mechanicalAlternative / not simultaneously installedfile-identifiedhw-v2.5/CAD/Q8_V2.5_MJF/MJF_Lower_Leg_Right_PRINT4.STLNot 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.
MJF_Upper_Leg_Short_PRINT4.STLhw-v2.5/CAD/Q8_V2.5_MJFcustom-mechanicalAlternative / not simultaneously installedfile-identifiedhw-v2.5/CAD/Q8_V2.5_MJF/MJF_Upper_Leg_Short_PRINT4.STLNot 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.
MJF_Upper_Leg_Tall_PRINT4.STLhw-v2.5/CAD/Q8_V2.5_MJFcustom-mechanicalAlternative / not simultaneously installedfile-identifiedhw-v2.5/CAD/Q8_V2.5_MJF/MJF_Upper_Leg_Tall_PRINT4.STLNot 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.
692ZZ_Ball_Bearing_20250303export.SLDPRThw-v2.5/CAD/SolidWorks Source Filecustom-mechanicalAlternative / not simultaneously installedfile-identifiedhw-v2.5/CAD/SolidWorks Source File/692ZZ_Ball_Bearing_20250303export.SLDPRTNot 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.
Batt_Case_keystone-PN1087_20250303export.SLDPRThw-v2.5/CAD/SolidWorks Source Filecustom-mechanicalAlternative / not simultaneously installedfile-identifiedhw-v2.5/CAD/SolidWorks Source File/Batt_Case_keystone-PN1087_20250303export.SLDPRTNot 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.
Batt_Clip_keystone-PN1087-1_20250303export.SLDPRThw-v2.5/CAD/SolidWorks Source Filecustom-mechanicalAlternative / not simultaneously installedfile-identifiedhw-v2.5/CAD/SolidWorks Source File/Batt_Clip_keystone-PN1087-1_20250303export.SLDPRTNot 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.
Batt_Clip_keystone-PN1087-2_20250303export.SLDPRThw-v2.5/CAD/SolidWorks Source Filecustom-mechanicalAlternative / not simultaneously installedfile-identifiedhw-v2.5/CAD/SolidWorks Source File/Batt_Clip_keystone-PN1087-2_20250303export.SLDPRTNot 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.
Batt_KeepPower_14500_P1450C2_20250303export.SLDPRThw-v2.5/CAD/SolidWorks Source FilecontrolAlternative / not simultaneously installedfile-identifiedhw-v2.5/CAD/SolidWorks Source File/Batt_KeepPower_14500_P1450C2_20250303export.SLDPRTNot 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.
Conn_EHR-3_20250303export.SLDPRThw-v2.5/CAD/SolidWorks Source Filecustom-mechanicalAlternative / not simultaneously installedfile-identifiedhw-v2.5/CAD/SolidWorks Source File/Conn_EHR-3_20250303export.SLDPRTNot 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.
M2_Tapping_Screw_20250303export.SLDPRThw-v2.5/CAD/SolidWorks Source Filecustom-mechanicalAlternative / not simultaneously installedfile-identifiedhw-v2.5/CAD/SolidWorks Source File/M2_Tapping_Screw_20250303export.SLDPRTNot 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.
Q8bot_20250303export.SLDASMhw-v2.5/CAD/SolidWorks Source Filecustom-mechanicalAlternative / not simultaneously installedfile-identifiedhw-v2.5/CAD/SolidWorks Source File/Q8bot_20250303export.SLDASMNot 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.
Q8bot_Leg_SubAssm_20250303export.SLDASMhw-v2.5/CAD/SolidWorks Source Filecustom-mechanicalAlternative / not simultaneously installedfile-identifiedhw-v2.5/CAD/SolidWorks Source File/Q8bot_Leg_SubAssm_20250303export.SLDASMNot 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.
Q8bot_Lower_Leg_20250303export.SLDPRThw-v2.5/CAD/SolidWorks Source Filecustom-mechanicalAlternative / not simultaneously installedfile-identifiedhw-v2.5/CAD/SolidWorks Source File/Q8bot_Lower_Leg_20250303export.SLDPRTNot 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.
Q8bot_Main_Frame_20250303export.SLDPRThw-v2.5/CAD/SolidWorks Source Filecustom-mechanicalAlternative / not simultaneously installedfile-identifiedhw-v2.5/CAD/SolidWorks Source File/Q8bot_Main_Frame_20250303export.SLDPRTNot 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.
Q8bot_Upper_Leg_20250303export.SLDPRThw-v2.5/CAD/SolidWorks Source Filecustom-mechanicalAlternative / not simultaneously installedfile-identifiedhw-v2.5/CAD/SolidWorks Source File/Q8bot_Upper_Leg_20250303export.SLDPRTNot 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.
Q8_PCB_Placeholder_20250303export.SLDPRThw-v2.5/CAD/SolidWorks Source FilecontrolAlternative / not simultaneously installedfile-identifiedhw-v2.5/CAD/SolidWorks Source File/Q8_PCB_Placeholder_20250303export.SLDPRTNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Electrical design or fabrication evidenceFile 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.
Q8_PCB_V2.4_20250303export.SLDPRThw-v2.5/CAD/SolidWorks Source FilecontrolAlternative / not simultaneously installedfile-identifiedhw-v2.5/CAD/SolidWorks Source File/Q8_PCB_V2.4_20250303export.SLDPRTNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Electrical design or fabrication evidenceFile 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.
XL330_M077_T_20250303export.SLDPRThw-v2.5/CAD/SolidWorks Source Filecustom-mechanicalAlternative / not simultaneously installedfile-identifiedhw-v2.5/CAD/SolidWorks Source File/XL330_M077_T_20250303export.SLDPRTNot 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.
Q8_V2.5.PrjPcbhw-v2.5/PCBA/Altium Source FilescontrolAlternative / not simultaneously installedfile-identifiedhw-v2.5/PCBA/Altium Source Files/Q8_V2.5.PrjPcbNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Electrical design or fabrication evidenceFile 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.
Q8_V2.5.PrjPcbStructurehw-v2.5/PCBA/Altium Source FilescontrolAlternative / not simultaneously installedfile-identifiedhw-v2.5/PCBA/Altium Source Files/Q8_V2.5.PrjPcbStructureNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Electrical design or fabrication evidenceFile 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.
Q8_V2.5_Brd.PcbDochw-v2.5/PCBA/Altium Source FilescontrolAlternative / not simultaneously installedfile-identifiedhw-v2.5/PCBA/Altium Source Files/Q8_V2.5_Brd.PcbDocNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Electrical design or fabrication evidenceFile 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.
Q8_V2.5_Sch.SchDochw-v2.5/PCBA/Altium Source FilescontrolAlternative / not simultaneously installedfile-identifiedhw-v2.5/PCBA/Altium Source Files/Q8_V2.5_Sch.SchDocNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Electrical design or fabrication evidenceFile 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.
Gerbers_20251110.ziphw-v2.5/PCBAcontrolAlternative / not simultaneously installedfile-identifiedhw-v2.5/PCBA/Gerbers_20251110.zipNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Electrical design or fabrication evidenceFile 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.
Pick Place for Q8_V2.5_Brd (Read Friendly).xlsxhw-v2.5/PCBAcontrolAlternative / not simultaneously installedfile-identifiedhw-v2.5/PCBA/Pick Place for Q8_V2.5_Brd (Read Friendly).xlsxNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Electrical design or fabrication evidenceFile 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.
Pick Place for Q8_V2.5_Brd.csvhw-v2.5/PCBAcontrolAlternative / not simultaneously installedfile-identifiedhw-v2.5/PCBA/Pick Place for Q8_V2.5_Brd.csvNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Electrical design or fabrication evidenceFile 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.
Pick Place for Q8_V2.5_Brd_JLCPCB.xlsxhw-v2.5/PCBAcontrolAlternative / not simultaneously installedfile-identifiedhw-v2.5/PCBA/Pick Place for Q8_V2.5_Brd_JLCPCB.xlsxNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Electrical design or fabrication evidenceFile 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.
Q8_V2.5_Assembly_Drawings.pdfhw-v2.5/PCBAcontrolAlternative / not simultaneously installedfile-identifiedhw-v2.5/PCBA/Q8_V2.5_Assembly_Drawings.pdfNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Electrical design or fabrication evidenceFile 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.
Q8_V2.5_BOM_PCBWay.xlsxhw-v2.5/PCBAcontrolAlternative / not simultaneously installedfile-identifiedhw-v2.5/PCBA/Q8_V2.5_BOM_PCBWay.xlsxNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Electrical design or fabrication evidenceFile 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.
Q8_V2.5_Schematics_20251110Export.pdfhw-v2.5/PCBAcontrolAlternative / not simultaneously installedfile-identifiedhw-v2.5/PCBA/Q8_V2.5_Schematics_20251110Export.pdfNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Electrical design or fabrication evidenceFile 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.
SOURCE REGISTER

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.

01

Q8bot release v1.2.1 — hw-v2.5.zip ↗

38 files spanning CAD, printable variants, SolidWorks sources, Altium sources, Gerbers, placement, BOM and schematics

GitHub release v1.2.1 asset hw-v2.5.zip, published 2025-11-11.

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 →

Return to all robot systems · Machine-readable record