There is a block called "Hours filter" which have less setting, but I think it will be easy to understand it. Backtest these blocks with "Draw arrow" block. In other words - Hours filter -> Draw arrow. If you add Once per bar just after Hours filter, this will give you 1 signal, otherwise the block will pass at every tick in the whole period of time.

Trailing stop has settings like:
Trailing stop - the size (in pips) where to put the SL
Trailing step - how often to make moves. If step is 10 pips, it will move SL in every 10 pips of profit. If it is 0, it will move it in every price that is bigger than SL+TrailingStop.
Trailing start parameter - when to start trailing stop functionality. You can put 10 pips here, and until you have 10 pips in profit, Trailing stop will not work, no matter what are the settings.

For you, I think the settings are:
Stop - 20
Step - 10
Start - 10

This can explain how trailing stop actually works. Here we have the same trailing stop functionality on the left and on the right. Well, without taking care of Start option. http://fxdreema.com/demo/mt4-9975

This website is located on a new server from today. After weeks of troubles at the oldest shared hosting, I decided to move everything on a new VPS server where I have better control and there are no other users using the same resources with me. The machine is located in New York, hosted by zap5.net, and it has 4 CPU cores and 2GB RAM, which is too good for fxdreema.com I believe.

Well, there were some troubles while moving to that new server, so I really want to apologize! It is possible that "fxdreema.com" is still not working at some places (including my laptop), but it will be ok soon. Domains takes time to be reconfigured.

Also, for some (still) unknown software reason the new server already crashed 2 times today, which is not good, but now it looks to be working fine. The truth is that I started managing VPS and installing server on VPS about two weeks ago, so I'm probably not the best server-guru 😮 At least I learn quiclky.

Thanks for your explanation. It is very clear so.

I know you are busy with your server. But when you have time will you look at my 2e question?

You know my EA will trade not on a crossover but only when the 3 conditions are true.
When i start my EA on a monday morning and we open for example 100 pips higher than the close of friday i don't want my EA to start right away.
I want the EA to wait until one or two of the conditions become false.
And when that situation has happened he is free to go for the next trade when the 3 conditions are true again.

I am looking forward to this answer.

Kind regards,
Martin

I think the rule "never risk more than 3%" is the one that calculates lot size depending on stop-loos. In this case if you want to set X pips SL, then the lot size is calculated in a way that when SL is hit you will lose about 3% of equity (or balance). And there are options for this situation, but they are named like "Risk % of Equity".

http://fxdreema.com/forum/topic/1983 🙂

For the system above. Is there some formula behind those numbers or they are imagined by you? If lot sizes, dropping pips and TP pips are totally custom, the whole thing will take many blocks, but if there is a formula behind those numbers, it can be done with minimum blocks (and better control).
Why 7.9 pips, not 8 pips? There must be something behind that...

In any case, there are two blocks to put multiple pending orders at once with different parameters. Their lot sizes, distance from each other, SL and TP can be non-linear, so this is maybe the best and easiest approach to do everything. At least to see if everything works. What is also good in pending orders is that they work automatically on the server.
Maybe the reason why you want to not use pending orders is that you don't want your broker to see how your EA works. Maybe I should also create virtual pending orders system. But in fact, I think that the broker, if he wants to, can cause much more damage on your trades.

For example, these days a friend of mine losed tousands of dollars because of 5-minutes problems with the server. The EA was confused of what to do. But if something wrong happens on your EA... well, from the broker's point, this is your fault. But if the whole system is located in their server in form of pending orders and if something went wrong - this is clearly their fault. Each pending order is like a micro-EA working on their server.

So, can you imagine the system described above with pending orders?

ok, well that will work but it gets really complicated when doing this...depending on if you export tick data with or without weekends...and so on

So would appreciate a block that checks on "current day"
That would be great

Cheers

Yeah... after I'm creating some problems I must take care of them 😆

This is well known situation with Moving Average. This indicator does not guarantee profits, it just calculates something and draws a line.

To know if MA is rising or falling, you must compare two values from it. Oldest value below the newest => rising. Otherwise => falling. You can also check "Indicators" category.

Blocks 6 and 13. Let's say that there is an option inside called "Filter by type" 🙂

Haha. Remove about 100-150 because in phpBB first 50+ users are reserved for bots, and there were spammers in the beginning when before I added the antispam question to register 😆

This is real situation from this morning. It happened to a friend of mine with AVA broker. I changed the name of the EA in the log:

08:13:17 EANAME EURUSD,M30: Error occured. Error code 129 08:13:19 EANAME EURUSD,M30: Error occured. Error code 129 08:13:21 EANAME EURUSD,M30: invalid slippage for OrderSend function 08:13:21 EANAME EURUSD,M30: invalid slippage for OrderSend function 08:13:21 EANAME EURUSD,M30: Error occured. Error code 4051 08:13:23 EANAME EURUSD,M30: invalid slippage for OrderSend function 08:13:23 EANAME EURUSD,M30: invalid slippage for OrderSend function 08:13:23 EANAME EURUSD,M30: Error occured. Error code 4051 08:13:27 EANAME EURUSD,M30: open #10365265 sell 0.30 EURUSD at 1.30140 ok 08:13:29 EANAME EURUSD,M30: Error occured. Error code 136

Weird errors. This is ECN broker, so first the trade must be sent, and then stops to be modified. Everything happens in 2 steps - OrderSend() and then OrderModify(). The actual problem here is not that the trade has troubles to be opened, but after that - when stops must be placed. You can see that error 136, which means... "Off quotes".

Leaving a trade without stops can be very dangerous sometimes, even if the EA itself is not scalping. For this EA - missing stops caused more trades to be opened because of wrong part in the code.

For example, in non-ECN brokers there are 2 outcomes - to create a trade with stops or to not create a trade at all. With ECN broker you can be easily found in a situation with a trade with missing stops.

So, be careful with ECN brokers. I know that everyone say that ECN is better, but obviously this is not exactly like that. It looks that every ECN broker has at least one more chance to fail - in OrderModify().

Done, also for vertical lines and rectangles. But on MT5 for some reason there is no effect 😮

This is very strange. I made a modification to another unconnected block, and now I'm getting just 1 trade. At least its working! 🙂

Looks normal here, ot at least I can't spot the problem 😎 Buy-Sell-Buy-Sell... 0.1 lots all the time.

Nope. Indicators have different structure and they can draw lines in a way that EA can't.

thanks for the detailed reply.
Yes you're right. For Cross to be confirmed it would have to be the previous candle otherwise like you said it would just be a temporary Cross.
I will try with candle ID 1.

Cheers !

You should know that the pink block is self-repeating as many times as many trades there are. When it finish it's job, it exits from the yellow output. Whie running, that block also loads attributes of the current trade that it is working with, and that attributes can be read in the way you will see in block 3.

Thanks, thats great.
Its great when it does what you want it to do.
I'm starting to see how it thinks.

Cheers
Andrew

Yes, create a non-linear trailing stop. Used Variable with Break even (BEP offset mode) block. Works. http://fxdreema.com/shared/9vn3S9afe
Modify SL (with positive / negative) input does something else. http://fxdreema.com/shared/bit5yw1xb

Thank you fxDreema and Alepie.

It's so mean. But I had a problem fxdreema! He did this by opening the pending orders. In place of of pending orders, puts the SL and not a pending order.

I need to open pending orders x_pips the custom indicator price channel, the order of hedge with 1.1 Multiple lots of the initial order.

This here my project dynamic hedging: http://fxdreema.com/shared/MDTxqC6Zc

Attached is the indicator price channel.

Even more!

......
Price Channel.mq4