Multi-timeframe indicator EA design in MQL5
Design an EA that reads higher-timeframe filters and lower-timeframe triggers without mixing bars incorrectly.
Lesson outcomes
- Separate higher-timeframe indicator filters from execution-timeframe triggers.
- Align indicator values by bar time instead of guessing.
- Log multi-timeframe state so Strategy Tester results can be audited.
Workshop lab
Complete the demo, notebook, platform, or code task before treating the lesson as finished.
Evidence pack
Keep screenshots, exports, logs, calculations, or code versions in a dated learning folder.
Pass standard
You should be able to explain the failure modes, show your work, and name the stop rule.
Free education, not signals. This lesson is part of EarnSouthAfrica's free forex course. It does not tell you what to buy or sell, it does not promise income, and it should be practised on a demo account before any real-money decision.
Multi-timeframe EAs sound easy: check H4 trend, trade M15 trigger. The complexity is timing. The H4 bar may still be forming while M15 bars are closing. If the EA uses unstable higher-timeframe values, the backtest can look better than live logic.
This lesson teaches conservative multi-timeframe design with closed-bar state and explicit logs.
What you should be able to do after this lesson
- Separate higher-timeframe indicator filters from execution-timeframe triggers.
- Align indicator values by bar time instead of guessing.
- Log multi-timeframe state so Strategy Tester results can be audited.
Design pattern
| Layer | EA responsibility |
|---|---|
| Higher timeframe | Read closed-bar trend, volatility, or regime filter. |
| Execution timeframe | Read trigger condition only if filter is valid. |
| Risk module | Calculate lot size from local stop distance and account risk. |
| Logger | Print filter state, trigger state, bar times, and rejection reason. |
Bar alignment problem
Do not assume indicator buffer index across timeframes refers to the same clock moment. Record the time of the bar whose value is being used. If the higher timeframe has not closed, decide whether to use the previous closed bar or stand aside.
Test case
Build a demo-only EA state logger with no trading. It should print H4 filter state and M15 trigger state for 100 bars. Compare logs to screenshots. Only after the state machine is correct should order logic be discussed.
Academy-grade study plan
Indicator automation should not scrape chart visuals. The professional approach is to understand indicator handles, buffers, bar indexing, new-bar timing, and the difference between closed-bar evidence and still-forming candle noise.
| Course element | What you must produce |
|---|---|
| Primary artifact | Indicator-to-EA bridge specification |
| Lesson focus | Multi-timeframe indicator EA design in MQL5 |
| Working environment | Demo account, notebook, exported platform data, or local code sandbox. Never live funds for first practice. |
| Completion standard | You can explain the concept, reproduce the exercise, identify failure modes, and show evidence without relying on a seller's claims. |
Instructor workflow
Use this workflow as if an instructor were marking the lesson. The important question is not whether the topic sounds familiar. The question is whether your notes, screenshots, calculations, logs, or code prove that you can apply multi-timeframe indicator ea design in mql5 under controlled conditions.
- Choose the indicator for a specific measurement job, such as trend, momentum, volatility, bands, or volume.
- Create indicator handles deliberately and copy only the buffers and bars required for the decision.
- Avoid using current-bar values as final evidence unless the strategy is explicitly designed for intrabar behaviour.
- Log buffer values, signal state, and rejection reasons so the EA can be debugged without staring at the chart.
Worked case study: Indicator signal repaints in the learner's head
A learner watches RSI cross a level during a live candle and assumes the signal is confirmed. By candle close, the value changes and the signal disappears. The paid-course response is to decide whether the strategy uses closed bars or intrabar data, then code CopyBuffer calls and logs to match that decision.
After reading the scenario, write the decision you would make before checking the suggested workflow above. Then compare your decision with the operating model. The gap between those two answers is the part of the lesson that deserves another demo repetition.
Professional template
Complete this template in your own notebook. A paid course would normally hide this kind of operating document behind worksheets; here it is part of the free lesson.
| Field | Standard |
|---|---|
| Indicator handle | MQL5 function, symbol, timeframe, parameters, and release/initialization plan. |
| Buffer read | Buffer number, shift, number of bars, closed-bar rule, and error handling. |
| Signal logic | Condition, filter, confirmation, rejection reason, and log output. |
| Test evidence | Visual chart screenshot, printed buffer values, Strategy Tester run, and forward-demo check. |
Failure-mode lab
Paid courses often sell confidence. A serious course teaches you how the idea breaks. Before continuing, test the failure modes below on demo, paper, or code review. If you cannot describe the failure, you are not ready to trust the concept.
- Reading buffer shift 0 as if it were a closed candle.
- Not checking whether CopyBuffer returned enough values.
- Mixing indicator timeframes without aligning bars and timestamps.
- Using visual indicator crossings that the EA cannot reproduce from data.
Evidence pack and pass standard
Do not mark this lesson complete because you read it. Mark it complete only when you can show the evidence below. Keep the files in a dated folder so your learning history survives platform updates, memory gaps, and sales pressure.
- A one-page note explaining multi-timeframe indicator ea design in mql5 without sales language or copied definitions.
- A screenshot, export, calculation, log, or code file that proves the practical work was completed on demo.
- A written stop rule that says when this topic must not be used with real money.
- A small MQL5 snippet that logs indicator buffer values for at least three closed bars.
- A screenshot matching the chart indicator with the logged values used by the EA.
Assessment rubric
| Level | What it looks like |
|---|---|
| Not ready | You can repeat the vocabulary but cannot complete the demo task, calculate the risk, explain the failure mode, or show evidence. |
| Course pass | You can complete the practical task on demo, explain the decision rules, show evidence, and name the conditions where the idea must not be used. |
| Strong pass | You can teach the concept to someone else, find edge cases, document a rejected example, and improve the template without weakening risk controls. |
Advanced homework
- Compare MA, RSI, ATR, and Bollinger buffer reads and document which buffer each signal uses.
- Build a closed-bar-only signal and prove it does not change after the bar closes.
- Add logs that explain why an indicator signal was rejected.
Practical drill
Do this lesson as a controlled exercise, not as a reason to trade live. Open a demo account or notebook, write the lesson title, and record what you changed, clicked, calculated, or checked. If the lesson includes code, compile it only in a demo environment and keep the original version unchanged so you can compare edits safely.
- Write a one-paragraph explanation of multi-timeframe indicator ea design in mql5 in your own words.
- Take one screenshot or note that proves you completed the platform, maths, research, or code task.
- Record one risk rule that would stop you from using this idea with real money.
- If anything feels unclear, repeat the lesson before moving to the next module.
How scammers misuse this topic
Scammers often take real concepts and wrap them in urgency. They may use platform jargon, bot screenshots, copied profit charts, or official-sounding language to make a paid offer feel safe. A real concept is not the same as a safe offer. Before paying anyone, ask whether you can verify the provider, reproduce the calculation, test the claim on demo, understand the risk, and walk away without pressure.
Checkpoint before continuing
- Your EA separates filter, trigger, risk, and logging.
- You know which higher-timeframe bar is being used.
- You can audit multi-timeframe state from logs.
Official references
These lessons are written as free education. When platform features or rules matter, verify against the official source before using real money.
Risk note: leveraged forex and contracts for difference can lose money quickly. EarnSouthAfrica is an educational publisher, not a broker, adviser, signal provider, or money manager.
Keep exploring
Read the latest guides, take the side-hustle quiz, or contact the editorial desk if you spot a correction.