Diskussion | HitAndRun | Kaufen Sie Handelsroboter (Expert Advisor) für den MetaTrader 4

Catalin Zachiu 2019.06.27 10:11 #1

26.06.2019 on usd/jpy , closed by Macd .

Dateien:

Screenshot_20190627-105933.png 633 kb

steinermar 2019.10.07 23:28 #2

Do you have special Settings for the three pairs?

Catalin Zachiu 2019.10.08 05:05 #3

steinermar:
Do you have special Settings for the three pairs?

No , they are all the same , the ideea is to use small stops and the closing I leave to the user's choice . Closing by Macd should give the greater possible profit , but it is more rare . Closing after bars would be with smaller profit but more often and with trail stop the profit would be even smaller than closing after bars but more often than closing after bars .

Catalin Zachiu 2019.10.08 07:19 #4

On the recovery settings , set Jump_Size to 0 for Eur/Usd and leave it to 100 on the other pairs if you use the recovery function .

steinermar 2019.10.08 20:28 #5

I tested with the default settings. the result ist not good. how can i optimise? what ist the meaning of the different settings? How can i activate them? Do you have an explanation? It's my first EA.

Catalin Zachiu 2019.10.08 21:20 #6

steinermar:

I tested with the default settings. the result ist not good. how can i optimise? what ist the meaning of the different settings? How can i activate them? Do you have an explanation? It's my first EA.

You have response in P.M.

Catalin Zachiu 2019.11.25 09:57 #7

Here are SET files of a few combinations that might be used with the EA :

Dateien:

Hit_And_Run_Set_Files.zip 9 kb

Catalin Zachiu 2019.12.03 11:20 #8

Closed by Macd , Usd/Jpy .

Dateien:

Screenshot_20191203-121737.png 690 kb

Mateusz Gora 2019.12.19 12:46 #9

Hi, I have a problem with your EA. It does not remove previous sell stop orders, so I end up with two of them and i have to close them manually. Could you fix this bug, please. I really like this EA for its simplicity and I would like to use it on real account, but with this bug i can't. Also close by macd seems to not work, but this isn't confirmed yet. Thanx

Dateien:

hitandrun.jpg 326 kb

Catalin Zachiu 2019.12.19 14:00 #10

Mateusz Gora:

Hi, I have a problem with your EA. It does not remove previous sell stop orders, so I end up with two of them and i have to close them manually. Could you fix this bug, please. I really like this EA for its simplicity and I would like to use it on real account, but with this bug i can't. Also close by macd seems to not work, but this isn't confirmed yet. Thanx

What version of the EA do you have , that bug was resolved from version 1.7 , now it's 2.2 . If your EA is updated please check the magic numbers of the two orders.

Catalin Zachiu 2019.12.19 14:10 #11

Mateusz Gora

The closing by Macd has a delay (Macd_Offset) so that the order will not be closed on the same bar it opened . I have put the default delay at 3 , so if the Macd closing condition is met , the order will close only after 3 bars have passed after the order was opened .

Mateusz Gora 2019.12.19 22:47 #12

Catalin Zachiu:

What version of the EA do you have , that bug was resolved from version 1.7 , now it's 2.2 . If your EA is updated please check the magic numbers of the two orders.

I've used version 2.1. I have now updated to 2.2. Magic numbers on these two orders are different. What should I do? I've changed magic numbers on each pair the EA trades. Is it correct? Will this help?

Catalin Zachiu 2019.12.20 03:48 #13

Mateusz Gora:

I've used version 2.1. I have now updated to 2.2. Magic numbers on these two orders are different. What should I do? I've changed magic numbers on each pair the EA trades. Is it correct? Will this help?

The orders are selected by symbol and magic , so it should be better , but it should have worked even using the same magic on different symbols . I think that either a sudden system restart changed or reset the magic number , or you changed it and forgot to delete the remaining pending order , or ...the broker did it .

Hung Phi Le 2019.12.20 05:15 #14

Catalin Zachiu:
The orders are selected by symbol and magic , so it should be better , but it should have worked even using the same magic on different symbols . I think that either a sudden system restart changed or reset the magic number , or you changed it and forgot to delete the remaining pending order , or ...the broker did it RW

What the "Magic Number" mean, sir ?

Hung Phi Le 2019.12.20 05:24 #15

How to update the new EA version ?

Catalin Zachiu 2019.12.20 05:50 #16

Hung Phi Le:
How to update the new EA version ?

Access Mt4 Terminal --> Market --> Purchased.

Catalin Zachiu 2019.12.20 06:18 #17

Hung Phi Le:

What the "Magic Number" mean, sir ?

It is a number atributed to an EA to identify it's orders . So if you want to use the same EA on the same symbol but with different settings you must assign different magic numbers to each EA . Like this , each EA identifies it's orders by the Magic Number so that the orders don't get mixed up .

Hung Phi Le 2019.12.20 09:04 #18

Catalin Zachiu:
It is a number atributed to an EA to identify it's orders . So if you want to use the same EA on the same symbol but with different settings you must assign different magic numbers to each EA . Like this , each EA identifies it's orders by the Magic Number so that the orders don't get mixed up .

At my MT4, I saw Magic of EURUSD, GBPUSD & USDJPY is the same ? Do I need to change them ?

Catalin Zachiu 2019.12.20 10:13 #19

Hung Phi Le:
At my MT4, I saw Magic of EURUSD, GBPUSD & USDJPY is the same ? Do I need to change them ?

No , only if you want to use the EA on the same symbol twice or more , for example , once on eur/usd h1 timeframe , and a second time on eur/usd h4 timeframe . Or on the same timeframe , but with different settings. As long as you use it only once per symbol there is no need to change the magic.

Mateusz Gora 2019.12.23 17:24 #20

Hi. It looks like version 2.2 calculates position size incorrectly. It cuts position in halve. For instance, for risk 1% it opens position 0.5% and for 0.5% it opens 0.25% and so on. Version 2.1 woes good. Do you have the same?