Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Thu, 25 Apr 2024 22:52:27 +0000
How to enable crypto currency?
View Count: 1507
| [2018-08-11 12:56:11] |
| User503358 - Posts: 50 |
|
I have Bitmex account and SC package 5, but Sierrachart show me not enable on package for cryptocurrencies. (see image) Reading Internal Order ID file. | 2018-08-11 12:50:38 Reading Trade Orders file. | 2018-08-11 12:50:39 Reading Trade Positions file. | 2018-08-11 12:50:39 Listening on UDP port 22904. | 2018-08-11 12:50:39 Software version: 1708 64-bit | 2018-08-11 12:50:39 Enabled for: Advanced Features. | 2018-08-11 12:50:39 Enabled for: Advanced Features 2. | 2018-08-11 12:50:39 Enabled for: Sierra Chart Historical Data Service. | 2018-08-11 12:50:39 Allow Support for Sierra Chart Data Feeds is enabled. | 2018-08-11 12:50:39 Current selected Data/Trading service: CQG FIX Trading | 2018-08-11 12:50:39 Chart Update Interval: 500 | 2018-08-11 12:50:39 Data/Trade Service Settings automatically set. | 2018-08-11 12:50:39 Time Zone: +00:00:00 (UTC+00) | 2018-08-11 12:50:39 2018-08-11 05:50:38 Local computer time | 2018-08-11 12:50:39 2018-08-11 12:50:38 Local computer time in UTC | 2018-08-11 12:50:39 2018-08-11 12:50:38 Local computer time in SC Time Zone | 2018-08-11 12:50:39 2018-08-11 12:50:35 Server time in UTC | 2018-08-11 12:50:39 Local computer UTC time and Server UTC time difference: 1 seconds. | 2018-08-11 12:50:39 Program path: C:\SierraChart\ | 2018-08-11 12:50:39 Data Files path: C:\SierraChart\Data\ | 2018-08-11 12:50:39 OS Version Number: 6.3 | 2018-08-11 12:50:39 Locale Setting: C | 2018-08-11 12:50:39 Checking for new symbol settings for service code cqg | 2018-08-11 12:50:39 HTTPS connection to www.sierrachart.com:443 (4) | Creating socket. Using TLS 1.2. | 2018-08-11 12:50:39 HTTPS connection to www.sierrachart.com:443 (4) | Connecting to IP: 204.15.192.108. | 2018-08-11 12:50:39 Symbol settings are up-to-date for cqg | 2018-08-11 12:50:39 Received 5 login tokens. | 2018-08-11 12:50:39 HTTPS connection to www.sierrachart.com:443 (5) | Creating socket. Using TLS 1.2. | 2018-08-11 12:50:41 HTTPS connection to www.sierrachart.com:443 (5) | Connecting to IP: 204.15.192.108. | 2018-08-11 12:50:41 HTTPS connection to www.sierrachart.com:443 (4) | Socket gracefully closed by remote side. | 2018-08-11 12:50:44 HTTPS connection to www.sierrachart.com:443 (4) | Received socket Close event. | 2018-08-11 12:50:44 HTTPS connection to www.sierrachart.com:443 (4) | Initiating close of socket by core. | 2018-08-11 12:50:44 HTTPS connection to www.sierrachart.com:443 (4) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2018-08-11 12:50:44 HTTPS connection to www.sierrachart.com:443 (4) | Closed. | 2018-08-11 12:50:44 HTTPS connection to www.sierrachart.com:443 (2) | Socket gracefully closed by remote side. | 2018-08-11 12:50:44 HTTPS connection to www.sierrachart.com:443 (2) | Received socket Close event. | 2018-08-11 12:50:44 HTTPS connection to www.sierrachart.com:443 (2) | Initiating close of socket by core. | 2018-08-11 12:50:45 HTTPS connection to www.sierrachart.com:443 (2) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2018-08-11 12:50:45 HTTPS connection to www.sierrachart.com:443 (2) | Closed. | 2018-08-11 12:50:45 HTTPS connection to www.sierrachart.com:443 (5) | Socket gracefully closed by remote side. | 2018-08-11 12:50:46 HTTPS connection to www.sierrachart.com:443 (5) | Received socket Close event. | 2018-08-11 12:50:46 HTTPS connection to www.sierrachart.com:443 (5) | Initiating close of socket by core. | 2018-08-11 12:50:46 HTTPS connection to www.sierrachart.com:443 (5) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2018-08-11 12:50:46 HTTPS connection to www.sierrachart.com:443 (5) | Closed. | 2018-08-11 12:50:46 CQG FIX: Connecting to fixapi.cqgtrader.com. Port: 6925. | 2018-08-11 12:50:49 CQG FIX socket (6) | Creating socket. Using TLS 1.2. | 2018-08-11 12:50:49 CQG FIX socket (6) | Connecting to IP: 208.48.16.214. | 2018-08-11 12:50:49 CQG FIX: Sending the Logon message. | 2018-08-11 12:50:50 CQG FIX Trading | Connected to trading server. | 2018-08-11 12:50:50 CQG FIX Trading | Connecting to server api.cqg.com | 2018-08-11 12:50:50 CQG WebSocket | Connecting to WebSocket server. | 2018-08-11 12:50:50 CQG FIX | FCM name: AMP | 2018-08-11 12:50:50 CQG WebSocket socket (7) | Creating socket. Using TLS 1.2. | 2018-08-11 12:50:50 CQG WebSocket socket (7) | Connecting to IP: 195.166.124.165. | 2018-08-11 12:50:50 CQG WebSocket | Opening WebSocket. | 2018-08-11 12:50:50 CQG WebSocket | Sending WebSocket handshake. | 2018-08-11 12:50:50 CQG WebSocket | Header line. HTTP/1.1 101 Switching Protocols | 2018-08-11 12:50:50 CQG WebSocket | Header line. Connection: upgrade | 2018-08-11 12:50:50 CQG WebSocket | Header line. Sec-WebSocket-Accept: CPE8/XxKWaNUNT334QTriSJP9mo= | 2018-08-11 12:50:50 CQG WebSocket | Header line. Server: WebSocket++/0.7.0 | 2018-08-11 12:50:50 CQG WebSocket | Header line. Upgrade: websocket | 2018-08-11 12:50:50 CQG WebSocket | Header line. | 2018-08-11 12:50:50 CQG WebSocket | Web socket state is now open. | 2018-08-11 12:50:50 CQG FIX Trading | WebSocket connected. | 2018-08-11 12:50:50 CQG FIX Trading | Sending market data logon message. | 2018-08-11 12:50:50 CQG FIX Trading | Base Time: 2018-08-04T03:58:04. 2018-08-04 03:58:04 | 2018-08-11 12:50:51 CQG FIX Trading | Logon successful. Session Token = oAxpN7CQgPLSkLLSo0vRHyxineisbkAwyhouI8/o/scI7sJfqfqLL7v4yW4Vlmxb/AkN8eaGn6A | 2018-08-11 12:50:51 CQG FIX Trading | Connected to data and trading server. | 2018-08-11 12:50:51 CQG FIX: DisconnectFIX called. | 2018-08-11 12:51:10 CQG FIX: Sending a Logout message. | 2018-08-11 12:51:10 CQG FIX Trading | Sending Web API Logoff message. | 2018-08-11 12:51:10 CQG WebSocket socket (7) | Adding bytes from final send buffer from buffered socket: 17 | 2018-08-11 12:51:10 CQG WebSocket socket (7) | Initiating close of socket by core. | 2018-08-11 12:51:10 CQG WebSocket | WebSocket closed. | 2018-08-11 12:51:10 CQG FIX Trading | WebSocket closed. | 2018-08-11 12:51:10 CQG WebSocket socket (7) | Sending bytes from final send buffer: 17 | 2018-08-11 12:51:10 CQG WebSocket socket (7) | Write in progress. Shutdown being delayed. | 2018-08-11 12:51:10 CQG FIX Trading | Disconnected. | 2018-08-11 12:51:10 CQG FIX socket (6) | Initiating close of socket by core. | 2018-08-11 12:51:10 CQG FIX socket (6) | Write in progress. Shutdown being delayed. | 2018-08-11 12:51:10 CQG WebSocket socket (7) | Write has completed. Shutdown being performed. | 2018-08-11 12:51:10 CQG WebSocket socket (7) | Shutdown started. Waiting for graceful close. | 2018-08-11 12:51:10 Checking for new symbol settings for service code bitmex.dtc.trading | 2018-08-11 12:51:10 Current selected Data/Trading service: BitMEX Trading Direct | 2018-08-11 12:51:10 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2018-08-11 12:51:10 HTTPS connection to www.sierrachart.com:443 (8) | Creating socket. Using TLS 1.2. | 2018-08-11 12:51:10 HTTPS connection to www.sierrachart.com:443 (8) | Connecting to IP: 204.15.192.108. | 2018-08-11 12:51:10 CQG WebSocket socket (7) | Socket gracefully closed by remote side. | 2018-08-11 12:51:10 CQG WebSocket socket (7) | Closed. | 2018-08-11 12:51:10 CQG FIX socket (6) | Write has completed. Shutdown being performed. | 2018-08-11 12:51:10 CQG FIX socket (6) | Shutdown started. Waiting for graceful close. | 2018-08-11 12:51:10 CQG FIX socket (6) | Socket gracefully closed by remote side. | 2018-08-11 12:51:10 CQG FIX socket (6) | Closed. | 2018-08-11 12:51:10 Requesting symbol settings for service code bitmex.dtc.trading. Overwrite = on. | 2018-08-11 12:51:10 Symbol settings received. | 2018-08-11 12:51:10 Processed 5 symbol settings. | 2018-08-11 12:51:11 Your current service package does not support this function. Select 'Help >> Account Control Panel' to change your package. | 2018-08-11 12:51:13 * BitMEX Trading Direct | Disconnected. | 2018-08-11 12:51:13 HTTPS connection to www.sierrachart.com:443 (8) | Socket gracefully closed by remote side. | 2018-08-11 12:51:15 HTTPS connection to www.sierrachart.com:443 (8) | Received socket Close event. | 2018-08-11 12:51:15 HTTPS connection to www.sierrachart.com:443 (8) | Initiating close of socket by core. | 2018-08-11 12:51:15 HTTPS connection to www.sierrachart.com:443 (8) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2018-08-11 12:51:15 HTTPS connection to www.sierrachart.com:443 (8) | Closed. | 2018-08-11 12:51:15 |
 Data_Trade+Service+Settings+2018-08-09+00.52.48.png / V - Attached On 2018-08-11 12:54:25 UTC - Size: 60.5 KB - 265 views |
