Ordermodify error 130 при тестировании

MQL для тебя

MQL для чайников, программирование на MQL4, MQL5

Вопрос №5 — «Коды ошибок при тестировании советника»

Что значит 2010.02.01 17:00 MyExpert GBPUSD,M15: OrderModify error 130
почему обычно эта ошибка возникает?

Очень много подобных вопросов мне приходит. Поэтому публикую таблицу кодов ошибок. Например посмотрев вышеописанную ошибку error 130 становится понятно, что функция OrderModify пытается изменить стоп-лосс или тейк-профит слишком близко к текущей цене.

Коды ошибок

GetLastError() — функция, возвращающая коды ошибок. Кодовые константы ошибок определены в файле stderror.mqh. Для вывода текстовых сообщений следует использовать функцию ErrorDescription(), определенную в файле stdlib.mqh.

Коды ошибок, возвращаемые торговым сервером или клиентским терминалом:

Коды ошибок выполнения MQL4 программы:

Источник

OrderModify и error 130 — моделирование по ценам открытия

Позиция на покупку открывается по Аску, а закрывается по Биду. Поэтому прежде всего нужно знать, что при подтягивании стопа нужно работать с ценой бид.
Далее. Если, как Вы утверждаете, подтягивание происходит слишком близко к рынку, то сама логика ситуации подсказывает Вам решение — сначала проверить цену на предмет близости, потом подтягивать, если близость допустимая.

Позиция на покупку открывается по Аску, а закрывается по Биду. Поэтому прежде всего нужно знать, что при подтягивании стопа нужно работать с ценой бид.
Далее. Если, как Вы утверждаете, подтягивание происходит слишком близко к рынку, то сама логика ситуации подсказывает Вам решение — сначала проверить цену на предмет близости, потом подтягивать, если близость допустимая.

Это правильно, если тестировать по тикам (методы «все тики» или «контрольные точки»). А как быть, если тестирование осуществляется «по ценам открытия». Как я уже упомянул, 1,3508 — это цена открытия текущего бара.
Как здесь написано, произойдет сравнение, SL не подтянется, правильно. Теперь следующий запуск функции start() произойдет ЛИШЬ на цене открытия следующего бара (так как метод моделирования по ценам открытия). И SL не будет подтянут. А само тело текущего бара запросто может пробить уровень SL, который не был выставлен.

Источник

Модификация ордера ошибка 130

Всем привет! Советник работает хорошо, но бывает выскакивает ошибка 130 , а бывает не выставляет ТП, бывает очень редко, в основном на движухе и то не всегда. Но это очень напрягает. Вот кусок кода и модификация ордера. NumberOfTry=5 , то есть всего 5 попыток. Понимаю, что цена за это время пока он крутит эти 5 попыток цикле уходит дальше чем ТП+Проскальзывание и потому вылетает эта ошибка 130. Но как сделать, чтобы он открывал по цене какая есть? Хотя тоже понимаю, что цена может рвануть сильно и никакое проскальзывание не спасёт и будет невозможно выставить ТП даже по новой цене или это не так? В общем, помогите опытные товарищи, советом как поступить?!

Всем привет! Советник работает хорошо, но бывает выскакивает ошибка 130 , а бывает не выставляет ТП, бывает очень редко, в основном на движухе и то не всегда. Но это очень напрягает. Вот кусок кода и модификация ордера. NumberOfTry=5 , то есть всего 5 попыток. Понимаю, что цена за это время пока он крутит эти 5 попыток цикле уходит дальше чем ТП+Проскальзывание и потому вылетает эта ошибка 130. Но как сделать, чтобы он открывал по цене какая есть? Хотя тоже понимаю, что цена может рвануть сильно и никакое проскальзывание не спасёт и будет невозможно выставить ТП даже по новой цене или это не так? В общем, помогите опытные товарищи, советом как поступить?!

Добрый день.
замените Аsк на MarketInfo(_Symbol,MODE_ASK)
в большинстве случаев помогает.

а еще можно перенести расчет тейка в цикл перед отправкой запроса на модификацию, так будет лучше, расчет тейка будет происходить по текущим данным цены.

Andrey Kisselyov :
Добрый день.
замените Аsк на MarketInfo(_Symbol,MODE_ASK)
в большинстве случаев помогает.

