API Support wrote:
M1 cannot be aligned with each tick. M1 bar's timestamp depends on timeframe rather than tick's timestamp value.
Again, this is not the issue I described. I'm not sure whether you read the original post. What I'm saying is that M1 data timestamps are shifted by
ONE HOUR against corresponding tick data (or S1 data).
Here's an example with M1 and S1:
M1:
Quote:
03.10.2016 00:00:00.000,1.05231,1.05231,1.05202,1.05205,162.99
03.10.2016 00:01:00.000,1.05205,1.05211,1.05192,1.05207,73.62
S1:
Quote:
02.10.2016 23:00:00.000,1.05231,1.05231,1.05214,1.05218,12.870000000000003
02.10.2016 23:00:01.000,1.05226,1.05226,1.05222,1.05225,4
02.10.2016 23:00:02.000,1.05227,1.05227,1.05222,1.05224,5.999999999999999
...
02.10.2016 23:00:59.000,1.05205,1.05205,1.05205,1.05205,1
02.10.2016 23:01:00.000,1.05205,1.05205,1.05205,1.05205,1
02.10.2016 23:01:01.000,1.05206,1.05206,1.05203,1.05203,2