garyfritz wrote:That doesn't look right to me, Dietmar. The "bool" statements were supposed to initialize the values to False, and then the "if" statements set them to True if the conditions were right. It looks to me like it will ALWAYS return true now.

garyfritz wrote:That doesn't look right to me, Dietmar. The "bool" statements were supposed to initialize the values to False, and then the "if" statements set them to True if the conditions were right. It looks to me like it will ALWAYS return true now.

scalpz wrote:

garyfritz wrote:That doesn't look right to me, Dietmar. The "bool" statements were supposed to initialize the values to False, and then the "if" statements set them to True if the conditions were right. It looks to me like it will ALWAYS return true now.

I agree. Dietmar, I think your alteration is not good.
The ea uses chart time for starting the grid and uses your local time to see if its ok to be running.
Well thats what I read in the instructions or within the ea itself maybe.

Loaded up ea yesterday at 2:10 gmt/ chart time. Altered grid start to 02:15 cause I wanted to see it triggered and the asia session had been flat till then. 02:15 oh look at that 6 pending trades placed. Nice but they are .01 .02 .03 lots. mmmm

Checked settings - ok well now I see the usemultiplier & its at 1.5 - Well I will just run with that this time while I think that thru a bit.

All 3 buys eventually triggered & finally closed at 144 pip profit. All pending trades closed, including those sell-stops added at each buy trade opening.

Not bad, but for quite a while it looked as if the basket/grid would not have closed if it had been applied around the 7 or 8am gmt area.

Noticed the 3 sell-stop trades applied when the 3rd buy trade triggered had 4 or 5 pip higher settings for everything including SL. So heaps of extra red lines on the chart.

Not sure at all about the value of increasing lot size for the 2nd & 3rd trades. Makes it an all or nothing play until TP hit.

Now wondering if I can amend this ea to do the Graeme millipede type of baskets.

Play time.

cheers scalpz

forextrader-radioman wrote: Hy Scalpz,

well, look at some posts b4 ... it looks like the lot multiplier is not working correct with that input. I run the EA here all time wit lot multi set to "2.0" and that works fine. First level is 0.01 (or 0.1) lot, second level is 0.02 (or 0.2) and third level is 0.04 (or 0.4) and thats exact what it should do with this setting.

forextrader-radioman wrote: And today morning I also see that my EURJPY trades are closed, TP was hit but there where still some buy stop pending orders in the order book and chart. They where not deleted and that could be the reason why some have trouble with backtests over some days in a row. There is a bug in the EA ... so only run the EA at "one run only". Not in full automatic mode.

scalpz wrote:Not an ea bug, just the way crap Empty4 works. When another tick arrives, the ea is stopped from doing whatever it is up to (like deleting pending orders) and restarts at the start() function.

garyfritz wrote:

scalpz wrote:Not an ea bug, just the way crap Empty4 works. When another tick arrives, the ea is stopped from doing whatever it is up to (like deleting pending orders) and restarts at the start() function.

You sure about that? I thought it *ignored* and dropped all incoming ticks until it finished with the last one...

In Expert Advisors the special function start() is called (and executed) immediately after a new tick comes. If a new tick has come during the execution of the special function start(), this tick will be ignored, i.e. the special function start() will not be called for execution when such a tick comes. All quotes received during the execution of the special function start() will be ignored. Start of the special function start() for execution is performed by the client terminal only provided that the previous operation session has been completed, the control has been returned to the client terminal and the special function start() is waiting for a new tick.

garyfritz wrote: [...] Dietmar, could you post some times when you've initiated your traps with your "wait for ranging market" rules? I tried implementing it in Tradestation and the results weren't too impressive. Maybe I change how I detect the ranges.

Actually I was wondering if it would work better to wait for a market that's *moving* strongly, and set the trap there. If the market keeps moving, it'll blow right through your price levels in your trap, which is the ideal. When you set the trap on a range, the market might wander back & forth inside your trap for a while before it finally breaks out -- causing losses.