а еще можно перенести расчет тейка в цикл перед отправкой запроса на модификацию, так будет лучше, расчет тейка будет происходить по текущим данным цены.

Спасибо буду пробовать. Вот что получилось))

Источник

OrderModify Error 130 on pending orders

I got the error «OrderModify error 130» but I do not why I got this error since I have all required check on take profit and stop loss before to call the function orderModify.

Below is my code:

I got the error «OrderModify error 130» but I do not why I got this error since I have all required check on take profit and stop loss before to call the function orderModify.

Below is my code:

int openOrder(int cmd, double volume,double priceDistance=0, double sl=0,double tp=0)
<
double marginFree = AccountFreeMargin(); // Allow some slack
double marginPerLot = MarketInfo( Symbol(), MODE_MARGINREQUIRED );
double stoplevel = MarketInfo(Symbol(),MODE_STOPLEVEL)*Point; //minimum stop loss/ take profit level, in points or pending order
double freezelevel = MarketInfo(Symbol(),MODE_FREEZELEVEL)*Point;

//number of digit for min lot
double maxLot = MarketInfo(Symbol(), MODE_MAXLOT);
double minLot=MarketInfo(Symbol(),MODE_MINLOT);
int lotDigit=2;

if(minLot==0.1)
lotDigit=1;
else if(minLot==1)
lotDigit=0;

double size =volume;

size=NormalizeDouble(size,lotDigit);
string description;
size=MathMax(minLot,size);
size=MathMin(maxLot,size);
if(!CheckVolumeValue(size,description))
<
lastErrorMessage=»Volume is not correct»;
lastDateErrorMessage=TimeCurrent();
Print(«Error opening order for size «,size,» : «,description);
return -1;
>

if(sl>0 || tp>0)
<
//bool res=OrderModify(lastTicketNumber,OrderOpenPrice(),NormalizeDouble(sl,Digits),NormalizeDouble(tp,Digits),0,White);
bool res=OrderModify(lastTicketNumber,NormalizeDouble(openPrice,Digits),NormalizeDouble(sl,Digits),NormalizeDouble(tp,Digits),0,White);

