Trade Copy

Thank you very much for the update. I will try the new versions.

So far I took three trades on MT4 and the trades received on MT5 almost perfectly matched in time and prices. Plus nothing was reported in the Experts logs and all actions by the receiver were reported in the Journal so everything seems to be working perfectly. Thanks again.

funchi wrote: Wed Jul 22, 2026 9:46 am It turned out to be a bug in the system. I sincerely apologise for the inconvenience.

There was no issue when an order was placed with the SL and TP set at the same time. However, a bug occurred when an order was placed without an SL or TP, i.e. when using One-Click Trading.

I have now fixed the bug in the MT5 and MT4 receiver EAs.

Thanks Master Funch for your time and valuable contributions to this community.

When attaching the EA in my MT5 terminal I am getting this error:
2026.07.23 12:49:32.186 MQL5 your CPU architecture does not allow to run the file 'Trade_copy_des.ex5': AVX2 required, you have AVX only

I don't have the source to change the AVX2 and compile it again.

Stay blessed always.

This is the AVX version.

Thanks Master Funchi
I have attached
Source EA on MT4
Destination Legacy EA on MT5 (now its working fine)

The trade was copied but this error message popped up 2026.07.24 00:27:59.504 Trade_copy_des_legacy (DE40,M5) CTrade::OrderSend: market buy 1.00 DE40 [timeout]
2026.07.24 00:27:59.504 Trade_copy_des_legacy (DE40,M5) Alert: error : compare_and_orderSend_positions OrderSend code=4756

Also is there a way to vary the entry price on the destination by a ceratain pips or percentage

Thanks again and stay blessed.

mazibee wrote: Fri Jul 24, 2026 9:41 am Thanks Master Funchi
I have attached
Source EA on MT4
Destination Legacy EA on MT5 (now its working fine)

The trade was copied but this error message popped up
error.png

2026.07.24 00:27:59.504 Trade_copy_des_legacy (DE40,M5) CTrade::OrderSend: market buy 1.00 DE40 [timeout]
2026.07.24 00:27:59.504 Trade_copy_des_legacy (DE40,M5) Alert: error : compare_and_orderSend_positions OrderSend code=4756

Also is there a way to vary the entry price on the destination by a ceratain pips or percentage

Thanks again and stay blessed.

Only market orders are supported.

There are no plans to support pending orders or to implement a mechanism within this tool that replicates the behaviour of pending orders.

funchi wrote: Fri Jul 24, 2026 5:39 pm Only market orders are supported.

There are no plans to support pending orders or to implement a mechanism within this tool that replicates the behaviour of pending orders.

Thanks Master Funchi

“TradeCopier_Master” and “TradeCopier_Client” are used to copy trades between PCs within a local network.
Their operating specifications are almost the same as “Trade_copy_src” and “Trade_copy_des”.

However, I have only tested them on the same PC. I have not tested operation between different PCs. If you encounter any problems, please let me know.

Overview

　　Copies trades to another account.
　　For use on a local network.

Operating Environment

　　Works with both MT5 and MT4.

Overview of Operation

　　The source and destination EAs associate trade copies using the “Pairing ID” parameter.
　　Trades from one source account can be copied to multiple destination accounts.
　　The source EA allows multiple Magic Numbers to be specified as copy targets.

Operating Conditions / Limitations

　　Limited to use within a local network.
　　Hedging mode only; Netting mode is not supported.
　　Market orders only; pending orders are not supported.
　　Full position closures only; partial closures are not supported and have not been tested.
　　If you are setting up a complex trade-copying configuration, please include details of your configuration when asking questions.

Detailed Operating Specifications

　　Trades to be copied

　　　　New orders
　　　　　　Copies market orders, SL and TP.

　　　　Order modifications
　　　　　　Modifies SL and TP.

　　　　Closing orders
　　　　　　Any order on the destination that does not exist on the source will be closed.
　　　　　　Full position closures only. Partial closures are not supported and have not been tested.

　　　　Magic Numbers
　　　　　　The Magic Numbers specified in the parameters are copied.
　　　　　　Multiple Magic Numbers can be specified.

　　　　Ignore new orders older than X seconds.
　　　　　　Specifies whether trades that have been open for a certain amount of time since execution should be copied.
　　　　　　This determines whether trades are copied retrospectively.
　　　　　　The value is specified in seconds.

　　Destination behaviour

　　　　Magic Numbers
　　　　　　Operates using the configured Magic Numbers.

　　　　User intervention
　　　　　　A closing order made manually on the destination remains closed and will not be copied again.
　　　　　　If an order on the destination is manually modified, it will be changed back to match the source order.
　　　　　　A new order on the destination that does not exist on the source will be closed. (If the Magic Number is different, it is not affected.)

　　　　Lot size
　　　　　　As a basic calculation, the lot size is calculated according to the balance ratio between the source and destination accounts.
　　　　　　It is then recalculated according to the configured conversion ratio parameter.

　　Behaviour in abnormal situations (or until both the source and destination EAs have finished starting up)

　　　　As a basic rule, source trade information is reflected on the destination even if there is a delay in operation.
　　　　However, new orders are copied according to the “Ignore new trade orders older than X seconds” parameter.

Startup Procedure

　　There is no specific order in which the source and destination should be started.

How It Works

　　Trade information is transferred over the network using TCP.
　　The “Pairing ID” parameter can be set within the range of -10000 to 10000.
　　The port used is adjusted from 49000 based on the value of the “Pairing ID” parameter.
　　Transfers are limited to PCs within the same local network. It also works between terminals on the same PC.
　　Trade information is never transferred to an external network.

Before Use
　　Windows will display a security warning window once.
　　Please allow access if you wish to continue using the software.
　　Depending on your environment, additional configuration of your router or other network equipment may be required. I cannot provide support for such network configuration.

Known Issue

If you use the EA button to switch between “Inactive” and “Active”, a message indicating that a connection cannot be established may appear at some point, after which trades can no longer be copied.
As a workaround, please restart the terminal or the EA.

Thanks for the Trade Copy EAs funchi. I read through the settings but I didn't see anything that specifically takes leverage into account. I just want to confirm for example, if source account has a $1000 balance and the leverage on the source account is 1:200 but the leverage on the receiving account is only 1:100 with a $5000 balance, I'm thinking that the Conversion Ratio is the setting to change to prevent the receiving account from opening a trade with a lot size that's too big for the 1:100 leverage. So with a Conversion Ratio = 0.5, the destination position size will be calculated based on the balance ratio and then reduced by half since the receiving account leverage is half of the sending account leverage and that will ensure that the risk on both accounts is the same. Please confirm as I just want to be sure. Thanks.

global wrote: Tue Aug 18, 2026 9:13 pm Thanks for the Trade Copy EAs funchi. I read through the settings but I didn't see anything that specifically takes leverage into account. I just want to confirm for example, if source account has a $1000 balance and the leverage on the source account is 1:200 but the leverage on the receiving account is only 1:100 with a $5000 balance, I'm thinking that the Conversion Ratio is the setting to change to prevent the receiving account from opening a trade with a lot size that's too big for the 1:100 leverage. So with a Conversion Ratio = 0.5, the destination position size will be calculated based on the balance ratio and then reduced by half since the receiving account leverage is half of the sending account leverage and that will ensure that the risk on both accounts is the same. Please confirm as I just want to be sure. Thanks.

Yes, that is correct.
With this EA, leverage does not affect the calculation of the lot size.
The lot size is basically calculated based on the balance ratio between the source and destination accounts, and is then adjusted using the Conversion Ratio.
Therefore, even if the source account has 1:200 leverage and the destination account has 1:100, the EA does not automatically adjust the lot size to account for the difference in leverage.
If you would like to take the difference in leverage into account when adjusting the lot size, you can adjust the Conversion Ratio as you wish.

Thanks for the confirmation.