I've seen several EA's like this and not one of them was able to make money over the long haul. Blowing an account is inevitable with martingale style money management.

But I like the idea of increasing/decreasing lot sizes based on the number of winners/losers in a row. Say 3 winners in a row, increase lot size; 3 losers in a row, decrease lot sizes.

Also, maybe a better entry method would make this system more profitable. There is an indicator called a squat bar that uses volume and range to show likely reversal points. It's very accurate about 70-80% of the time, but you have to pay a monthly fee for the software. I won't mention the name of the software here as I don't want to advertise it, but it's something to look into.

I was thinking of something along those same lines...keep it simple for the time shift challenged like me...I second the motion for a ServerOffset variable..I wish I knew how to do it myself. I'm not that far yet coding...the only thing better would be to have the code detect what it needs to and adjust automatically so the user doesn't have to mess it up.

I need some help. The BUY and SELL signals of Phoenix are generated by the following piece of code:

MA =iMA(NULL,MA_Timeframe,MA_Length,0,MODE_SMA,PRICE_ OPEN,0);
RVI=iRVI(NULL,0,10,MODE_MAIN,0)-iRVI(NULL,0,10,MODE_MAIN,1);

The MA is the heart of Phoenix and the RVI (Relative Vigor Index) is an additional signal. For a BUY, RVI needs to be > 0 and for a sell <0. I’m not happy with this because it’s far to simple. What I want is an additional signal that takes account of the trend. So no SELL if the trend is up and no BUY if the trend is down. I think this can be a major improvement.

I think a simple fast and slow EMA will do. I have made an indicator (PhoenixAdditionalIndicator) that makes it visible what this signal will do. If it’s red, only SELL’s are valid, green for BUY’s and yellow for BUY’s and SELL’s.

The indicator has the following settings (with the defaults I think will perform best):

The indicator is hard-coded for TF=15M!

SlowMAPeriod = 54;
The slow Moving Average
FastMAPeriod = 14;
The fast Moving Average
PriceConstant = 4;
PRICE_CLOSE = 0
PRICE_OPEN = 1
PRICE_HIGH = 2
PRICE_LOW = 3
PRICE_MEDIAN = 4
PRICE_TYPICAL = 5
PRICE_WEIGTHED = 6
EmaMode = 3;
Simple moving average, = 0
Exponential moving average =1
Smoothed moving average = 2
Linear weighted moving average = 3
Switch = 1.0;
The Switch defines the area where SELL and BUY signals are valid. Above +Switch only BUYS and below –Switch only SELLS.

Please try this indicator and give me some feedback about the default settings.

Attached Files

PhoenixAdditonalSignal.mq4 (3.4 KB, 226 views)

Hendrick, I still seem to follow you on these boards.

Firebird v63g had a trend code in it, but wasn't used. I use it in a modiifed Firebird and it seems to work in stopping trades during trends.

extern int DVLimit = 10; // included by Renato

int TrendUp=0, Trenddown=0;
double iFXAnalyser(int FXA_Period, int mode, int shift)// Made local function by MrPip

if ( (iFXAnalyser(0,MODE_DIV,0)>DVLimit*Point && iFXAnalyser(0,MODE_SLOPE,0)>0 )) Trendup=1;
if ( (iFXAnalyser(0,MODE_DIV,0)<-DVLimit*Point && iFXAnalyser(0,MODE_SLOPE,0)<0 )) TrendDown=1;

Then pur "&& TrendUp !=1" following DealTime==1 in SELL trigger. And "&& TrendDown !=1" following DealTime==1 in BUY trigger.

Another method is to put a controlling factor for RV! to regulate trading activity.

extern double RVI_Factor =50; // 0-200 factor added to RVI value to regulate trading activity

Then in SELL and BUY triggers change RVI codes to "RVI<(0-(RVI_Factor*Point))" and "RVI>(0+(RVI_Factor*Point))" respectifully.

Another method is to put a second larger iMA envelope to tighten the active trading area to encourage trading during non-trending periods.

