Login Page - Create Account

Support Board


Date/Time: Fri, 29 Mar 2024 10:36:11 +0000



Possible causes of DTC garbled records?

View Count: 858

[2019-02-13 14:09:42]
User640191 - Posts: 4
DTC Server: SC v1873
DTC Client: Dtc.HistoricalPriceDataRecordResponse.ParseFromString() [protocol version 8]

One example is CLG19 where 8000 1-min bars for a random span in Jan 2019 parses clean, but 9000 not.

Garbling threshold varies with instrument, but certainly the more I ask, the greater the risk.

Excluding basic bugs like pulling half-baked records from the wire, and excluding network buffer overflow, has SC heard other cases?
[2019-02-14 02:42:20]
Sierra Chart Engineering - Posts: 104368
You must be mishandling the data. We confirmed there is no problem with a large data download using protocol buffer encoding:
HD Request # 2 | Downloading Intraday chart data for XBTUSD-BMEX to the file XBTUSD-BMEX.scid. Service: DTCSubInstance | 2019-02-13 21:38:15
HD Request # 2 | Download start date-time: 2019-01-14 21:38:15.000 | 2019-02-13 21:38:15
HD Request # 2 | Using server: 127.0.0.1 port 11095 | 2019-02-13 21:38:15
Socket (2) | Creating socket. | 2019-02-13 21:38:15
Socket (2) | Receive buffer size: 262144 | 2019-02-13 21:38:15
Socket (2) | Send buffer size: 0 | 2019-02-13 21:38:15
Socket (2) | Connecting to IP: 127.0.0.1. | 2019-02-13 21:38:15
HD Request # 2 | Setting DTC encoding to Protocol Buffers | 2019-02-13 21:38:15
HD Request # 2 | Sending historical data logon request message. | 2019-02-13 21:38:15
HD Request # 2 | Requesting Intraday data. Start date-time: 2019-01-14 21:38:15. Record interval: 0. Symbol: XBTUSD-BMEX | 2019-02-13 21:38:15
HD Request # 2 | Receiving Intraday data for XBTUSD-BMEX starting at 2019-01-14 21:38:18 | 2019-02-13 21:38:15
HD Request # 2 | Timestamp of first Intraday data file record written: 2019-01-14 21:38:18 | 2019-02-13 21:38:15
Socket (2) | Maximum receive buffer size during socket life: 3358735 | 2019-02-13 21:38:55
Socket (2) | Max send buffers used during socket life: 1 | 2019-02-13 21:38:55
Socket (2) | Signaling to core to close socket | 2019-02-13 21:38:55
Socket (2) | Shutdown started. Waiting for graceful close. | 2019-02-13 21:38:55
Historical data download thread signaled to stop. | 2019-02-13 21:38:55
HD Request # 2 | Received 4411087 records from 2019-01-14 21:38:18 to 2019-02-11 23:54:04 (28.1 days) and wrote 4411087 records for XBTUSD-BMEX | 2019-02-13 21:38:55

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: 2019-02-14 02:42:48
[2019-02-24 17:54:01]
User640191 - Posts: 4
Cross-post:

https://dtcprotocol.org/SupportBoard.php?ThreadID=40694
[2019-02-24 21:37:29]
Sierra Chart Engineering - Posts: 104368
There is definitely no problem on the Sierra Chart side with this. This is 110% clear.
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:

Login

Login Page - Create Account