N
3D NEXUS META
SIERRA CHART EXECUTION BRIDGE
V4.3 execution layer · READ/DATA already validated

Sierra Chart Bridge User Guide

Connect Sierra Chart to 3D NEXUS META for live DOM visualization, volume bubbles, Time & Sales, manual execution, and signal-driven auto-trading.

This guide is written for the production 3D NEXUS META cloud version: https://nexus-meta-auth.3dnexusmeta.workers.dev/, together with the local Sierra execution bridge sc_nexus_bridge_dtc_v4_3_execution.py and optional launcher START_SC_EXEC_V4_3.bat.

⚡ Quick Start ⌁ Troubleshoot
Mission briefing

What this integration does

The bridge has two separate engines: one reads Sierra Chart market data files for the 3D map, the other submits orders through Sierra Chart DTC.

READ / DATA

Market data stream

Reads local Sierra Chart intraday and market depth files, then broadcasts order book levels and trade prints to NEXUS over ws://localhost:5559.

EXECUTION

Order routing

When trading is enabled, the Python bridge connects to Sierra Chart DTC on 127.0.0.1:11099 and sends MARKET, LIMIT, STOP, cancel, close, and position requests.

SECURITY

Auth token required

Every order command must include the bridge token. The new NEXUS build adds a token field directly in the Sierra Chart panel and injects it automatically.

✓
Current status from testing

The 3D map, volume bubbles, and Time & Sales are visible. That confirms the READ/DATA side is working. The remaining work is execution: token, DTC readiness, and auto-trade routing.

Architecture

The route from chart to order

DATA path

Sierra Chart writes files C:\SierraChart\Data\SYMBOL.scid C:\SierraChart\Data\MarketDepthData\SYMBOL.YYYY-MM-DD.depth ↓ sc_nexus_bridge_dtc_v4_3_execution.py tails files ↓ WebSocket broadcast on ws://localhost:5559 ↓ 3D NEXUS META renders map, bubbles, Time & Sales

EXECUTION path

3D NEXUS META creates order payload ↓ Auth token injected into order JSON ↓ Python bridge validates token ↓ DTCExecClient connects to Sierra Chart DTC :11099 ↓ Sierra Chart routes order to SIM or live account
Before launch

Requirements

Install the cockpit parts before enabling the lasers. Keep all first tests in SIM mode.

OS

Windows PC

Recommended because Sierra Chart and the supplied BAT launcher are Windows-oriented.

Platform

Sierra Chart

Installed, connected to a data feed, and configured for the symbol you want to trade.

Runtime

Python 3.10+

Python must be available in Windows PATH. The BAT file checks this automatically.

Dependency

websockets

The START file installs it automatically if missing. Manual command below.

python -m pip install websockets
Package contents

Files to use

FilePurposeWhere it goes
Production 3D NEXUS META URLThe cloud-hosted NEXUS cockpit with Sierra token field, manual order routing, auto-trade unlock, and Sierra execution badge.Open https://nexus-meta-auth.3dnexusmeta.workers.dev/ in the browser.
sc_nexus_bridge_dtc_v4_3_execution.pyThe Python bridge. Reads .scid/.depth data files and optionally sends orders through Sierra Chart DTC.Same folder as the BAT launcher.
START_SC_EXEC_V4_3.batOne-click launcher. Checks Python, installs websockets if missing, and opens the bridge GUI.Same folder as the Python bridge.
nexus_sc_v4_config.jsonCreated automatically by the bridge. Stores data folder, bind mode, and auth token.Created next to the Python bridge after first run.
Fast route

Quick start checklist

Use this when you just want to get Sierra Chart + NEXUS running in SIM as quickly as possible.

Prepare Sierra Chart

Open a chart or DOM for the symbol, for example MNQM26-CME. Make sure Sierra Chart is connected to live or sim data.

Enable market depth recording

Enable market depth recording for the symbols you want to stream. Without depth files, the map can lose its skyscrapers.

Enable DTC server

In Sierra Chart, enable the DTC Protocol Server and use port 11099. This is required for execution, even if market data already works.

Launch the bridge

Double-click START_SC_EXEC_V4_3.bat. In the bridge GUI, select the Sierra Chart Data folder and check Enable trading. Press START.

Copy the Auth token

Copy the full token shown in the bridge window. Do not copy only the shortened preview.

Open NEXUS

Open https://nexus-meta-auth.3dnexusmeta.workers.dev/ in your browser. Select Sierra Chart (DTC) in the Exchange dropdown.

Paste token into NEXUS

In the Sierra Chart DTC panel, paste the bridge token into Auth token and press SAVE. NEXUS should show token armed / execution ready.

Test in SIM

Use SIZE = 1 contract. Send one tiny market order, verify it appears in Sierra Chart, then press CLOSE ALL.

Sierra Chart setup

Configure Sierra Chart

DATA

For the map, bubbles, and T&S

  • Open a chart or DOM for every symbol you want NEXUS to read.
  • Confirm Sierra Chart is receiving real-time or sim data.
  • Enable Record Market Depth Data for the symbol.
  • Use the exact Sierra symbol in NEXUS, for example MNQM26-CME.
  • The bridge default data folder is C:\SierraChart\Data.
EXECUTION

For orders

  • Enable the Sierra Chart DTC Protocol Server.
  • Use DTC port 11099.
  • Use SIM first. Confirm order routing in Sierra Chart before live trading.
  • Make sure a trade account is available to the DTC server.
  • If NEXUS says data works but orders fail, troubleshoot DTC separately.
⌁
Data and execution are independent

The map can work while orders fail. That usually means the file reader is healthy, but DTC trading is not connected, not enabled, or not authenticated.

Bridge launcher

Install and start the bridge

Put files in one folder

Place START_SC_EXEC_V4_3.bat and sc_nexus_bridge_dtc_v4_3_execution.py together.

Run the BAT file

Double-click the BAT launcher. It checks Python and installs the websockets package if needed.

START_SC_EXEC_V4_3.bat

Bridge GUI settings

  • Data folder: usually C:\SierraChart\Data
  • Bind: Localhost / 127.0.0.1 for normal use
  • Enable trading: check this for execution
  • Filter: optional regex to reduce symbols

Press START

The bridge should show Running on port 5559. If trading is enabled, the log should show DTC connection attempts to 127.0.0.1:11099.

Headless / advanced launch examples

python sc_nexus_bridge_dtc_v4_3_execution.py --no-gui --data-folder "C:\SierraChart\Data" --enable-trading
python sc_nexus_bridge_dtc_v4_3_execution.py --no-gui --filter "^(MNQ|MES|ES|NQ)" --enable-trading

Use --bind-all only for explicit remote-machine setups. Localhost is safer for normal trading.

Security key

Auth token workflow

The token is the gatekeeper. No token, no order. That is intentional.

Where to find it

  1. Start the Python bridge GUI.
  2. Find the Auth token field.
  3. Copy the full token.
  4. Paste it in NEXUS under Sierra Chart DTC → Auth token.
  5. Press SAVE.

What it does

NEXUS automatically adds the token to these trading messages:

  • BUY / SELL order messages
  • CLOSE ALL
  • close_position
  • cancel_order
  • auto-trade signal orders
!
Never send live orders until token status is green

If NEXUS shows “Paste SC auth token first”, “Bearer token mismatch”, or “Authentication required”, the token in NEXUS does not match the bridge. Copy it again from the bridge window and press SAVE.

NEXUS setup

Connect the HTML cockpit

Open the updated HTML

Open the production NEXUS URL: https://nexus-meta-auth.3dnexusmeta.workers.dev/. Avoid using old local HTML files when testing Sierra execution.

Select Sierra Chart

In the exchange selector, choose 🏔️ Sierra Chart (DTC). The top status badge and execution panel should switch to Sierra Chart.

Check Bridge URL

The default bridge URL should be:

ws://localhost:5559

Reload symbols

Use the reload button near Trading Pair if needed. Select the exact Sierra symbol, for example MNQM26-CME.

Confirm data

You should see the 3D liquidity map, volume bubbles, Time & Sales prints, and the Sierra status badge. If yes, READ/DATA is healthy.

Execution

Manual orders

Start with tiny SIM orders. One contract, one click, one verification. No fireworks until the wires are proven.

MARKET

Immediate order

Use for the first SIM test. Size is treated as contracts for futures symbols. If size is below 1, NEXUS corrects it to 1.

LIMIT

Price order

Enter a valid price or let NEXUS estimate one near the book. Confirm the order appears as working inside Sierra Chart.

STOP

Trigger order

