Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • fnag
    Participant
    Post count: 3

    My bad, correction: Build version is 890 .

    I have pm’d you in the meantime. Please let me know if you need more/other info.

    In the meantime, the problem seems to be solved, as I stated, by simply going online for 30 seconds on the said FXCM demo. I can do normal testing offline now without issues…

    fnag
    Participant
    Post count: 3

    But it has worked fine offline for several weeks.. Anyway, if you treat the ea confidential I can forward you the entire code, let me know on what email address to send it and I will do so later today.

    As for your other question, I prefer to avoid importing all tick data on a fresh new installation as that takes too much time and cpu during my working hours…

    fnag
    Participant
    Post count: 3

    Hi there,

    Here are my findings – input:

    1. Since 2 weeks I do have exactly the same issue. i.e.: I used an offline MT4 installation build 840 (downloaded from FXCM) and imported the tickstory / Dukascopy data to do EA backtesting. This testing went perfect for several days.

    2. Then from 1 day to another, – and I can confirm as asked in a previous post with Mr Squiggle- with the same EA/ same parameters / settings and NO code change whatsoever, give me the #131 error message:

    OrderSendEx: OrderSend(Sell) invalid trade volume
    OrderSend error 131

    The error report happened with all other EA’s that I tried to test.

    3. Just now (on reading some suggestions in the thread above), I logged into the linked FXCM demo for about 30 seconds, some ticks came in, I went back offline and did re-retest same EA’s again, and now the testing DOES work fine again (apart from the fact that the test results are very very different… with same settings).

    Strange…

    4. Non-related question: modeling quality shows ”n/a” but always a solid full green bar and 0 mismatched chart errors.

    Hope this helps in rectifying this error..

Viewing 3 posts - 1 through 3 (of 3 total)