Posts made by fxDreema

It's not any of the blocks. It's that you have checked some of the parameters to be Input parameters for MT5. In this case you have to edit them via MT5's "Input" tab. It's right to the "Settings" tab, just before "Results".

No, not like that. Connect Trailing stop somewhere below "If trade exists" (or similar) or with "Just pass". It needs to be executed on every tick.

Ahaaa, then can you see what happens in Inputs tab?

Well, you can try with bigger SL and TP to see when you will be able to put it. Try with 3, 4, 5 pips...
Unfortunately this is something that does not depends on the EA. The error comes because the EA tries to put it at close levels, but it's impossibe due to broker limits.

Connect it where you need to do that calculation. I guess, just before the block where you will use Formula's result.

The easiest way is to use Formula block to calculate the difference, and then use it's result in another block. Note that the result will be in what I call "digits" format (for example 0.0010).

fxDreema does not care what point the broker uses. This point format (in project settings) is the one you want to work with, not the one the broker uses. Using "0.0001" means that the EA will work in this format in any broker, no matter if it is "0.0001" or "0.00001".

Do you have errors? Because I have errors when using 2 pips (0.0002), obviously my broker has some limits to the size of SL and TP. But when I put 5 pips, there are soo many positions out there (it's working).

Why MT root? fxDreema must know the root, but it writes files in "/eperts". It adds "/experts" automatically, so there is no need to put it.

Ah, yes, I forgot to tell you this... It's a good idea to take a look at your Journal (Experts) tab from time to time. In this project you tell the EA to put SL like 0.00002 and TP like 0.00001. In pips, this is 0.2 and 0.1 pips, and it's too small.
In fxDreema, with 0.00001 format, 1 pips in blocks is equal to 0.00001.

I think it's easier in 0.0001 format

It actually converts .5 to 0.5... normally... but obviously I missed the case when optimization checkbox is checked

oops...

"Signals" block works like this: when the condition inside is true, it outputs once and waits for the opposite condition to become true (and outputs once from the yellow output). Then, it starts again.
The condition you entered obviously makes it to work very often, so there are too many trades opened.

There is no single open condition that can be used, you must know when you want to enter in trade and when to allow it to trade again. Use "No trade is running" if you don't want to enter in new trade until the current one exists. Or "Once per bar" to limit trades in time. Or some of the time filters.

In order to open new Sell trade, you don't want to have sells at the moment. At least this is in your block 20 (and 13 on the buy-side). Follow alert messages in Journal to see what happens...
You can use "Condition -> Close each trade -> Sell now" if you want, but at the moment your strategy follows more conditions

I didn't noticed that error... thanks for reporting it!

By the way, the right operand in Signals block returns value like 1.3028, and after you add 2.5 to it, it will become 3,8028. You can use +0.00025 instead

The system can always be better

When the EA tries to create trade for the first time in normal way, if there is an error, it switches to "ECN mode" and all the next trade are created in ECN fashion. You can see message for this in Journal/Experts, it appears once when the first trade opens.

For MT4 only Magic Number exists and as I said, this is attribute of the trade/order. When all trades and orders exists in one single pool, if there are 2 or more EAs, each of them must recognize it's own trades/orders. Magic number is the color of the shirts of soccer players.
Within the EA we can use more than one magic number. Again, this is only attribute to the trade/order that is once set when it is created, and when needed we can load that trade/order and ask for it's magic number. So, within the EA: MagicNumber = MagicStart+GroupNumber

"MagicStart" is already included as input parameter.

If you have disabled Windows UAC, the output file is written under "/experts" subfolder for MT4 and everything should be ok. But don't include "/experts" part to the settings in fxDreema. With Windows UAC enabled, many strange things happens

MT4 and MT5 projects are separated, you choose the platform when creating a new one. The reason is that MT4 and MT5 are logically different - MT5 can only have single position per symbol, and this can make the whole strategy different. Also, there are other smaller differences and because of that they are totally separated.

Virtual stops in MT5... I have to write some code for this, at the moment it's only for MT4.

Screenshots are saved... It depends on what you do - backtest or demo/real. I think under "/files" folder, but you better search for the files and you will find them.

You can try "Time filter" block, this was the last one I created in this category. All the others are pretty old and maybe I need to replace them with...

End of the bar again... I should create an event system for that. At the moment it's better to do things on the new bar creation ("Once per bar" block at top level), because end bar detection is not as easy as it sounds like.

For X-pip question - "Once per bar" block.

No protection service is available here. Take a look at this website: https://mqllock.com/

The best way is to create some Constants (you can see Constants on the right side) and use them inside blocks. These are basically "extern" MQL4 variables. See here: http://fxdreema.com/documentation/proje ... 0variables

Magic number is attribute of every trade/order, and the idea is that different EAs can share the same pool with trades and orders without interfere each other.
Every EA created with fxdreema has at least one input parameter called MagicStart, which is magic basically number. More here: http://fxdreema.com/documentation/proje ... d%20groups

Very nice view of the question by the way

"Clear all objects" on deinit?

Well, you can search if there is a trick to do that. I remember that once I searched for this and didn't found a solution. If you ever find indicator, ea or script that can write such a thing, show it to me