Connect and understand
Install TRDR.PRO, connect MT5, read the dashboard and understand BUY, SELL, WAIT and BLOCKED.
- MT5 connection
- Dashboard cards
- Paper vs live
- Basic alerts
Learn how the market intelligence engine thinks, how every setting changes behaviour, why trades are accepted or blocked, and how MT5, risk, trade groups, Telegram, journal and analytics work together.

Each path is a guided route through the same platform. Start at the level that feels right, then move forward when the workflow becomes familiar.
Install TRDR.PRO, connect MT5, read the dashboard and understand BUY, SELL, WAIT and BLOCKED.
Set risk, sessions, entry modes, automation and three-leg trade management with confidence.
Read structure, liquidity, market state and evidence, then tune smarter execution behaviour.
Use journal, analytics, replay, diagnostics and synchronization to operate TRDR.PRO reliably.
TRDR.PRO is an institutional-style market intelligence and execution platform. It continuously converts live MT5 market data into context, probability, risk validation, execution decisions and managed trade outcomes.
Combines time, sessions, higher-timeframe bias, structure, liquidity, volatility and price location rather than reacting to a single indicator.
Dashboard, Trading Operations, risk preview, Telegram and MT5 execution are designed to use the same authoritative BUY, SELL, WAIT or BLOCKED decision.
Executes grouped TP1/TP2/TP3 positions, applies protection rules, records history and reports lifecycle events through the private Telegram channel.
Install and log into MetaTrader 5. Enable Algo Trading and confirm the broker’s gold symbol is visible. TRDR.PRO can auto-detect common XAUUSD symbol variants.
TRDR.PRO Setup.exeRun the official installer, then launch TRDR.PRO from the desktop shortcut or Windows Start Menu. Verify the header displays MT5 CONNECTED and the correct symbol, mode and live quote stream.
Set automation mode, confidence threshold, allowed sessions, maximum positions/groups, daily loss, drawdown and lot sizing before enabling live execution.
Save the bot token and public/private Telegram channel IDs, then use Send Test Alert to verify delivery to both destinations.
Run analysis and compare the Dashboard decision with Trading Operations. Confirm risk status, execution route and blockers before the first live order.
Auto Trading must be enabled and Execution Mode must be Fully Automatic before an approved decision can reach the MT5 order pipeline.
The dashboard is the fastest way to answer: What is happening, what does TRDR.PRO believe, and is the account ready to trade?


Directional evidence supports long execution and risk validation passes.
Directional evidence supports short execution and risk validation passes.
The market idea may be valid, but timing, confirmation or price location is not ready.
A decision exists, but execution is prevented by automation, risk, capacity, news, broker or validation rules.
Reasons supporting the decision: higher-timeframe bias, market structure, liquidity sweep, session alignment, location and momentum.
Reasons for caution and the condition that would make the scenario invalid, such as a candle close beyond a structural level.
Waits for stronger alignment and clearer confirmation. Produces fewer opportunities and may enter later.
Balances confirmation with opportunity. It can use a qualified early entry when evidence is strong but not perfect.
Adjusts aggressiveness based on trend strength, volatility, liquidity, session behavior and current opportunity cost.
H1 bearish · M15 BOS down · liquidity swept · price slightly extended · confidence 68%
The setup is strong enough to execute, but sizing and timing remain controlled.
This page combines the final decision, account risk, live exposure and MT5 execution status.
Open Trade Groups shows grouped strategies; MT5 Positions shows raw broker legs; Pending Orders, Closed Trades and Execution Log show the remaining lifecycle views.


The master switch. When off, analysis can continue but no automatic live order should be submitted.
Manual: no automatic execution. Semi-Automatic: requires user confirmation. Fully Automatic: approved final decisions can enter the MT5 pipeline without a manual click.
The minimum final-decision confidence required for the configured route. Entry-profile logic can apply additional conditions; reaching this number does not override blockers.
Limits concurrent broker exposure. In a three-leg setup, one TRDR trade group normally creates three MT5 positions. Confirm whether the displayed build treats the field as raw positions or grouped trades.
The maximum permitted estimated loss for a new trade, measured against Equity or Balance according to the selected calculation basis.
Caps the combined estimated stop-loss risk of all open exposure.
Equity responds to floating P/L; Balance uses closed-account value. Equity is generally more conservative during drawdown.
Stops new execution when the day’s loss reaches the configured percentage.
Blocks new trades if account drawdown exceeds the permitted limit.
Prevents execution around loaded high-impact events when the news filter is enabled.
Choose Sydney, Tokyo, London and/or New York. A setup outside every enabled session is blocked.
Manual: fixed preferred lot. Automatic risk-based: computes volume from stop distance and allowed risk. Hybrid: uses the preferred lot but caps it at the risk-safe size.
The preferred total or execution volume, depending on the installed build. For the standard 0.03 group, TRDR.PRO uses 0.01 × 3. Validate the preview before live use.
A hard ceiling that automatic and hybrid sizing may not exceed.
Allows the executor to retry eligible broker rejections using supported filling modes. It should not retry permanent validation failures indefinitely.
Daily loss, drawdown, open risk, margin and maximum capacity.
Entry, broker-valid volume, stop distance, TP plan, estimated loss and percentage risk.
Session permission, news filter, spread, stale signals and invalidation.
MT5 connection, Algo Trading, symbol visibility, filling mode and order confirmation.

