fxozgirl wrote:

SteveHopwood wrote:

spotdespot wrote: I can't think of any reason why any Main or Re-entry trade would open part way through a H4 candle - whatever the settings. For me that is the main mystery.
.

If the spread widens beyond MultiplierToDetectStopHunt * AverageSpread, BASA (and any other ea coded from later versions of my shell) will hang up its hat with a "EA suspended during a massive spread event" or some such wording. It will continue to monitor open trades but will not attempt to send new trades until the spread returns to within acceptable bounds.

This all happens within void CheckForSpreadWidening(), so the code to tell BASA that a new candle is not reached at the end of start(). So far as BASA is concerned, it is looking at a new candle even though that candle may be some minutes old.

Shouldn't be a problem, but we can monitor this and change if need be.

Ok, this is interesting...
I too had a GBPNZD trade taken 2 hours into the candle last night, the entry was correct for the start of the candle, just a delayed entry??
Unfortunately this trade due to a spike down in the next candle was stopped out, but if it had been taken at the start of the candle would have closed in a nice profit. Worse, it was my live account

gbpnzdh4_291013.png

SteveHopwood wrote:I tried to post my last a couple of hours ago. Then the dreaded "Waiting for stevehopwoodforex" message appeared, so I did my usual and wandered off to do something useful. And so ignored the, "Someone else has added a post. What do you want to do?" or whatever the wording is.

Is it only me, or is everyone else here spending half their lives "Waiting for stevehopwoodforex" these days?

Whatever. V 2n with the fix for the EveryTickMode thingy is in post 1. No idea how that crept in. My best guess is that I made the edit in the wrong scite tab - there is an EA out there somewhere that should be trading every tick but is waiting for the open of a new candle. Bugger.

fxozgirl wrote: and yes, SteveHopwoodForex is very slow these days...you may need to look at how much bandwidth the site has/is using? I would suggest it's pretty high due to the large number of attachments uploaded. Usually increasing the bandwidth will solve the problem!

SteveHopwood wrote:

fxozgirl wrote: and yes, SteveHopwoodForex is very slow these days...you may need to look at how much bandwidth the site has/is using? I would suggest it's pretty high due to the large number of attachments uploaded. Usually increasing the bandwidth will solve the problem!

Hehe. Never confuse my ability to hack together an EA with anything that remotely resembles an understanding of the underlying technology. In the past, when I have stood at the side of the road working out how to change the tire, girls have stopped to help out.

If mop hadn't stepped in to oversee this site's migration we would probably have lost it. What on earth does "Usually increasing the bandwidth will solve the problem!" mean?

SteveHopwood wrote:Aha. Problem solved.

It is common knowledge that I code my ea's using my shell. This shell caters for strategies that only trade at the open of a new candle and those that trade at every tick with the variable EveryTickMode. When an ea trades only at the start of a new candle, I hide the variable and set it to false.

Someow, BASA latest has this set to 'true'. I will post a fix later. In the meantime, those of you who can (and yes, that really should be all of you by now) find

bool EveryTickMode=true;

and change it to

bool EveryTickMode=false;

then recompile.

fxozgirl wrote:

SteveHopwood wrote:

spotdespot wrote: I can't think of any reason why any Main or Re-entry trade would open part way through a H4 candle - whatever the settings. For me that is the main mystery.
.

If the spread widens beyond MultiplierToDetectStopHunt * AverageSpread, BASA (and any other ea coded from later versions of my shell) will hang up its hat with a "EA suspended during a massive spread event" or some such wording. It will continue to monitor open trades but will not attempt to send new trades until the spread returns to within acceptable bounds.

This all happens within void CheckForSpreadWidening(), so the code to tell BASA that a new candle is not reached at the end of start(). So far as BASA is concerned, it is looking at a new candle even though that candle may be some minutes old.

Shouldn't be a problem, but we can monitor this and change if need be.

Ok, this is interesting...
I too had a GBPNZD trade taken 2 hours into the candle last night, the entry was correct for the start of the candle, just a delayed entry??
Unfortunately this trade due to a spike down in the next candle was stopped out, but if it had been taken at the start of the candle would have closed in a nice profit. Worse, it was my live account

gbpnzdh4_291013.png

forexdj wrote:Steve, am enjoying spotting your bloops!