Synchronise Windows local time with the MT5 server

prostotrader 2017.02.04 09:46 #161

Seryozh!

I don't like either my version (syncronisation on the first deal) or your version,

because it's "around the clock" and adjusts the time almostall the time,

whereas the time only needs to be adjusted before the start and at the end of sessions.

Need to think about making a hybrid of our versions.

Take a look and tell me what you think

//+------------------------------------------------------------------+
//|                                              Time_sync_forts.mq5 |
//|                   Copyright 2017 Sergey Chalyshev & prostotrader |
//|                                             https://www.mql5.com |
//+------------------------------------------------------------------+
#property copyright "Copyright 2017 Sergey Chalyshev & prostotrader"
#property link      "https://www.mql5.com"
#property version   "1.09"
//---
struct _SYSTEMTIME
  {
   short wYear;
   short wMonth;
   short wDayOfWeek;
   short wDay;
   short wHour;
   short wMinute;
   short wSecond;
   short wMilliseconds;
  };

_SYSTEMTIME loc_time;

#import "kernel32.dll"
//void GetLocalTime(_SYSTEMTIME &sys_time);
bool SetLocalTime(_SYSTEMTIME &sys_time);
#import
//
input ENUM_DAY_OF_WEEK FirstDay  = SATURDAY;        //Первый выходной
input ENUM_DAY_OF_WEEK SecondDay = SUNDAY;          //Второй выходной
//
MqlTick tick;
MqlDateTime sv_time, tts_time;
int st_st_mon   = 35100; //09-45
int end_st_mon  = 36000; //10-00
int st_end_mon  = 50280; //13-58
int end_end_mon = 50400; //14-00
int st_st_day   = 50460; //14-01
int end_st_day  = 50700; //14-05
int st_end_day  = 67380; //18-43
int end_end_day = 67500; //18-45
int st_st_evn   = 67560; //18-46
int end_st_evn  = 68400; //19-00
int st_end_evn  = 85680; //23-48
int end_end_evn = 85800; //23-50
//---
bool  is_sync;
//+------------------------------------------------------------------+
//| Expert initialization function                                   |
//+------------------------------------------------------------------+
int OnInit()
{
  is_sync = true;
  return(INIT_SUCCEEDED);
}
//+------------------------------------------------------------------+
//| Expert Convert To Time function                                  |
//+------------------------------------------------------------------+
bool ConvertToTime(const ulong n_value,_SYSTEMTIME  &a_time)
  {
   MqlDateTime cur_time={0};
   TimeToStruct(datetime(n_value/1000),cur_time);
   if(cur_time.year>0)
     {
      a_time.wDay=short(cur_time.day);
      a_time.wDayOfWeek=short(cur_time.day_of_week);
      a_time.wHour=short(cur_time.hour);
      a_time.wMinute= short(cur_time.min);
      a_time.wMonth = short(cur_time.mon);
      a_time.wSecond= short(cur_time.sec);
      a_time.wYear=short(cur_time.year);
      a_time.wMilliseconds=short(n_value%1000);
      return(true);
     }
   return(false);
  }
//+------------------------------------------------------------------+
//| Expert On Tick function                                          |
//+------------------------------------------------------------------+
void OnTick()
{
  tts_time.year = 0;
  TimeTradeServer(tts_time);
  if(tts_time.year > 0)
  {
    if((tts_time.day_of_week == int(FirstDay)) ||
       (tts_time.day_of_week == int(SecondDay))) return;
    int cur_time = tts_time.hour * 3600 + tts_time.min * 60 + tts_time.sec;
    if(((cur_time >= st_st_mon) && (cur_time < end_st_mon)) ||
       ((cur_time >= st_end_mon) && (cur_time < end_end_mon)) ||
       ((cur_time >= st_st_day) && (cur_time < end_st_day)) ||
       ((cur_time >= st_end_day) && (cur_time < end_end_day)) ||
       ((cur_time >= st_st_evn) && (cur_time < end_st_evn)) ||
       ((cur_time >= st_end_evn) && (cur_time < end_end_evn)))
    {
      if(!is_sync)
      {
        if(!SymbolInfoTick(Symbol(), tick))
        {
          Print("Error SymbolInfoTick", GetLastError());
          return;
        }
        sv_time.year = 0;
        TimeToStruct(tick.time, sv_time);
        if(sv_time.year>0)
        {
          ulong last_ping=ulong(NormalizeDouble(double(TerminalInfoInteger(TERMINAL_PING_LAST))/2000,0));
          ulong mls_time=ulong(tick.time_msc%1000);
          if((mls_time+last_ping)>999)
          {
            mls_time=tick.time_msc+last_ping;
            if(!ConvertToTime(mls_time, loc_time)) return;
          }
          else
          {
            loc_time.wYear = short(sv_time.year);
            loc_time.wMonth = short(sv_time.mon);
            loc_time.wDay = short(sv_time.day);
            loc_time.wDayOfWeek = short(sv_time.day_of_week);
            loc_time.wHour = short(sv_time.hour);
            loc_time.wMinute = short(sv_time.min);
            loc_time.wSecond = short(sv_time.sec);
            loc_time.wMilliseconds=short(mls_time+last_ping);
          }
          if(SetLocalTime(loc_time))
          {
            is_sync=true;
            Print("Local time sync is done. Symbol = ",Symbol()," Sync hour = ",loc_time.wHour, " Sync min = ",loc_time.wMinute,
                  " Sync sec = ",loc_time.wSecond," Sync ms = ",loc_time.wMilliseconds);
          }
        }
      }
    }
    else is_sync = false;
  }
}
//+------------------------------------------------------------------+

