How to create a watch in the terminal? - Trading stocks, futures, options and other exchange instruments

Dmitry Fedoseev 2017.02.01 06:46 #151

Sergey Chalyshev:

That's the thing, the trading server is not synchronised with the quote source.

On forex, trading is around the clock, there are no breaks in trading, the exact time may not be as critical.

On MICEX there are 3 trading intervals and it is necessary to guess if trading is permitted or not, in order not to run into errors. Everyone does it in his own way, because there is no way of knowing whether trading is allowed or not in the terminal.

You have to offer your own variant.

I would like to create a watch in the terminal. It would be in the form of an indicator updated using a timer that would not depend on ticks. The time is determined by TimeLocal() and it would work when there are no quotes but with corrections. Periodically a correction is made, as in this EA to measure delta.

Any questions from newcomers A programme to monitor Errors, bugs, questions

prostotrader 2017.02.01 07:08 #152

Sergey Chalyshev:

That's the thing, the trading server is not synchronised with the quote source.

On forex, trading is around the clock, there are no breaks in trading, the exact time may not be as critical.

On MICEX there are 3 trading intervals and it is necessary to guess if trading is permitted or not, in order not to run into errors. Everyone does it in his own way, because there is no way to find out in the terminal whether trading is allowed or not.

Suggest your variant.

Edit your code a bit

//+------------------------------------------------------------------+
//|                                            Delta Time Server.mq5 |
//+------------------------------------------------------------------+
struct _SYSTEMTIME
  {
   short             year;
   short             mon;
   short             day_of_week;
   short             day;
   short             hour;
   short             min;
   short             sec;
   short             msc;
  };

_SYSTEMTIME loc_time;

#import "kernel32.dll"
void GetLocalTime(_SYSTEMTIME &sys_time);
bool SetLocalTime(_SYSTEMTIME &sys_time);
#import
//---
MqlTick tick;
MqlDateTime sv_time;
int tick_msc,ping,time_server,time_local,delta=0,mdelta[10],n=0;
//+------------------------------------------------------------------+
//| Expert tick function                                             |
//+------------------------------------------------------------------+
void OnTick()
  {
   loc_time.year=0;
   GetLocalTime(loc_time);
   if(loc_time.year>0)
     {
      if(!SymbolInfoTick(_Symbol,tick)) { Print("error SymbolInfoTick: ",GetLastError()); return; }
      ping=TerminalInfoInteger(TERMINAL_PING_LAST)/1000;
      tick_msc=int(tick.time_msc%1000);
      TimeToStruct(tick.time,sv_time);

      time_server=(sv_time.sec+sv_time.min*60)*1000+tick_msc;
      time_local=(loc_time.sec+loc_time.min*60)*1000+loc_time.msc;

      delta=AvgDelta(time_server-time_local);
     datetime cur_time = TimeCurrent();
     Print(
           "ping : ",ping,
           " | time current: ", cur_time,
           " | time server: ",sv_time.hour,":",sv_time.min,":",sv_time.sec,",",tick_msc,
           " | time local: ",loc_time.hour,":",loc_time.min,":",loc_time.sec,",",loc_time.msc,
           " | delta ms: ",delta,
           " | min max delta: ",mdelta[ArrayMaximum(mdelta)]," : ",mdelta[ArrayMinimum(mdelta)],
           "");
     }
  }
//+------------------------------------------------------------------+
int AvgDelta(int d)
  {
   int avgd=0;
   mdelta[n]=d;
   n++; if(n>=10) n=0;
   for(int i=0;i<10;i++) avgd+=mdelta[i];
   return(avgd/10);
  }
//+------------------------------------------------------------------+

Sync by

2017.02.01 10:00:00.008 Net_switcher (URKA-3.17,H1) Local time sync is done. Symbol = Si-3.17 Sync hour = 10 Sync min = 0 Sync sec = 0 Sync ms = 8

Results of your Expert Advisor

PREDICT time period ASCTrend system Numerical series density

prostotrader 2017.02.01 07:16 #153

And a little more

Avalanche Strand 2D array problem PREDICT time period

Sergey Chalyshev 2017.02.01 07:29 #154

Dmitry Fedoseev:
Would make a clock in the terminal. In the form of indicator, updated by timer so as not to depend on ticks, the time is determined by TimeLocal(), so that it would work when there are no quotes, but with a correction. Periodically a correction is made, as in this EA to measure delta.

It is not quite clear how to take time accurate to milliseconds from the indicator. Does the indicator have to overwrite the buffer every millisecond?

Sergey Chalyshev 2017.02.01 07:31 #155

prostotrader:

And a little more

It's fine, it's just not clear why we need to synchronise the time after the trading session has started, we need to synchronise it before.

prostotrader 2017.02.01 07:35 #156

Sergey Chalyshev:
It's ok, but it's not clear why I need to synchronize time after trade session, I need it before.

I tried it, but only info (orders) can be taken before the start of sessions, but

using CopyTicks with INFO flag I get the same shit as I did withSymbolInfoTick

(I'll leave it like this, and then we'll see)

Added

And then 10-15 ms do not play royalty :)

On the market, anyway, you cannot buy at 10:00:00.000 (they will queue for a long time :( )

CopyTicks question What do you think Any questions from newcomers

prostotrader 2017.02.01 14:33 #157

After synchronisation at 14-05.

"Gone" in 3.5 hours, but not by much.

Added

I'll have another look before closing at 11pm

Added

If I don't fall asleep.

money managment Experts: Milestone Why my stop loss

prostotrader 2017.02.01 16:59 #158

Didn't have time to synchronise at 7:00 p.m.

Here's what's come up since 2 o'clock

Weekly performance BUG - Notifications: not A question for people

prostotrader 2017.02.01 19:44 #159

I'm off to bed now, it's from 2:05 p.m.

Trades not copied - Determine the future operability Why my stop loss

prostotrader 2017.02.03 07:03 #160

Here is a clear example of a local time mismatch:

2017.02.03 10:00:03.798 trader (Eu-3.17,M1)     StopTrading: Время сервера = 09:59:47; Статус ордера = SELL_ORDER; Билет = 0 OnTradeTransaction: Sell ордер не установлен! Причина:  Рынок закрыт
2017.02.03 10:00:03.798 trader (Eu-3.17,M1)     StopTrading: Удаление существующих ордеров по инструменту....
2017.02.03 10:00:03.798 trader (Eu-3.17,M1)     Эксперт остановлен. Инструмент Eu-3.17
2017.02.03 10:00:00.947 switcher (URKA-3.17,H1) Local time sync is done. Symbol = URKA-3.17 Sync hour = 10 Sync min = 0 Sync sec = 0 Sync ms = 947

Market closed Registration for the MetaQuotes-Demo EURUSD - Trends, Forecasts

Synchronise Windows local time with the MT5 server - page 16