MQL5 Wizard – Trade Signals Based on Bullish/Bearish Meeting Lines + MFI – EA MetaTrader 5

The MQL5 Wizard allows creating ready-made Expert Advisors based on the Standard library classes delivered together with the client terminal (see Creating Ready-Made Expert Advisors in MQL5 Wizard for the details). It allows to check your trade ideas quickly, all you need is to create your own trading signals class. The structure of this class and example can be found in the article MQL5 Wizard: How to Create a Module of Trading Signals.

The generic idea is the following: the class of trading signals is derived from CExpertSignal, the next, it’s necessary to override the LongCondition() and ShortCondition() virtual methods with your own methods.

There is a book “Strategies of best traders” (in Russian), there are many trading strategies are considered there, we will focus on reversal candlestick patterns, confirmed by Stochastic, CCI, MFI and RSI oscillators.

The best way is to create the separate class, derived from CExpertSignal for checking of formation of candlestick patterns. For confirmation of trade signals, generated by candlestick patterns, it’s sufficient to write the class, derived from CCandlePattern and add the necessary features (for example, confirmation by oscillators) there.

Here we will consider the signals, based on “Bullish/Bearish Meeting Lines” reversal candlestick patterns, confirmed by MFI (Market Facilitation Index) indicator. The module of trade signals is based on the CCandlePattern class, it’s simple example of its use for creation of trade signals with candlestick patterns.

1. “Meeting Lines” reversal candlestick patterns

1.1. Bullish Meeting Lines

The pattern consist of two candlesticks (bearish and bullish) with equal (or very close) close prices. The body of two candlesticks must be greater than average body length.

The “Bullish Meeting Lines” pattern indicates the reversal of a downward trend.

Fig. 1. “Bullish Meeting Lines” pattern 

The recognition of “Bullish Meeting Lines” pattern is implemented in CheckPatternCheckPatternBullishMeetingLines() method of CCandlePattern class:

//+--------------------------------------------------------------------+
//| Checks formation of "Bullish Meeting Lines" candlestick pattern    |            
//+--------------------------------------------------------------------+
bool CCandlePattern::CheckPatternBullishMeetingLines()
  {
//--- Bullish Meeting Lines
   if((Open(2)-Close(2)>AvgBody(1))              && // long black
     ((Close(1)-Open(1))>AvgBody(1))             && // long white
      (MathAbs(Close(1)-Close(2))<0.1*AvgBody(1)))   // doji close
      return(true);
//---
   return(false);
  }

1.1. Bearish Meeting Lines

The pattern consist of two candlesticks (bullish and bearish) with equal (or very close) close prices. The body of two candlesticks must be greater than average body length.

The “Bearish Meeting Lines” pattern indicates the reversal of a downward trend.

Fig. 2. “Bearish Meeting Lines” pattern

The recognition of “Bearish Meeting Lines” pattern is implemented in CheckPatternBearishMeetingLines() method of CCandlePattern class:

//+--------------------------------------------------------------------+
//| Checks formation of "Bearish Meeting Lines" candlestick pattern    |
//+--------------------------------------------------------------------+
bool CCandlePattern::CheckPatternBearishMeetingLines()
  {
//--- Bearish Meeting Lines
   if((Close(2)-Open(2)>AvgBody(1))             && // long white
     ((Open(1)-Close(1))>AvgBody(1))            && // long black
      (MathAbs(Close(1)-Close(2))<0.1*AvgBody(1)))  // doji close
      return(true);
//---
   return(false);
  }

2. Trade signals, confirmed by MFI indicator

The trading signals to open long or short position must be confirmed by MFI indicator. The value of MFI indicator must be lower than 40 (for long positions) or greater than 60 (for short positions).

The closing of opened position depends on the values of MFI indicator. It can be done in 2 cases:

1. if MFI has reached the opposite critical level (70 for long position and 30 for short position)
2. if the reverse signal isn’t confirmed (when MFI indicator reaches the following levels: 30 for long position and 70 for short position)

Figure 3. The “Bearish Meeting Lines” pattern, confirmed by MFI indicator

• int CML_MFI::LongCondition() – checks conditions to open long position (returns 80) and close of the short position (returns 40);
  
• int CML_MFI::ShortCondition() – checks conditions to open short position (returns 80) and close of the long position (returns 40).

2.1. Open long position/Close short position

1. The formation of “Bullish Meeting Lines” pattern must be confirmed by MFI indicator: MFi(1)<40 (the value of MFI indicator of the last completed bar must be less than 40).

2. The short position must be closed if MFI indicator has crossed upward the critical levels (70 or 30).

//+------------------------------------------------------------------+
//| Checks conditions for entry and exit from market                 |
//| 1) Market entry (open long position, result=80)                  |
//| 2) Market exit (close short position, result=40)                 |
//+------------------------------------------------------------------+
int CML_MFI::LongCondition()
  {
   int result=0;
//--- idx can be used to determine Expert Advisor work mode
//--- idx=0 - in this case EA checks trade conditions at each tick
//--- idx=1 - in this case EA checks trade consition only at news bars
   int idx   =StartIndex();
//--- checking of conditions to open long position
//--- formation of Bullish Meeting Lines pattern and MFI<40
  if(CheckCandlestickPattern(CANDLE_PATTERN_BULLISH_MEETING_LINES) && (MFI(1)<40))
     result=80;
//--- checking of conditions to close short position
//--- signal line crossover of overbought/oversold levels (upward 30, upward 70)
  if(((MFI(1)>30) && (MFI(2)<30)) || ((MFI(1)>70) && (MFI(2)<70)))
     result=40;
//--- return result
   return(result);
  }

2.2. Open short position/Close long position

1. The formation of “Bearish Meeting Lines” pattern must be confirmed by MFI indicator: MFI(1)>60 (the value of MFI indicator of the last completed bar must be greater than 60).

2. The long position must be closed if MFI indicator has crossed upward/downward the critical levels (70 or 30).

//+------------------------------------------------------------------+
//| Checks conditions for entry and exit from market                 |
//| 1) Market entry (open short position, result=80)                 |
//| 2) Market exit (close long position, result=40)                  |
//+------------------------------------------------------------------+
int CML_MFI::ShortCondition()
  {
   int result=0;
//--- idx can be used to determine Expert Advisor work mode
//--- idx=0 - in this case EA checks trade conditions at each tick
//--- idx=1 - in this case EA checks trade consition only at news bars
   int idx   =StartIndex();
//--- checking of conditions to open short position
//--- formation of Bearish Meeting Lines pattern and MFI>60
  if(CheckCandlestickPattern(CANDLE_PATTERN_BEARISH_MEETING_LINES) && (MFI(1)>60))
     result=80;
//--- checking of conditions to close long position
//--- signal line crossover of overbought/oversold levels (upward 70, downward 30)
   if(((MFI(1)>70) && (MFI(2)<70)) || ((MFI(1)<30) && (MFI(2)>30)))
     result=40;
//--- return result
   return(result);
  }

2.3. Creating Expert Advisor using MQL5 Wizard

To create an Expert Advisor launch MQL5 Wizard:

Fig. 4. Creating Expert Advisor using MQL5 Wizard

Let’s specify the name of the Expert Advisor:

Fig. 5. General properties of the Expert Advisor

After that we need to select the modules of trade signals used.

Fig. 6. Signal properties of the Expert Advisor

In our case we use only one module of trade signals.

Adding the “Signals based on Bullish/Bearish Meeting Lines by MFI” module of trading signals:

Fig. 7. Signal properties of the Expert Advisor

Module of trade signals added:

Fig. 8. Signal properties of the Expert Advisor

You can select any trailing properties, but we will use “Trailing Stop not used”:

Fig. 9. Trailing properties of the Expert Advisor

Concerning the money management properties, we will use “Trading with fixed trade volume”:

Fig. 10. Money management properties of the Expert Advisor

By pressing the “Finish” button, we will get the code of the generated Expert Advisor, located in Expert_AML_MFI.mq5, it will be saved in terminal_data_folder\MQL5\Experts\.

The default input parameters of the generated Expert Advisor:

//--- inputs for main signal
input int            Signal_ThresholdOpen   =10;     // Signal threshold value to open [0...100]
input int            Signal_ThresholdClose  =10;     // Signal threshold value to close [0...100]
input double         Signal_PriceLevel      =0.0;    // Price level to execute a deal
input double         Signal_StopLevel       =50.0;   // Stop Loss level (in points)
input double         Signal_TakeLevel       =50.0;   // Take Profit level (in points)

must be replaced to:

//--- inputs for main signal
input int            Signal_ThresholdOpen   =40;     // Signal threshold value to open [0...100]
input int            Signal_ThresholdClose  =20;     // Signal threshold value to close [0...100]
input double         Signal_PriceLevel      =0.0;    // Price level to execute a deal
input double         Signal_StopLevel       =0.0;    // Stop Loss level (in points)
input double         Signal_TakeLevel       =0.0;    // Take Profit level (in points)

The Signal_ThresholdOpen/Signal_ThresholdClose input parameters allow to specify threshold levels for open and close of positions.

In code of the LongCondition() and ShortCondition() methods of the trade signals class we have specified the fixed values of the threshold:

• Open position: 80;
• Close position: 40.
  

The values of  Signal_StopLevel and Signal_TakeLevel input parameters is set to 0, it means that closing of the positions will be done only when closing conditions will be true.

2.4. History backtesting results

Let’s consider backtesting of the Expert Advisor on historical data (EURUSD H1, testing period: 2000.01.01-2011.03.16, PeriodMFI=12, MA_period=4).

In creation of Expert Advisor we used the fixed volume (Trading Fixed Lot, 0.1), Trailing Stop algorithm is not used (Trailing not used).

Fig. 11. Testing results of the Expert Advisor, based on Bullish/Bearish Meeting Lines + MFI

The best set of input parameters can be found using the Strategy Tester of MetaTrader 5 client terminal.

The code of the Expert Advisor, created by MQL5 Wizard is attached in expert_aml_mfi.mq5.