2018.11.15 10:27:45.583 Network '10169544': connection to MetaQuotes-Demo lost
forcibly disconnected from the Internet (router turned off)
After reconnecting to
2018.11.15 10:32:58.823 Network '10169544': authorized on MetaQuotes-Demo through Access Point EU 2 (ping: 50.64 ms)
code
CopyTime(_Symbol,PERIOD_M1,0,1,CM1_T)
has ceased to give the current open time of a bar on M1, and all the time gives the last time before the connection is broken.
2018.11.1510:08:20.159 Experts expert Test CopyTime (AUDUSD,Daily) loaded successfully
2018.11.1510:27:45.583 Network '10169544': connection to MetaQuotes-Demo lost
2018.11.1510:32:58.823 Network '10169544': authorized on MetaQuotes-Demo through Access Point EU 2 (ping: 50.64 ms)
2018.11.1510:32:58.823 Network '10169544': previous successful authorization performed from 178.165.123.77 on 2018.11.1510:03:382018.11.1510:32:58.900 Network '10169544': terminal synchronized with MetaQuotes Software Corp.
2018.11.1510:32:58.900 Network '10169544': trading has been enabled - hedging mode
2018.11.1510:33:00.653 Network '10169544': scanning network for access points
2018.11.1510:33:19.062 Network '10169544': scanning network finished
2018.11.1510:33:19.062 Network '10169544': auto connecting to a better access point with 95 % quality (previous: 88 %)
2018.11.1510:33:19.062 Network '10169544': connection to MetaQuotes-Demo lost
2018.11.1510:33:19.716 Network '10169544': authorized on MetaQuotes-Demo through Access Point EU 4 (ping: 65.57 ms)
2018.11.1510:33:19.716 Network '10169544': previous successful authorization performed from 178.165.123.77 on 2018.11.1510:32:582018.11.1510:33:19.825 Network '10169544': terminal synchronized with MetaQuotes Software Corp.
2018.11.1510:33:19.825 Network '10169544': trading has been enabled - hedging mode
Try to put it on M30, and get data from M30 as well. That's exactly how it freezes, which is shown in the video. Switching the timeframe doesn't help, only removing the indicator and then installing it.
Try putting it on M30, and getting data from M30 as well. That's exactly how I'm getting the freeze, which is shown in the video. Switching the timeframe does not help, only removing the indicator and then installing it.
I confirm that playing with the reloading of the indicator is not 100% helpful, so to say that for every 3 times I manage to reload the indicator completely and of course not to guess by coffee grounds, it's easier to unload the indicator and reload it on the tool.
But it's a hell of a thing, what kind of trading automation can we talk about in this kind of dancing with tambourines.
You know, at work, I have to write a lot to technical support of different companies (Symantec, DeviceLock, Kaspersky, FortiNet, Xspider, etc.), but never before I had to find the cause of the problem described by me, mda .... There remains only to write myself a fix :)
I had a similar problem about six months ago. I was writing an arbitrage robot, so I was working with a large list of characters at the same time. I was writing an arbitrage robot, so I was working with a big list of symbols at the same time. The robot was protected from working with outdated quotes, so the problem was only a decrease in activity. The only thing that helped was re-attaching the EA to the chart.
The freezing of alien invisible timeframe update after reconnect has been dealt with and fixed. The reason was wrong cache statuses after the reconnect.
Beta version 1946 is available via Help -> Check Desktop Updates -> Latest Beta Version.
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
I did catch iTime hanging up on PERIOD_M1.
My system:
Runs normally, no Portable.
On AUDUSD, M5 I ran "Test CopyTime.mq5" at 10:08:20
Expert Advisor code
Then in
forcibly disconnected from the Internet (router turned off)
After reconnecting to
code
has ceased to give the current open time of a bar on M1, and all the time gives the last time before the connection is broken.
Maybe it's a static array
And need to use a dynamic array?
Added: replaced CM1_T[1] with a dynamic CM1_T[]. After forcibly breaking the connection for about three minutes, the string
Outputs the last known time with M1 before breaking the link.
I did catch iTime hanging up on PERIOD_M1.
My system:
Runs normally, no Portable.
On AUDUSD, M5 I ran "Test CopyTime.mq5" at 10:08:20
Expert Advisor code
Then in
forcibly disconnected from the Internet (router turned off)
After reconnecting to
code
has ceased to give the current open time of a bar on M1, and all the time gives the last time before the connection is broken.
Maybe it's a static array
and need to use a dynamic array?
Try to put it on M30, and get data from M30 as well. That's exactly how it freezes, which is shown in the video. Switching the timeframe doesn't help, only removing the indicator and then installing it.
Try putting it on M30, and getting data from M30 as well. That's exactly how I'm getting the freeze, which is shown in the video. Switching the timeframe does not help, only removing the indicator and then installing it.
I confirm that playing with the reloading of the indicator is not 100% helpful, so to say that for every 3 times I manage to reload the indicator completely and of course not to guess by coffee grounds, it's easier to unload the indicator and reload it on the tool.
But it's a hell of a thing, what kind of trading automation can we talk about in this kind of dancing with tambourines.
*** Maybe it's the static array
I have dynamic arrays, as it's originally written that it's better to use them at SoruXXX, the problem is not the type of array.
... but unfortunately, the MQ product, has been my focus for about 10 years.
in another 10 years everything will be working properly )))))))))))))))))))))
We will reproduce and correct.
How soon can we expect a correction?
How soon can we expect a fix?
The freezing of alien invisible timeframe update after reconnect has been dealt with and fixed. The reason was wrong cache statuses after the reconnect.
Beta version 1946 is available via Help -> Check Desktop Updates -> Latest Beta Version.