Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
I'm not sure when NT uses local pc time and when it uses exchange time, but I do know that NT uses the local pc time for the trade list and chart markers. I asked NT support why they don't use the exchange time for it and they just don't.
Can you help answer these questions from other members on NexusFi?
Oops, I think I misread the code, now that I went and looked at it more closely to post here.
I was referring to Bars.MarketData.Connection.Options.Provider and Bars.MarketData.Connection.Now, I thought in my head that .Now was referring to DateTime.Now, but upon a second look of the code, I am not sure and I really have no time to test it.
If your data is lagging, then Bar-Timer and data in T&S will not line up because BarTimer knows that the bar is supposed to have ended but the T&S data coming in still hasn't got there yet.
In any case, I have the Symmetricom time window just beneath my T&S window and I can see when there is a lag. Most of the time there isn't (remember that in most setups there is a 500 ms lag in the T&S window unless you go into Ninja Options and make it less than that).
I now trade instruments that I know that 98% of the time there is no lag (volume issues via dialup).
You also might want to do regular ping tests on your machine to check latency. Some broadband providers - most of whom packet data including your lovely unpacketed Zenfire data - have much worse latency than others, up to 3-400 ms, i.e. almost half a second each way. So your PC time might be right, but your latency slow. Running the clock helps zero in on that as well.
On latency: I was surprised to find out that my rural neighbour's new wireless highspeed which I should get fairly soon has a latency of only 65 ms, which is very fast and I was accessing my own website based in the US for the test, not the relay station up the road.
Thanks for the info on the clock...I always figured there was a way to change how often it updates, but never knew how. Now I will not have to manually update every morning.
Basically, the way "NTV V3" clients, like the Windows Time Service, work, is by regularly querying the time on a Time Server, updating the computer time, and waiting for next resync.
This is not a very good solution because
1. each time measure is not very precise
2. anyway the clock drifts between two measurements.
The solution is to install an NTP V4 Daemon. This system corrects both flaws : it uses multiple time sources to increase the precision of the time measurement, and it continually adjusts the local time clock using a PLL. It evaluates the hardware clock drift and keeps correcting it.
Notes :
1.For vista it's simpler to use c:\tools than "c:\program files" because modifying files in program files is a pain.
2. Simplest way is to choose Local System account in setup screen
3. Don't forget to disable windows time service because both programs need the 123 udp port.
Then you can modify the config file and add some stratus 2 servers (connecting to stratus 1 is considered "not cool", stratus 1 servers are those connected to precise time sources)
I use Dimension 4 mentioned in the first post of this thread, and it works flawlessly for me. On Win 7, it needs to run as admin though. Best way to do, is to start it as a scheduled task that starts on login with highest privileges. Once you do that, your clock is continually synced all day.
I like the idea of a NTP V4 Daemon though, thanks for posting.