Introduction
Axiom MA Osc Lite answers one question across multiple timeframes at once: **how far is price from its moving average right now?**
Written By Axiom Admin
Last updated About 1 month ago
Axiom MA Osc Lite
What this tool does
Axiom MA Osc Lite answers one question across multiple timeframes at once: how far is price from its moving average right now?
It measures the distance between price and a baseline moving average, adjusts that distance for the instrument's current volatility, and converts the result into a bounded score from β100 to +100. It does this independently for up to three MA slots, each running on its own timeframe β and optionally on a different ticker entirely. The individual slot readings can then be blended into a single composite oscillator using configurable weights.
The result is a separate-pane oscillator that tells you how stretched price is relative to its averages at different time scales, all on the same bounded range, regardless of the asset's price level or current volatility.
Why this exists
If you trade with moving averages, you already think about distance. You notice when price pulls away from an average and you notice when it snaps back. But turning that observation into something you can compare across timeframes β or across different instruments β is harder than it sounds.
A raw distance number (price minus MA) depends on the instrument's price level. A distance of 50 points means something very different on the S&P 500 than on a $20 stock. Even on the same instrument, a 50-point move during a quiet week means something different than a 50-point move during an earnings gap.
Most traders handle this by stacking separate oscillators β an RSI on the 5-minute, another on the 15-minute, maybe a Stochastic on the hourly β and then mentally comparing readings across panes that use different scales, different bounding methods, and different underlying math. That works, but it is slow, cluttered, and easy to misread under pressure. Three panes, three scales, three mental conversions β and you are supposed to synthesize all of that while the market is moving.
Axiom MA Osc Lite exists because that problem kept showing up. It normalizes the distance by the instrument's own volatility (ATR), which makes the score unitless. A reading of +60 on Apple and +60 on Bitcoin both mean the same thing: price is moderately above the average, relative to how much that instrument normally moves. That normalization is what lets you put different timeframes and different tickers on the same scale without the numbers fighting each other.
The oscillator also makes the repaint tradeoff explicit. A global On Bar Close switch controls whether higher-timeframe data comes from confirmed candles or from the still-building bar. Most multi-timeframe oscillators on TradingView bury this choice or make it for you silently. Here, the switch is in the settings and the consequences are documented. You decide whether to trade speed for historical stability, and you make that decision knowing what each side costs.
This is not RSI
If you have used RSI, Stochastic, or MACD, you will be tempted to read this oscillator the same way. It occupies a similar spot on the chart β a bounded line in a separate pane β but the construction is fundamentally different, and the differences matter for interpretation.
Different bounding method. RSI uses a ratio of average gains to average losses, which naturally produces values between 0 and 100. This oscillator uses a hyperbolic tangent function (tanh) that squashes a raw distance score into β100 to +100. The tanh function is smooth and symmetric around zero, but it has a specific property you need to understand: it flattens near the extremes. A reading that moves from +50 to +70 represents a meaningful increase in distance. A reading that moves from +90 to +95 may represent a much larger increase in actual distance, but the oscillator compresses it into a tiny visual change. This is called saturation, and it means the oscillator loses resolution exactly where you might want it most β when price is far from the average and you are trying to gauge whether the stretch is accelerating or decelerating.
Different threshold semantics. RSI's 70/30 levels carry some empirical weight in range-bound conditions β traders have decades of experience with what those zones tend to mean. The overbought and oversold levels on this oscillator (default +70/β70) are arbitrary marks on a tanh-bounded scale. They do not carry the same probabilistic meaning. Crossing +70 here means "the normalized distance from the MA is large enough to meet a threshold you set." It does not mean reversal is likely.
Different scale. This oscillator runs from β100 to +100, not 0 to 100. The zero line has a concrete meaning: it separates positive distance (price above the MA) from negative distance (price below the MA). RSI's 50 level does not map to the same idea.
Different persistence at extremes. RSI tends to oscillate out of extreme zones relatively quickly in most conditions. The tanh-bounded oscillator can sit near +100 or β100 for extended periods during strong trends β because the distance from the MA in ATR units remains large, and the tanh function holds it at the bound. Expecting a quick reversal from an extreme reading here will lead to premature countertrend trades.
The mental model you need is not "this is like RSI but different." The mental model is: this is a distance gauge with a compressed dial face. The needle moves freely near the center but physically cannot push past the edges of the dial, and the markings get closer together the further out you go.
Who gets value from this
Traders who already use moving averages for trend context and want a companion tool that converts the "how far is price from the average?" question into a readable, bounded number across multiple timeframes without stacking separate oscillator instances.
Traders who work across multiple instruments and want to compare MA-distance on the same scale. Because the oscillator is ATR-normalized, a reading of +50 on one ticker and +50 on another represent comparable levels of stretch relative to each instrument's own volatility. You can blend these readings into a composite if the instruments share some structural relationship.
Systematic traders building multi-timeframe confirmation logic who need oscillator values they can trust in historical review. With On Bar Close enabled, the readings in history match what was available when each bar closed β no future-leaked higher-timeframe data contaminating the picture.
Traders who are tired of oscillator panes they cannot fully explain. This manual exists to help you understand what the oscillator actually computes, how the bounding works, where the resolution degrades, and what the sensitivity parameter really does. If you are willing to spend time learning the construction, the tool becomes something you can reason about rather than something you react to.
Who should look elsewhere
Traders looking for a buy/sell signal oscillator. This tool measures distance. It does not generate entries, exits, or directional calls. If you want a line that tells you when to trade, this is not it.
Traders who want a standard RSI or Stochastic and would be confused or frustrated by the different saturation properties, the β100 to +100 scale, or the fact that overbought does not mean "time to sell." The construction is different enough that importing RSI habits will lead to misreads.
Complete beginners who have not yet developed a feel for what a moving average represents. This manual assumes you know what a moving average is and why timeframe matters. If those concepts are still new, start with the basics before adding a multi-timeframe oscillator to your chart.
The trust boundary
Before you go further, carry these four things with you through the rest of the manual. They are easy to forget under pressure, and each one has cost someone real money at least once:
The oscillator loses resolution at the extremes. When the reading is near +100 or β100, the bounding function compresses a wide range of actual distance into a narrow band. A reading of +95 and a reading of +99 can represent very different situations, but the oscillator cannot show you the difference. The further out you go, the less the number moves even when the underlying distance changes significantly. This is the zone where you most want gradation β and it is exactly where the oscillator cannot give it to you.
The sensitivity parameter reshapes the entire scale. It is not a quality dial or a reactiveness knob. It changes how much of the β100 to +100 range the oscillator actually uses under normal conditions. A reading of +70 at sensitivity 0.5 represents a different distance than +70 at sensitivity 2.0. If you change sensitivity, you have changed what every number on the oscillator means. Comparisons across different sensitivity settings are not valid.
The blended line can hide disagreement. When you blend three slots into one composite, a weighted average of one positive and one negative slot produces a near-zero reading that looks calm. But calm is not the same as agreement. One slot screaming while two are quiet averages into a gentle number β and that gentle number tells you nothing about the screaming. Always check the individual slot lines when the blend feels ambiguous or when you are about to act on it.
Overbought and oversold are your opinion, not the oscillator's. The OB and OS levels are thresholds you set. They are not statistically derived boundaries. Crossing +70 means the oscillator reached a line you drew. It does not mean the market is about to turn, or that momentum is exhausted, or that you should do anything in particular. What you do at that level is your decision β the oscillator just told you the reading got there.
What is in this manual
If you are loading the indicator for the first time, start with Quick Start.
If the oscillator just did something you did not expect, start with Troubleshooting.
If you want to understand the construction before you configure anything, start with For the Geeks.