Trade Copier Ultimate — Full documentation and user manual

4 May 2026, 03:20
Janitha Sandaruwan Amaradasa Wickramasingha Arachchilage
4
247

Trade Copier Ultimate v7.40 - Full Documentation and Advanced User Manual

Navigator Trading Systems | Version 7.40 | July 2026

FULL SETUP GUIDE IS HERE --->>>  

SIGNAL FORMAT TESTER --->>>



Trade Copier Ultimate
is a multi-source signal executor and trade copier for MetaTrader 5. It supports Telegram Bot API, NTS Bridge routing for Telegram and Discord, local MT5-to-MT5 copying, Telegram and Discord notifications, multi-TP execution, pending orders, trade management, and prop-firm risk controls.

This EA does not generate signals, provide investment advice, or guarantee profit. It executes or copies the sources and settings selected by the user.

New User
Start with one source, one demo account, Fixed Lot 0.01, and the EA DISARMED.
Bridge User
Run the latest NTS Bridge and MT5 on the same PC or VPS. The default local port is 5555.
Local Copier User
Use TCU_TradeCopier.csv and only one selected main Master per copier file.

Recommended first test: complete one open, modify, partial-close, and close cycle on demo before using a live or funded account.


Start Here - Three Safe Setup Paths

Setup What to configure Required WebRequest URL
NTS Bridge Start NTS Bridge, connect Telegram or Discord, assign sources to the correct MT5 account, enable Bridge Mode in the EA, and match port 5555. http://127.0.0.1:5555
Telegram Bot API Create or select a Telegram bot, add it to the source chat, enter its token and Chat ID, and enable Telegram Bot API in the EA. https://api.telegram.org
MT5-to-MT5 Copier Set one terminal to MASTER, one or more receiving terminals to SLAVE, and use the same TCU_TradeCopier.csv file name. None for normal same-PC local copying.

In MT5, WebRequest URLs are added under Tools > Options > Expert Advisors > Allow WebRequest for listed URL.

First-run safety rule: use only one signal source at first. Keep the EA DISARMED while testing the connection, then ARM it only after the correct account, source, symbol, lot size, and filters are visible.

1. What Is New in v7.40

Area Current behavior
Dedicated TCU copier file TCU now defaults to TCU_TradeCopier.csv. It is intentionally separated from the free NTS Local Copier and its TradeCopier.csv workflow.
Main-Master ownership Only one TCU Master can own a copier file. Other Masters are blocked until the user deliberately clicks USE AS MAIN.
Safer Master switching There is no automatic replacement Master. Existing positions on a newly selected Master are baselined so they are not surprise-copied after a takeover.
Restart and duplicate protection Copier role and ticket mappings are stored per account and Magic Number. Previously copied trades are linked after restart instead of being opened again.
Comment-independent tracking Local copier tracking continues when comments are set to OFF, SAFETY TAG, or CUSTOM+TAG.
Safer parser and commands Provider updates such as TP1 hit, Target reached, and Profit taken are rejected as updates instead of being treated as fresh trades.
Reply-command protection Close, partial close, breakeven, SL/TP changes, and pending cancellation use proven reply context. Broad standalone management text is blocked unless it is an explicit allowed account-wide command.
Pending-order preflight The EA checks symbol trade mode, order side, broker stop/freeze distances, and SL/TP validity before submitting a pending order.
SigTP leg controls TP1, TP2, and TP3 can be enabled independently. Percentage allocations rebalance to 100%, 50/50, or 40/30/30 according to the active legs.
Bridge recovery safety Session watermarks and stale-queue protection help prevent old signals from executing after a reconnect, restart, or drawdown halt.

2. Operating Modes

Mode Purpose Best for
NTS Bridge Routes Telegram MTProto, Telegram Bot API, Discord, OCR-assisted messages, and assigned sources to one or more MT5 accounts. Private channels, multiple providers, account routing, reply commands, and Bridge-side safety controls.
Direct Telegram Bot API The EA polls Telegram using a bot token and Chat ID without the desktop Bridge. A simple source where the bot is allowed to read the chat.
MT5-to-MT5 Copier Copies open positions from one selected local Master account to one or more local Slave accounts. Same-PC or same-VPS broker-to-broker mirroring.
Telegram Broadcast Sends configured MT5 trade activity to a Telegram destination. Private alerts, journaling, provider workflows, and team notifications.
Discord Send Sends configured notifications through a Discord webhook. Trade alerts and monitoring. Discord signal ingestion is configured in NTS Bridge.

Important: enabling more than one ingestion source can intentionally deliver more than one trade. During setup, use one source at a time so duplicate routing is easy to identify.


3. NTS Bridge Quick Setup

  1. Install the latest NTS Bridge build supplied for Trade Copier Ultimate.
  2. Run NTS Bridge and connect the required Telegram or Discord source.
  3. Open the Bridge Groups or source-assignment page and assign only the required groups/channels to the correct MT5 account.
  4. In MT5, add http://127.0.0.1:5555 to the allowed WebRequest list.
  5. Attach Trade Copier Ultimate to one chart on that account.
  6. Open Source, enable Bridge Mode, and confirm Bridge Port = 5555.
  7. Keep the EA DISARMED and use the connection test. Confirm the correct account appears online in Bridge.
  8. Set a small Fixed Lot, send one demo signal, inspect the parsed result, then ARM the EA for the execution test.
Routing rule: Bridge assignments are per MT5 client/account. A source that is not assigned to an account should not be delivered to it. Review assignments whenever you add a terminal or change account logins.

4. Direct Telegram Bot API Quick Setup

  1. Create a bot with @BotFather and copy the bot token.
  2. Add the bot to the required Telegram group/channel and grant the access required by that source.
  3. Obtain the correct Chat ID.
  4. Add https://api.telegram.org to MT5 WebRequest permissions.
  5. Enable Telegram Bot API in the EA and enter the token and Chat ID.
  6. Keep Bridge Mode off during the first Bot API test.
  7. Test on demo while DISARMED, then ARM only after confirming the correct chat is being read.

A bot cannot read a private group or channel merely because you know its Chat ID. The bot must be a member and must have suitable Telegram permissions.


5. ARM, DISARM, Restart, and Power-Loss Behavior

State or event Behavior
DISARMED Signals may be received and parsed, but no new trade is placed by the EA.
ARMED Execution is allowed after all risk, broker, symbol, and filter checks pass.
Clean MT5 close/reopen If Disarm On Restart is OFF and the EA was armed, the saved armed state can be restored after a clean restart.
Disarm On Restart = ON The EA returns DISARMED after restart and must be armed manually.
Abrupt stop or power loss Without a clean restart marker, the EA returns to the safer DISARMED state. Verify the panel before resuming.
Fresh chart attachment A fresh attachment remains DISARMED. It does not inherit an old armed state blindly.

Always look at the visible ARMED/DISARMED header after a terminal restart, VPS recovery, EA update, account change, or chart re-attachment.


6. Signal Formats

Type Example
Market buy BUY XAUUSD SL 4080 TP 4120
LONG wording XAUUSD LONG SL 4080 TP 4120 or LONG XAUUSD
Market sell SELL XAUUSD SL 4140 TP 4090
SHORT wording XAUUSD SHORT SL 4140 TP 4090 or SHORT XAUUSD
Multi-TP BUY GOLD SL 4080 TP1 4110 TP2 4130 TP3 4160
Sequential TPs BUY GOLD SL 4080
TP 4110
TP 4130
TP 4160
Buy limit GOLD BUY LIMIT 4090 SL 4070 TP 4130
Sell limit GOLD SELL LIMIT 4140 SL 4160 TP 4100
Buy stop BTCUSD BUY STOP 120000 SL 118500 TP 123000
Entry range GOLD BUY LIMIT 4088-4092 SL 4070 TP 4130
Reply close Reply to the original signal with CLOSE or an enabled close alias.
Reply partial close Reply with CLOSE HALF, CLOSE 50%, or another enabled partial-close phrase.
Reply breakeven Reply with BREAKEVEN, MOVE SL TO BE, or another enabled breakeven phrase.
Reply modification Reply with SL 4100, SET TP 4140, or a supported modification phrase.
Reply pending cancel Reply to the original pending signal with CANCEL PENDING.
Do not send ambiguous direction text. A literal message such as XAUUSD LONG / SHORT contains both directions and is intentionally ignored. Send exactly one direction: LONG/BUY or SHORT/SELL.

Relative price wording: phrases such as TP +30 pips or SL 50 points are not treated as absolute price levels. Unsupported relative levels are ignored instead of being converted blindly.


7. Parser and Reply-Command Safety

The Bridge parser separates fresh entries from provider updates and management commands.

