Quick Start

This page is about the shortest correct first run for Axiom RSI Osc Pro.

Written By AxiomCharts

Last updated About 2 hours ago

Quick Start

This page is about the shortest correct first run for Axiom RSI Osc Pro.

The first goal is not to build your final stack in one sitting. The first goal is to get one stack running cleanly enough that you can tell what the tool is helping with, what it is not settling for you, and what still needs verification before the pane earns more trust.

First decision: which path fits your chart?

Start here before you read the pane.

If this is trueUse this pathWhy
Your chart is `1m` or `5m`, and you want to try the shipped stack firstPath AThe default `5 / 15 / 60` ladder can load as intended
Your chart is above `5m`, or you already know the shipped ladder is not the right first baselinePath BYou need to adapt the active slots before the script can run cleanly

Why this matters:

  • every enabled slot must stay at or above the chart timeframe
  • the shipped defaults are useful, but they are not chart-timeframe-neutral
  • if you skip this check, the rest of the setup becomes harder than it needs to be

What a correct first run should look like

Before you worry about alerts, extra slots, or MA-family choices, a healthy first run is simpler than most people expect:

  • the script loads without a timeframe runtime error
  • you can name which slots are active
  • you know whether those slots are confirmed or still forming
  • you can tell which active slots are shaping the blend
  • the pane still feels explainable in plain language

If you do not have those five things yet, stay on this page a little longer.

Path A: use the shipped baseline as intended

Use this path when your chart timeframe is `1m` or `5m`.

  1. Add Axiom RSI Osc Pro to the chart.
  2. Confirm that you can see a lower pane with three visible slot lines and the blended pair.
  3. Open the settings panel and confirm the first three slots are still enabled with `TimeFrame:` values of `5`, `15`, and `60`.
  4. Confirm `On Bar Close?` is still on for those active slots.
  5. Leave `Optional Ticker:` blank, `Enable Master Smoothing` off, and slots 4 through 10 disabled for the first pass.
  6. Temporarily set one active slot's `Blended Weight:` to `0` and confirm the blended pair changes while that slot itself can still stay visible.
  7. Return the weight to its prior value before moving on.

What you should be able to say before leaving this path:

  • "This is a same-symbol three-slot baseline."
  • "My active slots are still in confirmed mode."
  • "The blend is reacting to weighted slots, not acting like a separate engine."

Path B: adapt the baseline before you trust it

Use this path when your chart timeframe is above `5m`, or when you already know the shipped `5 / 15 / 60` ladder is not the right first baseline.

  1. Add the indicator.
  2. Open settings immediately.
  3. For each enabled slot, compare `TimeFrame:` to the chart timeframe.
  4. Raise the slot timeframe, clear it so it inherits the chart timeframe, or disable the slot for now if it conflicts.
  5. Keep `On Bar Close?` on for every active slot during the first pass.
  6. Leave `Optional Ticker:` blank and `Enable Master Smoothing` off.
  7. Confirm the pane now loads with only the layers you intended to keep.

What you should be able to say before leaving this path:

  • "Every enabled slot is legal on this chart."
  • "I know which slots I kept on purpose."
  • "I am learning the stack I built, not fighting the stack I inherited."

Three quick sanity checks

Run these before you create alerts or expand the stack. Each one teaches a rule that matters later.

CheckHow to do itWhat you should seeWhat it teaches
Hide versus disableTurn on `Hide RSI 01 Plot` while leaving `Enable RSI 01` onThe line disappears, but the slot is still active internallyHidden is not the same as disabled
Blend participationSet one active slot's `Blended Weight:` to `0`The slot can still plot, but the blend recalculates without itZero weight removes blend influence, not slot behavior
Trust modeTurn `On Bar Close?` off on one higher-timeframe slot and watch it during an unfinished requested barThat slot can move sooner than confirmed modeEarlier updates come with a weaker trust boundary

If any of those checks surprise you, slow down there. That is exactly the kind of misunderstanding this indicator can hide behind a clean-looking pane.

A sensible first configuration

If you are learning the indicator, keep the first session small:

  • use no more than 3 active slots
  • keep those slots on the same symbol
  • leave all active slots on confirmed mode
  • use one MA family across the first stack
  • add alerts only after you can explain what each active slot is contributing

This is not restraint for its own sake. It is how you keep the pane readable enough to verify under pressure.

If something goes wrong immediately

Start with these questions in order:

  1. Is any enabled slot timeframe lower than the chart timeframe?
  2. Did I hide a slot and then forget it was still active?
  3. Did I set every weighted contributor to `0` and remove the blend by accident?
  4. Did I turn `On Bar Close?` off and then read the slot as if nothing changed?

If you need the symptom-by-symptom version, go to Troubleshooting.

Finish line for this page

You are ready to move on when you can answer these without guessing:

  • Which active slot has the lowest timeframe on your chart right now?
  • Which active slots are confirmed, and which are still forming?
  • Which active slots are shaping the blend right now?
  • What would make this baseline less trustworthy on the next change you make?

Once that version makes sense, move to MTF and Repainting, then Settings, then Visuals and Logic.

Visual placeholder: Side-by-side screenshots showing a valid `1m` or `5m` chart using the shipped `5 / 15 / 60` baseline and a higher-timeframe chart where at least one active slot had to be raised, inherited, or disabled before the pane became usable.