CP only checks whether the market is already at or beyond, the candle's hilo. It does not check to see if the stop order price is far enough away from the market to fulfil the stop level requirements. When the proposed stop order price is not far enough from the market to meet these requirements, an 'invalid stop' error 130 is generated.alecsa72 » Wed Sep 20, 2017 11:38 am wrote:
Tickmill (Seychelles)
There is a crapql constant that returns the stop level - MODE_STOPLEVEL. Run the attached script and you will see what your broker's stop level is.
I could add code to deal with this were it not for this little gem from the documentation:
So there is every chance I would be wasting my time. I will add some code to stop the error showing and send an immediate market trade when it is generated.
MODE_STOPLEVEL
Stop level in points
A zero value of MODE_STOPLEVEL means either absence of any restrictions on the minimal distance for Stop Loss/Take Profit or the fact that a trade server utilizes some external mechanisms for dynamic level control, which cannot be translated in the client terminal. In the second case, GetLastError() can return error 130, because MODE_STOPLEVEL is actually "floating" here.
That will cause some trades to look as though they have been sent incorrectly. Tough. Take it up with your broker.
Notably, Global Prime has a zero stop level. GP clients do not care about this situation because it does not arise. So, time for another plug for GP.
Anybody who can become a Global Prime client but still is not one, is barking at the moon so far in the wrong direction that the moon you should be barking at is tapping you gently on the back, coughing discretely to gain your attention and saying softly, "Ahem. Try barking at me. You might get a reply."