Message Expected result
BUY GOLD SL 4080 TP 4120 Fresh entry candidate, subject to all EA and Bridge filters.
TP1 hit, Target 1 reached, Profit taken GOLD Provider status update. It is not opened as a fresh trade.
CLOSE as a reply to the original signal Targeted close command when reply commands and that phrase are enabled.
CLOSE as an unrelated standalone post Blocked when no proven original signal target exists.
CLOSE ALL or EXIT ALL May be accepted as an explicit account-wide command when enabled. Treat these phrases as high risk.
Custom close, breakeven, modify, or cancel alias Processed only under the matching Bridge command category and normal reply-safety rules.

Bridge reply-command categories can be enabled or disabled individually: Close, Partial Close, Breakeven, Modify SL/TP, and Cancel Pending.

Multi-TP note: reply commands target the trade ticket registered to the original signal. Do not assume a generic reply will manage every split TP leg; verify the exact behavior on demo for your provider format.


8. Symbol Mapping

The EA resolves common aliases, broker prefixes, and broker suffixes. Examples include:

  • GOLD to XAUUSD, XAUUSDm, XAUUSD.pro, or a broker-specific gold symbol
  • BTC to BTCUSD or BTCUSDm
  • EURUSD to EURUSDm, EURUSD.r, or a similar broker suffix
  • Common index, oil, forex, crypto, and metal aliases where a matching broker symbol is available

Keep the broker symbol visible in Market Watch. Use Custom Mappings when automatic mapping cannot identify an unusual broker name.

Broker check: symbol mapping only resolves the name. The broker still decides whether trading is open, which order types are allowed, the minimum lot, lot step, stop distance, freeze distance, and filling mode.

9. Signal Lot Sizing and Risk

Setting Behavior
FIXED Uses the configured Fixed Lot for normal Telegram, Bridge, and direct signal execution.
RISK % Calculates volume from account balance and stop-loss distance. If no valid SL exists, Default SL Points may be used for the calculation when configured.
Per-Symbol Lots Overrides the global fixed lot for selected symbols, for example XAUUSD=0.03,BTCUSD=0.01.
Max Lot Limits calculated volume. The over-max action can trim to the cap or skip the trade.
Max Open Positions Blocks new entries when the configured account/EA cap is reached.
Max Trades Per Minute Acts as a circuit breaker against bursts of accepted entries.

Correction from the old manual: the normal signal executor uses FIXED or RISK %. MULTIPLIER is a separate MT5-to-MT5 Slave lot mode, not a general Telegram signal lot mode.


10. Signal TP (SigTP) and Multi-TP Splitting

When a signal contains TP1, TP2, or TP3, SigTP can split the total trade volume into separate positions.

Configuration Behavior
TP1 + TP2 + TP3 ON Default percentage allocation rebalances to 40 / 30 / 30.
Any two TP legs ON Percentage allocation rebalances to 50 / 50.
One TP leg ON The active leg receives 100% of the planned volume.
PERCENT allocation Splits the calculated main volume across enabled targets.
FIXED LOTS allocation Uses configured TP leg lot values, subject to broker minimum, step, and total-lot rules.
Prop Firm Mode Multi-TP splitting can be disabled by the Prop setting, in which case the EA uses the allowed single-target behavior.

If the calculated total lot is too small for the broker to create every requested leg, the EA may reduce the number of valid legs or reject an invalid split. Test small-lot multi-TP behavior with the actual broker.


11. Break-Even and Signal-TP Follow-Up

  • SL -> BE on TP1: moves remaining eligible legs to entry when TP1 closes.
  • SL -> TP1 on TP2: moves remaining eligible legs to the TP1 price after TP2 closes.
  • BE Extra Pips: can add a small configured buffer beyond entry.
  • Reply Breakeven: Bridge can send a targeted breakeven command when the provider replies to the original signal.

Broker stop and freeze distances still apply. A requested SL move can be rejected if the new stop is too close to the current market price.


12. Partial Close Management

The Partial tab can close part of a position at configured pip milestones.

Setting Purpose
PERCENTAGE Closes a percentage of the current position at each enabled milestone.
FIXED LOTS Closes a fixed lot amount at each enabled milestone.
Scope AUTO Ignores Signal Multi-TP split positions so global partial logic does not manage those legs a second time.
Scope ALL Applies configured global partial logic to all eligible tracked positions.
Follow-up SL Can move SL to BE, TP1, TP2, or TP3 after successive partial milestones.

