On this page

How to Source Robotics Sensors and Compute Modules

Source robotics sensors and compute modules as an exact proposed assembly. Identify orderable parts, selected carrier and cables, sensor firmware, drivers and SDK versions, then check the installed power, thermal, mechanical and support scope. A production purchase needs a current authorised US selling route and a usable delivery commitment for that same selection. Keep missing integration evidence visible and limit any early purchase to its approved evaluation purpose.

A camera or LiDAR model and a compute-module family name are only a starting point. The source record must resolve the ordering suffixes, interfaces and software artefacts that the team will actually receive and use.

Set hard prerequisites before comparing supplier terms

Begin with the sensing task. State the observation required, operating distance in metres, field of view in degrees, output mode, frame or scan rate in hertz, environment and relevant accuracy or timing criteria. The sensor owner supplies those requirements. The compute owner states the workload, memory, storage and interface needs.

Use a scorecard with Pass, Pending and Reject states. Each mandatory row needs evidence for the exact proposed pair. Cost and convenience can help choose among eligible candidates after the prerequisites are satisfied. A high commercial score cannot compensate for an unsupported driver or an unresolved power connection.

Hard prerequisite Evidence needed for the exact selection Accountable owner Hold condition
Orderable identity Manufacturer, full MPN, ordering suffix, revision where controlled, distributor SKU and supplied accessories Buyer and product-data owner A family name or substituted suffix leaves the received item ambiguous.
Sensor task fit Selected mode, lens or scan pattern, range in m, field of view in degrees and requirement-specific evidence Sensor owner Published maxima do not establish the intended installed measurement.
Cable and physical interface Both connector definitions, cable ordering code and length in m, carrier port and required adapter Electrical and integration owners A connector fit or interface label leaves the actual connection unresolved.
Driver and software pairing Sensor firmware, SDK/driver release, target architecture, OS/BSP version and exact installable image Software owner The selected software combination has no inspected support or integration evidence.
Power and thermal envelope Input voltage in V, peak/steady demand in W or A, chosen mode, cooling path and enclosure conditions in °C Electrical and thermal owners Candidate load or heat rejection exceeds the accepted envelope or remains unverified.
Mechanical fit Controlled outline and mounting drawing, envelope in mm, cable clearance and service access Mechanical owner The assembly depends on unreviewed mounting or interference.
Support and lifecycle Manufacturer lifecycle record, change-notification path, SDK maintenance and relevant support terms Product and software owners Required supply or software support horizon remains unsupported.
US purchase and receipt Authorised seller for the exact line, ship-from scope, dated quantity/arrival offer, required documents and receipt-check allowance Buyer and materials owner Displayed stock, authorisation or usable delivery remains unconfirmed at purchase.

Manufacturer support lists are evidence with a stated scope. Basler's pylon documentation, for example, distinguishes Linux ARM, x86 and other platform/interface support and describes system requirements. It is useful for inspecting an exact Basler camera software candidate. It supplies no universal compatibility or performance claim for an arbitrary sensor/compute pair. Basler pylon documentation

Separate a development kit from a production module

NVIDIA describes Jetson developer kits as intended for software development and system prototyping and publishes no lifecycle information for them. Its production-module documentation separately lists commercial module horizons and describes product-change notifications. Use the exact module entry when assessing supply continuity, then confirm the orderable line and its current terms. NVIDIA Jetson lifecycle

The archived Jetson Linux r36.4.4 bring-up guide describes adaptation from a developer kit to another hardware platform. Its Orin NX/Nano section identifies the module and carrier separately and requires platform configuration changes when using another carrier. That gives the sourcing team a concrete integration question to resolve. It does not establish that r36.4.4 is the latest release or the correct release for a new product. r36.4.4 adaptation guide and Orin NX/Nano platform guidance

Record the development-kit BOM and software state even if it is temporary. When proposing production hardware, explicitly replace or retain each module, carrier, power input, storage device, cable, driver and image. An unchanged compute-family label can conceal a changed assembly.

Work a future R-01 sensor and compute candidate

R-01 is the fictional indoor inspection robot used in Arc's BOM series. Its original pilot keeps SN-400 A and CB-200 A with firmware 1.2.0. Its harness split is two A for 001–002 and three B for 003–005 after ECO-017. Those historical selections remain intact in this future sourcing exercise. Original configuration matrix

Snapshot S0 proposes an added inspection-compute and camera assembly for a future configuration, CFG-R01-SC-C01. It uses a Jetson Orin Nano 8GB commercial module as a candidate family, a proposed carrier CB-SC-01 and a fictional camera CAM-P01. The lab comparison uses DEV-SC-01 and CAM-L01. Camera identifiers, software release labels and all performance/power values below are fictional teaching inputs. No camera or module assembly has been purchased, tested or approved here.

Selection field Lab setup to record Proposed production pair at S0
Compute and carrier DEV-SC-01, identified development kit and lab carrier Candidate Orin Nano 8GB commercial module with exact orderable MPN pending, CB-SC-01 A carrier
Sensor and cable CAM-L01 A, lab USB cable CAB-L01 CAM-P01 A camera, CAB-P01 A, 1 m proposed cable and specified carrier port
Software Lab image IMG-L01, camera driver DRV-L01 and SDK-L01 Proposed image IMG-P01, BSP-P01, driver DRV-P01 and SDK-P01, exact versions and support pending
Sensing scope Lab mode and conditions recorded, with no results supplied Proposed 2 m inspection distance and 20 Hz image output, task evidence pending
Power and heat Lab supply and open-bench cooling recorded Provisional assembly dissipation allocation 35 W and allowable heat dissipation 40 W at the same design condition. Peak electrical demand and installed evidence pending.
Robot connection Separate lab workstation Proposed added interface and power branch, unchanged original controller firmware retained provisionally
Release scope Evaluation reference only Future configuration candidate, no applicability to pilot 001–005

The 35 W dissipation allocation and 40 W allowable heat dissipation are provisional assumptions for the complete added assembly at one common design condition. That condition must define ambient temperature, enclosure and cooling path. Their nominal difference is 5 W. The comparison needs evidence for the steady heat load and installed cooling capacity before it becomes an accepted margin. Peak electrical demand remains a separate pending check with the electrical owner.

The selected camera output, cable and carrier form one compatibility case. If LiDAR is proposed instead, replace the sensing mode, scan data, network or physical connection and selected driver fields with the exact LiDAR requirements. A change of sensor type needs a revised candidate and its own evidence.

Record the staged decision and open actions

At S0, exact ordering identity, camera software support, carrier adaptation, thermal fit and US supply remain Pending. The future production selection stays held. The proposed next step is a bounded evaluation request for one identified candidate assembly after the purchasing authority confirms the item identities, seller and evaluation budget.

Action Owner Evidence before the next gate
Resolve module and camera MPNs Buyer and product-data owner Exact quoteable lines, accessories and current authorised US seller scope
Freeze the evaluation software set Software owner Retrieved versions, target support and exact IMG-P01 artefact identity
Review carrier and camera connection Electrical and integration owners Port/cable mapping, carrier configuration and candidate compatibility case
Check installed demand and cooling Electrical and thermal owners Declared operating modes and evidence for the complete assembly in its enclosure
Accept the future option and manifest Release authority Closed prerequisites, selected rows and inclusion approvals for CFG-R01-SC-C01

An evaluation purchase can be authorised with unresolved production-fit questions when its scope and limits are explicit. It is still subject to the procurement approval needed for that purchase. Record received identities and evaluation evidence before any production allocation.

Refresh the seller authorisation, exact available quantity and usable receipt date at the time of a real US order. Preserve the quotation date, ship-from scope, delivery basis and required receiving documents. The existing electronics-distributor guide owns the seller comparison and channel check.

Sensor and compute sourcing questions

Can a lab development kit become the production purchasing line?

Confirm the manufacturer's intended use and lifecycle scope, then identify the actual production assembly. Record every retained and changed component, software reference and support condition before release.

Does an SDK support list prove installed compatibility?

It supports the platforms and versions listed. Check the exact sensor, carrier, cable, image and workload, and retain the integration evidence needed for your selected configuration.

Can we purchase one candidate before production approval?

The purchasing authority can approve a bounded evaluation scope with explicit unresolved questions. Receiving the sample supplies no production acceptance by itself.

Should camera and LiDAR proposals share one generic BOM row?

Give each exact sensor assembly its own identity and selected software/cable scope. Compare them against the sensing task and retain the accepted variant choice.

Continue the candidate review

Use the RFQ template for comparable quote scope and the variant BOM guide for candidate-selection rules. Use the ICD guide and calibration-evidence guide for their detailed engineering decisions.

Move faster without compromising engineering rigour.

Bring one lab sensor/compute setup and its proposed production replacement to a demo.