Support Board
Date/Time: Tue, 28 Jul 2026 05:47:11 +0000
Post From: US Midwest NTP Introducing Data Delay
| [2026-06-11 05:15:38] |
| Sierra_Chart Engineering - Posts: 24317 |
|
We do not see any obvious problems. If using the US Midwest server, which is in Michigan, make sure this is the NTP configuration: NTP Client Enable: Yes NTP Client working Status: NTP processing thread running "NTP Servers" NTP Servers: "ntp_usmw.sierrachart.com:11497 (Sierra Chart US Midwest)" Individual Server Polling Interval (Seconds): 30 Number of Responses to Wait for to Update Time: 1 Minimum Number of Responses to Wait for to Update Time: 1 Time Delay After Last Received Response to Update Time if Insufficient Responses (Seconds): 5 Threshold Level in Milliseconds for Increasing/Decreasing Polling Interval: 5 Number of Clock Adjustments to Determine Automatic Adjustment: 5 "Read only values" Last Offset Value: 1.534224 millisec at 2026-06-11 01:14:37 Peers Info: Peer:ntp_usmw.sierrachart.com, Stratum:2, TimeSource:, ReferenceTime: 00:00:00.000000, OriginTime:2026-06-11 05:14:36.151999, ReceiveTime:2026-06-11 05:14:36.154018, TransmitTime:2026-06-11 05:14:36.154050, DestinationTime:2026-06-11 05:14:36.152999, RequestInterval:30s, CalculatedRoundTripDelay:0.0009684562683105469, CalculatedSystemClockOffset:0.0015342235565185547 "Advanced" Has Privilege to set System time: Yes Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |