Support Board
Date/Time: Thu, 28 Nov 2024 00:28:27 +0000
Sharing Sierra Exchange Data Feed
View Count: 1030
| [2014-10-26 18:16:32] |
| rhovega - Posts: 279 |
|
In en effort to share the SC Exchange Data Feed I followed the instructions here: http://www.sierrachart.com/index.php?page=doc/MultipleServices.html#Sharing Source copy has "Allow Support for Sierra Chart Data Feed" enabled, while destination copy has it disabled. The destination copy now shows the instrument name followed by [R] instead of followed by [M]. I worry that the destination copy is now pulling the data from my Broker's data feed (IB) rather than from the Sierra Chart Data Feed. Would the destination copy be using the Sierra Chart Data Feed even though it now says [R] instead of both [R] [M]? Furthermore, does sharing the data feed get the data files saved in both the source copy data folder and the destination copy data folder? (ie, so it uses double space) Thank you |
| [2014-10-26 19:06:46] |
| |
|
Would the destination copy be using the Sierra Chart Data Feed even though it now says [R] instead of both [R] [M]? Yes, it is using the Sierra Chart Exchange Data Feed.Furthermore, does sharing the data feed get the data files saved in both the source copy data folder and the destination copy data folder? (ie, so it uses double space) 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 |
| [2014-10-27 02:42:01] |
| rhovega - Posts: 279 |
|
I have problems with a continuous futures contract CL chart when opened on the destination copy. Chart is error free if opened from the source copy. Chart shows the [R]. Chart is looking for a particular contract (CLZ12) on the destination copy data folder instead of on the source copy data folder (and producing an error message). CLZ12.dly is present on the source copy data folder. CLZ12.dly has data (not an empty file). Just in case I copied CLZ12.dly to the destination copy as well. This did not solve the error. Could you suggest why is this happening so I may find a solution? I understand a chart showing the [R] should not be looking for data in the destination copy data folder, nor writing to it. But this chart is doing just that. This only happens with CLZ12 (Dec2012 contract), other daily files are found without problem. If I extend the data sample to 2011 I get the same error on 2011 contracts. LOG: CLZ14 [CBV] [R] Weekly #5 | Waiting for historical downloads to complete with the IDs: 5, | 2014-10-26 22:07:21 HD Request # 4 | Error downloading historical Daily data for CLZ12. Error while getting Historical Daily download information from file. Daily data file R:\Sierra\Sierra Data Com\CLZ12.dly does not exist. R:\Sierra\Sierra Data Com\CLZ12.dly | 2014-10-26 22:07:21 * HD Request # 4 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for CLZ12 | 2014-10-26 22:07:21 HD Request # 4 | Daily download COMPLETE for CLZ12. Completion time: 0s. Unique request ID: 5 | 2014-10-26 22:07:21 Removed historical data download ID 5 | 2014-10-26 22:07:21 Note: R:\Sierra\Sierra Data Com is the destination copy data folder Thanks |
| [2014-10-28 04:05:25] |
| |
|
The Continuous Futures Contract feature is not supported when sharing data across instances. We will see about supporting this, but really it is not very easy. 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 |
To post a message in this thread, you need to log in with your Sierra Chart account: