Manufacturer profile

RoboSense

LiDAR hardware and perception products for robotics and autonomous vehicles.

ChinaExact-model evidence linkedExpansion batch 2Checked 2026-08-13

Identity boundary

Profile, not endorsement.

RCI links the manufacturer identity to public evidence. Inclusion does not imply independent verification of performance, commercial availability in every region, or any commercial relationship with RCI.

Official website ↗

Integration relevance

Why this supplier matters to a robot-system decision.

RoboSense spans mechanical and digital LiDAR, active cameras and perception products. A robot-system decision must bind the exact sensor, field of view, target conditions, scan pattern, time synchronization, network transport, SDK/firmware and environmental envelope.

Desk review: 2026-08-13. This dossier maps official research routes and unresolved decision questions; it is not an exact-model recommendation.

OFFICIAL EVIDENCE ROUTES

Start with responsibility-party material.

These routes define the current desk-research surface. RCI does not treat a portfolio page as a datasheet, purchase commitment or independent result.

SELECTION SIGNALS

What changes the engineering decision.

Signals organize further evaluation; they are not rankings or proof that one supplier fits a specific robot.

Signal 1

The portfolio includes sensors with different ranging principles, scan patterns and intended application classes; family-level range values are not interchangeable.

Signal 2

Target reflectivity, weather, sunlight, minimum range and angular sampling can dominate robot perception performance.

Signal 3

Physical sensor output must be separated from optional perception software and from the downstream robot localization or obstacle-avoidance result.

PROCUREMENT QUESTIONS

Questions to resolve before comparison or purchase.

A useful quotation should identify the configuration and answer these boundaries in writing.

  1. What exact model, hardware revision, wavelength, scan pattern, field of view and connector/cable set are quoted?
  2. Under what reflectivity, ambient light, weather, frame-rate and detection-probability conditions are range and accuracy figures stated?
  3. Which PTP/PPS/GNSS or other synchronization modes, timestamp location and clock-accuracy limits apply?
  4. Which firmware, SDK, driver, packet format, operating-system and ROS integration versions are maintained?
  5. What ingress, shock, vibration, eye-safety, regional certification, lifecycle, calibration and service evidence attaches to the exact unit?
CURRENT EVIDENCE BOUNDARIES

What this dossier does not prove.

These limits prevent company-level research from being mistaken for product validation.

A maximum-range statement does not prove detection or localization performance for a robot-specific target and environment.

An eye-safety statement or certificate for one model cannot be generalized to the entire portfolio.

RCI has not captured RoboSense packets, benchmarked a sensor or validated a complete perception stack.

EVIDENCE DEPTH

What the current RCI record set actually supports.

12 claim-level observations point to 1 distinct source URLs; unresolved conditions remain visible.

Profile state

Exact-model evidence linked

At least one exact component record is linked below.

Product focus

Mechanical and solid-state LiDAR sensors with perception software

Scope is descriptive and does not establish regional availability, fitness or equivalence across product families.

Evidence surface

1 models · 12 claims

1 distinct claim sources and 5 explicit unknown, conflict or limitation entries.

Editorial next step

Deepen the weakest conditions

Prioritize thermal, lifecycle, compatibility and independent-test gaps.

CATEGORY-SPECIFIC REVIEW

Questions RCI applies before comparison.

These checks define the evidence work still required; they are not claims about this manufacturer.

B

Perception & Sensing

  • Bind range and accuracy to target, light and reflectivity
  • Preserve calibration, synchronization and filtering conditions
  • Pin firmware, SDK and host-platform support
  • Separate sensor output from downstream perception claims
AUDITED RECORDS

Components in the current release.

Every value on these records points to a claim-level source and verification date.

Automotive-grade mid-range digital LiDARactive

RoboSense

M2

The exact M2 page is retained, including the 10% reflectivity range condition, average angular sampling and single-return point rate. Platform-level qualification and supplier test-hour statements are not promoted to an independent M2 robot benchmark.