Nanningbob 10.2 auto-trading EA

[rjp9697]

Hi all

I've just joined the forum and have setup the 10.2 EA on an Alpari demo account, having read into the documentation. The EA is working fine and trading, but I'm getting the following error message in the Expert Tab:

"2012.07.19 12:35:08 Cannot open file 'C:\Program Files (x86)\Demo Trading Accounts\Alpari - Nanningbob 10.2\experts\indicators\10.2 WOH 2x1 4.29.ex4' on the USDJPY,H4"

I've searched the forum but couldn't find any info on this error.

Can anyone assist?

Thanks.

John

[garyfritz]

Thanks gary, that's kind of what I had figured when I set it up...but the EA is calling for them. Different names from the indi's I have now.

Gack. I posted that at 2am and obviously my brain wasn't working. Didn't think to check the code.

Yes, it does require two indis. As patman said, it appears to be two copies of the same indi with different names?? You'd have to ask Steve about that one.

[patman]

John, (rjp9697),

Really????
Just look at the post just above yours.
Read it

Ta daa

[rjp9697]

Thanks Patman. See it.

[SteveHopwood]

I thought this EA was going nowhere, which is why I locked the thread.

Earlier tonight, I received this from Panamamike:
"Hi Steve,

Wy is the EA suspended and no longer being updated? I am having excellent success trading this live and in Demo. For instance my 5k demo account started on 06/26 started this week at 7.45k. My live results are excellent as well. I trade it using 1% per trade. My two live accounts are also doing very well. No large draw downs. The issues mentioned in the thread can be minimize and eliminated by changing settings and using MPTM. It would be nice to fix the issues outright. It has done much better than any of the other 10.2/A based demos thus far."

So, I have the pleasure to reopen this thread. The EA was useless to me, but we all know that different crims = different feeds = different results. I should be learning by now that different users with dirrerent ea's should be achieving different results.

Hey ho.

[Panamamike]

If any coders are still following the thread. I have a version that was edited by al3xx and posted on July 01. I would like to change one aspect of the version I am trading. I would like to replace the stacked trades with a user defined choice of position size to the following to add to the D1 and D1/H4 positions.

When the pair is in +-.08 "buy and hold" and "Sell and hold" Add a position a user defined amount of pips below above/below the previous day H/L. In fact, if we can user define the time period of the previous candle we want to trade the H/L break of would be even better.

[Panamamike]

I am attaching the version I am using. My posts on page 50 explain how I am trading the EA. I am not using it as a set and forget robot.

[rewand]

I traded this EA with success, too, until it started to open multiple trades. Anyone fixed that issue? Without that it is still dangerous... Should not close threads without giving the reason why/in what cases the EA/strategy fails. I think this would put the site in order, too. Guys, "New" does not mean "better".

[Panamamike]

It has to do with the coding for the stacking. I would like to replace the stacking with adding positions in strong trends when previous day H/L are broken in the direction of the trend.

[al3xx]

It has to do with the coding for the stacking. I would like to replace the stacking with adding positions in strong trends when previous day H/L are broken in the direction of the trend.

I thought I fixed the problem with stack trades but now that I looked at it, and from Panamamike, I think I solved it halfway.

To explain for the coders out here, the use of factor to see the pippets from pips wasn't implemented in all cases and that broke the OkToStack function. 50 pips got interpreted as 5 pips and voila.

I suppose anyone using the latest EA is getting the 'correct' wait before the first stack trade happens and then everything goes haywire.

The reason could be because the line that indicates where the next stacked trade should be doesn't move up after entering a stack trade. Means OkToStack is still using the old stack line and always returning true. That's my theory right now and I haven't checked it out. You could probably survive by moving it manually. I haven't alot of time right now and will be probably be gone from the computer for a week or so but probably some coder can make time to check that out. If not, I will check it a soon as I can.

Panamamike has an idea of how the stack trades can be improved and am not sure if solving the bug described above would be sufficient. Then, not nessesary to implement his idea.

I am attaching a fix for an issue that could cause it to constantly reset the stoploss if you are using any of the TS BE CS stop methods (It was fixed in the last one, but not in all the cases). The problem is that it wasn't moving the visible line to the new stop and yet, the hidden stoploss magic uses the position of the line to read the current stop each time to know if to move the stop or not. Let us see how it goes.

Kind Regards,

Alex