Home >> Support Board

Support Board

Date/Time: Tue, 22 Apr 2025 05:16:50 +0000

How to Post a Message for Support

Cant connect to Rithmic

View Count: 384

[2025-01-30 00:38:05] #1 [Go To First Post]
User968091 - Posts: 47
Why cant I connect any Rithmic connection to Sierra? I tried both Apex paper trading login and with the broker Advantage futures and neither of them work and it will not give me a server option for the live broker.


2025-01-29_17-32-43.png / V - Attached On 2025-01-30 00:37:15 UTC - Size: 153.26 KB - 48 views

[2025-01-30 15:00:19] #2 [Go To First Post]
John - SC Support - Posts: 39395
Refer to steps 7 through 11 at the following link: Rithmic Trading Platform Service: Setup Instructions 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: 2025-01-31 13:55:51

[2025-01-31 13:17:27] #3 [Go To First Post]
User135243 - Posts: 67
I guess we all have the same problem (or at least most). If you try to connect to Apex, enter your username/password and click A and Apply All and thereafter shut down SC and come back to the connection area and now you should see the servers

[2025-02-03 03:04:09] #4 [Go To First Post]
User968091 - Posts: 47
Thank you. That worked and it shows I am connected but my charts are not updating.


2025-02-02_20-02-12.png / V - Attached On 2025-02-03 03:03:46 UTC - Size: 1.44 MB - 37 views

[2025-02-03 03:55:22] #5 [Go To First Post]
Sierra_Chart Engineering - Posts: 19290
Regarding post #4, activate the exchanges that you need here: https://www.sierrachart.com/UserControlPanel.php?page=DenaliDataFeed 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

[2025-02-03 05:05:27] #6 [Go To First Post]
User968091 - Posts: 47
I am not currently using Denali. I am using Apex Rithmic and it is not updating after I followed the directions in the previous post and is showing as connected.

[2025-02-03 05:10:57] #7 [Go To First Post]
User968091 - Posts: 47
Im getting the following messages in the screenshot.


2025-02-02_22-10-03.png / V - Attached On 2025-02-03 05:10:24 UTC - Size: 1.26 MB - 38 views

[2025-02-03 05:34:55] #8 [Go To First Post]
Sierra_Chart Engineering - Posts: 19290
The easiest thing to do is to activate the CME Top of Book exchange here: https://www.sierrachart.com/UserControlPanel.php?page=DenaliDataFeed This will resolve the problem for you. Also newer versions of Sierra Chart, require the Denali Data Feed be used with Rithmic. This is 2727 and higher. 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

[2025-02-03 05:40:07] #9 [Go To First Post]
User968091 - Posts: 47
Why do I need to pay for a Denali feed if I have a live feed through Apex/Rithmic?

[2025-02-03 07:16:22] #10 [Go To First Post]
Sierra_Chart Engineering - Posts: 19290
We are not sure why you are having problems with the Rithmic data feed, looks like an authorization issue on the Rithmic side, as long as you are running Sierra Chart version 2726 or earlier. For the reasons why in newer versions we do not support Rithmic market data, refer to: https://www.sierrachart.com/index.php?page=doc/Whats_New.php#SCVer2728 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: 2025-02-03 07:17:11

[2025-02-03 08:29:37] #11 [Go To First Post]
User135243 - Posts: 67
S. ;) if you want to use the Rithmic connection with elder SC versions, you have to enter username/password 3times, otherwise it will not work. With the newer versions you need the Denali realtime data, but the Rithmic connection will still work. So as long you don't update SC it should work. (I use the new version with Denali)

[2025-02-03 12:31:11] #12 [Go To First Post]
User968091 - Posts: 47
Thanks. I updated because I thought I needed to based on the original response to my post. Is Apex considered a broker in order to receive the Denali feed?

[2025-02-03 17:32:32] #13 [Go To First Post]
John - SC Support - Posts: 39395
Is Apex considered a broker in order to receive the Denali feed? No. Prop firms do not count towards the requirement from the CME Group to be a Non-Professional. Refer to the following: Denali Exchange Data Feed: Understanding and Accessing Data From the CME, CBOT, NYMEX, COMEX Exchanges For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing

[2025-02-03 18:26:38] #14 [Go To First Post]
User968091 - Posts: 47
Ok, then that just brings me back to my original issue. I tried to connect to Rithmic directly after updating as the steps in the link you sent told me to do and now I cant get the Rithmic data to update. It shows I am connected but does not show real-time data updating.

[2025-02-03 22:52:04] #15 [Go To First Post]
John - SC Support - Posts: 39395
User968091: To start, we are a bit confused. You have the "Full CME Group for Non-Professional Trading Accounts" active, and your "Verified Until" date is showing as "2025-02-22". So you should be getting the real-time data for the CME Group from us without any issues. If you are not getting the data properly, then please get us your Message Log by following these instructions: Follow the instructions here to clear the Message Log: Message Log: Clearing the Message Log Close all of the Chartbooks with "File >> Close All Chartbooks". Open a single chart for the symbol you have an issue with through "File >> Find Symbol". Tell us that symbol of the chart. Tell us about one symbol only. Disconnect from the data feed with "File >> Disconnect". Connect to the data feed with "File >> Connect to Data Feed". After the connection and after about 10 seconds, provide a copy of the Message Log following these instructions: Support Board Posting Information: How to Post Your Message Log (Required In Some Cases) We will then determine what the problem is. We would like to work through this issue first, then we can move forward from there. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing

[2025-02-04 03:15:55] #16 [Go To First Post]
User968091 - Posts: 47
Yes, have the "Full CME Group for Non-Professional Trading Accounts" active because I had to resubscribe to the Denali feed today because my Rithmic feed wont update prices but is showing as connected, which is what the problem was in the very first thread. The symbol I brought up with the instructions is NQH5 2025-02-03 20:12:39.630 \| Software version: 2735 64-bit 2025-02-03 20:12:39.630 \| Primary Thread ID: 11276 2025-02-03 20:12:39.630 \| Usage end date: 2025-03-02 2025-02-03 20:12:39.630 \| Enabled for: Advanced Features 2. 2025-02-03 20:12:39.630 \| Enabled for: Sierra Chart Historical Data Service. 2025-02-03 20:12:39.630 \| Enabled for: Denali Real-Time Exchange Data Feed. 2025-02-03 20:12:39.630 \| Enabled for: Delayed Denali Exchange Data Feed. 2025-02-03 20:12:39.630 \| Enabled for exchange2: CME (Trading Account Required) 2025-02-03 20:12:39.630 \| Enabled for exchange2: CBOT (Trading Account Required) 2025-02-03 20:12:39.630 \| Enabled for exchange2: COMEX (Trading Account Required) 2025-02-03 20:12:39.630 \| Enabled for exchange2: NYMEX (Trading Account Required) 2025-02-03 20:12:39.630 \| Allow Support for Sierra Chart Data Feeds is enabled. 2025-02-03 20:12:39.630 \| Current selected Data/Trading service: Rithmic Direct - DTC 2025-02-03 20:12:39.630 \| Custom symbol settings values: disabled 2025-02-03 20:12:39.630 \| Chart Update Interval: 500 2025-02-03 20:12:39.630 \| Intraday Data Storage Time Unit: 0 2025-02-03 20:12:39.630 \| Time Zone: -07:00:00 (MST-07) 2025-02-03 20:12:39.630 \| 2025-02-04 03:12:39 Local computer time in UTC 2025-02-03 20:12:39.630 \| 2025-02-03 20:12:39 Local computer time in SC Time Zone 2025-02-03 20:12:39.630 \| 2025-02-03 12:28:22 Server time in UTC 2025-02-03 20:12:39.630 \| Local computer UTC time and Server UTC time difference: 3 seconds. 2025-02-03 20:12:39.630 \| Program path: C:\SierraChart\ 2025-02-03 20:12:39.630 \| Data Files path: C:\SierraChart\Data\ 2025-02-03 20:12:39.630 \| OS Version Number: 10.0 2025-02-03 20:12:39.630 \| Locale Setting: C 2025-02-03 20:12:39.632 \| DLLs: LudwigLevels_2151_64 (1).dll, LudwigLevels_2151_64.dll, sst_drawing_to_csv_64.dll, sst_drawtoolshare_64.dll, TASIndicators.dll, TASSierra_64.dll, UserContributedStudies.dll, UserContributedStudies_64.dll 2025-02-03 20:12:39.632 \| Allowed protected custom studies: Ludwig Levels 2025-02-03 20:12:39.632 \| Crash reporter started: true 2025-02-03 20:12:39.632 \| 2025-02-03 20:12:50.308 \| File >> Disconnect selected. 2025-02-03 20:12:50.309 \| Rithmic Direct - DTC \| Waiting for socket receive thread to end 2025-02-03 20:12:50.309 \| DTC Client socket (1) \| CloseSocket call. 2025-02-03 20:12:50.309 \| DTC Client socket (1) \| Max send buffers used during socket life: 3 2025-02-03 20:12:50.309 \| DTC Client socket (1) \| Max send buffer size during socket life: 406 2025-02-03 20:12:50.309 \| Denali Data Feed \| Waiting for socket receive thread to end 2025-02-03 20:12:50.309 \| DTC Client socket (1) \| Shutdown started. Waiting for graceful close. 2025-02-03 20:12:50.309 \| DTC Client socket (2) \| CloseSocket call. 2025-02-03 20:12:50.309 \| DTC Client socket (2) \| Shutdown started. Waiting for graceful close. 2025-02-03 20:12:50.309 \| Denali Data Feed \| Disconnected from the server. 2025-02-03 20:12:50.309 \| Rithmic Direct - DTC \| Disconnected. 2025-02-03 20:12:50.385 \| DTC Client socket (1) \| Socket gracefully closed by remote side. 2025-02-03 20:12:50.385 \| DTC Client socket (1) \| Closed. 2025-02-03 20:12:50.403 \| DTC Client socket (2) \| Socket gracefully closed by remote side. 2025-02-03 20:12:50.404 \| DTC Client socket (2) \| Closed. 2025-02-03 20:12:56.725 \| 2025-02-03 20:12:56.725 \| Rithmic Direct - DTC \| Using server connection: Apex-Chicago Area-Non-Aggregated 2025-02-03 20:12:56.725 \| Rithmic Direct - DTC \| Trading server address/port: rsc.rithmic.com:50528 2025-02-03 20:12:56.725 \| Rithmic Direct - DTC \| Connecting to the server rsc.rithmic.com. Port 50528 2025-02-03 20:12:56.726 \| DTC Client socket (1) \| Creating socket. Using TLS 1.2. 2025-02-03 20:12:56.726 \| DTC Client socket (1) \| New receive buffer size: 0 2025-02-03 20:12:56.726 \| DTC Client socket (1) \| Connecting to IP: 216.57.156.163. 2025-02-03 20:12:56.797 \| Rithmic Direct - DTC \| Network connection to server complete. 2025-02-03 20:12:56.797 \| Rithmic Direct - DTC \| Starting socket receive thread. 2025-02-03 20:12:56.797 \| Rithmic Direct - DTC \| Setting DTC encoding to Binary 2025-02-03 20:12:56.797 \| Rithmic Direct - DTC \| Sending logon request message. 2025-02-03 20:12:57.025 \| Rithmic Direct - DTC \| Received logon response. 2025-02-03 20:12:57.025 \| Rithmic Direct - DTC \| Server Name: . 2025-02-03 20:12:57.025 \| Rithmic Direct - DTC \| Server protocol version: 8. Client protocol version: 8 2025-02-03 20:12:57.025 \| Rithmic Direct - DTC \| Successfully connected. 2025-02-03 20:12:57.025 \| Rithmic Direct - DTC \| Trading is supported. 2025-02-03 20:12:57.025 \| Rithmic Direct - DTC \| Order cancel and replace is supported. 2025-02-03 20:12:57.025 \| Rithmic Direct - DTC \| OCO Orders supported. 2025-02-03 20:12:57.025 \| Rithmic Direct - DTC \| Symbol and Exchange Delimiter: . 2025-02-03 20:12:57.025 \| Rithmic Direct - DTC \| MarketDepthIsSupported: 0 2025-02-03 20:12:57.025 \| Rithmic Direct - DTC \| Connected to server complete. 2025-02-03 20:12:57.028 \| No download requests in the queue to start downloads for. \| Number times message added: 3 2025-02-03 20:12:57.028 \| Mapping NQU1.CME to NQU21. Service code: cme 2025-02-03 20:12:57.028 \| Using symbol data fast lookup vector 2025-02-03 20:12:57.028 \| Denali Data Feed \| Starting real-time market data updates for: NQU1.CME (NQU21). ID: 1 Service code: cme 2025-02-03 20:12:57.028 \| Denali Data Feed \| Connecting to the server ds32-2.sierracharts.com. Port 10048 2025-02-03 20:12:57.028 \| Denali Data Feed \| Requesting security definition data for: NQU1.CME (NQU21). ID: 1 2025-02-03 20:12:57.028 \| Added historical Intraday data request for NQU1.CME to the queue. 2025-02-03 20:12:57.028 \| Intraday data recording state for symbol NQU1.CME is set to download 'Pending'. 2025-02-03 20:12:57.028 \| Triggering next historical data download in queue. 2025-02-03 20:12:57.029 \| Delaying start of download for NQU1.CME. 2025-02-03 20:12:57.054 \| DTC Client socket (2) \| Creating socket. 2025-02-03 20:12:57.054 \| DTC Client socket (2) \| New receive buffer size: 0 2025-02-03 20:12:57.054 \| DTC Client socket (2) \| Connecting to IP: 67.214.125.4. 2025-02-03 20:12:57.144 \| Denali Data Feed \| Network connection to server complete. 2025-02-03 20:12:57.144 \| Denali Data Feed \| Starting socket receive thread. 2025-02-03 20:12:57.144 \| Denali Data Feed \| Sending encoding request to server: Binary VLS. Compression: standard 2025-02-03 20:12:57.234 \| Denali Data Feed \| Setting DTC encoding to Binary VLS 2025-02-03 20:12:57.234 \| Denali Data Feed \| Sending logon request message. 2025-02-03 20:12:57.384 \| Mapping NQH5.CME to NQH25. Service code: cme 2025-02-03 20:12:57.384 \| Denali Data Feed \| Starting real-time market data updates for: NQH5.CME (NQH25). ID: 2 Service code: cme 2025-02-03 20:12:57.384 \| Denali Data Feed \| Requesting security definition data for: NQH5.CME (NQH25). ID: 2 2025-02-03 20:12:57.769 \| Denali Data Feed \| Received logon response. 2025-02-03 20:12:57.769 \| Denali Data Feed \| Server Name: SC Realtime Server. 2025-02-03 20:12:57.769 \| Denali Data Feed \| Server protocol version: 8. Client protocol version: 8 2025-02-03 20:12:57.769 \| Denali Data Feed \| Successfully connected. 2025-02-03 20:12:57.769 \| Denali Data Feed \| Trading is not supported. 2025-02-03 20:12:57.769 \| Denali Data Feed \| MarketDepthIsSupported: 1 2025-02-03 20:12:57.769 \| Denali Data Feed \| Restarting real-time data updates for symbol: NQH5.CME -> NQH25 2025-02-03 20:12:57.769 \| Denali Data Feed \| Restarting real-time data updates for symbol: NQU1.CME -> NQU21 2025-02-03 20:12:57.955 \| Denali Data Feed \| Setting external service identifier for symbol NQH5.CME to 42288528 2025-02-03 20:12:57.955 \| Denali Data Feed \| Received security definition for symbol NQH5.CME 2025-02-03 20:12:57.955 \| Denali Data Feed \| Real-time data for symbol NQU1.CME is currently unavailable. 2025-02-03 20:12:57.955 \| Denali Data Feed \| Received security definition for symbol NQU1.CME 2025-02-03 20:13:02.848 \| HD Request # 576 \| Downloading Intraday chart data for NQU1.CME to the file NQU1.CME.scid. Service: cme 2025-02-03 20:13:02.849 \| HD Request # 576 \| Download start date-time: 2021-09-17 06:29:59.000000. File last date-time: 2021-09-17 06:29:59.967000 2025-02-03 20:13:02.849 \| HD Request # 576 \| Using server: ds28.sierracharts.com port 10149 2025-02-03 20:13:02.849 \| Socket (3) \| Creating socket. 2025-02-03 20:13:02.849 \| Socket (3) \| New receive buffer size: 0 2025-02-03 20:13:02.849 \| Socket (3) \| Connecting to IP: 67.214.125.5. 2025-02-03 20:13:03.034 \| HD Request # 576 \| Setting DTC encoding to Binary VLS 2025-02-03 20:13:03.034 \| HD Request # 576 \| Sending historical data logon request message. 2025-02-03 20:13:03.168 \| HD Request # 576 \| Requesting Intraday data. Start date-time: 2021-09-17 06:29:59. Record interval: 0. Symbol: NQU21 2025-02-03 20:13:03.258 \| HD Request # 576 \| Decompressing data. 2025-02-03 20:13:03.342 \| HD Request # 576 \| Receiving Intraday data for NQU1.CME starting at 2021-09-17 06:29:59.133000 2025-02-03 20:13:03.342 \| Socket (3) \| CloseSocket call. 2025-02-03 20:13:03.342 \| Socket (3) \| Shutdown started. Waiting for graceful close. 2025-02-03 20:13:03.343 \| Historical data download thread signaled to stop. 2025-02-03 20:13:03.343 \| HD Request # 576 \| Received 4 Intraday data records from 2021-09-17 06:29:59.133000 to 2021-09-17 06:29:59.967000 (0.8 seconds. Delay: 3.4 years) and wrote 0 records for NQU1.CME 2025-02-03 20:13:03.343 \| HD Request # 576 \| Add time&sales data \| Remembered last file record date-time: 2021-09-17 13:29:59.967000 2025-02-03 20:13:03.343 \| HD Request # 576 \| Completion time: 1s. 2025-02-03 20:13:03.343 \| HD Request # 576 \| Intraday data download complete for NQU1.CME. Unique request ID: 574 2025-02-03 20:13:03.343 \| Removing historical data download ID 574. 2025-02-03 20:13:03.343 \| Real-time Intraday chart data file updates started for NQU1.CME 2025-02-03 20:13:03.343 \| Intraday chart data file opened for NQU1.CME 2025-02-03 20:13:03.343 \| HD Request # 576 \| Enabling Intraday chart updating for symbol. 2025-02-03 20:13:03.343 \| 2025-02-03 20:13:03.343 \| No download requests in the queue to start downloads for. 2025-02-03 20:13:03.427 \| Socket (3) \| Socket gracefully closed by remote side. 2025-02-03 20:13:03.427 \| Socket (3) \| Closed. 2025-02-03 20:13:16.715 \| HTTPS connection ID:4 to downloads.rithmic.com:443 for request ID:4 (3) \| Creating socket. Using TLS 1.2. 2025-02-03 20:13:16.715 \| HTTPS connection ID:4 to downloads.rithmic.com:443 for request ID:4 (3) \| New receive buffer size: 0 2025-02-03 20:13:16.715 \| HTTPS connection ID:4 to downloads.rithmic.com:443 for request ID:4 (3) \| Connecting to IP: 216.66.0.130. 2025-02-03 20:13:17.236 \| Rithmic Direct - DTC \| Wrote file: C:\SierraChart\RithmicConnections.json. Size: 81131 2025-02-03 20:13:17.238 \| Rithmic Direct - DTC \| Processed connection points. Count: 347 2025-02-03 20:13:17.491 \| HTTPS connection ID:4 to downloads.rithmic.com:443 for request ID:4 (3) \| CloseSocket call. 2025-02-03 20:13:17.491 \| HTTPS connection ID:4 to downloads.rithmic.com:443 for request ID:4 (3) \| Shutdown started. Waiting for graceful close. 2025-02-03 20:13:17.572 \| HTTPS connection ID:4 to downloads.rithmic.com:443 for request ID:4 (3) \| Socket gracefully closed by remote side. 2025-02-03 20:13:17.572 \| HTTPS connection ID:4 to downloads.rithmic.com:443 for request ID:4 (3) \| Closed.

[2025-02-04 16:25:00] #17 [Go To First Post]
John - SC Support - Posts: 39395
There are no errors or issues showing in the log. But it shows that there are charts open for both NQU1.CME and NQH5.CME. We only see data being downloaded for NQU1.CME in the log. Please follow the instructions below to get us the log, but only open a chart for NQH5.CME Follow the instructions here to clear the Message Log: Message Log: Clearing the Message Log Close all of the Chartbooks with "File >> Close All Chartbooks". Open a single chart for the symbol you have an issue with through "File >> Find Symbol". Tell us that symbol of the chart. Tell us about one symbol only. Disconnect from the data feed with "File >> Disconnect". Connect to the data feed with "File >> Connect to Data Feed". After the connection and after about 10 seconds, provide a copy of the Message Log following these instructions: Support Board Posting Information: How to Post Your Message Log (Required In Some Cases) We will then determine what the problem is. 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: