> For the complete documentation index, see [llms.txt](https://doc.realvirtual.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.realvirtual.io/components-and-scripts/sensors.md).

# Sensors

Components for detecting objects, measuring positions, and providing feedback in automation systems.

## Available Components

* [**Sensor**](/components-and-scripts/sensors/sensor.md) - Primary proximity sensor for detecting MUs and objects with configurable detection zones
* [**Measure**](/components-and-scripts/sensors/measure.md) - Position and distance measurement sensor for precise object positioning
* [**MeasureRaycast**](/components-and-scripts/sensors/measureraycast.md) - Raycast-based distance measurement for precise range detection

## Key Features

* **PLC Integration**: Direct connection with PLCOutputBool and PLCOutputFloat signals
* **Visual Feedback**: Editor gizmos and runtime visualization of detection zones
* **Configurable Detection**: Adjustable zones, timing delays, and object filtering
* **Logic Integration**: Works with Logic Steps and Behavior Graph systems

## See Also

* [Logic Steps](/components-and-scripts/defining-logic/logicsteps.md) - Automation sequences using sensor inputs
* [Interfaces](https://github.com/game4automation/doc/blob/doc/components-and-scripts/interfaces/README.md) - PLC communication for sensor data


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.realvirtual.io/components-and-scripts/sensors.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.