Bridge owns the message path
Source login, provider/topic identity, format rewrites, entry filters, freshness, duplicate detection, routing and optional provider total lot.
Navigator product guide
A beginner-first guide for Navigator Bridge 8.00 and the prepared Trade Copier Ultimate 8.00 paid/demo builds. It separates source access, Bridge policy and MT5 execution so every “why didn’t it trade?” question has a concrete place to look.
Bridge public v8.00TCU v8.00 Market publication unconfirmedUpdated 2026-08-28
Use a demo account first. Keep TCU disarmed until the source, provider/topic, MT5 account, symbol and lot owner are visible. Software cannot guarantee a fill or trading result.
TCU owns broker execution
Final account readiness, symbol resolution, lot normalization, pending/market placement, SL/TP and exact-ticket management.
Use the smallest setup that meets your source access.
TCU without Bridge
- Direct Telegram Bot API when the bot can access the chat
- Supported manual/API input
- Built-in local MT5-to-MT5 copier
- TCU handles local lots, filters, symbols and execution
TCU with Navigator Bridge
- Telegram MTProto for private groups/channels/chats
- Forum-topic selection and topic-specific rules
- Local image OCR, format profiles and provider filters
- One Bridge routing to multiple MT5 accounts
Paid TCU
Prepared v8.00 supports the current feature set and live/demo use subject to licensing. This guide does not claim v8.00 is already published on MQL5 Market; check the official listing.
TCU demo
The demo contains paid functions but has a demo-account firewall. Live/contest rejection is intentional; use a supported demo account or the paid edition.
Duplicate-source warning: MTProto and Bot API are separate listeners. If both watch the same provider, Bridge can receive two deliveries. Intentional SigTP legs can also look like duplicates—compare signal references first.
One clean route to one demo account.
Mark each step as you complete it. Progress stays on this device.
Install or update Bridge
New/clean install: full v8.00 OCR installer. Existing install: optional in-app update or portable 8.00 updater. Upgrades preserve settings/session/history; clean profiles start with external ingestion and auto-start OFF.
Install and attach TCU
Install the paid or demo EX5 through its intended distribution path. Open one MT5 chart and attach TCU. A fresh attachment should remain DISARMED.
Allow local WebRequest
MT5 → Tools → Options → Expert Advisors → Allow WebRequest. Add exactly http://127.0.0.1:5555.
http://127.0.0.1:5555Set the EA source
TCU Source: Bridge Mode ON, Bridge Port 5555. Keep direct Telegram Bot API OFF unless intentional. The legacy Bot/API command toggle in System can stay OFF; Bridge Reply Commands are independent.
Enable MT5 Algo Trading
Enable global Algo Trading and allow algorithmic trading for the EA. TCU Home must show AutoTrading ON. Keep TCU DISARMED.
Start Bridge and prove heartbeat
Dashboard: start Bridge. HTTP / EA should be Online. MT5 Accounts must show the exact demo broker/account with a recent heartbeat.
Connect one provider
For MTProto, complete QR/code login, refresh Groups, choose one provider/topic, then route only that source to the demo account.
Set one lot owner
Use EA FIXED 0.01 total signal, or BRIDGE PROVIDER with a 0.01 provider rule. Do not combine EA-calculated and Bridge provider lots.
Arm and test once
Choose an open market on demo. Arm only after the route is visible. Send one unique signal and match History → Activity Feed → Experts → MT5 order.
MTProto is not Bot API, and neither is outbound alerts.
QR login
Enter your Telegram API ID and API Hash, request a QR, then scan with the Telegram app for the intended account. That scanning account becomes the Bridge account; phone is not used by QR.
Code login
Enter API ID, API Hash and phone. Telegram delivers a login code; complete 2FA locally when required.
Bot API
A separate optional source for chats where your bot has access. It does not use the MTProto user session.
Outbound alerts
A separate optional destination for serious status notifications. Alerts do not ingest signals and stay OFF by default.
Never send to support
- API Hash, bot token, login code or 2FA password
- QR image, phone-number screenshot or session file
- Unredacted private/customer messages
Reset removes local authorization. Also revoke the device in Telegram Settings → Devices when retiring a PC.
Provider policy follows exact source identity.
Select the source
Refresh after login. Filter Groups, Channels, Bots or Private chats. Select only intended sources. Forum topics can be selected independently.
Total lot
In BRIDGE PROVIDER mode, an unconfigured provider defaults to 0.01 total lot. A topic inherits its provider lot until an override is saved. TCU allocates broker-step TP legs.
Allowed actions
Provider/topic policy may allow or disable entry, update and management action families. Existing providers keep normal actions unless you disable them.
Maximum entry age
Reject late entries with a short freshness window. Safety management of an already tracked trade remains separate.
Split-message protection
Provider opt-in. A strict SL/TP follow-up links only one recent same-provider, same-topic entry missing protection. Window is 1–10 minutes; ambiguity fails closed.
Reply aliases
Exact phrases may map to CLOSE, BREAKEVEN, MODIFY, TP_TO_ENTRY or CANCEL. Aliases never remove reply/ref/ticket proof.
Bridge normalizes; TCU resolves the broker.
Live order
Provider/topic → format rewrite → filters/classifier → parse → inverse → route → queue. The Format tester follows this path without enqueuing a trade.
Symbols
Bridge aliases provider wording and applies entry whitelist/blacklist. TCU resolves the exact broker symbol/suffix. Qualified stock symbols stay intact; exchange ambiguity fails closed.
Skip phrases
Bridge Skip Keywords are literal phrases with token boundaries. EA Keyword Replace/custom SL/TP/skip inputs apply to direct Bot/API/manual parsing, not normal Bridge Telegram messages.
Duplicate and cooldown
Duplicate blocks exact replay in its window. EA cooldown blocks same-symbol/same-direction entry for a configured time; an allowed SL/TP follow-up can still modify.
Keep formats narrow. Add a source-specific profile and test exact original text. Do not loosen generic parsing for one provider.
BUY XAUUSD
ENTRY: 2500.00
SL: 2490.00
TP1: 2510.00
TP2: 2520.00
TP3: OPENA management phrase is not enough. Context must prove the trade.
Built-in categories
Close/Exit, Partial Close, Breakeven, Modify SL/TP, Move TP to Entry and Cancel Pending. Strict CLOSE TP1–TP5 can close a registered target leg.
Exact scope
Reply CLOSE targets a registered ticket. Cancel Pending targets registered pending tickets for that signal. Numeric updates preserve explicit target-leg scope.
Move TP to Entry
Moves TP to each selected trade’s actual MT5 open price. It is a recovery/exit action, never re-entry.
Result chatter
TP1 HIT, TP2 REACHED and SL HIT alone are non-action, even with an old quoted signal. A proven “TP1 HIT MOVE SL TO BE” performs only breakeven.
Standalone commands fail closed. “close”, “move SL”, “cancel” or an alias without proof must not guess the latest trade. Keep Global CLOSE ALL OFF and bare SL/TP replies OFF for a safe first setup.
MOVE SL TO BE
CLOSE 50%
MOVE TP2 TO 2510
CANCEL PENDING
CLOSE TP1One source can route to many accounts without sharing state.
Multi-account routing
Each MT5 client has its own heartbeat, route, queue watermark, ticket registry and callback. One client rejection does not consume another client’s command.
Lot owner
EA FIXED/RISK/BALANCE/per-symbol calculates locally. BRIDGE PROVIDER accepts one provider/topic total and allocates TP legs. The selected mode decides ownership.
Multi-TP and pending
SigTP supports TP1–TP5 split or virtual modes, fair broker-step allocation, runners and pending multi-TP. Pending/zone/stop-limit still require correct side, distance, expiry and market session.
Prop and drawdown
Bridge Prop Safe transforms upstream; EA Prop is the final account guard. Pauses block new exposure while verified risk-reducing management can continue.
Weekend Protection
When enabled, Bridge persists one exact-account CLOSE ALL per weekend cycle from Friday 22:00 UTC minus the buffer, blocks stale/new entries until Sunday 22:00 UTC and avoids replay on restart.
Visible reasons
DISARMED, invalid stops, missing symbol and broker rejection can appear as red ticketless Activity rows. Intentional duplicate/cooldown SKIPPED rows are amber.
Every current navigation page.
Select a page for ownership, interactions and a safe starting point.
All 15 tabs and settings families.
Filter has six internal pages. Martin is an advanced recovery surface and should remain disabled for beginners.
Signals and protected management.
Market signal with three targets
SELL EURUSD
ENTRY: MARKET
SL: 1.1700
TP1: 1.1650
TP2: 1.1600
TP3: 1.1550Pending and zone examples
BUY LIMIT XAUUSD 2480.00
SL: 2465.00
TP1: 2500.00
TP2: 2520.00BUY XAUUSD
ENTRY ZONE: 2480 - 2485
SL: 2465
TP1: 2500
TP2: 2520Split SL/TP follow-up
Only after enabling that provider’s split-message rule.
ENTRY: OPEN
SL: 2465
TP1: 2500
TP2: 2520Pick the first visible symptom.
Forum topic issue: confirm the provider and exact topic are selected, then check whether a topic override disabled the action or changed lot/age rules.
Shared language for support.
MTProto
Telegram user-account protocol used for chats visible to the logged-in account.
Bot API
Separate bot source that sees chats where the bot has access.
Provider / topic
Source chat and optional forum subdivision whose rules Bridge applies.
Heartbeat
Recent EA contact proving the exact MT5 client is online.
Bridge Provider lot
One total lot supplied by provider/topic policy and split by TCU.
Signal reference
Durable Bridge identity used with registered tickets for exact management.
Duplicate window
Period during which the same signal replay is rejected.
Cooldown
EA rule blocking another same-symbol/same-direction entry for a period.
SigTP
TCU split or virtual multi-target engine up to TP5.
Fail closed
Reject ambiguity instead of guessing a symbol, side, price or ticket.
Answers before settings are changed.
Why does QR need API ID and API Hash?
Telegram requires an application identity. API credentials identify the app; the account scanning the QR identifies the user session.
Can TCU work without Bridge?
Yes: supported direct Bot/API/manual sources and the built-in MT5-to-MT5 copier. Add Bridge for MTProto/private Telegram, OCR, provider/topic policy and multi-account routing.
Why did one signal create several positions?
Check SigTP split legs first, then check duplicate source paths and routes.
Who controls lots?
EA FIXED/RISK/BALANCE/per-symbol is local. BRIDGE PROVIDER uses the provider/topic total. Modes are not added together.
Why did TP1 HIT do nothing?
It is result chatter. A proven reply with explicit management may act; chatter alone is non-action.
Why did the signal parse but not trade?
Parsing is only one gate. Routing, arm state, Algo Trading, symbol, lot, session, stops, margin, cooldown, prop/drawdown/news and broker checks happen later.
Send the complete path, without secrets.
Original input
- Exact raw text or redacted signal image
- Time + timezone, provider + forum topic
- Source mode: MTProto, Bot, Discord, HTTP, file or OCR
Bridge evidence
- Dashboard service/account status
- Signal History and Activity Feed row
- Relevant Logs lines around the exact time
MT5 / TCU evidence
- TCU Home and relevant settings tab
- Experts lines with reference
- Exact Market Watch symbol, ticket and retcode
Redact first
- Phone, API/hash, bot tokens, sessions, codes, QR and 2FA
- Unrelated chats, customers, account numbers and balances
Product/build: Bridge 8.00 / TCU edition + build
Time + timezone:
Source mode:
Provider + topic:
MT5 broker + exact symbol:
Bridge History result:
Activity Feed reason:
TCU Experts reason / broker retcode:
Expected outcome:
What changed immediately before:No section matched. Try “suffix”, “reply”, “WebRequest” or “cooldown”.