Nice one. Not much point in me including CSS without the indi. Added to post 1.OldTrader wrote:Oops, I shouldn't have updated hehe.
EA is looking for Alert: STOPPED - iCustom Indicator not found: 10.5 CSS 4H 1.0.8 modified for automation.ex4
can you put this indicator in post 1?
have just removed it from the code for now, so i can resume running it
I am trading it on my Cowboy IBFX play-money account - started today, so just one trade open at the mo.John wrote:Steve, Shelley... Brilliant concept here! I've gone live straight away (don't panic as I monitor my charts every 4 hours like clockwork and I do have some trading experience so not to worry!)....
Set StopTrading to true, then make sure that BASA has the same magic number as your open trades - manually sent trades have a magic of 0, then set your management inputs.Steve, this may seem like a crazy question but, alas... Is there a "simple" way such that I could force the EA to manage trades that I take manually in addition to it's own? I only ask because, at the conclusion of my most recent 4H candle, there were some beautiful RRTs that barely missed the qualifications for the bot to trigger the trades... So, naturally, I have taken these trades on my own. It would be nice if the EA could just apply the "management" portion of it's work for such situations... If not, no worries as there are other means to skin a cat, but I thought I'd ask. I know you did something similar with a 10.4 management script. Thanks in advance for any tips you might offer up. Again, nice work with this one!
John
Excellent! Muchas Gracias!SteveHopwood wrote:I am trading it on my Cowboy Cowboy IBFX play-money account - started today, so just one trade open at the mo.John wrote:Steve, Shelley... Brilliant concept here! I've gone live straight away (don't panic as I monitor my charts every 4 hours like clockwork and I do have some trading experience so not to worry!)....
Set StopTrading to true, then make sure that BASA has the same magic number as your open trades - manually sent trades have a magic of 0, then set your management inputs.Steve, this may seem like a crazy question but, alas... Is there a "simple" way such that I could force the EA to manage trades that I take manually in addition to it's own? I only ask because, at the conclusion of my most recent 4H candle, there were some beautiful RRTs that barely missed the qualifications for the bot to trigger the trades... So, naturally, I have taken these trades on my own. It would be nice if the EA could just apply the "management" portion of it's work for such situations... If not, no worries as there are other means to skin a cat, but I thought I'd ask. I know you did something similar with a 10.4 management script. Thanks in advance for any tips you might offer up. Again, nice work with this one!
John
Thanks for your ongoing work Steve...I've just loaded this version up this morning.SteveHopwood wrote:V 1e is in post 1.
BASA was drawing a stop loss line at the sl and this was causing problems with the JS function if PipsHiddenFromCriminal = 0.
The spread calculation routine is a recent one and I noticed a couple of bloops that was derailing the recalculation that takes place every 500 ticks.
Fixed both of these thingies in 1e.
Most of the problems have stemmed from LUC inviting his buddies around for a coffee, following changes I made to my shell code that looked good when I coded them. We are working our way through them and this helps users of both my shell and future ea's that I code.fxozgirl wrote:Thanks for your ongoing work Steve...I've just loaded this version up this morning.SteveHopwood wrote:V 1e is in post 1.
BASA was drawing a stop loss line at the sl and this was causing problems with the JS function if PipsHiddenFromCriminal = 0.
The spread calculation routine is a recent one and I noticed a couple of bloops that was derailing the recalculation that takes place every 500 ticks.
Fixed both of these thingies in 1e.
CADCHF - 'Main' Sell trade taken (entry was correct), price moved to +51 pips but a spike took the trade out at BE +2
EURCAD - Trade was taken out at BE+2 with a spike, but pretty choppy price action...there may be a chance to get back in later today if there's enough of a pullback during the Asian session
GBPAUD - Trade is still open, currently sitting at +138 pips with JS moved to +50
GBPNZD - Trade was taken out at BE+2 with a spike
GBPJPY - Pending change in trend direction
USDCAD - Sell trade (main entry) taken, stopped out at BE +2... a couple of wicked spikes there
We all know LUC can be a bitch at timesSteveHopwood wrote:Most of the problems have stemmed from LUC inviting his buddies around for a coffee, following changes I made to my shell code that looked good when I coded them. We are working our way through them and this helps users of both my shell and future ea's that I code.fxozgirl wrote:Thanks for your ongoing work Steve...I've just loaded this version up this morning.SteveHopwood wrote:V 1e is in post 1.
BASA was drawing a stop loss line at the sl and this was causing problems with the JS function if PipsHiddenFromCriminal = 0.
The spread calculation routine is a recent one and I noticed a couple of bloops that was derailing the recalculation that takes place every 500 ticks.
Fixed both of these thingies in 1e.
It is for someone who publicly acknowledges he has OCCDSteveHopwood wrote:Plaudits really go to you, for coming up with such an eminently automatable strategy. Is 'automatable' a word?
I have a lot of similar trades with lots of +2. Still in the AC with 250 locked in. Haven't been in +250 before that I can recall.fxozgirl wrote:There's been some big moves this week, so for the most part we're waiting for some pullbacks to set up some new trades...
AUDCAD - anyone who wasn't stopped out earlier in the week with the SL glitch, should now have their JS at +250 pips
Why would you buy the cad and the on another trade, sell the cad?AUDCAD - anyone who wasn't stopped out earlier in the week with the SL glitch, should now have their JS at +250 pips
audcad.gh4_130801.png
CADCHF - 'Main' Sell trade taken (entry was correct), price moved to +51 pips but a spike took the trade out at BE +2
cadchf.gh4_130731.png
