Login Page - Create Account

Support Board


Date/Time: Sun, 03 Jul 2022 00:25:30 +0000



[Sticky] [Locked] - Notice: Required Update for Rithmic Users (Version 2372, May 15, 2022)

View Count: 2095

[2022-04-27 21:08:18]
Sierra Chart Engineering - Posts: 103558
Support for versions prior to 2372 when using Rithmic are going to be discontinued May 8, 2022.

Rithmic users will need to update by following the instructions here:
Software Download: Fast Update

After May 14, 2022 older versions prior to 2372 will be locked out. An update will happen automatically when you start Sierra Chart when using a version prior to 2372.

If you need any help with updating, then let us know.

If you are updating from a version from approximately more than two years ago, you need to refer to the information here to open your Chartbooks in the newer versions:
Chartbooks (Workspaces): Opening Older Chartbooks

If you are also updating from a significantly older version, then there is a new method of connecting to Rithmic. You will need to go through the setup instructions here:
Rithmic Trading Platform Service: Setup Instructions

And be sure to read the information here:
Rithmic Trading Platform Service: Rithmic Market Data and Support Policy

There are also Service Package changes and when using Rithmic with Sierra Chart you will need to start using Service Package 10 or higher:
https://www.sierrachart.com/SupportBoard.php?ThreadID=72282
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-05-24 10:43:22
[2022-04-28 00:26:50]
LeDork - Posts: 18
If I could do it differently, I would. Unfortunately, funded programs such as Apex/Leeloo etc. all use Rithmic. That being said, I'm on 2382 so I assume this post does not really concern me, but I'm checking just to be sure.
[2022-04-28 01:19:15]
Predicate - Posts: 8
Just an FYI. I gave Rithmic an earful a while back and they got around to fixing the historical tick data on the DTC feed. Just don't abuse it or try to grab more than 10 days of backfill too frequently. In fact, their DTC connection now has better historical tick data than their own software does for Corn and Wheat futures. They said they were also working on getting compression working.
[2022-04-28 10:54:37]
Sierra Chart Engineering - Posts: 103558
Thank you. We will allow until May 14, 2022 for users to update to the newer versions when using Rithmic. If you have any issues just let us know and we will help to the extent we can.
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
[2022-04-28 23:54:16]
User139065 - Posts: 10
So what is the technical reason for forcing everyone to upgrade to a higher version of SC and have to pay for a higher-priced package to even use the new method of connecting to Rithmic?
When the lower versions that use the Rithmic bridge connection still work just fine with no issues.
Date Time Of Last Edit: 2022-04-29 00:09:33
[2022-04-29 19:36:11]
Https://tradingbalance.co.uk - Posts: 44
Ok guys I have been running Rithmic trading into 9 accounts and have had major issues when submitting OCO orders.
I have also suffered from slow DOM and price feed issues.

Finally a lot of issues have now been resolved and I would recommend allowing OpenGL and disabling the trade activity message log that I have been told you must do every day. Sierra chart now has me blushing its lightening quick!!!!! As good as any DOM I have ever used and I have used a lot including TT for 15 years.

Good luck
[2022-04-30 12:04:01]
Mayuri - Posts: 4
Hi,

Since i update SC, it is no more loading intraday data (see image).

Here is my log :

HTTPS connection ID:1 to www.rithmic.com:443 for request ID:1 (4) | Creating socket. Using TLS 1.2. | 2022-04-30 07:56:33.895
HTTPS connection ID:1 to www.rithmic.com:443 for request ID:1 (4) | New receive buffer size: 32768 | 2022-04-30 07:56:33.895
HTTPS connection ID:1 to www.rithmic.com:443 for request ID:1 (4) | Connecting to IP: 38.79.0.89. | 2022-04-30 07:56:33.895
Reading Internal Order ID file. | 2022-04-30 07:56:33.957
Reading Trade Orders file. | 2022-04-30 07:56:34.021
Reading Trade Positions file. | 2022-04-30 07:56:34.022
Reading Trade Account Data files. | 2022-04-30 07:56:34.022
UDPListener (1552). Port 22904 | Listening on UDP port 22904. | 2022-04-30 07:56:34.037
Software version: 2383 64-bit | 2022-04-30 07:56:34.037
Primary Thread ID: 20980 | 2022-04-30 07:56:34.037
Usage end date: 2022-05-13 | 2022-04-30 07:56:34.037
Enabled for: Advanced Features 2. | 2022-04-30 07:56:34.037
Enabled for: Sierra Chart Historical Data Service. | 2022-04-30 07:56:34.037
Enabled for: Denali Real-Time Exchange Data Feed. | 2022-04-30 07:56:34.037
Enabled for: Delayed Denali Exchange Data Feed. | 2022-04-30 07:56:34.037
Enabled for exchange2: CME (Trading Account Required) | 2022-04-30 07:56:34.037
Enabled for exchange2: CBOT (Trading Account Required) | 2022-04-30 07:56:34.037
Enabled for exchange2: COMEX (Trading Account Required) | 2022-04-30 07:56:34.037
Enabled for exchange2: NYMEX (Trading Account Required) | 2022-04-30 07:56:34.037
Enabled for exchange2: fairx_exchange.data | 2022-04-30 07:56:34.037
Allow Support for Sierra Chart Data Feeds is enabled. | 2022-04-30 07:56:34.037
Current selected Data/Trading service: Rithmic Direct - DTC | 2022-04-30 07:56:34.037
Custom symbol settings values: enabled | 2022-04-30 07:56:34.037
Chart Update Interval: 1000 | 2022-04-30 07:56:34.037
Intraday Data Storage Time Unit: 0 | 2022-04-30 07:56:34.037
Time Zone: -04:00:00 (EST-05EDT+01,M3.2.0/02:00,M11.1.0/02:00) | 2022-04-30 07:56:34.037
2022-04-30 11:56:34 Local computer time in UTC | 2022-04-30 07:56:34.037
2022-04-30 07:56:34 Local computer time in SC Time Zone | 2022-04-30 07:56:34.037
2022-04-30 11:56:44 Server time in UTC | 2022-04-30 07:56:34.037
Local computer UTC time and Server UTC time difference: 11 seconds. | 2022-04-30 07:56:34.037
Notice: Your computer's clock is off by 11 seconds. For help with this, press the 'Send for Analysis' button. | 2022-04-30 07:56:34.037
Program path: C:\SierraChart2\ | 2022-04-30 07:56:34.037
Data Files path: C:\SierraChart2\Data\ | 2022-04-30 07:56:34.037
OS Version Number: 10.0 | 2022-04-30 07:56:34.037
Locale Setting: C | 2022-04-30 07:56:34.037
DLLs: UserContributedStudies_64.dll | 2022-04-30 07:56:34.038
Allowed protected custom studies: zyp_app | 2022-04-30 07:56:34.038
Crash reporter started: true | 2022-04-30 07:56:34.038

