Troubled by the error there are no trading operations - page 8
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
The validator goes through the parameters. When the first combination is met with no trades, you unload the Expert Advisor. That's all. Further testing is useless.
The point is that you do not allow the validator to work with the Expert Advisor.
The tests are passed even if there are no trades on some of the symbols. The main thing is that if a trade operation cannot be performed, the Expert Advisor will issue a log entry about it and continue working.
You see, you are making a programme for people, not a validator. Why do you need a program in your market that does not handle errors, but simply deletes them from the chart? Would you buy such a miracle yourself?
Artem, this is a test EA (I'm checking the validation, and I'm not going to sell it), and it still won't make trades when the unloading condition works out. At the minimum lot, which is impossible to open a deal, it will just fill up the log file with prints. It won't do any more good.
I'll remove the unloading, but it won't change anything. See my previous posts with the results of testing the EA without unloading.
What's the point, Renat. Well, I did.
Here, I made this for the marketplace.
//+-------------- ФУНКЦИЯ ОБРАБОТКИ ОШИБОК ---------------------------------+
int Fun_Error(int Error)
{
switch(Error)
{
case 0: return (0);
case 1: Print("Trying to change already set values with the same values.");return(1);
case 2: Print("Common mistake. Stop all trading attempts until the circumstances are clarified.");return(0);
case 3: Print("Wrong parameters passed to the trading function.");return(1);
case 4: Print("The trading server is busy. Let's try again ..");Sleep(3000);return(1);
case 5: Print("Old version of the client terminal.");return(0);
case 6: Print("No connection to the trading server.");return(1);
case 7: Print("Not enough rights.");return(1);
case 8: Print("Too frequent requests.");return(1);
case 9: Print("Invalid operation disrupting server operation.");return(1);
case 64: Print("The account is blocked. It is necessary to stop all attempts at trading operations.");return(0);
case 65: Print("Invalid account number.");return(1);
case 128: Print("The transaction has expired.");return(1);
case 129: Print("Wrong bid or ask price, possibly not normalized price.");return(1);
case 130: Print("Stops that are too close or incorrectly calculated or abnormal prices in stops (or in the opening price of a pending order).");return(1);
case 131: Print("Wrong volume, error in granulation of volume.");return(1);
case 132: Print("The market is closed.");return(1);
case 133: Print("Trade is prohibited.");return(0);
case 134: Print("Not enough money to complete the operation.");return(0);
case 135: Print("The price has changed. We try again ..");RefreshRates();return(1);
case 136: Print("No price. We are waiting for a new tick ..");
while(RefreshRates()==false)// До нового тика
Sleep(1);
return(1);
case 137: Print("The broker is busy. Let's try again ..");Sleep(3000);return(1);
case 138: Print("The requested price is out of date, or bid and ask are confused.");return(1);
case 139: Print("The order is blocked and is already being processed.");return(1);
case 140: Print("Only purchase allowed. You cannot repeat the SELL operation.");return(1);
case 141: Print("Too many requests.");return(1);
case 142: Print("The order is queued.");return(1);
case 143: Print("The order has been accepted by the dealer for execution.");return(1);
case 144: Print("The order is canceled by the client upon manual confirmation of the transaction.");return(1);
case 145: Print("Modification is prohibited, because the order is too close to the market and is blocked due to possible early execution.");return(1);
case 146: Print("The trading subsystem is busy. Let's try again ..");Sleep(500);return(1);
case 147: Print("Using the expiration date of the order is prohibited by the broker.");return(1);
case 148: Print("The number of open and pending orders has reached the limit set by the broker.");return(1);
case 149: Print("An attempt to open an opposite position to an existing one if hedging is prohibited.");return(1);
case 4000: return (0);
case 4001: Print("Invalid function pointer.");return(1);
case 4002: Print("Array index is out of range.");return(1);
case 4003: Print("No memory for function stack.");return(1);
case 4004: Print("Stack overflow after recursive call.");return(1);
case 4005: Print("There is no memory on the stack for passing parameters.");return(1);
case 4006: Print("There is no memory for the string parameter.");return(1);
case 4007: Print("There is no memory for the time line.");return(1);
case 4008: Print("Uninitialized string.");return(1);
case 4009: Print("An uninitialized string in an array.");return(1);
case 4010: Print("There is no memory for the string array.");return(1);
case 4011: Print("Line is too long.");return(1);
case 4012: Print("The remainder of division by zero.");return(1);
case 4013: Print("Division by zero.");return(1);
case 4014: Print("Unknown team.");return(1);
case 4015: Print("Wrong transition.");return(1);
case 4016: Print("Uninitialized array.");return(1);
case 4017: Print("DLL calls are not allowed.");return(1);
case 4018: Print("Unable to load library.");return(1);
case 4019: Print("Unable to call function.");return(1);
case 4020: Print("Calls to external library functions are not allowed.");return(1);
case 4021: Print("There is not enough memory for the string returned from the function.");return(1);
case 4022: Print("The system is busy.");return(1);
case 4050: Print("Incorrect number of function parameters.");return(1);
case 4051: Print("Invalid function parameter value.");return(1);
case 4052: Print("Internal error of string function.");return(1);
case 4053: Print("Array error.");return(1);
case 4054: Print("Misuse of timeseries array.");return(1);
case 4055: Print("Custom indicator error.");return(1);
case 4056: Print("Arrays are incompatible.");return(1);
case 4057: Print("Error processing global variables.");return(1);
case 4058: Print("Global variable not detected.");return(1);
case 4059: Print("Function not allowed in test mode.");return(1);
case 4060: Print("Enter the HTTP address !!!.");return(1);
case 4061: Print("Error sending mail.");return(1);
case 4062: Print("A parameter of type string is expected.");return(1);
case 4063: Print("A parameter of type integer is expected.");return(1);
case 4064: Print("A parameter of type double is expected.");return(1);
case 4065: Print("An array is expected as a parameter.");return(1);
case 4066: Print("The requested historical data is in an update state.");return(1);
case 4067: Print("An error occurred while performing a trading operation.");return(1);
case 4099: Print("End of file.");return(1);
case 4100: Print("An error occurred while working with the file.");return(1);
case 4101: Print("Invalid file name.");return(1);
case 4102: Print("Too many open files.");return(1);
case 4103: Print("Unable to open file.");return(1);
case 4104: Print("Incompatible file access mode.");return(1);
case 4105: Print("No order has been selected.");return(1);
case 4106: Print("Unknown character.");return(1);
case 4107: Print("Incorrect price parameter for the trading function.");return(1);
case 4108: Print("Invalid ticket number.");return(1);
case 4109: Print("Trading is not permitted. You must enable the option Allow Expert Advisor to trade in the expert properties.");return(1);
case 4110: Print("Long positions are not allowed. It is necessary to check the properties of the expert.");return(1);
case 4111: Print("Short positions are not allowed. It is necessary to check the properties of the expert.");return(1);
case 4200: Print("The object already exists.");return(1);
case 4201: Print("An unknown property of the object was requested.");return(1);
case 4202: Print("The object does not exist.");return(1);
case 4203: Print("Unknown object type.");return(1);
case 4204: Print("No object name.");return(1);
case 4205: Print("Error coordinates of the object.");return(1);
case 4206: Print("The specified subwindow was not found.");return(1);
case 4207: Print("An error occurred while working with the object.");return(1);
return(0);
}
return(0);
}
I hook it up like this:
ticket=OrderSend(Symbol(),OP_SELL,Lot,BID,0,0,0,"",0,0,clrNONE);
if(ticket<0 && Fun_Error(GetLastError())==1){return;}
//---
ticket=OrderSend(Symbol(),OP_BUY,Lot,ASK,0,0,0,"",0,0,clrNONE);
if(ticket<0 && Fun_Error(GetLastError())==1){return;}
try it, it may throw up errors
Artyom, this is a test Expert Advisor, and it won't make trades when the unload condition works out anyway. At the minimum lot with which it is impossible to open the deal, it will simply fill up the log file with prints. The further work will be of no use.
I'll remove the unloading, but it won't change anything. Please refer to my previous posts with the results of testing an EA without Dumping.
Well can't you make a single entry for each of the erroneous trade requests?
yes, it works without errors
Here, for the marketplace.
//+-------------- ФУНКЦИЯ ОБРАБОТКИ ОШИБОК ---------------------------------+
This is not error handling. It's just printing out a description of the error code.
Processing is the execution of an algorithm when it receives an error. The algorithm should try to create conditions to correct the error and resend the request. If it is completely unable to do this, it should log the original parameters, try to correct them to so-and-so, and the final verdict that even with the parameters corrected, it is not possible to send the request.
Thank you, Renat. It's useful. I'll take it ))))
Don't...
This is not error handling. It is simply printing out a description of the error code.
Processing is the execution of an algorithm when it receives an error. The algorithm should attempt to create conditions to correct the error and send a second request. If it is completely unable to do this, log the original parameters, attempt to correct them to so-and-so, and the final verdict that even with corrected parameters, it is not possible to send the request.
10 years with this
no complaints
By the way, one of the first moderators did.
Vinin, remember him?