Support Board
Date/Time: Mon, 25 Nov 2024 08:40:59 +0000
Binance on CQG?
View Count: 410
| [2024-02-27 11:28:25] |
| StephenL - Posts: 98 |
|
Hi guys, I use CQG data (for access to ICE) and I wanted to also get up Binance products. However, I can only see BitMex when I'm logged into CQG WebAPI. When I swap the data over to SC Data - All Services I can access Binance but I obviously lose my ICE data as it disconnects from CQG. Is there a way to run both concurrently? Thanks |
| [2024-02-27 16:44:10] |
| John - SC Support - Posts: 36238 |
|
The only way to get both at the same time is to have a separate installation of Sierra Chart with the "Current Selected Service" set to "SC Data - All Services" so you can get he Binance data in that installation. Refer to the following for how to install a second Sierra Chart: Using Multiple Data and Trading Services at the Same Time: Step-By-Step Instructions to Install Multiple Copies of Sierra Chart For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2024-02-28 20:04:44] |
| StephenL - Posts: 98 |
|
Hi John, That worked perfect. Thanks! |
| [2024-03-11 16:33:17] |
| StephenL - Posts: 98 |
|
Hi John, Ive been using this with one instance no problem since I commented last. However, Ive opened a new instance for the first and none of the data is loading from Binance? The data on the ExampleChartbook page loads fine. Ive added a screenshot of the settings in case you need it. Thanks |
 Screenshot 2024-03-11 163202.png / V - Attached On 2024-03-11 16:32:33 UTC - Size: 35.86 KB - 56 views Screenshot 2024-03-11 162953.png / V - Attached On 2024-03-11 16:32:39 UTC - Size: 23.73 KB - 57 views Attachment Deleted. |
