scooby-doo BOJ JPY pairs trading robot

Quoting scooby-doo

Disliked

Information

The martingale type systems you see on ebay for 0.99 will ofcourse blow your accounts very quickly.

The one I put forward has very clear entries based on OB/OS in multiple timeframes.

Also, we only ever goto 3 levels and start with a relatively low starting lot size.

Having said this, nothing in forex (or anything else) is gauranteed as external factors such as earthquakes, political assinations, government scandal, interest rate changes etc will upset the apple cart at some point.

Anyway, try it on a demo account.

Scoobs...

Ignored

Quoting camvcvoo

Disliked

DXTrade,

I remember along the way you post your dashboard with M15, H1 and H4. The link in the first post is M5, M15 and H1.

Do you think you can post the version with H4?

Thanks.

Ignored

Quoting swnke2

Disliked

Regarding the implementation of the SillyHedgingStopLoss (that some of us need to use because of our criminal partners (LOL - great phrase), I think the logic for calcuating the SL is incorrect and results in some of the errors we've seen:

Ignored

//Auto lot calc
   if (RobotCalculatesLotSize)
   {
      double LotStep = MarketInfo(Symbol(), MODE_LOTSTEP);   
      //Make sure that there are not too many decimal places in the result of the calculation
      int decimals;
      if (LotStep >0 && LotStep < 0.1) decimals = 2;//0.01
      if (LotStep >0.09 && LotStep < 1) decimals = 1;//0.1
      if (LotStep >0.9) decimals = 0;//1   
      Lot = NormalizeDouble(AccountEquity() / LotDivisor, decimals);
      if (Lot < LotStep) Lot = LotStep * 2;
   }//if (RobotCalculatesLotSize)

Quoting SteveHopwood

Disliked

Cheers. Nice bit of blunder-spotting.

Fix is in post 1. If you are never going to use SillyHedgingStopLoss then you don't need it.

Now, can anyone see why this code snippet should fail to calculate a lot size that is acceptable to the criminal?

[code]
//Auto lot calc...

Ignored

Quoting SteveHopwood

Disliked

Cheers. Nice bit of blunder-spotting.

Fix is in post 1. If you are never going to use SillyHedgingStopLoss then you don't need it.

Now, can anyone see why this code snippet should fail to calculate a lot size that is acceptable to the criminal?

[code]
//Auto lot calc...

Ignored

Quoting hotstorm

Disliked

One of the reasons could be that even LotStep*2 can be less than MODE_MINLOT, which is not necessarily equal to MODE_LOTSTEP.

From MQL4 docs:
MODE_MINLOT 23 Minimum permitted amount of a lot.

Ignored

Quoting macman

Disliked

Hi Steve,

Some way back Scooby posted an idea which looked promising, basically increasing lot size the further into the OB/OS zone a trade went.

Did you consider it for the DB?

Here are some code snippets which show the idea

extern int...

Ignored

Quoting awk

Disliked

Alright guys, I have been running DB for 24 hours, it opened all 7 trades and hedged them all. So now I am in approx 6% drawdown. The obvious question is, what now ? Should I just wait for the trades to close themselves or ?

Ignored

Quoting Jaula

Disliked

Sell XXX/JPY now

Ignored

Quoting scooby-doo

Disliked

This is not a thread for posting trading signals.

Do it again and you will be banned by the thread starter.

Ignored

Quoting Jaula

Disliked

Ok, sorry didn't mean to post trading signal, have changed the post.

Ignored

Quoting scooby-doo

Disliked

Another RSI method for any pair which is very safe due to starting lotsize.

Example:

Go Short

- Wait for 2TF RSI > 70 Sell 1.0 Lot
- Wait for 2TF RSI > 80 Sell 2.0 Lot
- Wait for 2TF RSI > 90 Sell 3.0 Lot
- Close out when TP hit

Go Long

- Wait for 2TF RSI < 30 Sell 1.0 Lot
- Wait for 2TF RSI < 20 Sell 2.0 Lot
- Wait for 2TF RSI < 10 Sell 3.0 Lot
- Close out when TP hit

Your starting lotsize should be AccountFreeMargin() / 50000. The sequence should only start when the currency pair first becomes OB or OS.

Scoobs

PS. This is...

Ignored