if(!res)
<
lastErrorMessage=»#»+IntegerToString(GetLastError())+» can not modify order»;
lastDateErrorMessage=TimeCurrent();
Print(«Error #»,GetLastError(),» Cmd:»,cmd,» Order :»,OrderType(),» Price:»,OrderOpenPrice(),» SL:»,NormalizeDouble(sl,Digits),» TP:»,NormalizeDouble(tp,Digits));
Print(«Error initial price: «,NormalizeDouble(openPrice,Digits));
>
>

return lastTicketNumber;
>
else
<
error_code=GetLastError();
switch(error_code)
<
case ERR_TRADE_NOT_ALLOWED :
lastErrorMessage=»#»+IntegerToString(error_code)+» Trade is not allowed»;
break; //4109 Trade is not allowed.
case ERR_INVALID_STOPS:
lastErrorMessage=»#»+IntegerToString(error_code)+» Invalid stop»;
break; //130 invalid stop
default:
lastErrorMessage=»#»+IntegerToString(error_code)+» Error opening order»;
>
lastDateErrorMessage=TimeCurrent();
>
return 0;
>

FreezeLevel Limitation (Freezing Distance).

Market orders can not be closed if the StopLoss and TakeProfit values violate the FreezLevel parameter requirements.
StopLoss or TakeProfit orders can not be modified if StopLoss or TakeProfit values violate the StopLevel parameter requirements.
Pending orders can not be deleted or modified if the declared open price violates the FreezeLevel parameter requirements.

Источник

OrderModify sometimes returning ERROR 130

Please read some other posts before posting . . .

Please edit your post or your thread will be removed . . . please use the SRC button to post code: How to use the SRC button.

1. Play video

   Please edit your post. For large amounts of code, attach it.

2. The == operand. — MQL4 forum

I cant use the operator != do this ?

I should use it?

I cant use the operator != do this ?

I should use it?

The code now is:

For me is the same problem yet.

You are modifying your order when it hits 100 Points profit

You are not checking to see if it has already been modified

Next tick, if profit remains at more than 100 Points, the program will try to modify the order again with the same values.

This will return the error.

You are modifying your order when it hits 100 Points profit

You are not checking to see if it has already been modified

Next tick, if profit remains at more than 100 Points, the program will try to modify the order again with the same values.

This will return the error.

The check below ensure that the order already been modified. And the error 130 is not about it, if you the in the table ERROR this error say: Stops are too close, or prices are ill-calculated or unnormalized . .

The check below ensure that the order already been modified. And the error 130 is not about it, if you the in the table ERROR this error say: Stops are too close, or prices are ill-calculated or unnormalized . .

The check below ensure that the order already been modified. And the error 130 is not about it, if you the in the table ERROR this error say: Stops are too close, or prices are ill-calculated or unnormalized . .

Sorry about that.

To be honest, with a name like checkDoubles(), I thought that it was some kind of checking normalise double function, so I didn’t look too closely at it.

Especially as you wrote in your post «I changed the code removing the NormalizeDouble in the ‘if’ operators and put the function checkDoubles, but the error 130 continue happening.»

Источник

Другие публикации рубрики «FAQ по MQL и Metatrader»:

• Вопрос №9 «Как заставить работать советник при выключенном компьютере?»
• Вопрос №8 «Как рассчитать размер лота в зависимости от размера стоплосса?»
• Можно ли настроить нестандартный тайм-фрейм в MT4? — Вопрос №7
• Вопрос №6 «Как уменьшить размер папки с терминалом MT4?»
• Вопрос №4 — «Выключение компьютера из MQL»
• Вопрос №3
• Вопрос №2
• Вопрос №1

What is MT4 error 130?

The MT4 error 130 is an OrderSend error code of the MetaTrader 4 platform. A trading platform shows this error code when an Expert Advisor fails to execute an order according to expectations. This error is also known as invalid stops.

An OrderSend error can be very crucial for the day traders because their timing of market entry and exits are equally important. Also, such errors may damage your profit factors and heavily affect your risk to reward ratio.

In this article, we will discuss when an MT4 error 130 happens and how to fix this issue ensuring a smoother trading experience.

Why does MT4 error 130 happen?

An MT4 error 130 may occur for the following reasons:

Market orders

While opening a buy or sell order if you set the stop-loss and take profit levels closer to the market price, the MT4 platform will not accept the order. Instead, it will show your the error code 130.

For direct buy orders, if your stop-loss limit is greater than the asking price and the take profit level is lower than the bidding price, the MT4 will still show the OrderSend error code. On the other hand, for market sell orders, an error code 130 appears when the stop-loss level is lower than the bidding price and the take-profit level is higher than the asking price.

Pending orders

An error code130 may also appear during placing a buy limit and buy stop order. It happens when the difference between the asking and the entry price or the difference between the entry and take profit price is less than the stop-loss limit.

For sell limit and sell stop orders, the OrderSend error occurs if the difference between the bidding and entry price or the difference between the entry and take profit price is less than the stop-loss level.

How to fix Invalid Stops errors

By popular demand, proven strategies on how to beat every algorithmic trader’s worst nightmare – Error 130

The OrderSend Error 130 appears in MetaTrader 4 when an Expert Advisor can’t execute a marker order as expected. Also known as the Invalid Stop (ERR_INVALID_STOPS) in MQL jargon, the Error 130 happens when the TakeProfit and StopLoss levels are set to close to the current market price.

Where does this error come from? What does it mean for your Expert Advisor? How can you find the part of your code that is causing the error? We tackle all this and more…

Video Tutorial

Alright! Let’s go ahead and send some orders with OrderSend. The video below is available if you prefer watching instead of reading

To start off, a formal definition from our friend, MQL4 Documentation:

That’s right! That is all you get from MetaQuotes. And the rest… Go figure!

Ordersend Error 130 is briefly mentioned in other sections of the documentation. However, there is no thorough guide to what “Invalid Stops” actually means and how to deal with this, perhaps, most common problem in Forex programming.

But not a worry! That’s why I have written this article. Let’s get through this together!

The silent killer

So… you launched your expert advisor and… nothing happens. No BUY orders, no SELL orders, no pending orders, not even error messages in the logs…. Just silence. You decide to wait a few hours / days / weeks, and nothing really changes – the charts go up and down, but you don’t see any profit. This can go on forever…

The real reason is simple – you’re actually getting ERR_INVALID_STOPS (which is the correct technical term for the issue), but you can’t see it. That’s because 130 is a silent killer. A cold-blooded murderer of your brain and inner calm 🙂

There is no way to pick up this error through expert advisor logs or even terminal logs. The only way to catch it is by adding the right failsafe mechanisms into your code. Here’s an example you can adapt to your code:
int ticket;
ticket = OrderSend("EURUSD", OP_BUY, 1.0, Ask, 10, StopLossLevel, TakeProfitLevel, "My 1st Order!");

if(ticket < 0)
{
Alert(“OrderSend Error: “, GetLastError());
}
else
{
Alert(“Order Sent Successfully, Ticket # is: ” + string(ticket));
}
What we are doing here is taking the ticket number and that OrderSend() returns and checking if it is less than zero. If yes, then that is a signal from MetaTrader 4 telling us that there was a problem with the request.

The error code is then printed out onto the screen using Alert() and the built-in GetLastError() function. This code will give a pop-up window like in the image up at the top of this article.

Note: you can use Print() instead of Alert() to redirect the message straight to the EA’s log instead of displaying it on the screen.

Core of Ordersend Error 130

Invalid stops is the real name for the culprit we are dealing with today. So what does invalid stops in MetaTrader 4 actually mean?

• For a market order (BUY or SELL) invalid stops means that the StopLoss and/or TakeProfit you requested were not possible to set for your order. Therefore, since a request cannot be fulfilled only partially, the order was not executed at all
• For a pending order (BUY STOP, BUY LIMIT, SELL STOP, or SELL LIMIT) invalid stops means that either (1) there were issues with the SL/TP (same as above) OR (2) the issue was with the entry price which you specified for the order itself

As we can see, the issue is always with one (or many) of the prices that your Forex Robot specified in its request to the trade server. Now that we know our enemy – let’s beat it!

1) StopLoss & TakeProfit are prices

There are several possible causes of ERR_INVALID_STOPS, and one of the more frequent ones among beginners is specifying the StopLoss and TakeProfit in pips rather than actual price levels. Like this:
OrderSend(EURUSD, OP_BUY, 0.1, 1.1606, 10, 20, 40);
This person tried to set a StopLoss of 20 pips and a TakeProfit of 40 pips. Big NO-NO….. The correct and only way of specifying your SL and TP is through price levels:
OrderSend(EURUSD, OP_BUY, 0.1, 1.1606, 10, 1.1585, 1.1645);
By the way, here we assumed that the current ASK price is 1.1606 and current BID price is 1.1605 (i.e. 1 pip spread).

2) 4-digits vs 5-digits