Checking for new symbol settings. Requested symbol settings MD5 for service code rithmic_v2.trading. Request ID: 1. | 2022-04-30 07:56:34.038
HTTPS connection ID:1 to login.sierrachart.com:443 for request ID:1 (1) | Shutdown started. Waiting for graceful close. | 2022-04-30 07:56:34.065
HTTPS connection ID:1 to login.sierrachart.com:443 for request ID:1 (1) | Socket gracefully closed by remote side. | 2022-04-30 07:56:34.108
HTTPS connection ID:1 to login.sierrachart.com:443 for request ID:1 (1) | Closed. | 2022-04-30 07:56:34.108
Received 5 login tokens. | 2022-04-30 07:56:34.177
HTTPS connection ID:1 to www.rithmic.com:443 for request ID:1 (4) | Socket gracefully closed by remote side. | 2022-04-30 07:56:34.419
HTTPS connection ID:1 to www.rithmic.com:443 for request ID:1 (4) | CloseSocket call. | 2022-04-30 07:56:34.420
HTTPS connection ID:1 to www.rithmic.com:443 for request ID:1 (4) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2022-04-30 07:56:34.420
HTTPS connection ID:1 to www.rithmic.com:443 for request ID:1 (4) | Closed. | 2022-04-30 07:56:34.420
Symbol settings MD5 received. Request ID: 1. | 2022-04-30 07:56:35.355
Symbol settings are up-to-date for rithmic_v2.trading. | 2022-04-30 07:56:35.356

