Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Mon, 06 May 2024 04:56:29 +0000
Post From: Data Glitch
| [2020-03-31 08:29:58] |
| |
|
CQG did contact us about this because you contacted them. They showed us that their log files and showed that the correct_price_scale field was being provided in the symbol resolution report which is necessary to properly convert the values. We again did an extensive code review. And just cannot see how anything could have gone wrong on the Sierra Chart side with using that value and we did tell them that. The way that report is requested , processed, and subsequently a market data request is made is all very consistent and stable. It just cannot fail under any condition unless something goes wrong on the server side . The only thing that we could conclude and we told them, is that perhaps because we are using an older version of the protocol definition file from CQG, somehow this field was not indicated to be set or was not present for some unknown reason. That would be the only logical explanation. We had trouble with the latest CQG protocol definition file but we will work on it using it again, now that we have updated the Google protocol buffer library in Sierra Chart. We also removed the check to see if that particular field is present because if somehow if the check at the Google protocol buffer library level was failing for an unknown reason, then this will also resolve the issue. This is in version 2072, so we recommend updating. 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: 2020-03-31 08:33:38
|