Another reason you could be getting ERR_INVALID_STOPS is if you are setting the input parameters of your EA in Pips (4-digit points) when the Robot is anticipating 5-digit points. Let’s look at an example:
extern int StopLoss = 20;
extern int TakeProfit = 40;

//…

OrderSend(EURUSD, OP_BUY, 0.1, Ask, 10, Bid-StopLoss*Point(), Bid+TakeProfit*Point());

This code will work fine on a 4-digit broker, however will fail on a 5-digit broker. The reason is that on a 4-digit broker, Point() equals to 0.0001, whereas on a 5-digit broker Point() equals to 0.00001.

Basically, with no additional adjustments, on a 5-digit broker the EA will be attempting to set the StopLoss and TakeProfit at only 2 and 4 pips away from the Bid price respectively!

That’s why in the case of a 5-digit broker you have to increase your StopLoss and TakeProfit parameters tenfold. Like this:
extern int StopLoss = 200;
extern int TakeProfit = 400;

//…

OrderSend(EURUSD, OP_BUY, 0.1, Ask, 10, Bid-StopLoss*Point(), Bid+TakeProfit*Point());
However, be careful! Some EA’s already have modules that will detect the number of digits after the decimal and will automatically adjust your input parameters for you. In these situations multiplying inputs by 10 can actually lead to erroneous performance.

Note: I plan on posting a separate article where we will discuss how to create our own modules to detect the number of digits after the decimal

3) ECN brokers

