![MQL5 - Language of trade strategies built-in the MetaTrader 5 client terminal](https://c.mql5.com/i/registerlandings/logo-2.png)
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
Difference of run with the same Expert Advisor in MT175 and MT176 from 1.1.2004 to CurTime()
Number of open orders in MT175 = 2902; in MT176 = 20
Unclear multiple (>10000) errors in logs in MT176 (none in MT175)
like
10:06:19 2004.01.13 09:56 exp4: Error opening order : 2 ; common error tip_signal= 3,* signal= -1, kol_zdelok=5
10:06:19 2004.01.13 13:38 exp4: Error opening order : 2 ; common error tip_signal= 3,* signal= -1, kol_zdelok=6
10:06:19 2004.01.13 14:35 exp4: Error opening order : 2 ; common error tip_signal= 3,* signal= -1, kol_zdelok=7
10:06:19 2004.01.13 15:29 exp4: Error opening order : 2 ; common error tip_signal= 3,* signal= -1, kol_zdelok=8
10:06:19 2004.01.13 17:05 exp4: Error opening order : 2 ; common error tip_signal= 3,* signal= -1, kol_zdelok=9
10:06:19 2004.01.13 21:50 exp4: Error opening order : 2 ; common error tip_signal= 3,* signal= -1, kol_zdelok=10
10:06:19 2004.01.14 09:01 Tester: take profit #4 at 1.2708 (1.2706 / 1.2710)
10:06:19 2004.01.14 09:05 Tester: take profit #3 at 1.2698 (1.2693 / 1.2697)
10:06:19 2004.01.14 09:06 Tester: take profit #3 at 1.2698 (1.2688 / 1.2692)
10:06:19 2004.01.14 09:07 Tester: take profit #3 at 1.2698 (1.2687 / 1.2691)
10:06:19 2004.01.14 09:08 Tester: take profit #3 at 1.2698 (1.2693 / 1.2697)
10:06:19 2004.01.14 09:09 Tester: take profit #3 at 1.2698 (1.2693 / 1.2697)
10:06:19 2004.01.14 09:10 Tester: take profit #3 at 1.2698 (1.2693 / 1.2697)
10:06:19 2004.01.14 09:11 Tester: take profit #3 at 1.2698 (1.2689 / 1.2693)
10:06:19 2004.01.14 09:12 Tester: take profit #3 at 1.2698 (1.2689 / 1.2693)
10:06:19 2004.01.14 09:13 Tester: take profit #3 at 1.2698 (1.2686 / 1.2690)
10:06:19 2004.01.14 09:14 Tester: take profit #3 at 1.2698 (1.2685 / 1.2689)
10:06:19 2004.01.14 09:15 Tester: take profit #3 at 1.2698 (1.2688 / 1.2692)
10:06:19 2004.01.14 09:16 Tester: take profit #3 at 1.2698 (1.2691 / 1.2695)
10:06:19 2004.01.14 09:17 Tester: take profit #3 at 1.2698 (1.2693 / 1.2697)
Conclusion: You have messed up something there in 176, we will have to use 175 for now.
Good luck.
OK. It works.
It is rather boring to prescribe an Expert Advisor to see what it outputs, to say the least.
Print function doesn't work only during optimization. It works during simple testing.
Can you clear the log?
When you run the Expert Advisor several times, so much rubbish accumulates there :(
I mean in the tester.
I mean in the tester.
have to think about it
Преписывать эксперт для просмотра что он там выводит несколько влом, если не сказать больше.
The Print function only fails during optimisation, but works during simple testing.
Yeah, it didn't seem to work to me though. Print() works in init(), but not in start()
For instance, out of 6-8 Print() only 1 works. The rest never get into the log during tests. Without optimization, of course.
Open the corresponding log file in the log file using the context menu and see if it was printed or not. The data are printed to the log tab asynchronously, on a timer so as not to slow down the tester, therefore you can lose data in the tab (and not in the log, i.e. not in the log itself).