---
title: "Setpoints"
description: "Set the descent, working and decompression setpoints, add depth-triggered overrides, and see which one is active."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.divelogic.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Setpoints

import { SetpointCard } from "@/components/react/PlannerSettingsScreens";

Setpoints live in **Plan → CCR → Setpoint Settings**. Three are always present,
and you can add depth-triggered overrides.

- **Descent Setpoint (bar)** starts at 0.7, active from the surface.
- **Working Setpoint (bar)** starts at 1.3, active once the deepest planned
  depth is reached.
- **Decompression Setpoint (bar)** starts at 1.3, active from the first
  mandatory stop to the surface.

All three accept 0.2 to 1.6 bar in steps of 0.05. Anything below 0.4 bar is
planned as 0.4 bar, and nothing in the interface tells you it was raised.

## Custom depth setpoints

The **Custom Depth Setpoints** block sits under the three fixed fields. **Add
Custom Setpoint** appends a row starting at 20 m and 1.3 bar; **Depth (m)**
takes 1 to 350 in whole metres and **Setpoint (bar)** 0.2 to 1.6 in steps of
0.05. The **✕** deletes a row, with no undo.

## Which setpoint is active

A depth trigger fires on the greatest depth reached so far, not the current
depth, and it latches: a setpoint that came on during the descent stays on
through the ascent. When several have fired the deepest custom row wins, so a
custom setpoint at 30 m on a 55 m dive leaves the working setpoint governing
nothing. The decompression setpoint sits outside that order, taking priority
from the first mandatory stop onwards.

Where a setpoint is higher than the ambient pressure, as 1.3 bar is in the top
few metres, the planner clamps the loop ppO₂ to ambient and does not warn: a
shallow stop planned at 1.3 bar is planned on a loop the machine cannot deliver
there.

> **Caution**
>
> The planner takes the setpoints as given: it does not check that one is
> reachable with the diluent you carry, that the deco setpoint is achievable at
> your last stop, or that a custom setpoint is one your controller can hold. CNS
> and OTU are tracked at the resulting ppO₂.

## In the schedule

The schedule's **Advanced** view carries a **ppO₂** column, the loop partial
pressure used for each segment. A setpoint change takes no time, so it shows as
a step in the column, not a row.

## Next

- [Diluents](/ccr/diluents) covers what supplies the inert fraction.
- [Oxygen exposure](/theory/oxygen-exposure) tracks CNS and OTU.

Source: https://docs.divelogic.ai/ccr/setpoints/index.mdx