
01-30-2008, 05:54 AM
|
|
Senior Member
|
|
Join Date: Jun 2006
Posts: 116
|
|
I was only trading one pair.
Quote:
Originally Posted by wolfe
Cijas,
Could you post the statement to look at? Also, post the trade journal. Were there any errors in the journal?
I'm not too concerned with when your Next_Trade was hit. Next_Trade will execute when current price is >= (greater than, or equal to) your last open + Next_Trade for buys, or <= your last open - Next_Trade for sells. There could be many situations that you won't see your Next_Trade execute exactly on your set parameter. The EA is coded so when your Next_Trade situation is met (could be > for buys, or < for sells) to fire an Ordersend() command. If the server context is busy, re-quoting in a fast moving market, or not responding, the EA will try up to 5 times to put your order through. When the order finally does go through, you may or may not be EXACTLY on your Next_Trade price. GBPJPY with it's high spread, and fast moving volitility, makes it a good candidate NOT to land it's Next_Trade exactly where desired.
A little more concerning to me is why ALL orders didn't close when your 1% TP was met. Out of curiosity, what does 1% work out to.
The EA closes orders by identifying them by their magic number, it doesn't just close ALL open orders because you may have EA attached to more than 1 chart. Each currency pair is assigned it's own magic number for this purpose. In v1_5 (currently working on) I will try to address this issue.
What happened to you is all the orders didn't close, only one did. Then the EA looked at the last order placed (0.2) and when the conditions were met is added to that (0.3). In the next version I will put in some more fail safe measures to try and fix this problem.
|
Hi wolfe,
I was only trading GBPJPY contrary to what you thought.
These are my log and a screenshot.
Last edited by Cijas; 01-30-2008 at 05:59 AM.
|