Let's discuss this idea.
Imagine you know the future (like Sai ;) and want to tell EA: "don't open BUYs under this level" or "open new BUYs only above this trend line".
How do you see it?
How it can be improved?
How would you rate the customer service you received?
Satisfaction mark by Andrey Khatimlianskyi 1 year ago
Add a comment about quality of support you received (optional):
https://www.fxpip.one/tma-bands-strategy-in-forex-robot-mpgov3-2-5/ Could we implement CP to use TMA band strategy? This is also an efficient channel.
You can use it as a 3rd party indicator.
We also have TMA as a MA type in MA filter.
https://www.fxpip.one/tma-bands-strategy-in-forex-robot-mpgov3-2-5/ Could we implement CP to use TMA band strategy? This is also an efficient channel.
https://www.mql5.com/en/code/8016 Please reference the link above.
https://www.fxpip.one/tma-bands-strategy-in-forex-robot-mpgov3-2-5/ Could we implement CP to use TMA band strategy? This is also an efficient channel.
https://www.mql5.com/en/code/8016 Please reference the link above.
Looks great sir.
One doubt sir. Can we have these lines read from another indicator like pivot etc?
If they have some predefined names, yes. But if they names change dynamically, we will not be able to handle them.
I'm going to make it simple and universal.
Line name: uniq object name to work with
Work mode:
Distance: distance from the line to activate the filter.
For example, in Buy above mode, with Distance = 10 points, Buys will be allowed only if price >= line + 10 points. With Distance = -5, Buys will be allowed if price >= line - 5 points.
Distance calculation type: points / volatility
Reverse mode: reverse all signals (Buy below, Buy on cross DN).
Use closed bars only: analyze signals on bar close only.
TimeFrame for Use closed bars only mode.
Any suggestions?
Looks great sir.
One doubt sir. Can we have these lines read from another indicator like pivot etc?
The idea is to trade small range bound identities or whenever currency is moving in range bound zone.
Say for example, NGUSD, we will buy in grid/martingale as long as it is between 2 to 6. and sell between 6 to 10. And close the trades when reaches certain global profit. May be we need to be careful when the entity reaches the boundary and needs refinement/study further/SL.
Simply we can disable trades as desired based on the current price and enable martingale. But it does not help the backtest feature.
Hence calls for requirement of the filter with input as prices i.e. buy between a & b and sell between x & y.