The broker must accept the requested remaining volume and lot step. If a position is already at the minimum lot, a partial close may be impossible.


13. Trailing Stop

  • Trail Start Pips: profit required before trailing begins.
  • Trail Distance Pips: distance maintained behind price.
  • Trail Step Pips: minimum improvement before the SL is moved again.
  • Move to Breakeven: optionally moves SL to entry when trailing activates.
  • Breakeven Buffer: optionally moves slightly beyond entry.

Trailing is managed by the EA and requires MT5, the EA, and Algo Trading to remain running. Broker stop/freeze limits can delay or reject a requested update.


14. Pending Orders

The signal engine supports BUY LIMIT, SELL LIMIT, BUY STOP, and SELL STOP when the broker allows that order type.

  • Pending Expiry: can remove an unfilled order after the configured number of hours.
  • Pending Multi-TP: can split a pending signal across supported TP legs.
  • Reply Cancel: a reply to the original pending signal can cancel its registered pending ticket.
  • Broker Preflight: validates market state, order side, stop/freeze distance, and SL/TP direction before submission.
  • Failure Feedback: rejected/failed Bridge execution is returned to Bridge for visible diagnostics.

Important: the built-in MT5-to-MT5 local copier mirrors open positions, not pending orders. Pending-order support belongs to the Telegram/Bridge signal engine.


15. Duplicate Filter and Cooldown

Control Behavior
Duplicate Filter Blocks the same successfully processed signal text inside the configured duplicate window. Hash memory is restart-safe.
Signal Cooldown Blocks repeated same-symbol, same-direction entries for the configured time.
Allow SL/TP During Cooldown Allows a valid management update even while new entries remain blocked by cooldown.
Minimum Same-Type Distance Can require a minimum price distance between same-direction trades.
Bridge Session Watermark Prevents old queued signals from being delivered later after reconnect, re-assignment, or a temporary halt.

Disable duplicate protection only for a controlled demo test. A forwarded signal can arrive through multiple groups or sources and create more than one trade if protections and routing are configured incorrectly.


16. Entry, Spread, Slippage, Time, Symbol, and News Filters

  • Entry Armour: can require direction + symbol + at least one of SL, TP, or entry information.
  • Skip Without SL/TP: can reject incomplete signals.
  • Auto SL / Auto TP: can add configured fallback distances when a required level is missing.
  • Wrong-Side SL/TP Action: can reject the signal, remove invalid levels and open empty, or use configured auto-pip levels.
  • Spread Filter: blocks entries above the configured maximum spread.
  • Slippage Filter: can skip the entry or use the configured pending-order action when entry slippage is too large.
  • Time Filter: limits execution to configured broker hours.
  • Whitelist / Blacklist: controls which symbols may be traded.
  • Skip Keywords: blocks provider status text and user-defined phrases.
  • News Pause: can pause affected currencies around available economic-calendar events.

News filtering depends on the calendar data available to the terminal. Always verify event times, broker server time, and the selected pause window on demo.


17. Prop Firm Mode

Prop Firm Mode applies a stricter set of execution controls. It does not guarantee compliance with any prop firm.

  • Require SL and optionally require TP
  • Hide MT5 trade comments when Prop No Comments is enabled
  • Limit open positions/orders
  • Limit accepted trades per minute
  • Apply account-wide daily loss limits
  • Use a separate prop spread limit
  • Block same-symbol, same-direction exposure
  • Disable Multi-TP unless Prop Allow MultiTP is enabled

The old "Beginner Safe Mode" wording has been removed. There is no single preset that can make an unknown provider, broker, or funded-account rule safe. New users should use DISARMED testing, Fixed Lot 0.01, one source, and conservative limits.

Funded accounts: confirm the firm's rules for EAs, signal copying, copier comments, minimum trade duration, news trading, account sharing, multi-account mirroring, and automated execution. Software settings cannot override a firm's rules.

18. Daily Loss and Drawdown Protection

The EA and Bridge provide separate safety layers.

Layer Behavior
EA Daily Loss % / Amount Blocks new EA entries when the configured daily threshold is reached.
Peak Equity Protection Can detect daily drawdown from the day's peak equity, including profit that was made and then given back.
Reset Timezone Can use broker-server midnight or UTC midnight. Match the actual rule used by the prop firm.
Bridge Drawdown Halt Can halt delivery per account. Stale queued entries are drained/watermarked so they are not released later after the halt resets.

