Support Board
Date/Time: Thu, 08 Jan 2026 17:38:04 +0000
EUREX DOM freezes every ~5 seconds (1–2s lag) despite low chart draw time
View Count: 155
| [2026-01-05 14:48:41] |
| User197029 - Posts: 58 |
|
Hello, I am experiencing repeated short freezes on the EUREX feed, specifically affecting the DOM on the FESX. Description of the issue: The DOM freezes for roughly 1–2 seconds every ~5 seconds Between freezes, everything works normally This happens consistently and is very noticeable during active markets What I have already checked: Switched between the standalone DOM and Chart Trading DOM → same behavior Chart drawing time is stable, typically 13 ms to 27 ms No other performance issues visible Only one instance of Sierra Chart running Only one chartbook open Chartbook contains 23 charts including the DOM Environment: Single SC instance No other chartbooks No heavy studies being added or removed during the freezes Given the regular timing and the fact that chart drawing times stay low, this does not look like a local performance bottleneck. It feels more like a short data pause or feed-related lag. Could you please check if there is any issue or instability with the EUREX data feed at the moment, or advise what additional diagnostics I should run to help pinpoint the cause? Thank you. Date Time Of Last Edit: 2026-01-05 14:51:20
|
| [2026-01-05 18:15:45] |
| John - SC Support - Posts: 43858 |
|
Do you have a standard chart open as well? Does the lag show in the bars? Or is this just a Market Depth update issue?
For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2026-01-05 18:39:58] |
| User197029 - Posts: 58 |
|
I’ll check this again tomorrow morning. The market is too quiet right now to properly assess it. The lag is also visible on my Number Bars charts, not just Market Depth. When it happens, the entire bid/offer seems to freeze for 1-2secs and then resumes live again. Thanks for looking into this. |
| [2026-01-05 19:49:26] |
| John - SC Support - Posts: 43858 |
|
Do you see the price updating properly, or does it freeze as well? When this occurs can you interact with the system? Can you select a Menu item and it will open immediately, or does everything need to "wait" for that second or two? Also, please get us your Message Log after you have this occur by following these instructions: Support Board Posting Information: How to Post Your Message Log (Required In Some Cases) For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2026-01-06 08:16:17] |
| User197029 - Posts: 58 |
|
Price freezes as well when this occurs. The system itself remains fully responsive. I can interact normally, select menu items, and they open immediately without delay. There is no general UI freeze. The issue is isolated to market data updates. It affects: DOM Charts, including standard charts and Number Bars charts When it happens, the bid and offer stop updating entirely and then resume live again after a few seconds. This occurs simultaneously on all EUREX instruments I am running. For example, both DAX futures and FESX futures freeze at the same time, then continue together. Because this happens very frequently, every few seconds, I am not sure how clearly it will show up in the Message Log, but I have included relevant excerpts below as requested. 2026-01-06 09:13:12.204 | NTP Client | Sending packet to 0.pool.ntp.org:123 2026-01-06 09:13:12.205 | NTP Client | Sending packet to 1.pool.ntp.org:123 2026-01-06 09:13:12.205 | NTP Client | Sending packet to 2.pool.ntp.org:123 2026-01-06 09:13:12.205 | NTP Client | Sending packet to 3.pool.ntp.org:123 2026-01-06 09:13:12.233 | NTP Client | Received Packet | RoundTripDelay=0.026962757110595703, SystemClockOffset=0.3318474292755127 2026-01-06 09:13:12.238 | NTP Client | Received Packet | RoundTripDelay=0.03387880325317383, SystemClockOffset=0.33129334449768066 2026-01-06 09:13:12.244 | NTP Client | Received Packet | RoundTripDelay=0.03995943069458008, SystemClockOffset=0.3336946964263916 2026-01-06 09:13:12.252 | NTP Client | Received Packet | RoundTripDelay=0.046967506408691406, SystemClockOffset=0.33438825607299805 2026-01-06 09:13:13.203 | NTP Client | Set System Time failed: Windows error code 1314: A required privilege is not held by the client. 2026-01-06 09:13:52.360 | Chat | Message response. Chat ID: 136. Request ID: 1195378580 2026-01-06 09:14:12.200 | NTP Client | Sending packet to 0.pool.ntp.org:123 2026-01-06 09:14:12.200 | NTP Client | Sending packet to 1.pool.ntp.org:123 2026-01-06 09:14:12.200 | NTP Client | Sending packet to 2.pool.ntp.org:123 2026-01-06 09:14:12.200 | NTP Client | Sending packet to 3.pool.ntp.org:123 2026-01-06 09:14:12.230 | NTP Client | Received Packet | RoundTripDelay=0.029980182647705078, SystemClockOffset=0.33449816703796387 2026-01-06 09:14:12.235 | NTP Client | Received Packet | RoundTripDelay=0.03496980667114258, SystemClockOffset=0.33463454246520996 2026-01-06 09:14:12.241 | NTP Client | Received Packet | RoundTripDelay=0.04095888137817383, SystemClockOffset=0.33420586585998535 2026-01-06 09:14:12.246 | NTP Client | Received Packet | RoundTripDelay=0.04593944549560547, SystemClockOffset=0.3338813781738281 2026-01-06 09:14:13.200 | NTP Client | Set System Time failed: Windows error code 1314: A required privilege is not held by the client. |
| [2026-01-06 15:29:49] |
| John - SC Support - Posts: 43858 |
|
The items you show from your log are related to the Network Time Protocol and have nothing to do with issues with the data. Refer to the following regarding the NTP issues you are getting: Network Time Protocol Client: Operating System Privileges for Setting Time We need to see your entire Message Log by following these instructions: Support Board Posting Information: How to Post Your Message Log (Required In Some Cases) For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2026-01-06 19:01:27] |
| User197029 - Posts: 58 |
|
Ok as the entire message log is extremely long I have clicked Send For Analysis according to the instructions here Support Board Posting Information: How to Post Your Message Log (Required In Some Cases)
Date Time Of Last Edit: 2026-01-06 19:05:40
|
| [2026-01-06 19:42:57] |
| Sierra_Chart Engineering - Posts: 22227 |
|
When you notice this problem we want you to reconnect to the data feed with File >> Reconnect and see if that resolves the problem. Data for EUREX is distributed from two different locations in Germany with different ISPs and we want to see if it makes a difference reconnecting.
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 Date Time Of Last Edit: 2026-01-06 19:43:27
|
| [2026-01-06 21:34:33] |
| John - SC Support - Posts: 43858 |
|
There are a number of issues in your log. The following is the breakdown in chronological order of how they show up in the log: 2026-01-06 09:21:19.399 | Symbol Error | EUR-202109-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request
2026-01-06 09:21:20.289 | Symbol Error | NZD-202109-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request 2026-01-06 09:21:20.293 | Symbol Error | ES-202109-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:20.293 | Symbol Error | CAD-202109-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:20.293 | Symbol Error | JPY-202109-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:20.335 | Symbol Error | GF-202109-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request 2026-01-06 09:21:20.335 | Symbol Error | GF-202109-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request 2026-01-06 09:21:20.399 | Symbol Error | CHF-202109-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:20.431 | Symbol Error | AUD-202109-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request 2026-01-06 09:21:20.431 | Symbol Error | GBP-202109-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request 2026-01-06 09:21:20.431 | Symbol Error | AUD-202109-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request 2026-01-06 09:21:20.486 | Symbol Error | GBP-202109-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request 2026-01-06 09:21:20.529 | Symbol Error | LE-202112-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:20.686 | Symbol Error | GBP-202112-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:21.293 | Symbol Error | CHF-202112-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:21.295 | Symbol Error | EUR-202112-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:21.295 | Symbol Error | CAD-202112-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:21.296 | Symbol Error | JPY-202112-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:21.296 | Symbol Error | AUD-202112-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:21.391 | Symbol Error | NZD-202112-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:21.475 | Symbol Error | LE-202202-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:21.583 | Symbol Error | CAD-202203-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:21.685 | Symbol Error | GBP-202203-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:27.240 | Symbol Error | LE-202204-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request 2026-01-06 09:21:27.240 | Symbol Error | AUD-202203-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request 2026-01-06 09:21:27.240 | Symbol Error | LE-202204-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request 2026-01-06 09:21:27.240 | Symbol Error | AUD-202203-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request 2026-01-06 09:21:27.240 | Symbol Error | HE-202206-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:27.240 | Symbol Error | GBP-202206-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:27.240 | Symbol Error | NZD-202206-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:27.240 | Symbol Error | CHF-202206-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:27.240 | Symbol Error | EUR-202206-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:27.240 | Symbol Error | JPY-202206-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:27.240 | Symbol Error | LE-202210-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:27.241 | Symbol Error | LE-202206-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:27.241 | Symbol Error | NZD-202209-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:27.241 | Symbol Error | AUD-202209-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:27.241 | Symbol Error | HE-202210-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:27.241 | Symbol Error | LE-202302-GLOBEX is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:27.241 | Symbol Error | F.US.MCLEM23 is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:27.241 | Symbol Error | F.US.SR3U23 is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 2026-01-06 09:21:27.244 | Symbol Error | F.US.SR3Z24 is unknown, unavailable, or improperly formatted. No security definition has been found for the request | Number times message added: 1 These are improper symbols. There are no symbols in Sierra Chart that have the word "GLOBEX" at the end. You need to change these symbols to what they should be (most likely "-CME"). F.US.SR3U23 and F.US.SR3Z24 is a CQG symbol, but you are connected to Interactive Brokers. 2026-01-06 09:21:23.767 | Error loading: C:\SierraChart TEST FESX ONLY\Data\sst_volume_profile.dll. File not found or may be missing SCDLLName line.
There is a problem with this DLL file and it can not be loaded. You need to talk to the developer and get it corrected. 2026-01-06 09:21:24.083 | sst_volume_dots.dll is not 64-bit
2026-01-06 09:21:24.156 | sst_volume_dots_2151.dll is not 64-bit 2026-01-06 09:21:26.099 | TicinoMathV3.0.dll is not 64-bit 2026-01-06 09:21:26.236 | TicinoMathV3.0_2151.dll is not 64-bit You are not using the 64-bit version of these studies and you need to be since you are on a 64-bit system. You would need to get the updated versions from the developer, or remove them from your system. 2026-01-06 09:21:29.035 | Circular chart reference detected. Charts: 5, 2. Chartbook: FESX 13-05-24.Cht.
2026-01-06 09:21:36.548 | Circular chart reference detected. Charts: 2, 5. Chartbook: FESX 13-05-24.Cht. 2026-01-06 09:21:37.420 | Circular chart reference detected. Charts: 5, 2. Chartbook: FESX 13-05-24.Cht. This is quite likely what is causing you the issue. Refer to the following: High CPU Usage | Inactive User Interface | Poor Performance | Long Time to Load Chart Data | Charts Reloading Often: 30.9 References to Other Charts / Continuous Full Recalculation of Charts There are also numerous mentions of charts recalculating due to being tagged, which means that there is a reference to another chart (most likely a Study/Price Overlay). These could also create Circular References that the software did not find. So you would need to look through your charts. 2026-01-06 09:21:37.593 | Chart: HG-202605-COMEX[M] 240 Min #12 | Study: ASK Circles | You are not allowed to use this study. Contact frederik@simplesystemtrading.com to discuss authorization
2026-01-06 09:21:37.593 | Chart: HG-202605-COMEX[M] 240 Min #12 | Study: BID Circles | You are not allowed to use this study. Contact frederik@simplesystemtrading.com to discuss authorization As it states, you are not authorized to use this study, so you should not have it on any charts. 2026-01-06 09:30:25.167 | Message from IB: Market data farm connection is inactive but should be available upon demand.usfuture.il. IB Error Code: 2108. Request ID: -1. | Number times message added: 1 2026-01-06 09:30:25.167 | Message from IB: Market data farm connection is inactive but should be available upon demand.usfuture.nj. IB Error Code: 2108. Request ID: -1. | Number times message added: 1 This indicates some kind of issue with the connection to Interactive Brokers. This could also be a reason for the system not updating, as when it loses connection to the trading service, the data stops as well. We do not have any insight as why there is an issue or what exactly these errors indicate. You would need to discuss with Interactive Brokers. 2026-01-06 13:43:30.997 | Message from IB: Market data farm connection is broken:usfuture.il. IB Error Code: 2103. Request ID: -1. 2026-01-06 13:43:30.997 | Message from IB: Market data farm connection is broken:usfuture.nj. IB Error Code: 2103. Request ID: -1. 2026-01-06 13:43:30.997 | Message from IB: Market data farm connection is OK:eufarm. IB Error Code: 2104. Request ID: -1. 2026-01-06 13:43:30.997 | Message from IB: Market data farm connection is OK:cashfarm. IB Error Code: 2104. Request ID: -1. 2026-01-06 13:43:30.997 | Message from IB: Market data farm connection is OK:usfarm. IB Error Code: 2104. Request ID: -1. 2026-01-06 13:43:30.997 | Message from IB: HMDS data farm connection is OK:euhmds. IB Error Code: 2106. Request ID: -1. 2026-01-06 13:43:30.997 | Message from IB: HMDS data farm connection is OK:ushmds. IB Error Code: 2106. Request ID: -1. 2026-01-06 13:43:30.997 | Message from IB: Sec-def data farm connection is OK:secdefeu. IB Error Code: 2158. Request ID: -1. 2026-01-06 13:43:31.030 | Message from IB: Market data farm connection is OK:usfuture.nj. IB Error Code: 2104. Request ID: -1. Another set of messages from IB indicating some issue with connectivity. From here there was a reconnection to the data feed and the issues repeat. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2026-01-07 12:49:01] |
| User197029 - Posts: 58 |
|
Thank you John, and thanks as well for dissecting the log and clearly pointing out the different issues. I have now addressed all of them: Removed the invalid and legacy symbols Cleaned up the DLL related issues Resolved the circular chart reference problem Reduced cross chart references significantly I am now starting to monitor the systems and will update if there are still issues. Regarding the remaining messages about charts being recalculated due to being tagged: from what I can see, these recalculations only occur during chartbook loading and initial startup. After that point, there are no further tagging or recalculation messages in the log during the trading session. Based on your experience, is this expected behavior and safe to ignore once the chartbook is fully loaded? Or is it possible for charts to continue recalculating in the background without producing corresponding log messages? I just want to make sure there is no remaining hidden performance impact during live trading now that the circular references have been removed. Thanks again for the help. |
| [2026-01-07 16:17:07] |
| John - SC Support - Posts: 43858 |
|
You will only see those messages in the log on the initial load, or when a full recalculation occurs. There is no issue with having those messages in general. It just means that a chart needs to get data from another chart. As we mentioned, this most likely is the "Study/Price Overlay" and generally is not a problem. But, when we see a lot of them, then we worry that there may be other circular references that are being created but the system is not specifically seeing those. This can occur. So it's just something to keep in mind and keep an eye out for. Also, if you do have a lot of charts depending on other charts, then you may want to consider setting the following to "Yes": General Settings Window: Use Controlled Order Chart Updating (Global Settings >> General Settings >> Charts >> Charts) Note the caveats in the information for that setting, so use it carefully and only if you really feel that the way you have your charts setup would benefit from this. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2026-01-08 15:40:22] |
| User197029 - Posts: 58 |
|
Thank you John, I appreciate the clarification and the continued guidance. As a next step, I have taken things further and opened a completely separate Sierra Chart instance dedicated only to execution. This instance now contains just two DOMs, one for DAX and one for FESX, and no regular charts at all. At this point there are no remaining charts that could create cross-chart references. In this DOM-only instance I have: Removed all invalid and legacy symbols Cleaned up and eliminated all DLL related issues Eliminated all cross-chart references (there are only the two DOM charts) Disabled chart drawings, study collections, and chart linking Reduced market depth levels and internal depth calculation scope Minimized historical data loading and trade statistics Disabled anything not strictly required for DOM execution I have attached the current message log for reference. From what I can see, it is now clean. Despite this very minimal setup, I am unfortunately still seeing a small but noticeable lag on the DOM. It mainly occurs when offers are lifted or bids are hit. Occasionally it takes a second or two, sometimes slightly longer, for those hits and lifts to visually update. I am confident this reflects a data delay rather than just rendering, as I am running a NinjaTrader SuperDOM alongside Sierra Chart on the same machine and can observe the difference in responsiveness during aggressive buying or selling. I am not complaining and understand there are multiple factors involved, including the data feed and trading service. At this point I am simply trying to confirm whether there is anything else on the Sierra Chart side that could still be checked or adjusted, or whether this behavior is within what would be expected given such a minimal, isolated setup. Thanks again for the continued help and for taking the time to review this. LOG: 2026-01-08 16:37:33.115 | Software version: 2813 64-bit 2026-01-08 16:37:33.115 | Primary Thread ID: 161688 2026-01-08 16:37:33.115 | Usage end date: 2026-06-25 2026-01-08 16:37:33.115 | Enabled for: Advanced Features 2. 2026-01-08 16:37:33.115 | Enabled for: Sierra Chart Historical Data Service. 2026-01-08 16:37:33.115 | Enabled for: Denali Real-Time Exchange Data Feed. 2026-01-08 16:37:33.115 | Enabled for: Delayed Denali Exchange Data Feed. 2026-01-08 16:37:33.115 | Enabled for exchange2: CME (Trading Account Required) 2026-01-08 16:37:33.115 | Enabled for exchange2: CBOT (Trading Account Required) 2026-01-08 16:37:33.115 | Enabled for exchange2: COMEX (Trading Account Required) 2026-01-08 16:37:33.115 | Enabled for exchange2: NYMEX (Trading Account Required) 2026-01-08 16:37:33.115 | Enabled for exchange2: EUREX EOBI 2026-01-08 16:37:33.115 | Allow Support for Sierra Chart Data Feeds is enabled. 2026-01-08 16:37:33.115 | Current selected Data/Trading service: Interactive Brokers 2026-01-08 16:37:33.115 | Custom symbol settings values: enabled 2026-01-08 16:37:33.115 | Chart Update Interval: 100 2026-01-08 16:37:33.115 | Intraday Data Storage Time Unit: 0 2026-01-08 16:37:33.115 | Time Zone: +01:00:00 (CET+01CEST+01,M3.5.0/02:00,M10.5.0/03:00) 2026-01-08 16:37:33.115 | 2026-01-08 15:37:33 Local computer time in UTC 2026-01-08 16:37:33.115 | 2026-01-08 16:37:33 Local computer time in SC Time Zone 2026-01-08 16:37:33.115 | 2026-01-08 13:42:22 Server time in UTC 2026-01-08 16:37:33.115 | Local computer UTC time and Server UTC time difference: 0 seconds. 2026-01-08 16:37:33.115 | Program path: C:\SierraChart DOM only\ 2026-01-08 16:37:33.115 | Data Files path: C:\SierraChart DOM only\Data\ 2026-01-08 16:37:33.116 | OS Version Number: 10.0 2026-01-08 16:37:33.116 | Locale Setting: C 2026-01-08 16:37:33.116 | Crash reporter started: true 2026-01-08 16:37:33.116 | | Number times message added: 1 2026-01-08 16:37:35.454 | Interactive Brokers | Connecting to 127.0.0.1:7496 2026-01-08 16:37:35.454 | IB TWS socket (2) | Creating socket. 2026-01-08 16:37:35.455 | IB TWS socket (2) | New receive buffer size: 0 2026-01-08 16:37:35.455 | IB TWS socket (2) | Connecting to IP: 127.0.0.1. 2026-01-08 16:37:35.959 | Interactive Brokers | Sending API sign: API 2026-01-08 16:37:35.959 | Interactive Brokers | Sending client version: v100..176 +PACEAPI. Waiting for acceptance. 2026-01-08 16:37:35.977 | Interactive Brokers | TWS server version: 176 2026-01-08 16:37:35.977 | Interactive Brokers | TWS time: 20260108 16:37:35 Central European Standard Time 2026-01-08 16:37:36.227 | Interactive Brokers | Connected. Sending Start API command. 2026-01-08 16:37:36.227 | Interactive Brokers | Waiting for account information. 2026-01-08 16:37:36.232 | Interactive Brokers | Next valid order ID: 1 2026-01-08 16:37:36.232 | IB Account information received. 2026-01-08 16:37:36.232 | Interactive Brokers | Received 1 Trade Accounts from TWS. 2026-01-08 16:37:36.232 | Interactive Brokers | Connected to Live account. 2026-01-08 16:37:36.232 | Interactive Brokers | Trade Account: U2498. Index: 0 2026-01-08 16:37:36.232 | Updated verified funded futures trading account ending date to: 2026-02-07 15:37:36 2026-01-08 16:37:36.232 | Interactive Brokers | Connection to server complete. 2026-01-08 16:37:36.233 | No download requests in the queue to start downloads for. | Number times message added: 3 2026-01-08 16:37:36.233 | Updated verified funded futures trading account ending date to: 2026-02-07 15:37:36 2026-01-08 16:37:36.235 | Message from IB: Market data farm connection is OK:usfuture.nj. IB Error Code: 2104. Request ID: -1. 2026-01-08 16:37:36.235 | Message from IB: Market data farm connection is OK:usfuture. IB Error Code: 2104. Request ID: -1. 2026-01-08 16:37:36.235 | Message from IB: Market data farm connection is OK:eufarm. IB Error Code: 2104. Request ID: -1. 2026-01-08 16:37:36.235 | Message from IB: Market data farm connection is OK:cashfarm. IB Error Code: 2104. Request ID: -1. 2026-01-08 16:37:36.235 | Message from IB: Market data farm connection is OK:eufarmnj. IB Error Code: 2104. Request ID: -1. 2026-01-08 16:37:36.235 | Message from IB: Market data farm connection is OK:usfarm. IB Error Code: 2104. Request ID: -1. 2026-01-08 16:37:36.235 | Message from IB: HMDS data farm connection is OK:euhmds. IB Error Code: 2106. Request ID: -1. 2026-01-08 16:37:36.235 | Message from IB: HMDS data farm connection is OK:ushmds. IB Error Code: 2106. Request ID: -1. 2026-01-08 16:37:36.235 | Message from IB: Sec-def data farm connection is OK:secdefeu. IB Error Code: 2158. Request ID: -1. 2026-01-08 16:37:36.236 | Interactive Brokers | Next valid order ID: 1 | Number times message added: 1 2026-01-08 16:37:36.329 | Mapping DAX-202603-EUREX-EUR-25 to FDAX202603_FUT_EUREX. Service code: eurex 2026-01-08 16:37:36.329 | Using symbol data fast lookup vector 2026-01-08 16:37:36.330 | Denali Data Feed | Starting real-time market data updates for: DAX-202603-EUREX-EUR-25 (FDAX202603_FUT_EUREX). ID: 1 Service code: eurex 2026-01-08 16:37:36.330 | Denali Data Feed | Connecting to the server ds50.sierracharts.com. Port 10048 2026-01-08 16:37:36.330 | Denali Data Feed | Requesting security definition data for: DAX-202603-EUREX-EUR-25 (FDAX202603_FUT_EUREX). ID: 1 2026-01-08 16:37:36.330 | Added historical Intraday data request for DAX-202603-EUREX-EUR-25 to the queue. 2026-01-08 16:37:36.330 | Intraday data recording state for symbol DAX-202603-EUREX-EUR-25 is set to download 'Pending'. 2026-01-08 16:37:36.330 | DTC Client socket (3) | Creating socket. 2026-01-08 16:37:36.330 | Triggering next historical data download in queue. 2026-01-08 16:37:36.330 | DTC Client socket (3) | New receive buffer size: 0 2026-01-08 16:37:36.330 | DTC Client socket (3) | Connecting to IP: 62.209.53.225. 2026-01-08 16:37:36.355 | Delaying start of download for DAX-202603-EUREX-EUR-25. 2026-01-08 16:37:36.356 | Mapping ESTX50-202603-EUREX-EUR-10 to FESX202603_FUT_EUREX. Service code: eurex 2026-01-08 16:37:36.356 | Denali Data Feed | Starting real-time market data updates for: ESTX50-202603-EUREX-EUR-10 (FESX202603_FUT_EUREX). ID: 2 Service code: eurex 2026-01-08 16:37:36.356 | Denali Data Feed | Requesting security definition data for: ESTX50-202603-EUREX-EUR-10 (FESX202603_FUT_EUREX). ID: 2 2026-01-08 16:37:36.357 | Added historical Intraday data request for ESTX50-202603-EUREX-EUR-10 to the queue. 2026-01-08 16:37:36.357 | Intraday data recording state for symbol ESTX50-202603-EUREX-EUR-10 is set to download 'Pending'. 2026-01-08 16:37:36.357 | Triggering next historical data download in queue. 2026-01-08 16:37:36.372 | Denali Data Feed | Network connection to server complete. 2026-01-08 16:37:36.372 | Denali Data Feed | Starting socket receive thread. 2026-01-08 16:37:36.373 | Denali Data Feed | Sending encoding request to server: Binary VLS. Compression: standard 2026-01-08 16:37:36.431 | Denali Data Feed | Setting DTC encoding to Binary VLS 2026-01-08 16:37:36.431 | Denali Data Feed | Sending logon request message. 2026-01-08 16:37:36.474 | Interactive Brokers | Requesting Trade Positions updates. 2026-01-08 16:37:36.476 | Interactive Brokers | Received Trade Positions download end message 2026-01-08 16:37:36.476 | Interactive Brokers | Begin Trade Positions processing. 2026-01-08 16:37:36.476 | Interactive Brokers | Received Trade Positions. Performing final processing. 2026-01-08 16:37:37.033 | Denali Data Feed | Received logon response. 2026-01-08 16:37:37.033 | Denali Data Feed | Server Name: SC Realtime Server. 2026-01-08 16:37:37.033 | Denali Data Feed | Server protocol version: 8. Client protocol version: 8 2026-01-08 16:37:37.033 | Denali Data Feed | Successfully connected. 2026-01-08 16:37:37.033 | Denali Data Feed | Trading is not supported. 2026-01-08 16:37:37.033 | Denali Data Feed | MarketDepthIsSupported: 1 2026-01-08 16:37:37.033 | Denali Data Feed | Restarting real-time data updates for symbol: DAX-202603-EUREX-EUR-25 -> FDAX202603_FUT_EUREX 2026-01-08 16:37:37.033 | Denali Data Feed | Restarting real-time data updates for symbol: ESTX50-202603-EUREX-EUR-10 -> FESX202603_FUT_EUREX 2026-01-08 16:37:37.092 | Enabling compression for file: C:\SierraChart DOM only\Data\MarketDepthData\ESTX50-202603-EUREX-EUR-10.2026-01-08.depth 2026-01-08 16:37:37.186 | Opened cached Depth file: C:\SierraChart DOM only\Data\MarketDepthData\ESTX50-202603-EUREX-EUR-10.2026-01-08.depth 2026-01-08 16:37:37.227 | Denali Data Feed | Setting external service identifier for symbol DAX-202603-EUREX-EUR-25 to 9160456 2026-01-08 16:37:37.227 | Denali Data Feed | Received security definition for symbol DAX-202603-EUREX-EUR-25 2026-01-08 16:37:37.228 | Denali Data Feed | Setting external service identifier for symbol ESTX50-202603-EUREX-EUR-10 to 9160922 2026-01-08 16:37:37.228 | Denali Data Feed | Received security definition for symbol ESTX50-202603-EUREX-EUR-10 2026-01-08 16:37:41.224 | Requesting market depth updates for: DAX-202603-EUREX-EUR-25 if supported. NumLevels=100 2026-01-08 16:37:41.224 | Requesting market depth updates for: ESTX50-202603-EUREX-EUR-10 if supported. NumLevels=100 2026-01-08 16:37:41.291 | Denali Data Feed | Clearing market depth for DAX-202603-EUREX-EUR-25 2026-01-08 16:37:41.292 | Denali Data Feed | Clearing market depth for ESTX50-202603-EUREX-EUR-10 2026-01-08 16:37:42.194 | HD Request # 7 | Downloading Intraday chart data for DAX-202603-EUREX-EUR-25 to the file DAX-202603-EUREX-EUR-25.scid. Service: eurex 2026-01-08 16:37:42.195 | HD Request # 7 | Download start date-time: 2026-01-08 16:37:22.000000. File last date-time: 2026-01-08 16:37:22.972001 2026-01-08 16:37:42.196 | HD Request # 7 | Using server: ds14.sierracharts.com port 10150 2026-01-08 16:37:42.196 | Socket (4) | Creating socket. 2026-01-08 16:37:42.197 | Socket (4) | New receive buffer size: 0 2026-01-08 16:37:42.197 | Socket (4) | Connecting to IP: 176.9.9.252. 2026-01-08 16:37:42.278 | HD Request # 7 | Setting DTC encoding to Binary VLS 2026-01-08 16:37:42.278 | HD Request # 7 | Sending historical data logon request message. 2026-01-08 16:37:42.823 | HD Request # 7 | Requesting Intraday data. Start date-time: 2026-01-08 16:37:22. Record interval: 0. Symbol: FDAX202603_FUT_EUREX 2026-01-08 16:37:42.861 | HD Request # 7 | Decompressing data. 2026-01-08 16:37:42.901 | HD Request # 7 | Receiving Intraday data for DAX-202603-EUREX-EUR-25 starting at 2026-01-08 16:37:22.972000 2026-01-08 16:37:42.901 | Socket (4) | CloseSocket call. 2026-01-08 16:37:42.901 | Socket (4) | Shutdown started. Waiting for graceful close. 2026-01-08 16:37:42.903 | Historical data download thread signaled to stop. 2026-01-08 16:37:42.903 | HD Request # 7 | Timestamp of first Intraday data file record written: 2026-01-08 16:37:32.563000. 2026-01-08 16:37:42.903 | HD Request # 7 | Received 4 Intraday data records from 2026-01-08 16:37:22.972000 to 2026-01-08 16:37:40.616000 (17.6 seconds. Delay: 2.3 seconds) and wrote 2 records for DAX-202603-EUREX-EUR-25 2026-01-08 16:37:42.903 | HD Request # 7 | Completion time: 0s. 2026-01-08 16:37:42.903 | HD Request # 7 | Intraday data download complete for DAX-202603-EUREX-EUR-25. Unique request ID: 7 2026-01-08 16:37:42.903 | Removing historical data download ID 7. 2026-01-08 16:37:42.903 | Real-time Intraday chart data file updates started for DAX-202603-EUREX-EUR-25 2026-01-08 16:37:42.903 | Intraday chart data file opened for DAX-202603-EUREX-EUR-25 2026-01-08 16:37:42.903 | HD Request # 7 | Enabling Intraday chart updating for symbol. 2026-01-08 16:37:42.903 | 2026-01-08 16:37:42.903 | Triggering next historical data download in queue. 2026-01-08 16:37:42.904 | HD Request # 8 | Downloading Intraday chart data for ESTX50-202603-EUREX-EUR-10 to the file ESTX50-202603-EUREX-EUR-10.scid. Service: eurex 2026-01-08 16:37:42.905 | HD Request # 8 | Download start date-time: 2026-01-08 16:37:22.000000. File last date-time: 2026-01-08 16:37:22.302000 2026-01-08 16:37:42.905 | HD Request # 8 | Using server: ds50.sierracharts.com port 10149 2026-01-08 16:37:42.905 | Socket (5) | Creating socket. 2026-01-08 16:37:42.905 | Socket (5) | New receive buffer size: 0 2026-01-08 16:37:42.905 | Socket (5) | Connecting to IP: 62.209.53.225. 2026-01-08 16:37:42.939 | Socket (4) | Socket gracefully closed by remote side. 2026-01-08 16:37:42.939 | Socket (4) | Closed. 2026-01-08 16:37:42.984 | HD Request # 8 | Setting DTC encoding to Binary VLS 2026-01-08 16:37:42.984 | HD Request # 8 | Sending historical data logon request message. 2026-01-08 16:37:43.456 | HD Request # 8 | Requesting Intraday data. Start date-time: 2026-01-08 16:37:22. Record interval: 0. Symbol: FESX202603_FUT_EUREX 2026-01-08 16:37:43.499 | HD Request # 8 | Decompressing data. 2026-01-08 16:37:43.533 | HD Request # 8 | Receiving Intraday data for ESTX50-202603-EUREX-EUR-10 starting at 2026-01-08 16:37:22.302000 2026-01-08 16:37:43.534 | Socket (5) | CloseSocket call. 2026-01-08 16:37:43.534 | Socket (5) | Shutdown started. Waiting for graceful close. 2026-01-08 16:37:43.537 | Historical data download thread signaled to stop. 2026-01-08 16:37:43.537 | HD Request # 8 | Timestamp of first Intraday data file record written: 2026-01-08 16:37:30.930000. 2026-01-08 16:37:43.537 | HD Request # 8 | Received 39 Intraday data records from 2026-01-08 16:37:22.302000 to 2026-01-08 16:37:40.446000 (18.1 seconds. Delay: 3.1 seconds) and wrote 38 records for ESTX50-202603-EUREX-EUR-10 2026-01-08 16:37:43.537 | HD Request # 8 | Completion time: 1s. 2026-01-08 16:37:43.537 | HD Request # 8 | Intraday data download complete for ESTX50-202603-EUREX-EUR-10. Unique request ID: 8 2026-01-08 16:37:43.537 | Removing historical data download ID 8. 2026-01-08 16:37:43.537 | Real-time Intraday chart data file updates started for ESTX50-202603-EUREX-EUR-10 2026-01-08 16:37:43.537 | Intraday chart data file opened for ESTX50-202603-EUREX-EUR-10 2026-01-08 16:37:43.537 | HD Request # 8 | Enabling Intraday chart updating for symbol. 2026-01-08 16:37:43.537 | 2026-01-08 16:37:43.537 | No download requests in the queue to start downloads for. 2026-01-08 16:37:43.576 | Socket (5) | Socket gracefully closed by remote side. 2026-01-08 16:37:43.577 | Socket (5) | Closed. 2026-01-08 16:37:45.700 | Opened cached Intraday file: C:\SierraChart DOM only\Data\DAX-202603-EUREX-EUR-25.scid. Thread ID: 158848 2026-01-08 16:38:00.705 | Opened cached Intraday file: C:\SierraChart DOM only\Data\ESTX50-202603-EUREX-EUR-10.scid. Thread ID: 158848 |
| [2026-01-08 17:02:22] |
| John - SC Support - Posts: 43858 |
|
The log does not show any issues. Given that you are looking at another system in comparison, the one thing we think you may want to do is change your "Chart Update Interval" to a lower value in order to get the updates occurring faster, which we think may be all that you are really seeing. Refer to the following: Chart Settings: Chart Update Interval in Milliseconds (Chart >> Chart Settings >> Display >> Chart Update Interval menu) For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
To post a message in this thread, you need to log in with your Sierra Chart account: