Thread: vForce Like EA

The 'Order Modify Error 130' I'm still getting in backtesting.

Also seeing an 'Order Send Error 4107' from time to time.

.....all on v2. not messing around with 1.

I'm wondering if these losses I'm talking about above are a result of this alltogether? If so, I'll feel stupid later....too busy for that this wekend.

Originally Posted by maximf

Hi,

I ve got a Trend Magic indicator from Magic Machine site.
It somehow detects the trend change. Can we use it for
stopping losses?

Maxim

Dont think it will because at first glance it looks like it repaints. Market is closed but I've seen many of these before and it look like another one.

Along the lines of something that trails, I was thinking about Elder's Safe Zone, but effectively it would be doing the same thing as closing losers on a break of the PSAR or.....same idea and I think it would just overcomplicate.

Honestly dont think it needs anything else, the EA makes money as is, just needs some tweaking of the basic logic, methinks.

Hi all,

thanks to Funyoo for his ea and all members who work for improve it.
I made same backtest than Funyoo for period : jan 2008 to march 09 and have same results, but i see than many loosing trades are in 2009, same for march to may 2009, my question is anybody had optimise settings for 2009 and what settings can we improve ?

thanks for share

Greg

Originally Posted by Geneo

Hi funyoo,

I just started testing vforce on 2 demos.
I am not a programmer at all. Can you please tell us what to add to the code to get Friday and Sunday trading? I am using version2 and version2 for (5 digits).


Thank you.

Geneo

Hi Geneo and welcome,

Here is another version with the time filter options available.

Originally Posted by finimej

funyoo,
Thanks for the EA.
which broker did you test your EA?
I have tried this EA on FXDD, ATC Brokers, Alpari,
all I got is ordersend error 130, and later on order modify error 130. (after the order is modifed).

I think the OrderModify and OrderSend errors are being caused due to the fact that the EA opens several positions close to one another at any given point in time, also putting in new buys and sell stops. Particularly you'll see it on other pairs that carry a wider spread than just 2, like GBP/USD.

I found this today: ordermodify error 130 - MQL4 forum

I'm not a programmer, but it would make sense this being the case. I really wish I was, because Ive got a lot of good ideas for this ea.

Here's more: http://forum.mql4.com/18804

Could have something to do with the bid/ask criteria and the way the ea calls to lock in price/trail, etc.....just my guess.

Originally Posted by winias

I think the OrderModify and OrderSend errors are being caused due to the fact that the EA opens several positions close to one another at any given point in time, also putting in new buys and sell stops. Particularly you'll see it on other pairs that carry a wider spread than just 2, like GBP/USD.

I found this today: ordermodify error 130 - MQL4 forum

I'm not a programmer, but it would make sense this being the case. I really wish I was, because Ive got a lot of good ideas for this ea.

Here's more: Always price error - MQL4 forum

Could have something to do with the bid/ask criteria and the way the ea calls to lock in price/trail, etc.....just my guess.

I just went back to the periods in backtesting where the errors were received and in a few instances it was accompanied with a big loss, but not all. Also weekend gaps were found in a few spots, but again not all. But still cant be 100% whats causing it or what the solution is.

That issue I was taking about where a ton of positions were in the money but the trailing stop never kicked in seems to be as a result of this error. I picked it up on pairs like USD/CHF,etc etc.
I notice there's a void trailing stop area towards the end of the code. Something to do with this?