A software drawdown limit is a last line of defense, not a guaranteed stop price. Fast markets, gaps, slippage, broker latency, disconnected terminals, and already-open exposure can exceed the configured value.


19. Bridge Advanced Features

  • Per-Account Routing: assign different Telegram groups, channels, Discord sources, or providers to different MT5 accounts.
  • Reply Commands: control close, partial close, breakeven, SL/TP modification, and pending cancellation by category.
  • Custom Aliases: add provider-specific command phrases under the correct safe action.
  • Prop-Safe Delivery: optional entry delay, comment OFF/custom/random, signal-reference stripping, and SL/TP variation.
  • Urgent Commands: targeted management commands can bypass a configured entry delay.
  • Drawdown Halt: stop routing to a selected account when its configured drawdown rule is reached.
  • Signal History: review received, parsed, routed, delivered, filtered, acknowledged, rejected, and failed events.
  • OCR: optionally reads supported image signals. OCR accuracy depends on image quality, font, layout, crop, and language.
  • Language Support: English is always available; supported Spanish terms can be enabled in Bridge.
  • Format Updates: data-only format packs can extend supported aliases and provider patterns without executing remote code.

Bridge and MT5 should normally run on the same PC or VPS. The EA communicates through local loopback, normally http://127.0.0.1:5555.


20. MT5-to-MT5 Copier - Safe Setup

Step Master terminal Slave terminal(s)
1 Attach TCU to one chart and select Copier Mode = MASTER. Attach TCU to one chart on each receiving account and select Copier Mode = SLAVE.
2 Use CSV File = TCU_TradeCopier.csv. Use the exact same file name.
3 Select NEW TRADES ONLY for the safest first test. Select NEW TRADES ONLY and a small Slave lot mode.
4 Confirm the panel does not show Blocked By. Enable Auto-close Slave if the Slave should close with the Master.
5 ARM the EA and open one small demo position. ARM the EA and confirm exactly one copy appears.
6 Modify SL/TP, partially close, then close the position. Confirm the matching position modifies, reduces, and closes once.
Critical: TCU is a single-main-master copier. It does not have the true multi-master mode found in NTS Simple Local Copier. One selected main Master can feed one or more Slaves through one copier file.

What the TCU Master publishes

The TCU Master publishes every open position on the Master account, including manual trades and positions opened by another EA. It does not limit publishing to TCU's Magic Number.

Do not set an account as MASTER unless you intend its open positions to be eligible for copying.

Startup Copy Mode

Mode Behavior
NEW TRADES ONLY Registers the stable current Master snapshot without copying it. Trades opened after the baseline are copied.
COPY EXISTING On a fresh setup/source, currently open Master positions may be copied. Saved ticket mappings are still restored after restart so previously copied positions are not duplicated.
After main-Master takeover Existing positions on the newly selected Master are baselined for safety, even if COPY EXISTING is selected. Only later trades are copied.

Slave Lot Modes

Mode Behavior
COPY MASTER Uses the Master position volume, adjusted to the Slave broker's valid lot rules and Max Lot.
FIXED LOT Uses the configured Slave fixed volume.
MULTIPLIER Multiplies the Master volume by the configured factor.
RISK % Calculates Slave volume from the configured risk and copied SL distance.
BALANCE PROPORTIONAL Scales the Master volume using the Master and Slave account balances.

21. Main-Master Ownership and Switching

TCU stores a persistent owner record for TCU_TradeCopier.csv.

  1. The first active Master claims the file as the main Master.
  2. Another Master using the same file shows Blocked By and cannot publish.
  3. The blocked Master does not take over automatically when the old Master goes offline.
  4. To change ownership, open the intended Master and click USE AS MAIN.
  5. The previous Master becomes blocked, and Slaves follow the newly selected owner.
  6. Positions already open on the new Master are baselined and are not surprise-copied.
Before switching Masters: decide what should happen to positions previously copied from the old Master. A safety takeover does not automatically remap or close those old Slave positions. Manage or close them deliberately before switching if required.

The explicit button prevents an unexpected account from becoming the main Master simply because another terminal was closed or disconnected.


