Holy Graily Bob 'n Grid

[Gertje]

Amazing results, too bad the USDCAD won't clear.
GBPJPY in the lead again, start to fall in love with this pair.....

GBPJPYMonthly.png

I will keep updating.

[Gertje]

GBPJPY closed twice on a high semafor, no low semafor shown -yet-......

GBPJPYM15.png

With this pair responseble for 60% of the profits, I start to wonder if we need more pairs at all....

[goldcourse]

GBPJPY closed twice on a high semafor, no low semafor shown -yet-......



With this pair responseble for 60% of the profits, I start to wonder if we need more pairs at all....

Gertje,

Can you kindly share your set file for v2n. Thanks

[Gertje]

Gertje,

Can you kindly share your set file for v2n. Thanks

Sure, attached.
Be aware there will be DD involved....

Global Prime - Empty4 4.png

Margin is beginning to be an issue, $2.000,- is the minimum for 0.01 lots in my opinion.
.

[PeterUK]

Greetings,

Steve: many thanks for your hard work in putting v1a together, a kind of gift received after my birthday on the Friday

I was having problems with the latest version 1a, trades would often trigger and then suddenly closes. As I've yet to discover the know how on how to fix this, I thought I learn from post 2 and do a bit of coding myself...

I've combined elements of v1a (trade comments and Bob's double MA with a twist) to v2n of HGB 'n Grid.

As you may have noticed, if you plot the 34 EMA Close on your charts, price action tend to bounce of this MA after a retracement... in an uptrend above the line, in a downtrend below the line... so I have used Bob's double MA to implement this... a kind of basic trend filter in helping us to identify a trend, letting HGI handle signals and then trading with it...

Results are attached running on a GP Demo account...

20160322 GP Demo.jpg

Pips gained were quite impressive from running overnight in the UK (focus on the Nett Pips). To help reduce floating DD I'd suggest using 0.01 lots for small accounts of less than USD$2000, and probably use 'SizeOfDollop' of USD$2000+ depending on how risk averse you are.

I've been running this on 7 Majors plus EA, EJ & GJ, 15min TF, AUD$3000 Demo, Global Prime, leverage 400:1 (you may not get this on a new GP live account, maybe 100:1 or 200:1, but you can increase it later).

Also using a VPS designed for traders close to the exchange, in my case CNS VPS... depends on how latency is important to you in filling trades orders at lower TF.

Thought I give back to the community, enjoy...

DISCLAIMER: Use at your own risk on a live account!

Regards,

Peter

UPDATE: If the latest HGB'nG v1c works well again you can use this set file instead of my modified EA. Main purpose was to share the 34EMA possibility of defining a trend and then trade this EA at lower TF, 15mins+, ATR 30mins.

HGBnG 34EMA M15 v1g+.set

(for use with v1g and onwards...)

-------

On live:

Holy Graily Bob 'n Grid v2n PQL 34EMA H4 TF.mq4

(added 34EMA filter using Bob's MA)

On Demo experimental with live presets:


Demo:

Holy Graily Bob 'n Grid v2n PQL 34EMA M15 TF.mq4

(added 34EMA filter using Bob's MA)

Holy Graily Bob 'n Grid v2p PQL 34EMA M15 TF.mq4

(with some of v1a code and added 34EMA filter using Bob's MA)

[SteveHopwood]

There is a problem with the latest version. Using either of the new trend filters results in hundreds and hundreds of stop orders being sent. One of the trend filters causes immediate deletion of the order.

My demos have been auto-blocked by GP's servers. Check your demos by closing one down and restarting it. You have been blocked if you see 'No connection" in the bottom right of your platform. Go to http://www.whatsmyip.org/ and send your IP to GP to have your IP unblocked.

I will sort out the bloop today.

Check your live accounts first. Use the attached script if you find an excessive number of stop orders on any of the charts.

[PeterUK]

Hi Steve,

I think the problem you mentioned, also happens with the trend filters off... after a few tests I did with my demo account - I may be wrong.

Regards,

Peter

[tonyharmony]

Greetings,

Steve: many thanks for your hard work in putting v1a together, a kind of gift received after my birthday on the Friday

I was having problems with the latest version 1a, trades would often trigger and then suddenly closes. As I've yet to discover the know how on how to fix this, I thought I learn from post 2 and do a bit of coding myself...

I've combined elements of v1a (trade comments and Bob's double MA with a twist) to v2n of HGB 'n Grid.

As you may have noticed, if you plot the 34 EMA Close on your charts, price action tend to bounce of this MA after a retracement... in an uptrend above the line, in a downtrend below the line... so I have used Bob's double MA to implement this... a kind of basic trend filter in helping us to identify a trend, letting HGI handle signals and then trading with it...

Results are attached running on a GP Demo account...



Pips gained were quite impressive from running overnight in the UK (focus on the Nett Pips). To help reduce floating DD I'd suggest using 0.01 lots for small accounts of less than $2000. An probably use 'SizeOfDollop' of $2000+ depending on how risk averse you are.

I've been running this on 7 Majors plus GJ, 15min TF, $3000 Demo, Global Prime.

Thought I give back to the community, enjoy...

DISCLAIMER: Use at your own risk on a live account!

Regards,

Peter

Thanks Pete for your efforts, glad to see the chart info came in handy.
Decided to have a go at your setup on Gold, EU, GJ, GU, UC, and UJ ...

Cheers
Tony

[SteveHopwood]

Hi Steve,

I think the problem you mentioned, also happens with the trend filters off... after a few tests I did with my demo account - I may be wrong.

Regards,

Peter

Thanks Peter. I do not see how it can be a problem with the trend filters either.

I think lines 5212/3
//Examine the position for trade closure/deletion
ShouldTradesBeClosed();

are in the wrong place. I think they should be moved to just underneath line 5234
CountOpenTrades();

because HGBnG is examining the trade closure function before building up a picture of the position.
Copy this over the top of line 5234:

Code: Select all

   CountOpenTrades();
   //Examine the position for trade closure/deletion
   ShouldTradesBeClosed();

then scroll back up to line 5212 and delete it along with 5213.

I will put a fixed version in post 1 soon.

[SteveHopwood]

V 1b is in post 1 with the fix I described above. Keep an eye open especially on your live accounts folks. I am not sure this is the solution.