> For the complete documentation index, see [llms.txt](https://carec.gitbook.io/carec-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://carec.gitbook.io/carec-docs/documentation/safety/sensor-failure-mode-analysis.md).

# Sensor Failure-Mode Analysis

| Failure               | Detection                       | Required response            |
| --------------------- | ------------------------------- | ---------------------------- |
| Disconnected sensor   | Link or health fault            | Degrade dependent capability |
| Frozen frame          | Timestamp/hash inconsistency    | Never report clear           |
| Stale data            | Maximum-age threshold           | Reject and transition safe   |
| Obstructed lens       | Quality/confidence check        | Fault alert                  |
| Exposure failure      | Image statistics and confidence | Reduce capability            |
| Implausible range     | Bounds or cross-check           | Reject or lower confidence   |
| Misalignment          | Calibration/scene consistency   | Maintenance fault            |
| Excess latency        | Deadline monitor                | Exclude late result          |
| Intermittent link     | Error counters                  | Log, alert, safe transition  |
| Corrupt configuration | Schema/checksum validation      | Refuse activation            |

Each failure is injected in simulation and hardware where applicable. Record detection time, motion response, alerts, recovery, logs, and any interval during which CAREC could incorrectly present a healthy state.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://carec.gitbook.io/carec-docs/documentation/safety/sensor-failure-mode-analysis.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.