ORB 15M error with buy limit MultiTimeFrame

Forums ProRealTime English forum ProOrder support ORB 15M error with buy limit MultiTimeFrame

Tagged: , , ,

Viewing 12 posts - 1 through 12 (of 12 total)
  • #81133

    Hi everyone, i have a problem, here is my system that i’m working on, is a Breokout of the first 15m bar, in a 5m timeframe default.
    The problem is that the price limit is not respected, as you can see in the photo.

    errore-1

    Here is the code:

    #81142

    Your strategy works fine as you asked it to do!

    As from the attached screenshot you can see that at 9:55 it enters a trade because the conditions were true in the setup bar at 9:50. Condition you asked to be met were that the previous candle (at 09:45) had crossed over RES, which it did!

    Lines 19-20 can be written

    since for a crossover/under to be true CLOSE must be above/under RES or SUPP.

    The problem is, I guess, that you are referencing the previous candle ([1]) instead of the current one.

     

    1 user thanked author for this post.
    #81178

    Your strategy works fine as you asked it to do!

    As from the attached screenshot you can see that at 9:55 it enters a trade because the conditions were true in the setup bar at 9:50. Condition you asked to be met were that the previous candle (at 09:45) had crossed over RES, which it did!

    Lines 19-20 can be written

    since for a crossover/under to be true CLOSE must be above/under RES or SUPP.

    The problem is, I guess, that you are referencing the previous candle ([1]) instead of the current one.

    yes, it work fine, but i want that when the cross happens the buy/sell order must be at the limit price of the 15m bar of  9.15 that i supposed will be

    but, price of traded are executed to the max of tha last bar.

     

    the line 19 is ok, because the condition are 2, first the bar (1) have to cross, second the last bar have to close over or under the level, then the system have to put a limit order only at the PRICE of 9.15 (max and minimum)

     

    #81179

    Also in your test there is the difference i am talkin for. The price of “res” is different from the price of execution.

    #81193

    Sorry if I’m wrong, but since maxsetup=res and you are already above it because “longok” is true, why are you putting a pending STOP order? Buy at a level below the current price is made with a LIMIT order. Same goes for short orders.

    #81199

    Sorry if I’m wrong, but since maxsetup=res and you are already above it because “longok” is true, why are you putting a pending STOP order? Buy at a level below the current price is made with a LIMIT order. Same goes for short orders.

    i tried also with LIMIT but price is not respected sometimes

    #81200

    Here the img of todayCattura

    #81203

    Sorry if I’m wrong, but since maxsetup=res and you are already above it because “longok” is true, why are you putting a pending STOP order? Buy at a level below the current price is made with a LIMIT order. Same goes for short orders.

    Hello, i’ve solved the issue, there was something wrong with the variable maxsetup/minsetup

     

     

    #81204

    But there is still some problems with some orders, like in this. The 31/07/2018 at 9.40 am, the sistem should put an order long at 12.816,80 but that price was never touched in that bar and te sistem bid at 12.807

    Cattura-1

    Any idea?

    #81209

    After line 21 insert these lines:

    otherwise they’ll never be reset and lines 25 and 33 will never be true again!

    Also, despite not affecting the strategy itself, this code is logically WRONG (lines 19-20) as I said before:

     

     

    1 user thanked author for this post.
    #81216

    GRAPH is your best friend when debugging.

    #81225

    GRAPH is your best friend when debugging.

    Totally true 🙂

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

Create your free account now and post your request to benefit from the help of the community
Register or Login