> 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.

# Columns Per Packet

> Control how many measurement blocks are grouped into each lidar UDP packet.

> **Note**
>
> Supported through operator in firmware v4.0 or later.

Columns Per Packet controls how many measurement blocks are grouped into each lidar UDP packet. Adjusting this value changes packet size and packet rate while the total data per frame stays the same. Configure it from the sensor web interface **Mode** settings or through the HTTP API.

Valid values are 1, 2, 4, 8, 16, 32, and 64. The default is **16** for most sensors and **8** for OS1-MAX (256 channels).

Lower values produce smaller, more frequent packets. Higher values produce larger, less frequent packets. The maximum usable value depends on the selected lidar profile, channel count, and network packet size limits.

Values below 4 are only supported with the low data rate lidar profile in 512x10 mode.

Set the parameter with [`POST /api/v1/sensor/config`](/sensor-docs/firmware/api-reference#sensor-configuration):

```shell
curl -X POST http://os-991234567890.local/api/v1/sensor/config \
  -H 'Content-Type: application/json' \
  --data '{"columns_per_packet": 8}'
```