Mobile base · SIGRobotics UIUC LeKiwi project

LeKiwi wired mobile-base configuration

Record state

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

Publication surface

Markdown table · 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

LeKiwi wired mobile-base configuration

Only the standalone “Everything needed for the wired version” table at LeKiwi commit efa608d7ee5a495a4803b1d28cd0c955b4f1e033.

Version state

Addressable source snapshot

Commit-addressable table without a release-tag or unit manifest.

Lifecycle boundary

Changes remain attached to the source.

Wired is an explicit alternative to battery configurations and remains separate.

Responsibility party

SIGRobotics UIUC LeKiwi project

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.

standard-configuration-change

LeKiwi wired mobile base → LeKiwi 5 V or 12 V battery configuration

The official BOM publishes wired as a separate cheapest alternative and gives it a standalone ten-row table.

System impact: Power source, host connection, USB fan-out and system scope differ; the wired record is not a full two-arm battery configuration.

Open: No as-built wiring diagram or independent run binds this table to one unit.

Strongest supported conclusion

A compact quantified wired-base path including wheels, cameras, servos, control, power, hub and extension cable.

Largest rebuild gap: No complete mechanical file selection, wiring diagram binding, serial evidence or independent physical build.

Editorial boundary: The source table does not establish a dual-arm installed build; RCI labels this profile as a mobile-base configuration.

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 quantitiesPublishedThe selected responsibility-party surface publishes this dimension inside the recorded boundary.
Manufacturer part numbersPartialUseful information exists, but exactness, completeness or version binding remains incomplete.
Supplier linksPublishedThe selected responsibility-party surface publishes this dimension inside the recorded boundary.
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 historyPublishedThe selected responsibility-party surface publishes this dimension inside the recorded boundary.
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

LeKiwi BOM wired-version table

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

Selected count

10 rows / list items

Ten responsibility-party item rows; total-price summary excluded. This boundary is a wired mobile base, not the two-arm 5 V or 12 V manipulator.

Format

Markdown table

RCI did not treat the publication format as a normalized database table.

Next evidence gate

Normalize without inventing.

Resolve exact part identity, quantity scope, placement, revision and substitution state while retaining nested assemblies, alternatives and generic groups as explicit boundaries.

As-built state

Not published

A public list does not establish what one serialised unit actually contained.

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

7 bounded nodes and 6 source-supported interface relations.

RCI publishes a connection only when the selected responsibility-party source explicitly supports the endpoints or architecture. A BOM co-occurrence, component capability or engineering convention is not enough.

external-host node

External laptop host

Laptop endpoint named by the pinned wired assembly instructions; outside the selected ten-row BOM.

Identity boundary: No host SKU, operating system, USB controller, software revision or physical port is fixed.

Source rows: Architecture text only; no BOM row.

control node

Orientation-sensitive USB-C extension

One USB-C extension cable in the wired BOM, installed in the responsibility-party printed cable holder.

Identity boundary: The guide specifies plug orientation but not one immutable cable lot, e-marker, negotiated mode or measured signal integrity.

Source rows: lekiwi-wired-item-10

control node

Wired USB hub fan-out

One USB hub in the selected wired BOM and the assembly-described hub holder/cable fan-out.

Identity boundary: Retail link and hub implementation are mutable; chipset, descriptors, port numbering, power behavior and bandwidth are not frozen.

Source rows: lekiwi-wired-item-09

control node

Two wired USB cameras

Two generic USB cameras connected through the assembly-described wired cable fan-out.

Identity boundary: Camera option, sensor, lens, descriptors, cable mapping, calibration and concurrent throughput are unresolved.

Source rows: lekiwi-wired-item-03, lekiwi-wired-item-04

control node

Wired mobile-base motor-control board

One motor-control board in the selected wired BOM, connected into the wired USB fan-out by the assembly.

Identity boundary: No exact controller manufacturer/model, firmware, descriptor, serial port, protocol or current rating is fixed.

Source rows: lekiwi-wired-item-07, lekiwi-wired-item-04

actuation node

Three wired-version STS3215 drive servos

Three STS3215 units in the selected wired mobile-base table.

Identity boundary: Voltage/reduction suffix, serials, IDs, chain order, calibration and physical condition are not fixed.

Source rows: lekiwi-wired-item-06

power node

External wired power supply and USB-C-to-DC lead

One generic power supply and one USB-C-to-DC cable in the wired BOM.

Identity boundary: Output voltage/current, connector dimensions, polarity, grounding, protection, cable trigger behavior and loaded measurements are not published in the selected table.

Source rows: lekiwi-wired-item-05, lekiwi-wired-item-08

