Posts made by fxDreema

Interesting question, I don't know, I have to check this

Do you know what the word "Average" means in the title of this block? More than that, look at what "Profit mode" says - Pips. Pips are not Money. And the term "Pips" when different lot sizes are used is a little bit... even I can't tell you right now what these Pips means exactly

Again, your number 2,28 is the SUM of all profits in MONEY. This is not the AVERAGE value of some PIPS.

Of course you can do calculations, as many as you want. The problem is that if you use "Formula", this means 1 block for 1 calculation, which is kinda stupid. But there are other ways to calculate things as well. In these examples you can see them - https://fxdreema.com/examples/#Constants-and-Variables Also, there is a block "Custom MQL4 code".

When you use "Formula" blocks, make sure that each calculation follows the previous one. I don't know why people prefer to connect many "Formula" blocks in parallel. It looks beautiful, but it's much better to connect multiple "Formula" blocks one after another, because calculations must be done in order. Don't rely on block numbers very much. Look at your block numbers - 25, 26, 16 - which one of these block will run first? Do you know and do you care? 16 runs first and you should care. Trace runs before Formula blocks.

If you have issues with values... well, you should know them before going to work with them. ATR gives you values like 0.00010. Ask/Bid are values like 1.23456. Sometimes values must be converted.

So, this is what I see - http://prntscr.com/akf0a0
If ATR is let's say 0.0007, this is 7 pips. In Formula blocks you double that value and put it in both sides of the current price. Something like +/- 0.0014 (or 14 pips). This is pretty much what I see - http://prntscr.com/akf1kb (127 = 12.7 pips).

I found a bug in this block and I think I fixed it. The problem was that if you select one mode in "Price relative to", other mode is actually used. But I'm not sure that your problem is this...

Look at this - https://book.mql4.com/appendix/limits
There are some limitations and you are not allowed to put the order too close to the current price. But in your case the new price does not look to be very close and I don't really know what is happening. Can you check what happens if you have no stops (sl, tp) for the order? How close to the current price can you put it? Do you always get this error, whatever values you are using?

Block 53, undefined variable is used, PipsEntrada

There are other problems that come from "Trace", but it's my fault and I will fix them right now

If you are in "Condition", look somewhere in "Market properties" - https://fxdreema.com/demo/mt4-trace-multiple Only Highest and Lowest prices are available here.
As an indicator this is known as Donchian Channel

Now you want to make indicators Unfortunately fxDreema works only for EAs and Scripts.

I don't really remember I made this for someone back then. I personally hate this indicator and I don't know why people are using it. But everywhere, when you see ID = 0, this means the current point of something. If it's 1, then this is the previous one on the left side. Just like candles. If you are confised about the word "ID", then think of it as Index or Number or Offset of Shift.

Look at the default value in Custom Sequence. These are not lots, these are times... times bigger than the initial lot. If the initial lot is 0.1, then the value of 3 means 0.3 lots

Timeframe (or Period) is H4, H1, M1, Daily and so on... There is no such thing as "previous timeframe".

There is previous candle (or bar). Open "More settings" and you can see the parameter called "Candle ID". 0 means the current candle, 1 means the previous (on the leff), then 2, 3 and so on...

I don't have this problem. Give me some file or instructions. If I don't see the problem, I can't fix it

You want to make Buy Stop to Buy Limit? I don't think that MT is capable of doing this

i think it's ok now

Damn...

I remember reports about such problems before and I was thinking that everything is fixed... who knows... I must check this again

I remember 3 types of expiration:

ORDER_TIME_GTC - Good till cancel, which is when there is no expiration
ORDER_TIME_DAY - Good till current trade day order, which is "Today" - the expiration that ends at 00:00
ORDER_TIME_SPECIFIED - The option you are using

I tried the "Today" option and it works. As you can see, ORDER_TIME_SPECIFIED is not valid option for this symbol. I was not aware of this "Specified day", it's probably new option, and this is what they say about it:

ORDER_TIME_SPECIFIED_DAY - The order will be effective till 23:59:59 of the specified day. If this time is outside a trading session, the order expires in the nearest trading time.

This mode does not exists in fxDreema yet. In any case, you can's set expiration of 2 hours. As you can see, in theory you can only use options that expire at 00:00 in some day. But if you really need to expire pending orders few hours later, then you can make artificial expiration - check the age of orders and close them when they are N hours old. Something like "For each Pending Order -> check age -> close"

It shows some valid expiration modes - http://prntscr.com/aj4kml
http://i.imgur.com/tFWRzed.png
These symbols are so weird, but MT5 is crazy anyway

Maybe something like this - http://prntscr.com/aj119m
http://i.imgur.com/52Mrpgr.png

Candle Close is Bid, but when working with indicators I prefer to use Candle Close.

You can always use "Condition" block to compare 2 values. For example, values like Candle Low of the current candle or any other candle (look at the Candle ID parameter in More Settings) and many others. I don't know how you get these hammers and I don't know what to say about them

Maybe you should connect these "Condition" blocks with Buy/Sell blocks. From what I see, now your EA will buy and sell on every tick until there are no money left