3D NEXUS META — Dual MT5 Bridge

00

What is the Dual Bridge?

Understanding the two-broker architecture

📡DATA STATION

Connected to a broker with Level 2 Market Depth (DOM). Recommended: AvaFutures MT5 — provides real CME futures L2 data including bid/ask ladders up to 10 levels deep.

ℹ️

AvaFutures provides the Futures MT5 account type with full CME market depth via CQG data feed.

⚡EXECUTION STATION

Connected to your preferred trading broker. Recommended: IC Markets MT5 — tight spreads, fast execution, no requotes. All orders from NEXUS META are routed here.

✓

IC Markets has paid out reliably without issues — a tier-1 broker for execution.

💡

Why two brokers?

Some brokers (like AvaFutures) have exceptional market depth data but limited instruments for execution. Others (like IC Markets) are excellent for execution but lack futures L2 DOM. The Dual Bridge combines the best of both worlds — best data + best execution.

01

How it Works

Data flow between NEXUS, the Bridge, and MT5 terminals

SYSTEM ARCHITECTURE

3D NEXUS META

Browser · ws://localhost:5555

│

WebSocket

▼

DUAL MT5 BRIDGE

Python · mt5_nexus_bridge_dual.py

Symbol Mapper · Order Router

▲ DOM / Ticks

Orders ▼

DATA STATION

AvaFutures MT5

CME L2 Market Depth

Real-time DOM, ticks,
bid/ask levels

│

EXEC STATION

IC Markets MT5

Spot Gold, Forex, CFDs

Order routing,
fills, positions

⚡

Important: The Python MetaTrader5 API connects to only one MT5 terminal at a time. The Bridge switches briefly to EXEC for order placement, then returns to DATA for continuous streaming. This switch takes only a few milliseconds.

02

Prerequisites

Everything you need before starting

🖥️SOFTWARE REQUIREMENTS

✓
Python 3.10+ — Download from python.org. During install, check Add Python to PATH ✅
✓
MetaTrader 5 — Installed twice (two separate installations for two brokers, or two instances)
✓
Python packages — MetaTrader5 and websockets (installed automatically by the BAT file)
✓
3D NEXUS META — The 3D_NEXUS_META.html file and Chrome/Edge browser

📂BROKER ACCOUNTS REQUIRED

✓
AvaFutures account (or any broker with CME futures L2 DOM) — for the DATA station. Request the Futures MT5 account type specifically.
✓
IC Markets account (or your preferred execution broker) — for the EXEC station. Works with standard MT5 account.

⏰

Market Hours CME Futures markets are closed on weekends. AvaFutures opens Sunday at ~11:59 PM CET. You can test the bridge connection and symbol mapping during off-hours — just no live data will flow until markets open.

📁FILES REQUIRED (place in same folder)

# Your project folder should contain:
📄 3D_NEXUS_META.html
📄 mt5_nexus_bridge_dual.py
📄 START_NEXUS_DUAL.bat
📄 symbol_mappings.json (auto-generated on first run)

03

Installation

One-time setup process

1

INSTALL PYTHON

Download and install Python 3.10 or higher

Go to python.org/downloads and download the latest release. During installation, make sure to check "Add Python to PATH" — this is required for the BAT file to work.

# Verify installation — open Command Prompt and run:
python --version
# Should show: Python 3.10.x or higher

2

INSTALL DEPENDENCIES

The BAT file handles this automatically

When you double-click START_NEXUS_DUAL.bat for the first time, it automatically installs the required packages. Or install manually:

pip install MetaTrader5 websockets

3

DOWNLOAD BRIDGE FILES

Download the Dual Bridge V3 package

Download the latest Dual Bridge package from the link provided by your NEXUS license. Extract all files into the same folder as your 3D_NEXUS_META.html.

🔗

Latest version: dualMT5bridgeNEXUSv3.zip — available at metaquantuniverse.com/download/

4

INSTALL MT5 TERMINALS

Install and log in to both MT5 accounts

Install MetaTrader 5 for each broker. Log in to your AvaFutures account (DATA) and IC Markets account (EXEC). Both terminals must be open and logged in before starting the bridge.

💡

You can install each broker's MT5 in a different folder. Example: C:\MT5_AvaFutures\ and C:\MT5_ICMarkets\

04

Full Launch Guide

The exact sequence — follow this every time you start

⚠️

Order matters! Always follow this exact sequence. Starting in the wrong order is the most common cause of connection issues.

1

STEP 1

Start MT5 AvaFutures (DATA station)

Open your AvaFutures MetaTrader 5 terminal. Make sure it is fully connected and logged in (green connection indicator in the bottom-right corner). Do NOT proceed until it shows market data.

AvaFutures MT5 — Connected and running

2

STEP 2

Start MT5 IC Markets (EXEC station)

Open your IC Markets MetaTrader 5 terminal. Ensure it is connected. Enable AutoTrading in MT5: click the "AutoTrading" button in the top toolbar (it should turn green/active).

IC Markets MT5 — Connected and AutoTrading enabled

🔴

Critical: AutoTrading MUST be enabled in MT5 for the bridge to send orders. Without this, orders will fail silently.

3

STEP 3

Launch the Dual Bridge

Double-click START_NEXUS_DUAL.bat. A GUI window will open. Wait for it to fully load — this takes 3–5 seconds.

NEXUS DUAL MT5 BRIDGE v3

AUTO-DETECTED MT5 TERMINALS

DATA (DOM) AvaFutures MT5 · C:\...\terminal64.exe

EXEC IC Markets MT5 · C:\...\terminal64.exe

4

STEP 4

Configure the Bridge — Auto-Detect

In the Bridge GUI, click the DETECTED button (or equivalent dropdown). The bridge will automatically find all running MT5 terminals on your computer.

🔍

If auto-detect finds both terminals, you'll see them listed. Select AvaFutures for the DATA role and IC Markets for the EXEC role using the dropdowns.

5

STEP 5

Assign DATA and EXEC stations

In the GUI, use the dropdowns to assign:

→
DATA station = AvaFutures MT5 (provides real CME L2 market depth)
→
EXEC station = IC Markets MT5 (receives your orders)

ℹ️

You do NOT need to enter login/password if both MT5 terminals are already running and logged in. The bridge connects directly to the running process.

6

STEP 6

Check Symbol Mapping

In the bridge GUI, check the MAPPING list. This shows how symbols from AvaFutures (DATA) map to IC Markets (EXEC). Example: EPM26 (AvaFutures futures contract) → XAUUSD or XAUUSD.sml on IC Markets.

If the mapping for your instrument is wrong, correct it manually and click SAVE MAPPINGS.

SYMBOL MAPPING

AvaFutures EPM26 → IC Markets XAUUSD

AvaFutures ENQc1 → IC Markets NASUSD

7

STEP 7

Click START BRIDGE

Click the START BRIDGE button. The status bar at the bottom of the GUI should turn green and show "Bridge running on port 5555".

STATUS

▶ START BRIDGE

■ STOP

Bridge running on ws://localhost:5555 · DATA: AvaFutures · EXEC: ICMarkets

8

STEP 8

Open NEXUS META in your browser

Open 3D_NEXUS_META.html in Chrome or Edge. Do NOT open NEXUS before starting the bridge — the bridge must be ready first.

9

STEP 9

Switch exchange to "MT5 Local"

In the NEXUS Controls panel, find the Exchange dropdown. Select MT5 Local (Futures / CFD). The bridge URL should auto-populate as ws://localhost:5555.

💡

If you need to switch from another exchange (e.g., Binance) to MT5: change the exchange dropdown from Binance → MT5. This resets the bridge connection.

10

STEP 10

Add instruments to your MT5 Watchlist

In AvaFutures MT5, open the Market Watch (Ctrl+M), right-click → Show All, then find the instruments you want to trade and add them to the watchlist. NEXUS will only display instruments that are in the watchlist.

⚠️

Common mistake: If NEXUS shows only 2 pairs in the dropdown, this means only 2 instruments are in your MT5 watchlist. Add more instruments in MT5 first, then they will appear in NEXUS automatically.

11

STEP 11

Select instrument and verify connection

In NEXUS, pick an instrument from the dropdown (e.g., GOLD, EPM26, or whatever appears from your AvaFutures watchlist). You should see:

✓ Connection status: LIVE
✓ Real-time bid/ask price updating
✓ 3D order book surface populating with data
✓ Trade bubbles appearing as trades execute

12

STEP 12

Configure the EXECUTE panel

In NEXUS, open the EXECUTE panel. Set your trade size (in lots), order type (Market/Limit/Stop), and TP/SL in ticks. Verify the exchange badge shows MT5 LOCAL.

13

STEP 13

Test with a manual order

Before enabling auto-trading, test with a manual order. Click the BUY or SELL button. Verify the order appears in IC Markets MT5 terminal.

✅

If the order appears in IC Markets MT5, the full pipeline is working correctly!

14

STEP 14

Enable Auto-Trading

In the NEXUS EXECUTE panel, scroll down to the AUTO TRADE section. Configure minimum confidence, max positions, TP/SL in ticks. Click ACTIVATE. NEXUS will now automatically trade based on scalp signals.

You are fully operational!

05

Configuring NEXUS META

Key settings inside the browser interface

🔗MT5 BRIDGE URL

In the Controls panel, when MT5 Local is selected, the bridge URL field appears. Default value:

ws://localhost:5555

Only change this if you're running the bridge on a different machine or port.

⚙️TICK SIZE

The bridge auto-detects and sets the correct tick size when you subscribe to a symbol. If needed, adjust manually in Controls → Tick Size dropdown.

💡

Changing the tick size in MT5 mode does NOT reconnect — it just re-maps the price grid. Safe to change anytime.

🧹CLEAN MEMORY BUTTON

If the 3D surface looks glitchy or bubbles are not rendering correctly, click CLEAN MEM in the info panel. This flushes all 3D buffers and resets the visual state without disconnecting from the bridge.

💡

Use CLEAN MEM when the surface looks frozen or distorted. It does not close the bridge connection.

06

Symbol Mapping

How the bridge translates symbols between brokers

Different brokers use different names for the same instrument. The bridge uses a 3-level mapping system to automatically translate AvaFutures symbols to IC Markets equivalents when routing orders.

AUTO-MAPPING LEVELS (in order of priority)

1
Exact match — Same symbol name on both brokers. No config needed.
2
Canonical match — Strips expiry codes. EPM26 → EP → matches SPXUSD etc.
3
Known equivalences — Built-in database of common mappings between brokers.

COMMON SYMBOL MAPPINGS

AvaFutures (DATA)	IC Markets (EXEC)	Instrument
EPM26 / ESM26	SPXUSD or US500	E-mini S&P 500
ENQc1 / NQM26	NASUSD or NAS100	E-mini Nasdaq 100
GCc1 / GCM26	XAUUSD	Gold CME Futures
CLc1 / CLM26	XTIUSD or USOIL	Crude Oil WTI
BTCUSD	BTCUSD	Bitcoin CFD
EURUSD	EURUSD	Euro / US Dollar
XAUUSD	XAUUSD	Gold Spot

✏️MANUAL OVERRIDE — symbol_mappings.json

If auto-mapping fails, edit the symbol_mappings.json file manually:

{
  "mappings": {
    "EPM26": "SPXUSD",
    "ENQc1": "NAS100",
    "GCc1": "XAUUSD",
    "CLc1": "USOIL"
  }
}

After editing, click SAVE MAPPINGS in the Bridge GUI. The bridge applies changes immediately without restarting.

07

Trade Execution

How orders flow from NEXUS to your MT5 broker

ORDER TYPES SUPPORTED

✓ MARKET — Instant execution at current price
✓ LIMIT — Entry at specified price or better
✓ STOP — Entry when price reaches trigger

TP / SL IN TICKS

Take Profit and Stop Loss are set in ticks (minimum price increments). The bridge automatically converts to the correct price based on the instrument's tick size from MT5.

Example: Gold (XAUUSD) tick = 0.01. TP = 20 ticks = $0.20 profit target.

🔄

2-Step TP/SL Process

For MARKET orders with TP/SL: the bridge first sends the market order, waits for the fill confirmation with the exact execution price, then sends a modify_position request to set TP/SL precisely on the filled price. This ensures accuracy regardless of slippage.

08

Auto-Trading

Let NEXUS signals drive your execution automatically

AUTO-TRADE CONFIGURATION

MIN CONFIDENCE %

Minimum signal confidence to trigger a trade. Start conservatively at 65–70%.

