Posts made by fxDreema

Видях че на сървъра часовника беше с един ден напред и го върнах, то пък станаха странни неща във форума. Иначе за trailing take profit отдавна са питали, ама все ме мързи да го направя

There is a block "Check current unrealized profit" that checks the profit made from a group of trades, but time factor is not considered in this block, so it does not care if the profit/loss is made for today, yesterday...

I guess there should be custom indicators like this, something that gives direct signals (arrows) maybe. Unfortunately fxDreema still cannot create custom indicators, and it cannot use indicator over indicator.

Ooops, one file was not uploaded. Thanks for noticing and reporting that!

What risk management? Unfortunately, fxDreema is still not a indicators builder.

С други думи ти трябва нещо като trailing take-profit (обратното на трейлинг стопа)?

I can suggest 2 ways to delete a pending order after another one was previously deleted. The first way is by checking the number of orders/trades under "on Tick", and for example if there is a trade created - to delete pending orders. And the other way is in "on Trade" - when a pending order is opened, this will execute "on Trade" event and there you can detect that a new trade is opened and do something at this moment.

Има една опция да се ползват виртуални стопове вместо реални. Това си има своите предимства и недостатъци, но веднъж един поиска опция за изчакване на стопа - ако е тръгнало на загуба и не се е върнало до известно време, тогава се затваря, а ако се е върнало - нищо не се случва. Или поне такова нещо беше по спомен. Тая опция е "Virtual stops timeout" в "Options->Current project options". Разбира се трябва и виртуалните стопове да са пуснати.

Разликата между ръчно пусната поръчка и пусната от експерт е т.нар. Magic Number. Добра идея е да се запознаеш с това нещо. Това е атрибут който го има всяка поръчка, и при ръчно пусната е равен на 0, иначе има друг номер. Цели се разграничаване на поръчките от експертите - всеки да си знае номера на неговите поръчки и да не закача другите.

За всички генерирани експерти има един входен параметър MagicStart, който е същото като Magic number-a, ама с малко условности. Вътре в експерта на доста места има един параметър Group, който нормално е празен, което е 0. За поръчката дето ще се пуска важи формулата Magic number = MagicStart + Group.

I searched the forum and I found this... It can give some ideas at least http://fxdreema.com/shared/saUu2Td5b

There is a block called "Trades count".

There was somewhere in the forum Sure-Fire project, you found it?

"Start trades loop" makes the next block(s) connected to it to be executed as many times as many filtered trades there are. In a
single tick, "Start trades loop" can pass 10 times if you have 10 trades, so it can execute what follows 10 times in a tick.

I think this project is not very well constructed, it will probably work in a "random" manner. If possible, make projects with less Buy now/Sell now blocks as possible. Also if possible, don't copy/paste the same group of blocks - reuse them instead.

I don't want to create full EAs for anyone, my role here is to help people to understand how something works and then they should be able to do it alone. I prefer exact simple questions about how some block works or something like that. Unfortunately I'm not even able to think about bigger and complex projects, because I already have one to think about - fxDreema.

Значи No trade проверява дали има поръчки, но филтрира наличните по определени критерии - валутна двойка, magic number (Group), тип (buy, sell). Мисля че е добре да сложиш Market mode на Specified market и без да пишеш нищо в полето, за да си работи блока само с поръчки от валутната двойка на графиката.

What is a condition? If you have numbers 1 and 2, there cah be a condition like this: Is 1 lower than 2?. Every time when you ask that question it will be true!
Notice that your Condition blocks are located under "on Tick", which means that they are executed on every tick.
Notice one more thing - your Conditions does not care how many trades you have, they work with something else - indicators.

In a single tick, all the blocks connected to AND must be passed in order for AND to pass. Obviously AND passes when the last block connected to it passes, and only when others were passed too.

OR is also to be used with multiple blocks connected to it. OR passes once when one of the blocks connected to it passes. Again, this happens In a single tick .... for the next one everything is clear again.

Well, at first glance I can't see any trades-limiting blocks, such as "No trade is running" or "Once per bar" or whatever it takes to limit the number of trades. You know that the condition is just a condition and it can be true tick after tick all day long.

By the way, you don't need this "OR" block over there. Maybe you want to connect the output of the "AND" to the input of "OR".

What is not working exactly?

Using or not something should be personal choise I think. But in case of this EA I think the problem is in the stops size. If it works with 10 pips, for example, that means the constant is ok. But if it stops to work below some limit... well, broker things.

Now I think I should at least make it to put SL/TP to the lowest available distance when the requested is too low

Because you are using Constants, I can tell that sometimes there can be problems when a certain constant is named the same way as a local variable in the block that is used. I think this is not the case in this particular EA, but in any case I want to say that. To overcome this, there is a small "MQL prefix" field that can be used to automatically add something to the names of all of the constants, for example "_".

In the beginning I decided to use local variables in this style - VariableName - but now I can see that most of the people are using this style for their input parameters as well. In most cases this is not a problem, but there are some situations where strange things happen. So I plan to take some measures about that in the near future.

My broker is... I'm using the one that comes with the original MetaTrader dowloaded from metaquotes.net

What is the minimum SL distance that works? In my backtester it seems to work with 7 pips of SL. Well, I can't help much when brokers has limits. The same trick should work here: (in loop) Pips away from Open Price -> (in loop) Delete pending order

Fixed

The error says "Invalid trade parameters", which means that some parameter is not ok. Parameter such as SL, TP, Lots... or Expiration. In case of this EA, that parameter is Expiration. Everyone knows that manually we can cancel pending order as soon as we created it, but when EA is working there are different rules sometimes.

Check this one: http://w.molanis.com/forum/viewtopic.php?f=6&t=5559
and this one...: http://www.forexfactory.com/showthread.php?t=59997
and this one...: http://forum.mql4.com/10531

But there is other way to close pending orders. Try this one: %(#FF00BF)[Start pending orders loop -> (in loop) Check trade/order age -> (in loop) Delete pending order]