Posts made by fxDreema

За всеки случай ето ти една таблица с правила: http://book.mql4.com/appendix/limits

И малко от моите логове. Явно някой път успява да отвори поръчка, друг път не. Това дето не успява да модифицира стоповете е по-приемливо, докато изпрати данните на сървъра и условията се променят, но после следва нов опит така или иначе.

__
21:54:57.935 '561917': order was opened : #176340514 sell stop 0.01 EURUSD at 1.39041 sl: 0.00000 tp: 1.39031
21:54:58.091 '561917': modify pending order #176340084 buy stop 0.01 EURUSD at 1.39082 sl: 0.00000 tp: 1.39092 -> price: 1.39060 sl: 0.00000 tp: 1.39070
21:54:58.207 '561917': modification of pending order #176340084 buy stop 0.01 EURUSD at 1.39082 sl: 0.00000 tp: 1.39092 -> price: 1.39060 sl: 0.00000 tp: 1.39070 failed [Trade is disabled]
21:54:58.209 '561917': modify pending order #176340514 sell stop 0.01 EURUSD at 1.39041 sl: 0.00000 tp: 1.39031 -> price: 1.39042 sl: 0.00000 tp: 1.39032
21:54:58.363 '561917': request was accepted by server
21:54:58.523 '561917': request in process
21:54:58.541 '561917': pending order #176340514 sell stop 0.01 EURUSD was modified -> price: 1.39042 sl: 0.00000 tp: 1.39032
21:54:58.646 '561917': modify pending order #176340084 buy stop 0.01 EURUSD at 1.39082 sl: 0.00000 tp: 1.39092 -> price: 1.39058 sl: 0.00000 tp: 1.39068
21:54:58.724 '561917': modification of pending order #176340084 buy stop 0.01 EURUSD at 1.39082 sl: 0.00000 tp: 1.39092 -> price: 1.39058 sl: 0.00000 tp: 1.39068 failed [Trade is disabled]
21:54:58.726 '561917': pending order sell stop 0.01 EURUSD at 1.39042 sl: 0.00000 tp: 1.39032
21:54:58.847 '561917': order sell stop 0.01 EURUSD opening at 1.39042 sl: 0.00000 tp: 1.39032 failed [Invalid S/L or T/P]
21:54:58.849 '561917': pending order sell stop 0.01 EURUSD at 1.39042 sl: 0.00000 tp: 1.39032
21:54:58.958 '561917': order sell stop 0.01 EURUSD opening at 1.39042 sl: 0.00000 tp: 1.39032 failed [Invalid S/L or T/P]
21:55:02.127 '561917': pending order sell stop 0.01 EURUSD at 1.39042 sl: 0.00000 tp: 1.39032
21:55:02.248 '561917': request was accepted by server
21:55:02.507 '561917': request in process
21:55:02.650 '561917': order was opened : #176340519 sell stop 0.01 EURUSD at 1.39042 sl: 0.00000 tp: 1.39032
21:55:02.822 '561917': modify pending order #176340084 buy stop 0.01 EURUSD at 1.39082 sl: 0.00000 tp: 1.39092 -> price: 1.39058 sl: 0.00000 tp: 1.39068
21:55:03.046 '561917': modification of pending order #176340084 buy stop 0.01 EURUSD at 1.39082 sl: 0.00000 tp: 1.39092 -> price: 1.39058 sl: 0.00000 tp: 1.39068 failed [Trade is disabled]
21:55:03.048 '561917': pending order sell stop 0.01 EURUSD at 1.39041 sl: 0.00000 tp: 1.39031
21:55:03.105 '561917': order sell stop 0.01 EURUSD opening at 1.39041 sl: 0.00000 tp: 1.39031 failed [Invalid S/L or T/P]
21:55:06.617 '561917': pending order sell stop 0.01 EURUSD at 1.39041 sl: 0.00000 tp: 1.39031
21:55:06.738 '561917': request was accepted by server
21:55:07.076 '561917': request in process
[/quote:3jndgwbe]

Пф, то пък се оказа че сме края на петък, и аз чакам да ми зацепи експерта отново. Явно процедурата ще се отложи
Иначе спреда ти колко е? И freeze level-a, ама едва ли си го знаеш

А може и да говоря глупости, проблема явно е при отварянето на нов ордер, а аз си мисля че е при модифицирането. Явно трябва да го проуча повече. Честно казано не съм голям специалист по скалперските експерти, твърде бързо и на дребно ми се случват неща
Ако все пак достигнеш до някакъв извод или намериш начин да се предизвика грешката умишлено - пиши.

If you think that this is quickly... I'm not forcing myself to answer as soon as possible lately, I can delay it for hours, but also I don't like to have too many pending questions.

That close trades block will pass anyway, even if there is nothing closed. It's there to clear the Sell before going to Buy and clear the Buy before going to Sell. It's because something should close those trades, they have no SL and no TP. Well, this is the example I give, this is the general example of buy-sell-buy-sell on reverse situations, if you know what I mean.

This?
http://fxdreema.com/shared/8oILfIjme

Or this? (here the difference is in blocks 2 and 9, crossover is used)
http://fxdreema.com/shared/xnSLoRu9b

In the first example it happens very often to have Stochastic and RSI overbought/oversold and in the same time Close[0] to be beyond the half of the previous candle. Sometimes it's beyond the half of candle 2. It looks better in the second example where we wait for a crossover.

Малко е сложно за обяснение. Направил съм го така че когато получи грешка при някой опит за отваряне/редактиране/затваряне и тази грешка има шанс да е временна, да опита отново на следващия тик... докато успее. Само че в случая опитва с едни и същи данни всеки път и затова зацикля. Сега защо данните са грешни трябва да проуча малко, може нещо кода да е бъгав или да не му достига някоя проверка, ама за всеки случай май не е много добра идея за правиш трейлинг стоп на толкова поръчки толкова често. Аз пробвах този експерт и в даден момент започва да ми дава грешки Trading is not allowed, предполагам от брокера или от МТ се активира някаква временна забрана. С виртуални стопове дали би станало?

You want to do something like this? http://fxdreema.com/shared/83jLbqm8c
Well, I used MAs here, but the idea is to buy-sell-buy-sell when conditions reverse (in this case when MAs cross).

Notice that indicators are moving in the current candle, and what to say about Candle Close. it's not impossible to have Close>Indicator at certain time and few seconds later to be Close<Indicator... and Close>Indicator again... and Close<Indicator again and again.

Is the problem that trades are closed too early, maybe because the conditions connected before "Close trades" are happen to be all true in a time when "Close trades" must not be executed?

In above posts it was not buying, now it's buying... what is the exact problem now?

So you have to determine the lowest low and then figure out where it is the previous and next low around it? I think we are going too deep here, an EA can check some basic things and do some basic calculations, but for special calculations they created indicators. So I can suggest to find some indicator.
By the way some people are working with ZigZag (I don't know why, I don't like it) and I added some calculations to get it's Xth top/low. Find it in the list of built in indicators. It is a custom indicator, but it comes with MT so it's almost built in

Well, if you know when to modify stops they can be modified. "For each Trade -> modify stops" like here: http://fxdreema.com/demo/mt4-loop-how-it-works Read the description of "For each Trade" for more information about these pink blocks, because so many people just don't get it and I don't think that this is rocket science.
This is only for how to modify stops of trades. Inside "For each Trade" there are filter settings to choose which trades to work with.

More specific details?

Yes, it looks that it does not work

If all candles[n] are between 0 and 10 pips it will pass, if one of them fails - does not pass. But they can be only bulls forming nice uptrend and if each one is less than 10 pips the uptrend does not matter.

If they are values like 30 and 70, they are exactly that - 30 and 70.
If you work with RSI, if a single RSI value from the last N candles is lower than 30 or above 70, the block fails. The same is if andle size is used, if that candle size for that particular candle ID is lower or above the limits - the block fails. So the block will pass if all candles are small enough if you look at them as independent candles, which also means that the block will pass if you have N small candles in strong trend. Just check both methods and you will see the difference.

It's not the same thing, it's similar but not the same
"Indicator moves within limits" check for N candles if the indicator is between Upper and Lower level:

• candle 0: indicator[0] < upper level and indicator[0] > lower level ?
• candle 1: indicator[1] < upper level and indicator[0] > lower level ?
  ...
• candle N: indicator[N] < upper level and indicator[N] > lower level ?

when you have candle total size instead of indicator... what you check is each one candle independently. This is not like knowing what is the highest and lowest value of all N candles.

But if you can work with timeframe x10 it will be even better and faster.

No, but i think this is not what you need. Look here: http://fxdreema.com/shared/zwNkkDvob
On the left side is using that block, but it checks each candle alone for past 10 candles.
On the right side I calculate the difference between the highest and lowest value from the last 10 candles, and then I check if that difference is lower than some value (0.0010).

Aaah this line comes from the past, so candle ID should be at least 26. When I'm looking at this particular indicator I'm like
For the other thing, maybe "Indicator moves within limits" block? I remember that we had a discussion about this block in the past with somebody, you can search for it in the forum.

This is maybe the only indicator that draws something in the "future". Normally you want to get some value from the current candle or from older candle knowing the candle ID. 0 is the current candle, 1 is the previous one and so on. To get something from the future try negative value for Candle ID, something like -26