One Sensing Toolkit, Six Robotics Worlds: How ScioSense Components Power Perception

Introduction

Let’s talk about this engineering reality: a robot is only as capable as what it can sense. Obstacle detection, positioning, orientation, and autonomy all begin at the sensor itself and at the integrated circuits (ICs) that convert physical events into digital data with enough precision to be worth acting on.

ScioSense is a component supplier whose portfolio (time-to-digital converters, capacitance-to-digital converters, resistance-to-digital front ends, and environmental sensor ICs) provides the building blocks engineers assemble into LiDAR receivers, capacitive skins, load cells, and environmental modules. 

Across six very different robotics sub-segments, the same compact set of ICs keeps appearing. For a design engineer planning across multiple platforms, this overlap is the real story. 

The Six Robotics Segments at a Glance

To understand how a single component toolkit scales, it is necessary to examine the diverse operational requirements across the six primary robotics segments:

• Industrial Robotics: Fixed arms and collaborative cobots in manufacturing environments, where repeatability, safety-zone monitoring, and condition-based maintenance dominate the sensing requirement.

• Service Robotics: Cleaning, delivery, and hospitality bots operating in semi-structured indoor spaces, where navigation and human-adjacent safety are central.

• Medical Robotics: Surgical assistants, diagnostic platforms, and rehabilitation devices, where accuracy and patient safety are non-negotiable and every sensor sits inside a regulated context.

• Mobile Robotics: AMRs and AGVs in warehouses and logistics, where SLAM, obstacle avoidance, and fleet positioning drive the sensor architecture.

• Humanoid & Social Robotics: Bipedal and interaction-focused platforms that require rich multimodal sensing in dynamic environments.

• Defense Robotics: EOD systems, reconnaissance platforms, and unmanned ground vehicles, where ruggedisation and harsh-environment performance define the design envelope.

The sensing priorities differ across these six worlds. The component-level building blocks, as we'll see next, largely do not.

The Cross-Segment Component Pattern

The ScioSense component-to-segment matrix reveals a pattern that is easy to miss when each segment is viewed in isolation: with one specific and logical exception, the same core ICs apply across all six robotics segments.

So, why does this happen at the component level? Because regardless of whether a robot is welding a chassis, delivering room service, or clearing a path, it broadly needs to do the same physical things: measure time of flight, detect proximity and presence, sense its environment, and monitor its own internal state. The application context changes; the underlying physics does not.

Grouped by sensing function rather than by part number, the portfolio maps cleanly onto the block diagram of almost any robotic sensor stack:

• Distance and Ranging: The time-to-digital converter family: LTDC-X3, TDC-GPX2, AS6501, AS6500, and the higher-end TDC-GPX provides the precision timing layer inside LiDAR and time-of-flight designs.

• Proximity, Touch, and Presence: The PCAP04 capacitance-to-digital converter serves as the front end for safety bumpers, capacitive skins, HMI surfaces, and capacitive pressure sensing.

• Force, Torque, and Position Feedback: PS09 and PS081 resistance-to-digital converters handle strain-gauge and load-cell read-out inside joints, end effectors, and force-sensitive interfaces.

• Environmental Awareness: ENS16x multi-gas sensors, and ENS21x temperature-and-humidity sensors support both operating-condition monitoring and context sensing.

• Power-Sensitive Event Detection: The AS3930 / AS3932 / AS3933 low-frequency wake-up receivers allow battery-driven platforms to remain dormant until a defined event occurs.

• Outdoor Situational Awareness: The AS3935 Franklin Lightning Sensor™ provides storm-front detection for platforms deployed in the field.

The single exception in the matrix is the AS3935, which maps to five of the six segments but not to Medical Robotics, which is an entirely logical omission, since medical robots operate indoors and have no meaningful need for lightning detection. Every other IC in the portfolio applies across all six segments. 

Spotlight: LTDC-X3 as the Proof Point

The LTDC-X3 two-channel time-to-digital converter is a clean example because it demonstrates the "One IC, One Sensor Type, all Six Segments" pattern in a single component.

