Okay, thanks.
I loaded it yesterday on the mentioned 2 pairs and added GBPNZD to it, just to see it's behaviour.
GBPNZD alone earns as much as the other 2 together, the future will tell if the DD is there to match.

During the evening, I noticed that nearly every trade closes shortly after the 1st jump of the SL, averaging 20 pips.
Did you ever try to just enter a 20 pip TP, and no BE/ JS? This might help with the speed of the totall Empty4 install.
Maybe this screws up the offsetting, I need to find out how that works on this one.

Thanks for the setfile, this gives me a startingpoint to work from.

rapple » Thu Dec 14, 2017 10:47 pm wrote: Sounds like a plan Gerte

I have set up a new instance where I have a 5 pip Breakeven and a 5 pip Jumping Stop (see attached)

The 5pip JS will hopefully give the trades a bit more room to move and may make a bit more $$ on a price run.

Have only set this up on GBPJPY and EURUSD so I can compare tom my TJF setfile

Cheers Richard

marx64 » Wed Dec 27, 2017 5:02 pm wrote:Interesting settings Is it profitable?

Anyways, you say that those closures do happen during rollover, and as I see you have enabled trading during rollover (it's disabled by default). May i ask why? Have you tried to disable it?

Gertje » Wed Dec 27, 2017 4:02 pm wrote:I'm trying to have CP to perform a certain thing, and for some weird reason, it keeps closing trades at rollover.
Not all, but everyday a few with no duplicadable reason.

What I'm trying to do;
- have CP set pendings in the D1 chart, after rollover
- do the same everyday
- when the set TP on a pair is reached, close the trade and start again at rollover

The below AUDJPY chart, shows that nearly everyday the open trade was closed at a small profit/ loss, where I believe should at least 3 times the basket have closed at the basket-TP of 75pips/ $50,-

Anybody willing to help find out what is wrong with my settings?

   //Rollover
   if (DisableEaDuringRollover)
   {
      RolloverInProgress = false;
      if (AreWeAtRollover())
      {
         RolloverInProgress = true;
         DisplayUserFeedback();
         return;
      }//if (AreWeAtRollover)
   }//if (DisableEaDuringRollover)
  

if(OldBarsTime!=iTime(NULL,TradingTimeFrame,0))

SteveHopwood » Thu Dec 28, 2017 9:45 am wrote: It could be that the spread widening during roll over causes one of the closure conditions to occur temporarily.

Try disabling the bot during roll over. This block of code:

Code: Select all

intercepts the program run before it gets to the code that tries to send a trade. The run can continue once roll over has finished and will reach this line of code:

Code: Select all

Then CP will discover that a new candle has started and send the trades.