Page 40 of 54 FirstFirst ... 30383940414250 ... LastLast
Results 391 to 400 of 539
  96 96 Attachment(s)    

Thread: vForce Like EA

  1. #391
    Junior Member
    Join Date
    May 2009
    Posts
    17

    Default VForce Like EA Testing

    Quote Originally Posted by bt2 View Post
    Funyoo fixed that error in v202, see page 33 post 323. He says needs re-optimize now, cause its a structure change (fix).
    I've done very little optimization...it's not my expertise, but I'll try it and see what I get.

    Quote Originally Posted by bt2 View Post
    I also run my versions in M15, in FXDD demo. More trades to get things moving & check ea's trade handling. But I have not worked out if it would run better in H1. Thats why I asked if you had done backtest on v202. Would be great if you could, over the exact same time period & chart you did the v1.1 over.

    Would be interesting to do the same with a "fixed" v1.1
    I'll try this and start collection data graphs and post them. I'm also try to see about getting server data from all the major fx brokers (IBFX, FXPRO, FXDD, Alpari, etc). Alpari no longer supplies HST data for MT4, so I need to find additional free sources of historical data.

    Quote Originally Posted by bt2 View Post
    I have loaded up the indicators on a separate chart to get a feel for when orders could be coming. The psar has a big effect on wether the ea is finding only long or only short trades, for quite long periods. Thats part of the catching trends I guess.
    Which indicators are you using? The ones Funyoo posted a long while ago? I haven't tried these out yet, just the simple back testing and forward demo testing. There is obviously more work to be done in this area.

    If I can find the time and correct data, I'll back test all versions of VForce Like EA with all major broker's data at M15, M30, and H1 time frames. That would be a great test strategy to perform...lots of good data to analyze.

  2. #392

    Thumbs up Indicators in v202

    Quote Originally Posted by fxrobot View Post
    Which indicators are you using? The ones Funyoo posted a long while ago? I haven't tried these out yet, just the simple back testing and forward demo testing. There is obviously more work to be done in this area.

    If I can find the time and correct data, I'll back test all versions of VForce Like EA with all major broker's data at M15, M30, and H1 time frames. That would be a great test strategy to perform...lots of good data to analyze.
    Hi fxrobot,
    I only load the indicators that are checked inside the v202. They are all standard MT4 indicators. Template attached for info.
    There are more indicators used in v1.1 & most check the next older bar also. That might be helping with your v1.1 on M15.

    As I also add comments into the ea's to see what they are upto, I dont load the ea's on the same chart cause it would be too cluttered.
    The ea's dont like changing timeframes while running, extra sets of orders pop up sometimes.

    Do you have a set file for your v1.1 that you could post. How do you get to see/access them outside the MT4 platform.

    cheers bt2
    Attached Files Attached Files
    Last edited by bt2; 06-22-2009 at 01:52. Reason: cant spell for shet

  3. #393
    Junior Member
    Join Date
    Jun 2009
    Location
    Berlin
    Posts
    8

    Default short orders with vForce 2.04A

    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

  4. #394
    Junior Member
    Join Date
    May 2009
    Posts
    3

    Default

    Hi.
    I'm looking for 5 digit version vFors 4

  5. #395

    Default

    can someone amend the latest vforce EA so it trades shorts and post it for us please?

  6. #396
    Junior Member
    Join Date
    Jun 2009
    Posts
    3

    Default OrderSend Error 130 ó What to Do?

    Hi!
    I'm having problems with error 130 and now I know what happens but I don't know anything about programming. If somebody know how to make this....


    The expert advisors that work on one broker can stop working on another; the problem with them often lies in OrderSend Error 130. If you see Error 130 in the Log of your MetaTrader platform when your expert advisor should be opening a position, then that means that the stop-loss or take-profit levels are set to close to the current market price. In the MQL documentation this error is called ERR_INVALID_STOPS (ęInvalid stopsĽ). Some Forex broker set the minimum distance between the current price and the stop-loss/take-profit levels to prevent scalping or abusing the quote delays. Thatís not a real problem for the majority of the expert advisors that donít use scalping. To prevent this error from occurring, you need to change the expertís code.

    First, you might want to know whatís the minimum stoplevel is set in your brokerís MetaTrader server. Adding this line of code will output the current minimum stoplevel for the currency pair of the chart, where you run the EA:
    Print(MarketInfo(Symbol(),MODE_STOPLEVEL));

    You shouldnít be using stop-loss or take-profit level, which are closer than MarketInfo(Symbol(),MODE_STOPLEVEL) to the current market price. If your EA calculates stops and take-profits dynamically, this is what I suggest you to do:

    1. Declare a global variable for the minimum StopLevel; e.g.:
    int StopLevel;
    2. In the init() function of your expert advisor define the minimum StopLevel:
    StopLevel = MarketInfo(Symbol(), MODE_STOPLEVEL) + MarketInfo(Symbol(), MODE_SPREAD);
    Note, that adding a spread difference is also required.
    3. The next time your stop-loss or take-profit is calculated, just check them to be not less than StopLevel:
    if (StopLoss < StopLevel) StopLoss = StopLevel;
    if (TakeProfit < StopLevel) TakeProfit = StopLevel;
    4. Donít forget to refresh the current market rates with RefreshRates() before adding the stop-loss/take-profits levels to the actual market rates.

    That should help in the majority of the cases. At least, for me such handling of the OrderSend Error 130 has always worked.

  7. #397

    Smile vForceLikeEAv202

    Quote Originally Posted by Viv108 View Post
    can someone amend the latest vforce EA so it trades shorts and post it for us please?
    Hi Viv108 & Abe fine,
    Funyoos latest version is v202, located in post 323 here vForce Like EA

    It trades buy & sell at different times, depending how it reads the market trend.
    It is also setup for 4 & 5 digit brokers.

    I think the PriceActionFilter should be left false as its still using current close instead of current price in the code.

    Have fun.

    cheers bt2

  8. #398
    Junior Member
    Join Date
    Jun 2009
    Posts
    3

    Default OrderSend error 4107

    The second problem that people have is OrderSend error 4107

    2009.06.19 18:45 vForceLikeEA_V2_03 EURUSD,M15: OrderSend error 4107
    2009.06.19 18:45 vForceLikeEA_V2_03 EURUSD,M15: invalid price 1.39937000(Why 8 digits???) for OrderSend function

    I'm not programmer but I try to help....

    The price that is send with OrderSend function should be normalized to the standard of rates that is used in your brokerís MT4 server. For example, if you try to use price like 1.23339 to open EUR/USD position and the current EUR/USD rate at your broker is 1.2334, it wonít work because your order open price isnít normalized. If your broker uses 6-digit quotes for EUR/USD then sending price like 1.2334 when the actual rate is 1.23345 will also generate OrderSend Error 129. In any case you should use NormalizeDouble function to fix the open price before sending it to your broker. It takes two parameters: first is the value you want to normalize (the price), second is the number of digits after the dot in the resulting number. Here is the example of its usage for the brokers with 6-digit quotes (like 1.23345 for EUR/USD):

    OpenPrice = NormalizeDouble(OpenPrice,5);
    OrderSend(Symbol(), OP_BUY, 1, OpenPrice, ...);

    Itís also a good idea to normalize all your StopLoss and TakeProfit values before using them in the OrderSend function. This is a good coding practice even if you donít get any Error 129 messages.

  9. #399

    Talking Good Info

    Quote Originally Posted by zetapaf View Post
    Hi!
    I'm having problems with error 130 and now I know what happens but I don't know anything about programming. If somebody know how to make this....
    Hi Zetapaf,
    Thanks for the good info & your next post too. I will have a play. Problem is I dont get the error as I have been using Funyoo's v202. I think there are a few little errors in Maximf's v203 & 204 still. They were posted before Funyoo fixed an error in his & posted his v202.

    Where do you get your info from? Looks like an easy to read source.

    cheers bt2

  10. #400
    Junior Member
    Join Date
    Jun 2009
    Posts
    3

    Default

    I have problems with every version.

    2009.06.23 23:34:44 2009.06.08 17:00 vForce Like EA v202 EURUSD,M15: OrderSend error 4107
    2009.06.23 23:34:44 2009.06.08 17:00 vForce Like EA v202 EURUSD,M15: invalid price 1.36239000 for OrderSend function

    Here is the info:
    OrderSend Error 129 ? What to Do? — Forex Blog
    OrderSend Error 130 — What to Do? — Forex Blog

Similar Threads

  1. vForce Like EA v2
    By funyoo in forum Expert advisors live statements
    Replies: 113
    Last Post: 10-21-2013, 19:59
  2. VForce Like EA v1.1
    By fxrobot in forum Expert advisors live statements
    Replies: 5
    Last Post: 08-29-2009, 15:15
  3. vForce EA Great Trading System
    By iForex in forum Ideas for expert advisors
    Replies: 5
    Last Post: 06-16-2009, 16:00

Tags for this Thread

100, advisor, alpari, alpari uk, analysis, automated trading, automatic, average, backtest, backtesting, bonus, breakeven, broker, brokers, change, closing, coding, color, comparison, copy, correlation, demo, design, divergence, eas, elite, eur, eur/usd, eurjpy, eurusd, expert, expert advisor, experts, forex, free, fxopen, gbpusd, hedging, high, historical, home, how to, indicator, indicators, learn, live, live account, low, magic, magic number, main, managed, manual, manual trading, metatrader, moving average, mq4, mql, mt4, mt5, offer, parabolic sar, power, price action, profit, profitable, programmer, programming, rating, real, research, review, robot, robots, rsi, sales, sells, server, signal, signals, simple, slippage, spread, stoch, stochastic, stop, stoploss, strategy, support, system, test, thank you, time, trader, trading, trading forex, trading system, trading volume, trailing, trend, usd

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •