Thread: vForce Like EA

Originally Posted by fxrobot

I was able to resolve the backtesting issue, and it didn't not require a source code change. I found this article on the mql4.com forum:
All Brokers MT4 platforms invalid prices - MQL4 forum
In it, there is a discussion about exporting the Metaquotes historical data to CSV files, deleting the old HST files, and then importing the CVS back into Metatrader. I tried this and now ALL OrderSend error 4107 problems have disappeared! I am using VForce Like EA v2.0 on an FXDD platform, build 225. All historical data has been downloaded from the Metaquotes server.

I still see the occasional OrderSend error 130 issue showing up in the logs:

I believe this is a separate issue, but right now, I'm not sure what is causing it.

Hi fxrobot,
Thanks for posting that link. Thats a good write-up on a fix for that particular 4107 problem.

I think the NormalizeDouble function may help fix some of the 130 errors. Might need a refresh or similarly named function just before placing the orders.
But I need a round-to-it instead of a sitting-on-it, to get some progress in my coding.

cheers bt2

one month very good profit and after that total crash

Cuold you please send me all indicators in detail, I prefered working manually

Originally Posted by funyoo

A second version that has taken me a while, I have tested a ton of indicators to find the best filters.

Long when :

- Stochastic main over Stochastic signal,
- RSI over 50,
- BearsPower over 0,
- Price over Parabolic SAR,
- Fast Moving average over Slow Moving average,
- Price Action option.

Short when :

- Stochastic main under Stochastic signal,
- RSI under 50,
- BearsPower under 0,
- Price under Parabolic SAR,
- Fast Moving average under Slow Moving average,
- Price Action option.

Two pending stop orders, one with SL and TP, the other with SL and TS.

EU H1. On one year.

Total net profit : 661.25%
RDD : 19.93%

out of all the backtests I've done, this Vforce seems to show the most promise, no doubt. I like all the ways you can play with it, to get to to a good growth that will not bust out

Hi fxrobot,
Thanks for posting that link. Thats a good write-up on a fix for that particular 4107 problem.

I think the NormalizeDouble function may help fix some of the 130 errors. Might need a refresh or similarly named function just before placing the orders.
But I need a round-to-it instead of a sitting-on-it, to get some progress in my coding.

Anytime bt2. I like helping others out since so many have helped me out. Believe me, I've this entire thread, as well as others, many times. Lots and lots to learn on these forums!

I'm not so sure using the NormalizeDouble function would prevent error 130 problems from occurring. The error 130 problem is caused by the EA opening a trade where stop-loss or take-profit levels are set too close to the market price (please see this link:

OrderSend Error 130 — What to Do? — Forex Blog

In order to fix this error, I beleive some mods to the VForce Line EA source code is in order. As soon as I get a better understanding FX markets and MQL4 source code, I can help out!

I've also seen OrderSend 131 errors when using different brokers during back tests. See this link:

Handling OrderSend Error 131 in MetaTrader 4 — Forex Blog

I found other links using Google, but the above is a pretty good reference.

Where can I get the latest version of the Vforce like EA with the best optimization setting.
Chuckie

Hi ,

I added in the code but I get order2size - variable not defined .

How to fix that ?

Do you have a fixed version of 2.04A ?

Regards
Law

Originally Posted by RConcu

Hi Maxim, hi funyoo,

great work, great EA. I like it.

i found the reason why the EA does no short orders.

Put in the code in red:

int openSellOrder( int barIndex )
{
double stopLoss = calculateSellStopLoss( barIndex ),
takeProfit = calculateSellTakeProfit( barIndex ),
orderOpenPrice,
// The order size of both orders
orderSize,
// order1Size
order1Size = g_order1Size,
// order2Size
order2Size = g_order2Size;

.... }

cu Robbi

Hi,

I already solve the problem due a comma should be used instead of semicolon.
Anyway I found another problem with the EA ver 2.04A that turn a sell into a buy so that this version alwasy gtes a buy.

If interested in the fix please please let me know .

Regards
SP

Originally Posted by splaw

Hi ,

I added in the code but I get order2size - variable not defined .

How to fix that ?

Do you have a fixed version of 2.04A ?

Regards
Law