Support Board
Date/Time: Fri, 29 Nov 2024 18:41:45 +0000
data lagging on instance with CQG order routing only
View Count: 360
| [2023-01-26 15:07:31] |
| Bango - Posts: 76 |
|
I have a strange issue today. Instances with CQG only order routing have symbols data delayed. No problem with SC DATA. No issue with orders though.
Date Time Of Last Edit: 2023-01-26 16:12:48
|
 Immagine 2023-01-26 170051.png / V - Attached On 2023-01-26 16:12:36 UTC - Size: 31.51 KB - 92 views Attachment Deleted. |
| [2023-01-26 16:33:51] |
| John - SC Support - Posts: 36350 |
|
This could occur if there are issues connecting to CQG. Follow the instructions at the following link to get us your Message Log: Support Board Posting Information: How to Post Your Message Log (Required In Some Cases) For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2023-01-26 17:17:38] |
| Bango - Posts: 76 |
|
Reading Internal Order ID file. | 2023-01-26 18:15:22.615 Reading Trade Orders file. | 2023-01-26 18:15:22.682 Reading Trade Positions file. | 2023-01-26 18:15:22.682 Reading Trade Account Data files. | 2023-01-26 18:15:22.682 UDPListener (1556). Port 11099 | Listening on UDP port 11099. | 2023-01-26 18:15:22.683 Software version: 2466 64-bit | 2023-01-26 18:15:22.683 Primary Thread ID: 4228 | 2023-01-26 18:15:22.683 Usage end date: 2023-02-12 | 2023-01-26 18:15:22.683 Enabled for: Advanced Features 2. | 2023-01-26 18:15:22.683 Enabled for: Sierra Chart Historical Data Service. | 2023-01-26 18:15:22.683 Enabled for: Denali Real-Time Exchange Data Feed. | 2023-01-26 18:15:22.683 Enabled for: Delayed Denali Exchange Data Feed. | 2023-01-26 18:15:22.683 Enabled for exchange2: CME (Trading Account Required) | 2023-01-26 18:15:22.683 Enabled for exchange2: CBOT (Trading Account Required) | 2023-01-26 18:15:22.683 Enabled for exchange2: COMEX (Trading Account Required) | 2023-01-26 18:15:22.683 Enabled for exchange2: NYMEX (Trading Account Required) | 2023-01-26 18:15:22.683 Enabled for exchange2: EUREX EOBI | 2023-01-26 18:15:22.683 Enabled for exchange2: fairx_exchange.data | 2023-01-26 18:15:22.683 Allow Support for Sierra Chart Data Feeds is enabled. | 2023-01-26 18:15:22.683 Current selected Data/Trading service: CQG WebAPI | 2023-01-26 18:15:22.683 Custom symbol settings values: disabled | 2023-01-26 18:15:22.683 Chart Update Interval: 1000 | 2023-01-26 18:15:22.684 Intraday Data Storage Time Unit: 0 | 2023-01-26 18:15:22.684 Time Zone: +01:00:00 (CET+01CEST+01,M3.5.0/02:00,M10.5.0/03:00) | 2023-01-26 18:15:22.684 2023-01-26 17:15:22 Local computer time in UTC | 2023-01-26 18:15:22.684 2023-01-26 18:15:22 Local computer time in SC Time Zone | 2023-01-26 18:15:22.684 2023-01-26 17:15:22 Server time in UTC | 2023-01-26 18:15:22.684 Local computer UTC time and Server UTC time difference: 0 seconds. | 2023-01-26 18:15:22.684 Program path: D:\SC-AMP\ | 2023-01-26 18:15:22.684 Data Files path: D:\SC-AMP\Data\ | 2023-01-26 18:15:22.684 OS Version Number: 10.0 | 2023-01-26 18:15:22.684 Locale Setting: C | 2023-01-26 18:15:22.684 DLLs: UserContributedStudies_64.dll | 2023-01-26 18:15:22.684 Allowed protected custom studies: | 2023-01-26 18:15:22.684 Crash reporter started: true | 2023-01-26 18:15:22.684 Checking for new symbol settings. Requested symbol settings MD5 for service code cqg. Request ID: 1. | 2023-01-26 18:15:22.701 HTTPS connection ID:1 to login.sierrachart.com:443 for request ID:1 (1) | Shutdown started. Waiting for graceful close. | 2023-01-26 18:15:22.737 HTTPS connection ID:1 to login.sierrachart.com:443 for request ID:1 (1) | Socket gracefully closed by remote side. | 2023-01-26 18:15:22.793 HTTPS connection ID:1 to login.sierrachart.com:443 for request ID:1 (1) | Closed. | 2023-01-26 18:15:22.794 Received 5 login tokens. | 2023-01-26 18:15:22.916 Symbol settings MD5 received. Request ID: 1. | 2023-01-26 18:15:24.293 Symbol settings are up-to-date for cqg. | 2023-01-26 18:15:24.293 CQG WebAPI | Connecting to server api.cqg.com | 2023-01-26 18:15:28.991 CQG WebSocket | Connecting to WebSocket server api.cqg.com:443 | 2023-01-26 18:15:28.991 CQG WebSocket socket (1) | Creating socket. Using TLS 1.2. | 2023-01-26 18:15:28.992 CQG WebSocket socket (1) | New receive buffer size: 5242880 | 2023-01-26 18:15:28.992 CQG WebSocket socket (1) | Connecting to IP: 195.166.124.165. | 2023-01-26 18:15:28.992 CQG WebSocket | Opening WebSocket. | 2023-01-26 18:15:29.034 CQG WebSocket | Sending WebSocket handshake. | 2023-01-26 18:15:29.034 CQG WebSocket | Server header | HTTP/1.1 101 Switching Protocols | 2023-01-26 18:15:29.160 CQG WebSocket | Server header | Connection: upgrade | 2023-01-26 18:15:29.160 CQG WebSocket | Server header | Sec-WebSocket-Accept: GmzchSa4oUorQT+lhCKX7cbAiec= | 2023-01-26 18:15:29.160 CQG WebSocket | Server header | Server: WebSocket++/0.7.0 | 2023-01-26 18:15:29.160 CQG WebSocket | Server header | Upgrade: websocket | 2023-01-26 18:15:29.160 CQG WebSocket | Server header | | 2023-01-26 18:15:29.160 CQG WebSocket | Web socket state is now open. | 2023-01-26 18:15:29.160 CQG WebAPI | WebSocket connected. | 2023-01-26 18:15:29.160 CQG WebAPI | Sending market data logon message. | 2023-01-26 18:15:29.160 CQG WebAPI | Base Time: 2023-01-08T01:10:10. 2023-01-08 01:10:10 | 2023-01-26 18:15:29.510 CQG WebAPI | Logon successful. Session Token = /DFQlN2VHeLpHzXsVYsIEFbMx/DNVO5iUJ1Nh6MACjYtcEGgIwnU+Y320caOkZfUvosr4hnh89r | 2023-01-26 18:15:29.510 CQG WebAPI | Connected to server complete. | 2023-01-26 18:15:29.510 Triggering next historical data download in queue. | 2023-01-26 18:15:29.510 Triggering next historical data download in queue. | 2023-01-26 18:15:29.510 Triggering next historical data download in queue. | 2023-01-26 18:15:29.510 Triggering next historical data download in queue. | 2023-01-26 18:15:29.510 Updated verified funded futures trading account ending date to: 2023-02-25 17:15:29 | 2023-01-26 18:15:29.510 CQG WebAPI | Sending Trade Accounts request message. | 2023-01-26 18:15:29.510 No download requests in the queue to start downloads for. | 2023-01-26 18:15:29.510 No download requests in the queue to start downloads for. | 2023-01-26 18:15:29.511 No download requests in the queue to start downloads for. | 2023-01-26 18:15:29.511 No download requests in the queue to start downloads for. | 2023-01-26 18:15:29.512 CQG WebAPI | Brokerage name: AMP. Account Name: 160985 | 2023-01-26 18:15:29.601 Updated verified funded futures trading account ending date to: 2023-02-25 17:15:29 | 2023-01-26 18:15:29.601 CQG WebAPI | Sending collateral subscribe request. | 2023-01-26 18:15:29.601 CQG WebAPI | Sending positions subscribe request. RequestID: 222399 | 2023-01-26 18:15:29.740 CQG WebAPI | Sending orders subscribe request. RequestID: 222400 | 2023-01-26 18:15:29.740 |
| [2023-01-26 18:13:50] |
| John - SC Support - Posts: 36350 |
|
We do not see anything in the log that shows any issues. Do you have two separate installations of Sierra Chart so that you had both running at the same time when you took the image of the Time and Sales windows? What else are you seeing that makes you think your data is lagging when connected to CQG? For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2023-01-26 18:40:27] |
| Bango - Posts: 76 |
|
Yes, I have separate installations of SC. I had an instance connected to CQG order routing and another to SC data both running at the same time when I took the image of the Time and Sales windows. Also tried to disconnect and reconnect. Cqg instance was getting immediately off almost 30 sec up to 2 minutes. No issue for SC data instance in the meantime. |
| [2023-01-26 18:57:45] |
| John - SC Support - Posts: 36350 |
|
On the CQG instance in the Chart Header do you have an item that starts with DD:? If so, then what is the value after it? If not, then please go to Global Settings >> Customize Chart Header - Standard and add the Data Delay option from the left to the right. Then select OK to close that window. Then let us know what value is after the DD: in the chart header. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2023-01-26 19:34:07] |
| Bango - Posts: 76 |
|
DD now is 0 the issue lasted a couple of hours from 15:30 to 18:30 local time
|
| [2023-01-26 21:32:58] |
| John - SC Support - Posts: 36350 |
|
There simply is no reason that we can think of that would cause this - apart from issues connecting to CQG, but your log does not show any of those. We are glad that it is working now.
For the most reliable, advanced, and zero cost futures order routing, use 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: