Posts made by fxDreema

"Once per bar" knows which is the current bar and this block can only pass 1 time per bar. When it runs under "on Tick" and there is no block above, then "Once per bar" passes in the first tick of each new bar (or candle).

If the block is under some "Condition" and that "Condition" passes somewhere in the middle of the bar, then "Once per bar" will pass at that time, let's say at 20th pip in that candle.

There are "Candle ID" parameters in many tools in "Condition". The EA always knows the OHLC values of the visible candles on the chart, so when you change "Candle ID" you can get O, H, L or C from the 20th candle, or from the 35th, or from the candle you want. The same is true for the indicators. You can get indicator's value from the 3rd candle or from any particular candle just by changing "Candle ID"

https://fxdreema.com/help/pics/crossover_bars.png

The difference between 1.15878 and 1.1548 is 40 pips, pretty large number.

Do you know how this block works? Because it reads the trades, calculates their average lot size and average open price using some formula (imagine that the result is one single position) and sets SL of all trades to a particular level behind that invisible "open price". Of course, each trade is still individual, each one still have its type (Buy or Sell) and depending on the current price you are able to set SL at certain level for some of the trdes, but not for others.

Imagine you have Sell trade that is on profit. You can't put the SL level below the current price.
Imagine you have Buy trade that is on loss. You can't put the SL level above the current price.

When you have mix of Sells and Buys, it depends, some of them might be out of the game.

Try with "Modify stops of trades" and use SL as "Custom (price level)". The problem with this block is that TP must also be set.
The other way is "For each Trade -> modify stops"

To detect when RSI is cerian level, use "Condition"

In "Trailing stop (each trade)" there is an option for "Trailing Stop is..." that is "Custom (level)"

Buffer 0 appears to be the Close price of the blue candles and Close price of the red candles. Otherwise its value is 0
... and so on...

Get some Trace block, play with it in Visual mode and you will eventually understand what each buffer means. Then how to use them... I don't exactly know. Even the built-in Heiken Ashi is kinda weird. I used to detect red/white candle by comparing the values from 2 of the buffers.

The price is Bid. Normally on the chart we see candles based on Bid price and indicators based on those candles

I can see Buy-Sell pairs, 2 trades located close to each other. Do you have error messages in the log? Because, how can you set the same SL for both trades in a pair when they are so close to each other? And why do I think that the value of TPPips is 0. And why TPPips is sounds like something about take-profit, but it used as a trailing SL.

By the way you don't need any of the "AND" blocks you use.

Hours for 1 month testing doesn't sound normal for me. I can see this in one of your projects: http://prntscr.com/cbv6m1 Blue blocks doesn't need pink blocks to work. In this case you don't need the pink blocks, because the Trailing stop block has the loop, the filters and everything inside. Trailing stop block is like multiple pink blocks into 1 block.

Well, I don't have that particular indicator in my /Indicators. But you can always check each buffer with "Trace". If something doesn't look as expected, try with to set Candle ID to 1 (some indicators don't draw anything for the current candle)

Set Candle ID to 1 when you want to work with the last candle. At the first tick of the new candle O, H, L and C are equal.

https://fxdreema.com/demo/mt4-sell-each-bar

Not at the moment. As I said above, this block is very basic, it only does iterations and nothing more. It's code is as simple as this:

for (int i=1; i<=Cycles; i++) {~next~}
~inext~

... where ~next~ is the orange output and ~inext~ is the yellow output.

Who knows when will I decide to add some "break" and "continue" blocks.

What if you turn these blocks into MQL4 code in a custom block?

"Formula" #26 now works like this: Result26 = RISK + 1

But I'm pretty sure that you don't need a global variable named "Result26". Try with "RISK" instead.

In "For each..." blocks there are filter, sorting and limiting settings, so it depends on how you set them up. This is also true for blue blocks.

The EA controls the size of 1 pip. Click on the bench icon (the project's settings) and look at the settings at the top.

Ok, but technically what are you trying to do and it doesn't work?

It's most probably possible, but I don't fully understand the question

This loop is very very basic and does not stop by itself, so the value of LookBack is always decremented RunTimes times. I think this is the reason.

I can see that in your latest project you have "Trailing pending orders". Are you sure you want to use exactly this block?

Yes, but again, the situation is not exactly the same. I think that it's technically better to put the EA on separate charts. But I also never tried that personally, so I'm not talking from experience

This is how the indicator works. It's not the "Indicator tester" or "Trace" that shows wrong values. Sometimes I introduce bugs in the code, but I'm 99% sure that the block is working very fine

The huge number (21... ) is also known as EMPTY_VALUE and this number is how indicators tell the EA that there is no value to be shown. That's why the constant is called EMPTY_VALUE

It was discussed before...
So, before using "Risk % of...", make sure that SL is a positive value, because SL is used to calculate the lot size. The exact row where the error happens is:

else if (mode=="equityRisk") {size=((value/100)*AccountEquity())/(sl*TickValue*PipValue(symbol));}

... you can see this small "sl" just after /. If this is 0, the "zero divide" error appears.