From → toRelationPublished supportStill unresolved
External laptop host → Orientation-sensitive USB-C extensionbidirectionaldata-controlLaptop USB-C link with responsibility-party-specified plug orientationThe pinned wired assembly connects the extension to a laptop and explicitly warns that the marked plug orientation determines whether cameras and controller are detected.SIGRobotics-UIUC/LeKiwi commit efa608d7ee5a495a4803b1d28cd0c955b4f1e033Host port, cable lot/e-marker, negotiated mode, orientation behavior across hosts, insertion loss and observed enumeration are not frozen. RCI has not connected this cable.Physical validation: none.
Orientation-sensitive USB-C extension → Wired USB hub fan-outbidirectionaldata-controlUSB-C extension into mounted USB hub fan-outThe assembly adds the cable holder and USB hub holder, then attaches the extension and downstream device cables in the illustrated wired configuration.SIGRobotics-UIUC/LeKiwi commit efa608d7ee5a495a4803b1d28cd0c955b4f1e033Hub chipset, upstream port identity, power source, negotiated topology, bandwidth and fault behavior are not frozen. RCI has not enumerated the hub.Physical validation: none.
Wired USB hub fan-out → Two wired USB camerasbidirectionaldata-controlTwo camera cables on the wired USB fan-outThe pinned wired instructions attach cables for two cameras, the controller and extension at the mounted hub area; the BOM publishes two cameras and one hub.SIGRobotics-UIUC/LeKiwi commit efa608d7ee5a495a4803b1d28cd0c955b4f1e033Camera SKUs, hub port allocation, descriptors, simultaneous bandwidth and calibration are not frozen. RCI has not captured either stream.Physical validation: none.
Wired USB hub fan-out → Wired mobile-base motor-control boardbidirectionaldata-controlMotor-control-board USB link on the wired fan-outThe wired assembly explicitly groups the motor-control-board cable with the two camera cables and USB-C extender; the selected BOM publishes one board and one hub.SIGRobotics-UIUC/LeKiwi commit efa608d7ee5a495a4803b1d28cd0c955b4f1e033Controller model, descriptor, serial device, protocol, baud and hub port are not frozen. RCI has not enumerated or exchanged control traffic.Physical validation: none.
Wired mobile-base motor-control board → Three wired-version STS3215 drive servosbidirectionaldata-controlMotor-control-board bus to three wired-version STS3215 drive servosThe pinned base assembly attaches servo-driver wires to three drive servos; the wired table publishes one board and three STS3215 units.SIGRobotics-UIUC/LeKiwi commit efa608d7ee5a495a4803b1d28cd0c955b4f1e033Servo submodel, voltage, IDs, bus order, wheel mapping, calibration and controller firmware are not frozen. RCI has not scanned or moved this bus.Physical validation: none.
External wired power supply and USB-C-to-DC lead → Wired mobile-base motor-control boardsource-to-targetpowerExternal supply through USB-C-to-DC cable to controller barrel inputThe wired BOM publishes one power supply, one USB-C-to-DC cable and one motor-control board; the final assembly powers the controller through the DC barrel input.SIGRobotics-UIUC/LeKiwi commit efa608d7ee5a495a4803b1d28cd0c955b4f1e033Voltage/current, trigger behavior, barrel dimensions, polarity, protection, grounding and loaded measurements are not published. RCI has not energized this path.Physical validation: none.
NORMALIZED BOM

10 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
4-inch omni wheelsEverything needed for the wired versionmechanical-hardwareInstalled / build itemgeneric-descriptionNo exact identity published3 unitThree wheels are published.Holonomic mobile-base contactNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot.
M2/M3/M4 assorted screw setEverything needed for the wired versionfastenerInstalled / build itemgeneric-descriptionNo exact identity published1 bundleOne assortment is published.Assembly fastenersNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot.
USB cameraEverything needed for the wired versionsensorInstalled / build itemgeneric-descriptionNo exact identity published2 unitTwo cameras are published.Visual sensingNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot.
USB-C to USB-A cable 2 pcsEverything needed for the wired versioncableInstalled / build itemgeneric-descriptionNo exact identity published1 bundleOne two-cable bundle is published.Host/controller cable bundleNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot.
USB-C to DC cableEverything needed for the wired versioncableInstalled / build itemgeneric-descriptionNo exact identity published1 unitOne cable is published.Wired power pathNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot.
STS3215 servoEverything needed for the wired versionactuationInstalled / build itemvariant-namedSTS32153 unitThree servos are published.Mobile-base driveNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot.
Motor control boardEverything needed for the wired versioncontrolInstalled / build itemgeneric-descriptionNo exact identity published1 unitOne board is published.Base servo controlNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot.
Power supplyEverything needed for the wired versionpowerInstalled / build itemgeneric-descriptionNo exact identity published1 unitOne supply is published.Wired external powerNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot.
USB hubEverything needed for the wired versioncontrolInstalled / build itemgeneric-descriptionNo exact identity published1 unitOne hub is published.Host USB fan-outNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot.
USB-C extension cableEverything needed for the wired versioncableInstalled / build itemgeneric-descriptionNo exact identity published1 unitOne extension cable is published.Wired host extensionNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot.
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.

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