Posts made by fxDreema

http://prntscr.com/a7j5tx

Here is for example how to close a trade if it's older than 1 hour - https://fxdreema.com/shared/QKXmhyGWb Of course, something else can be used instead "close".

There is actually a function to turn any Time value into candle offset - https://docs.mql4.com/series/ibarshift I wonder if it's a good idea to add it in Condition -> (in loop)... , but I'm not sure

Why is this? http://prntscr.com/a7iok1

"OR" block is something like Once Per Tick. Each "OR" block can pass 1 time for the current tick. It doesn't care and is not aware of other blocks. So everything above it will run on every tick for sure, even if it's not needed. All those green blocks on top run on every tick, just because they are on top level.

Yes, this is not very optimal way of doing things. This way is better - https://fxdreema.com/demo/mt4-or-logic-1

I don't think you need 6 different "Once per bar" blocks connected like this. How it will work if you use only 1 of them? If the logic is the same, just use one. Also, I don't know what's in "Check trades count" and "CCI < 0", but if all of them are the same too, then what will happen if you use only one group of them, not 6?

Server problems were out ot my reach. It was something with the hosting company, unfortunately. But they fixed it now.

Yes, "Comment" blocks are just like other blocks - they work when they run. The result of their work is the text message that appears somewhere in the chart, but it is only updated if the block runs over and over again. If you want it to be updated on every tick, then connect is somewhere on top level, so the block runs on every tick

Not only this, also the website of the hosting company was gone for hours. This is overview of their servers from today, it looks that they experienced some problems - http://prntscr.com/a7id6c

I don't have "Stop ATR" indicator and with it I have another kind of error, so I changed it with "Fixed pips" in all "Buy now" and "Sell now" blocks. Then I started the Tester and for now it works: http://prntscr.com/a7ia8o When the problem does not happen to me, I can't say what causes it. Can you isolate it somehow?

I decided to rename "Start price" to "First price". With this set of parameters you are defining one price level that is the Open Price of the first pending order. From that price the Grid Size value is used to calculate price levels of the other pending orders. So everything starts with that first price level.

block 1 - "Time filter" works for me. I connected "Draw Arrow" to it and everything was expected. And the EA produces this result: http://prntscr.com/a6xomt It looks that something starts to happen at 10:00 and ends near 18:00.

block 24 - this is also working fine. The problem is that you have second path to reach "Buy now" and "Sell now", which is block 25. If you disable block 25, then you got this: http://prntscr.com/a6xqbq

block 24 and block 25 are connected from the same source - block 9. Because block 24 has lower number, it does it's job first. It's job is to run blocks 4 and 12. Block 4 is checked and then block 12 is checked. If one of them is true at that time => one new position is created. If both of them are true at the same time, the EA will Buy and then Sell.
Let's say that you only got one Buy position after blocks 24->4->5. The next block to run is block 25. What follows are two Condition blocks and they are the same as 4 and 12. Because 4 passed, now 14 will pass. The position that you just got is losable, so it is closed by "Close losable positions". Then you create a new position again. And all this happened within one tick.

On the next tick block 24 will not pass, but block 25 passes and once again, the position that exists is closed and new one opened. And this repeats over and over again or every new tick.

No

Better don't think for the end of the candle. That's why - https://fxdreema.com/help/-/working%20w ... e%20closes

There is a block called "Once per bar". When that block is placed in "on Tick", it basically detects the moment when a new candle is created and passes in it's first tick, only once. Once for each candle. If this block is below some Condition, it can pass in the middle of the candle. Also once.

What do you want to do exactly?

It's midnight, 00:00, a new day starts. The EA is working. Nothing happens until 08:02. At 08:02 a new trade is created... How this story continues?

Even one single Condition block does that, it check IF and then if the result is TRUE it goes to one path, otherwise it goes to another path. Few Condition blocks work as a single Condition if there is 1 input and 2 outputs.

I don't really know what to say, I think it's obvious. When two blocks are connected, the first one (if it passes) causes the next one to run. Two groups of Conditions can be connected. There is also "Run blocks" block.

https://fxdreema.com/shared/AVcp6daAb

Ok, I added this option. It's called First Price: Round Number and is measured in pips. So, if in EURUSD you write 100 (pips), this will be translated to 0.0100 and the round number will be calculated using this value.

If you Buy and if this value is positive, then the output price is rounded to the round number above (Ceil). For negative value - below (Floor).
If you Sell, then it's like in a mirror. Positive value rounds below, negative value rounds above.

I was wondering if I also need to consider the "Grid Size" value, because this value can also be negative. If this value is negative, then the grid of orders is mirrored.

I need to add some option in grid blocks to snap to some rounded price, but now there is no such option. However, I can suggest some not-so-complicated calculations. Take this for example: https://fxdreema.com/shared/KzCrYyUrd
http://prntscr.com/a6uyc1
http://i.imgur.com/97e0SBN.png

Bid is predefined constant in MQL4 and it gives us the current Bid price.
Here is the description of the other functions that I used:
https://www.mql5.com/en/docs/math/mathceil
https://www.mql5.com/en/docs/math/mathfloor

The grid size does the rest.

But I think I will add some option in these blocks

I can't say how, because it depends Obviously if you run "Turn ON blocks" after that, block 10 will be enabled again. But when to run that "Turn ON blocks"... again, it depends. My question is, do you really need to use these blocks

The lowest timeframe is M1. For each M1 Candle you have 4 price levels - Open, High, Low and Close. There is no data for the ticks inside those candles, nothing more that those 4 prices exists.

The first thing that the Tester does is to generate ticks. It reads the information from M1 (or other timeframes) and based on that information it uses some algorithm to create ticks. By the look of each candle it decides how ticks would travel within that candle. Candle's Volume is probably used to decide how many fake ticks to put in that candle. It's the same as if I give you one candle and ask you what was the path of the ticks inside.

If you have candle with height of 10 pips, then fake ticks will be generated for the path of those 10 pips within that candle. But what if you create a trade with stops of 5 pips? If that trade is created and closed within that candle, how accurate will the result be?

It's another story if you for example create a trade in the first tick of the candle and then close it at the first tick of another candle. Those are the Open prices and they should be accurate. Or if you have stops much bigger than the biggest M1 candle.

The problem with Trailing Stop and similar functions is that in most cases they react on small movements. The price moves with 1 pip and Stop-Loss is set somewhere, which means that Stop-Loss is also fake, because it is based on fake ticks.

Here is more to read:
https://www.mql5.com/en/articles/1511
https://www.mql5.com/en/articles/75 (this is for MT5)

A Variable is something that has Name and Value. Then when you refer to that Variable by it's Name, you can get it's Value. That Value can also be modified. This can happen everywhere in the EA, because Variables are global. There are different ways to get and modify them and I tried to sumarize them here in this example: https://fxdreema.com/demo/mt4-variables

"For each Trade" finds how many trades there are (depending on the filter settings) and starts to load each one, one after another. For each loaded trade the orange output becomes active => what is connected there runs. For each trade only its parameters are loaded - open-price, stop-loss, whatever... All the other pink blocks are designed to work with those parameters, to check them, to modify them. In other words this block creates "for" loop where the body of the loop is represented by all blocks connected after "For each Trade".

"If trade" finds how many trades there are, depending on the filter settings. Then it decides to pass or not. That's all.

X bars from the trade.... What is that mean? Because:

• Each bar has Time attribute, along with Open, High, Low, Close and Volume attributes. That Time attribute equals to the rounded time when the bar was created. For H1 the first bar of the day has the Time that is translated to 00:00 at this day. The second candle of the day has Time that is 01:00. Not 01:00:04 or something like that. This can be easily seen in the Histry Center:
  http://prntscr.com/a6ue5y
  http://i.imgur.com/WkgRBTH.png
• Each trade has two Time attributes - Open Time and Close Time. If we take Open Time for example, this is the exact time when the trade was opened. This time is not rounded to the nearest minute or hour.
  http://prntscr.com/a6ug7s
  http://i.imgur.com/8r5AxLu.png

So what X bars from the trade really means? If you are in H1 and a trade is opened at 00:59, visually it will appear that the trade is opened within the very first bar in the day, but in fact it is opened at the last minute of that candle. Then what means 1 bar after that trade? It is something after 01:00 or is it something after 01:59?