Support Board
Date/Time: Thu, 06 Mar 2025 21:57:35 +0000
Using Multiple Data and Trading Services at the Same Time
View Count: 1089
| [2022-02-14 15:16:47] |
| madness99 - Posts: 35 |
|
Hi Support, I am trying to setup Multiple Data and Trading Services at the Same time suggested in the article below. Using Multiple Data and Trading Services at the Same Time I believe everything was setup correctly on my end but it's not working correctly. I am not getting intraday or historical data. Here are some screenshots of my configuration. Here is my log from 2nd copy of sierra chart as stated in the document. Software version: 2353 64-bit | 2022-02-13 18:20:47.311 Primary Thread ID: 23500 | 2022-02-13 18:20:47.311 Usage end date: 2022-03-09 | 2022-02-13 18:20:47.311 Enabled for: Advanced Features 2. | 2022-02-13 18:20:47.311 Enabled for: Sierra Chart Historical Data Service. | 2022-02-13 18:20:47.311 Enabled for: Delayed Denali Exchange Data Feed. | 2022-02-13 18:20:47.311 Allow Support for Sierra Chart Data Feeds is enabled. | 2022-02-13 18:20:47.311 Current selected Data/Trading service: Rithmic Direct - DTC | 2022-02-13 18:20:47.311 Custom symbol settings values: enabled | 2022-02-13 18:20:47.311 Chart Update Interval: 800 | 2022-02-13 18:20:47.311 Intraday Data Storage Time Unit: 0 | 2022-02-13 18:20:47.311 Time Zone: -05:00:00 (EST-05EDT+01,M3.2.0/02:00,M11.1.0/02:00) | 2022-02-13 18:20:47.311 2022-02-13 23:20:47 Local computer time in UTC | 2022-02-13 18:20:47.311 2022-02-13 18:20:47 Local computer time in SC Time Zone | 2022-02-13 18:20:47.311 2022-02-12 13:15:53 Server time in UTC | 2022-02-13 18:20:47.311 Local computer UTC time and Server UTC time difference: 1 seconds. | 2022-02-13 18:20:47.311 Program path: F:\SierraChart - Helios 100K\ | 2022-02-13 18:20:47.311 Data Files path: F:\SierraChart - Helios 100K\Data\ | 2022-02-13 18:20:47.311 OS Version Number: 10.0 | 2022-02-13 18:20:47.311 Locale Setting: C | 2022-02-13 18:20:47.311 DLLs: DeltaPivotPoints_64 (1).dll, DeltaPivotPoints_64.dll, FootprintReversalSystem_64.dll, OFA Bars (by Zdislav)_2151_64.dll, OrderFlowLabs.com.beta_64.dll, OrderFlowLabs.com_64.dll, sst_draw_imbalance_64.dll, sst_FreeBundle_64.dll, UserContributedStudies_64.dll, zyp sierra free 2020_2151_64.dll, zyp sierra free 2021_2151_64.dll, zyp sierra free_2151_64.dll | 2022-02-13 18:20:47.312 Allowed protected custom studies: OrderFlowLabs.com, OrderFlowLabs.com Beta, SST_FreeBundle | 2022-02-13 18:20:47.312 HTTPS connection ID:259 to www.rithmic.com:443 for request ID:259 (1) | Creating socket. Using TLS 1.2. | 2022-02-13 18:20:52.388 HTTPS connection ID:259 to www.rithmic.com:443 for request ID:259 (1) | New receive buffer size: 32768 | 2022-02-13 18:20:52.388 HTTPS connection ID:259 to www.rithmic.com:443 for request ID:259 (1) | Connecting to IP: 38.79.0.89. | 2022-02-13 18:20:52.388 HTTPS connection ID:259 to www.rithmic.com:443 for request ID:259 (1) | Socket gracefully closed by remote side. | 2022-02-13 18:20:52.445 HTTPS connection ID:259 to www.rithmic.com:443 for request ID:259 (1) | CloseSocket call. | 2022-02-13 18:20:52.445 HTTPS connection ID:259 to www.rithmic.com:443 for request ID:259 (1) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2022-02-13 18:20:52.445 HTTPS connection ID:259 to www.rithmic.com:443 for request ID:259 (1) | Closed. | 2022-02-13 18:20:52.445 Rithmic Direct - DTC | Using server connection: Rithmic 01-Chicago Area-Aggregated | 2022-02-13 18:21:02.670 Rithmic Direct - DTC | Connecting to the server rsc.rithmic.com. Port 50503 | 2022-02-13 18:21:02.670 DTC Client socket (1) | Creating socket. Using TLS 1.2. | 2022-02-13 18:21:02.670 DTC Client socket (1) | New receive buffer size: 5242880 | 2022-02-13 18:21:02.670 DTC Client socket (1) | Connecting to IP: 216.57.156.163. | 2022-02-13 18:21:02.670 Rithmic Direct - DTC | Network connection to server complete. | 2022-02-13 18:21:02.696 Rithmic Direct - DTC | Starting socket receive thread. | 2022-02-13 18:21:02.696 Rithmic Direct - DTC | Setting DTC encoding to Binary | 2022-02-13 18:21:02.696 Rithmic Direct - DTC | Sending logon request message. | 2022-02-13 18:21:02.696 Rithmic Direct - DTC | Received logon response. | 2022-02-13 18:21:02.777 Rithmic Direct - DTC | Server Name: . | 2022-02-13 18:21:02.777 Rithmic Direct - DTC | Server protocol version: 8. Client protocol version: 8 | 2022-02-13 18:21:02.777 Rithmic Direct - DTC | Successfully connected. | 2022-02-13 18:21:02.777 Rithmic Direct - DTC | Trading is supported. | 2022-02-13 18:21:02.777 Rithmic Direct - DTC | Order cancel and replace is supported. | 2022-02-13 18:21:02.777 Rithmic Direct - DTC | OCO Orders supported. | 2022-02-13 18:21:02.777 Rithmic Direct - DTC | Symbol and Exchange Delimiter: . | 2022-02-13 18:21:02.777 Rithmic Direct - DTC | Connected to server complete. | 2022-02-13 18:21:02.777 Triggering next historical data download in queue. | 2022-02-13 18:21:02.777 Triggering next historical data download in queue. | 2022-02-13 18:21:02.777 Triggering next historical data download in queue. | 2022-02-13 18:21:02.777 Triggering next historical data download in queue. | 2022-02-13 18:21:02.777 Updated verified funded futures trading account ending date to: 2022-03-15 23:21:02 | 2022-02-13 18:21:02.777 No download requests in the queue to start downloads for. | 2022-02-13 18:21:02.784 No download requests in the queue to start downloads for. | 2022-02-13 18:21:02.784 No download requests in the queue to start downloads for. | 2022-02-13 18:21:02.784 No download requests in the queue to start downloads for. | 2022-02-13 18:21:02.784 Using symbol data fast lookup vector | 2022-02-13 18:21:02.784 Generic Client (127.0.0.1:11099) | Starting real-time market data updates for: MESH2.CME (MESH22). ID: 1 Service code: rithmic.trading | 2022-02-13 18:21:02.785 Generic Client (127.0.0.1:11099) | Connecting to the server 127.0.0.1. Port 11099 | 2022-02-13 18:21:02.785 DTC Client socket (2) | Creating socket. | 2022-02-13 18:21:02.785 Generic Client (127.0.0.1:11099) | Requesting security definition data for: MESH2.CME (MESH22). ID: 1 | 2022-02-13 18:21:02.785 Generic Client (127.0.0.1:11099) | Starting real-time market data updates for: ESH2.CME (ESH22). ID: 2 Service code: rithmic.trading | 2022-02-13 18:21:02.785 Generic Client (127.0.0.1:11099) | Requesting security definition data for: ESH2.CME (ESH22). ID: 2 | 2022-02-13 18:21:02.785 DTC Client socket (2) | New receive buffer size: 5242880 | 2022-02-13 18:21:02.785 DTC Client socket (2) | Connecting to IP: 127.0.0.1. | 2022-02-13 18:21:02.785 Added historical Intraday data request for ESH2.CME to the queue. | 2022-02-13 18:21:02.785 Intraday data recording state for symbol ESH2.CME is set to download 'Pending'. | 2022-02-13 18:21:02.785 Triggering next historical data download in queue. | 2022-02-13 18:21:02.785 Delaying start of download for ESH2.CME | 2022-02-13 18:21:02.805 Generic Client (127.0.0.1:11099) | Network connection to server complete. | 2022-02-13 18:21:02.805 Generic Client (127.0.0.1:11099) | Starting socket receive thread. | 2022-02-13 18:21:02.805 Generic Client (127.0.0.1:11099) | Sending encoding request to server: Binary VLS. Compression: none | 2022-02-13 18:21:02.805 Generic Client (127.0.0.1:11099) | Setting DTC encoding to Binary VLS | 2022-02-13 18:21:02.811 Generic Client (127.0.0.1:11099) | Sending logon request message. | 2022-02-13 18:21:02.811 Generic Client (127.0.0.1:11099) | Starting real-time market data updates for: MNQH2.CME (MNQH22). ID: 3 Service code: rithmic.trading | 2022-02-13 18:21:02.811 Generic Client (127.0.0.1:11099) | Requesting security definition data for: MNQH2.CME (MNQH22). ID: 3 | 2022-02-13 18:21:02.811 Generic Client (127.0.0.1:11099) | Starting real-time market data updates for: NQH2.CME (NQH22). ID: 4 Service code: rithmic.trading | 2022-02-13 18:21:02.811 Generic Client (127.0.0.1:11099) | Requesting security definition data for: NQH2.CME (NQH22). ID: 4 | 2022-02-13 18:21:02.811 Added historical Intraday data request for NQH2.CME to the queue. | 2022-02-13 18:21:02.814 Intraday data recording state for symbol NQH2.CME is set to download 'Pending'. | 2022-02-13 18:21:02.814 Triggering next historical data download in queue. | 2022-02-13 18:21:02.814 Updated verified funded futures trading account ending date to: 2022-03-15 23:21:02 | 2022-02-13 18:21:02.829 Generic Client (127.0.0.1:11099) | Received logon response. | 2022-02-13 18:21:02.829 Generic Client (127.0.0.1:11099) | Server Name: SC DTC Server. Build=40998M. | 2022-02-13 18:21:02.829 Generic Client (127.0.0.1:11099) | Server protocol version: 8. Client protocol version: 8 | 2022-02-13 18:21:02.829 Generic Client (127.0.0.1:11099) | Successfully connected. Connected to SC DTC Protocol server. Service=rithmic_v2.trading|SymbolSettings=rithmic_v2.trading. | 2022-02-13 18:21:02.829 Generic Client (127.0.0.1:11099) | Trading is supported. | 2022-02-13 18:21:02.829 Generic Client (127.0.0.1:11099) | Order cancel and replace is supported. | 2022-02-13 18:21:02.829 Generic Client (127.0.0.1:11099) | OCO Orders supported. | 2022-02-13 18:21:02.829 Generic Client (127.0.0.1:11099) | Bracket Orders supported. | 2022-02-13 18:21:02.829 Generic Client (127.0.0.1:11099) | Restarting real-time data updates for symbol: ESH2.CME -> ESH22 | 2022-02-13 18:21:02.829 Generic Client (127.0.0.1:11099) | Restarting real-time data updates for symbol: MESH2.CME -> MESH22 | 2022-02-13 18:21:02.829 Generic Client (127.0.0.1:11099) | Restarting real-time data updates for symbol: MNQH2.CME -> MNQH22 | 2022-02-13 18:21:02.829 Generic Client (127.0.0.1:11099) | Restarting real-time data updates for symbol: NQH2.CME -> NQH22 | 2022-02-13 18:21:02.829 Generic Client (127.0.0.1:11099) | Received security definition for symbol ESH2.CME | 2022-02-13 18:21:02.830 Generic Client (127.0.0.1:11099) | Received security definition for symbol MESH2.CME | 2022-02-13 18:21:02.830 Generic Client (127.0.0.1:11099) | Received security definition for symbol MNQH2.CME | 2022-02-13 18:21:02.830 Generic Client (127.0.0.1:11099) | Received security definition for symbol NQH2.CME | 2022-02-13 18:21:02.830 HD Request # 31 | Downloading Intraday chart data for ESH2.CME to the file ESH2.CME.scid. Service: rithmic.trading | 2022-02-13 18:21:07.455 HD Request # 31 | Download start date-time: 2022-02-11 16:59:59.000000. File last date-time: 2022-02-11 16:59:59.000000 | 2022-02-13 18:21:07.456 HD Request # 31 | Using server: 127.0.0.1 port 11098 | 2022-02-13 18:21:07.456 Socket (3) | Creating socket. | 2022-02-13 18:21:07.456 Socket (3) | New receive buffer size: 5242880 | 2022-02-13 18:21:07.456 Socket (3) | Connecting to IP: 127.0.0.1. | 2022-02-13 18:21:07.456 HD Request # 31 | Setting DTC encoding to Binary VLS | 2022-02-13 18:21:07.537 HD Request # 31 | Sending historical data logon request message. | 2022-02-13 18:21:07.537 HD Request # 31 | Requesting Intraday data. Start date-time: 2022-02-11 16:59:59. Record interval: 0. Symbol: ESH22 | 2022-02-13 18:21:07.538 Socket (3) | CloseSocket call. | 2022-02-13 18:21:07.539 Historical data download thread signaled to stop. | 2022-02-13 18:21:07.539 HD Request # 31 | Received 0 Intraday data records from 00:00:00.000000 to 00:00:00.000000 (0.0 seconds) and wrote 0 records for ESH2.CME | 2022-02-13 18:21:07.539 Socket (3) | Shutdown started. Waiting for graceful close. | 2022-02-13 18:21:07.539 HD Request # 31 | Add time&sales data | Remembered last file record date-time: 2022-02-11 21:59:59.000000 | 2022-02-13 18:21:07.539 HD Request # 31 | Completion time: 0s | 2022-02-13 18:21:07.539 HD Request # 31 | Intraday data download complete for ESH2.CME. Unique request ID: 43 | 2022-02-13 18:21:07.539 Removing historical data download ID 43. | 2022-02-13 18:21:07.539 Real-time Intraday chart data file updates started for ESH2.CME | 2022-02-13 18:21:07.539 Intraday chart data file opened for ESH2.CME | 2022-02-13 18:21:07.539 HD Request # 31 | Enabling Intraday chart updating for symbol. | 2022-02-13 18:21:07.539 Triggering next historical data download in queue. | 2022-02-13 18:21:07.539 HD Request # 32 | Downloading Intraday chart data for NQH2.CME to the file NQH2.CME.scid. Service: rithmic.trading | 2022-02-13 18:21:07.539 Socket (3) | Socket gracefully closed by remote side. | 2022-02-13 18:21:07.539 Socket (3) | Closed. | 2022-02-13 18:21:07.539 HD Request # 32 | Download start date-time: 2022-02-11 16:59:59.000000. File last date-time: 2022-02-11 16:59:59.000003 | 2022-02-13 18:21:07.540 HD Request # 32 | Using server: 127.0.0.1 port 11098 | 2022-02-13 18:21:07.540 Socket (3) | Creating socket. | 2022-02-13 18:21:07.540 Socket (3) | New receive buffer size: 5242880 | 2022-02-13 18:21:07.540 Socket (3) | Connecting to IP: 127.0.0.1. | 2022-02-13 18:21:07.540 HD Request # 32 | Setting DTC encoding to Binary VLS | 2022-02-13 18:21:07.554 HD Request # 32 | Sending historical data logon request message. | 2022-02-13 18:21:07.554 HD Request # 32 | Requesting Intraday data. Start date-time: 2022-02-11 16:59:59. Record interval: 0. Symbol: NQH22 | 2022-02-13 18:21:07.555 Socket (3) | CloseSocket call. | 2022-02-13 18:21:07.556 Socket (3) | Shutdown started. Waiting for graceful close. | 2022-02-13 18:21:07.556 Socket (3) | Socket gracefully closed by remote side. | 2022-02-13 18:21:07.556 Socket (3) | Closed. | 2022-02-13 18:21:07.556 Historical data download thread signaled to stop. | 2022-02-13 18:21:07.566 HD Request # 32 | Received 0 Intraday data records from 00:00:00.000000 to 00:00:00.000000 (0.0 seconds) and wrote 0 records for NQH2.CME | 2022-02-13 18:21:07.566 HD Request # 32 | Add time&sales data | Remembered last file record date-time: 2022-02-11 21:59:59.000003 | 2022-02-13 18:21:07.566 HD Request # 32 | Completion time: 0s | 2022-02-13 18:21:07.567 HD Request # 32 | Intraday data download complete for NQH2.CME. Unique request ID: 44 | 2022-02-13 18:21:07.567 Removing historical data download ID 44. | 2022-02-13 18:21:07.567 Real-time Intraday chart data file updates started for NQH2.CME | 2022-02-13 18:21:07.567 Intraday chart data file opened for NQH2.CME | 2022-02-13 18:21:07.567 HD Request # 32 | Enabling Intraday chart updating for symbol. | 2022-02-13 18:21:07.567 Triggering next historical data download in queue. | 2022-02-13 18:21:07.567 No download requests in the queue to start downloads for. | 2022-02-13 18:21:07.567 Requesting market depth updates for: MESH2.CME if supported. | 2022-02-13 18:21:07.779 Requesting market depth updates for: MNQH2.CME if supported. | 2022-02-13 18:21:07.779 Generic Client (127.0.0.1:11099) | Clearing market depth for MESH2.CME | 2022-02-13 18:21:07.780 Generic Client (127.0.0.1:11099) | Clearing market depth for MESH2.CME | 2022-02-13 18:21:07.780 Generic Client (127.0.0.1:11099) | Clearing market depth for MNQH2.CME | 2022-02-13 18:21:07.780 Generic Client (127.0.0.1:11099) | Clearing market depth for MNQH2.CME | 2022-02-13 18:21:07.780 HTTPS connection ID:260 to www.rithmic.com:443 for request ID:260 (3) | Creating socket. Using TLS 1.2. | 2022-02-13 18:21:32.667 HTTPS connection ID:260 to www.rithmic.com:443 for request ID:260 (3) | New receive buffer size: 32768 | 2022-02-13 18:21:32.667 HTTPS connection ID:260 to www.rithmic.com:443 for request ID:260 (3) | Connecting to IP: 38.79.0.89. | 2022-02-13 18:21:32.667 HTTPS connection ID:260 to www.rithmic.com:443 for request ID:260 (3) | Socket gracefully closed by remote side. | 2022-02-13 18:21:32.715 HTTPS connection ID:260 to www.rithmic.com:443 for request ID:260 (3) | CloseSocket call. | 2022-02-13 18:21:32.715 HTTPS connection ID:260 to www.rithmic.com:443 for request ID:260 (3) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2022-02-13 18:21:32.715 HTTPS connection ID:260 to www.rithmic.com:443 for request ID:260 (3) | Closed. | 2022-02-13 18:21:32.715 Thanks https://www.sierrachart.com/Download.php?Folder=TicketingSystem&download=61367 https://www.sierrachart.com/Download.php?Folder=TicketingSystem&download=61368 https://www.sierrachart.com/Download.php?Folder=TicketingSystem&download=61369 |
| [2022-02-14 18:30:10] |
| John - SC Support - Posts: 38463 |
|
Are you getting data in your first instance? And what service is that instance connected to? Although there is no error showing up, we are wondering if the problem you are having is due to having 2 different connections to Rithmic at the same time, hence 2 different data connections. But, you would have to check with your broker if this is an issue or not. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2022-02-14 18:41:50] |
| madness99 - Posts: 35 |
|
Hi John, This is my setup. I have two copies of SC running. My primary SC is an Apex prop Rithmic connection. The data works fine My second SC is Helios Live Rithmic with data. I am trying to connect to the data using the multiple data connection setting. I configured the Global Symbol Settings for MES with real-time data client using the generic sub-client. From reading the document, that should work. On my 2nd SC, I can submit order so that works, but I’m just not getting any data from the sub-client option. Regard, Jerome |
| [2022-02-14 19:32:31] |
| John - SC Support - Posts: 38463 |
|
The connection you are trying to make between the systems can be done, but it seems a bit more complicated than what you need for your setup. Is there a reason why you can not connect each installation to the specific firm for data/trading? In other words, have Primary installation set to Apex with a Rithmic connection and then have Secondary installation set to Helios with a Rithmic connection? Otherwise, you would have to go through the following setup in order to get data into that second instance and be able to trade out of that system to Helios: https://www.sierrachart.com/index.php?page=doc/MultipleServices.html#AccessingMarketDataFromOtherInstancesOfSierra%20Chart For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2022-02-14 21:20:52] |
| madness99 - Posts: 35 |
|
Hi John, That is what I’m doing. My first connection from Apex connects to their paper trading server but on the 2nd Helio Rithmic connects to Rithmic 01 live server. I’m trying to piggy back on the paper trading server data connection. Is there an easier way, I’m all ears. Thanks Jerome |
| [2022-02-14 22:33:12] |
| John - SC Support - Posts: 38463 |
|
If you do not get data directly on that 2nd connection, then it makes sense what you are doing. You could, however, use the Denali Exchange Data Feed instead, and as long as both installations are on the same computer, then you would be able to get the data to both installations for the same cost. You would just need to have a live, funded, futures trading account that you can connect to in order to qualify for the non-professional exchange fees. Refer to the information here: Real-Time Exchange Data Feeds Available From Sierra Chart: Understanding and Accessing Data From the CME, CBOT, NYMEX, COMEX Exchanges And refer to the following for the Denali Exchange Data Feed in general: 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 |
| [2022-02-14 22:59:14] |
| madness99 - Posts: 35 |
|
Hi John, Then what am I doing wrong why my 2nd i stance is not receiving data? I prefer to not pay anything extra, since I already have to pay fees for these prop firm. Thanks Jerome |
| [2022-02-15 14:38:33] |
| John - SC Support - Posts: 38463 |
|
First thing we need to understand - are you not setup to get data from Helios? Typically the Prop firms include the data, so this has us a bit confused.
For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2022-02-15 14:59:35] |
| |
|
We see you are using Rithmic data. You are most definitely going to have issues with this. You need to use the Denali Exchange Data Feed for market data when using Rithmic. Refer to: Rithmic Trading Platform Service: Rithmic Support Policy I prefer to not pay anything extra, since I already have to pay fees for these prop firm. Easy Solution to CME Funded Trading Account Requirement 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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2022-02-15 15:06:41
|
| [2022-02-15 17:43:12] |
| madness99 - Posts: 35 |
|
Hi John, I had an option to have Helios to provide me with data or without data. I chose the the option of not having data because I’m already paying apex for evaluation. I figure I can piggy back on that data option using the following SC Link: Using Multiple Data and Trading Services at the Same Time From what I read and following the instruction, it should work? Regards, Jerome |
| [2022-02-15 18:15:11] |
| John - SC Support - Posts: 38463 |
|
Ok, thanks for the information. The section of documentation you need is the following: https://www.sierrachart.com/index.php?page=doc/MultipleServices.html#AccessingMarketDataFromOtherInstancesOfSierra%20Chart You would need to follow through those instructions and update symbol settings for all the symbols for which you want to get the data from the primary source. Just be sure you follow all the instructions carefully and it should work for you. Another option would be to use the Denali Exchange Data Feed as we mentioned previously. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2022-02-15 20:50:05] |
| madness99 - Posts: 35 |
|
Hi John, I did follow the document. Here is a screenshot of my configuration. I modified the symbol as stated in the document with the correct settings. Regards, Jerome |
 Source DTC Server.jpg / V - Attached On 2022-02-15 20:48:36 UTC - Size: 123.77 KB - 160 views 2nd SIerra Chart setup for MES.jpg / V - Attached On 2022-02-15 20:49:14 UTC - Size: 108.82 KB - 164 views |
| [2022-02-16 15:04:31] |
| John - SC Support - Posts: 38463 |
|
The one thing we see is that your Source Data Symbol is not correct. If you are getting Rithmic data in the Main instance, then your Source Data Symbol needs to be the symbol in the Main instance, in this case, you would want to use MES?##.CME and then make sure the symbol setting for Use Pattern Matching Characters is set to Yes. We really do recommend just using the Denali data, as you can get it to both instances without having to pay anything extra. If you do not have a live trading account, then you can use the following service in order to qualify for the Non-Professional exchange fees: Easy Solution to CME Funded Trading Account Requirement For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2022-02-16 21:11:39] |
| madness99 - Posts: 35 |
|
Hi John, I believe I have everything setup correct. Here is the screenshot of MES Global Symbol. Thanks John for your help Regards, Jerome |
| MES GLobal Symbol.jpg / V - Attached On 2022-02-16 21:09:53 UTC - Size: 224.87 KB - 158 views Source DTC Server.jpg / V - Attached On 2022-02-16 21:11:09 UTC - Size: 123.77 KB - 148 views |
| [2022-02-16 21:40:35] |
| John - SC Support - Posts: 38463 |
|
The only thing we can see if that you will want to specify a "Category" that is different from what the primary symbol would be located. Just make sure you have gone through all of the items as specified in the link for how to set this up. The "Category" is one of the items listed. The only thing I am doing is looking through that documentation, as I have set this up in the past, but not done it recently. I know it works, you just have to go through every item and make sure it is setup properly. 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: