추세 TrendFilterCrossover Builder에서 사용 가능
Moving Average
MA
A moving average smooths price into a single line that shows the direction and slope of the underlying trend. It is the baseline every other trend tool is built on, the most common filter in an EA, and the simplest indicator to turn into a no-code strategy.
- Template periods
- 10 / 50
- Methods
- SMA / EMA / SMMA / LWMA
- Scale
- Price
예시용 — 합성 데이터로, 실시간 호가가 아닙니다.
What a moving average tells you
A moving average replaces the last N prices with their average, so the noise of individual bars falls away and only the direction of the move is left. It says nothing about what price will do next — it says what price has been doing, with a lag you choose by picking the period.
- Price above a rising MA: the trend is up
- Price below a falling MA: the trend is down
- A flat MA means there is no trend to follow, whatever price is doing bar to bar
- 1 Take the last N applied prices
- 2 Average them with the chosen method
- 3 Plot the result on the price scale
공식 및 계산 세부 정보 표시
A moving average replaces the last N applied prices with a single averaged value, recomputed on every bar:
- Choose the period N and the applied price (Close by default).
- Choose the averaging method. Simple (SMA) weights every bar equally:
SMA = (P₁ + P₂ + … + Pₙ) / N. Exponential (EMA) weights the newest bar most, with a smoothing factor of2 / (N + 1). Smoothed (SMMA) and linear-weighted (LWMA) sit between the two. - Plot the result on the price scale. The line always lags price — that lag is the cost of removing noise, and the period is the dial that sets it.
Because the output shares the price scale, a moving average is directly comparable to price, which is why it doubles as a dynamic support/resistance reference and as the simplest possible trend filter. The trade-off never goes away: a shorter period tracks price closely and inherits its noise, a longer one is smooth but tells you about a turn well after it happened.
In MQL5 the call is iMA(symbol, period, ma_period, ma_shift, ma_method, applied_price) and it returns a handle to a single buffer. Both ma_method (ENUM_MA_METHOD) and applied_price (ENUM_APPLIED_PRICE) are real arguments — the SMA-on-Close form is only the most common configuration, not the indicator’s definition.
신호
MA이 제공하는 백테스트 가능한 뚜렷한 신호 — 및 각 신호에 적합한 시장 상황.
Price vs MA
Builder로 구현 가능Pullback to the MA
Builder로 구현 가능Slope and Fan
고급 로직MT5 구현
MetaTrader 5가 실제로 계산하고 그리는 내용 — 이 페이지의 모든 규칙이 기준으로 삼는 사양입니다.
버퍼
| 인덱스 | 버퍼 | MT5 표시 방식 | 저장 값 |
|---|---|---|---|
| 0 | MAIN_LINE | Line | The averaged price itself, plotted on the price scale. iMA publishes one buffer — a fast/slow pair is two separate handles, not two buffers of one. |
가장 잘 작동하는 경우 / 주의해서 사용
어떤 지표도 보편적인 우위를 가지지 않습니다. MA이 도움이 되는 곳 — 그리고 오해를 일으키는 곳.
가장 잘 작동하는 경우
- Trending markets
- As a filter for another signal
- On higher timeframes
- When the slope is clearly non-flat
주의해서 사용
- Sideways, directionless ranges
- Crossovers as a standalone entry
- Very short periods on low timeframes
- Optimised period pairs without validation
MA 전략 구축
신호를 진입 및 청산 규칙에 연결하고, 컴파일 가능한 MT5 EA를 내보내세요 — 코드 없이.
- Fast MA (SMA 10)
- Slow MA (SMA 50)
- Fast crosses above slow → Open Buy · SL 50 / TP 100
- Fast crosses below slow → Open Sell
MA을 다른 지표와 결합
하나의 지표만으로는 충분하지 않습니다. 이 조합들이 MA의 취약점을 보완합니다.
MA + TRIX
- Price above the EMA(200)
- TRIX crosses above zero
- Buy
MA + RSI
- EMA 5 / 20 / 60 aligned up
- RSI > 50
- Buy
MA + Momentum
- Price above the EMA
- Momentum crosses above 100
- Buy
MA + ADX
- ADX > 25
- Fast MA crosses slow
- Buy
No single-flow template pairs a moving average with ADX. Start from MA Crossover and add an ADX node with a Compare at 25 into an And gate — the ADX Trend template shows that filter wired up.
Builder 열기 →MA + ATR
- Fast MA crosses slow
- ATR sets stop distance
- Buy
No single-flow template pairs a moving average with ATR. Start from MA Crossover and add an ATR node feeding a risk-based lot or stop node.
Builder 열기 →매개변수
자신의 통화쌍과 시간 프레임에서 검증할 초기값 — 보장된 설정이 아닙니다.
| 매개변수 | 기본값 | 권장 테스트 범위 | 기능 |
|---|---|---|---|
| Period | 10 | 5–200 | How many bars are averaged. Short reacts fast and whipsaws; long is smooth and late. The template pairs 10 with 50. |
| Method | SMA | SMA / EMA / SMMA / LWMA | How the bars are weighted. SMA treats every bar equally; EMA and LWMA lean on recent bars; SMMA is the smoothest. All four are ENUM_MA_METHOD values iMA accepts. |
| Applied price | Close | Close / Open / High / Low / Median / Typical / Weighted | Price series that gets averaged. Close is the default; Median and Typical fold the bar's range in, which makes the line slightly steadier on noisy instruments. |
| Shift | 0 | 0–5 | Displaces the plotted line forward in time. Cosmetic for reading a chart, but it changes which bar a rule compares against, so leave it at 0 unless you mean it. |
초기 프리셋
Fast pair 5 / 20 More crossovers, more noise
Standard pair 10 / 50 The Builder template's baseline
Slow pair 50 / 200 Few signals, regime-level only
시장 예시
MA이 작동하는 곳, 실패하는 곳, 그리고 필터가 결과를 어떻게 바꾸는지.
Crossover into a trend
The fast average crosses up through the slow one just as a range resolves, and the two lines stay apart for the whole move — the case the crossover rule is designed for.
Whipsaw in a flat market
In a range the two averages sit on top of each other and cross repeatedly. Each cross is a trade with no move behind it.
Filtered by trend strength
Add a strength or momentum filter and the same cluster of crossings is ignored while price goes nowhere — the filter is what separates a signal from range noise.
FAQ
- SMA or EMA — which should an EA use?
- Neither is better in general. The EMA reacts sooner because recent bars carry more weight, so it turns earlier and also whipsaws earlier; the SMA is steadier and later. iMA accepts both as ENUM_MA_METHOD values, so make it an input and let the backtest decide per pair and timeframe rather than choosing on principle.
- What period should I use?
- There is no universal number. 10/50 is the Builder template's baseline and a reasonable starting point; 50/200 describes regime rather than entries. Treat any pair as a value to re-validate on your own data — a period that only wins on one window is a fitted number, not a setting.
- Can a moving average be calculated on something other than the close?
- Yes. iMA takes an ENUM_APPLIED_PRICE argument, so the average can run on Open, High, Low, Median, Typical or Weighted price as well as Close. Median and Typical include the bar's range, which slightly steadies the line on instruments with long wicks.
- Why do crossovers perform so badly on their own?
- Because a crossover is a statement about the past — the shorter average has already moved. In a trend that lag is acceptable; in a range it guarantees you buy the top of every swing and sell the bottom. The crossover is a trigger, and it needs a filter that says whether a trend exists.
- Can I build a moving-average EA without coding?
- Yes. The MA Crossover template wires two MA nodes into a Cross node with period, method and applied price exposed as EA inputs, so you can compile, backtest and optimise it per pair without writing MQL5. Reading a multi-MA fan as one state is the exception — that needs an ordering node such as the Perfect Order template's.
- How should I validate settings before going live?
- Backtest on quality tick data first, then run the EA on a demo account before risking money. When optimising, hold back data the search never saw and prefer settings that stay profitable across periods over the single in-sample peak — chasing that peak is overfitting the noise. No default or preset here is a performance promise; every value is a starting point to re-validate on your own pair and broker.