22. Local Copier Restart, Auto-Close, and Comment Safety

  • Role persistence: MASTER/SLAVE role is stored per account and Magic Number.
  • Ticket-state persistence: copied Master-to-Slave ticket links are saved after important changes.
  • Restart deduplication: a previously copied open trade is linked after restart instead of being copied again.
  • Auto-close safety: when the Master file is stale or no active writer is present, auto-close pauses instead of assuming every Master trade was closed.
  • Same-account protection: a Slave refuses to copy a file owned by the same account.
  • Magic isolation: Slave close management only handles matching copier trades. Use a unique TCU Magic Number and do not share it with unrelated EAs.
Comment Mode Behavior
SAFETY TAG Uses a visible TCU#master-ticket tag.
CUSTOM+TAG Uses the custom text plus the Master-ticket safety tag when it fits the MT5 comment limit.
OFF Leaves the MT5 comment blank. Copier tracking continues through the saved state file.
Prop No Comments Overrides copier comments and keeps them blank while that Prop setting is active.

TCU and NTS Simple Local Copier are deliberately separate. Do not rename both products to the same copier file or expect cross-product compatibility.


23. Telegram Broadcast and Discord Notifications

  • Telegram Send: forwards configured trade activity to a Telegram chat/channel.
  • Separate Send Bot: can use a different bot token and destination for outgoing messages.
  • Send Tag / Suffix: adds configured text to outgoing alerts.
  • Discord Send: uses a configured webhook for outgoing notifications.

Broadcasting is separate from signal ingestion. Avoid routing your own outgoing messages back into an assigned signal source. Permanent anti-loop markers and duplicate protection help, but clean source separation is the safest design.


24. Diagnostics and Activity Reports

Use the Experts and Journal tabs together with the Bridge history when a trade does not behave as expected.

  • Last Filter Reason: shows why the most recent candidate did not execute.
  • Bridge History: shows receive, parse, route, delivery, acknowledgement, rejection, and failure stages.
  • EA Report CSV: records copier and execution activity in the MetaTrader Common Files folder.
  • Diagnostic Log: provides deeper parser/filter information when enabled.
  • Startup Summary: prints active source, ARM state, duplicate filter, pending state, Magic Number, and copier file information.

When contacting support, provide:

  • the original signal text or screenshot
  • Bridge history/log lines for that signal
  • MT5 Experts log lines from the same time
  • broker name, account type, and exact symbol name
  • EA version/build shown in the startup log
  • screenshots of the Source, Lots, Filter, Prop, and Copier settings involved

25. Recommended Demo Acceptance Test

  1. Start with zero open positions and pending orders.
  2. Confirm the correct EA version, account login, Magic Number, and ARMED/DISARMED state.
  3. Test one simple market BUY and one market SELL.
  4. Test symbol mapping on the actual broker suffix.
  5. Test SL and TP modification.
  6. Test a targeted reply close and partial close.
  7. Test one pending order and reply cancellation.
  8. Test TP1/TP2/TP3 splitting with the intended lot size.
  9. Test duplicate delivery and confirm only one trade opens.
  10. Test spread, max-open, missing-SL, and daily-loss rejection.
  11. Restart MT5 with a trade open and confirm no duplicate appears.
  12. For local copying, test one Master, two Slaves, SL/TP sync, partial close, restart, and auto-close.
  13. Test a deliberate USE AS MAIN switch and confirm old positions are not surprise-copied.
  14. Finish with all demo positions/orders closed and review the logs for unexpected activity.

Repeat this checklist whenever you change broker, account type, VPS, signal provider, routing assignment, Magic Number, lot mode, or major EA/Bridge version.


26. Troubleshooting

