Quick Start

Quick Start

This page gets the indicator on your chart, confirms it is working, and walks you through the first things that might look wrong but are not. The goal is five minutes to a working setup, not five minutes to full understanding. Configuration depth comes later in Settings.

Step 1: Add the indicator

Search for Axiom MA Osc Pro in TradingView's indicator panel and add it to your chart. It will appear in a separate pane below the price chart — it is not an overlay.

Before you add it, check your chart timeframe. The default slot configuration uses 5-minute, 15-minute, and 60-minute timeframes. Your chart timeframe must be equal to or lower than the lowest slot timeframe. For the defaults, that means your chart should be on 5 minutes or lower. If your chart is on 15 minutes, the 5-minute slot will throw a runtime error and the indicator will not render.

If you are on a higher chart timeframe and want to use the defaults, either lower your chart timeframe or open the settings and adjust the slot timeframes upward. There is no way around this constraint — it is enforced to prevent the indicator from requesting data that does not exist at the resolution you are asking for.

Step 2: Check what you see

With the defaults loaded on a 5-minute (or lower) chart, you should see:

• Three lines oscillating between -100 and +100. These are the Fast lines for slots MA 01, MA 02, and MA 03. Each one measures how far price sits from its baseline MA on its assigned timeframe.

• MA 01 (teal): 5-minute timeframe, EMA 20

• MA 02 (aqua): 15-minute timeframe, EMA 20

• MA 03 (blue): 60-minute timeframe, EMA 20

• Two additional lines — the blended Fast (lime/red) and blended Slow (gray), with a colored fill between them. These represent the weighted composite of the three active slots.

• Five horizontal reference lines: +100 (red), overbought at +70 (gray dashed), zero (gray solid), oversold at -70 (gray dashed), and -100 (green).

• No runtime errors in the Pine console.

If this matches what you see, the indicator is working correctly. Move to Step 3.

Step 3: First sanity check

Find a recent period where price made an obvious move — a clear rally or a clear drop that you can identify on the price chart without the indicator's help.

Look at the oscillator pane during that move:

• During a rally, the blended Fast line should be positive (above zero). The individual slot lines should mostly be above zero as well, though slower timeframe slots may lag.

• During a drop, the blended Fast line should be negative (below zero).

• If the reading is inverted — positive during a drop, negative during a rally — something is misconfigured. The most common cause is a slot pulling data from the wrong ticker (check the Optional Ticker field in settings).

This check is not about precision. You are confirming that the oscillator's direction agrees with the obvious price direction. If it does, the basic configuration is sound.

If the market was mostly sideways during the period you picked, the readings will be mixed and hard to interpret. That is not a problem — pick a different period where price moved clearly in one direction. The sanity check works best on moves you can identify with confidence. You will learn to read ambiguous conditions later; right now you just need to confirm the wiring is correct.

Step 4: Confirm history is stable

Scroll back in time on your chart. Watch the oscillator lines as you scroll.

They should not change. The values on completed bars should remain exactly where they were. This is the default non-repainting behavior — each slot has On Bar Close enabled, which means it uses only confirmed higher-timeframe data.

If you see completed-bar values changing in the default setup while you simply scroll, first confirm all enabled slots still have On Bar Close turned on. If you intentionally turned a slot to live mode, do not use scroll-stability as the test — the meaningful check is to watch that slot through an actual higher-timeframe bar close. See MTF & Repainting for the right verification workflow.

What looks wrong but is not

These are the most common first-load reactions that feel like a problem but are actually the tool working as designed:

"The indicator looks flat or dead"

Your slot timeframes may be much higher than the chart timeframe, or your sensitivity may be set too low for the instrument you are watching. On a 1-minute chart with slots set to 240m, D, and W, confirmed higher-timeframe slots update in steps and can look quiet between higher-timeframe closes. That is not a malfunction — it is the script waiting for those higher-timeframe contexts to move.

What to do: Either bring the slot timeframes closer to the chart timeframe, or accept that very high-timeframe slots will update slowly. If the structure is right but the readings still hug the middle, raise ATR Sensitivity a bit and see whether the oscillator starts using more of its range.

"One of the slot lines is missing"

That slot's Optional Ticker field may contain an invalid symbol, or the slot is pulling from a ticker that has no data for the requested timeframe. The slot returns na (not available) and the line disappears.

What to do: Open settings and check the Optional Ticker field for that slot. Clear it to use the chart's symbol, or correct the ticker. Also check that the ticker has data on the timeframe you are requesting — some instruments do not have intraday data on all providers.

"The blended line does not match any individual slot"

This is correct behavior. The blended line is a weighted average of all enabled slots. It will generally sit somewhere between the individual slot readings, pulled toward whichever slot has the highest weight. If one slot is at +60 and another is at -40 with equal weights, the blend will be near +10. It is a composite, not a selection.

"Colors keep flickering on the current bar"

If On Bar Close is disabled for any slot, that slot's Fast line updates in real time as the higher-timeframe bar builds. The color comparison (Fast vs. Slow) recalculates with every tick, which can cause the color to flicker near crossover points. This is expected when you have allowed real-time updating. It will stop flickering once the higher-timeframe bar closes and the value locks in.

"I got a runtime error immediately"

The error message should say something about a slot timeframe being lower than the chart timeframe. Check each enabled slot's TimeFrame setting. Every slot's timeframe must be equal to or higher than your chart timeframe, or left blank (which inherits the chart timeframe). There is no workaround — this is a hard constraint.

What to do next

If the indicator is on your chart, the lines are moving, and the history looks stable, you have a working setup. From here:

• To understand what the lines and colors mean, go to Visuals & Logic.

• To customize the slots for your instruments and timeframes, go to Settings. Read the slot anatomy section first — it will save you time.

• To understand the repaint tradeoff before you change any On Bar Close toggles, go to MTF & Repainting.

• To set up alerts, go to Alerts — but understand the continuous-vs-event distinction first, or you will get more notifications than you expect.

The defaults are a deliberate starting point. They are not something you need to change immediately, but they are not tuned for your specific instruments, timeframes, or process. Resist the urge to enable five more slots right away. The most useful next step is understanding how the current three-slot setup reads for your instrument — what the oscillator shows during a move you already understand. Once you have that baseline feel, adjustments become informed rather than experimental.