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
total of 6 files (8 experts), date of change from 23:59 to 00:01 (Alpari time)
Nothing has changed while I was writing this post...
That's enough for now, we will deal with it tomorrow ;)
And now, your code pinned, started a new hour - in the log only a few errors, no position open...
2005.09.07 01:01:11 quark_test_expert: wrong delimiter for FileOpen as BIN function
2005.09.07 01:00:21 quark_test_expert: wrong delimiter for FileOpen as BIN function
2005.09.07 01:00:14 quark_test_expert: wrong delimiter for FileOpen as BIN function
2005.09.07 00:59:55 quark_test_expert: wrong delimiter for FileOpen as BIN function
2005.09.07 00:59:55 quark_test_expert: wrong delimiter for FileOpen as BIN function
These errors can be safely ignored. I asked the developers about them, they didn't answer.
Improved interaction between terminal and trade server;
I wonder if this is relevant to our topic?
So, it must not be able to output the information to a file? If the error is in the file opener...
I don't think we'll be able to... We need to sift the code as much as possible, so that we can ask later: "Is this line right?" =) then there's a better chance...
MetaTrader 4 Mobile, build 184
I don't think so....
These errors can be safely ignored. I asked the developers about them, they didn't answer.
So it can't output the information to a file, then? If file opener error...
No. The program sees the wrong (from its point of view) separator character in the file opening function. It doesn't affect the output in any way, since the character is for text mode, and I'm using binary mode. This is a glitch in the error-catching system.
I don't think so... We should sift the code as much as possible, so that later we can ask: "is this line right?" =) then there is a better chance...
I'm reporting bugs that are not caught by their control system, affect money handling, and potentially - create a conflict between client and broker. Sounds to me like they should be clawing at me.
Renat wrote (in this thread), let me see the log. I have given all the logs possible. I also posted the expert. What else can I do?
It costs me nothing in principle to create a workaround where the client makes 25 attempts instead of 5, with a timeout rather than without one. This is almost guaranteed to solve the problem. Or change the EA's logic, although that's a shame :) But there will be other clients who will not catch this error, which will then put them "on the money". And there will be nothing in their logs and they will go to their brokerage company to complain.
MetaTrader 4 Mobile, build 184
I think not.... [/quote]
I missed it :)
OrderClose returned true, position remained open. 3 times.
2005.09.07 14:35:10 XOINDATR USDCHF,M5: trade_lib&info_lib - _OrderClose( 934068, 0.1, 5, 65280 ) - Error on OrderClose(...). GetLastError() = 6, ErrorDescription = no connection with trade server, Running time: 241 sec.
2005.09.07 14:33:37 Alert: XOINDATR (GBPUSD, M5) - Close Sell!
Order #934150 closed OK
2005.09.07 14:32:26 Alert: XOINDATR (GBPUSD, M5) - Close Sell!
Order #934150 closed OK
2005.09.07 14:31:41 Alert: XOINDATR (GBPUSD, M5) - Close Sell!
Order #934150 closed OK
2005.09.07 13:56:44 Alert: XOINDATR (USDCAD, M5) - Close Buy!
Order #934351 closed OK
2005.09.07 13:56:44 XOINDATR USDCAD,M5: trade_lib&info_lib - _OrderClose( 934351, 0.1, 5, 65280 ) - Successful. Mission time: 2 sec.
2005.09.07 13:56:44 XOINDATR USDCAD,M5: close #934351 buy 0.10 USDCAD at 1.1897 at price 1.1879
2005.09.07 14:35:10 TradeContext: ping failed
2005.09.07 14:35:10 TradeContext: ping error
2005.09.07 14:31:09 '63310': close order #934068 buy 0.10 USDCHF at 1.2376 sl: 0.0000 tp: 0.0000 at price 1.2374
Needless to say, that no matter how reliable a tester is, optimizing an EA in it, that will always work in the tester, but in reality - once in a while, um... can't find the right word :) Well, gentlemen developers, here's a problem for you...
If only OrderSend and not OrderClose - still "not opened" is better than "not closed" =)