2 questions

[RobinURSS]

hi dear fxdreema

my questions:

1- when i have a condition block with the comparison switched to "crosses" (i.e. x<) and i use the yellow output, this will be passed when the crooe ocure in the opposite direction like x>?

Because in the general information of the condition block the yellow output means that occures right the opposite that in the comparison, so the opposite of x< is x> right?

2- if i have 3 fxdreema robots running in the same MT4 and i want a trailing stop for those 3, can i creat a single robot of trailing stop for those 3 robots? How can i do it? i meant, how can i make that the robot of trailing stops works with the trades of all eas in the platform at the same time ?

thanks very much

[fxDreema]

1 - Yes
2 - Magic numbers should match. Well, in the EAs generated with fxDreema you don't control magic numbers directly, but this is done with the input parameter called "MagicStart" and Group numbers in blocks. The short answer is - for those 3 EAs use the same MagicStart and don't change Group # in blocks.

[RobinURSS]

This would be the Trailing stop Ea

https://fxdreema.com/shared/twhyyVmxb

Check and tell me if im wrong, the boxes of Group and Market, in the other 3 eas i have those boxes with default settings.

Finaly when i put the 3 eas on the chart i have to copy past the magic number of the trailing stop ea to those 3 eas rgiht?

[RobinURSS]

Fxdreema also could u explain me a little more about macd divergence pattern, its parametres and how exactly it considers that there is a divergence? i mean i know whats a divergence but how the ea will recognize them?

thanks a lot

[fxDreema]

Oh boy, now I have no idea, if you are asking me about the block I made this block long time ago, but then I just realized that some things are better to be made with indicators. I left this block active, but I'm almost sure that I will hide them soon. I will suggest to find some indicator.

Use the same number for all 3 EAs:
http://prntscr.com/67s9us

[RobinURSS]

U should give me 2 days free of full version for that ;D

[RobinURSS]

Please help fxdreema..

I have these errors compilators, i think is something related with constants i have, but they are logical, i dont know please check it..

https://fxdreema.com/shared/Vw7Xe9u7

and

https://fxdreema.com/shared/FvtLOvCoe

[fxDreema]

The accepted format of all "Adjust" fields is something like:
+123
-123
123
/123
+123-29434743*OrderLots()/something_else

As you can see, you should start with +, -, * or /. The contents of the "Adjust" field are appended to the operand in the output code. If you want to use Constant there, write it's name manually.

[RobinURSS]

oh i see...

what i did was creat constants (as numerics) like "*12500" and put it on adjust, to make this valu "*12500" a input parametre.

So if i understood i just have to change to put the constat with right click to just write the name i called the constat?

https://fxdreema.com/shared/l0PLhO7nb

[fxDreema]

Now the problem is that the constant names that you are using in "Adjust" are not constants actually. These are the real names used in the project: http://prntscr.com/6923un

I will eventually make it mandatory to write correct constant/variable names in future. It was not a good idea to make it possible to use free names like "TS DISTANCE", containing that free space.

[RobinURSS]

Well man i have to say i couldnt solve the problem because i couldnt understand a word about u said
What i did to solve the problem was to put the values manualy so i dont have constants for that parametres right now.

But i have another existencial problem man..

When i use once per bar, it all works good but it is not exactly what i want.
For example, i use a no trade is running->once per bar->condition block->close trades
And then trades passes the once per bar just when the next bar has just started.
So its technicaly ok, because the price wich the candle 1 ends is the same with the price wich the candle 0 starts and in that tick the once per bar passes... but what i want is that the trades closes when a certain conditions are filtered at the exactly 0:59 minute of the bar ( 1 minute before it closes) because it affects a lot my friend.

For this problem i found the block "once per hour" but my doubt is if this block will be synchronized with the server time of my broker. I mean, every time 1 minute before an hour bar ends the block has to passes.

Can u understand me?

[fxDreema]

You can use some time filter, but I can't guarantee the result. If for some technical reason there are no ticks around this time, you will miss it completely.

[RobinURSS]

Hi man i have problems again, but at least iim learning more..

i have this ea running on mt4 https://fxdreema.com/shared/GguVJtM3b

Could u tell me why only works the break even point and that there is no trace about the trailing stop? never works... just break even

[fxDreema]

Probably because Trailing stop does not work with these settings. What is this ATR4666 (http://prntscr.com/6d713a) If my ATR is 0.0020, then 0.00204666 = 9.332. USDCAD price is now 1.248, this 9.332 is not even near to this price

[RobinURSS]

Im using the block " once an hour" with server time and at certain minutes with minute 59.

The problem is that it isnt realy exact at the moment of pass this block for example, may be it passes at 1:05:00 or 8:32:00 so i passes whatever it wants, but 80% of the times it passes in the minute 59 of an hour.
Is there any block that passes exactly before a candle ends, and if are thinking on once per bar, it doesnt work because if i put it right before the conditions blocks it will open the trades with the open price of the new candle and this affects to the other indicators calculation, I need it works with the right close price of the candle before a new beguns.

[fxDreema]

So you also want to detect the last second of a candle? Here is the problem with this - you can't do that in the backtester. Backtests are driven by generated ticks. Each tick has some time attribute, but there is no guarantee that you will always have a tick in every :59 second.

It matters where blocks like "Once per...." are placed - on top level, before some filter/condition, after some filter/condition.

[RobinURSS]

i know all of that fxdreema.... and im testing the ea on the vps on real time...

but i fund an inteligent way to make it works like i want.

I use a once per bar after no trade is running, then all the conditions and the buy now blocks, but all the conditions has the more settings activated with candle id 1 and some times i use also the variable "candle" with parametre candle close and id 1. So right the tick before the new candle beguns the ea checks the exactly value of the past candle close and indicator calculation.

i want my dimplomaaon fxdreema ...

[fxDreema]

"Once per bar" is one of the best blocks

[RobinURSS]

my next questiion..

if i have formulas wich im going to use with a condition block, i have to put the formula block first then the condition block right?