Welcome to Forex-TSD!, one of the largest Forex forums worldwide, where you will be able to find the most complete and reliable Forex information imaginable.
From the list below, select the forum that you want to visit and register to post, as many times you want. It’s absolutely free. Click here for registering on Forex-TSD.
Exclusive Forum
The Exclusive Forum is the only paid section. Once you subscribe, you will get free access to real cutting-edge Trading Systems (automated and not), Indicators, Signals, Articles, etc., that will help and guide you, in ways that you could only imagine, with your Forex trading.
Elite Section
Get access to private discussions, specialized support, indicators and trading systems reported every week.
Advanced Elite Section
For professional traders, trading system developers and any other member who may need to use and/or convert, the most cutting-edge exclusive indicators and trading systems for MT4 and MT5.
i' am testing mode 3, can i suppose that these errors limits EA's performance ?
do you think we must correts errors before attach EA on live-account?
Of course, you should not use beta version on live account. _06 is beta version. Well, at least I wouldn't...
Actually we are still on the development road for our first stable version as far as I know.
A very wild guess: I seem to recall seeing somewhere that Alpari handles Sunday bars differently than FXDD. You might want to visually compare the price plots in both platforms, and especially compare the Sunday bars.
With MT I'll assume that you'll also want to test and optimize using the platform that you'll be trading with.
I haven't verified that what you are saying is true, but my gut honestly tells me the same thing. The PhoenixFund has IB approval, working on paperwork now. When that is done, I hope to make historic data available from that broker. We should backtest, optimize, forward test and trade all using the same data.
Of course, you should not use beta version on live account. _06 is beta version. Well, at least I wouldn't...
Actually we are still on the development road for our first stable version as far as I know.
Mario
THat is correct, still trying to make a stable version. I do think that this is an "innocent error" - meaning we have an error but it isn't hurting the actual performance of the EA.
Invalid Stops and Error #1 I have confirmed that the EA is attempting to set the same settings again. That is a bug and needless chatter with the broker, but shouldn't affect your actual trades.
Looking at the bugs in 5.6.4 and 5.6.3 for mode 3 that *do* affect your actual trades, I would highly recommend 5.6.6 for Mode 3. 5.6.4 and 5.6.3 mode 1 are identical. 5.6.6 changes the trading logic slightly for Mode 1 or Mode 2, in an attempt (and possibly met with moderate success) to make the trading more reliable. Some backtests have slightly lower or much higher profit levels, but the main goal was to make the EA more consistent with its trades.
Has anyone been able to get the errors listed above in 5.6.6 with their backtested data? I might have an easy fix if the answer is no, but it will take live trade debugging to verify it.
Two demo accounts one IBFX. the other FXDD...
Two image to day... look carefully... 10h00 gmt
Where is the truth ????
Add at that, local electricity is between 105 and 115 v (sometimes more ! sometimes les ! Or not at all during 2 hours) Server response is between 25 and 305 ms (sometimes no response between 2,3 4, 5 seconds !) frequency 48/52 hz.....
No ! No ! I will try now...golf : a ball and an hole... Tiger Woods earned 69 millions $ in 2005... I have my chance !!! (joking!)
someone mentioned a text editor that is user friendly for matching up parenthesis etc when writing code. Does anyone remember what the software and where the download is?
THat is correct, still trying to make a stable version. I do think that this is an "innocent error" - meaning we have an error but it isn't hurting the actual performance of the EA.
Invalid Stops and Error #1 I have confirmed that the EA is attempting to set the same settings again. That is a bug and needless chatter with the broker, but shouldn't affect your actual trades.
Looking at the bugs in 5.6.4 and 5.6.3 for mode 3 that *do* affect your actual trades, I would highly recommend 5.6.6 for Mode 3. 5.6.4 and 5.6.3 mode 1 are identical. 5.6.6 changes the trading logic slightly for Mode 1 or Mode 2, in an attempt (and possibly met with moderate success) to make the trading more reliable. Some backtests have slightly lower or much higher profit levels, but the main goal was to make the EA more consistent with its trades.
Has anyone been able to get the errors listed above in 5.6.6 with their backtested data? I might have an easy fix if the answer is no, but it will take live trade debugging to verify it.
This error is happening in Mode 3. I have Mode 3 on two pairs but only one is generating errors. Is this error because of adjusting Stop Sell (S/L) point? In that case it makes sense that I have error only on one pair, because on another one I don't have enough profit for changing Stop Sell order.
Mario
Last edited by alamanjani; 12-05-2006 at 02:59 AM.
I don't know why, but this is an example of 5.6.06 setting sl to breakeven (152.99) and then 1 second later, resetting s/l to 143.51. Something is triggering a double OrderModify call with the 2nd call having bad data.
2006.12.05 11:27:51 '332005': order #6331108 buy 0.10 EURJPY at 152.9900 was modified -> sl: 143.5100 tp: 154.0400
2006.12.05 11:27:51 '332005': request in process
2006.12.05 11:27:51 '332005': request was accepted by server
2006.12.05 11:27:51 '332005': modify order #6331108 buy 0.10 EURJPY at 152.9900 sl: 152.9900 tp: 154.0400 -> sl: 143.5100 tp: 154.0400
2006.12.05 11:27:50 '332005': order #6331108 buy 0.10 EURJPY at 152.9900 was modified -> sl: 152.9900 tp: 154.0400
2006.12.05 11:27:50 '332005': request in process
2006.12.05 11:27:50 '332005': request was accepted by server
2006.12.05 11:27:50 '332005': modify order #6331108 buy 0.10 EURJPY at 152.9900 sl: 143.5100 tp: 154.0400 -> sl: 152.9900 tp: 154.0400
The OrderModify - Error # 1 is stopped by changing this code:
Linear Mode
