Support Board
Date/Time: Sat, 23 Nov 2024 22:42:49 +0000
Cannot properly connect data in new account, endless cycle
View Count: 168
| [2024-07-17 06:07:20] |
| dyas447 - Posts: 2 |
|
I cannot successfully connect my data. It seemed to work the first time I was setting it up, to the best of my knowledge, however maybe it was not working then either but I did not have this exact issue. Subsequently, when I connect my data, the chart says “waiting to download historical data,” followed by “downloading historical data. Bars may not appear until done,” and then “historical download complete.” However, this keeps happening in a rapid and endless cycle, and never seems to actually complete. A message log similarly runs continually, quickly scrolling downward, but I cannot understand what it is saying even if it were paused. I sent a log for analysis just now but it says that will not be reviewed unless it was requested. I am using a Rithmic data feed. Although I am not completely certain that it ever properly worked with Sierra and I'm completely new to Sierra (I do think it worked the first time though), I know this data feed works in general, it is capable of providing historical data and have used it with 2 other platforms (not concurrently).Not sure how to proceed and would appreciate any help.
Date Time Of Last Edit: 2024-07-17 07:10:09
|
 bandicam 2024-07-16 23-06-14-247.jpg / V - Attached On 2024-07-17 06:06:53 UTC - Size: 1.71 MB - 41 views |
| [2024-07-17 12:46:09] |
| Sierra_Chart Engineering - Posts: 17154 |
|
The log you provided is too large. We want you to close all Chartbooks with File >> Close All Chartbooks and then: Follow the instructions here to clear the Message Log: Message Log: Clearing the Message Log Connect to the data feed: Select "File >> Disconnect" Select "File >> Connect to Data Feed" After about 30 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. 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 |
| [2024-07-17 16:48:57] |
| dyas447 - Posts: 2 |
|
It did not get into that cycle after following your instructions so I'm not sure if this reflects the problem but here you go: 2024-07-17 16:44:08.082 | Software version: 2655 64-bit 2024-07-17 16:44:08.082 | Primary Thread ID: 45032 2024-07-17 16:44:08.082 | Usage end date: 2024-08-12 2024-07-17 16:44:08.082 | Enabled for: Advanced Features 2. 2024-07-17 16:44:08.082 | Enabled for: Sierra Chart Historical Data Service. 2024-07-17 16:44:08.082 | Enabled for: Denali Real-Time Exchange Data Feed. 2024-07-17 16:44:08.082 | Enabled for: Delayed Denali Exchange Data Feed. 2024-07-17 16:44:08.082 | Allow Support for Sierra Chart Data Feeds is enabled. 2024-07-17 16:44:08.082 | Current selected Data/Trading service: Rithmic Direct - DTC 2024-07-17 16:44:08.082 | Custom symbol settings values: enabled 2024-07-17 16:44:08.082 | Chart Update Interval: 400 2024-07-17 16:44:08.082 | Intraday Data Storage Time Unit: 1 2024-07-17 16:44:08.082 | Time Zone: +00:00:00 (UTC+00) 2024-07-17 16:44:08.082 | 2024-07-17 16:44:08 Local computer time in UTC 2024-07-17 16:44:08.082 | 2024-07-17 16:44:08 Local computer time in SC Time Zone 2024-07-17 16:44:08.082 | 2024-07-16 08:40:49 Server time in UTC 2024-07-17 16:44:08.082 | Local computer UTC time and Server UTC time difference: 1 seconds. 2024-07-17 16:44:08.082 | Program path: C:\SierraChart\ 2024-07-17 16:44:08.082 | Data Files path: C:\SierraChart\Data\ 2024-07-17 16:44:08.082 | OS Version Number: 10.0 2024-07-17 16:44:08.082 | Locale Setting: C 2024-07-17 16:44:08.082 | DLLs: UserContributedStudies_64.dll 2024-07-17 16:44:08.082 | Allowed protected custom studies: 2024-07-17 16:44:08.082 | Crash reporter started: true 2024-07-17 16:44:08.082 | 2024-07-17 16:44:35.711 | 2024-07-17 16:44:35.711 | Rithmic Direct - DTC | Using server connection: Rithmic Paper Trading-Chicago Area-Non-Aggregated 2024-07-17 16:44:35.711 | Rithmic Direct - DTC | Trading server address/port: rsc.rithmic.com:50500 2024-07-17 16:44:35.711 | Rithmic Direct - DTC | Connecting to the server rsc.rithmic.com. Port 50500 2024-07-17 16:44:35.800 | DTC Client socket (1) | Creating socket. Using TLS 1.2. 2024-07-17 16:44:35.800 | DTC Client socket (1) | New receive buffer size: 0 2024-07-17 16:44:35.800 | DTC Client socket (1) | Connecting to IP: 216.57.156.163. 2024-07-17 16:44:35.891 | Rithmic Direct - DTC | Network connection to server complete. 2024-07-17 16:44:35.891 | Rithmic Direct - DTC | Starting socket receive thread. 2024-07-17 16:44:35.891 | Rithmic Direct - DTC | Setting DTC encoding to Binary 2024-07-17 16:44:35.891 | Rithmic Direct - DTC | Sending logon request message. 2024-07-17 16:44:36.171 | Rithmic Direct - DTC | Received logon response. 2024-07-17 16:44:36.171 | Rithmic Direct - DTC | Server Name: . 2024-07-17 16:44:36.171 | Rithmic Direct - DTC | Server protocol version: 8. Client protocol version: 8 2024-07-17 16:44:36.171 | Rithmic Direct - DTC | Successfully connected. 2024-07-17 16:44:36.171 | Rithmic Direct - DTC | Trading is supported. 2024-07-17 16:44:36.171 | Rithmic Direct - DTC | Order cancel and replace is supported. 2024-07-17 16:44:36.171 | Rithmic Direct - DTC | OCO Orders supported. 2024-07-17 16:44:36.171 | Rithmic Direct - DTC | Symbol and Exchange Delimiter: . 2024-07-17 16:44:36.171 | Rithmic Direct - DTC | MarketDepthIsSupported: 0 2024-07-17 16:44:36.171 | Rithmic Direct - DTC | Connected to server complete. 2024-07-17 16:44:36.171 | No download requests in the queue to start downloads for. | Number times message added: 3 2024-07-17 16:44:36.171 | Notice: Not connected to Live trading account to receive CME realtime futures data at non-professional fees. 2024-07-17 16:44:55.836 | HTTPS connection ID:15 to downloads.rithmic.com:443 for request ID:15 (2) | Creating socket. Using TLS 1.2. 2024-07-17 16:44:55.836 | HTTPS connection ID:15 to downloads.rithmic.com:443 for request ID:15 (2) | New receive buffer size: 0 2024-07-17 16:44:55.836 | HTTPS connection ID:15 to downloads.rithmic.com:443 for request ID:15 (2) | Connecting to IP: 216.66.0.130. 2024-07-17 16:44:56.658 | HTTPS connection ID:15 to downloads.rithmic.com:443 for request ID:15 (2) | CloseSocket call. 2024-07-17 16:44:56.659 | HTTPS connection ID:15 to downloads.rithmic.com:443 for request ID:15 (2) | Shutdown started. Waiting for graceful close. 2024-07-17 16:44:56.751 | HTTPS connection ID:15 to downloads.rithmic.com:443 for request ID:15 (2) | Socket gracefully closed by remote side. 2024-07-17 16:44:56.751 | HTTPS connection ID:15 to downloads.rithmic.com:443 for request ID:15 (2) | Closed. 2024-07-17 16:45:26.591 | The message log has been sent to support. * 2024-07-17 16:45:26.596 | HTTPS connection ID:2 to www.sierrachart.com:443 for request ID:2 (2) | Creating socket. Using TLS 1.2. 2024-07-17 16:45:26.596 | HTTPS connection ID:2 to www.sierrachart.com:443 for request ID:2 (2) | New receive buffer size: 0 2024-07-17 16:45:26.596 | HTTPS connection ID:2 to www.sierrachart.com:443 for request ID:2 (2) | Connecting to IP: 64.158.105.204. 2024-07-17 16:45:26.925 | The Message Log was sent. Result: Message Log received. * 2024-07-17 16:45:27.182 | HTTPS connection ID:2 to www.sierrachart.com:443 for request ID:2 (2) | CloseSocket call. 2024-07-17 16:45:27.182 | HTTPS connection ID:2 to www.sierrachart.com:443 for request ID:2 (2) | Shutdown started. Waiting for graceful close. 2024-07-17 16:45:27.253 | HTTPS connection ID:2 to www.sierrachart.com:443 for request ID:2 (2) | Socket gracefully closed by remote side. 2024-07-17 16:45:27.253 | HTTPS connection ID:2 to www.sierrachart.com:443 for request ID:2 (2) | Closed. |
| [2024-07-17 17:19:30] |
| John - SC Support - Posts: 36238 |
|
The particular pattern you are referencing usually means that you have a symbol somewhere in your chartbooks that Rithmic does not like. For example, from one of your logs, we see the symbol "ESU24-CME". This is not a Rithmic symbol. Open your Chartbooks and select "Edit >> Translate Symbols to Current Service". Refer to the following: Edit Menu: Edit >> Translate Symbols To Current Service If you continue to have the problem, then use the documentation at the following link to go through all the places that symbols could be entered and either remove, or update them to what Rithmic needs. The following documentation is for cleaning up old symbols, but the basics still apply: Chart Data and Chart Data Files: Cleaning Up Old and Unused Symbols for Efficiency Note that there are also other issues with Rithmic connectivity right now, so if you go through all of this and still have issues, then you could also have a general issue with Rithmic. Refer to the following on this: Notice: Internet Connectivity Issues for Some Users Affecting Rithmic/Denali Data 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: