Frequently asked questions

No. The copier is infrastructure. It does not generate entries, exits or trading ideas by itself. The trading logic must already exist in your strategy or workflow.

The source platform controls the logic. The MT5 side should be treated as the execution layer, not as the decision maker. If the source strategy remains in a position, the copier will normally try to keep the MT5 side aligned with that state.

No. The key requirement is that the source strategy can generate the expected signal/output. The MT5 side can be a demo account, live account, prop-firm account or other compatible MT5 environment, depending on your broker and configuration.

Yes. Demo testing is the correct first step. Use small size, verify symbol mapping, lot conversion, synchronization, reconnect behaviour and broker execution before using real capital.

Yes, if the mapping is configured correctly. This is useful when the research logic is built on a continuous contract while execution is routed to the broker-specific MT5 symbol, CFD or synthetic equivalent. The conversion must be tested carefully.

The project is built around MultiCharts / PowerLanguage workflows. Other workflows can be evaluated only when they can produce a structured, validated signal with clear symbol mapping, side, quantity, order type, model ID and execution rules.

No. Differences can come from spread, slippage, swaps, sessions, broker symbols, lot steps, order execution rules, latency, platform reconnects and data differences. The copier reduces operational friction; it does not remove execution risk.

You need MultiCharts or a compatible source workflow, MetaTrader 5, the Expert Advisor, a defined signal/output folder, broker symbols to map, lot-sizing rules and a demo account for validation.

Check that algorithmic trading is enabled in MT5, the Expert Advisor is attached to the right chart, the Experts tab shows a clean initialization, and the source platform is writing the expected signal file or message in the expected location.

Use a stable folder that both the source workflow and the MT5 side can access. The path must match the input used by the Expert Advisor. Avoid temporary folders or paths that change after a restart.

Yes. A VPS is often preferable for automated workflows because MultiCharts, MT5 and any relay or helper process can remain online continuously. The VPS should be stable, close enough to the broker/server for your execution needs and monitored regularly.

Yes, if the machine is stable and remains online. The important point is that the source platform and MT5 can access the same configured workflow and that sleep, updates and network interruptions are controlled.

Usually yes, if the account is a normal MT5 environment and the prop-firm rules allow the type of automation used. Always verify the firm’s rules on EAs, copy trading, news, latency arbitrage, hedging and overnight exposure.

Some components may be delivered as protected tools rather than open source. This protects the infrastructure logic. You can still use the component as intended even if the internal code is not visible.

No. First install on demo, then test with minimal size. Only after mapping, synchronization and broker behaviour are understood should you consider live use.

The source symbol and broker-specific MT5 symbol must be explicitly matched. For example, the research side may use a futures or continuous symbol while the broker side may use a CFD or suffix-based symbol. Incorrect mapping is one of the most common causes of wrong execution.

Position size must be translated from contracts, units or strategy size into the MT5 lot format accepted by the broker. Lot step, minimum lot, maximum lot, contract value and account currency must be checked.

Yes, but each strategy should be separated by model identity, magic number, naming convention or another unambiguous routing rule. Without separation, strategies can interfere with one another.

Avoid changing a live strategy mid-session. A cleaner approach is to load the modified strategy on a separate chart, use a new model identifier or magic number, connect it to a separate MT5 configuration and retire the older version only after positions are flat or controlled.

If the source strategy still considers the position open, the synchronization logic may detect that MT5 is no longer aligned and reopen the position. The source strategy should be treated as the master state unless you intentionally disable or disconnect the copier before manual intervention.

You can, but the copier may re-align the position if the source platform still shows it as open. For manual intervention, first disable the relevant copier/chart or make sure the source strategy has also exited.

This depends on the broker account type and how the Expert Advisor is configured. Hedging accounts are usually easier for separating models, while netting accounts require more care because positions on the same symbol are aggregated.

It can be designed for stop-and-reverse or fast direction changes, but the implementation must be tested. Close/reopen timing, broker execution rules and lot conversion must be checked in demo before live use.

Visible SL/TP can be used for broker, prop-firm or risk-display purposes, but the actual strategy logic should still be clear. If MT5 exits while the source strategy remains in position, synchronization rules may re-open exposure.

Latency depends on the source platform, local machine or VPS, file/message relay method, MT5 terminal, broker server and network. The copier is not a low-latency HFT solution; it is an execution workflow tool for systematic strategies.

Check that the source strategy is actually generating an order or signal, that the output file/message is written in the configured folder, that the magic number/model ID matches, and that the MT5 Experts tab shows a successful initialization.

Check that MultiCharts has finished loading/backfilling, automated trading is enabled in MT5, the market is open, the symbol is tradeable, the lot size is accepted and the broker has not rejected the order.

Useful material includes MT5 Experts logs, MT5 Journal logs, screenshots of the EA inputs, source-platform order output, the signal file if used, symbol specifications and a short description of the expected versus actual behaviour.

The result depends on the disconnection duration and the current state. When reconnected, the system may need to resynchronize. Always test reconnect scenarios in demo.

If the source platform stops, new signals will not be produced. Existing MT5 positions may remain open depending on how the system is configured. You should have a clear emergency procedure before live use.

Avoid updates while positions are open unless you understand the consequences. The safer procedure is to stop new signals, flatten or isolate open positions, back up settings, then update.

A live automated setup should be monitored daily, and more often during market open, news, platform restarts or broker maintenance windows. Automation reduces manual work; it does not remove operational responsibility.

Run a full checklist: symbol mapping, lot conversion, demo trades, restart test, disconnect test, close/reopen test, broker rejection test, log review and small-size live validation.

No. The site provides research notes, software material and technical infrastructure. Nothing should be understood as personalized investment advice or a recommendation to trade.

You can use material at your own responsibility after review and testing. Live use requires understanding broker rules, costs, slippage, sizing, platform stability and risk limits.

No. No copier setup, code component or research note can guarantee profits, execution quality or future results.

The user is responsible for live trading decisions, account risk, broker choice, configuration, testing and monitoring. Technical tools can fail or behave differently under real conditions.

Yes, use the contact page with enough technical detail. Include platform, broker, account type, symbol, screenshots, logs and the exact issue.

You should understand the logic, assumptions and risks before using any code in live markets. If the code is protected, you should still understand the operational behaviour and configuration.

No, unless explicitly allowed. The copier and related tools are intended for the purchaser’s own use under the relevant terms.

Do not go live. Test on demo, reduce size, ask for clarification or request a technical review before risking capital.