Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Thu, 25 Apr 2024 19:35:36 +0000
Sub instance data gap
View Count: 748
| [2018-11-30 09:56:52] |
| User907968 - Posts: 802 |
|
Hi support, Since switching to using SC in server/client (main instance + 4 sub instances on local computer), the data download upon initially opening the charts is not complete. It appears that the intraday data from the historical data server is downloaded completely, but the intraday data from the live server only begins from the time the chart is opened. Please see the attached image captured immediately after opening the chartbook, this shows a 10-min gap. Performing a 'reload & recalculate' makes no difference, the charts reload exactly the same. Performing a 'delete & download data' does fill in the missing data, however this must be repeated for each and every symbol anytime that the incoming data feed has been disconnected. The observed behaviour is consistent across all symbols monitored (CME & NYMEX), the data feed is CTS T4 FIX, SC is set to 'periodically set system date time from server'. I have reviewed the help documents, but cannot find a solution, am I missing something obvious? edit - I forgot to upload the image, sorry Date Time Of Last Edit: 2018-11-30 11:17:29
|
 data gap.png / V - Attached On 2018-11-30 11:16:59 UTC - Size: 77.85 KB - 260 views |
| [2018-11-30 17:02:03] |
| |
|
Next time you notice this when you start a sub instance, provide a copy of the Message Log following these instructions: https://www.sierrachart.com/index.php?page=PostingInformation.php#MessageLog And tell us one of the symbols it happens with. 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: 2018-11-30 17:02:45
|
| [2018-11-30 18:06:25] |
| User907968 - Posts: 802 |
|
Hi support, logs submitted for analysis, 1800GMT, both for main instance and sub instance. The symbol is CL.20190100.CME_NY Thank you. |
| data gap CL.png / V - Attached On 2018-11-30 18:05:37 UTC - Size: 64 KB - 239 views |
| [2018-12-01 08:29:35] |
| |
|
This is not something we usually recommend but we want you to perform a Full Reset of the Symbol Settings: https://www.sierrachart.com/index.php?page=doc/GlobalSymbolSettings.php#FullResetSymbolSettingsSteps It is hard to definitively say but it appears as though there is either missing symbol settings or something wrong with the rollover rules causing Sierra Chart to think CL.20190100.CME_NY is an expired contract. 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 |
| [2018-12-01 08:41:28] |
| |
|
Actually the answer given at post #4 might not be correct. There is some complexity going on here. We want you to disable Global Settings >> Data/Trade Service Settings >> Allows Support for Sierra Chart Data Feeds. 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 |
| [2018-12-01 09:41:39] |
| |
|
We have determined the reason for the problem and a solution will be implemented in the next release. It has to do with a two-step download from the Sierra Chart Historical Data Service and then from the primary service.
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 |
| [2018-12-01 12:25:29] |
| User907968 - Posts: 802 |
|
Based on your last post, can I assume that posts 4 & 5 no longer apply? Thank you for looking at this so quickly. |
| [2018-12-01 20:57:52] |
| |
|
Post #5 is the solution to use right now. But we expect to have a new release out tomorrow.
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 |
| [2018-12-03 16:44:53] |
| User907968 - Posts: 802 |
|
This issue seems resolved now in v1849, thanks.
|
To post a message in this thread, you need to log in with your Sierra Chart account: