Quick Start

Quick Start

This page gets Axiom CVD Osc Lite on your chart with safe defaults, confirms it is working, and flags the things that most often confuse people on first contact.

Step 1: Add the indicator

Search for Axiom CVD Osc Lite in TradingView's indicator search (or the full title, "Axiom CVD Osc Lite (MTkr, MTF CVD Stack Oscillator w/Blend)") and add it to your chart.

Use a liquid symbol — something like BTCUSDT, ES, or SPY on an intraday timeframe. A 5-minute chart is a good starting point. The default slot timeframes are 5m, 15m, and 60m, and every slot's timeframe must be at or above the chart timeframe. If you load this on a 15-minute chart, the 5-minute slot will throw a runtime error before anything draws.

Step 2: Check what you see

With defaults, the lower pane should show:

• Three colored oscillator lines — Slot 01 (teal), Slot 02 (aqua), Slot 03 (blue). Each oscillates within the -100 to +100 range, colored by its own regime: one color when the slot's CVD is above its Signal line, another when below.

• A blended CVD line with a gray Signal line and a shaded fill between them — green tint when blended CVD is above Signal, red tint when below.

• Horizontal reference lines at +100 (red), -100 (green), 0 (gray), +70 (dashed gray, overbought), and -70 (dashed gray, oversold).

• Vertical dashed lines at session boundaries. All three slots default to Session mode with a Daily window, so you should see dashed markers where the daily boundary rolls over.

If you see all of that, the indicator loaded correctly.

Step 3: Understand what "normal" looks like

A few things about the defaults that are worth noticing before you start changing anything:

The slot lines move at different speeds. Slot 01 (5m) will be the most responsive. Slot 03 (60m) will be the smoothest and slowest to change. This is expected — higher timeframes accumulate delta over more bars and respond less to individual candles.

The blended line is smoother than any individual slot. It is a weighted average of all three slots. Its purpose is to summarize, not to amplify. When the blend looks calm but the individual slots disagree, the blend is masking a conflict — not resolving it.

Readings tend to cluster between -70 and +70 most of the time. Values near +100 or -100 mean the CVD accumulation is at or near the extreme of its normalization window. Early in a session, extreme readings can happen on modest volume because the window has not built out yet. That is a cold-start artifact, not a strong signal. More on this in Visuals and Logic.

The oscillator resets at session boundaries. With the default Session mode and Daily window, the accumulation window rolls over when a new daily boundary begins. The vertical dashed lines mark where this happens. The first few bars after a reset are thin-data — the oscillator has very little history to normalize against, so early readings can swing to extremes that would not hold up once the session fills out. If you see a +85 in the first five minutes and feel tempted to read it as strong conviction, resist. The number is real — the CVD is near the top of its range — but the range is barely two bars deep. Wait for the session to build out before treating the readings as something you can reason from.

Step 4: Check the On Bar Close setting

Now that you know what the default display looks like, check the setting that determines whether you can trust the chart's history.

Open the indicator settings and find On Bar Close under PU Settings. It should be on by default.

This is the single most important setting for trust. When it is on, each slot displays the CVD value from the last completed higher-timeframe bar. Historical values are stable — what you see on past bars is what was visible at the time. When you turn it off, the oscillator updates intrabar on the higher timeframe, which feels more responsive but means past bars show the final state of each HTF bar, not what was visible while it was forming.

If you plan to scroll back through history or compare the oscillator against past price action, leave this on. If you want to understand the tradeoff fully, MTF and Repainting explains both sides in detail.

First traps

These are the things that most commonly make new users think the indicator is broken. None of them are bugs.

"The indicator threw an error when I loaded it"

Almost always a timeframe constraint. The three most common causes:

1. Chart timeframe is higher than a slot's timeframe. The default Slot 01 is set to 5m. If your chart is on 15m or higher, that slot cannot request data from a lower timeframe. Fix: switch to a chart timeframe at or below the lowest slot TF, or raise each slot's timeframe to match your chart.

2. Lower TF Precision is not strictly below the slot's timeframe. Each slot has a Lower TF Precision setting that controls how finely the estimation model samples sub-bars. It must be lower than the slot's own timeframe. Fix: set Lower TF Precision to a timeframe below the slot.

3. Window is shorter than the slot's timeframe. The Window setting (the accumulation period for Session or Rolling mode) must be at least as long as the slot's timeframe. Fix: raise the Window to at least the slot's TF.

"The oscillator looks extreme right after the session opens"

That is the cold-start effect. In Session mode, the accumulation window resets at each session boundary. The first few bars have very little data and a narrow normalization range. A modest amount of directional volume can push the reading to +80 or +90 simply because the range has not expanded yet. This is especially misleading because session opens are when many traders are most alert and most inclined to act quickly. The oscillator showing an extreme reading right when you are looking for early-session direction is a setup for over-reading thin data. Wait for the normalization range to build out before treating the readings as contextually meaningful. More on this in Visuals and Logic.

"The blended line does not match the visible slot lines"

Check whether any slots are hidden but still enabled. Each slot has both an Enable toggle and a Hide Plot toggle. Hiding a slot removes its line from the pane but does not remove it from the blend calculation. If you see two slot lines and the blend sits somewhere that does not make sense relative to those two, a third hidden slot is probably pulling it. See Settings for the full distinction between hiding and disabling.

"I changed chart timeframe and the oscillator broke"

The indicator enforces that every slot's timeframe must be at or above the chart timeframe. If you switch from a 5m chart to a 30m chart without adjusting the slot timeframes, any slot set below 30m will cause a runtime error. This is a safety check, not a limitation of the tool — it prevents the indicator from requesting data that TradingView cannot provide reliably.

What to do next

• Configure the slots for your actual timeframes. The defaults (5m/15m/60m) are a reasonable starting point for intraday work on a 5m chart, but they are not universal. If you trade on a different chart timeframe or want a different cross-TF spread, open Settings and adjust accordingly.

• Learn what the visual states mean before you start reading the oscillator. The pane shows a lot of information — regime colors, blended fill, session resets, multiple slot lines. Visuals and Logic explains what each element tells you and, just as importantly, where the chart can mislead you if you read it at the surface level.

• Understand what "estimated CVD" means for your interpretation. If you have used CVD tools before, you may be carrying assumptions about what the numbers represent. This oscillator estimates delta from candle structure, not from order flow. That changes what you can infer from the readings. The README introduces this boundary, and Limitations and Trust Boundaries maps it fully.