Problem What to check
Signal is visible but no trade opens Check EA ARMED state, MT5 Algo Trading, Bridge account assignment, source mode, Last Filter Reason, market hours, spread, cooldown, duplicate filter, max-open cap, daily loss, and margin.
Bridge account does not appear Start Bridge, enable Bridge Mode, match port 5555, allow http://127.0.0.1:5555, and confirm another app is not using that port.
Telegram Bot API receives nothing Check token, Chat ID, bot membership/permissions, privacy mode, internet access, and https://api.telegram.org WebRequest permission.
Wrong symbol or symbol not found Show the broker symbol in Market Watch and configure Custom Mappings for unusual names.
LONG/SHORT signal is ignored Use exactly one direction. Text containing both LONG / SHORT is ambiguous and rejected.
Provider result text did not open a trade This is intentional for status messages such as TP hit, target reached, closed, or profit taken.
Reply command is ignored Confirm Reply Commands and the correct category/phrase are enabled, and reply directly to the original signal so the ticket target is proven.
Pending order is rejected Check market status, order side, current price, broker stop/freeze distance, SL/TP direction, minimum lot, filling rules, and Bridge failure feedback.
Multi-TP does not split Check Enable Signal TP, Enable MultiTP, active TP1/TP2/TP3 switches, Max TP Targets, allocation mode, lot size, and Prop Allow MultiTP.
Lot size is unexpected Check FIXED/RISK %, Per-Symbol Lots, Max Lot action, stop distance, SigTP allocation, and broker min/step. For local copying, also check Slave Lot Mode.
Local Master says Blocked By Another TCU Master owns the same file. Use the current main Master or deliberately click USE AS MAIN on the account you want to select.
New Master does not copy its old trades This is intentional after a main-Master takeover. Existing positions are baselined; open a new demo trade after the switch.
Slave duplicates trades after restart Confirm the exact v7.40 EA is attached, the account and Magic Number are unchanged, the role restored as SLAVE, and the state file was not manually deleted.
Slave does not close when Master terminal is off Auto-close pauses while the Master file is stale. This prevents a terminal shutdown from being misread as every trade closing.
Local copied comment is blank Check Comment Mode and Prop No Comments. OFF is supported and does not disable state-file tracking.
TCU and free NTS copier do not connect This is intentional. TCU uses TCU_TradeCopier.csv; NTS Simple Local Copier uses its own separate workflow.
Old Bridge signal did not execute after reconnect This is normally intentional stale-queue protection. Send a fresh test signal after connection and assignment are confirmed.

27. Advanced Martingale Warning

The Martingale area is an advanced, separately unlocked feature and is not part of the recommended quick setup.

Martingale can increase exposure rapidly and can exceed account or prop-firm loss limits. Do not enable it because a preset appears convenient. Understand the exact progression, reset rule, per-symbol state, maximum lot, maximum steps, and daily-loss protection first. Test it on demo across restarts and losing sequences before considering any live use.


28. Validation Summary for the v7.40 Candidate

Test area Result in the tested demo configuration
EA compilation Main and demo builds compiled with 0 errors and 0 warnings.
Parser/filter regression suite 106/106 checks passed, including duplicate, provider-update, reply-command, payload, and language safety gates.
Real Telegram cycle 19/19 checks passed in the tested routing configuration.
Live Bridge/EA matrix 22/22 checks passed using a demo BTCUSD workflow.
Local copier Copy, restart, deduplication, owner switching, comment OFF tracking, SL/TP handling, and auto-close passed across Exness, XM, Fusion, and IC demo terminals.

This validation is evidence for the tested builds and demo environment. It is not a guarantee for every broker, symbol, VPS, network, account type, provider format, or market condition. Netting accounts, broker-specific rules, live news events, OCR sources, and Discord setups should be tested separately by each user.


29. Important Limitations and Final Safety Notes

  • Hedging accounts are recommended. Netting accounts merge positions and can change copier/management behavior.
  • The local TCU copier supports one selected main Master per file, not simultaneous multi-master aggregation.
  • The local TCU copier mirrors open positions, not pending orders.
  • The local Master publishes every open account position, including manual and other-EA positions.
  • OCR can misread images. Always review new image formats on demo.
  • Broker execution, spread, slippage, liquidity, gaps, stop rules, and market hours remain outside the EA's control.
  • MT5, Algo Trading, Bridge, internet access, and the VPS must remain healthy for features that depend on them.
  • No parser can safely infer every informal provider message. Use clear, tested formats and reply context.
  • Never reuse TCU's default Magic Number 333333 in an unrelated EA on the same account.
  • Test every provider, broker, symbol mapping, lot mode, prop rule, and restart path on demo before live use.
Risk warning: foreign exchange, CFDs, metals, indices, and crypto trading can cause rapid losses. A copier can repeat both good and bad source decisions across several accounts. Use conservative volume, verify every receiving account, and never risk money you cannot afford to lose.

Support

For help with setup, broker symbols, Telegram Bot API, NTS Bridge, private Telegram sources, Discord, VPS configuration, local copying, reply commands, or provider-format compatibility, contact Navigator Trading Systems through the MQL5 product page or private messages.

Please include the original signal, Bridge history, MT5 Experts log, account type, exact broker symbol, EA version/build, and screenshots of the relevant settings.

(c) 2026 Navigator Trading Systems