| stevehopwoodforex.com https://www.stevehopwoodforex.com/phpBB3/ Print view |
|
| Bob's Biggest Balls Ever https://www.stevehopwoodforex.com/phpBB3/viewtopic.php?t=1375 |
Page 23 of 26 |
| Author: | fmuir [ Fri Jan 25, 2013 5:14 pm ] |
| Post subject: | Re: Bob's Biggest Balls Ever |
@ Wiggy1965, Here is a script that makes it a snap to close all open or pending trades. -Frank |
|
| Author: | House Brick [ Fri Jan 25, 2013 5:52 pm ] |
| Post subject: | Re: Bob's Biggest Balls Ever |
Code: Select all The variable OpenTrades isn't being initialised before being incremented. Not sure what Empty4 does, are ints defaulted to zero? If not, it could have random crap in like -12 so even when incremented Code: Select all will always pass. Or it could sometimes have a bigger number e.g. 1012 which would stop some valid trades. But Code: Select all Should block later on when OpenTrades is randomly negative unless Code: Select all Isn't doing what it should. Is Order Open Time Local time or Criminal time? Seems to be Criminal time, (it looks like it is for my Oanda acct). Sometimes Criminal and Local time will overlap which would explain why this isn't happening all the time. So we need: Code: Select all However: Code: Select all Can you spot the problem, #3 allows up to MaxTrades but #8 TrendTradingDoneForToday blocks after 1 trade. I suggest removing the !TrendTradingDoneForToday check in the Trade allowed filters as being the easiest thing to do. I'm just guessing though. Ta, HouseBrick |
|
| Author: | SteveHopwood [ Fri Jan 25, 2013 9:51 pm ] |
| Post subject: | Re: Bob's Biggest Balls Ever |
Thanks again. I have learned/been taught not to trust Crapql4 documentation and normally explicitly initialise variables. I forgot to do this here with OpenTrades. Re the #8 Code: Select all Code: Select all So, the next update will have OpenTrades explicitly declared to zero. To be honest, I cannot see this making any difference, but accurate code is always better than my usual rubbish. Do me a favour, please, and cast your eagle eye over the O_R_CheckForHistory code. This is industrial strength code provided by one of the best in the business and it is foolproof. Thing is, Matt's original code is for single pair EA's, so there is always the possibility that I have mucked up its translation for multi-pair use. I cannot see anything wrong, but that means not a lot. |
|
| Author: | SteveHopwood [ Sun Jan 27, 2013 10:12 pm ] |
| Post subject: | Re: Bob's Biggest Balls Ever |
V 1l is in post 1, with a fix for the implicit/explicit thingy that HB spotted. Do I think this will make a scrap of difference? Nope, but we can hope. It will save a hell of a lot of bug-hunting if it does. |
|
| Author: | McNish [ Mon Jan 28, 2013 7:49 am ] |
| Post subject: | Re: Bob's Biggest Balls Ever |
CADCHF gone berserk for 10.2 short on V1l. Suspended EA for now, will resume an hour later with new H1 candle formation. Anyone else? |
|
| Author: | SteveHopwood [ Mon Jan 28, 2013 10:17 am ] |
| Post subject: | Re: Bob's Biggest Balls Ever |
V 1m is in post 1. I found the cause of the repeated order sends as soon as I looked for it. It is the most gormless mistake imaginable. Hey ho. Those of you who can, go to int CountOpenTrendTrades() and change it to int CountOpenTrendTrades(string symbol). Then change the reference to Symbol() to symbol. Recompile and follow the links to the two errors this generates and change CountOpenTrendTrades() to CountOpenTrendTrades(symbol). |
|
| Author: | McNish [ Mon Jan 28, 2013 10:45 am ] |
| Post subject: | Re: Bob's Biggest Balls Ever |
Thanks Steve, Will edit and report back. |
|
| Author: | babalu4u [ Tue Jan 29, 2013 5:45 pm ] |
| Post subject: | Re: Bob's Biggest Balls Ever |
Hi Steve, the bot on my Cowboy IBFX au mini account have a problem to set tp.... |
|
| Author: | ovisun [ Tue Jan 29, 2013 8:52 pm ] |
| Post subject: | Re: Bob's Biggest Balls Ever |
case 130: Error Invalid stops Check if broker is ecn or not |
|
| Author: | blinkxzero [ Tue Jan 29, 2013 9:19 pm ] |
| Post subject: | Re: Bob's Biggest Balls Ever |
Would the error imply that the broker is ECN but the setting is not changed to true? Or would it mean the broker isn't ECN and the setting is set to true? If you set CrimIsECN to true and your Crim is not ECN, would this result in an error or just use 2 steps to put in your order but still function properly? Thanks for the clarification! |
|
| All times are UTC | Page 23 of 26 |
|
Powered by phpBB® Forum Software © phpBB Limited |
|