Posts made by fxDreema

There is no best way, it depends If there is something like "best way", I will just put that limit inside "Buy now" and "Sell now" blocks. But it depends.

You may want to limit your trades by number or by time, or mixed. For example, you can decide to put 1 new trade on every new candle - here you don't care how much trades you have. Or, you can decide to have certain number of trades, for example 1 at a time.

Try this;
No trade is runniung -> Condition -> Buy now

https://fxdreema.com/shared/EPkXa3Nhd

It will probably work

I also need Password

Hey, you are here and I am here? Send me TeamViewer data on PM

Last high and last low is very subjective, it depends. There are indicators to do that. Otherwise for fixed number of candles or fixed time, look in Condition -> Market properties -> Highest... Lowest... you will see these

I was called by one friend to do something today and was off
Otherwise it is still fine for me, look: http://prntscr.com/4shxo5

So we have to match our times now

https://fxdreema.com/demo/mt4-trailing-pending-orders
https://fxdreema.com/demo/mt4-trailing-stop

Yes, when the first option is No and the second is Yes, the block is allowed to create many objects (first option), but because it is set to redraw (second option) the current object, the result is that it creates 1 object and then it only redraws it.

What, Draw Arrow creates lines?

The top two options control the number of objects to be created. There are 4 situations:

• the block creates a new object every time
• the block creates a new object once per bar
• the block creates a new object once per bar, and then it updates it until the end of that bar
• the block creates 1 object only, and then keeps it updated (this is what redraw means here)

Again, this is what I already said few times, you can test any block or small group of blocks in a temporary separate project, to see how it behave.

What project is this? I looked at your projects and the last one is actually clear.

Also I don't understand what you want to trail - pending orders or SL of running orders.

Weird, the values for Open price, SL and TP should be the same. And I don't get this error on my backtester, even on the same date and spread. If it's not a problem for you, can I look at the problem with TeamViewer?

Just remove those "once per trade/order" blocks and try it. I will suggest to connect block 54 to "Once per bar", so the variables will be calibrated on every new candle.

We have separate e-mail conversation, but I will tell that I tried that and...

• Normal EA cannot place order in binary options mode, error 133 (Trade is disabled) is returned and that's all
• The tester also does not work

What's specific for Binary Options brokers is that the normal "New Order" panel is replaced with another one that looks like this http://prntscr.com/4rvjnu and probably communicates in different way with the broker.

If somebody have more information about this topic, feel free to share

Very well written ЕА

It seems to wait for the profit of the last trade to reach some value and then in creates a new trade. I probably missed the fact that you want to look in the last trade only to create a new one, which then turns into new last trade. In this case you actually don't need that "once per trade" block. When you look only at the last trade (let's call it trade A) and when you reach some profit for it, then a new one is created (trade B) with 0 profit (well, negative). The profit changes immediately. You will never go back to trade A again! So you don't need "once per trade", this happens naturally in the moment you create a new trade.

If for some other reason you are always looking at all available trades, then you will probably need this artifical "once per trade" functionality, but this is not your case.

Interesting, mine is working well: http://prntscr.com/4rht4f

Can you try this one: https://fxdreema.com/shared/wcpJyP4ad I want to see indicator values in the moment of failure.

Can you create some simple EA that contains the problematic block and... let's say "Draw Arrow"... so I can get that EA and recreate the situation directly?

Otherwise for MT5 I know that very often it does some weird things, because it does not work in synchrony with the EA. For example, when you start the EA and the first thing to do is to load some indicator, MetaTrader 5 will start loading the indicator, but will throw an error message before finishing that loading. It just does not wait for something to be loaded and you end up with error messages and value of 0, which can cause problems with the EA.

Worse than that, recently I found that it does not wait it's own database with positions and orders to be updated before giving you information for some position or order. So if you decide to modify some position and then immediately get the modified value - it will give you the old value instead of first updating it's database and then giving you what is needed.

I tricked the both cases, but who knows what else could be wrong...

(before this, I posted another answer that is now on the previous page)

I intentionaly set "grid_space_factor" to 2 to make things faster, and after I added the EA I got this: http://prntscr.com/4rgdjd
Two initial trades were opened, and after a while - 2 more appeared.

Then I reloaded the EA and as expected, nothing more happens, because "once per trade/order" does not react for these previously opened trades. It will start to react if I close them all and everything starts again.

Let's say I revert that update or I add an option in "once per trade/order" to select how to react on old trades. If you decide to make it clear every time the EA starts, then it will be possible to create bunch of new trades every time you load the EA, maybe more than 2 at a time.

What you really need is "once per trade/order" to keep it's memory when the EA is removed and then, after the EA is loaded again - to load that memory and continue working. This is a little bit different than the way I updated it - by checking the trade's age and reject it if it was opened before the EA was started. But in the same time this also can create problems sometimes... it depends.

I have few simple questions:

• Are you aware of the value of the "grid_space_factor" variable after you add the EA to the chart?
• Do you understand what I mean by saying that I recently I updated the "once per trade/order" block in such a way, so now it can only work on trades/orders created after the EA was started? So if the trades were created before the EA was started - the block will not react.
• Do you want me to revert that update, so "once per trade/order" will start clear every time you start the EA?