| [2024-03-11 16:54:28] |
| Sierra_Chart Engineering - Posts: 17172 |
|
You will need a separate installation of Sierra Chart to use with Binance symbols. Instructions: Using Multiple Data and Trading Services at the Same Time: Step-By-Step Instructions to Install Multiple Copies of Sierra Chart And it needs to be set to use the service SC Data-All Services. 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, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2024-03-12 16:39:03] |
| StephenL - Posts: 98 |
|
Thanks for the reply. I have Binance on a separate installation of Sierra Chart, and its working. But when I create a second Instance from the separate Sierra Chart, Binance won't work on the second instance. I've attached the data settings for the separate Sierra Chart and the Second Instance. |
| Screenshot 2024-03-12 163517.png / V - Attached On 2024-03-12 16:35:30 UTC - Size: 34.58 KB - 53 views |
| [2024-03-12 17:22:14] |
| John - SC Support - Posts: 36238 |
|
Please get us your Message Log in the sub-instance where you are having an issue by following these instructions: Follow the instructions here to clear the Message Log: Message Log: Clearing the Message Log Close all of the Chartbooks with "File >> Close All Chartbooks". Open a single chart for the symbol you have an issue with through "File >> Find Symbol". Tell us that symbol of the chart. Tell us about *one* symbol only. Disconnect from the data feed with "File >> Disconnect". Connect to the data feed with "File >> Connect to Data Feed". After the connection and after about 10 seconds, provide a copy of the Message Log following these instructions: Support Board Posting Information: How to Post Your Message Log (Required In Some Cases) We will then determine what the problem is. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2024-03-12 20:05:12] |
| StephenL - Posts: 98 |
|
The one symbol is BTCUSDT_PERP_BINANCE 2024-03-12 20:02:00.817 | Software version: 2604 64-bit 2024-03-12 20:02:00.817 | Primary Thread ID: 16768 2024-03-12 20:02:00.817 | Usage end date: 2024-03-23 2024-03-12 20:02:00.817 | Enabled for: Advanced Features 2. 2024-03-12 20:02:00.817 | Enabled for: Sierra Chart Historical Data Service. 2024-03-12 20:02:00.817 | Enabled for: Denali Real-Time Exchange Data Feed. 2024-03-12 20:02:00.817 | Enabled for: Delayed Denali Exchange Data Feed. 2024-03-12 20:02:00.817 | Enabled for exchange2: CME (Trading Account Required) 2024-03-12 20:02:00.817 | Enabled for exchange2: CBOT (Trading Account Required) 2024-03-12 20:02:00.817 | Enabled for exchange2: COMEX (Trading Account Required) 2024-03-12 20:02:00.817 | Enabled for exchange2: NYMEX (Trading Account Required) 2024-03-12 20:02:00.817 | Enabled for exchange2: EUREX EOBI 2024-03-12 20:02:00.817 | Enabled for exchange2: CFE 2024-03-12 20:02:00.817 | Enabled for exchange2: NASDAQ TotalView US stock data 2024-03-12 20:02:00.817 | Allow Support for Sierra Chart Data Feeds is enabled. 2024-03-12 20:02:00.817 | Current selected Data/Trading service: DTC - Sub Instance 2024-03-12 20:02:00.817 | Custom symbol settings values: enabled 2024-03-12 20:02:00.817 | Chart Update Interval: 500 2024-03-12 20:02:00.817 | Intraday Data Storage Time Unit: 0 2024-03-12 20:02:00.817 | Time Zone: +00:00:00 (GMT+00BST+01,M3.5.0/01:00,M10.5.0/02:00) 2024-03-12 20:02:00.817 | 2024-03-12 20:02:00 Local computer time in UTC 2024-03-12 20:02:00.817 | 2024-03-12 20:02:00 Local computer time in SC Time Zone 2024-03-12 20:02:00.817 | 2024-03-11 15:51:08 Server time in UTC 2024-03-12 20:02:00.817 | Local computer UTC time and Server UTC time difference: 11 seconds. 2024-03-12 20:02:00.817 | Notice: Your computer's clock is off by 11 seconds. For help with this, press the 'Send for Analysis' button. 2024-03-12 20:02:00.817 | Program path: C:\SierraChartCrypto\SierraChartInstance_2\ 2024-03-12 20:02:00.817 | Data Files path: C:\SierraChartCrypto\SierraChartInstance_2\Data\ 2024-03-12 20:02:00.817 | OS Version Number: 10.0 2024-03-12 20:02:00.817 | Locale Setting: C 2024-03-12 20:02:00.817 | DLLs: CustomSwingHighLow_64.dll, UserContributedStudies_64.dll 2024-03-12 20:02:00.817 | Allowed protected custom studies: 2024-03-12 20:02:00.817 | Crash reporter started: true 2024-03-12 20:02:00.817 | 2024-03-12 20:02:22.848 | Saved Chartbook: Layer 1.Cht. Time: 0.0638 seconds. 2024-03-12 20:02:29.557 | Saved Chartbook: ExampleChartbook.cht. Time: 0.0038 seconds. 2024-03-12 20:03:17.999 | BTCUSDT_PERP_BINANCE 1 Min #1 | Reloading chart. 2024-03-12 20:03:22.624 | BTCUSDT_PERP_BINANCE 1 Min #1 | Chart data loading complete. 2024-03-12 20:03:36.384 | File >> Disconnect selected. 2024-03-12 20:03:36.384 | DTC - Sub Instance | Waiting for socket receive thread to end 2024-03-12 20:03:36.384 | DTC Client socket (1) | CloseSocket call. 2024-03-12 20:03:36.384 | DTC Client socket (1) | Shutdown started. Waiting for graceful close. 2024-03-12 20:03:36.384 | DTC Client socket (1) | Socket gracefully closed by remote side. 2024-03-12 20:03:36.384 | DTC Client socket (1) | Closed. 2024-03-12 20:03:36.385 | DTC - Sub Instance | Disconnected. 2024-03-12 20:03:43.808 | 2024-03-12 20:03:43.808 | DTC - Sub Instance | Connecting to the server 127.0.0.1. Port 11099 2024-03-12 20:03:43.809 | DTC Client socket (1) | Creating socket. 2024-03-12 20:03:43.809 | DTC Client socket (1) | New receive buffer size: 0 2024-03-12 20:03:43.809 | DTC Client socket (1) | Connecting to IP: 127.0.0.1. 2024-03-12 20:03:43.809 | DTC - Sub Instance | Network connection to server complete. 2024-03-12 20:03:43.809 | DTC - Sub Instance | Starting socket receive thread. 2024-03-12 20:03:43.809 | DTC - Sub Instance | Sending encoding request to server: Binary VLS. Compression: none 2024-03-12 20:03:43.809 | DTC - Sub Instance | Setting DTC encoding to Binary VLS 2024-03-12 20:03:43.809 | DTC - Sub Instance | Sending logon request message. 2024-03-12 20:03:43.810 | DTC - Sub Instance | Received logon response. 2024-03-12 20:03:43.810 | DTC - Sub Instance | Server Name: SC DTC Server. Build=48734M. 2024-03-12 20:03:43.810 | DTC - Sub Instance | Server protocol version: 8. Client protocol version: 8 2024-03-12 20:03:43.810 | DTC - Sub Instance | Successfully connected. Connected to SC DTC Protocol server. Service=cqg|SymbolSettings=cqg. 2024-03-12 20:03:43.810 | DTC - Sub Instance | Trading is supported. 2024-03-12 20:03:43.810 | DTC - Sub Instance | Order cancel and replace is supported. 2024-03-12 20:03:43.810 | DTC - Sub Instance | OCO Orders supported. 2024-03-12 20:03:43.810 | DTC - Sub Instance | Bracket Orders supported. 2024-03-12 20:03:43.810 | DTC - Sub Instance | MarketDepthIsSupported: 1 2024-03-12 20:03:43.810 | DTC - Sub Instance | Connected to server complete. 2024-03-12 20:03:43.818 | No download requests in the queue to start downloads for. 2024-03-12 20:03:43.818 | No download requests in the queue to start downloads for. 2024-03-12 20:03:43.818 | No download requests in the queue to start downloads for. 2024-03-12 20:03:43.818 | No download requests in the queue to start downloads for. 2024-03-12 20:03:43.819 | Checking for new symbol settings. Requested symbol settings MD5 for service code cqg. Request ID: 3. 2024-03-12 20:03:43.902 | Using symbol data fast lookup vector 2024-03-12 20:03:43.902 | DTC - Sub Instance | Starting real-time market data updates for: F.US.ENQH24. ID: 1 Service code: cqg 2024-03-12 20:03:43.902 | DTC - Sub Instance | Requesting security definition data for: F.US.ENQH24. ID: 1 2024-03-12 20:03:43.902 | DTC - Sub Instance | Received security definition for symbol F.US.ENQH24 2024-03-12 20:03:43.993 | DTC - Sub Instance | Starting real-time market data updates for: BTCUSDT_PERP_BINANCE. ID: 2 2024-03-12 20:03:43.993 | DTC - Sub Instance | Requesting security definition data for: BTCUSDT_PERP_BINANCE. ID: 2 2024-03-12 20:03:43.993 | Added historical Intraday data request for BTCUSDT_PERP_BINANCE to the queue. 2024-03-12 20:03:43.993 | Intraday data recording state for symbol BTCUSDT_PERP_BINANCE is set to download 'Pending'. 2024-03-12 20:03:43.993 | Triggering next historical data download in queue. 2024-03-12 20:03:43.997 | Delaying start of download for BTCUSDT_PERP_BINANCE. 2024-03-12 20:03:43.997 | DTC - Sub Instance | Received security definition for symbol BTCUSDT_PERP_BINANCE 2024-03-12 20:03:48.078 | HD Request # 60 | Downloading Intraday chart data for BTCUSDT_PERP_BINANCE to the file BTCUSDT_PERP_BINANCE.scid. Service: DTCSubInstance 2024-03-12 20:03:48.078 | HD Request # 60 | Download start date-time: 2024-03-11 15:25:10.000000. File last date-time: 2024-03-11 15:25:10.506000 2024-03-12 20:03:48.079 | HD Request # 60 | Using server: 127.0.0.1 port 11098 2024-03-12 20:03:48.079 | Socket (3) | Creating socket. 2024-03-12 20:03:48.079 | Socket (3) | New receive buffer size: 0 2024-03-12 20:03:48.079 | Socket (3) | Connecting to IP: 127.0.0.1. 2024-03-12 20:03:48.140 | Symbol settings MD5 received. Request ID: 3. 2024-03-12 20:03:48.140 | Requested symbol settings for service code cqg. Request ID: 4. 2024-03-12 20:03:48.142 | HD Request # 60 | Setting DTC encoding to Binary VLS 2024-03-12 20:03:48.142 | HD Request # 60 | Sending historical data logon request message. 2024-03-12 20:03:48.143 | HD Request # 60 | Requesting Intraday data. Start date-time: 2024-03-11 15:25:10. Record interval: 0. Symbol: BTCUSDT_PERP_BINANCE 2024-03-12 20:03:48.147 | Socket (3) | CloseSocket call. 2024-03-12 20:03:48.147 | Socket (3) | Shutdown started. Waiting for graceful close. 2024-03-12 20:03:48.147 | Historical data download thread signaled to stop. 2024-03-12 20:03:48.147 | HD Request # 60 | Received 0 Intraday data records from 00:00:00.000000 to 00:00:00.000000 (0.0 seconds and wrote 0 records for BTCUSDT_PERP_BINANCE 2024-03-12 20:03:48.147 | HD Request # 60 | Add time&sales data | Remembered last file record date-time: 2024-03-11 15:25:10.506000 2024-03-12 20:03:48.148 | HD Request # 60 | Completion time: 0s. 2024-03-12 20:03:48.148 | HD Request # 60 | Intraday data download complete for BTCUSDT_PERP_BINANCE. Unique request ID: 62 2024-03-12 20:03:48.148 | Removing historical data download ID 62. 2024-03-12 20:03:48.148 | Real-time Intraday chart data file updates started for BTCUSDT_PERP_BINANCE 2024-03-12 20:03:48.148 | Intraday chart data file opened for BTCUSDT_PERP_BINANCE 2024-03-12 20:03:48.148 | HD Request # 60 | Enabling Intraday chart updating for symbol. 2024-03-12 20:03:48.148 | 2024-03-12 20:03:48.148 | No download requests in the queue to start downloads for. 2024-03-12 20:03:48.148 | Socket (3) | Socket gracefully closed by remote side. 2024-03-12 20:03:48.148 | Socket (3) | Closed. 2024-03-12 20:03:53.128 | Symbol settings received. Request ID: 4. 2024-03-12 20:03:54.001 | DTC - Sub Instance | Starting real-time market data updates for: F.US.ENQM24. ID: 3 Service code: cqg 2024-03-12 20:03:54.001 | DTC - Sub Instance | Requesting security definition data for: F.US.ENQM24. ID: 3 2024-03-12 20:03:54.001 | DTC - Sub Instance | Received security definition for symbol F.US.ENQM24 |
| [2024-03-12 20:12:55] |
| John - SC Support - Posts: 36238 |
|
Please open a chart for BTCUSDT_PERP_BINANCE in the Main Sierra Chart instance. Once that loads, try to bring up the Sub-Instance and see if you are able to get the data into that sub-instance.
For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2024-03-12 20:25:22] |
| StephenL - Posts: 98 |
|
Yep it works in the main instance.
|
| Screenshot 2024-03-12 202457.png / V - Attached On 2024-03-12 20:25:13 UTC - Size: 4.6 KB - 61 views Attachment Deleted. |
| [2024-03-12 21:28:51] |
| John - SC Support - Posts: 36238 |
|
Now that there is data in the main instance, are you able to get it in the Sub-Instance? If not immediately, then please try "Edit >> Delete All Data and Download" and let us know.
For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2024-03-13 01:03:16] |
| Sierra_Chart Engineering - Posts: 17172 |
|
This is not going to work at all for you: 2024-03-12 20:03:43.810 | DTC - Sub Instance | Successfully connected. Connected to SC DTC Protocol server. Service=cqg|SymbolSettings=cqg. You need a fully separate independent installation of Sierra Chart. Not a sub instance. That will not work. You need to do what we said in post #5. Your main instance of Sierra Chart is set to use CQG. That is not going to work. 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, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2024-03-13 01:03:57
|
| [2024-03-13 09:33:50] |
| StephenL - Posts: 98 |
|
Ahhhhh right, I think I get you now. I did what you said in Post #5 (and John's Post #2) and I had two sperate Main Instances of Sierra Chart running (located on separate drives on the same computer). The original CGQ data one, and a new one for SC Data. And so even though I created a new Sub-Instance from the SC Data Main Instance (running Binance on SC Data), the new Sub Instance still links up with the original CQG Main Instance? (I appreciate you taking the time to walk me thru this im sure its basic stuff from your pov) |
| [2024-03-13 15:18:27] |
| John - SC Support - Posts: 36238 |
|
With regards to the Sub-Instance situation, refer to the following: Using DTC Server for Data and Trading in Another Sierra Chart Instance: Resolving DTC Protocol Server Port Number Conflicts 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: