Multi Pair Swing Trader,,

[MrLong]

Bug Fix 1.01b on the front page.

[MrLong]

Hi Andy
A couple of curiosities.
The "xxx: Order Send failed, Non-positive ticket returned" error (we got >70)
might be fixed with the ModifyOrder loop as used in Steve H's EAs. instead of a one shot routine.
Also very strange that USDJPY is missing from our pair list.
Since drawn to my attention in Sept. USDJPY has risen 850pip & expected to continue far further as US unemployment drops - need it in any list for retracements. Riding up the big swing!
regards Paul

Hi Paul,

USDJPY has been fixed in 1.02, I'll upload this over the weekend, I've been testing for errors.

I'll look at the send order also.

Many Thanks
Andy

[quanttraderjoe]

Bug Fix 1.01b on the front page.

Mr Long,

thanks for v1.01b, i have loaded it on my demo, n for testing, put it on m30 timeframe...
have u tried m30 for the swing trade ea? any good? i think it does well during gradual trends but will suffer in whipsaws.

i noticed that the ea fired a buy usd/jpy when there was in fact a swing lo on the m30 ... so i guess there is a bug on usd/jpy cos the other pairs trades were in accordance with the ea logic.

thanks again!

[quanttraderjoe]

Mr Long,

just an update on my demo, on h1 it has done pretty well with the profit lock which is real conservative but reaped 500pips since dec 18th...max gain banked was 660pips but took some losses today so went down a bit. i suspect without profit lock, n no tp set...might have even hit 5000pips...crazy man.

is it possible to let the successful trades run till the ema21 crosses back against the ema55? i noticed many good trades could have run for 200-600pips! and there were indeed many such trades n i was surprised at the reliabilty of the cross on h1. so in this case since the stoploss is fixed at the previous swing hi/lo, we simply take the loss when price reverses strongly but let the winners run till the 2 emas re-cross.

is this viable? or will this lead to a margin call during flat markets?

[chrisD]

Mr Long,

just an update on my demo, on h1 it has done pretty well with the profit lock which is real conservative but reaped 500pips since dec 18th...max gain banked was 660pips but took some losses today so went down a bit. i suspect without profit lock, n no tp set...might have even hit 5000pips...crazy man.

is it possible to let the successful trades run till the ema21 crosses back against the ema55? i noticed many good trades could have run for 200-600pips! and there were indeed many such trades n i was surprised at the reliabilty of the cross on h1. so in this case since the stoploss is fixed at the previous swing hi/lo, we simply take the loss when price reverses strongly but let the winners run till the 2 emas re-cross.

is this viable? or will this lead to a margin call during flat markets?

what's your broker?why my broker: Order Send failed, Non-positive ticket returned. 1.01b.

[quanttraderjoe]

chrisD,

i got alot of the pop up alerts saying "Order Send failed, Non-positive ticket returned" but somehow the trade was triggered anyway. weird.

i'm on alpari uk micro demo acct.

[AGT]

hi guys ! As I understand MrLong is preparing a new v. 1.02 - read above his post ! He will fix some bugs. So .... MrLong - where are you ?

[MrLong]

Mr Long,

just an update on my demo, on h1 it has done pretty well with the profit lock which is real conservative but reaped 500pips since dec 18th...max gain banked was 660pips but took some losses today so went down a bit. i suspect without profit lock, n no tp set...might have even hit 5000pips...crazy man.

is it possible to let the successful trades run till the ema21 crosses back against the ema55? i noticed many good trades could have run for 200-600pips! and there were indeed many such trades n i was surprised at the reliabilty of the cross on h1. so in this case since the stoploss is fixed at the previous swing hi/lo, we simply take the loss when price reverses strongly but let the winners run till the 2 emas re-cross.

is this viable? or will this lead to a margin call during flat markets?

Hello quanttraderjoe,

Pleased your doing well, I'll have a look at the EMA,s crossing back, I've added the option to use the slope to try confirm the swing break, I'm just testing it.

Best Regards
Andy

[MrLong]

Mr Long,

just an update on my demo, on h1 it has done pretty well with the profit lock which is real conservative but reaped 500pips since dec 18th...max gain banked was 660pips but took some losses today so went down a bit. i suspect without profit lock, n no tp set...might have even hit 5000pips...crazy man.

is it possible to let the successful trades run till the ema21 crosses back against the ema55? i noticed many good trades could have run for 200-600pips! and there were indeed many such trades n i was surprised at the reliabilty of the cross on h1. so in this case since the stoploss is fixed at the previous swing hi/lo, we simply take the loss when price reverses strongly but let the winners run till the 2 emas re-cross.

is this viable? or will this lead to a margin call during flat markets?

what's your criminal?why my criminal: Order Send failed, Non-positive ticket returned. 1.01b.

Fixed in 1.02.

[AGT]

Mr Long,

just an update on my demo, on h1 it has done pretty well with the profit lock which is real conservative but reaped 500pips since dec 18th...max gain banked was 660pips but took some losses today so went down a bit. i suspect without profit lock, n no tp set...might have even hit 5000pips...crazy man.

is it possible to let the successful trades run till the ema21 crosses back against the ema55? i noticed many good trades could have run for 200-600pips! and there were indeed many such trades n i was surprised at the reliabilty of the cross on h1. so in this case since the stoploss is fixed at the previous swing hi/lo, we simply take the loss when price reverses strongly but let the winners run till the 2 emas re-cross.

is this viable? or will this lead to a margin call during flat markets?

what's your criminal?why my criminal: Order Send failed, Non-positive ticket returned. 1.01b.

Fixed in 1.02.

Ok - fine - but where did you post the v. 1.02 ?