Use only after MARKET and LIMIT have been verified. Confirm Sierra Chart accepts the stop parameters for that symbol/account.

Set size

For MNQ/MES/ES/NQ futures, set SIZE = 1 for first tests. Do not use crypto-style sizes such as 0.001 on futures.

Set TP / SL ticks

Optional. NEXUS can arm virtual TP/SL after fill. These are monitored by the HTML page.

Click BUY or SELL

NEXUS sends a token-authenticated order to the Python bridge. The bridge submits it to Sierra Chart DTC.

Verify in Sierra Chart

Watch the Trade Activity Log, Orders window, or chart trade markers. Confirm the order reaches Sierra Chart and is in SIM mode.

Close safely

Use CLOSE ALL from NEXUS or close directly inside Sierra Chart during the first validation round.

⚠
Virtual TP/SL limitation

The current Sierra integration uses NEXUS-side virtual TP/SL monitoring. The NEXUS page must remain open and connected. For broker-native protection, add Sierra Chart attached orders or native DTC bracket logic in a future bridge build.

Signal to order

Auto-trade with Sierra Chart

The new build unlocks Sierra Chart as an auto-trade execution route instead of blocking on MT5 only.

Required before enabling

✓
Sierra Chart selected in Exchange dropdown.
✓
Bridge connected on ws://localhost:5559.
✓
Auth token pasted and saved in NEXUS.
✓
Sierra DTC server enabled on 11099.
✓
Bridge GUI has Enable trading checked before START.
✓
SIM mode confirmed.

Recommended first settings

Min Conf75–85% for first tests
Max Pos1
TP10–20 ticks
SL8–12 ticks
Cooldown30–60 seconds
SignalsStart with one signal type only

Set safety limits

Set Daily Loss Limit and Daily Profit Limit. Set both to 0 only when intentionally disabling the limits for testing.

Apply settings

Press APPLY SETTINGS after changing confidence, TP, SL, max position, cooldown, or signal filters.

Enable auto-trade

Toggle Auto Trade to ACTIVE. The status should no longer say “Auto-trade requires MT5”. It should arm Sierra Chart execution.

Watch one signal

Let only one SIM trade trigger. Confirm order, fill, virtual TP/SL behavior, and close behavior before expanding settings.

Risk controls

Close, positions, and emergency actions

CLOSE ALL

NEXUS sends a close_all request to the bridge. The bridge requests current DTC positions and submits opposite MARKET orders for non-zero positions.

POSITIONS

NEXUS requests Sierra Chart DTC positions and updates the position monitor when DTC responses arrive.

Manual override

During early tests, always keep Sierra Chart visible so you can flatten directly from Sierra Chart if the browser or bridge becomes unresponsive.

⏻
Emergency rule

If there is any doubt, close from Sierra Chart first. Treat NEXUS as a cockpit, but Sierra Chart remains the trading terminal connected to the broker/account.

Validation protocol

Recommended SIM test plan

Data verification

  • Map moves.
  • Volume bubbles print.
  • Time & Sales updates.
  • Symbol badge matches Sierra Chart symbol.

Token verification

  • Paste token.
  • Save token.
  • Check status says execution ready / token armed.
  • Reload page and confirm token persists locally.

Manual BUY test

SIM only. Set SIZE = 1, MARKET, TP/SL optional. Click BUY. Confirm order appears in Sierra Chart.

Manual SELL test

After closing the first trade, send one SELL. Confirm direction, size, account, and order type are correct.

CLOSE ALL test

Open one SIM position, press CLOSE ALL, verify Sierra Chart flattens it.

Auto-trade test

Max Pos = 1, high confidence, one signal enabled, cooldown 60 seconds. Let one signal fire, then switch OFF and review logs.

When the cockpit coughs smoke

Troubleshooting

Most failures fall into one of four baskets: token, WebSocket, DTC, or symbol mismatch.

Error / SymptomLikely causeFix
Authentication required / Bearer token mismatchNEXUS did not send the correct bridge token.Copy the full token from the bridge GUI, paste into NEXUS Sierra Chart Auth token, press SAVE, retry.
Paste SC auth token firstToken field is empty in NEXUS.Paste token and confirm the hint says token armed.
Auto-trade requires MT5Old HTML is being used or browser cache has old code.Open the production NEXUS URL: https://nexus-meta-auth.3dnexusmeta.workers.dev/. Hard refresh the browser. Confirm the exchange badge says SIERRA CHART.
SC Bridge not connectedPython bridge is not running or URL/port is wrong.Start START_SC_EXEC_V4_3.bat. Check ws://localhost:5559. Verify no other bridge occupies port 5559.
Trading not enabled on this bridge instanceBridge started without Enable trading.Stop bridge, check Enable trading in the GUI, START again.
Trading is not readyDTC server not connected, no trade account, or Sierra Chart DTC not enabled.Enable Sierra DTC Protocol Server on port 11099, confirm Sierra is connected, restart bridge.
Data works but orders failFile reader is OK, DTC execution path is not.Troubleshoot DTC separately. Confirm logon, trade account, TradingIsSupported, and SIM/live account status.
No volume bubbles / no Time & SalesTrades not streaming from .scid, wrong symbol, or chart not open.Open the symbol chart in Sierra, confirm data feed, select the exact symbol in NEXUS.
Flat / empty depth mapMarket depth files are not being recorded.Enable Record Market Depth Data in Sierra Chart for the symbol and wait for depth to populate.
Order size looks wrongUsing crypto-style quantity on futures.For futures, use whole contracts. Start with SIZE = 1.
Wrong symbol routedSymbol in NEXUS does not match Sierra Chart exactly.Select exact Sierra symbol from the bridge symbol list, for example MNQM26-CME.
LIMIT / STOP rejectedInvalid price, unsupported order type/account rule, or bad tick size.Test MARKET first. Then set valid price increments matching the Sierra symbol tick size.
Virtual TP/SL did not closeNEXUS page closed, browser slept, or connection dropped.Keep NEXUS open for virtual TP/SL. For live protection, use Sierra attached orders until native bracket logic is added.
Debugging

What to send when reporting an issue

Screenshots

  • NEXUS status / error message.
  • Bridge GUI with token hidden if needed.
  • Sierra Chart Trade Activity Log.
  • Sierra Chart DTC server settings.

Text details

  • Exact symbol, for example MNQM26-CME.
  • SIM or live mode.
  • Order type and size.
  • Whether data map, bubbles, and Time & Sales are working.
  • Bridge version and HTML version.
Advanced notes

Operating details

Token storage

NEXUS stores the Sierra auth token in browser localStorage using a local-only key. It is not a broker API key, but still treat it like a trading permission key.

Localhost by default

The bridge binds to 127.0.0.1 by default. This is safer. Only use bind-all when NEXUS and the bridge intentionally run on different machines.

Symbol filter

Use the bridge filter to reduce symbol list noise. Example: ^(MNQ|MES|ES|NQ).

Native brackets later

Future improvement: add Sierra Chart / DTC attached order support so TP/SL lives server-side instead of being monitored by the browser.

Final pre-flight

Before sending real orders

Green lights

✓
3D map updates from Sierra Chart.
✓
Volume bubbles print on the surface.
✓
Time & Sales updates live.
✓
Bridge status shows running on port 5559.
✓
DTC logon and trade account are visible in bridge logs.
✓
NEXUS says SC execution ready / token armed.
✓
SIM BUY, SELL, and CLOSE ALL have been tested.

Red lines

!
Do not trade live if token errors still appear.
!
Do not trade live if DTC trading is not confirmed.
!
Do not rely on browser virtual TP/SL as your only live risk control.
!
Do not use fractional futures size. Start with 1 contract.
!
Do not enable auto-trade before manual order tests are clean.
FAQ

Common questions

Why does the map work while orders fail?

Because the map uses the file reader path, while orders use Sierra Chart DTC. They are two different lanes.

Is the token the Sierra Chart password?

No. It is a local bridge token created by the Python bridge to protect order commands.

Should I use Bridge 2.0 or V4.3?

Use V4.3 for this integration. The tester confirmed V4.2 works for data where Bridge 2.0 did not work on his system.

Can auto-trade use Sierra Chart now?

Yes, in the updated SierraExec HTML. The old MT5-only block is bypassed for Sierra Chart.

Are TP/SL orders native at the broker?

Not yet in this version. TP/SL is virtual inside NEXUS for Sierra Chart execution. Native attached orders should be added later for live-grade protection.

What should the first live size be?

After SIM validation, use the minimum safe contract size. For many futures tests, that means 1 micro contract, but only after manual SIM tests are clean.