fxDreema

    • Register
    • Login
    • Search
    • Back to the main page
    • Categories
    • Recent
    • Tags
    • Popular
    • Search

    Psar wrong value?!?

    Bug Reports
    2
    4
    954
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B
      Babago last edited by

      Hi FxDreema,
      i'm using your masterpiece of software since more than 2.5 years now with a lot of satisfaction..
      But now i'm facing a problem that i didn't resolve in more than two months..
      So here i am asking your help..

      I have this EA that check in all my running trades if PSAR value is higher or lower than price and then alert me and do stuff...

      https://fxdreema.com/shared/iu7ohSHmb

      Here the problem: once every a while, about once or two a day (i can't replicate the problem), the EA trigger because it reads a wrong value of PSAR.
      Here a picture of a notification with the values of EA's variables it just worked on,
      where Psar is lower than price but that isn't the correct Psar value!

      https://s31.postimg.org/bxpwi4dez/Copia_di_IMG_7106.jpg

      https://s32.postimg.org/y9jzcyt3p/Copia_di_IMG_7107.jpg

      If i immediately reset the take profit to allow the EA to check again that trade, it doesn't trigger anymore..
      it seems it reads a wrong value of Psar just for a second, but the second after reads the correct value...

      Here some of the steps i tried to avoid this problem..

      1. i've cheked it not depends on spread (and for this reason i made the condition block with bid price..)... but didn't resolve

      2. I used delay block imagine that too many calculations and switch between markets can create problems in reading indicator data..... (in past i had some strange behaviour when using "Set "Current Market" for next blocks" in loop to check all trades and i resolved with the daly block set to 5 seconds) ... i set it on 1 sec but didn't resolve, i cant set it on 5 sec beacause it would be too slow..

      3. i used candle id 1 to avoid repaintings... but didn't resolve

      4. i first store values of Psar and Price in variable and then compare them with the "condition" block... but didn't resolve

      5. i tried it in backtest with "trace" block to check if were problems... but didn't find any problem..

      6. Probably most important, i first start using built-in PSAR indicator and then switch to parabolic.mq4 also of Metaquotes.. ... but didn't resolve with both of them..

      Can you put me in the right direction to resolve this problem? i'm givin up..
      Thank you very much!

      1 Reply Last reply Reply Quote 0
      • fxDreema
        fxDreema last edited by

        This is more than 100 pips difference. The value looks like it comes from D1, but probably not. Can this mobile MetaTrader take screenshots? Because there is a block that can do that and maybe this is the best way to investigate this problem. How often this happen?

        Do you actually use "Set Current Market..." for other symbols, different from the the symbol that belongs to the trade? I don't understand why this block is used.

        1 Reply Last reply Reply Quote 0
        • B
          Babago last edited by

          1- Every time it happened the difference with the correct value was big
          2- Yes i can add the block to take screenshots but i didn't think it can be useful because Psar is not a repainting indicator... but i can add it!
          3- Now are 2 days it doesn't happen.. i think it happens on an average of 48hr. But sometimes less than 12
          4- I use "Set current market" because i use to check with one EA all my running trades. I can't leave open a chart for each pair...

          1 Reply Last reply Reply Quote 0
          • fxDreema
            fxDreema last edited by

            Who knows. It's interesting that both PSAR fail - the built-in and the one that is as a custom indicator. I think that it's something with the indicator itself, but I don't know exactly how it works. And it's also very hard to find the reason of the problem when the problem happens very rarely 🙂

            1 Reply Last reply Reply Quote 0
            • 1 / 1
            • First post
              Last post

            Online Users

            O
            E
            M
            C
            F
            S
            S

            17
            Online

            146.8k
            Users

            22.4k
            Topics

            122.6k
            Posts

            Powered by NodeBB Forums | Contributors