A standard trade group contains three 0.01 positions. Each leg should have one broker-side target: TP1, TP2 or TP3—not three targets on one 0.01 position.
Market watch, waiting for retest, extra confirmation and non-executed setup messages.
The platform validates automation, capacity, risk and broker execution.
Trade opened, TP/SL/manual closure and execution errors after broker confirmation.
Displays local application notifications.
The BotFather-issued token. Treat it as a secret.
Destination for setup and watch alerts. Numeric channel IDs normally begin with -100.
Destination for confirmed live entries and trade lifecycle results.
Tests both destinations and should display the real Telegram API result.
Optional SMTP notification route configured by host, port, username, password, recipient and TLS setting.
The Journal records trade-group identity, leg, MT5 ticket, symbol, side, volume, entry, exit, P/L, status, source and timestamps.

Reliable analytics depend on successful MT5 history reconciliation and correct grouping. A three-leg trade should generally be evaluated as one strategy group while still retaining leg-level detail.

Enter comma-separated symbols and timeframes, then run Scan Markets Now. Results include Symbol, Timeframe, Decision, Confidence, Scenario and any Error.
Symbols: XAUUSD, EURUSD
Timeframes: M15, H1TRDR.PRO is XAUUSD-first. Additional symbols must be validated for broker naming, point value, stop rules and strategy suitability before live automation.
The replay and strategy-lab tools support historical validation, current MT5 candle snapshots, scenario review and performance export. Use them to compare profiles, thresholds, sessions and management policies without risking a live account.
Step through historical market sequences and inspect decisions.
Measure decision quality, execution frequency and strategy behaviour.
Save results for external review and comparison.
DEBUG, INFO, WARNING, ERROR or CRITICAL. INFO is suitable for normal operation; DEBUG is useful during troubleshooting.
Displays runtime events in the terminal used to start TRDR.PRO.
Persists logs for later review.
Reloads current service and connection health.
New, Open, Save and Export Runtime Snapshot manage application workspace and layout functions according to the installed build.
Clears journal, analytics, trade groups and runtime caches while preserving automation, risk, Telegram, license and UI settings. For safety, close active MT5 positions before resetting.
Choose the current state and the Academy will identify the most likely blocker.
An executable BUY or SELL may proceed to MT5 confirmation.
The public message is pre-execution. Check Trading Operations for blockers: FULL mode, Auto Trading enabled, capacity, confidence, session, daily loss, drawdown, news, margin, spread, stops and broker rejection.
The private trade-opened alert is sent only after MT5 confirms a live position. No broker-confirmed position means no confirmed VIP entry alert.
Compare the configured limit with both trade-group count and raw MT5 position count. One three-leg trade usually consumes three MT5 positions.
The order comment must be a short broker-safe string. Full strategy metadata belongs in the journal, not the MT5 comment.
Verify MT5 Account History contains closed deals for the selected day, then inspect history reconciliation and timezone handling. Today’s P/L should sum trading-deal profit, commission, swap and fees while excluding deposits and credits.
All live pages should read the same MT5-backed state. A mismatch usually indicates one page is displaying stale database or cached data.
Confidence and timing are different. Price may be extended, confirmation incomplete, counter-evidence present or the selected entry profile may require a retest.
Check the Execution Log and MT5 Journal for invalid volume, invalid stops, filling mode, margin, market closure or broker-specific restrictions. A robust build should roll back incomplete groups.
This manual describes platform behaviour and controls. Trading involves substantial risk, and no decision engine can guarantee a profitable outcome. Validate settings on a demo account before live deployment.