ECN accounts have their own specifics. One of them is – when trading through a ECN broker you will not be able to set a StopLoss and/or TakeProfit with your Market Order (BUY or SELL). If you try to do this – you will get Error 130.

However, of course, you do need to set a StopLoss (and maybe TakeProfit) for your order, and this must be done as soon as possible after the order has been executed. Try this code:
int MarketOrderSend(string symbol, int cmd, double volume, double price, int slippage, double stoploss, double takeprofit, string comment, int magic)
{
int ticket;

ticket = OrderSend(symbol, cmd, volume, price, slippage, 0, 0, NULL, magic);
if(ticket <= 0) Alert(“OrderSend Error: “, GetLastError());
else
{
bool res = OrderModify(ticket, 0, stoploss, takeprofit, 0);
if(!res) { Alert(“OrderModify Error: “, GetLastError());
Alert(“IMPORTANT: ORDER #”, ticket, ” HAS NO STOPLOSS AND TAKEPROFIT”);}
}
return(ticket);
}
You can add this function to your code (at the very end) and then use it instead of OrderSend() in your main code. This function adds an extra step in the process of sending a Market Order.

First, it send the request to execute a market order stripping out the StopLoss and TakeProfit. Next, it modifies the newly opened market order by adding the desired SL and TP.

There is, of course, a risk that the order will be executed, but the modification will fail. However, in that case the function will promptly notify the trader that the StopLoss and TakeProfit have not been set.

Feel free to modify this function to suit your needs and trading style.

4) Stop-Levels

Stop-Levels are a mechanism for brokers to protect themselves from certain volatility and liquidity related risks. In simple terms, you will not be able to set your StopLoss or TakeProfit OR any pending order closer than a predetermined number of Pips to the current market price.

To find out what the Stop Level is for a specific currency pair you need to press CTRL+U on your keyboard, select the desired currency pair and click the “Properties” button as shown on the illustration below:

In this example the Stop Level for AUDUSD is 3 Pips. This means that you will not be able to set the StopLoss for your order closer than 3 Pips to the price at which the order will be opened.

This also means that any pending order will have to be set at least 3 Pips away from the current market price.

If you Robot tries to break these rules and set a StopLoss / TakeProfit or Pending Order within the Stop Level range, then it will get Error 130 “Invalid Stops”. So just be mindful of the Stop Level of the currency where your EA’s are trading – don’t specify excessively small StopLoss and TakeProfit parameters.

It is also worth noting that more exotic currency pairs can have much more significant Stop Levels. Fore example, for AUDNZD the Stop Level with the same broker as in the above example is 20 Pips. For GBPSEK (British Pound vs Swedish Krone) – it’s 100 Pips.

5) Normalization of doubles

With some brokers you will find that for an unknown reason the Ask and Bid prices are passed onto the trader with additional negligible digits after the decimal. For example:

Instead of 1.1606 the broker would give you 1.160600001

Now this phenomenon has no effect on manual trading, moreover since the MT4 terminal is hardwired to display a certain number of digits after the decimal point (either 4 or 5) – you will not be able to notice any difference at all!

However, these ‘negligible’ digits after the decimal can have a dramatic effect on Expert Advisors causing……… that’s right! Our old friend, OrderSend Error 130!

Here’s a strategy that I personally use to protect my Robots from this issue:
void OnTick()
{
//...
OrderSend(EURUSD, OP_BUY, 0.1, ND(Ask), 10, ND(Bid-StopLoss*Point()), ND(Bid+TakeProfit*Point()));

}

double ND(double val)
{
return(NormalizeDouble(val, Digits));
}
This neat little trick allows you to normalize (in simple terms – Round) any prices that you are inputting into the OrderSend() function. This way you cut off all ‘negligible’ digits after the decimal point.

Conclusion

Today we saw that there may be multiple (at least 5) causes to error 130. Though this is quite a few, the underlying issues are all trivial and can be corrected in a matter of minutes.

Therefore, Error 130 should not be feared! If you have encountered this culprit, it’s just a matter of going through the list above, finding the situation that applies to you and applying the prescribed solution.

Hope you found this article useful!

Let me know if you have any questions by using the comments section below.

Happy trading,

Kirill

P.S: if you liked what you read in this article, here you can find the full course: