(binned per thread starter’s request) Custom Indicators for TMA-A

R4M RSX Exit Indicator (R4M-RsxExit.ex4)

The RSX Exit indicator is based on the RSX indicator I found here:
https://www.mql5.com/en/code/7204

RSX (and R4M-RsxExit) are variations of RSI -- which is intended to detect when a currency is overbought or oversold. It is easy to implement and when used as a signal to Exit it seems to be fairly accurate. I will be using this algorithm as the Exit condition in SpikeHunter.



In the screen shot above I've cherry-picked a trade to show how I intend to use this indicator inside SpikeHunter. The purple dot (and blue vertical line) mark a SELL Entry. The red vertical line shows where the slope of the RSX indicator is '0', indicating that oversold has exhausted and the price will likely go up again.

A word about using TakeProfit versus using an Exit condition...
TakeProfit is convenient because it is handled by your broker. All you need to do is press a BUY/SELL button and you can then walk away or even turn off your computer. However, the down-side to TP is that if the signal is a false positive then it will probably be your SL that closes the trade. Using an Exit condition softens the blow of a false positive. It also may allow a true signal to run longer than if you had used a fixed TP. The down-side to using an Exit condition is that the indicator (or EA) must continuously monitor the broker data for the pair / TF used to open a trade -- i.e. it must always be attached to the same chart the trade was opened on. If you were to switch to a different pair or TF then the indicator (or EA) would be monitoring the wrong data.

R4M BD ADR Dashboard EA (R4M-BD-ADR-DashboardEA.ex4)

R4M-BD-ADR-DashboardEA is an alert and trading dashboard Expert Advisor that uses the R4M-BD-ADR indicator. The R4M-BD-ADR indicator must be installed for this dashboard to work.



The dashboard is a "work-in-progress" and I do not consider it a polished piece of software. But it is functional and I hope some find it useful. If nothing else it can be used as a glorified Alert to let you know when there is a new BD signal.

The dashboard EA is passive -- that is, it does not generate signals and it will not open trades without you pushing a button.

The dashboard EA is easy to use -- simply attach it to a new chart -- any symbol will do. However, the time frame is important. If you wish to monitor the BD indicator on the D1 time frame then you will need to attach the dashboard EA to a D1 chart.

The dashboard EA monitors the symbols in your Market Watch window -- so, if you wish to monitor 28 pairs then make sure those are shown in your Market Watch window.

The dashboard EA updates every time it receives a new tick. If you attach it to an exotic symbol that rarely receives ticks then the chart will rarely update. I recommend attaching it to EURUSD.

Though there is a maximum of 300 pairs that can be monitored at once -- I do not recommend that. The more pairs then, obviously, the longer it takes to update when a new tick arrives. For practical reasons I don't think I can fit more than 40 pairs on a chart.

The color coding matches with the R4M-BD-ADR indicator -- blue is for Bullish and purple for Bearish.

When used for opening trades, the dashboard uses 3 input settings:
1. Lot Size -- default is 0.01 lots
2. Stop Loss -- which is a fraction of that symbol's ADR (default is 0.5)
3. Take Profit -- also a fraction of that symbol's ADR (default is 0.25)

Though you can manually trade directly from the dashboard -- keep in mind it is "hot off the press". So, before pushing BUY or SELL buttons you should visually confirm trade signals by also using the R4M-BD-ADR indicator.

R4M ADR All Pairs (R4M-ADR-AllPairs.ex4)



R4M-ADR-AllPairs is a simple indicator that computes the ADR for all the symbols in your Market Watch window. The results can be sorted alphabetically, ascending or descending. Also, you can change the number of days used when computing the ADR.

MT4 Strategy Tester

I would like to go over some guidelines on how to use MT4 Strategy Tester with the BD EA -- which I will release in the next post. If you don't plan on using Strategy Tester then no need to read this -- but you'd be missing out on a lot. Plus, the more people who test then the better chance we have of flushing-out bugs and finding the best settings for different pairs.

If you are not familiar with using Strategy Tester then read-up on your own -- I'm not holding anyone's hand on how to use it. It shouldn't take more than 10 - 15 minutes to figure out how to use it for testing and optimizing settings. You can start with one of the simple EAs that MetaQuotes includes with your MT4 installation.



Tester Settings: Symbol: GBPNZD <== please stick with GBPNZD for now
Model: Open prices...
Use date: 2018.02.01 To: 2019.07.05 <== this will result in about 100 trades

Period: D1 (only) <== this version of the EA is locked to D1

A note about the data horizon (From: 2018.02.01 To: 2019.07.05) -- whenever back testing there are two things to consider:

1. Use recent data -- i.e. do NOT go back 20 years (unless you have a time machine). Since we trade in the present then we want to use data that reflects the present. If you include old, stale data then it will skew the results. Using old data does NOT make an EA more robust -- there is no evidence for that and, in fact, it's quite the contrary. People say that because we've been trained that more is better. But more old data is NOT better.

2. For results to be statistically significant we need a minimum sample size -- i.e. a minimum number of trades. 100 trades is a good number to shoot for. So I've chosen a data horizon that results in about 100 trades.

Inputs:

There are 3 important inputs -- NumberDaysADR, StopLoss fraction of ADR, and TakeProfit fraction of ADR. To include these in the optimization you'll need to check the CheckBox next to the parameter and provide Start, Step and Stop values. In the screen shot above I've shown examples of the values I've been using.




For the optimizer to work you'll need to check the 'Optimization' check box and then press the 'Start' button. It takes several minutes to complete, but when it is done you can view the results using the 'Optimization Results' tab.

Additional Notes:

1. In my hands there are some pairs I could not test using Strategy Tester -- i.e. the results were blank. I'm not sure why. Perhaps the data horizon is too big and my broker does not provide enough historical data -- I don't know. Perhaps someone here has an answer or can figure out why some pairs can be tested and others can not.

2. In the short-term I am primarily interested to see if people can reproduce my results using GBPNZD-D1. Once we agree that results are reproducible then we can move on to other types of testing.

3. The default settings for the EA where chosen based on my results for GBPNZD-D1. It is for sure these will not be the best results for other pairs:
NumberDaysADR: 20
StopLossFractionADR: 1.8
TakeProfitFractionADR: 0.4

4. There are two additional parameters of interest, but I would recommend sticking with the defaults for now:
MaxSpreadPoints: 40 -- ignores trade signal if spread is > 40 points
MaxOpenTrades: 10 -- ignores trade signal if there are already 10 open trades

5. Hidden Exit rule -- there is one additional Exit rule that I've incorporated that was not part of @bishopdotun's original set of rules. And that is if the strategy generates a SELL signal then it will close any BUY trades that are still open (and vice-versa).

R4M BD Trading EA (R4M-BD-ADR-EA.ex4)

This is the trading EA that relies on signals generated by R4M-BD-ADR indicator. To use the EA simply attach it to a D1 chart of the pair you wish to trade -- it MUST be a D1 chart.




There are a few settings to be aware of:

* The most important is 'StopLoss fraction of ADR'. The current value of 1.8 works well for GBPNZD, but probably is suboptimal for other pairs.
* 'TakeProfit fraction of ADR'
* 'NumberDaysADR' -- number of days used when computing the ADR (20 days is a good default value).
* 'MaxOpenTrades' -- if the number of open trades exceeds this value, then new signals are ignored.
* 'MaxSpreadPoints' -- if the current spread exceeds this value, then new signals are ignored.

It is best not to overload a chart running a trading EA with a bunch of indicators. Each chart is allotted a fixed time-slice of the CPU to perform all its computations. Once the time-slice has been exhausted then MT4 switches the time-slice to the next chart -- regardless whether the previous chart had finished all its computations. Each indicator you attach to a chart needs to perform its own computations and these count against the chart's allotted time-slice. Having said that, I think it is probably okay to attach the R4M-BD-ADR indicator to the chart so you can visually confirm that trades occur as expected.



The screen shot above shows an example of the BD EA and indicator running on the same chart.

R4M BD ADR All Pairs Trading EA (R4M-BD-ADR-AllPairsEA.ex4)

This is a trading EA that relies on signals generated by R4M-BD-ADR indicator. To use the EA simply attach it to a chart of the pair you wish to trade. D1 is the preferred time frame, but you are welcome to use others, as well.

R4M-BD-ADR-AllPairsEA.ex4 trades multiple pairs at the same time -- in contrast to the other trading EA (R4M-BD-ADR-EA.ex4) that trades only the pair associated with the chart it is attached to.

There are two ways to specify which pairs to trade -- all pairs listed in your Market Watch window, or manually entering them in the EA's input settings. From a practical point of view, I recommend not to exceed 28 pairs. The computations are fairly CPU-intensive and too many pairs will cause MT4 to freeze. Also, it is probably a good idea to run this in a separate MT4 session that does not include other charts. It is very easy to launch more than one MT4 session so this shouldn't be an issue.



There are a few settings to be aware of -- really not too complicated. However, please be aware these settings have a huge effect on the EAs performance. For optimal performance each pair and time frame will require different settings. When using the single-pair trading EA (R4M-BD-ADR-EA.ex4) you could apply calibrated settings that were specifically tailored for a particular pair / time frame. But for this "All Pair" EA we have to compromise and apply one set of parameters that will be used for all pairs. Perhaps in the future we can create a "Calibration Table" the EA can use to look-up the best parameters for each pair / time frame.

Below I will briefly describe the most important settings:

BD Time Frame:
The BD strategy is based on the centered TMA indicator which includes 3 bands -- middle, upper and lower. The BD Time Frame is the time frame used to compute these bands and will always be higher than your chart's time frame. For example, the default setup is to use a BD Time Frame of W1 on a D1 chart. Since a week includes 5 trading days, then that means every W1 "bar" will include 5 D1 bars. But since we are drawing bands, then that means every TMA horizontal step will cover 5 D1 bars.

Percent ADR:
The upper and lower TMA bands are drawn as offsets from the midline. This offset is computed as a percent of the ADR of the current pair. The default is 100%. So, for example, if a pair's ADR is 48 pips then the upper and lower bands should track with the midline -- 48 pips above and 48 pips below.

Number Days to Average ADR:
The ADR (Average Daily Range) is an average of the delta (i.e. difference) between each days High and Low over a period of days. The default is 20 days.

Exit Conditions:
Three types of Exit conditions (signals) are supported: Crossing the midline, crossing the opposite band, closing above / below the midline. The default is "crossing the midline".

Apply Momentum Filter:
I've adapted the momentum filter from the SpikeHunter indicator to also work with this EA. It is a combination of two momentum indicators -- @Nih98's FX RSI indicator plus Stochastic momentum index (SMI). The default for this parameter is 'false'.

Lot Size:
Self explanatory. The default is 0.01.

StopLoss Fraction ADR:
The StopLoss is calculated as a fraction of the current pair's ADR (in pips).

TakeProfit Fraction ADR:
Similarly, the TakeProfit is calculated as a fraction of the current pair's ADR (in pips).

Using iCustom to access BUY, SELL and EXIT signals from the R4M-BD-ADR.ex4 indicator:


Below is an example of how the EAs access signals from the R4M-BD-ADR indicator. Please note this is accurate as of 2019-07-12, but could change in the future.

enum ENUM_EXIT_CONDITION {
EXIT_CROSS_MIDLINE = 101, // Exit when price crosses midline
EXIT_CROSS_OPPOSITE_BAND = 102, // Exit when price crosses opposite band
EXIT_CLOSE_ABOVE_MIDLINE = 103 // Exit when price closes above / below midline
};

#define INDEX_EXPORTED_BUY (15)
#define INDEX_EXPORTED_SELL (16)
#define INDEX_EXPORTED_EXIT (17)


//+------------------------------------------------------------------+
//| |
//+------------------------------------------------------------------+
string g_strCustomPath_BishopDotun = "R4M-BD-ADR";
bool CustomValue_BishopDotun(string strSymbol, int iPeriod, int shift, int iPercentADR, int& iExportedBUY, int& iExportedSELL, int& iExportedEXIT,
int iMaxBars = 100, int iNumberOfDaysToAverage=20, ENUM_EXIT_CONDITION eWhichExitCondition=EXIT_CROSS_MIDLINE, ENUM_BD_TIMEFRAMES eBDTimeFrame=BD_TF_10080,
bool bApplyMomentumFilter=false)
{
string strMessage = "";

strMessage = StringFormat("*** ENTERING iCustom | %s", WindowExpertName());
// Print(strMessage);

ResetLastError();

iExportedBUY = (int)iCustom(strSymbol, iPeriod /*timeframe*/, g_strCustomPath_BishopDotun,
"", eBDTimeFrame, iPercentADR, iMaxBars, iNumberOfDaysToAverage, eWhichExitCondition, bApplyMomentumFilter,
INDEX_EXPORTED_BUY, shift);

iExportedSELL = (int)iCustom(strSymbol, iPeriod /*timeframe*/, g_strCustomPath_BishopDotun,
"", eBDTimeFrame, iPercentADR, iMaxBars, iNumberOfDaysToAverage, eWhichExitCondition, bApplyMomentumFilter,
INDEX_EXPORTED_SELL, shift);
iExportedEXIT = (int)iCustom(strSymbol, iPeriod /*timeframe*/, g_strCustomPath_BishopDotun,
"", eBDTimeFrame, iPercentADR, iMaxBars, iNumberOfDaysToAverage, eWhichExitCondition, bApplyMomentumFilter,
INDEX_EXPORTED_EXIT, shift);
// if (iExportedEXIT > 0)
// {
// strMessage = StringFormat("*** ExportEXIT iCustom | %s | iExportedEXIT: %d | shift: %d", WindowExpertName(), iExportedEXIT, shift);
// Print(strMessage);
// }
int iLastError = GetLastError();
if (0 != iLastError)
{
// NOTE: 4072 ==> "Cannot load custom indicator"
strMessage = StringFormat("*** [FAILED]: %s: %s: ErrorCode: %d: -- %s",
"CustomValue_BishopDotun", strSymbol, iLastError, ErrorDescription(iLastError));
Print(strMessage);
Alert(strMessage);
return (false);
}

return (true);
}

R4M BD LTF Indicator (R4M-BD-LTF.ex4)
R4M Consecutive Candles Indicator (R4M-ConsecutiveCandles.ex4)
R4M Fractals Indicator (R4M-TTFractals.ex4)

R4M-BD-LTF.ex4 is a variation of the R4M-BD-ADR.ex4 primarily intended for use at lower time frames (LTFs). R4M-BD-LTF differs from R4M-BD-ADR in that its Entry signals are generated by fractals and / or consecutive candles (CC). This has two benefits:

(a) The combination of a spike above / below a band plus a fractal or consecutive candles that confirm a reversal provides added confluence. At lower time frames there is a higher risk of false signals caused by "waterfall" price movements. Waterfalls could partially be avoided using a momentum-type filter, but fractals and / or consecutive candles offer an alternative and, perhaps, better solution.

(b) At lower time frames we typically see clusters of Entry signals when using the R4M-BD-ADR indicator. The LTF version that uses fractals and / or consecutive candles helps to thin these out.

The 'Which_LTF_Entry' parameter controls whether fractals and / or consecutive candles are used to generate Entry signals. You can choose to use one or the other or both. Using both does not increase the strictness of the Entry signals. The two Entry signals are mutually exclusive and operate independently of one another. Sometimes the Entry singles overlap, sometimes they don't. My recommendation is to use both since this will generate a few more Entry signals than using only one.

I've also included the stand-alone indicators R4M-TTFractals.ex4 and R4M-ConsecutiveCandles.ex4. I adapted their algorithms for use in R4M-BD-LTF.ex4. You may find them useful in trouble shooting when you have questions about the Entry signals generated by R4M-BD-LTF.ex4.

Below are screen shots of the R4M-BD-LTF indicator using both fractals and consecutive candles, fractals only and consecutive candles only.

R4M-TTFractals-Plus-ConsecutiveCandles.ex4 is a standalone indicator that combines BOTH TTFractals and ConsecutiveCandles in a single indicator. My purpose in creating this indicator is to show that though their algorithms are completely different, the TTFractals and ConsecutiveCandles indicators can be equally effective in identifying good Entry signals.

The purple and blue dots are the Entry signals created by the TTFractals algorithm. The green and red arrows are the Entry signals created by the ConsecutiveCandles indicator.

BDX Trading Strategy

The BDX strategy was architected by @bishopdotun and its rules implemented in software by @robots4me. The BDX strategy is a variation of an earlier version -- the BD strategy. The rules for BDX are very similar to BD and, so, performance should be similar.

The BDX Strategy includes 4 software components -- one indicator and three EAs.

R4M-BDX-ADR.ex4 -- this is indicator work horse. The EA's get their signals from the indicator.
R4M-BDX-DashboardEA.ex4 -- dashboard EA for manual trading
R4M-BDX-EA.ex4 -- single pair, auto-trading EA
R4M-BDX-AllPairsEA.ex4 -- multi-pair, auto-trading EA

The software can be downloaded from the other thread -- "Custom Indicators for TMA-ADR Reversal Trading and BBMA" (https://www.forexfactory.com/showthread.php?t=920925). All indicators are bundled in a single *.zip file -- R4M-BDX_<version>.zip. Indicators must be installed under MT4's 'Indicators' folder and EAs must be installed under the 'Experts' folder. To avoid version skews, please make sure that all indicators and EAs come from the same *.zip file.

The BDX strategy is a reversal trading strategy -- that is, an extreme price is detected and you then "trade away" (i.e. open a trade in the opposite direction). Like many reversal trading strategies BDX relies on an "envelope-type" indicator with a midline. We've chosen to use a Centered TMA as our "envelope-type" indicator -- though it's certainly possible to use others. Many reversal trading strategies that use an "envelope-type" type indicator draw multiple bands above and below the midline. These bands are used to rank extreme prices. The more extreme the price the more likely it will revert back to the midline -- i.e. "fair value", equilibrium price.

The BDX strategy distinguishes itself from other reversal strategies in that it uses only one upper and lower band -- offset by the ADR from the midline. BDX explicitly defines an extreme price as one that pokes its head above or below the upper or lower band. That's it -- there is only one rule -- an extreme price must break an upper or lower band, and then you trade away. No other indicators are required. No other indicators are used by the EAs. The magic sauce is the upper and lower bands are offset by the ADR from the midline.



Referring to the chart above:

Entries: Blue dots are BUY signals and purple dots are SELL signals.
Exits: The 'x's are Exit signals. Red 'x's mean close either BUY or SELL trades. Blue 'x's mean close BUY trades. Purple 'x's mean close SELL trades.

With any trading strategy it always comes down to Entries and Exits. If someone describes a trading strategy but neglects to point out Entries and Exits -- either intentionally or unintentionally -- run away in the other direction as fast as you can. Without Entries and Exits it is just pretty pictures drawn using historical data. Without Entries and Exits there is no trading. With the BDX strategy @bishopdotun and I have tried to be as transparent as possible. We tell you everything -- nothing is hidden. Not only do we want for the strategy to be successful but, also, for you to understand exactly how it works. No "black boxes". To this end, the BDX clearly marks candidate Entries and Exits.




Additional Details:

Entries: We use Heiken Ashi transitions. If a Heiken Ashi transition occurs above / below an ADR band then that is marked as a candidate Entry signal.
Exits: And Exit signal is marked when the price crosses the midline OR there is a HMA transition -- whichever comes first. Midline crossings are much more common, though HMA transitions do offer a little bit of protection.

StopLoss and TakeProfit: These are really the only two settings you need to calibrate according to your trading preference. The default values of 1.8xADR for StopLoss and 0.4xADR for TakeProfit are good starting points.

The Centered TMA for BDX differs in three ways compared to the one used for BD:
(1) It does not repaint.
(2) It is "curvilinear", rather than horizontal (un-interpolated)
(3) It uses the same time frame as the chart to which it is attached.

The default value for the 'Extreme Price (% ADR)' setting is '100'. Though the value can be changed, we highly recommend that you leave it at '100' -- otherwise you lose the "edge" that ADR extreme price provides and BDX becomes YARTS (Yet-Another-Reversal-Trading-System). Since the BDX strategy is so simple and robust then other settings will still "work", but you haven't discovered anything new. All you'd be doing is crippling the edge that BDX provides.

You can attach the BDX indicator to any time frame. As long as you keep 'Extreme Price (%ADR)' at '100' then the lower time frame will display more signals. For example, suppose there is a signal on an H4 and you zoom-in to M15, then you are likely to see several signals (since H4 compresses 16 M15 bars). Again -- for more signals trade at a lower time frame, and for fewer signals trade at a higher time frame.



I'd like to draw your attention to several settings:

'TMA Time Frame' -- The time frame used for the Centered TMA is the same as the current chart. The setting has only one option "Current Time Frame" and can not be changed.

'Extreme Price (% ADR)' -- As mentioned above we recommend using the default value of '100', but this can be changed.

'MinPercentAdrCup' -- In the BD strategy the default was '70' and here I've changed it to '0'. Since the Heiken Ashi transitions create such nice Entry points then my impression is if you set it too strict then the strategy may ignore too many candidate Entries that would have resulted in winning trades. Also, the best value probably depends on your broker's server time. So, to be honest, I'm not so sure about this one.

'BDX Entry Type' -- only one option -- 'Heiken Ashi transitions'.

'BDX Exit Type' -- only one option -- 'Crosses midline OR HMA transition'


To be continued in next post...

R4M-BDX-EA.ex4 -- single pair, auto-trading EA

This is the trading EA that relies on signals generated by R4M-BDX-ADR indicator -- the R4M-BDX-ADR.ex4 indicator must be present in the "Indicators" folder. To use the EA simply attach it to a chart of the pair you wish to trade. Though it works on any chart, we recommend H4.



There are a few settings to be aware of:

* TMA-related settings were mentioned above.
* 'StopLoss fraction of ADR'.
* 'TakeProfit fraction of ADR'.
* 'MaxOpenTrades' -- if the number of open trades exceeds this value, then new signals are ignored.
* 'MaxSpreadPoints' -- if the current spread exceeds this value, then new signals are ignored.

It is best not to overload a chart running a trading EA with a bunch of indicators. Each chart is allotted a fixed time-slice of the CPU to perform all its computations. Once the time-slice has been exhausted then MT4 switches the time-slice to the next chart -- regardless whether the previous chart had finished all its computations. Each indicator you attach to a chart needs to perform its own computations and these count against the chart's allotted time-slice.


Strategy Tester

A useful feature I've added for the single-trading BDX EA are visual markings. This allows you to run the EA in Strategy Tester using "Visual Mode" and see how trades align with the visual markings. Please, please read my earlier post about Strategy Tester's reliability -- or lack there of. The purpose of displaying visual markings is (a) to confirm the code is doing the right thing, and (b) to help people better understand how the rules work.



To be continued in next post...

R4M BDX Dashboard EA (R4M-BDX-DashboardEA.ex4)

R4M-BDX-DashboardEA is an alert and trading dashboard Expert Advisor that uses the R4M-BDX-ADR indicator. The R4M-BDX-ADR indicator must be installed in the "Indicators" folder for this dashboard to work.



The dashboard EA is passive -- that is, it does not generate signals and it will not open trades without you pushing a button.

The dashboard EA is easy to use -- simply attach it to a new chart -- any symbol will do. However, the time frame is important. If you wish to monitor the BDX indicator on the H4 time frame then you will need to attach the dashboard EA to an H4 chart.

The dashboard EA monitors the symbols in your Market Watch window or you can manually enter which pairs to trade.

The dashboard EA updates every 2 seconds -- updating the next 2 pairs in the list.

The color coding matches with the R4M-BDX-ADR indicator -- blue is for Bullish and purple for Bearish.

When used for opening trades, the dashboard uses 3 input settings:
1. Lot Size -- default is 0.01 lots
2. Stop Loss -- a fraction of that symbol's ADR (default is 1.8)
3. Take Profit -- a fraction of that symbol's ADR (default is 0.4)

There are a few additional settings that I'd like to point out:

'Use FIFO to close orders':
This setting would only be of interest to US clients. US brokers must follow NFA regulations -- which include (a) no hedging, and (b) trades must be closed in the same order they were opened (FIFO = "First-In-First-Out"). When this setting is enabled then the EA will attempt to close trades in the order in which they were opened. Furthermore, if that fails then it will attempt "brute force" closing of all orders. In the end I think all trades will be closed, but MT4 may report FIFO errors along the way.

'Pairs to Trade':
The default is to use the 18 pairs listed in this setting. However, if you wish to trade all pairs in your Market Watch window then change the setting 'Use Market Watch for pairs to trade' from 'false' to 'true'.

'Toggle AutoExit':
The default is 'false' -- but when enabled this feature will close open trades that meet the BDX Exit Type of "Crosses midline OR HMA transition". Furthermore, the only trades that will be closed are those that were opened by the dashboard EA.

To be continued in next post...

R4M BDX All Pairs Trading EA (R4M-BDX-AllPairsEA.ex4)

This is a trading EA that relies on signals generated by R4M-BDX-ADR indicator. To use the EA simply attach it to a chart of the pair you wish to trade. H4 is the preferred time frame.

R4M-BDX-AllPairsEA.ex4 trades multiple pairs at the same time -- in contrast to the other trading EA (R4M-BDX-EA.ex4) that trades only the pair associated with the chart it is attached to.

There are two ways to specify which pairs to trade -- all pairs listed in your Market Watch window, or manually entering them in the EA's input settings. From a practical point of view, I recommend not to exceed 28 pairs. The computations are fairly CPU-intensive and too many pairs will cause MT4 to freeze. Also, it is probably a good idea to run this in a separate MT4 session that does not include other charts. It is very easy to launch more than one MT4 session so this shouldn't be an issue.

hi is it possible to modify like indicator draw high-low line only price break previous swing or high-low i mean significatt move (attached image)