Added by

I also don't like that the ping rarely changes in the terminal

Market closed new mql4 providing millisecond Any rookie question, so

prostotrader 2017.02.06 07:34 #162

The first result of the new advisor

BrainSystem: Trading System Development Reversal Magic trading system PREDICT time period

prostotrader 2017.02.06 11:25 #163

Before the end of the morning session the time was synchronised, but at 14-01 -- 14-04 it was not :(

Apparently, this is due to the fact that the applications were only taken down.

But there is still synchronisation :)

BrainSystem: Trading System Development Reversal Magic trading system PREDICT time period

prostotrader 2017.02.06 13:38 #164

Decided on the following

int st_st_mon   = 35100; //09-45
int end_st_mon  = 36000; //10-00
int st_tr_mon   = 36060; //10-01
int end_tr_mon  = 36120; //10-02
int st_end_mon  = 50280; //13-58
int end_end_mon = 50400; //14-00
int st_st_day   = 50700; //14-05
int end_st_day  = 50760; //14-06
int st_end_day  = 67380; //18-43
int end_end_day = 67500; //18-45
int st_st_evn   = 68700; //19-05
int end_st_evn  = 68760; //19-06
int st_end_evn  = 85680; //23-48
int end_end_evn = 85800; //23-50

I think the topic is exhausted

Latest version here

https://www.mql5.com/ru/forum/167309#comment_4065302

Советники: Time sync FORTS

www.mql5.com

Форум алго-трейдеров MQL5

Registration for the MetaQuotes-Demo Great EA in backtest! Experts: Moving Average Trade

prostotrader 2017.02.06 16:19 #165

Developers now have the option of adding time to glasses "in small blood

From the Spectra 5.3 release

4. technological changes.

Separation of the trading and clearing component

Modernization of the core and risk module of the TCS, aimed at stabilizing the system.

Change in the implementation of the transaction flow limiter on the TCSSPECTRAcore

In version 5.3, the gateway transaction flow limiters from clients have been replaced by a single point. In previous versions, a per-gateway restrictor was used.

Fixing transaction logging times with nanosecond accuracy

A new moment_ns field has been added for the flow tables broadcasting transactions and requests.

URRRAAAAAAAAAAA!

Added

Spectra 5.3 will go live on the exchange on 27 february 2017.

Added

struct MqlBookInfo
  {
   ENUM_BOOK_TYPE   type;       // тип заявки из перечисления ENUM_BOOK_TYPE
   double           price;      // цена
   long             volume;     // объем
   ulong            moment_ns;  //ООООООООО-ЧЕНЬ ЖДЁМ
  };

List of changes in Which instruments to trade Any rookie question, so

[Deleted] 2017.02.06 18:08 #166

prostotrader:

Added

struct MqlBookInfo
  {
   ENUM_BOOK_TYPE   type;       // тип заявки из перечисления ENUM_BOOK_TYPE
   double           price;      // цена
   long             volume;     // объем
   ulong            moment_ns;  //ООООООООО-ЧЕНЬ ЖДЁМ
  };

And also for sentiment (as far as I understand the info on OI, warrants etc is called that). Millisecond would be enough there. And in general, the more accurate the better, but would like one accuracy for all possible information.

General question about signal FOREX - Trends, Forecasts A topic for traders.

prostotrader 2017.02.07 09:36 #167

Alexey Kozitsyn:
And it would also be for sentiment (as far as I understand the information on OI, warrants, etc. is called that). A millisecond will suffice there. And in general, the more precise the better, but I would like one precision for all possible information.

And will the ULONG non-seconds fit in?

Added

Need to see howthe moment_ns exchange announced

In 20 days it will already be live, but

documentation is not posted yet (as always) :(

Now let's be clear, CopyTicksRange () does not Indicators

[Deleted] 2017.02.07 09:56 #168

prostotrader:

And will the ULONG non-seconds fit in?

Added

Need to see howthe moment_ns exchange announced

In 20 days it will already be live, but

documentation is not posted yet (as always) :(

It will fit and there will still be some left over. But then again, if you take that kind of accuracy, you need to have that accuracy for all the information provided. It would, of course, be unrealistically cool, but at least let them add time in milliseconds everywhere.

The second sacred cow: Acceptance of SL/TP orders Any rookie question, so

prostotrader 2017.02.22 16:05 #169

Обращаем ваше внимание, что новый релиз Spectra 5.3 состоится 27 февраля 2017 г.,
вечерняя дополнительная торговая сессия на срочном рынке 24 февраля 2017 г.
(является торговым днем на срочном рынке) будет отменена.

Waiting for time in the glass from the developers....

How to Start with Forecast and levels for Press review

Synchronise Windows local time with the MT5 server - page 17