stochastic indicator is in fxdreema, you can work with this indicator directly in blocks ...

@miro1360

Miro,

When the current price reaches a support or resistance, I close the trade with profit and open another trade in the opposite direction. If I closed a trade sell, I will now have two trades buy. When the profits of these two trades buy is greater than a certain amount, I close the two trades buy (Area#7).

https://fxdreema.com/shared/AYeJe5GSc

OK @miro1360, that makes sense. I mostly use candle 1 close. My analysis seems to accurately reflect what I am trying to achieve and I don't get 99% accuracy so I think I am good to go... I have found a variance between results on candle close and tick data, I will continue to forward test to find out which has greater consistence.

This code is from another project in which block 6 is "Condition" block 😮

There is some kind of grid now - blocks snap to 5 pixels or something. But they all have different sizes and this is problem.

Trailing stop (each trade) work for individual trades only. But there are other Trailing stop blocks, maybe some of them?

____Really simply

Long case: 3 consecutive lower high and lower low candle... the 4th candle break the last short candle... enter buy. that's all
Short case: the opposite of long case[/quote:3ljhvyed]

and if you dont find way how to make it with indicator or with block Bulls in row and Bears in row, there still "dirty way" how to make it using army of blocks:

https://fxdreema.com/shared/7TI1vbrpe

and here with Bulls Bears in row block, with "advanced" settings 😆

https://fxdreema.com/shared/T4LMSTn6c

;)[/quote:3ljhvyed]

THANK'S A LOT!!!
Really, thank you for interesting

Bye
Andrea

I can admit that it's not only the connection right now. There is some weird error that appears from time to time and Apache restarts. But I'm almost done with the new NodeJS version, so I hope that this problem will disappear with Apache/PHP. Well, I expect problems with NodeJS initially, as always, but at the end I think everything will work very good 🙂

Hey fxDreema!
Thanks for replying....
I think i have sorted it.... i put all the functions in on Tick,,, and used "Once per bar -> Indicator visable -> Buy/Sell"
Seems to work now 🙂

Threadopener: is it still relevant?

If your indicator is really worth to be used you ask me by private message for fixing the buffers or using some other "tricks" to read the arrows for use in an EA.

i solved the wrong sell signal putting 2 "once per bar", one for buy condition, one for sell condition (scanner project)
now i wish to add the w% filter....

the ea must enter only when the w% signal level is broken, so when the buy signal is active and (buy case here...) the W% break from down to up level -90 it enter on it.... the opposite for sell condition

True story...

I don't fully understand the question 😕 Maybe you are asking for this: http://prntscr.com/czd7m3

When you have x>, this means that the Condition block does 2 checks - one > for the current candle and another < for the previous candle. More info here: https://fxdreema.com/demo/mt4-crossover-indicators This means that the x> state... I mean the time period where both checks are true... can be up to 1 candle long. When that candle is closed, this x> is no more true. While if you use >, this remains true for all candles where one of the lines is above the other, until they cross.

But because x> remains true for multiple ticks (while the current exists), "Once per bar" is used to catch only the first one.

If you have 2 blocks with different indicators connected one after another and if x> (or x<) is used, then better don't expect both crossovers to happen at the same candle. Instead, leave x> (or x<) only in one Condition and in the other use > or <. You know, if now MAx is > than MAy, this means that MAx crossed MAy some time ago.

There is another kind of crossover as well - https://fxdreema.com/demo/mt4-price-vs-indicator

Invited to try EA !

Step 1 > Load history in MT4 (2016- 2016.10 month)

Stept 2 > Start optimize SL & TP parametr

Best result go test

EA for test attached

Different means "not equal to", the opposite of "!=". These is no option to check that a value is between two limits in "Condition". Well, you can try "Indicator moves within limits", which I think with proper settings can do that

I missed to answer to this...

I don't know. The current prices are part of a straight line. I basically decided what to be the lowest price and what to be the highest price, and then I got the rest from the line that connects both. The longer the period, the cheaper the price (for each 1 month). Now look what would be the prices for 1 week and 1 day: http://prntscr.com/cpi4sk I think they are relatively expensive. I also don't understand why so many people prefer the currently most-expensive price anyway ($19 for 1 month) 🙂
Also, to be honest, almost from the beginning I was thinking about rising the prices, but they are still low (in my opinion) 🙂

+15pips is not a valid for "double" type variable (constant or whatever) at all. "double" variables - the values can be ONLY numeric values with floating point, such as 1.2345 or 2882.38387.

The value can be something like 0.0015 and then in "Adjust" you can put +ConstantName
The problem is that 0.0015 is a fixed number. Someone would recommend to write +toPips(ConstantName) and it will work, but this function is a custom function made by me, and at some point I may decide to change it or remove it

I'm trying to create a strategy to operate in graphics 5 minutes, I wanted the robot to operate during the day and make some points, but never leave negative. What indicators would be better ?? What combination do I pick up a few points and make few operations? Google translator, sorry do not know English! 😁

I believe it's you I just wrote an e-mail to. Basically, use the Adjust field in "Condition" block when you compare prices, or work with pending orders.