Blue — As for the back test you are speaking about - I had about 5 pairs out of the 26 (one of them was EURUSD, I don't remember the others) which ended the test as looser, but I conceder this as something one can handle manually.

Nanningbob V5: Steve Hopwood's auto-trading robot

The forward test is on 26 pairs. But remember that I'm running a corrected version of 71c which handles recovery correct for both 4H-trend and NB trades and several other major error correction. Most of those corrections are implemented in ver 81. ...

Nanningbob V5: Steve Hopwood's auto-trading robot

Status for my forward test on the corrected 71c — Running since October 4 at market start. image image

Nanningbob V5: Steve Hopwood's auto-trading robot

Ok! I will do that. But please clarify point number 2 in my previous post.

Nanningbob V5: Steve Hopwood's auto-trading robot

Max ver 81 — Hi Max, 1. In 81 you have added a new sequence in CountOpenTrades4H function. The compare (colored red) should be adjusted with correct digits otherwise it is producing repeated error 1 (no error). the correct compare should be: ...

Nanningbob V5: Steve Hopwood's auto-trading robot

I'm trading 1H as it seems to be most profitable on my backtest.

Nanningbob V5: Steve Hopwood's auto-trading robot

KG_OS and RSI_OS — You are right! I think that this mode should either run mutually-exclusive with NB trades or have its own set of functions just like KG trades and only then it can trade in parallel with NB and KG.

Nanningbob V5: Steve Hopwood's auto-trading robot

I did not, but I am posting some bug fix to the latest version. I prefer doing it this way and let Max manage the real Max's EA. as you can see Max has already released new version that includes my corrections. But there are more to come, ...

Nanningbob V5: Steve Hopwood's auto-trading robot

Here are some result from the corrected 71c — I love Max's work. This is way I'm so keen about cleaning it up! I will post some more corrections when I get the time to go through some more code in the new version. Here are the status for my ...

Nanningbob V5: Steve Hopwood's auto-trading robot

The following are some bugs corrections in Max's 078 — As I have posted before, I have detected several major bugs in ver 71c, and as I suspected they are still there in ver 78. 1. In RecoveryModule4H there is a “Copy and paste” error that ...

Nanningbob V5: Steve Hopwood's auto-trading robot

Max's 71c — After fixing quite few major bugs in this version I have managed to backtest several pairs for the last 3 months. Most of them with quite nice results for example: USDCHF: image USDJPY: image AUDUSD: image GBPJPY: image I ...

Nanningbob V5: Steve Hopwood's auto-trading robot

Max! Concerning TS JS routines — Looking at the code of these functions and doing some backtesting I have observed that the logic do not check the new value of sl to see if it is the same as the one that already in OrderStoploss(). When you do ...

Nanningbob V5: Steve Hopwood's auto-trading robot

Max! Concerning TS JS routins — Looking at the code of these functions and doing some backtesting I have observed that the logic do not check the new value of sl to see if it is the same as the one that already in OrderStoploss(). When you do ...

Nanningbob V5: Steve Hopwood's auto-trading robot

I think that what you need to do is just add the following line: PendingOrderPipsDistance *=multiplier; to the list of variables that you adjust for correct digits in the init() function. then it will look like that: MaxADr *= multiplier; TakeProfit ...

Nanningbob V5: Steve Hopwood's auto-trading robot

Max — Ok, I will look at the code for JS and TS and see if I can find somthing (I'm not using those functions in may test and this is why i did not met the problem). in the mean time I have another thing. I think that PendingOrderPipsDistance ...

Nanningbob V5: Steve Hopwood's auto-trading robot

Max — You don't need it there because when you later use PendingOrderPipsDistance you multiply it by Point as in this line: EntryPrice = NormalizeDouble(Bid - (PendingOrderPipsDistance * Point), Digits);

Nanningbob V5: Steve Hopwood's auto-trading robot

Another way to correct the strange TP in ver 64 — in both SetTarget and SetTarget4H functions you need to replace only one line: double MinDist=MarketInfo(Symbol(),MODE_STOPLEVEL); with this line: double ...

Nanningbob V5: Steve Hopwood's auto-trading robot

Don't conclude hasty conclusions about my coding skill... You are of course right! The correction of this tricky bug (it appears only on symbols that have larger StopLevel Then the AtrVal. And Stoplevel is different with different brokers - even ...

Nanningbob V5: Steve Hopwood's auto-trading robot

Max Ver 64 — I guess that this error was also in previous versions. It is the reason for some strange TP values and also some order rejection. in SetTarget and SetTargetH4 functions the Target with AtrVal Should be multiply with Point: ...

Nanningbob V5: Steve Hopwood's auto-trading robot

Max's 056 — sorry, I was not aware of that you had two diffirent analyse functions. It should be ok. Then the Lines: if (OrderMagicNumber()!= magic4H)continue; if (OrderMagicNumber()!= magicR)continue; in CheckRecoveryTakeProfit4H and ...

Nanningbob V5: Steve Hopwood's auto-trading robot