MT4i Personal Trade Copier
MT4i Personal Trade Copier
www.mt4i.com
Contents: 1. Overview of the Personal Trade Copier.............................................................................................2 1.1 Purpose of the trade copier..........................................................................................................2 1.2 Licence........................................................................................................................................2 2. Installing and running the Personal Trade Copier..............................................................................3 2.1 Installing the trade copier............................................................................................................3 2.2 Running the sender......................................................................................................................3 2.3 Running the receiver....................................................................................................................4 2.4 Multiple senders and receivers....................................................................................................4 2.5 Testing the trade copier...............................................................................................................5 3. How the Personal Trade Copier works..............................................................................................6 3.1 Trade placement and closure.......................................................................................................6 3.2 Heartbeats....................................................................................................................................6 3.3 Pending orders.............................................................................................................................6 3.4 Lot sizing and risk.......................................................................................................................7 3.5 Broker symbol names and suffixes..............................................................................................8 3.6 Market execution.........................................................................................................................8 3.7 Hedging vs. non-hedging.............................................................................................................9 3.8 Order comments and magic numbers..........................................................................................9 3.9 Partial closes..............................................................................................................................10 3.10 Inverting trade direction..........................................................................................................10 4. EA parameters.................................................................................................................................11 4.1 Sender EA parameters...............................................................................................................11 4.2 Receiver EA parameters............................................................................................................13 4.3 Variables for use in receiver alert text.......................................................................................19 4.4 Trading-time restrictions...........................................................................................................20 5. Diagnosing problems.......................................................................................................................22
Page 1 of 22
The Personal Trade Copier duplicates trades between two copies of MetaTrader 4 running on the same computer. You place trades in one copy of MT4, and these are replicated almost instantly in the other copy of MT4. The trade copier duplicates both manual and automated trading. You can copy from multiple instances of MT4 into a single receiver, and vice versa, by running more than one copy of the sender and receiver. The sending copy of MT4 does not need the ability to place trades. Therefore, the sending copy can be logged in using the read-only MT4 investor password. MT4i can also provide tools for broadcasting messages over the internet between one master copy of MT4 and any number of receivers running anywhere in the world. Please contact us at support@mt4i.com.
1.2
Licence
Unless otherwise specified in writing by MT4i.com, this software is licensed for personal use only. You are not allowed to distribute it to other people, regardless of whether or not money is changing hands. The software is provided entirely at the users risk, and you should check it thoroughly before deploying it on computers trading real money. MT4i.com accepts no responsibility whatsoever for any loss of any kind caused by installation or use of the software.
Page 2 of 22
You need two copies of MT4 installed on the same computer. In the sending instance of MT4, you need to install the following files: Copy MT4i - TradeCopy Sender.ex4 into the experts directory. Copy MT4iQuickChannel.dll into the experts\libraries directory.
In the receiving instance of MT4, you need to install the following files: Copy MT4i - TradeCopy Receiver.ex4 into the experts directory. Copy MT4iQuickChannel.dll into the experts\libraries directory.
MT4 needs to be restarted in order for its Navigator list to update after new EAs are installed.
2.2
In the sending instance of MT4 you open a new chart for any symbol and add the MT4i - TradeCopy Sender EA to the chart, by double-clicking on it in the Navigator list or dragging it onto the chart. The EAs Allow DLL imports setting must be turned on. You do not need to run multiple copies of the EA on charts for each symbol which you trade. You should only run one copy of the sender EA, on any chart. This will duplicate all trades for all symbols. The sender EA does not need the ability to place orders. Therefore, it can be running on an account which is logged in using the read-only MT4 investor password. N.B. If the sending MT4 account is not in USD, then the MT4 Market Watch must contain the currency pair for converting to USD. For example, if the senders deposit currency is GBP or JPY, then the Market Watch must contain GBPUSD or USDJPY.
Page 3 of 22
In the receiving instance of MT4 you open a new chart for any symbol and add the MT4i TradeCopy Receiver EA to the chart, by double-clicking on it in the Navigator list or dragging it onto the chart. The EAs Allow DLL imports setting must be turned on. You do not need to run multiple copies of the EA on charts for each symbol which you trade. You should only run one copy of the receiver EA, on any chart. N.B. The Market Watch must contain all the symbols which are going to be traded. In addition, if the receiving MT4 account is not in USD, then the MT4 Market Watch must contain the currency pair for converting to USD. For example, if the receivers deposit currency is GBP or JPY, then the Market Watch must contain GBPUSD or USDJPY.
2.4
A sender and receiver are identified by a channel name, which you can control using the EAs parameters. The default channel name is MT4iTradeCopy. There should only be one sender EA and one receiver EA using a channel. A single copy of the sender EA can broadcast on multiple channels, but each receiver EA can only listen on a single channel. If you want to send trades from one copy of MT4 to 3 receiver copies of MT4, you should do the following: In the sender instance of MT4, you run one copy of the sender EA. You set the Channel parameter in the EA to a comma-separated list of the channel names which the sender should use. For example: Channel1,Channel2,Channel3. (Alternatively, you can also run three copies of the sender EA, each broadcasting on one of the channels.) In each receiver instance of MT4, you run a copy of the receiver EA and configure each one to use one of the three channels you have set up in the sender. If you want a single copy of MT4 to receive trades from 3 senders, then you should do the following:
Page 4 of 22
2.5
Once both the sender and receiver EAs are running, the receiver should shortly receive a heartbeat message from the sender and update its status on screen. Both EAs display their current status in the top-right of the chart. If no status is visible, please make sure that MT4s Expert Advisors button is turned on.
Page 5 of 22
The sender EA sends a message to the receiver EA as soon as it spots that there is a new open order in its copy of MT4. The receiver EA will then attempt to place the same trade. Transmission is more or less instant; the time taken to copy the trade should depend almost entirely on your broker(s), not on the speed of transmission between the two EAs. The same applies to trade closure. As soon as it spots that a previously open order has been closed, the sender EA tells the receiver EA to close its trade.
3.2
Heartbeats
The sender EA sends a periodic heartbeat message, every 10 seconds by default. This states which orders should still be open. If a receiver misses a trade-closure instruction, e.g. because its copy of MT4 is not running at the time, then it should close the order when it next receives a heartbeat from the sender. Changes to a trades s/l or t/p are also sent in the heartbeat message. Therefore, there may be a delay of up to 10 seconds between the s/l or t/p changing in the senders copy of MT4 and the receiver making the change. However, if the trade is closed out on the sender within those 10 seconds because the s/l or t/p is hit, that should lead to an immediate close instruction being sent to the receiver. Changes to the entry price on a pending order are also sent in the heartbeat, and therefore updated within 10 seconds.
3.3
Pending orders
By default the trade copier does not send pending orders. It only sends a message to the receiver once a pending order is filled and turns into a buy or sell order. Copying pending orders is potentially very dangerous. Let's say that you are trading the breakout of yesterday's range, and you have a buy-stop at yesterday's high. This could get triggered on the receiver without being triggered on the sender, because of slight price differences between the two
Page 6 of 22
3.4
Receivers can use any of five modes for determining what lot sizes to trade: Fixed lot size. The receiver always uses a fixed size (the UseFixedLotSize parameter) regardless of the senders lot size. Risk-based. The receiver adjusts the lot size based on the relative equity of the two accounts. For example, if the senders equity is $2000 and the receivers equity is $4000, and UseRiskFactor is set to 1.5, then the receiver will trade three times the lot size of the sender i.e. 4000 / 2000 x 1.5 = 3. Multiple. The receiver trades a multiple of the senders lot size (regardless of the equity on each account). For example, if LotSizeMultiplier is set to 2, then the receiver will trade double the senders lot size. Equity-based lot-sizing. The receiver ignores the senders lot size, and instead uses a value based solely on the receivers account equity. Balance-based lot-sizing. As above, except that the account balance is used instead of account equity. These settings are in order of priority. If UseFixedLotSize is non-zero, then the receiver will use a fixed lot size. Or if UseRiskFactor is non-zero, then it will use equity-based sizing. Or if LotSizeMultiplier is non-zero, then the receiver will trade a simple multiple of the senders lot size. Of if EquityPerLot is non-zero, then the receiver will trade a lot size based on its account equity, ignoring the senders lot size. And if all these are zero, then the receiver will trade a lot size based on its account balance using BalancePerLot.
Page 7 of 22
The default setting is risk-based lot sizing (with UseRiskFactor = 1). The receiver will trade the equivalent of the senders lot size given the different equity on the two accounts. In addition, you can modify the signals which are issued. The sender EA can be configured always to send a fixed lot size, regardless of what has actually been traded, or a multiple of the actual lot size. You can also modify the s/l and t/p which are used on orders: the sender can be configured to hide or change the real s/l and t/p, and the receiver has options for overriding the s/l and t/p with a maximum value in order to limit risk. The receiver EA also has a StopTradingBelowEquity setting which can be used to terminate all copying activity if the equity on the account becomes dangerously low, plus MaxOpenOrders_Total and MaxOpenOrders_FromCopier settings for controlling the number of concurrent open orders.
3.5
Some MT4 brokers use different suffixes for the same symbol. For example, some brokers may refer to EURUSD as EURUSDFXF, EURUSDcx, EURUSDi, EURUSDm etc. The sender and receiver should automatically adjust between different symbol names on different brokers. If the receiver is unable to place a trade then it is probably because the symbol is not in its Market Watch. (The receiver EA does have a ForexSymbolSuffix parameter, but the receiver will auto-detect this if the parameter is left blank.) Some non-forex symbols need special mapping. For example, most MT4 brokers refer to spot gold as XAUUSD, but there are a few brokers who use a different symbol name such as GOLD. You can use the receiver EAs CustomSymbolMappings parameter to translate any such symbols. For example, if the sending accounts broker uses GOLD and the receiving accounts broker uses XAUUSD, then you would enter GOLD=XAUUSD in the CustomSymbolMappings parameter.
3.6
Market execution
Some brokers use market execution where an s/l or t/p has to be placed separately from a buy or sell order. The receiver caters for this by always placing the trade first, and then setting any s/l and t/p
Page 8 of 22
3.7
At the moment the trade copier does not convert between hedging and non-hedging accounts. If the receiver is running on a broker which does not allow hedging, then trades will fail if the messages coming from the sender break the hedging rules.
3.8
The trade copier uses order comments to track orders on the receiver. Therefore, it does not duplicate the original order comment from the sending copy of MT4. The receiver also uses an orders magic number to identify which orders belong to it, versus which orders are from manual trading or other EAs running on the account. Therefore, magic numbers are also not copied from the sender account. The receiver EA uses the same magic number for all orders which it processes. By default, it automatically selects a magic number based on the channel name. You can choose your own magic number by setting the MagicNumber parameter to something other than zero. If you trade multiple EAs on the sending copy of MT4, and you want each order in the receiving copy of MT4 to have a different magic number based on the magic number in the sending copy of MT4, then you can do the following: Run multiple copies of the sender EA, and set the IncludeMagicNumbers parameter or the IncludeOrderComments parameter so that each sender only includes the orders from one of the EAs on the account. Each sender EA must use a different channel name. Run multiple copies of the receiver EA (using the same channel names as in the sender EA). You can either leave the receivers MagicNumber parameters set to zero, in which case the magic numbers will be different for each channel but will not match the sending copy of MT4, or you can configure each receiver to use the same magic number which is being used in the corresponding sender EA to filter the orders on the channel.
Page 9 of 22
3.10 Inverting trade direction The receiver can be configured to invert the broadcasters trade direction, turning buys into sells and vice versa. (This feature has been included at user request; we are not aware of any loss-making trading system which can be made profitable by inverting it.) In order to use this feature you need to turn on the receiver EAs InvertTrades parameter, and you will also need to do one of the following: Turn on the TradeAllOrdersAtMarket parameter. This means that the receiver ignores the senders entry price (because e.g. the sender is buying at the ask price whereas the receiver will be selling at the bid price). Increase the AllowSlippagePips parameter, to cater for the fact that the difference between the senders entry price and the receivers entry price will be at least the size of the spread.
Page 10 of 22
Server settings Channel The channel name(s) to use for communicating with the receiver(s). There should only be one receiver and one sender on each channel. A single sender EA can broadcast on multiple channels, which you specify by entering a commaseparated list of names in the Channel parameter, e.g. Scalp1,Scalp2,Scalp3. Channel names must not contain any of the following characters: / \ : * ? < > | HeartbeatPeriodSeconds Orders to include IncludeSymbols If not blank, a comma-separated list of symbols to include in the messages to the receiver. This must exactly match the brokers names, including upper/lower case such as EURUSDfx,GBPUSDfx. Trades for symbols which are not on this list are not included. IncludeMagicNumbers If not blank, a comma-separated list of EA magic numbers to include in the messages to the receiver. For example, 0,1234,6789 will include manual orders (which have magic number 0), plus orders from the EA(s) which use the magic numbers 1234 and 6789 IncludeOrderComments If not blank, a comma-separated list of order comments to include. For example, pivot,breakout will only include orders whose comment includes either pivot or breakout. The match is case-sensitive. You can also match an exact order comment using quotes. For example, pivot,breakout will match an order whose comment includes pivot (e.g. pivot123), or an order whose comment is the exact text breakout. IncludePendingOrders Determines whether pending orders are sent, or whether the broadcaster only sends messages when trades are filled. The number of seconds to wait between sending each heartbeat message
Page 11 of 22
Page 12 of 22
4.2
Receiver EA parameters
Server settings Channel The channel name to use for communicating with the sender. There should only be one receiver and one sender on each channel. A receiver can only listen on a single channel; you cannot use a comma-separated list for the receivers Channel parameter. Channel names must not contain any of the following characters: / \ : * ? < > | Local settings ForexSymbolSuffix Any suffix used by the broker for forex symbols. If left blank, the EA should automatically detect any suffix which its broker uses. (For example, if the broker refers to EURUSD as EURUSDcx, then this parameter can be manually set to cx though this should not be necessary.) FuturesSymbol Symbol used by the broker as a prefix for futures. Can be ignored if you do not intend to trade/broadcast futures. The prefix is typically # for the small number of MT4 brokers who offer futures. CustomSymbolMappings A comma-separated list of symbols which need special mapping between the broadcaster and receiver accounts. For example, GOLD=XAUUSD,CRUDE_OIL=OIL will convert broadcaster trades for GOLD into receiver trades for XAUUSD, and broadcaster trades for CRUDE_OIL into receiver trades for OIL. If the receiving broker uses a suffix such as cx, then this does need to be included in the mapping: e.g.
Page 13 of 22
Page 14 of 22
Page 15 of 22
Page 16 of 22
Page 17 of 22
Page 18 of 22
4.3
You can control the text which is displayed by the receiver on screen or sent by email. The following variables can be used in the alert text parameters such as OrderOpen_ScreenAlertText: Variable {CHANNEL} {ACC} {TICKET} {SYMBOL} {LOTS} {OPENTIME} {OPENPRICE} Description The name of the channel which the EA is receiving messages on MT4 broker account number Broker ticket number of the receivers order Symbol of the receivers order Lot size of the receivers order Open time of the receivers order (broker time, not local or UTC) Open price of the receivers order
Page 19 of 22
4.4
Trading-time restrictions
The IncludeTradingTimes parameter in the receiver EA lets you control the timesof day when the receiver is allowed to place trades. Any incoming order messages outside these times will be ignored. All times are interpreted as broker time, not local time.
Page 20 of 22
19:20-19:25 Only allow trading between 7.20pm and 7.25pm Any number of these settings can then be combined as a comma-separated list (in any order). Therefore, the above examples could be combined to create a complex trading window as follows: 2:45,14,16-17:30,7:15-11,19:20-19:25
Page 21 of 22
If trades are instantly closed on the receiver Check that there is only one EA sending messages on the specified Channel.
Page 22 of 22