In a LiDAR receiver, TDC timestamps the arrival of the returning photon with picosecond-level resolution. That timestamp is what converts "light bounced off something" into "an obstacle 4.2 metres ahead." The TDC is the receive-path measurement engine, everything downstream in the point-cloud pipeline depends on the quality of that timestamp.

That single function has applications in every one of the six segments:

• Mobile Robots use LiDAR-derived point clouds for SLAM and obstacle avoidance in warehouse and logistics deployments.

• Industrial Cells use LiDAR for safety-zone monitoring and intrusion detection around fenced and unfenced work areas.

• Service and Humanoid Platforms use it for orientation and free-space perception in unstructured, human-shared environments.

• Medical Platforms use it for workspace mapping and proximity awareness around the patient and clinical staff.

• Defense Platforms use it for terrain mapping, obstacle awareness, and threat detection in field conditions.

The same underlying TDC technology used to build robot LiDAR is used inside LiDAR systems for autonomous cars. For a robotics engineer specifying components, that is a useful signal; the part has already been pushed against automotive-grade reliability expectations, even if the platform it goes into never leaves a warehouse floor.

LTDC-X3 is one part of a broader TDC family. AS6500, AS6501, TDC-GPX, and TDC-GPX2 each offer different combinations of resolution, channel count, and power envelope. This helps engineers scale their LiDAR architecture, from short-range solid-state modules through to high-end scanning systems, without leaving the ScioSense catalogue.

Cross-Applications: Where One IC Enables Several Sensor Types?

The second insight in the matrix is arguably more interesting than the first. Some ScioSense ICs don't only span segments, they span sensor categories. That is where the BOM-consolidation argument really lands. 

A few examples include:

• PCAP04 shows up behind touch sensors, proximity sensors, and capacitive pressure sensors. One qualified part covers three distinct sensor modalities that a service or humanoid robot might all use in different places on the same platform.

• PS09 and PS081 cover both force/torque sensors and strain-gauge front ends, which are the same physical measurement problem in two different mechanical wrappers. A collaborative arm joint and a surgical end-effector might use both — with the same front-end IC.

• ENS21x collapses temperature and humidity into a single device, useful for both ambient monitoring and condition-based maintenance data streams.

• TDC family scales from short-range time-of-flight through to high-end lidar without changing supplier, which matters for engineers who want a consistent qualification path as their sensor architecture matures.

Choosing ScioSense components can compress a BOM. One qualified part can serve multiple sensor modalities, reducing supplier count and easing reuse across product lines targeting different robotics segments.

The Market Context

Let’s see briefly why the cross-segment story matters right now. Three market beats are worth surfacing, without turning this into a market report. 

• Solid-State LiDAR is showing the strongest growth rate among robotic sensing categories, which is exactly where TDC-based ICs like LTDC-X3 are most relevant.

• LiDAR Systems, Vision/Camera Systems, and Infrared are the dominant sensing categories shaping next-generation robots.

• Industrial Robotics is where volume sits today; service robotics is the strongest near-term growth area over the next five years; humanoid robotics is a longer-horizon opportunity.

For an engineer, the practical read is this: a portfolio that already spans all six segments is well-positioned regardless of which of those curves accelerates first. The sensor stack you qualify for an industrial cobot today is largely the sensor stack you'll reuse in a service robot next year, and with adjustments in a humanoid platform after that.

Conclusion

ScioSense plays at the IC and component layer, and its portfolio is structured so that the same building blocks support sensor designs across all six robotics sub-segments.

The three practical takeaways:

1. The same ScioSense parts you qualify for one robotics platform are likely reusable on the next.

2. For LiDAR, ToF, and other ranging-based perception, the time-to-digital converter family (with LTDC-X3 as the headline part) is the place to start.

3. For multimodal perception stacks, the broader portfolio: capacitive, environmental, and analog read-out ICs is worth treating as a single, coherent toolkit rather than a list of disparate parts.

For engineers who want to map specific parts to specific designs, the documentation and details are available on ScioSense - Robotics.