Site Administrator Swing Trader Data Scientist & DevOps
Manta, Ecuador
Experience: Advanced
Platform: My own custom solution
Trading: Emini Futures
Posts: 49,753 since Jun 2009
Thanks: 32,299 given,
97,501
received
Windows time service is only accurate to within a handful of seconds. This is by design, and there is no getting around it. It does not matter how close or accurate your source clock is, Windows time is not designed to be accurate within milliseconds.
If you want real accuracy, you need a true NTP service. I use Meinberg NTP personally, but there are many to choose from.
just in case for those that might not understand or might missunderstand @bigmike comment.... the windows client for keeping time is what he is referring to... hence the mention of an alternate NTP Client that would keep time better than ms windows built-in client... windows itself will track time to the milli and micro second with a valid NTP Client.
on windows computers with vista or higher you can configure to automatically synchronize your time once a day. you donīt have the need of additional programs.
go to date and time and then internettime - configure your nearest clock.
I've been digging into the synching of time via internet servers because I get trade markers on my chart that are way off the bar that the trade was executed on.
I've tried all the suggestions in this thread but am getting random results.
I've tried:
1. Dimension 4
2. Windows automatic updates
3. Manual syncing
The results are that some days its no problem and time is updated immediately and other days it just errors constantly. Some suggested it was a firewall issue so I pinged the server simultaneously while updating time. The ping went through but the time update produced an error.
What is interesting is Dimension 4 gives you a history of its synching operation. This picture shows that there are gaps in days where time updates do not work. Does anyone have any information on this? It just seems so strange.
that has a very cool factor..
