Here's the new "Goblin" ea...little brother to Predator - page 2

New comment
 
Wackena:
pluto,

I was reading the Globin code and have a question. In the Turbo_JVEL part of the code, is the last part below correct. I see you have when trendtype=2 and trendtype=3, both trendtext="Weak Downtrend/Ranging".

When trendtype=3, should trendtext="Strong Uptrend";

UpTrendVal = iCustom(Symbol(), PERIOD_D1, "Turbo_JVEL",10,-100,0,0);

DnTrendVal = iCustom(Symbol(), PERIOD_D1, "Turbo_JVEL",10,-100,1,0);

TrendVal = (UpTrendVal + DnTrendVal);

if(TrendVal <= -0.1)

{

trendtype = 1;

TrendTxt = "Strong Downtrend";

}

if(TrendVal > -0.1 && TrendVal < 0)

{

trendtype = 2;

TrendTxt = "Weak Downtrend/Ranging";

}

if(TrendVal > 0 && TrendVal < 0.1)

{

trendtype = 2;

TrendTxt = "Weak Uptrend/Ranging";

}

if(TrendVal >= 0.1)

{

trendtype = 3;

TrendTxt = "Weak Downtrend/Ranging";

}
Wackena

Yes, good catch there. It should've said "Strong Uptrend".

I've attached a revised EA with the fix.

Files:
goblin.mq4  13 kb
 
Wackena:
bluto,

any suggested or preferred pairs for Goblin?

Wackena

Shouldn't matter. This EA should be able to handle any of them. It does seem to really "gobble" the pips during ranging periods.

 

In reviewing the Turbo_JEVL Indicator code, another question. The indicator has this code.

if ((Symbol()=="USDJPYm") || (Symbol()=="EURJPYm") || (Symbol()=="JPGBPYm"))

{

series = ((High[shift]+Low[shift]+Close[shift])/3);

} else {

series = ((High[shift]*100 + Low[shift]*100 + Close[shift]*100)/3);

}[/CODE]

Should the code be this for all JPY pairs and both Standard and Mini/Micro accounts. And there is a typo above, "JPGBPYm" should be "GBPJPYm"

[CODE]if ((Symbol()=="USDJPY") || (Symbol()=="USDJPYm") || (Symbol()=="EURJPY") || (Symbol()=="EURJPYm") || (Symbol()=="GBPJPY") || (Symbol()=="GBPJPYm") || (Symbol()=="CHFJPY") || (Symbol()=="CHFJPYm") || (Symbol()=="NZDJPY") || (Symbol()=="NZDJPYm") )

{

series = ((High[shift]+Low[shift]+Close[shift])/3);

} else {

series = ((High[shift]*100 + Low[shift]*100 + Close[shift]*100)/3);

}

Wackena

 
Wackena:
In reviewing the Turbo_JEVL Indicator code, another question. The indicator has this code.
if ((Symbol()=="USDJPYm") || (Symbol()=="EURJPYm") || (Symbol()=="JPGBPYm"))

{

series = ((High[shift]+Low[shift]+Close[shift])/3);

} else {

series = ((High[shift]*100 + Low[shift]*100 + Close[shift]*100)/3);

}[/CODE]

Should the code be this for all JPY pairs and both Standard and Mini/Micro accounts. And there is a typo above, "JPGBPYm" should be "GBPJPYm"

[CODE]if ((Symbol()=="USDJPY") || (Symbol()=="USDJPYm") || (Symbol()=="EURJPY") || (Symbol()=="EURJPYm") || (Symbol()=="GBPJPY") || (Symbol()=="GBPJPYm") || (Symbol()=="CHFJPY") || (Symbol()=="CHFJPYm") || (Symbol()=="NZDJPY") || (Symbol()=="NZDJPYm") )

{

series = ((High[shift]+Low[shift]+Close[shift])/3);

} else {

series = ((High[shift]*100 + Low[shift]*100 + Close[shift]*100)/3);

}
Wackena

Well aren't you just the little code scrutinizer!! LOL.

Actually, that code really makes no difference for the purposes of the EA call. That was a small mod I stuck in there to make the bars on the histogram larger because due to time scaling, they're hard to read on larger TF's. The underlying slope values are unaffected which is what the EA depends upon. In any event, attached is a modified version of the indicator to take into account either mini or standard accounts.

Files:
turbo_jvel.mq4  12 kb
 
bluto:
Well aren't you just the little code scrutinizer!! LOL. Actually, that code really makes no difference for the purposes of the EA call. That was a small mod I stuck in there to make the bars on the histogram larger because due to time scaling, they're hard to read on larger TF's. The underlying slope values are unaffected which is what the EA depends upon. In any event, attached is a modified version of the indicator to take into account either mini or standard accounts.

Thanks for the "..little.." comment. At my weight and height, I appreciate all the "little" comments I get.

Wackena.

 
Wackena:
Thanks for the "..little.." comment. At my weight and height, I appreciate all the "little" comments I get. Wackena.

Ooops....no harm intended.

 

Here is a years back test I did on Goblin.

Using euro$ 15m

30 TP

pips 10

no s/l

secure profit based on 30 pips per .1 lot used. So for .2 lots secure profit was 60.

max orders of 3.

and lot size of .2 for a 5k account.

the rest of the settings are default.

I am going to forward test it soon.

There was about 2 times durring the last year when the positions were held for about a month or mabe more. This happened when buy orders were placed near an extream high above 1.2900.

I would suggest adding an option to the settings for BUY only and SELL only. This way when it reaches an extream high(like now 1.2975) I would set it to sell only because its unlikely that the price will remain above 1.3000 for any peroid of time. But if a buy order is placed at this level the price can run all the way down to 1.1600 befor ever comming back to 1.3000.

So looking at long term charts and determining what the extreams are you can use buy and sell when price is near these extreams.

Dave

Files:
goblin_year.gif  8 kb
goblin_year.htm  321 kb
 
xxDavidxSxx:
Here is a years back test I did on Goblin.

Using euro$ 15m

30 TP

pips 10

no s/l

secure profit based on 30 pips per .1 lot used. So for .2 lots secure profit was 60.

max orders of 3.

and lot size of .2 for a 5k account.

the rest of the settings are default.

I am going to forward test it soon.

There was about 2 times durring the last year when the positions were held for about a month or mabe more. This happened when buy orders were placed near an extream high above 1.2900.

I would suggest adding an option to the settings for BUY only and SELL only. This way when it reaches an extream high(like now 1.2975) I would set it to sell only because its unlikely that the price will remain above 1.3000 for any peroid of time. But if a buy order is placed at this level the price can run all the way down to 1.1600 befor ever comming back to 1.3000.

So looking at long term charts and determining what the extreams are you can use buy and sell when price is near these extreams.

Dave

Good ideas there. Let's do it!

 
xxDavidxSxx:
Here is a years back test I did on Goblin.

Using euro$ 15m

30 TP

pips 10

no s/l

secure profit based on 30 pips per .1 lot used. So for .2 lots secure profit was 60.

max orders of 3.

and lot size of .2 for a 5k account.

the rest of the settings are default.

I am going to forward test it soon.

There was about 2 times durring the last year when the positions were held for about a month or mabe more. This happened when buy orders were placed near an extream high above 1.2900.

I would suggest adding an option to the settings for BUY only and SELL only. This way when it reaches an extream high(like now 1.2975) I would set it to sell only because its unlikely that the price will remain above 1.3000 for any peroid of time. But if a buy order is placed at this level the price can run all the way down to 1.1600 befor ever comming back to 1.3000.

So looking at long term charts and determining what the extreams are you can use buy and sell when price is near these extreams.

Dave

where i can see the max drawdown of ur margin?

 

I am sorry I have some problems when running the EA,platform IBFX,DEMO

any ideas about it ? Thanks!

00:37:24 Custom indicator Turbo_JRSX EURUSD,H1: removed

00:37:24 Custom indicator Turbo_JVEL EURUSD,Daily: removed

00:37:29 Custom indicator Turbo_JVEL EURUSD,Daily: loaded successfully

00:37:29 Custom indicator Turbo_JRSX EURUSD,H1: loaded successfully

00:37:32 Custom indicator Turbo_JRSX GBPUSD,H1: removed

00:37:32 Custom indicator Turbo_JVEL GBPUSD,Daily: removed

00:37:32 Custom indicator Turbo_JVEL GBPUSD,Daily: loaded successfully

00:37:32 Custom indicator Turbo_JRSX GBPUSD,H1: loaded successfully

00:37:32 TradeDispatcher: trade context is busy

00:37:34 '1308699': order sell 0.01 USDJPY opening at 116.1000 sl: 0.0000 tp: 115.7000 failed [Trade is disabled]

00:37:36 '1308699': instant order buy 0.10 GBPUSD at 1.9163 sl: 0.0000 tp: 1.9203

00:37:37 '1308699': order buy 0.10 GBPUSD opening at 1.9163 sl: 0.0000 tp: 1.9203 failed [Trade is disabled]

00:37:42 Custom indicator Turbo_JRSX USDJPY,H1: removed

00:37:42 Custom indicator Turbo_JVEL USDJPY,Daily: removed

00:37:52 Custom indicator Turbo_JRSX USDCHF,H1: removed

00:37:52 Custom indicator Turbo_JVEL USDCHF,Daily: removed

00:37:59 Custom indicator Turbo_JVEL USDJPY,Daily: loaded successfully

00:37:59 Custom indicator Turbo_JRSX USDJPY,H1: loaded successfully

00:37:59 '1308699': instant order sell 0.10 USDJPY at 116.1100 sl: 0.0000 tp: 115.7100

00:37:59 '1308699': order sell 0.10 USDJPY opening at 116.1100 sl: 0.0000 tp: 115.7100 failed [Trade is disabled]

00:38:31 Custom indicator Turbo_JVEL USDCHF,Daily: loaded successfully

00:38:31 Custom indicator Turbo_JRSX USDCHF,H1: loaded successfully

00:38:48 TradeDispatcher: trade context is busy

00:38:49 TradeDispatcher: trade context is busy

00:38:50 TradeDispatcher: trade context is busy

00:38:56 '1308699': instant order buy 0.10 GBPUSD at 1.9162 sl: 0.0000 tp: 1.9202

00:39:16 TradeContext: ping error

00:39:20 '1308699': instant order buy 0.10 GBPUSD at 1.9160 sl: 0.0000 tp: 1.9200

00:39:23 '1308699': order buy 0.10 GBPUSD opening at 1.9160 sl: 0.0000 tp: 1.9200 failed [Trade is disabled]

00:40:30 '1308699': instant order buy 0.10 GBPUSD at 1.9162 sl: 0.0000 tp: 1.9202

00:40:31 '1308699': order buy 0.10 GBPUSD opening at 1.9162 sl: 0.0000 tp: 1.9202 failed [Trade is disabled]

00:40:36 '1308699': instant order buy 0.10 GBPUSD at 1.9163 sl: 0.0000 tp: 1.9203

00:40:37 '1308699': order buy 0.10 GBPUSD opening at 1.9163 sl: 0.0000 tp: 1.9203 failed [Trade is disabled]

123456789...99
New comment
Reason: