Home › Forums › Tickstory Lite › Issue/Bug tracking › Export of MT4 Symbol Properties

Viewing 14 posts - 1 through 14 (of 14 total)
  • Author
    Posts
  • imported_tickstory
    Participant
    July 2, 2013 at 12:46 am
    Post count: 1479
    #18965

    Hi Hypernics,

    Thanks for taking the time to raise this issue. We have identified the problem – it is specifically related to the fact that you are mapping the symbol (i.e. XAUUSD->XAUUSD.arm) which causes the system to take default values for that symbol (i.e. 5 digits, etc). A fix has been made and will be available as soon as possible.

    In the mean-time, the workaround is to use the MT4 Editor to correct the values.

    Regards.

    d4amenace
    Participant
    July 3, 2013 at 9:13 am
    Post count: 4
    #18966

    I have tried the manual fix using the mt4 data editor….when I do this and use with birts backtester I get zero divide errors….my broker (profiforex) also uses a suffix (v).

    imported_tickstory
    Participant
    July 3, 2013 at 11:27 am
    Post count: 1479
    #18967

    Hi d4amenace,

    Do you get the zero divide error only after editing the FXT file or before as well?

    We will try to release a fix asap, however would like to make sure that are no other related issues.

    Thanks.

    d4amenace
    Participant
    July 3, 2013 at 1:42 pm
    Post count: 4
    #18968

    The error happens only after I edit the data.

    imported_tickstory
    Participant
    July 3, 2013 at 11:26 pm
    Post count: 1479
    #18969

    Hi d4menance,

    Could you please assist us by providing more details such as:

    1) Are you changing any values when you edit the data?
    2) Do you get the problem when using the Tickstory launcher rather than Birt’s TDS?
    3) What is the symbol you are trying this on along with date range?
    4) Have you tried using the standard MT4 Build 432 to see if you get the same problem?

    Any other information you think might be relevant would help as well.

    Thanks for your assistance.

    d4amenace
    Participant
    July 4, 2013 at 1:57 am
    Post count: 4
    #18970

    [attachment=0:1gmo2f2q]ts1.png[/attachment:1gmo2f2q]

    1)The first box is the Tick Story EA provided broker data that I initially used for downloading tick data. The second box is the data editor opening of 15m on XAUUSD after download. I then open the TS Data Editor and change these incorrect values, in the second box, for what they should be in the first box. This causes the zero divide error.

    2) I have tried to run backtest opening using just birt’s TDS and Tick Story MT4 launcher with the same results.

    3) The symbol I am using is XAUUSD. I have 5 years of data (7/1/2008 to 7/1/2013) This must be where the problem is since dukascopy using a lot of decimal places in their prices for metals. I have not had this problem with currencies under the assumption that it is because typically most brokers use the same amount of decimal places for currency pairs. (The 5 digit brokers).

    4) I have not tried using MT4 432 because metaquotes has gotten very smart and forces you to upgrade any version you open to 509 regardless, since at some point you have to log on to an account to get broker feed. It immediately senses an old version and updates.

    *Note: The downloaded Dukascopy data has 3 or 4 decimal places worth of pricing in their ticks which is the reason why XAUUSD must be changed for my broker. (Downloaded Dukascopy sample price 1025.2632…. what is necessary for my broker 1025.26)

    Also very interesting is the fact that I can backtest with the downloaded incorrect decimal places feed of XAUUSD but of course the test is wrong since too many decimal places are used.

    imported_tickstory
    Participant
    July 4, 2013 at 11:13 am
    Post count: 1479
    #18971

    Hi d4menace,

    Many thanks for the additional info. We are in the process of seeing whether we can reproduce your issue. Couple more questions that will assist:

    – Can please confirm that it stops on a “standard” EA such as the “MACD Sample” provided with MT4?
    – Is there a particular date range we can use where you know the back-test will stop? Ideally, we need the shortest period required to reproduce the error (a few days would be the best).

    Regarding point 3), Dukascopy data only has 3 decimal points for metals, so not sure where you are seeing more?

    Regarding point 4), could you please download the MT4 Build 432 from here:

    http://www.tickstory.com/files/MetaTrader432.7z

    This Metatrader installation will not automatically update as it does not connect to any broker. If you could try this, it would narrow down the issue further.

    We will get back to you if we find out further information.

    Thanks again.

    imported_tickstory
    Participant
    July 10, 2013 at 12:49 am
    Post count: 1479
    #18972

    Hi all,

    v0.9.2 has just been released to address the above two issues. That is:

    •[TICKLITE-114] MT4 Export: Export uses incorrect MT4 Info when exporting a mapped symbol.
    •[TICKLITE-116] MT4 Editor: Editing FXT file caused crashes/zero-divide errors.

    Thanks for your assistance in identifying and reporting the issue.

    Trader2384
    Participant
    August 7, 2013 at 2:56 pm
    Post count: 75
    #18973

    Hi,

    I have read through this thread and am still not able to correctly backtest GOLD or GOLDmicro.
    I am running the latest version of Tickstory
    I have tried on mt4 432 as well as version 509.
    For all EAs (included standard ones) It opens only 1 order and immediately closes it.

    Thank you 🙂

    imported_tickstory
    Participant
    August 9, 2013 at 1:24 am
    Post count: 1479
    #18974

    Hi Trader2384,

    If you are having issues with a specific EA it is hard for us to troubleshoot what it is doing. From a Tickstory point-of-view, as long as you are getting a “99%” quality back test, it indicates you are using tick data correctly. After that, it is a matter of trouble-shooting why the EA is closing a trade early or what-ever you believe is the incorrect behaviour. You will need to check things like whether you have sufficient equity, etc.

    Hope this helps.

    ejcmartins
    Participant
    January 17, 2014 at 12:22 am
    Post count: 1
    #18975

    Hi, as a user(Trader2384) told you before, there is a problem on the conversion of XAUUSD to GOLD. The problem was found when the EA didn’t work at all, the same case as this trader, then it was solved using “MAP TO” changing the name to another pair name that is already used.

    For example: I was exporting XAUUSD using “MAP TO” changing the name to GOLD to test the EA, It just starts and closes almost at the same time, but when i changed the “MAP TO” to GBPUSD it worked, the “new” GBPUSD was actually with the GOLD data and EA kept working normally as it was working before on others pairs.

    This error was fixed by my son Rafael Clain Martins,he is a programmer like me.

    imported_tickstory
    Participant
    January 20, 2014 at 3:42 am
    Post count: 1479
    #18978

    Hi Ejcmartins,

    Could you please do a comparison between your “MT4 Symbol” info between XAUUSD and GBPUSD. It is possible that the instrument information for XAUUSD is not configured fully which could be causing the issue (for eg. the Lot Step setting could be zero causing an issue).

    Regards.

    zanzistor
    Participant
    January 21, 2014 at 3:08 pm
    Post count: 4
    #18976

    .

    imported_tickstory
    Participant
    January 21, 2014 at 11:22 pm
    Post count: 1479
    #18977

    Hi – If it is working with the settings from GBPUSD, then the first step would be to copy all those settings and use them when exporting XAUUSD. If the back-test looks betterm then fine tune the individual settings (Lot step, etc) from there so they correspond with your broker’s settings.

    Hope this helps.

  • Author
    Posts
Viewing 14 posts - 1 through 14 (of 14 total)

You must be logged in to reply to this topic.