ProOrder stopped – stop below minimum distance (IG Index)

Forums ProRealTime English forum ProOrder support ProOrder stopped – stop below minimum distance (IG Index)

Viewing 15 posts - 31 through 45 (of 55 total)
  • #196463

    And that is thus not working. Yeah, for 3 days only.

    On Fx the seconds would provide 1 month (with 1M bars).

    I was thinking Giddy could get 1 million bars?

    #196464

    You are correct.  I thought too much of my own situation. Sorry !!

    1 user thanked author for this post.
    #196669

    Sorry, been away for a few days.

     

    As far as I can see, I can only get 200,000 bars backtest in live.  Not tried demo as yet.  Systems definitely ‘working’ since I made the adjustments but the limit orders are way too wide for anything to have been triggered…so no actual deals.  Backtesting suggests that one or two deals per month, per strategy seems to be the average – way down on ‘normal’.  To stand any chance of making them work (££), I either need to up size significantly or increase the number of live strategies….both of which increase my risk so not ideal.

     

    Re timeframes, my minimum (that I use) is one minute but the vast majority are 15 minute (so I would have thought IG’s systems should be able to hedge/cope with that?).  Backtests on these run from 2014 but since the issue seems to be with IG, the ‘theoretical’ performance run via the PRT backtests won’t be affected by the IG distance changes?

     

    Still no response to my follow-up questions to IG so not sure if this is something they have applied to my account only.  Going to try a few different options over the next few days.

    #196676

    Have you tried it without pending orders? So with “Close crosses under” or “high > highest(x)high[1]”?

    #196677

    (so I would have thought IG’s systems should be able to hedge/cope with that?)

    No ? once your order with 4 points above the price (Limit) becomes active, they have “4 points” which could be 0.2 seconds.
    It is all computer systems anyway (I’d say) but even a second could be “not so much” if you’d have to stroll all bids elsewhere – and again – and again – until you must give up and be too late anyway.

     

    Have you tried it without pending orders? So with “Close crosses under” or “high > highest(x)high[1]”?

    Of course the intentions are good, but now the opposite will be at work from what I just told :
    Now after 15 minute the price rose 30 points and you buy at market (you initiated that 14:59 minutes ago). The RSI by then is at 100+ 🙂 and there goes your trade.
    Btw, I am not claiming that you won’t be able to make profit this way, but if your system has not been set up from the ground like that, you will relatively only “lose” (make less profit up till lose indeed).


    I could have expected that @nonetheless would have jumped in on a thing like this ? are you still there ?

    #196681

    are you still there ?

    I’ve been worried for a few weeks that nonetheless has blown his account, got covid or worse … hope he replies!

    1 user thanked author for this post.
    #196685

    By the way… without wanting to open a new topic… Why can it be that my systems in M1 don’t always open a trade safely, my M3 systems do? They are exactly the same except for the time frame.

    #196686

    By pending orders I mean of course.

    #196687

    With pending orders, I think they can. But this was not what you were suggesting ?

     

    Have you tried it without pending orders? So with “Close crosses under” or “high > highest(x)high[1]”?

    At least that is what I was responding to …
    (maybe we talk past each other)

    #196688

    I was just about to post my own problem and someone can give me an answer. 😉 My M1 systems and the M3 systems are exactly the same… only my M1 systems don’t always safely open a trade with a pending order. My M3 systems always open. Why?

    #196689

    don’t always safely open a trade

    What do you mean by ‘safely’?

    #196692

    M1 is NOT always reliably triggered in reality. M3 always.

    1 user thanked author for this post.
    #196723

    Further response from IG:

     

    Confirming with the dealing desk in regards to your query, the change is affecting Forex pairs as well as Cryptocurrencies only. No mention of it currently being in place for markets such as Indices or Commodities.

     

    The Stop and Limit type Working Orders will need to be set 50 points away from the current market price.

     

    In regards to when it may be reverted, the change will be regularly reviewed by the dealing desk.

     

     

    1 user thanked author for this post.
    #196840

    IG change settings and stop executing orders by the dealing desk as they choose and without warning.

    I have witnessed rejected market orders occur for minutes and longer durations that you probably do not want to know (this is not through PRT but via other algorithm trading methods to IG).

    I have 1000’s of logs showing rejected orders when they should NOT be rejected and closed markets when they show a price feed and the market should be open but the logs say market is closed.

    Other brokers don’t set such limits so instead you have to accept a lot more slippage instead of rejected orders and limits.

    2 users thanked author for this post.
    #196862

    Thanks David. It’s really frustrating – system was working perfectly and now it doesn’t even open trades. I’ve modified so that trades *should* open as the orders are wide enough but I’m still having issues.  I’m still trying different options but out of interest, who else (other brokers) offer cfd/spread betting via PRT? I might have to go down that route – a little slippage is fine, I’m happy to give up a couple of % rather than 100%, which is the case now with IG because of no trades.
    Thanks again 👍

     

Viewing 15 posts - 31 through 45 (of 55 total)

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