Bob and Shelley Again

[fxozgirl]

curious, is JS working for you guys? On the audcad trade, JS isnt working here (BE did though).
Set a regular trailing stop for now, so will see on the next new trade if noone else is having issues

Unfortunately, it doesn't look like it...my audcad trade was stopped out at approx +100

audcad.gh4_closed trade 130730.png

[fxozgirl]

That eurcad is a correct entry. EA's work on absolute values at the time of working. What something subsequently looks like a on a chart is irrelevant.

On my chart, the candle shift 2 from the trade open closed below the fast ma by 0.00001 of a pip. Shift 1 closed above the fast ma, so the bot detected a cross upwards. RSI-TMA slipped below 10 during the trigger candle, and so the bot took the trade.

EA's do what they are programmed to do. You want them to do something different, you have to tell them to do it.

Welcome to my world.

What a smart bot...the trade has come back nicely

and thanks for the clarification & explanation...your world is a whole new (& scary) world for me

[SteveHopwood]

curious, is JS working for you guys? On the audcad trade, JS isnt working here (BE did though).

No, it isn't. I will sort it out later.

[fxozgirl]

Just going through the charts to see what's happened today...

CADCHF - Main entry trade taken

cadchf.gh4_main entry trade_130730.png

EURCAD - Main entry trade taken

eurcad.gh4_buy main entry_130730.png

EURUSD Missed 're-entry' trade

eurusd.gh4missedtrade_130730.png

GBPNZD Potential 'main' entry setting up

gbpnzd.gh4_potential main entry setup_130730.png

GBPUSD BUY trade taken (a bit weird, the EA set the SL at 50 pips again, once I deleted the SL, the EA then set the SL correctly at 100 pips)

gbpusd.gh4_buy130730.png

NZDUSD Potential main entry setting up

nzdusd.gh4_potential main entry setting up.png

USDCHF - Missed re-entry trade

usdchf.gh4_missed re-entry trade_130730.png

Looks like there could be a problem with the 're-entry' type trades taken off the stoch, EURUSD, USDCHF both missed today.

[SteveHopwood]

V 1b is in post 1 - fixed the JS thingy.

The re-entry code was ridiculously wrong. You guys do not usually see the kind of mess I made of the code because backtesting in Crapergy Tester usually highlights it - but this one does not run in CT. Hey ho.

Brilliant pics, Shelley; big help.

BASA is making a belting start on demo. I have two closed losers, both gbpaud at their 50 sl. Looking at them, an sl of 100 would have allowed them to recover, so I have changed this by default. Next thing is to spot whether I also get a 50 sl despite wanting 100.

[fxozgirl]

V 1b is in post 1 - fixed the JS thingy.

The re-entry code was ridiculously wrong. You guys do not usually see the kind of mess I made of the code because backtesting in Crapergy Tester usually highlights it - but this one does not run in CT. Hey ho.

Brilliant pics, Shelley; big help.

BASA is making a belting start on demo. I have two closed losers, both gbpaud at their 50 sl. Looking at them, an sl of 100 would have allowed them to recover, so I have changed this by default. Next thing is to spot whether I also get a 50 sl despite wanting 100.

Thanks a lot Steve for your prompt fixes...I'll get v1b on tonight.

I think SL 100 is ideal, given we're trading with a defined trend, in most cases this should give us enough room for price to move about before continuing on, but not cause too much damage if on the odd occasion a trade does hit SL. With my manual (visual) backtesting there were very few trades that hit 100 pip SL. Any trades that went bad were usually saved by the BE setting.

[trader689]

just in case anybody else was having the same issue as myself with the "cannot open...\10.4 4H RSI2 modified for automation.ex4" error message i found the solution. the EA (on all three broker platforms i tried it on in any case) was looking for a file with *two spaces* between the words '10.4' and '4H' in the filename of the ex4. renamed the ex4 (and mq4) with two spaces and it's sorted the problem.

[SteveHopwood]

It is Official. Required stop loss 100: actual sent stop loss 50. Delete the stop and BASA replaces the sl at the desired level.

And I haven't even the beginnings of the faintest glimmering of an understanding why. : : :

[OldTrader]

Latest update on mine, when I delete the stop (50 which is incorrect), it replaces it with 50 again.
So I did a little test, and I changed my JS setting to 100 pips instead of 50. I then deleted the SL again, and BASA set it at 100.
So it definitely has to do with the JS, hopefully that will send you in the right direction to find the issue.
Almost like it's treating the JS as an instant trailing stop

[SteveHopwood]

Latest update on mine, when I delete the stop (50 which is incorrect), it replaces it with 50 again.
So I did a little test, and I changed my JS setting to 100 pips instead of 50. I then deleted the SL again, and BASA set it at 100.
So it definitely has to do with the JS, hopefully that will send you in the right direction to find the issue.
Almost like it's treating the JS as an instant trailing stop

You are dead right.

It occurred to look in the log. This shows the trade being sent without sl (Global Prime) then modifying it correctly, then modifying it again by moving the stop from 100 pips to 50.

Thanks for the confirmation. More later. Nearly there.