Rithmic Direct - DTC | Using server connection: Rithmic Paper Trading-Chicago Area-Non-Aggregated | 2022-04-30 07:56:40.290
Rithmic Direct - DTC | Connecting to the server rsc.rithmic.com. Port 50500 | 2022-04-30 07:56:40.291
DTC Client socket (1) | Creating socket. Using TLS 1.2. | 2022-04-30 07:56:40.292
DTC Client socket (1) | New receive buffer size: 5242880 | 2022-04-30 07:56:40.292
DTC Client socket (1) | Connecting to IP: 216.57.156.163. | 2022-04-30 07:56:40.292
Rithmic Direct - DTC | Network connection to server complete. | 2022-04-30 07:56:40.389
Rithmic Direct - DTC | Starting socket receive thread. | 2022-04-30 07:56:40.389
Rithmic Direct - DTC | Setting DTC encoding to Binary | 2022-04-30 07:56:40.389
Rithmic Direct - DTC | Sending logon request message. | 2022-04-30 07:56:40.389
Rithmic Direct - DTC | Received logon response. | 2022-04-30 07:56:40.690
Rithmic Direct - DTC | Server Name: . | 2022-04-30 07:56:40.690
Rithmic Direct - DTC | Server protocol version: 8. Client protocol version: 8 | 2022-04-30 07:56:40.690
Rithmic Direct - DTC | Successfully connected. | 2022-04-30 07:56:40.690
Rithmic Direct - DTC | Trading is supported. | 2022-04-30 07:56:40.690
Rithmic Direct - DTC | Order cancel and replace is supported. | 2022-04-30 07:56:40.690
Rithmic Direct - DTC | OCO Orders supported. | 2022-04-30 07:56:40.690
Rithmic Direct - DTC | Symbol and Exchange Delimiter: . | 2022-04-30 07:56:40.690
Rithmic Direct - DTC | Connected to server complete. | 2022-04-30 07:56:40.690
Triggering next historical data download in queue. | 2022-04-30 07:56:40.691
Triggering next historical data download in queue. | 2022-04-30 07:56:40.691
Triggering next historical data download in queue. | 2022-04-30 07:56:40.691
Triggering next historical data download in queue. | 2022-04-30 07:56:40.691
Notice: Not connected to Live trading account to receive CME realtime futures data at non-professional fees. | 2022-04-30 07:56:40.719
No download requests in the queue to start downloads for. | 2022-04-30 07:56:40.719
No download requests in the queue to start downloads for. | 2022-04-30 07:56:40.719
No download requests in the queue to start downloads for. | 2022-04-30 07:56:40.719
No download requests in the queue to start downloads for. | 2022-04-30 07:56:40.719
HTTPS connection ID:2 to www.rithmic.com:443 for request ID:2 (2) | Creating socket. Using TLS 1.2. | 2022-04-30 07:57:10.302
HTTPS connection ID:2 to www.rithmic.com:443 for request ID:2 (2) | New receive buffer size: 32768 | 2022-04-30 07:57:10.302
HTTPS connection ID:2 to www.rithmic.com:443 for request ID:2 (2) | Connecting to IP: 38.79.0.89. | 2022-04-30 07:57:10.302
HTTPS connection ID:2 to www.rithmic.com:443 for request ID:2 (2) | Socket gracefully closed by remote side. | 2022-04-30 07:57:10.774
HTTPS connection ID:2 to www.rithmic.com:443 for request ID:2 (2) | CloseSocket call. | 2022-04-30 07:57:10.775
HTTPS connection ID:2 to www.rithmic.com:443 for request ID:2 (2) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2022-04-30 07:57:10.775
HTTPS connection ID:2 to www.rithmic.com:443 for request ID:2 (2) | Closed. | 2022-04-30 07:57:10.775
Loading DLL: C:\SierraChart2\Data\UserContributedStudies.dll (UserContributedStudies_64.dll). Handle: 7ffeb1560000 | 2022-04-30 07:57:31.291
RTYM2.CME [CB] Daily #1 | Reloading chart. | 2022-04-30 07:57:31.299
RTYM2.CME [CB] Daily #1 | Limiting the number of years to 5 years to load data for the continuous futures chart. Reason: Single-digit year in symbol. | 2022-04-30 07:57:31.299
RTYM2.CME [CB] Daily #1 | Limiting the number of years to download historical data to 5 years for the continuous futures chart. Reason: Single-digit year in symbol. | 2022-04-30 07:57:31.299
RTYM2.CME [CB] Daily #1 | Performing continuous chart historical Daily data download for symbol RTYM2.CME starting at last date in file. | 2022-04-30 07:57:31.321
Starting DelayedDownloadMonitoringTimer | 2022-04-30 07:57:31.321
Starting HDTimeoutTimer | 2022-04-30 07:57:31.321
Added historical Daily data request for RTYM2.CME to the queue. | 2022-04-30 07:57:31.321
Triggering next historical data download in queue. | 2022-04-30 07:57:31.321
RTYM2.CME [CB] Daily #1 | Waiting for historical downloads to complete with the IDs: 1, | 2022-04-30 07:57:31.603
RTYM2.CME [CB] 6000 Volume #2 | Reloading chart. | 2022-04-30 07:57:31.616
Starting DelayedDownloadMonitoringTimer | 2022-04-30 07:57:31.618
Starting HDTimeoutTimer | 2022-04-30 07:57:31.618
Added historical Intraday data request for RTYH2.CME to the queue. | 2022-04-30 07:57:31.618
Triggering next historical data download in queue. | 2022-04-30 07:57:31.618
Added historical Intraday data request for RTYM2.CME to the queue. | 2022-04-30 07:57:31.619
RTYM2.CME [CB] 6000 Volume #2 | Waiting for historical downloads to complete with the IDs: 1, 2, 3, | 2022-04-30 07:57:31.658
RTYM2.CME [CBV] 3000 Volume #3 | Reloading chart. | 2022-04-30 07:57:31.664
RTYM2.CME [CBV] 3000 Volume #3 | Waiting for historical downloads to complete with the IDs: 1, 2, 3, | 2022-04-30 07:57:31.689
RTYM2.CME [CBV] 1600 Volume #4 | Reloading chart. | 2022-04-30 07:57:31.695
RTYM2.CME [CBV] 1600 Volume #4 | Waiting for historical downloads to complete with the IDs: 1, 3, | 2022-04-30 07:57:31.704
RTYM2.CME [CBV] #5 | Reloading chart. | 2022-04-30 07:57:31.710
RTYM2.CME [CBV] #5 | Waiting for historical downloads to complete with the IDs: 1, 2, 3, | 2022-04-30 07:57:31.735
RTYM2.CME [CBV] #6 | Reloading chart. | 2022-04-30 07:57:31.741
RTYM2.CME [CBV] #6 | Waiting for historical downloads to complete with the IDs: 1, 3, | 2022-04-30 07:57:31.750
RTYM2.CME/M2KM2.CME 800 Volume #7 | Reloading chart. | 2022-04-30 07:57:31.760
RTYM2.CME/M2KM2.CME 5 Min #8 | Reloading chart. | 2022-04-30 07:57:31.770
RTYM2.CME/M2KM2.CME 1.6 Range #9 | Reloading chart. | 2022-04-30 07:57:31.780
Using symbol data fast lookup vector | 2022-04-30 07:57:31.808
HD Request # 1 | Downloading Historical Daily chart data for RTYM2.CME. Starting date: 2022-04-27. Service: rithmic.trading | 2022-04-30 07:57:31.809
HD Request # 2 | Downloading Intraday chart data for RTYH2.CME to the file RTYH2.CME.scid. Service: rithmic.trading | 2022-04-30 07:57:31.809
HD Request # 2 | Download start date-time: 2021-11-23 19:00:00.000000. File last date-time: 00:00:00.000000 | 2022-04-30 07:57:31.810
HD Request # 2 | Using server: rsc.rithmic.com port 50502. Use encryption. | 2022-04-30 07:57:31.810
Socket (3) | Creating socket. Using TLS 1.2. | 2022-04-30 07:57:31.810
Socket (3) | New receive buffer size: 5242880 | 2022-04-30 07:57:31.810
Socket (3) | Connecting to IP: 216.57.156.163. | 2022-04-30 07:57:31.810
RTYM2.CME/M2KM2.CME 800 Volume #7 | Currently no data in file to display. Will start historical data download and real-time updates. File: C:\SierraChart2\Data\RTYM2.CME.scid | 2022-04-30 07:57:31.811
RTYM2.CME/M2KM2.CME 5 Min #8 | Currently no data in file to display. Will start historical data download and real-time updates. File: C:\SierraChart2\Data\RTYM2.CME.scid | 2022-04-30 07:57:31.814
RTYM2.CME/M2KM2.CME 1.6 Range #9 | Currently no data in file to display. Will start historical data download and real-time updates. File: C:\SierraChart2\Data\RTYM2.CME.scid | 2022-04-30 07:57:31.817
HD Request # 2 | Sending historical data logon request message. | 2022-04-30 07:57:31.906
Rithmic Direct - DTC | Starting real-time market data updates for: RTYM2.CME. ID: 1 Service code: rithmic.trading | 2022-04-30 07:57:31.937
Rithmic Direct - DTC | Connecting to the server rsc.rithmic.com. Port 50501 | 2022-04-30 07:57:31.937
Rithmic Direct - DTC | Requesting security definition data for: RTYM2.CME. ID: 1 | 2022-04-30 07:57:31.937
Rithmic Direct - DTC | Starting real-time market data updates for: M2KM2.CME. ID: 3 Service code: rithmic.trading | 2022-04-30 07:57:31.937
Rithmic Direct - DTC | Requesting security definition data for: M2KM2.CME. ID: 3 | 2022-04-30 07:57:31.937
DTC Client socket (4) | Creating socket. Using TLS 1.2. | 2022-04-30 07:57:31.937
DTC Client socket (4) | New receive buffer size: 5242880 | 2022-04-30 07:57:31.938
DTC Client socket (4) | Connecting to IP: 216.57.156.163. | 2022-04-30 07:57:31.938
Rithmic Direct - DTC | Network connection to server complete. | 2022-04-30 07:57:32.035
Rithmic Direct - DTC | Starting socket receive thread. | 2022-04-30 07:57:32.035
Rithmic Direct - DTC | Setting DTC encoding to Binary | 2022-04-30 07:57:32.035
Rithmic Direct - DTC | Sending logon request message. | 2022-04-30 07:57:32.035
HD Request # 1 | Requesting historical Daily data for QRM22 starting at 2022-04-26. SC External HD service. | 2022-04-30 07:57:32.057
HD Request # 2 | Requesting Intraday data. Start date-time: 2021-11-23 19:00:00. Record interval: 0. Symbol: RTYH2.CME | 2022-04-30 07:57:32.204
Socket (3) | CloseSocket call. | 2022-04-30 07:57:32.303
Socket (3) | Shutdown started. Waiting for graceful close. | 2022-04-30 07:57:32.303
HD Request # 2 | Error downloading historical Intraday data for RTYH2.CME. unknown request | 2022-04-30 07:57:32.303
Historical data download thread signaled to stop. | 2022-04-30 07:57:32.303
HD Request # 2 | Received 0 Intraday data records from 00:00:00.000000 to 00:00:00.000000 (0.0 seconds) and wrote 0 records for RTYH2.CME | 2022-04-30 07:57:32.303
HD Request # 2 | Add time&sales data | Remembered last file record date-time: 00:00:00.000000 | 2022-04-30 07:57:32.304
HD Request # 2 | Completion time: 1s | 2022-04-30 07:57:32.304
HD Request # 2 | Intraday data download complete for RTYH2.CME. Unique request ID: 2 | 2022-04-30 07:57:32.304
Removing historical data download ID 2. | 2022-04-30 07:57:32.304
Real-time Intraday chart data file updates started for RTYH2.CME | 2022-04-30 07:57:32.304
Intraday chart data file opened for RTYH2.CME | 2022-04-30 07:57:32.304
HD Request # 2 | Enabling Intraday chart updating for symbol. | 2022-04-30 07:57:32.304

Triggering next historical data download in queue. | 2022-04-30 07:57:32.304
Delaying start of download for RTYM2.CME | 2022-04-30 07:57:32.304
Rithmic Direct - DTC | Received logon response. | 2022-04-30 07:57:32.332
Rithmic Direct - DTC | Server Name: . | 2022-04-30 07:57:32.332
Rithmic Direct - DTC | Server protocol version: 8. Client protocol version: 8 | 2022-04-30 07:57:32.332
Rithmic Direct - DTC | Successfully connected. | 2022-04-30 07:57:32.332
Rithmic Direct - DTC | Trading is not supported. | 2022-04-30 07:57:32.332
Rithmic Direct - DTC | Symbol and Exchange Delimiter: . | 2022-04-30 07:57:32.332
Rithmic Direct - DTC (Data) | Restarting real-time data updates for symbol: M2KM2.CME | 2022-04-30 07:57:32.332
Rithmic Direct - DTC (Data) | Restarting real-time data updates for symbol: RTYM2.CME | 2022-04-30 07:57:32.332
Socket (3) | Socket gracefully closed by remote side. | 2022-04-30 07:57:32.399
Socket (3) | Closed. | 2022-04-30 07:57:32.400
HD Request # 1 | Receiving historical Daily data for RTYM2.CME starting at 2022-04-27 | 2022-04-30 07:57:32.409
HD Request # 1 | Writing historical Daily data to the file RTYM2.CME.dly | 2022-04-30 07:57:32.409
HD Request # 1 | Bytes received: 231 | 2022-04-30 07:57:32.412
HD Request # 1 | Received 4 Daily data records from 2022-04-27 00:00:00 to 2022-04-29 00:00:00 (3.0 days) and wrote 3 records for RTYM2.CME | 2022-04-30 07:57:32.412
HD Request # 1 | Completion time: 1s | 2022-04-30 07:57:32.412
HD Request # 1 | Daily data download complete for RTYM2.CME. Unique request ID: 1 | 2022-04-30 07:57:32.412
Removing historical data download ID 1. | 2022-04-30 07:57:32.412

Triggering next historical data download in queue. | 2022-04-30 07:57:32.412
No download requests in the queue to start downloads for. | 2022-04-30 07:57:32.412
Rithmic Direct - DTC (Data) | Received security definition for symbol M2KM2.CME | 2022-04-30 07:57:32.433
Rithmic Direct - DTC (Data) | Received security definition for symbol RTYM2.CME | 2022-04-30 07:57:32.433
RTYM2.CME [CB] Daily #1 | Download is complete for all contract months in chart. Proceeding with data load. | 2022-04-30 07:57:33.318
RTYM2.CME [CB] Daily #1 | Reloading chart. | 2022-04-30 07:57:33.319
RTYM2.CME [CB] Daily #1 | Reloading chart. | 2022-04-30 07:57:34.335
RTYM2.CME [CB] Daily #1 | Limiting the number of years to 5 years to load data for the continuous futures chart. Reason: Single-digit year in symbol. | 2022-04-30 07:57:34.335
RTYM2.CME [CB] Daily #1 | Limiting the number of years to download historical data to 5 years for the continuous futures chart. Reason: Single-digit year in symbol. | 2022-04-30 07:57:34.335
HD Request # 3 | Downloading Intraday chart data for RTYM2.CME to the file RTYM2.CME.scid. Service: rithmic.trading | 2022-04-30 07:57:37.654
HD Request # 3 | Download start date-time: 2022-02-22 19:00:00.000000. File last date-time: 00:00:00.000000 | 2022-04-30 07:57:37.654
HD Request # 3 | Using server: rsc.rithmic.com port 50502. Use encryption. | 2022-04-30 07:57:37.655
Socket (2) | Creating socket. Using TLS 1.2. | 2022-04-30 07:57:37.655
Socket (2) | New receive buffer size: 5242880 | 2022-04-30 07:57:37.655
Socket (2) | Connecting to IP: 216.57.156.163. | 2022-04-30 07:57:37.655
HD Request # 3 | Sending historical data logon request message. | 2022-04-30 07:57:37.752
HD Request # 3 | Requesting Intraday data. Start date-time: 2022-02-22 19:00:00. Record interval: 0. Symbol: RTYM2.CME | 2022-04-30 07:57:38.049
Socket (2) | CloseSocket call. | 2022-04-30 07:57:38.147
HD Request # 3 | Error downloading historical Intraday data for RTYM2.CME. unknown request | 2022-04-30 07:57:38.147
Socket (2) | Shutdown started. Waiting for graceful close. | 2022-04-30 07:57:38.147
Historical data download thread signaled to stop. | 2022-04-30 07:57:38.147
HD Request # 3 | Received 0 Intraday data records from 00:00:00.000000 to 00:00:00.000000 (0.0 seconds) and wrote 0 records for RTYM2.CME | 2022-04-30 07:57:38.147
HD Request # 3 | Add time&sales data | Remembered last file record date-time: 00:00:00.000000 | 2022-04-30 07:57:38.147
HD Request # 3 | Completion time: 1s | 2022-04-30 07:57:38.147
HD Request # 3 | Intraday data download complete for RTYM2.CME. Unique request ID: 3 | 2022-04-30 07:57:38.147
Removing historical data download ID 3. | 2022-04-30 07:57:38.147
Real-time Intraday chart data file updates started for RTYM2.CME | 2022-04-30 07:57:38.147
Intraday chart data file opened for RTYM2.CME | 2022-04-30 07:57:38.147
HD Request # 3 | Enabling Intraday chart updating for symbol. | 2022-04-30 07:57:38.147

Triggering next historical data download in queue. | 2022-04-30 07:57:38.147
No download requests in the queue to start downloads for. | 2022-04-30 07:57:38.147
Socket (2) | Socket gracefully closed by remote side. | 2022-04-30 07:57:38.244
Socket (2) | Closed. | 2022-04-30 07:57:38.244
RTYM2.CME [CB] 6000 Volume #2 | Download is complete for all contract months in chart. Proceeding with data load. | 2022-04-30 07:57:38.655
RTYM2.CME [CB] 6000 Volume #2 | Reloading chart. | 2022-04-30 07:57:38.655
RTYM2.CME [CB] 6000 Volume #2 | Currently no data in file to display. Will start historical data download and real-time updates. File: C:\SierraChart2\Data\RTYM2.CME.scid | 2022-04-30 07:57:38.680
RTYM2.CME [CBV] 3000 Volume #3 | Download is complete for all contract months in chart. Proceeding with data load. | 2022-04-30 07:57:38.681
RTYM2.CME [CBV] 3000 Volume #3 | Reloading chart. | 2022-04-30 07:57:38.681
RTYM2.CME [CBV] 3000 Volume #3 | Currently no data in file to display. Will start historical data download and real-time updates. File: C:\SierraChart2\Data\RTYM2.CME.scid | 2022-04-30 07:57:38.699
RTYM2.CME [CBV] 1600 Volume #4 | Download is complete for all contract months in chart. Proceeding with data load. | 2022-04-30 07:57:38.728
RTYM2.CME [CBV] 1600 Volume #4 | Reloading chart. | 2022-04-30 07:57:38.729
RTYM2.CME [CBV] #5 | Download is complete for all contract months in chart. Proceeding with data load. | 2022-04-30 07:57:38.732
RTYM2.CME [CBV] #5 | Reloading chart. | 2022-04-30 07:57:38.732
RTYM2.CME [CBV] 1600 Volume #4 | Currently no data in file to display. Will start historical data download and real-time updates. File: C:\SierraChart2\Data\RTYM2.CME.scid | 2022-04-30 07:57:38.749
RTYM2.CME [CBV] #5 | Currently no data in file to display. Will start historical data download and real-time updates. File: C:\SierraChart2\Data\RTYM2.CME.scid | 2022-04-30 07:57:38.751
RTYM2.CME [CBV] #6 | Download is complete for all contract months in chart. Proceeding with data load. | 2022-04-30 07:57:38.828
RTYM2.CME [CBV] #6 | Reloading chart. | 2022-04-30 07:57:38.829
RTYM2.CME [CBV] #6 | Currently no data in file to display. Will start historical data download and real-time updates. File: C:\SierraChart2\Data\RTYM2.CME.scid | 2022-04-30 07:57:38.832
RTYM2.CME [CB] 6000 Volume #2 | Reloading chart. | 2022-04-30 07:57:39.672
RTYM2.CME [CB] 6000 Volume #2 | Currently no data in file to display. Will start historical data download and real-time updates. File: C:\SierraChart2\Data\RTYM2.CME.scid | 2022-04-30 07:57:39.735
RTYM2.CME [CBV] 3000 Volume #3 | Reloading chart. | 2022-04-30 07:57:39.737
RTYM2.CME [CBV] 3000 Volume #3 | Currently no data in file to display. Will start historical data download and real-time updates. File: C:\SierraChart2\Data\RTYM2.CME.scid | 2022-04-30 07:57:39.778
RTYM2.CME [CBV] #5 | Reloading chart. | 2022-04-30 07:57:39.780
RTYM2.CME [CBV] #5 | Currently no data in file to display. Will start historical data download and real-time updates. File: C:\SierraChart2\Data\RTYM2.CME.scid | 2022-04-30 07:57:39.820
RTYM2.CME [CBV] 1600 Volume #4 | Reloading chart. | 2022-04-30 07:57:39.822
RTYM2.CME [CBV] 1600 Volume #4 | Currently no data in file to display. Will start historical data download and real-time updates. File: C:\SierraChart2\Data\RTYM2.CME.scid | 2022-04-30 07:57:39.834
RTYM2.CME [CBV] #6 | Reloading chart. | 2022-04-30 07:57:39.836
RTYM2.CME [CBV] #6 | Currently no data in file to display. Will start historical data download and real-time updates. File: C:\SierraChart2\Data\RTYM2.CME.scid | 2022-04-30 07:57:39.847
The message log has been sent to support. | 2022-04-30 07:59:51.949 *
HTTPS connection ID:1 to www.sierrachart.com:443 for request ID:1 (2) | Creating socket. Using TLS 1.2. | 2022-04-30 07:59:51.949
HTTPS connection ID:1 to www.sierrachart.com:443 for request ID:1 (2) | New receive buffer size: 32768 | 2022-04-30 07:59:51.949
HTTPS connection ID:1 to www.sierrachart.com:443 for request ID:1 (2) | Connecting to IP: 95.216.233.104. | 2022-04-30 07:59:51.949
HTTPS connection ID:1 to www.sierrachart.com:443 for request ID:1 (2) | Socket gracefully closed by remote side. | 2022-04-30 07:59:57.172
HTTPS connection ID:1 to www.sierrachart.com:443 for request ID:1 (2) | CloseSocket call. | 2022-04-30 07:59:57.172
HTTPS connection ID:1 to www.sierrachart.com:443 for request ID:1 (2) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2022-04-30 07:59:57.172
HTTPS connection ID:1 to www.sierrachart.com:443 for request ID:1 (2) | Closed. | 2022-04-30 07:59:57.172
Sending of the Message Log is completed. The response was saved to C:\SierraChart2\Data\MessageLogAnalysis.htm | 2022-04-30 08:00:09.569
attachmentChartImage.bmp - Attached On 2022-04-30 12:01:32 UTC - Size: 3.83 MB - 50 views
[2022-04-30 14:44:01]
User701453 - Posts: 175
@Mayuri,

Since the log was generated on 2022-04-30 which is a weekend day.
Rithmic servers are down on the weekends.

To get Friday's data or previous days' data (historical data).
It appears that you will be now forced to pay extra for SC Denali Exchange Data Feed and must now also pay extra exchange fees for data when using Rithmic.

Rithmic Trading Platform Service

Even if you are just using a Prop firm(Earntotrade,Leeloo, Uprofit, Apex) to take an eval.
Which is crazy because the Rithmic data is free with the Prop firm eval subscription.
[2022-04-30 19:27:18]
Predicate - Posts: 8
I suspect most of these problems are now due to misconfiguration in SC, including people who are trying to still use some old R+ API Plug-In version. However, I do not execute or manage trades at all within SC. I only use it for charting, so my experience is largely tied to the live streaming data and the backfill. Both are working just fine for me right now. Make sure you have DC Data disabled and set the maximum backfill to something reasonable. If you're just populating intraday numbers bars (footprints) you could reasonably clamp your backfill to just the prior session or overnight inventory. I know there used to be a note about this on the forums for Rithmic suggesting 5 days. For footprints you can clamp that further. For TPO charts I doubt most people will need more than two weeks to initially seed their chart.

I had meant to contact SC about this so they could know, but I've been too busy lately with a grandparent nearly dying in January and spending a month in the ICU. All due to their surgeries being cancelled in 2020 thanks to covid restrictions. I'm livid even typing this part up because they had an early Wuhan strain and only had mild bronchitis, only to end up almost dying to protect overweight diabetics who are at high risk with any respiratory illness. That comorbidity isn't unique to covid. But, that's neither here nor there.

I'll reiterate what I said before; After some strongly worded language I got Rithmic to fix the DTC connection's historical backfill, so now Denali is unnecessary. When I was testing the fix, if I recall correctly, it took about 20 minutes to do 20 days of 1-Tick backfill on a chart that had three studies; TPO, VbP, and Current Price. Even for TPO charts you shouldn't be trying to backfill a ridiculous amount of 1-Tick data, so I considered this fine. However, Rithmic still wants to implement the compression that DTC supports to speed that up.
[2022-04-30 19:40:03]
Mayuri - Posts: 4
OK, i reconnect my live trading account on interactive brokers, which is my investment account.
The monthly subscription to benefit from reduced fees from CME.

Problem solve.
[2022-04-30 20:39:19]
User701453 - Posts: 175
@Predicate
I suspect most of these problems are now due to misconfiguration in SC, including people who are trying to still use some old R+ API Plug-
Completely 100% incorrect.

I still use the Rithmic bridge connection(old R+ API Plug) with SC version 2308 every single day with zero problems.
Even on those days when Prop firms cant connect with NT to Rithmic.
I can still connect with SC using the plugin and place trades with no issues.

I also agree with User139065, why is SC forcing everyone to upgrade to a more expensive version and have to pay extra data and exchange fees if there is no technical reason to do so.
Date Time Of Last Edit: 2022-05-01 12:25:55
[2022-05-01 19:40:57]
User93534 - Posts: 30
I am reading thru the update instructions and trying to make a concurrent install so I don't mess up my spreadsheets on a failed install (did this last time tried to update & had to revert,lost all formulas) and it says I need to update to package 10. My account just renewed package 5 for 6 months a few days ago.

Not sure how to do this other than paying the full 6 months again and hitting renew now, its asking me to pay again and I have 6 months available.

Also unsure what is the difference between package 10 & 11, I am reading thru the denali data and can't tell which is standard and regular, I have no idea what the difference between packages is other than the orderbook in the MBO package, which is why people use rithmic in the first place given the entire book. I am on SC v2204 and the last update attempt was an abortion. I am assuming I can run an install with denali then as well as rithmic?

Regardless, I am a bit lost here.
[2022-05-01 20:08:05]
Predicate - Posts: 8
I am reading thru the update instructions and trying to make a concurrent install so I don't mess up my spreadsheets on a failed install (did this last time tried to update & had to revert,lost all formulas) and it says I need to update to package 10. My account just renewed package 5 for 6 months a few days ago.

If that's true then we are going to need clarification from SC staff. I don't know why they would start forcing Denali packages after Rithmic finally fixed historical data on their end when using the DTC connection. That would leave a really sour taste having to pay for something no longer needed.
[2022-05-01 20:14:47]
User701453 - Posts: 175
I am reading thru the update instructions and trying to make a concurrent install so I don't mess up my spreadsheets on a failed install (did this last time tried to update & had to revert,lost all formulas)
There are two ways you can do this.
You can copy and paste your entire SC folder to a backup drive.
Then install the upgrade\update of SC to your current C:\SierraChart folder.

Or you can create a new folder on your C:\ and name the folder different than your current working copy of SC.
Then copy all the contents of your current working copy of SC into the newly named folder.
Startup SC by using SierraChart_64.exe from within the newly named folder.

Then go to help on the toolbar and download the current version of SC.
Install this current version into the newly named folder.
Once the installation is finished.

Right-click on SierraChart_64.exe, and create a new shortcut.
Rename the shortcut to whatever you want and copy it to your desktop.
Now you have two working copies of SC. Your original copy and the new install for testing.

I currently have multiple install of SC. Screen shot attached.

----

Sierra Chart Support Update:

For the official documentation on this kind of subject, refer to:
https://www.sierrachart.com/index.php?page=doc/helpdetails15.html
Date Time Of Last Edit: 2022-05-02 10:52:49
imagemulti-folders.PNG / V - Attached On 2022-05-01 20:16:52 UTC - Size: 3.84 KB - 44 views
[2022-05-01 20:27:18]
User701453 - Posts: 175
If that's true then we are going to need clarification from SC staff. I don't know why they would start forcing Denali packages after Rithmic finally fixed historical data on their end when using the DTC connection. That would leave a really sour taste having to pay for something no longer needed.

They shouldn't be forcing customers to upgrade at all to the DTC connection method if their customer's don't need the new DTC to connect to Rithmic.
The Rithmic bridge connection is still working just fine with the older SC version.
If there was a technical reason that the Rithmic bridge connection could not be used with older versions.
Such as Rithmic changed their connection strings or process.
That I would understand.
But to pull a Biden and say "if you don't upgrade, you can no longer work and feed yourself or your family".Is just wrong and 1984ish.
[2022-05-01 20:36:15]
User93534 - Posts: 30
Thanks guys but I learned the hard way from the last update attempt, I am trying to run it on a clean install and have saved my files.

Its not about price since package 5 & 10 cost the same, unless I am on the hook for more fees which I do not believe to be the case. The documentation on what is included on the different Denali packages is left wanting.

I don't actually care about any of this drama, I just want it to work. Should be an easy fix on SC's end to change the package--I will just purchase another 6 months if need be, I don't have time to worry about this.


edit:
I realize now the standard vs advanced is the software version so the denali is an extra $8/mo which is not a deal breaker but it is not the same situation w/the gain feed. I am already paying multiple exchange fees. Regardless the documentation is confusing and I am also now interested in the denali futures options data but no idea what is included with which package. Is it possible to pull options data from one chart and overlay onto futures contract?
Date Time Of Last Edit: 2022-05-01 21:07:08
[2022-05-02 10:21:33]
Sierra Chart Engineering - Posts: 103558
In regards to post #7:

Since i update SC, it is no more loading intraday data (see image).
Everything with your Sierra Chart account looks ok in regards to using the Denali Data Feed.

Follow the instructions here to clear the Message Log:
Message Log: Clearing the Message Log

Fully re-download the data in the chart by going to the chart and selecting "Edit >>Delete All Data and Download".

After about a minute provide a copy of the Message Log following these instructions:
https://www.sierrachart.com/index.php?page=PostingInformation.php#MessageLog

We will then determine what the problem is.
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
[2022-05-02 10:29:10]
Sierra Chart Engineering - Posts: 103558

I also agree with User139065, why is SC forcing everyone to upgrade to a more expensive version and have to pay extra data and exchange fees if there is no technical reason to do so.
This is not true.

There is no forced upgrade to an "expensive version". This is 100% false. There are some upcoming changes with our Service Packages regarding connectivity to external services:
https://www.sierrachart.com/SupportBoard.php?ThreadID=72282

However, these would apply whether you are using an older Sierra Chart version or a newer version. If you do have to use one of our higher packages like 10, 11 or 12, at $10 a month more before discount, that is hardly expensive. And you are not forced to pay Exchange fees. If Rithmic cannot provide proper data which they cannot in regards to historical data and sometimes issues with real-time data, then you need to use our Denali Data Feed by activating exchanges. Otherwise you can use Rithmic data. This is explained here:
Rithmic Trading Platform Service: Rithmic Market Data and Support Policy

And with inflation there is absolutely no price increase at all and our prices are very low to begin with. Expensive is a ridiculous comment.

What you are saying is simply false. It is postings like these which we should just simply be deleting. Instead of wasting time responding to them and we are now locking this thread because of the nonsense being posted here.

We are banning your account from the board. This is completely inappropriate and we are not going to tolerate this.


I don't know why they would start forcing Denali packages after Rithmic finally fixed historical data on their end when using the DTC connection.
This is not true. There is a requirement to use our higher packages( 10, 11, 12) which are inexpensive to connect to any external service, but you do not have to use the Denali Data Feed. But if you do use the Denali data feed you are going to have much better market data.

And there are only about 100 users, affected by this. Most of our Rithmic users are not using the older bridge program. And the users using the new DTC connection also have to update to a more recent version because we have corrected a Rithmic specific price formatting issue which affects some currency futures.
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-05-02 10:37:55
[2022-05-02 10:39:59]
Sierra Chart Engineering - Posts: 103558
If anyone has any questions about or needs help with updating Sierra Chart, or changing Service Packages or help with the Denali Data Feed (which you do not have to use, other than using a Service Package that has support for it), related to what is described in post #1, start a new thread.

And post from your current account by selecting Help >> Support Board from within Sierra Chart.
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-05-02 10:41:53
[2022-06-09 18:19:45]
Sierra_Chart Engineering - Posts: 2711
At this time users using Sierra Chart with Rithmic running version 2350 and earlier, now need to update to any version after that.

Later we will require an update to 2372 or 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

To post a message in this thread, you need to log in with your Sierra Chart account:

Login

Login Page - Create Account