extern double PercentLimit = 0.15; // 2nd higher envelope (band) that stops trading.

int Safe2=0;
if ( myMA*(1+(PercentLimit/100))<=Bid || myMA*(1-(PercentLimit/100))>=Ask) Safe2=1;

Put "&& Safe2==1" in SELL and BUY triggers. You can attached a 2nd Firebird type Indicator set to PercentLimit to see active trading area.

I use one Firebird with all three filters and it averages ~50% less trades with ~90% win rate. The problem I have is the effect news has on the market. I've reported to this thread, that the last 4 Fridays had a big negative effect because of carry over open trades from Thursday. I am testing eliminating trading days and/or times to see if I can better manage the historic group loses.

Hendrick, this would be a further development of your trading time results chart and it would be a lot of work. But, I would like to have an EA that is 6/24 trading time programable and can survey its history, determine bad trading times & stop trading during these times, while maintaining a ghost trade history for these times. When historic ghost trades are again profitable, these times are re-established as good trading times. Wishful thinking, but I'm going to try to work on this or see if a coder can make this work. Right now, I use yor type of chart and try to do this manually.

Way too much typing. Well, this is what happens when you drink wine while on a thread. If all of this doesn't make sense, it's the wine's fault.

Wackena

Someone over at the Firebird thread suggested the following change:

instead of yours:

RVI=iRVI(NULL,0,10,MODE_MAIN,0)-iRVI(NULL,0,10,MODE_MAIN,1);

They changed it to:

RVI=iMACD(NULL,0,24,52,9,PRICE_CLOSE,MODE_MAIN,0)-iMACD(NULL,0,24,52,9,PRICE_CLOSE,MODE_MAIN,1);

They claimed it gave less false signals. Does that help?

Hi Hendrick,

when preparing to trade, I always look to a higher TF to see the trend forming.
Perhaps adding an additonal signal to Phoenix on the same 15 minutes TF is to limited?

Please have a look at the Multi-Time-Frame indicator XO.
You can have it set to any TF you like, but for Phoenix working on the M15 I
would have it set to H4 or maybe even D1.
Maybe it's most flexible to have it's TF setting in the inputs panel of the EA so it can be optimized along the way.

See attched picture with the indicator loaded twice; one for M15 and the other one for H4.

Regards,
Herbert

PS, I did change Firebird's iRVI to iMACD like Holyguy7 reminded today, but although it increased Firebird's speed in backtesting as a side-effect , I was under the impression that it did not remove the false signals.

Attached Images

mtf-xo.gif (19.4 KB, 336 views)

Attached Files

ZZ MTF XO A.mq4 (3.6 KB, 142 views)

Hey Holyguy,

For Phoenix version 2 I'm now using a SMA 120 and SMA 12 on a 15M chart. The main purpose is to prevent that Phoenix is placing trades against the trend. So far it seems to work OK.

Hey Herberth,

See my previous answer to Holyguy.

Phoenix version 2.

Changes:
removed divergence (I think its of no use)

removed Surf-orders (performance was not good)

replaced RVI by this piece of code:

AdMA=(iMA(NULL,PERIOD_M15,120,0,0,3,1) - iMA(NULL,PERIOD_M15,12,0,0,3,1));
if(Point==0.0001) {AdMA=AdMA*1000;}
if(Point==0.01) {AdMA=AdMA*10;}
if(AdMA > 1)
{
AdSELLSignal = true;
SortOrder = "SELLSignal";
}
if(AdMA < -1)
{
AdBUYSignal = true;
SortOrder = "BUYSignal";
}
if((AdMA > -1) && (AdMA < 1))
{
AdBUYSELLSignal = true;
SortOrder = "BUYSELLSignal";
}

The purpose of this code is to prevent that Phoenix is placing trades against the trend.

For testing:
Use the settings from the file. TF=15. All available pairs.

Attached Files

Phoenix_EA_v2_0.zip (3.0 KB, 292 views)

Thanks, put on charts.
are u make any backtest?