You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Aagarcia, they look pretty close to being the same, except v2 has no tails and it being ex4 not able to tell code wise if they are the same or not. The top picture is v2 and the bottom is v1 with the same MaPeriod as v2.
Yeah you're right. Thanks for looking. Have you found any particular TF where it is most reliable? Are the higher TFs more accurate?
Mr. Tools, in regards to the decrease factor parameter, what if my broker can only trade .1 lots and up and I'm already trading at .1?
I like the concept though, to protect as much as possible from ranging markets, but what can I do in my particular situation. ? Any thoughts?
Thanks, great work!
Yeah you're right. Thanks for looking. Have you found any particular TF where it is most reliable? Are the higher TFs more accurate?
Mr. Tools, in regards to the decrease factor parameter, what if my broker can only trade .1 lots and up and I'm already trading at .1?
I like the concept though, to protect as much as possible from ranging markets, but what can I do in my particular situation. ? Any thoughts?
Thanks, great work!Yes the higher time frames would give you longer runs and would say they are the most accurate, but you will still have those times when the market is ranging, but would say less in the higher time frames.
About the decrease factor that's a good question, by default if after 3 losses(decrease factor) the lot size will go to the smallest lot size which in your case would be .1 lots, but maybe try it on back test starting with a larger than .10 lot size to make sure it is working that way in your case. Otherwise not sure what else to tell you.
Yes the higher time frames would give you longer runs and would say they are the most accurate, but you will still have those times when the market is ranging, but would say less in the higher time frames. About the decrease factor that's a good question, by default if after 3 losses(decrease factor) the lot size will go to the smallest lot size which in your case would be .1 lots, but maybe try it on back test starting with a larger than .10 lot size to make sure it is working that way in your case. Otherwise not sure what else to tell you.
Great, will do. Thanks so much for your input. One last question please - I saw v. 1.04 of the EA. Is the only difference between 1.04 and 1.03 the added parameters for hours and minutes?
Great, will do. Thanks so much for your input. One last question please - I saw v. 1.04 of the EA. Is the only difference between 1.04 and 1.03 the added parameters for hours and minutes?
Yes the time filter added minutes to it and on the close on Friday, changed it to a daily close.
Hello MrTools,
I did a test with the latest version on renko charts and I found the following problems. I hope you can solve them:
1. unexpected restarts with uninit reason 2 (from MQL = expert recompiled) ?
from the log file:
16:59:44 Heiken Ashi Ea_v1.04 USDJPYi,M3: deinitialized
16:59:44 Heiken Ashi Ea_v1.04 USDJPYi,M3: uninit reason 2
16:59:44 Heiken_Ashi_Smoothed_v1 USDJPYi,M3: uninit reason 1
16:59:44 Heiken_Ashi_Smoothed_v1 USDJPYi,M3: removed
16:59:45 Heiken Ashi Ea_v1.04 USDJPYi,M3: loaded successfully
16:59:45 Heiken Ashi Ea_v1.04 USDJPYi,M3: initialized
16:59:45 Heiken Ashi Ea_v1.04 USDJPYi,M3 inputs: "originally here is the default set"
16:59:46 Heiken_Ashi_Smoothed_v1 USDJPYi,M3: loaded successfully
16:59:46 Heiken_Ashi_Smoothed_v1 USDJPYi,M3: initialized
Sometimes the EA recompiles itself and restarts with the default sets for an unknown reason.
2. double order opening
from the log file:
A normal order opening with SLTP modication:
10:00:54 '2089040421': order buy market 0.10 USDJPYi sl: 0.000 tp: 0.000
10:00:55 '2089040421': request was accepted by server
10:00:55 '2089040421': request in process
10:00:55 '2089040421': order was opened : #10469228 buy 0.10 USDJPYi at 104.403 sl: 0.000 tp: 0.000
10:00:55 '2089040421': modify order #10469228 buy 0.10 USDJPYi at 104.403 sl: 0.000 tp: 0.000 -> sl: 104.302 tp: 104.452
10:00:55 '2089040421': request was accepted by server
10:00:55 '2089040421': request in process
10:00:55 '2089040421': order #10469228 buy 0.10 USDJPYi at 104.403 was modified -> sl: 104.302 tp: 104.452
double order opening:
15:36:06 '2089040421': order buy market 0.10 USDJPYi sl: 0.000 tp: 0.000
15:36:07 '2089040421': request was accepted by server
15:36:07 '2089040421': request in process
15:36:07 '2089040421': order was opened : #10472446 buy 0.10 USDJPYi at 104.480 sl: 0.000 tp: 0.000
15:36:07 '2089040421': order buy market 0.10 USDJPYi sl: 0.000 tp: 0.000
15:36:07 '2089040421': request was accepted by server
15:36:07 '2089040421': request in process
15:36:07 '2089040421': order #10472447 buy 0.10 USDJPYi at 104.478 was modified -> sl: 0.000 tp: 0.000
In this case the EA opens 2 orders simultaneously and don't set the SL and the TP for some reason.
Do you have any idea what can cause these?
Besides these annoying things the EA works very nice.
Additionally I would like to ask you to improve the TP function further if possible. Can you add partial TP levels to the EA please?
Something like:
TP1 (pips)
TP1_percent (percentage of the original order size)
TP2 (pips)
TP2_percent (percentage of the original order size)
I would like to keep the original TP function as a final TP.
Thanks for your great work. :-)
Regards,
Daniel.
Hello MrTools,
I did a test with the latest version on renko charts and I found the following problems. I hope you can solve them:
1. unexpected restarts with uninit reason 2 (from MQL = expert recompiled) ?
from the log file:
16:59:44 Heiken Ashi Ea_v1.04 USDJPYi,M3: deinitialized
16:59:44 Heiken Ashi Ea_v1.04 USDJPYi,M3: uninit reason 2
16:59:44 Heiken_Ashi_Smoothed_v1 USDJPYi,M3: uninit reason 1
16:59:44 Heiken_Ashi_Smoothed_v1 USDJPYi,M3: removed
16:59:45 Heiken Ashi Ea_v1.04 USDJPYi,M3: loaded successfully
16:59:45 Heiken Ashi Ea_v1.04 USDJPYi,M3: initialized
16:59:45 Heiken Ashi Ea_v1.04 USDJPYi,M3 inputs: "originally here is the default set"
16:59:46 Heiken_Ashi_Smoothed_v1 USDJPYi,M3: loaded successfully
16:59:46 Heiken_Ashi_Smoothed_v1 USDJPYi,M3: initialized
Sometimes the EA recompiles itself and restarts with the default sets for an unknown reason.
2. double order opening
from the log file:
A normal order opening with SLTP modication:
10:00:54 '2089040421': order buy market 0.10 USDJPYi sl: 0.000 tp: 0.000
10:00:55 '2089040421': request was accepted by server
10:00:55 '2089040421': request in process
10:00:55 '2089040421': order was opened : #10469228 buy 0.10 USDJPYi at 104.403 sl: 0.000 tp: 0.000
10:00:55 '2089040421': modify order #10469228 buy 0.10 USDJPYi at 104.403 sl: 0.000 tp: 0.000 -> sl: 104.302 tp: 104.452
10:00:55 '2089040421': request was accepted by server
10:00:55 '2089040421': request in process
10:00:55 '2089040421': order #10469228 buy 0.10 USDJPYi at 104.403 was modified -> sl: 104.302 tp: 104.452
double order opening:
15:36:06 '2089040421': order buy market 0.10 USDJPYi sl: 0.000 tp: 0.000
15:36:07 '2089040421': request was accepted by server
15:36:07 '2089040421': request in process
15:36:07 '2089040421': order was opened : #10472446 buy 0.10 USDJPYi at 104.480 sl: 0.000 tp: 0.000
15:36:07 '2089040421': order buy market 0.10 USDJPYi sl: 0.000 tp: 0.000
15:36:07 '2089040421': request was accepted by server
15:36:07 '2089040421': request in process
15:36:07 '2089040421': order #10472447 buy 0.10 USDJPYi at 104.478 was modified -> sl: 0.000 tp: 0.000
In this case the EA opens 2 orders simultaneously and don't set the SL and the TP for some reason.
Do you have any idea what can cause these?
Besides these annoying things the EA works very nice.
Additionally I would like to ask you to improve the TP function further if possible. Can you add partial TP levels to the EA please?
Something like:
TP1 (pips)
TP1_percent (percentage of the original order size)
TP2 (pips)
TP2_percent (percentage of the original order size)
I would like to keep the original TP function as a final TP.
Thanks for your great work. :-)
Regards,
Daniel.Daniel
It seems that your version of renko is having a problem. EA can not recompile itself on its own. The only thing that comes in mind (if you are not the one that recompiles the EA) is that renko generating code is sending a wrong message to the renko offline chart window (but that would be very, very complicated error). In any case, try using some other renko and see what happens then
For double orders : as far as I see the EA should be altered to have strict error checking when the orders are opened otherwise when an attempt to open an order is made that kind of problems can happen sometimes on a two consecutive ticks (or you have a serrious problem with your broker too )
Thanks for your reply mladen!
I tested on ICM demo. I will continue to monitor the EA and I will try to test it on different renko charts and brokers.
Regarding the partial TP function, can you add it to the EA please?
Regards,
Daniel.
Mr tools,
Good day!
Thank you very much, that was me on your Pm!
I will work on it!
Again, thanks a lot.
Márcio
This was in request to a PM it uses a Fast Heiken Smoothed and a Slow Heiken Smoothed this version the same as version 1.03 except the time filter is different and of course the fast/slow heiken ashi, also if desired this version has some chart comments. Also added spread protection if the spread rises above a certain level (news time most often), and if spread protection enabled the EA shouldn't open orders.You can use it as version 1.03 if you put the fast and slow settings the same.
This was in request to a PM it uses a Fast Heiken Smoothed and a Slow Heiken Smoothed this version the same as version 1.03 except the time filter is different and of course the fast/slow heiken ashi, also if desired this version has some chart comments. Also added spread protection if the spread rises above a certain level (news time most often), and if spread protection enabled the EA shouldn't open orders.You can use it as version 1.03 if you put the fast and slow settings the same.
Dear all:
I am sorry to be taking more of your time, but i am trying to set this ea with no success. I need it to run 2 hashi, one fast and the other slow, and when both are blue it buys, and when both are red, it sell. When one of them is in different collour, it closes the open trade and dont trade.
Is it possible? Could someone kindly help me?
Thanks