> This page is for Firmware, version 3.2.
> For other versions, use one of these documentation indexes:
> - 4.0 (default): https://docs.ouster.com/sensor-docs/firmware/4.0/llms.txt
> - 3.2: https://docs.ouster.com/sensor-docs/firmware/3.2/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.ouster.com/sensor-docs/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.ouster.com/sensor-docs/_mcp/server.

# Azimuth Window

> Limit lidar UDP output to a configurable angular region of interest.

The azimuth window limits UDP lidar output to a configurable region of interest, defined by a minimum and maximum bound in millidegrees. Angles in the Lidar Coordinate Frame increment counterclockwise when viewed from above:

* 0° towards the external connector
* 90° a quarter turn counterclockwise from the connector
* 180° opposite the connector
* 270° three quarter turns counterclockwise from the connector

![Image](/sensor-docs/_fern-files/_img/fdbc9443fc3a281e721dc6941238421534b311a722d26f84573d3b6818270e6a.webp)

Reducing the azimuth window lowers average output data rate but does not affect peak data rate. Lasers continue to fire outside the window, so power consumption and thermals are unaffected.

#### Expected Sensor Behavior

The sensor rounds input bounds to the nearest *Measurement Block* IDs, then uses those ID-based bounds to mask *Measurement Blocks* in lidar packets. Packets containing only masked blocks are suppressed. The two bookending packets in each frame may be partially masked; the *Measurement Block Status* field identifies valid versus masked blocks in those packets. See [Sensor Data](/sensor-docs/firmware/coordinate-system) for packet format details.

Staggered beam azimuth angles produce jagged edges at the window boundaries. Set slightly wider bounds to push jagged edges outside the desired region. The correct bounds can be found by trial-and-error or calculated from the queryable beam azimuth angles.

#### Azimuth Window Examples

Use the [sensor configuration endpoint](/sensor-docs/firmware/api-reference#sensor-configuration) to set `azimuth_window`.

Default settings of 360° window:

```shell
curl -i -X POST os-991234567890.local/api/v1/sensor/config \
  -H 'content-type: application/json' \
  --data-raw '{"azimuth_window": [0, 360000]}'
```

Set a region of interest between 0° to 180°:

```shell
curl -i -X POST os-991234567890.local/api/v1/sensor/config \
  -H 'content-type: application/json' \
  --data-raw '{"azimuth_window": [0, 180000]}'
```

Set a region of interest between 270° to 90° with 180° field of view:

```shell
curl -i -X POST os-991234567890.local/api/v1/sensor/config \
  -H 'content-type: application/json' \
  --data-raw '{"azimuth_window": [270000, 90000]}'
```

Set a region of interest 90° to 270° with 180° field of view:

```shell
curl -i -X POST os-991234567890.local/api/v1/sensor/config \
  -H 'content-type: application/json' \
  --data-raw '{"azimuth_window": [90000, 270000]}'
```

Set a region of interest between 0° to 90° with 90° field of view:

```shell
curl -i -X POST os-991234567890.local/api/v1/sensor/config \
  -H 'content-type: application/json' \
  --data-raw '{"azimuth_window": [0, 90000]}'
```

Set a region of interest 90° to 360° with 270° field of view:

```shell
curl -i -X POST os-991234567890.local/api/v1/sensor/config \
  -H 'content-type: application/json' \
  --data-raw '{"azimuth_window": [90000, 0]}'
```

#### Azimuth Laser Masking

When a limited azimuth window is set, the sensor automatically disables lasers outside that window. This reduces thermal load and can improve sustained performance at elevated temperatures.