MAX POSITIONS

Maximum simultaneous open positions. Start with 1 until you're comfortable.

TP (TICKS)

Take profit in tick units. 20 ticks on Gold = $0.20 move.

SL (TICKS)

Stop loss in tick units. Always set a stop loss. Recommended: half of TP.

⚠️

Risk Warning

Auto-trading involves real financial risk. Always test with minimum lot size first. Use a demo account to validate signal performance before going live. NEXUS signals are generated from market microstructure patterns — no trading signal is 100% reliable.

SIGNAL TYPES THAT CAN TRIGGER AUTO-TRADES

🛡️
ABSORPTION — Smart money absorbing supply/demand at a price level
🧊
ICEBERG — Hidden liquidity detected (refilling pattern)
💀
EXHAUSTION — Opposite side losing steam (bid or ask wall melting)
⚡
DELTA SPIKE — Aggressive volume burst in one direction

09

Troubleshooting

Solutions to the most common problems

🔧

Most issues are solved by a complete restart in the correct order.

See the Emergency Protocol in Section 10 for the fastest recovery procedure.

Problem	Likely Cause	Solution
Bridge disconnected — reconnecting	NEXUS was closed or refreshed while bridge was running. The WebSocket connection timed out.	Do a full restart: close NEXUS, stop bridge, restart bridge, reopen NEXUS, reselect MT5 Local.
Nexus shows "Waiting for connection"	NEXUS opened before the bridge was ready, or the bridge crashed silently.	Switch exchange to Binance, then switch back to MT5 Local. This resets the WebSocket handshake.
NEXUS META not connecting (stuck)	Bridge is running but NEXUS cannot reach it. Firewall or port conflict.	Check that port 5555 is not blocked by Windows Firewall. Click "Clean Memory" in NEXUS info panel. Try full restart.
Only 2 pairs visible in NEXUS dropdown	Only 2 instruments are in the AvaFutures MT5 watchlist.	In AvaFutures MT5: Market Watch → right-click → Show All → add desired instruments → restart bridge.
Orders not executing	AutoTrading disabled in IC Markets MT5, or EXEC station not set correctly.	Enable AutoTrading button in IC Markets MT5 toolbar. Verify EXEC station is set to IC Markets in bridge GUI.
Wrong symbol on execution (e.g., buying NQ when chart shows Gold)	Symbol mapping error. AvaFutures symbol not correctly mapped to IC Markets equivalent.	Edit symbol_mappings.json manually. Set the correct AvaFutures → IC Markets mapping. Save and reload bridge.
TP/SL not applied after order fill	MT5 rejected the modify_position request (symbol mismatch or invalid price).	Check the trade status in NEXUS execute panel. Verify tick size is correct. Try entering TP/SL manually in MT5.
Bridge GUI doesn't open	Python tkinter or GUI dependency missing.	Run in CLI mode: open Command Prompt, navigate to folder, run: `python mt5_nexus_bridge_dual.py --no-gui`
"pip is not recognized"	Python not added to PATH during installation.	Reinstall Python — check "Add to PATH" during setup. Or use: `py -m pip install MetaTrader5 websockets`
Bridge starts but no data flows	Markets are closed (weekend/holiday) or AvaFutures MT5 is not subscribed to the symbol.	Check market hours. Add the symbol to AvaFutures MT5 watchlist. Verify AvaFutures shows live prices.
Auto-trading not triggering	Confidence threshold too high, or no bridge connection to MT5.	Lower MIN CONF % to 60. Click APPLY SETTINGS. Verify bridge status shows MT5 connected. Check MT5 AutoTrading is ON.
3D surface is frozen / not updating	Memory overflow or rendering issue in the browser.	Click "CLEAN MEM" button in NEXUS info panel. If still frozen, refresh the browser page (bridge stays running).

10

Emergency Protocol

The fastest way to recover from any connection problem

When you encounter bridge disconnection or "stuck" connection issues, follow this exact sequence. This is the fastest, most reliable recovery method — it has been tested and confirmed working.

🚨 FULL RESET PROCEDURE

Close NEXUS META completely (close the browser tab).
In the Bridge GUI, click STOP BRIDGE. Then close the Bridge window entirely.
Verify both MT5 terminals (AvaFutures + IC Markets) are still running and connected.
Relaunch the bridge by double-clicking START_NEXUS_DUAL.bat.
In the bridge GUI, re-select DATA station (AvaFutures) and EXEC station (IC Markets).
Click START BRIDGE — wait for the green status bar.
Open 3D_NEXUS_META.html in a fresh browser tab.
In NEXUS Controls, switch Exchange to MT5 Local (Futures / CFD).
Select the instrument you want to trade from the dropdown.
You should see LIVE status and data flowing.

⚡QUICK FIX — Without Full Restart

If you see "disconnected" or "reconnecting" in NEXUS but the bridge is still running:

1. In NEXUS Controls, switch Exchange from MT5 Local to Binance SPOT
2. Wait 2 seconds
3. Switch back to MT5 Local
4. This resets the WebSocket handshake and forces a fresh connection

🖥️CLI MODE — If the GUI Fails to Open

If the GUI crashes or fails to start, run the bridge in headless CLI mode:

# Open Command Prompt, navigate to your folder:
cd C:\path\to\your\nexus\folder

# Run in CLI mode (uses saved config or defaults):
python mt5_nexus_bridge_dual.py --no-gui

# Or force single broker mode:
python mt5_nexus_bridge_dual.py --no-gui --single

# Custom port:
python mt5_nexus_bridge_dual.py --port 5555

11

Frequently Asked Questions

Common questions from NEXUS users

Do I need to enter my MT5 login and password in the bridge?

No! If both MT5 terminals are already running and logged in on your computer, the bridge connects directly to the running process using the MT5 Python API. You only need to provide credentials if you want the bridge to log in on your behalf (advanced use).

Can I use a single MT5 terminal (not dual mode)?

Yes. Run the bridge and uncheck "DUAL MODE" in the GUI, or use --single flag in CLI mode. You'll use one MT5 for both data and execution. This works perfectly if your broker provides good DOM data and execution.

What happens if the bridge disconnects while auto-trading is active?

Open positions remain open in MT5 — the bridge disconnecting does NOT close your positions. NEXUS will show a disconnection warning. Any already-set TP/SL on MT5 positions will still work independently. You must manually restart the bridge and reconnect to resume auto-trading.

Can I trade Spot Gold (XAUUSD) on IC Markets while using AvaFutures for data?

Yes. This is actually the primary use case. You use AvaFutures CME Gold Futures for the real-time L2 order book data (better market depth, institutional flow), and route actual orders to IC Markets Spot Gold (XAUUSD). The symbol mapping handles this automatically: AvaFutures GCc1 → IC Markets XAUUSD.

The futures markets are closed — can I still test the bridge?

Yes. You can test the bridge connection, GUI, symbol mapping, and manual order routing during off-hours. Just no live tick data or DOM will flow until markets open. Use Spot Gold or Forex instruments on IC Markets (which trade 24/5) to test execution.

How do I know which AvaFutures symbol corresponds to CME Gold Futures?

In AvaFutures MT5, CME Gold futures appear as GCM26 or GCc1 (continuous contract). These are the front-month CME Gold futures with full Level 2 market depth. The futures contract rolls quarterly — the expiry code changes (M for June, U for September, Z for December, H for March).

Can I use this bridge with Rithmic or other data feeds?

The Rithmic bridge is a separate file (rithmic_bridge.py) available as an add-on. Select "Rithmic Futures" in NEXUS exchange dropdown to use it. It connects to ws://localhost:5556 by default.

How do I update the bridge to a new version?

Download the new ZIP from metaquantuniverse.com, extract it, and replace the old mt5_nexus_bridge_dual.py file. Your symbol_mappings.json settings are preserved. The BAT file automatically picks up the new Python script.

Is my MT5 login data sent anywhere?

No. The bridge runs entirely on your local machine. It communicates only with the MT5 processes running locally via the official MetaTrader5 Python API. No data is sent to any external server. The WebSocket runs on localhost only.

Can I run NEXUS on a different computer than the bridge?

Yes. Run the bridge on the same machine as MT5. In NEXUS Controls, change the MT5 Bridge URL from ws://localhost:5555 to ws://[your-PC-IP]:5555. Make sure port 5555 is allowed through the firewall on the bridge machine.