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 have been monitoring the progress of this work of art here and on the charts. I do not have consistent results to show you today, but am working on something which I can bring to the thread when ready. I am in search of a "step down feature" to add to my EA which will reduce the trade size with each loosing trade. So if you start with 5% in each trade, set max losses of 3 trades, after the first loss you are trading 4%, then 3%, etc. until you get to 0% or have reached you maximun preset consecutive losses in a row. This would allow me to run the EA for several days without worrying if it kept getting in consecutive loosing trades while I am away. Please help if you can, I think I am ready after this is added. Thanks!
B
Hey Bryan:
Is this for another Synergy EA that you have been developing? Or something unrelated? It doesn't sound too hard, but unfortunately, I have a bit much on my plate now to take on new things.
This addresses my previous issue with keeping the EA from re-entering a trade in the same direction on the same run.
Additionally, I did a lot of forward testing, watching it on various settings, and it seems to do as expected. I wish I could say I had tracked and found specific issues/bugs that will fix the various problems everyone has had, but I found little wrong with the code.
I have updated the debug logging that it does to the experts tab, which will hopefully help anyone interested in finding problems to diagnose what is going on. Certainly any of the capable programmers out there are welcome to analyze it to perhaps find any errors in the code; sometimes it just takes another set of eyes. If anyone finds anything suspicious, please post it back here.
There have also been a number of changes/updates to the OrderReliable library. I was finding a lot of errors had to do with modification order errors, so I concentrated on improvements to that library. Since this one seems to be working pretty well for me, I am hopeful others will find the same.
Also the instructions document has also been brought back to current.
As always, updated files are in post #65. You should be able to download the attached .zip file and unzip it to your platform's top folder, and everything should just fall in place. Please see the instruction manual for more installation info. And, if you haven't read the whole manual, I encourage you to do so if you really want to get any results from this EA. There are a lot of settings; fortunately, most folks will want to only enable a few at a time, but it's important you know what they all mean.
Best to you all,
-Derk
Last edited by DerkWehler; 01-25-2008 at 02:09 PM.
However, I think that PSAR should be used as one of at least 2 exit strategies, including one based on the oscillators (e.g. Stochastic and RSI fast reversing direction, but not yet crossing slow).
However, I think that PSAR should be used as one of at least 2 exit strategies, including one based on the oscillators (e.g. Stochastic and RSI fast reversing direction, but not yet crossing slow).
autumn
I could certainly add a PSAR trailing stop option. I have thought about adding it as a standard trail option for some time....
Is this for another Synergy EA that you have been developing? Or something unrelated? It doesn't sound too hard, but unfortunately, I have a bit much on my plate now to take on new things.
It would be for both. I am working on an EA and would like to try it on your Synergy EA as well. I undersand you are busy and wouldn't ask you to write it for me. I had hoped you already had such language written and stored in the archives, or could point me in the direction of someone who could help. Thanks for your time!
B
Regarding all the problems people have had with the EA: Closing orders too soon, failing to close, failing to move trailing stop, etc:
With the kind help of a programming associate, a couple of things have been discovered. First off, MT4 has bugs and cannot be trusted to do double comparisons with equality. Here is an example:
double d1, d2;
if (d1 < d2) // Works reliably
if (d1 > d2) // Works reliably
if (d1 <= d2) // FAILS (at times -when they are equal)
To get it working correctly, one has to convert to integers. In my example d1 & d2 contained prices, so we tried:
if ((d1 / Point) <= (d2 / Point))
This also failed when d1 and d2 were equal. In order to get it to work, we had to do:
if (NormalizeDouble((d1 / Point), 0) <= NormalizeDouble((d2 / Point), 0))
I have seen a bug like this more than a year ago, but hadn't realized the extent of it, or thought it Metaquotes had fixed it. So I will have to change a lot of code around to work around it. I think right now we are mostly seeing its effects in the trailing stop code.
Another matter we both saw at the same time on the same broker, was that the function IsConnected(), which checks if you are connected with your broker, failed. It was reporting false on FXDD, when in fact it was surely connected. The OrderReliable library uses this function to figure out how to approach getting the order sent.
REQUEST: Anyone who experiences problems with the EA; if it fails to open or close or modify orders, can you keep an eye on your experts tab and let me know if you see "not connected" errors being reported from the OrderReliable library? Do not bother if you use FXDD, we already know that has problems. I want to know if there are problem with other brokers or if it was somehow just FXDD.
Thank you and I'll let you know when there is a fix available.
It is looking increasingly like most if not all problems with Synergy are related to MT4 bugs. I am devising workarounds now. I'll test them for a couple days, and if they seem to be working, I will make a new release.
Regarding all the problems people have had with the EA: Closing orders too soon, failing to close, failing to move trailing stop, etc:
With the kind help of a programming associate, a couple of things have been discovered. First off, MT4 has bugs and cannot be trusted to do double comparisons with equality. Here is an example:
double d1, d2;
if (d1 < d2) // Works reliably
if (d1 > d2) // Works reliably
if (d1 <= d2) // FAILS (at times -when they are equal)
To get it working correctly, one has to convert to integers. In my example d1 & d2 contained prices, so we tried:
if ((d1 / Point) <= (d2 / Point))
This also failed when d1 and d2 were equal. In order to get it to work, we had to do:
if (NormalizeDouble((d1 / Point), 0) <= NormalizeDouble((d2 / Point), 0))
I have seen a bug like this more than a year ago, but hadn't realized the extent of it, or thought it Metaquotes had fixed it. So I will have to change a lot of code around to work around it. I think right now we are mostly seeing its effects in the trailing stop code.
Another matter we both saw at the same time on the same broker, was that the function IsConnected(), which checks if you are connected with your broker, failed. It was reporting false on FXDD, when in fact it was surely connected. The OrderReliable library uses this function to figure out how to approach getting the order sent.
REQUEST: Anyone who experiences problems with the EA; if it fails to open or close or modify orders, can you keep an eye on your experts tab and let me know if you see "not connected" errors being reported from the OrderReliable library? Do not bother if you use FXDD, we already know that has problems. I want to know if there are problem with other brokers or if it was somehow just FXDD.
Thank you and I'll let you know when there is a fix available.
-Derk
THANK GOD SOMEONE ELSE HAS SEEN THIS!!!!
<rant> I've been kicked off of the MQL forums, under a different nik, for screaming about this for months. Metaquotes said I was full of it.
Now maybe if more coders out there can speak up on this, MAYBE, they'll listen.
Linear Mode
