I trade ProRealTime via a broker and they have minimum stop distances that vary over time due to volatility and market risk.
I’m looking to code something that automatically sets the minimum allowed stop when I enter the market.
As for now I just have a low value that gets rejected a few times until it somehow settles with a stop at minimum allowed distance.
Any ideas on how to avoid this?
Or is there any way to see what the minimum stop distance is at any given time and say something like:
SET STOP pLOSS currentminimumstopdistance
Nope, there is not built-in function to know the minimum stop level in real time (also called freeze level). If only we knew the spread in real-time it would help, I think it will be a new functionnality in future update, since it is often requested!
Hi Nicolas
Any news on this development? As Noxxiq said it would be a useful addition.
For my part I would like to use it in order to help my system avoid taking trades when IG minimum stop is extended as they tend to do that quite regularly and it regularly negatively affects the outcome!
I understand and totally agree. By now, it is still not possible to retrieve this information by the code and I don’t know when IG will send us this crucial information through their pipes..
+1 this is a long time wished for feature and to my mind crucial (my strategies often don’t enter or are stopped out due to min stop distance spikes and knowing the spread would help with order entry timing)
I am able to see this information and base my decisions on entering/exiting trades when manually trading so why not when autotrading? Speaking with IG (senior bloke) yesterday he told me he had tried to push this (as well as BID/ASK prices therefore Spread too) through development some time ago but (understandably) with recent ESMA changes it has had to take a back seat in terms of priorities and there were no promises about anything happening any time soon but good to know at least IG ‘want’ to implement this (rather than anything like wanting to ‘withhold’ this information)
SebParticipant
Average
If ProOrder tries to set a new stop within the minimum stop distance range and fails, the previous stop remains. Is there a feature in ProBuilder language that tries something and takes an error as an acceptable outcome? (Like try:, except: pass in Python) This way the algo would try again next end of bar and you’d have your old stop until than.
Server error for rejected order (or for any other case) cannot be interpreted by the code. That would be very useful I totally agree! 😐
