Support Board
Date/Time: Tue, 26 Nov 2024 06:33:47 +0000
Rithmic Download Loop
View Count: 269
| [2023-12-22 18:10:33] |
| User1293821 - Posts: 42 |
|
To preface Denali fixes this and should be the preferred provider for market data when using Sierra Chart, but I have done testing the best to my knowledge and I think a problem could be on Sierra's side. The issue seems to be with the Sierra4.config file. If I use my custom Sierra4.config file I get constant disconnect/reconnect for Topstep Rithmic when not using denali data. The error message prints to the log if I do not have open any chartbooks, custom quotes, etc. If I delete my custom Sierra4.config and force sierra to download a fresh one the constant disconnect/reconnect goes away. I make sure to set the datafeed back to Topstep Rithmic and disable the "Allow support for sierra data feeds" for testing purposes. I would hate to have to rebuild my custom Sierra4.config file from scratch if there was some sort of corruption. I could be missing a specific setting to fix the problem, but I tried for a couple hours flipping settings and had no success. I have attached two full message logs. One with my custom Sierra4.config and the other with a fresh Sierra4.config. The lines that seem to be the problem are "Rithmic Direct - DTC (Data) | Restarting real-time data updates for symbol: | 2023-12-22 11:38:42.489 DTC Client socket (2) | Socket gracefully closed by remote side. | 2023-12-22 11:38:42.511 DTC Client socket (2) | CloseSocket call. | 2023-12-22 11:38:42.511" The symbol for "Restarting real-time data updates for symbol" shows blank above, but in my text editor is a weird SX symbol. Thanks for the help. I use denali personally and with no issues, and push others to do the same, but this rithmic issue has been a problem for the last couple of months. Thanks again for the help! |
 Screenshot 2023-12-22 at 13.04.28.png / V - Attached On 2023-12-22 18:04:35 UTC - Size: 34.7 KB - 59 views Private File Private File |
| [2023-12-22 18:39:11] |
| Sierra_Chart Engineering - Posts: 17179 |
|
That symbol must exist somewhere. Remove it: Chart Data and Chart Data Files: Cleaning Up Old and Unused Symbols for Efficiency And the core problem is that Rithmic is closing the connection due to it. Sierra Chart has no control over either of these. The problem is on your side, and with Rithmic. 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: 2023-12-22 18:39:41
|
| [2023-12-22 18:43:07] |
| Sierra_Chart Engineering - Posts: 17179 |
|
The log actually shows the origin of that symbol: Subscribing to symbol for symbol alert. | 2023-12-22 12:06:39.078 Number 5 here shows how to clean that up: Chart Data and Chart Data Files: Cleaning Up Old and Unused Symbols for Efficiency 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: 2023-12-22 18:44:11
|
| [2023-12-22 18:51:01] |
| User1293821 - Posts: 42 |
|
Yup that did the trick. Thank you for the swift reply.
|
| [2023-12-22 19:12:46] |
| HeyUgly - Posts: 247 |
|
I just went through this all yesterday and into today Ive been able to re-create a problem" IF you have a quoteboard open and say rithmic does not support one of the symbols you have in there, you will be stuck in this loop. It will not stop. Once you remove this symbol from the quote board. restart sierra and it should be ok. Took me 6 hours on a fresh install yo re-create and isolate this problem. Hopefully Dev team reads this and does what I did, youll see the problem. |
To post a message in this thread, you need to log in with your Sierra Chart account: