Bob's Biggest Balls Ever

[MurphyMan]

@Murphyman (Sam)
Are you using the latest version of BBBE. 'ThisInstanceIsMaster' can either be true or false.
I am using "+13.00,-18.00" for the Asian Session and it's working fine.

I was running 1D when I noticed the problem.

[fmuir]

@Murphyman (Sam)
Are you using the latest version of BBBE. 'ThisInstanceIsMaster' can either be true or false.
I am using "+13.00,-18.00" for the Asian Session and it's working fine.

@Murphyman (Sam)

I was running 1D when I noticed the problem.

Have you had a chance to update to version 1e? Another issue that might affect this is that the times entered for a particular trading session should be your wall clock time in 24hr format.

Good Luck

[Lifesys]

Hi Frank
There appear to be 2 failed requests at 17.12.13 then success at 17.12.14 (reported by BBBE 17.12.15) which would suggest to me the system worked very well. MPTM does this - keeps trying until success or give up.

[fmuir]

Hi Frank
There appear to be 2 failed requests at 17.12.13 then success at 17.12.14 (reported by BBBE 17.12.15) which would suggest to me the system worked very well. MPTM does this - keeps trying until success or give up.

Hello Lifesys,

I understand what your saying, but this particular action caused 5 Alerts in a period of one hour. The modifcations had suceeded. The order finally exited with a SL in positive value.

The Asian session had opened three orders. Only one of these orders displayed this particular action. The other two orders have remained open.

If that is the normal way it behaves, what is the need for the alert(s)? I hadn't recalled this kind of activity with MBPM or MTPM.

Regards,
-Frank

[ovisun]

Using v1e, but still problems with trading hours, see picture.
I use two versions with different magic no., one version for 10.00-18.00 GMT and one 10.30-18.30 GMT

Regards

[McNish]

@ Lifesys : Thanks for the response.

A general query here. The Adx and Doji filters in the new versions, are they for scalp trades or positional ones?

I see two JSL's, one asking for trend trades, the other below the BE section asking again for T/F.

Somehow, I'm not able to get the trades for the different values I set. Been so since the first version posted. Thus can anyone post a set file where the system is taking trades regularly so that I can find the error at my end.

Thanks.

[Lifesys]

Hi Frank
Not exactly sure to what you refer but maybe it is what Bob addressed in the manual thread. Some companies do not allow jump increments less than, in that case, 8. So default

Code: Select all

extern int      JumpIncrementPips = 5;//The profitable trade jumping increments
extern int  NegativeIncrementPips = 10;//SL jump increment while the sl is negative.
extern int  PositiveIncrementPips  = 6;//SL jump increment while the sl is positive.

gets rejected until SL > 8 ie 1.26639 - 1.26539 = 10 pips. Don't think MBTM or MPTM used jump stops that small.

McNish
I see Steve has included these filters in both but doubt they will have real affect on scalps as Doji looks for H4, D1 candles. Set to false to test. I have found they reduce trades but increase success.
I have trades using defaults (except 'UseH1ADX' = false;) but not many & happy EA trades slowed down on BBBE given current retracements. esp. those buying on D1 TMASlope. Some JPY pairs have D1 TMASlope > 1.2 yet H1 TMASlope <-0.5 & ADX is -60. Good time to CT but look for turn for trends. Better out than wishing you were.
'JumpScalpTrades' is under 10.3, 'JumpingStop' under BE is in "10.2A trend trading " section.

Hope this helps. Any more ask Steve - far more trading experience than me!

[Bader]

Not sure why these would read differently on the same Criminal (EURUSD) - 10.3 and 10.2 DWMP differ. Could it be that Steve you are using Baluda's latest Daily Pivot indicator (in your code) and the template(bob's) is the original?

When applied to the chart new indi (baluda's) seems to make no difference but that could be pot luck.

[Lifesys]

Sorry Bader
Eludes me as to what the difference is! In chart image the values are cut off (need a bigger screen) & in table DO is rounded off at 1.3380 for expediency. Mine is slightly difference value.
The only difference I can see is DO & Price swapped but unless snaps were captured somehow at same instance, price is only a few pips from DO and that 12:01 1min candle moved 5 pips, DO & Price could well have swapped.
Or am I missing something here?

[Bader]

Just wondering why the DWMP was different on this chart - ready for a buy when price crosses upwards through DO, but on table the DWMP states we missed trade.

I realise that rounding makes for different numbers (small) but would like to see DWMP aligned.

Snapped at same time ( I had been watching it for a while). Not big issue- just a query.