Support Board
Date/Time: Fri, 12 Jun 2026 13:09:52 +0000
More than 3 Denali Exchange Data Feed Connections on Same Computer Simultaneously
View Count: 421
| [2026-04-27 18:33:43] |
| User512353 - Posts: 144 |
|
As per documentation Denali Exchange Data Feed: Denali Exchange Data Feed Connections on Same Computer Simultaneously the number of simultaneous connections is limited to 3. Is there any way to set this limit to 4, e.g. by paying an additional fee? |
| [2026-04-27 20:42:14] |
| John - SC Support - Posts: 46649 |
|
There are no options to go beyond 3 on a single computer. The only option available would be to use another computer and pay a second set of exchange fees and then you can get an additional 3 installations on that second computer. Refer to the following: Denali Exchange Data Feed: Denali Exchange Data Feed on Two Computers Simultaneously One thing to keep in mind is that if you have multiple installations connecting to the same service, then you would be best served to use the option for "File >> New Instance", as these sub-instances do not count towards the connection limit. Refer to the following: File Menu: New Instance (File) For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2026-04-27 21:37:30] |
| User512353 - Posts: 144 |
|
I would only need 1 incoming Denali feed, plus 1 incoming IBKR data feed for NASDAQ indexes. But for trade I need 1 SC_Data sim 1 IBKR sim acct 1 IBKR live acct 1 other broker live acct IBKR sim and live are routed over separate IB Gateways, both running on that machine. This should all be on the same machine. Is there any other way to set this up? Date Time Of Last Edit: 2026-04-27 21:40:43
|
| [2026-04-28 14:29:34] |
| John - SC Support - Posts: 46649 |
|
The following statement has us a bit confused: I would only need 1 incoming Denali feed, plus 1 incoming IBKR data feed for NASDAQ indexes.
Of the 4 connections (separate installations of Sierra Chart), which ones will be using the Denali Exchnage Data Feed and which are not? You can have 3 of these connections getting data from our Denali Exchange Data Feed at the same time. You can setup one to not get data from our Denali Exchange Data Feed, and therefore it could get data from Interactive Brokers, or the other broker account (depending on what service you are using with that broker). For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2026-04-28 16:44:50] |
| User512353 - Posts: 144 |
|
All 4 are separate SC installations and they all use Denali, and due to the restriction I can only use 3 of them simultaneously. The "other broker" is Ironbeam via Teton. I did some experiments, and it may be feasible for my uses to use the Ironbeam data feed for some live data use cases, (but probably not for historical data). But I have some questions on that: With Teton/Ironbeam and Global Settings >> Data/Trade Service Settings >> Common Settings >> Allow Support for Sierra Charts Data Feeds = Yes the scid data is stored in files named e.g. ESM26_FUT_CME.scid With Global Settings >> Data/Trade Service Settings >> Common Settings >> Allow Support for Sierra Charts Data Feeds = No the scid data is stored in files named e.g. ESM26-CME.scid These files are not binary compatible. If combining them, you see old, copied data with prices as e.g. 715100.00, and in new downloaded data prices are e.g. 7151.00. Is there any logic behind that? Why this incompatibility? Most important question for me on this topic is currently: Can I configure SC so that the Main instance is using Global Settings >> Data/Trade Service Settings >> Common Settings >> Allow Support for Sierra Charts Data Feeds = Yes and a sub-instance is using Global Settings >> Data/Trade Service Settings >> Common Settings >> Allow Support for Sierra Charts Data Feeds = No so that Main and sub-instance would use binary incompatible data formats? Would that work? |
| [2026-04-28 18:10:57] |
| John - SC Support - Posts: 46649 |
|
Every service connection uses different underlying data types, therefore it is necessary to have separate files for each connection type. And as you saw, you can not combine these files. Sub-instances, started by selecting "File >> New Instance", do not count towards the limit of 3 installations on the same computer. These sub-instances are tied to the main instance and get their data and trade settings from that main instance. It does not do any good to try and set the option for "Allow Support for Sierra Chart Data Feeds" to "No" in a sub-instance. This just creates issues that are not necessary. As we have stated - you can only the Denali data to a total of 3 installations at the same time. If you have 4 on the same computer, then one will have to be setup to NOT get the data from our Denali Exchange Data feed. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2026-04-28 20:54:46] |
| User512353 - Posts: 144 |
|
What does this mean: It does not do any good to try and set the option for "Allow Support for Sierra Chart Data Feeds" to "No" in a sub-instance. This just creates issues that are not necessary.
The program obviously allows the setting for Global Settings >> Data/Trade Service Settings >> Common Settings >> Allow Support for Sierra Charts Data Feeds to deviate between the Main instance and a sub-instance. If such a configuration is possible, the result should be predictable. |
| [2026-04-28 21:20:25] |
| John - SC Support - Posts: 46649 |
|
What we were referring to is that you are creating more issues by bothering with that setting in a sub-instance. It actually has no impact whatsoever in a sub-instance. As we had noted previously, sub-instances are not directly connected to the Denali Exchange Data Feed, they get their data from the main instance. So whatever data is being received in the Main Instance will be what flows down to the Sub-Instances. 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-04-28 21:20:38
|
| [2026-04-29 21:07:57] |
| User512353 - Posts: 144 |
|
I have set up a new SC main instance with connect to Teton/Ironbeam. And I have set Global Settings >> Data/Trade Service Settings >> Common Settings >> Allow Support for Sierra Charts Data Feeds = No SC still connects to dsxx.sierracharts.com and gets delayed data from the server(s), while the three other, already connected SC main instances receive live data. This is not understandable. Why is SC connecting to SC data servers when it is told not to??? Log: ... 2026-04-29 13:50:03.979 | Delayed Data Feed | Starting real-time market data updates for: NQM26_FUT_CME (NQM26). ID: 1 Service code: cme 2026-04-29 13:50:03.979 | Delayed Data Feed | Connecting to the server ds32.sierracharts.com. Port 10043 2026-04-29 13:50:03.979 | Delayed Data Feed | Requesting security definition data for: NQM26_FUT_CME (NQM26). ID: 1 ... 2026-04-29 13:50:04.116 | Delayed Data Feed | Network connection to server complete. 2026-04-29 13:50:04.116 | Delayed Data Feed | Starting socket receive thread. 2026-04-29 13:50:04.116 | Delayed Data Feed | Sending encoding request to server: Binary VLS. Compression: standard 2026-04-29 13:50:04.251 | Delayed Data Feed | Setting DTC encoding to Binary VLS 2026-04-29 13:50:04.251 | Delayed Data Feed | Sending logon request message. 2026-04-29 13:50:04.814 | Delayed Data Feed | Received logon response. 2026-04-29 13:50:04.814 | Delayed Data Feed | Server Name: SC Realtime Server. 2026-04-29 13:50:04.814 | Delayed Data Feed | Server protocol version: 8. Client protocol version: 8 2026-04-29 13:50:04.814 | Delayed Data Feed | Successfully connected. 2026-04-29 13:50:04.814 | Delayed Data Feed | Trading is not supported. 2026-04-29 13:50:04.814 | Delayed Data Feed | MarketDepthIsSupported: 1 2026-04-29 13:50:04.814 | Delayed Data Feed | Restarting real-time data updates for symbol: NQM26_FUT_CME -> NQM26 2026-04-29 13:50:05.032 | Delayed Data Feed | Setting external service identifier for symbol NQM26_FUT_CME to 42004058 2026-04-29 13:50:05.032 | Delayed Data Feed | Received security definition for symbol NQM26_FUT_CME 2026-04-29 13:50:10.012 | HD Request # 1 | Downloading Intraday chart data for NQM26_FUT_CME to the file NQM26_FUT_CME.scid. Service: cme 2026-04-29 13:50:10.012 | HD Request # 1 | Download start date-time: 1976-05-11 13:50:10.000000. File last date-time: 00:00:00.000000 2026-04-29 13:50:10.012 | HD Request # 1 | Using server: ds26.sierracharts.com port 10150 2026-04-29 13:50:10.019 | Socket (6) | Creating socket. 2026-04-29 13:50:10.019 | Socket (6) | New receive buffer size: 5242880 2026-04-29 13:50:10.019 | Socket (6) | Connecting to IP: 64.152.155.17. 2026-04-29 13:50:10.276 | HD Request # 1 | Setting DTC encoding to Binary VLS 2026-04-29 13:50:10.276 | HD Request # 1 | Sending historical data logon request message. 2026-04-29 13:50:10.432 | HD Request # 1 | Requesting Intraday data. Start date-time: 1976-05-11 13:50:10. Record interval: 1. Symbol: NQM26 2026-04-29 13:50:10.553 | HD Request # 1 | Decompressing data. 2026-04-29 13:50:10.573 | HD Request # 1 | Receiving Intraday data for NQM26_FUT_CME starting at 2025-04-11 17:44:12.831000 2026-04-29 13:50:11.433 | HD Request # 1 | Timestamp of first Intraday data file record written: 2025-04-11 17:44:12.831000. 2026-04-29 13:50:27.488 | Socket (6) | CloseSocket call. 2026-04-29 13:50:27.488 | Socket (6) | Shutdown started. Waiting for graceful close. 2026-04-29 13:50:27.493 | Historical data download thread signaled to stop. 2026-04-29 13:50:27.493 | HD Request # 1 | Received 1747837 Intraday data records from 2025-04-11 17:44:12.831000 to 2026-04-29 13:50:25.240000 (382.8 days. Delay: 2.3 seconds) and wrote 1747837 records for NQM26_FUT_CME 2026-04-29 13:50:27.494 | HD Request # 1 | Add time&sales data | Remembered last file record date-time: 2026-04-29 13:50:25.240000 2026-04-29 13:50:27.494 | HD Request # 1 | Completion time: 17s. 2026-04-29 13:50:27.494 | HD Request # 1 | Intraday data download complete for NQM26_FUT_CME. Unique request ID: 1 2026-04-29 13:50:27.494 | Removing historical data download ID 1. 2026-04-29 13:50:27.494 | Real-time Intraday chart data file updates started for NQM26_FUT_CME 2026-04-29 13:50:27.494 | Opened cached Intraday file: E:\SierraChart\sc26\Data\NQM26_FUT_CME.scid. Thread ID: 1364 2026-04-29 13:50:27.494 | Intraday chart data file opened for NQM26_FUT_CME 2026-04-29 13:50:27.494 | HD Request # 1 | Enabling Intraday chart updating for symbol. |
| [2026-04-29 21:38:04] |
| John - SC Support - Posts: 46649 |
|
That is occurring because you are connecting to one of our services - Teton. In this case, setting the option of "Allow Support for Sierra Chart Data Feeds" to "No" means that you will get the delayed streaming data. But what you are doing makes no sense. By setting the option of "Allow Support for Sierra Chart Data Feeds" to "No" in a connection to Teton would mean that you are not going to get any real-time data, as that data has to come from us, since Teton is our service as well. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2026-04-29 22:23:00] |
| User512353 - Posts: 144 |
|
This confusing. In #4 above you said that You can setup one to not get data from our Denali Exchange Data Feed, and therefore it could get data from Interactive Brokers, or the other broker account
So, how do I do this then with Ironbeam, if not through Global Settings >> Data/Trade Service Settings >> Common Settings >> Allow Support for Sierra Charts Data Feeds = No ??? |
| [2026-04-30 14:00:33] |
| John - SC Support - Posts: 46649 |
|
You did not quote that line fully. The rest of it stated "...(depending on what service you are using with that broker)." If you were using Rithmic, then you could get the data from that account. But CQG or Teton would not work. You have us confused. You are setup to use Teton order routing with Ironbeam. Given this, any real-time data must come from our Denali Exchange Data Feed. What exactly are you trying to accomplish by setting "Allow Support For Sierra Chart Data Feeds" to "No" in that instance? Even though you are getting the delayed streaming data, that does not count towards the maximum of 3 installations getting real-time data at the same time. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2026-04-30 21:50:15] |
| User512353 - Posts: 144 |
|
What I am trying to accomplish? Well, it is documented above: Use the 4 named accounts in parallel on one computer. Looks like it does not work. I do not understand why there is a restriction of 3 data streams. I also do not understand why the SC design is so inflexible. The SC system design should be such that in one SC (main) instance - any number of data sources can be defined and used simultaneously - whereby any incoming data format discrepancies are automatically converted to the default format - any number of brokerage accounts can be defined and used simultaneously, including SC-sim and brokerage live accounts simultaneously - whereby any outgoing transaction data format discrepancies are automatically converted to the necessary format I am currently using 12 parallel SC installations, some with sub-instances, to get all my trading-related work done. It is insane! All because of the above restrictions! And now you want me to even get a second machine just because of this artificial restriction of 3 data streams. I could get all my trading-related work done with 2 SC installations, save 80% of my disk space, and save a lot of my time spent with maintaining these installations - if SC had a reasonable platform design with respect to data sources and execution interfaces. |
| [2026-04-30 21:54:53] |
| John - SC Support - Posts: 46649 |
|
These restrictions are not our choice. It is the exchanges that have these requirements. We are simply enforcing the rules. And taking data from multiple sources is not as simple as it sounds. There are an incredible amount of issues with other data services. Which is why we have our own. 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: