I just need it to set the trade and then make sure a TP and SL sets.
Last edited by aagarcia; 04-29-2010 at 19:57.
Has anyone done any backtesting on other pairs?.
The issue that aagarcia refers to is one of the EA not testing error return codes after submitting the order to the server. Due to the high speed execution ATC offers for scalpers and grid traders, ATC uses a one second "Too Frequent Request" option to deter pipsers and cheaters. Any consecutive modify of an order in less than one second will result in a rejection of the modify. When the EA is not reading the return codes, it can never come to know this and may attempt the modify next tick.
This error process lets ATC support a very tight Freeze/SL of only a single, fixed, one Pip value and still support tight scalping and grid trading.
MQ Recommended error managements can be found here Here
The MtServer is a per-transaction, telnet based server and requires at least moderate error management. While it appears relatively simple on the surface, making a well designed, error tolerant EA which will work well across all brokers, is a learning process, where access to a Metaquotes server makes this task considerably easier to see, test and understand.
If you would like error control tossed into the EA, let me know, I'd be glad to help out. (Shame on Zapper)
ATC also supports 3 part integrated orders on their ECN, so it's not essential to select the ECN option in order to trade the xbars on ATC, which means the SL/TP will post with the main order, not after.
Mt4 traders, Comcast and others are inserting resets into your TCP, causing slippage.
WARNING - to Comcast customers
J have heard it is a very good ea