2. It is very useful to add more indicators, however, as I said before I will never trust in fully automated EA. However, I believe that this is a good EA as can resolve the constant problem of SL of EAs.
But I have an idea in my mind. As you quoted in
ASCTrend is a great indicator but the problem is that some of the signals are not valid. In fact, this indicator is very helpful if one avoid such invalid signals. I think it is difficult to define it in an EA (the best case will be the ASCTrend System discussed in this thread). I think one need to inspect the market with different indicators to ignore such invalid signals.
As you know EAs on MT4 works on two systems: fully automatic trades, and with manual approve. Is it possible to design something in between. I mean a fully automatic trades but with few minutes delay (asking for approve).
AscTrend set up from this post https://www.mql5.com/en/forum/173249 is working mainly on D1, and W1 timeframes so 1 minutes or half an hour delay is not a problem. We may use simple 'manual confirmation' designed in Metatrader to open any order in manual confirmation and use it as alarm, or email ... because no one will wait for 3 or 4 days without sleeping just to open one order with confirmation.
You are right: too many false signals sometimes and that is why one asctrend indicator is not enough. It is necessary to add some more indicators to the system if we want to get something profitable.
But we need to check this closing/openning on demo account first.
I think there is a bug in the EA
The only variable of ASCTrend is the Risk parameter
Although one can change it in the EA, but in action no difference in the EA behavior
On the other hand, I found that you have used two indicators in this EA: ASCTrend and ASCTrend1
Although ASCTrend1 is an essential indicator for ASCTrend, however, to avoid confusion, and finding the best conditions for ASCTrend EA, could you please modify the EA to work based on ASCTrend indicator only...
Should be one.
I also tested the other ASCTrend EA, but there was the same problem
I even edited the files of EA and indicator by putting a different RISK value, and then compile them from the beginning, but still the EA works for the default RISK 3.
What can be the reason of this problem ?
Sorry, I made a mistake
The EA uploaded in post https://www.mql5.com/en/forum/173249/page6 works fine with various RISK values
But I still have the problem to adapt the new EA developed by newdigital
I could not fix this Risk issue. I asked Igorad as this asctrend code is from him originally so he knows better (see comments inside the code in MetaEditor).
As to this EA on this post https://www.mql5.com/en/forum/173249/page6 so it is using asctrend indicator as icustom from outside (means that you must have indicator in /indicators folder).
My EA is not using any indicator from outside and that is why I could not fix it.
Hope it will be fixed soon.
I understand your situation, but I cannot understand from where this default value of RISK 3 comes, as I edited even in the EA script before compiling
I updated new 1.1 version of AsctrendBuySellExpert EA on this post https://www.mql5.com/en/forum/173249/page51
Igorad fixed the Risk.
Many thanks for this improvement. I will put it in action. I took a look at the script and found that the trading system is like the ASCTrend EA uploaded in post https://www.mql5.com/en/forum/173249/page6
As I discussed in https://www.mql5.com/en/forum/177886
there is a big problem with this trading system, as it will always open a new trade if there is no opened trade. Thus, if a trade closed manually or by TP or SL, EA will open another trade while the signal is in the same direction.
In other words, this EA works on only one condition open/close by ASCTrend