Every closed-circuit rebreather dive leaves behind a detailed record, and almost nobody reads it. You surface, rinse the unit, break down the loop, and the most honest account of what just happened stays locked in the controller’s memory. The handset in front of you only ever showed a live snapshot — the number you needed in the moment — while the full recording quietly captured the whole story at a level of detail no diver can hold in their head.

That recording is the closest thing a rebreather diver has to a flight-data recorder. It logs what each oxygen cell was reading, how tightly the controller held your setpoint, your depth and time, and how the scrubber warmed through the dive. The kind of slow drift that never trips an alarm underwater is exactly what shows up when you plot the dive afterward. Reading it is one of the cheapest safety and skill tools you own, and it is the habit that separates divers who catch a problem early from the ones who get surprised by it.

Why Does Your Rebreather Log Every Dive?

The handset is built for decisions you make underwater, not for the full picture. It shows current oxygen partial pressure, depth, the setpoint the controller is targeting, and maybe a scrubber temperature reading — a tight, live view tuned for the next few minutes. Behind that screen, the controller is writing a far more complete record to memory: a time-stamped trace of every parameter, sampled every few seconds for the entire dive. Getting at it means moving the data off the unit and onto a computer, where curves replace single numbers.

That transfer is the step most divers skip, usually because it needs a physical link between the handset and a laptop. On many AP Diving setups that link is a small Bluetooth adaptor that pairs the handset to the desktop software, and it is the one piece of kit standing between a dive you can only remember and a dive you can actually study. Once the dive is on your screen as a graph rather than a number, patterns that were invisible in the water — a cell lagging its neighbors, a setpoint you never quite settled, a scrubber warming faster than usual — jump out in a few seconds of scrolling.

What a full dive log actually holds

A complete log is more than a depth profile. It carries each oxygen cell’s individual reading, the setpoint the controller chased and how often the solenoid fired to hold it, the full depth-and-time curve, water and scrubber temperature, and any alarms or diver-triggered events. That combination is what makes the record diagnostic rather than decorative — it lets you reconstruct not just where you went, but how the unit behaved the whole way there and back.

What Can Each Oxygen Cell’s Log Trace Reveal?

The single most useful thing in the log is the separate oxygen cell traces plotted together. Underwater the handset votes those cells into one number so you can dive; the log lets you pull them back apart. Healthy cells track each other closely through the whole dive, rising and falling in near-unison as depth and setpoint change. When one cell starts reading consistently high or low, or flattens out and stops responding near the top of its range, you are looking at the early signature of a cell reaching the end of its useful life — long before it becomes a voting problem at depth.

None of that announces itself as a hard failure on any single dive, which is exactly why the log matters: it is a trend you read across dives, watching how your oxygen sensors age across their stamped service life rather than waiting for a warning. A cell that looked fine last month but now lags a millivolt or two behind its neighbors at your working setpoint is quietly telling you to plan a replacement on your schedule, not on the boat with a dive plan already written.

Current limiting is easier to see than to feel

When a cell can no longer produce the current a high oxygen partial pressure demands, it current-limits: it reads lower than reality at precisely the moment you rely on it most, on a high-setpoint decompression stop. In the log that shows up as a cell that tracks its neighbors fine at low partial pressures but pinches off up high. That is information you almost never get from the handset in the moment, because in the water the vote hides the disagreement instead of exposing it.

How Well Did You Actually Hold Your Setpoint?

The controller’s job is to hold your loop at the oxygen level you asked for, and how tightly it managed that is a quality signal worth reading. A clean dive shows the measured value riding close to the setpoint line with small, regular solenoid corrections. Big swings, a long chase after every depth change, or a partial pressure that sits consistently above or below target all point at something worth understanding — diluent added too aggressively, a sticky solenoid, buoyancy work disturbing the loop, or simply a setpoint that does not suit the profile you dived.

Reading those swings after the fact also sharpens the choice you make before the next dive, because which setpoint makes sense for a given depth and deco plan is a decision the log lets you second-guess with real data instead of habit. If your trace shows you fighting the loop on every ascent, that is a cue to revisit both your technique and the setpoint schedule you are running — the graph turns a vague feeling that the dive was busy into a specific thing you can fix.

Manual additions leave fingerprints

Every time you add diluent or oxygen by hand, the log shows a step in the trace. Reviewing those steps tells you whether your manual gas management was smooth and anticipatory or reactive and late. That is a skill you can only improve if you can see it, and the record is the only place it is written down honestly — memory tends to round off the moments where you were a beat behind the unit.

What Does the Log Say About Your Scrubber?

Units fitted with a temperature-monitoring stick record the scrubber’s thermal profile, and that curve is one of the better real-world reads on how your carbon dioxide absorbent is performing. As the reaction front moves through the canister, the warm zone migrates, and the log captures how far and how fast. A scrubber that heats predictably and holds a strong warm band deep into the dive is doing its job; one that cools early, or never develops a clear warm zone, is hinting that packing, absorbent age, or cold water cut its real working life short.

The log turns an abstract rating into something specific to the dive you actually did, which is why it pairs so well with understanding what really drives your scrubber’s working duration instead of trusting the number on the box. Cold water, a high work rate, and deep dives all pull that duration down, and the thermal trace is where those effects stop being theoretical and become a line you can point at on the screen.

Read the trend, not just the dive

One scrubber curve is a data point; a folder of them is a baseline. When today’s warm zone develops later or fades sooner than your normal pattern, you have caught a change worth explaining before it costs you bottom time. The value is in the comparison, so the goal is not to admire a single graph but to know what your own normal looks like well enough to notice when a dive falls outside it.

How Do You Build Log Review Into Your Routine?

A dive log only compounds in value if you keep and compare the files, so the aim is a habit light enough to survive a tired post-dive evening. Download the dive the same day, while the details are fresh, and give it a quick scan for anything that departs from your normal picture: cells that drifted apart, a setpoint you chased, a scrubber that behaved oddly. Save every file in one place so you are building a personal baseline over months rather than collecting a pile of one-off snapshots you never look at twice.

Pair the numbers with a sentence or two of context — water temperature, how hard you worked, how the unit felt on the loop — because the reason behind an odd trace is often in what you were doing, not just what the sensors saw. Over a season that combined record becomes the most honest coach you have. It remembers the dives you would rather forget, flags the slow changes your memory smooths over, and gives you something concrete to bring to a course, a mentor, or a service technician when a question comes up.

When the log says something you can’t explain

Not every anomaly has an obvious cause, and that is the right moment to get another set of eyes on the data rather than guessing. A trace you cannot account for — a cell behaving strangely, a scrubber curve that does not fit your history — is a reason to pause and ask before the next dive, not after it. Treating an unexplained log as a question rather than a shrug is what keeps self-review from turning into false confidence.

How Does Silent Diving Help You Read Your Logs?

Silent Diving has been the exclusive AP Diving distributor for North, Central, and South America for more than 20 years, and the team servicing Inspiration and Evolution units reads these logs for a living. When your data shows a cell drifting, a solenoid firing oddly, or a scrubber trace that does not match your history, that is exactly the kind of thing worth handing to people who work on the platform every week rather than puzzling over it alone at the kitchen table.

If a dive left you with a record you cannot fully explain, the rebreather service and repair team at Silent Diving can help connect what the trace is showing to what the unit actually needs — whether that is a cell replacement, a controller check, or simple reassurance that the dive was cleaner than it felt. Reading your own logs makes you a sharper diver; having a specialist to call when the data raises a question is what keeps that habit from sliding into guesswork.

Frequently Asked Questions

Do I really need to download every rebreather dive?

Downloading every dive is the habit that makes the data useful, because most of what a log reveals is a trend rather than a single dramatic event. A cell drifting, a scrubber curve shifting, or a setpoint you keep chasing only becomes obvious when you can compare today against your normal picture. If downloading every dive is unrealistic, at least capture any dive that felt off, ran deep, or worked the unit hard.

What do I need to get the log off my handset?

You need a computer running the desktop logging software and a communication link between it and the handset. On many AP Diving setups that link is a small Bluetooth adaptor that pairs the unit to the software, which is what lets you pull the recorded dive across and view it as a graph. Once it is transferred, the whole dive is on screen as curves you can scroll through and compare.

What should I look at first in a CCR dive log?

Start with the oxygen cells plotted together. Healthy cells track each other closely all dive; a cell reading consistently high or low, or flattening near the top of its range, is the clearest early warning the log gives. After that, look at how closely the measured oxygen level held your setpoint, then at the scrubber temperature trace. Those three views cover most of what matters on a routine review.

Can a dive log really tell me a cell is failing?

It can show you the early trend, which is more useful than a single pass or fail. A cell that begins lagging its neighbors, responds sluggishly, or current-limits at high partial pressure is signaling that it is aging out, often well before any handset warning. Reading that trend across several dives lets you replace a suspect cell on your own schedule instead of discovering the problem at depth.

How long should I keep my dive logs?

Keep them indefinitely and in one place. The whole point of the record is comparison over time, so a file from six months ago is what makes today’s dive readable as normal or unusual. A tidy archive also gives a service technician real history to work from if a question ever comes up, which is far more useful than trying to describe from memory how a past dive felt.

What if I see something in the log I don’t understand?

Treat it as a question to answer before your next dive rather than something to explain away. An unexplained cell trace, an odd scrubber curve, or a setpoint the controller could not hold is worth reviewing with someone who works on the platform. Getting a specialist’s read on the actual data is quicker and safer than guessing, and it often turns an unsettling graph into a clear, fixable answer.