| [2018-08-11 20:58:56] |
| |
|
You need to use your own Sierra Chart account for support for that service: Direct Sierra Chart Account 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: 2018-08-11 20:59:04
|
| [2018-08-11 21:51:52] |
| User503358 - Posts: 50 |
|
Which minimum package do I need for my own account to enable cryptocurrencies?
Date Time Of Last Edit: 2018-08-12 23:06:28
|
| [2018-08-13 11:19:45] |
| User503358 - Posts: 50 |
|
I start new direct account, but I have no access to Bitmex data feed in Trial mode. May I use trial for new account, if I have active one?
|
| [2018-08-13 18:08:54] |
| |
|
You need just the standard service package 3. If you have already created your Sierra Chart account, then contact us here to activate it and make reference to this thread: https://www.sierrachart.com/usercp.php?page=SupportTickets Make sure you provide us your Account Name of the new account in the ticket. 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: 2018-08-13 18:09:36
|
| [2018-09-10 18:45:02] |
| User323476 - Posts: 1 |
|
I setup a free trial on SC which just expired yesturday. I was running the trial on the Bitmex datafeed. Today, my new broker account funded and when I was setting it up last week, I asked them to set me up with Sierra Charts package 5 with CQG datafeed for CME products. I recieved my SC and CQG credentials this morning. This SC account was supplied through my broker, OptimusFutures/Amp I'M confused because I would like to run both CME/CQG and Bitmex but it appears from this post Direct Sierra Chart Account at I need to purchase a second license from SC. Is this correct? Date Time Of Last Edit: 2018-09-10 18:46:25
|
| [2018-09-10 18:56:50] |
| |
|
You do not need to pay for a second Sierra Chart account. You just need to pay for your own direct account. But you will need your own direct account to use BitMex. So contact your broker and just let them know you will be paying for your own Sierra Chart account and to cancel the Service package 5 you are getting through them. 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: 2018-09-10 18:57:43
|
To post a message in this thread, you need to log in with your Sierra Chart account: