Support Board
Date/Time: Fri, 27 Dec 2024 17:14:38 +0000
any improvement in load capacity coming ?
View Count: 1608
| [2016-03-14 23:46:25] |
| User20450 - Posts: 330 |
|
wondering if there was any thing in the works to improve cpu load from sierra ? i see alot of posts on this and it creates a big lag on interaction within orders . uses very low ram but about 10-15% cpu , i have went through the section on lowering this and i havent been able to get it much lower , and lowering tick size on profile kinda defeats the purpose of the profile , even though this dosent change my issue at all maybe .5% cpu when i tun profiles off , all charts are less then 30 days off data , no spreadsheet studies thanks |
| [2016-03-15 04:32:42] |
| |
|
Previously we asked you to post an image of your TPO Profile Chart so we can understand what you are doing to see if we can make any performance improvements. Here are the instructions: https://www.sierrachart.com/index.php?page=PostingInformation.php#Image Also, Sierra Chart will support the easy launching of additional instances which receive data from the primary instance and also support trading . This will distribute CPU load among multiple CPU cores. We hope this will be out in about two weeks. 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 |
| [2016-03-15 12:13:37] |
| User20450 - Posts: 330 |
|
i understand that but i have taken my profile off ,closed it and still nothing , is there a way to share my chart book with u guys privately so the rest of the people cant access it ?
|
| [2016-03-16 02:05:33] |
| |
|
It is not possible for us to reliably determine the cause of high CPU usage by getting a Chartbook from a user that is apparently using a lot of CPU usage.
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: 2016-03-16 02:06:19
|
| [2016-03-16 12:35:05] |
| User20450 - Posts: 330 |
|
ok so how can i get this resolved as a paying customer ,?
|
| [2016-03-16 17:42:15] |
| |
|
Other than the information in help topic 30, it is the responsibility of the user to resolve this: Http://www.sierrachart.com/index.php?page=doc/helpdetails30.html As a matter of policy we would not get involved with a complex set up. Based upon what we have read so far, you should not be having a problem so it must be one of the items in help topic 30. The proper approach is to start with an empty Chartbook and then gradually add to it and see what is causing the high CPU usage. This is the only way to resolve this. 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: 2016-03-16 17:46:11
|
| [2016-03-16 17:45:13] |
| |
|
Corrections were made to the prior post and additional information added.
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: 2016-03-16 17:45:40
|
| [2016-03-17 17:29:53] |
| |
|
Next week we are going to be releasing a new feature to allow you to easily launch another instance of Sierra Chart. You can use that to distribute CPU load. Check back with us then. As we said previously, the basic procedure is going to be to start with a new Chartbook and do not use your existing Chartbooks. Gradually add to your set up until you begin to see a problem, then you can conclude what is causing the higher CPU usage. This is the only way. 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 |
| [2016-03-17 17:38:06] |
| User20450 - Posts: 330 |
|
Ok great I like that idea of splitting load as I think entry chart should have its own load Thanks |
| [2016-03-17 17:41:47] |
| |
|
By doing it this way and if you have a multi-CPU or core, this is another definite solution. You should be running an Intel CPU. Preferably the I7 class and it should be at least a quad core. We are actually working on this feature today and might even have it out this evening. 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 |
| [2016-03-17 18:49:41] |
| User20450 - Posts: 330 |
|
I run a i7 4790 4 ghz , 32 ram , double ssd, she's a beast , and only run sierra , but cpu runs about 10-15 % and lags interactions , Hopefully this fixes it , thanks again |
| [2016-03-18 12:31:41] |
| User20450 - Posts: 330 |
|
"As we said previously, the basic procedure is going to be to start with a new Chartbook and do not use your existing Chartbooks" would love to but there are no chart templates , so is there a way to build new chart book without having old one open and getting same built charts ? |
| [2016-03-18 16:30:22] |
| |
|
No but there would be no reason to use a template in this particular case because you need to start from a clean state to determine where the source of the problem is. You need to start simple and then gradually add to the set up until it becomes apparent what is causing the high CPU usage. 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 |
| [2016-03-21 17:58:16] |
| User20450 - Posts: 330 |
|
was this offered in 1384 version ?
|
| [2016-03-21 18:14:31] |
| |
|
Yes. Refer to: Introduction to DTC Server and Multiple Sierra Chart Instances 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 |
| [2016-03-22 01:15:01] |
| User20450 - Posts: 330 |
|
ok i tried to do new instance but one just keeps reconnecting and first ones goes from green to yellow and back and forth , neither one stay connected
|
| [2016-03-22 01:42:07] |
| |
|
Provide the Message Log from one of these instances. Provide a copy of the Message Log by following these instructions: http://www.sierrachart.com/index.php?l=PostingInformation.php#MessageLog 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 |
| [2016-03-22 11:16:17] |
| User20450 - Posts: 330 |
|
it just keeps repeating these messages over and over with no connection
|
 2016-03-22_07-15.jpg / V - Attached On 2016-03-22 11:15:30 UTC - Size: 301.84 KB - 303 views |
| [2016-03-22 18:02:29] |
| |
|
We need to see the text log as explained here: https://www.sierrachart.com/index.php?page=PostingInformation.php#MessageLog Restart Sierra Chart and when you start to notice the re-connections provide it at that time. 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 |
| [2016-03-22 20:47:13] |
| User20450 - Posts: 330 |
|
Software version: 1385 | 2016-03-22 07:19:13 Uses New Spreadsheets | 2016-03-22 07:19:13 Enabled for: Advanced Features. | 2016-03-22 07:19:13 Enabled for: Advanced Features 2. | 2016-03-22 07:19:13 Enabled for: Sierra Chart Historical Data Service. | 2016-03-22 07:19:13 Allow Support for Sierra Chart Data Feeds is enabled. | 2016-03-22 07:19:13 Current selected Data/Trading service: CQG FIX Trading | 2016-03-22 07:19:13 Chart Update Interval: 500 | 2016-03-22 07:19:13 Data/Trade Service Settings automatically set. | 2016-03-22 07:19:13 Time Zone: -04:00:00 (EST-05EDT+01,M3.2.0/02:00,M11.1.0/02:00) | 2016-03-22 07:19:13 2016-03-22 07:19:16 Local computer time | 2016-03-22 07:19:13 2016-03-22 11:19:16 Local computer time in UTC | 2016-03-22 07:19:13 2016-03-22 07:19:16 Local computer time in SC Time Zone | 2016-03-22 07:19:13 2016-03-22 11:19:13 Server time in UTC | 2016-03-22 07:19:13 Local computer UTC time and Server UTC time difference: 3 seconds. | 2016-03-22 07:19:13 Program path: E:\sierracharts\ | 2016-03-22 07:19:13 Data Files path: E:\sierracharts\Data\ | 2016-03-22 07:19:13 OS Version Number: 6.2 | 2016-03-22 07:19:13 Locale Information: C | 2016-03-22 07:19:13 Created the DTC Protocol server. | 2016-03-22 07:19:13 DTC Protocol Server listening on port 11099. | 2016-03-22 07:19:13 Created the DTC Protocol historical data server. | 2016-03-22 07:19:13 HD Server Manager | Listening on port 11098 | 2016-03-22 07:19:13 Checking for new symbol settings for cqg | 2016-03-22 07:19:13 HTTPS connection to www.sierrachart.com:443 (0) | Resolved address sierrachart.com to IP 5.9.8.236. | 2016-03-22 07:19:13 HTTPS connection to www.sierrachart.com:443 (3) | Connected. | 2016-03-22 07:19:13 HTTPS connection to www.sierrachart.com:443 (3) | Starting TLS 1.2 connection. | 2016-03-22 07:19:13 HTTPS connection to www.sierrachart.com:443 (3) | SSL connection established. | 2016-03-22 07:19:13 Requesting symbol settings for cqg. Overwrite = on. | 2016-03-22 07:19:17 Symbol settings received. | 2016-03-22 07:19:17 Processed received symbol settings | 2016-03-22 07:19:17 CQG FIX: Connecting to fixapi.cqgtrader.com. Port: 6912. | 2016-03-22 07:19:21 socket (0) | Resolved address fixapi.cqgtrader.com to IP 208.48.16.214. | 2016-03-22 07:19:21 socket (4) | Connected. | 2016-03-22 07:19:21 CQG FIX: Sending the Logon message. | 2016-03-22 07:19:21 CQG FIX Trading | Connected to trading server. | 2016-03-22 07:19:21 CQG FIX Trading | Connecting to market data server api.cqg.com | 2016-03-22 07:19:21 CQG WebAPI | Connecting to websocket server. | 2016-03-22 07:19:21 CQG FIX - FCM name: AMP | 2016-03-22 07:19:21 CQG WebAPI websocket (0) | Resolved address api.geo.cqg.com to IP 216.219.76.101. | 2016-03-22 07:19:22 CQG WebAPI websocket (5) | Connected. | 2016-03-22 07:19:22 CQG WebAPI websocket (5) | Starting SSL 3/2 connection. | 2016-03-22 07:19:22 HTTPS connection to www.sierrachart.com:443 (3) | SSL connection closed by remote side. | 2016-03-22 07:19:22 HTTPS connection to www.sierrachart.com:443 (3) | Connection gracefully closed by remote side. | 2016-03-22 07:19:22 HTTPS connection to www.sierrachart.com:443 (3) | SSL object has been freed. SSL state is now disconnected. | 2016-03-22 07:19:22 HTTPS connection to www.sierrachart.com:443 (3) | Shutdown and closed. | 2016-03-22 07:19:22 CQG WebAPI websocket (5) | SSL connection established. | 2016-03-22 07:19:22 CQG WebAPI | Opening websocket. | 2016-03-22 07:19:22 CQG WebAPI | Sending websocket handshake. | 2016-03-22 07:19:22 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-03-22 07:19:22 CQG WebAPI | Web socket state is now open. | 2016-03-22 07:19:22 CQG FIX Trading | Websocket connected. | 2016-03-22 07:19:22 CQG FIX Trading | Sending market data logon message. | 2016-03-22 07:19:22 CQG FIX Trading | Logon successful. Session Token = woCxUK1+UNhZDGG1uhKz7oGotNK6/Mz4sB+931XGYe0 | 2016-03-22 07:19:22 CQG FIX Trading | Connected to data and trading server. | 2016-03-22 07:19:22 Successfully copied E:\sierracharts\SierraChart.exe file to the folder E:\sierracharts\SierraChartInstance_2\ | 2016-03-22 07:19:57 Successfully copied E:\sierracharts\SierraChartSetup.exe file to the folder E:\sierracharts\SierraChartInstance_2\ | 2016-03-22 07:19:57 Successfully copied E:\sierracharts\SpreadsheetFileConverter.exe file to the folder E:\sierracharts\SierraChartInstance_2\ | 2016-03-22 07:19:57 CQG FIX: Received a Logout message. Text = Trader Baird2nd's session has been disconnected. This could be due to a second login using the same credentials. Contact Customer Support for assistance. | 2016-03-22 07:20:06 CQG FIX: Sending a Logout message. Text = Received Logout message. | 2016-03-22 07:20:06 socket (4) | Shutdown and closed. | 2016-03-22 07:20:06 CQG FIX: Disconnected. | 2016-03-22 07:20:06 Connection to the external service has been lost. | 2016-03-22 07:20:06 CQG FIX Trading | Sending Web API Logoff message. | 2016-03-22 07:20:06 CQG WebAPI websocket (5) | SSL shutdown indicates not able to send 'close notify'. | 2016-03-22 07:20:06 CQG WebAPI websocket (5) | SSL has been shut down. | 2016-03-22 07:20:06 CQG WebAPI websocket (5) | SSL object has been freed. SSL state is now disconnected. | 2016-03-22 07:20:06 CQG WebAPI websocket (5) | Shutdown and closed. | 2016-03-22 07:20:06 CQG WebAPI | Websocket closed. | 2016-03-22 07:20:06 CQG FIX Trading | Websocket closed. | 2016-03-22 07:20:06 CQG FIX Trading | Disconnected. | 2016-03-22 07:20:06 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-03-22 07:20:06 Remote instance connected: E:\sierracharts\SierraChartInstance_2\SierraChart.exe | 2016-03-22 07:20:06 CQG FIX: Connecting to fixapi.cqgtrader.com. Port: 6912. | 2016-03-22 07:20:09 socket (0) | Resolved address fixapi.cqgtrader.com to IP 208.48.16.214. | 2016-03-22 07:20:09 socket (6) | Connected. | 2016-03-22 07:20:09 CQG FIX: Sending the Logon message. | 2016-03-22 07:20:09 CQG FIX Trading | Connected to trading server. | 2016-03-22 07:20:09 CQG FIX Trading | Connecting to market data server api.cqg.com | 2016-03-22 07:20:09 CQG WebAPI | Connecting to websocket server. | 2016-03-22 07:20:09 CQG WebAPI websocket (0) | Resolved address api.geo.cqg.com to IP 216.219.76.101. | 2016-03-22 07:20:09 CQG FIX - FCM name: AMP | 2016-03-22 07:20:09 CQG WebAPI websocket (7) | Connected. | 2016-03-22 07:20:09 CQG WebAPI websocket (7) | Starting SSL 3/2 connection. | 2016-03-22 07:20:09 CQG WebAPI websocket (7) | SSL connection established. | 2016-03-22 07:20:09 CQG WebAPI | Opening websocket. | 2016-03-22 07:20:09 CQG WebAPI | Sending websocket handshake. | 2016-03-22 07:20:09 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-03-22 07:20:09 CQG WebAPI | Web socket state is now open. | 2016-03-22 07:20:09 CQG FIX Trading | Websocket connected. | 2016-03-22 07:20:09 CQG FIX Trading | Sending market data logon message. | 2016-03-22 07:20:09 CQG FIX Trading | Logon successful. Session Token = EUuyZqxdBfb8wyieIm2CooyoTGeqCy74sAPzMpha21k | 2016-03-22 07:20:10 CQG FIX Trading | Connected to data and trading server. | 2016-03-22 07:20:10 CQG FIX: Received a Logout message. Text = Trader Baird2nd's session has been disconnected. This could be due to a second login using the same credentials. Contact Customer Support for assistance. | 2016-03-22 07:20:12 CQG FIX: Sending a Logout message. Text = Received Logout message. | 2016-03-22 07:20:12 socket (6) | Shutdown and closed. | 2016-03-22 07:20:12 CQG FIX: Disconnected. | 2016-03-22 07:20:12 Connection to the external service has been lost. | 2016-03-22 07:20:12 CQG FIX Trading | Sending Web API Logoff message. | 2016-03-22 07:20:12 CQG WebAPI websocket (7) | SSL shutdown indicates not able to send 'close notify'. | 2016-03-22 07:20:12 CQG WebAPI websocket (7) | SSL has been shut down. | 2016-03-22 07:20:12 CQG WebAPI websocket (7) | SSL object has been freed. SSL state is now disconnected. | 2016-03-22 07:20:12 CQG WebAPI websocket (7) | Shutdown and closed. | 2016-03-22 07:20:12 CQG WebAPI | Websocket closed. | 2016-03-22 07:20:12 CQG FIX Trading | Websocket closed. | 2016-03-22 07:20:12 CQG FIX Trading | Disconnected. | 2016-03-22 07:20:12 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-03-22 07:20:12 Remote instance connected: E:\sierracharts\SierraChartInstance_2\SierraChart.exe | 2016-03-22 07:20:13 CQG FIX: Connecting to fixapi.cqgtrader.com. Port: 6912. | 2016-03-22 07:20:15 socket (0) | Resolved address fixapi.cqgtrader.com to IP 208.48.16.214. | 2016-03-22 07:20:15 socket (8) | Connected. | 2016-03-22 07:20:15 CQG FIX: Sending the Logon message. | 2016-03-22 07:20:15 CQG FIX Trading | Connected to trading server. | 2016-03-22 07:20:16 CQG FIX Trading | Connecting to market data server api.cqg.com | 2016-03-22 07:20:16 CQG WebAPI | Connecting to websocket server. | 2016-03-22 07:20:16 CQG WebAPI websocket (0) | Resolved address api.geo.cqg.com to IP 216.219.76.101. | 2016-03-22 07:20:16 CQG FIX - FCM name: AMP | 2016-03-22 07:20:16 CQG WebAPI websocket (9) | Connected. | 2016-03-22 07:20:16 CQG WebAPI websocket (9) | Starting SSL 3/2 connection. | 2016-03-22 07:20:16 CQG WebAPI websocket (9) | SSL connection established. | 2016-03-22 07:20:16 CQG WebAPI | Opening websocket. | 2016-03-22 07:20:16 CQG WebAPI | Sending websocket handshake. | 2016-03-22 07:20:16 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-03-22 07:20:16 CQG WebAPI | Web socket state is now open. | 2016-03-22 07:20:16 CQG FIX Trading | Websocket connected. | 2016-03-22 07:20:16 CQG FIX Trading | Sending market data logon message. | 2016-03-22 07:20:16 CQG FIX Trading | Logon successful. Session Token = Npfxqs1YM19kTHCVX5WgcxNFPBRITNq6z90ImrlHuUQ | 2016-03-22 07:20:16 CQG FIX Trading | Connected to data and trading server. | 2016-03-22 07:20:16 CQG FIX: Received a Logout message. Text = Trader Baird2nd's session has been disconnected. This could be due to a second login using the same credentials. Contact Customer Support for assistance. | 2016-03-22 07:20:19 CQG FIX: Sending a Logout message. Text = Received Logout message. | 2016-03-22 07:20:19 socket (8) | Shutdown and closed. | 2016-03-22 07:20:19 CQG FIX: Disconnected. | 2016-03-22 07:20:19 Connection to the external service has been lost. | 2016-03-22 07:20:19 CQG FIX Trading | Sending Web API Logoff message. | 2016-03-22 07:20:19 CQG WebAPI websocket (9) | SSL shutdown indicates not able to send 'close notify'. | 2016-03-22 07:20:19 CQG WebAPI websocket (9) | SSL has been shut down. | 2016-03-22 07:20:19 CQG WebAPI websocket (9) | SSL object has been freed. SSL state is now disconnected. | 2016-03-22 07:20:19 CQG WebAPI websocket (9) | Shutdown and closed. | 2016-03-22 07:20:19 CQG WebAPI | Websocket closed. | 2016-03-22 07:20:19 CQG FIX Trading | Websocket closed. | 2016-03-22 07:20:19 CQG FIX Trading | Disconnected. | 2016-03-22 07:20:19 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-03-22 07:20:19 Remote instance connected: E:\sierracharts\SierraChartInstance_2\SierraChart.exe | 2016-03-22 07:20:19 CQG FIX: Connecting to fixapi.cqgtrader.com. Port: 6912. | 2016-03-22 07:20:22 socket (0) | Resolved address fixapi.cqgtrader.com to IP 208.48.16.214. | 2016-03-22 07:20:22 socket (10) | Connected. | 2016-03-22 07:20:22 CQG FIX: Sending the Logon message. | 2016-03-22 07:20:22 CQG FIX Trading | Connected to trading server. | 2016-03-22 07:20:22 CQG FIX Trading | Connecting to market data server api.cqg.com | 2016-03-22 07:20:22 CQG WebAPI | Connecting to websocket server. | 2016-03-22 07:20:22 CQG WebAPI websocket (0) | Resolved address api.geo.cqg.com to IP 216.219.76.101. | 2016-03-22 07:20:22 CQG FIX - FCM name: AMP | 2016-03-22 07:20:22 CQG WebAPI websocket (11) | Connected. | 2016-03-22 07:20:22 CQG WebAPI websocket (11) | Starting SSL 3/2 connection. | 2016-03-22 07:20:22 CQG WebAPI websocket (11) | SSL connection established. | 2016-03-22 07:20:23 CQG WebAPI | Opening websocket. | 2016-03-22 07:20:23 CQG WebAPI | Sending websocket handshake. | 2016-03-22 07:20:23 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-03-22 07:20:23 CQG WebAPI | Web socket state is now open. | 2016-03-22 07:20:23 CQG FIX Trading | Websocket connected. | 2016-03-22 07:20:23 CQG FIX Trading | Sending market data logon message. | 2016-03-22 07:20:23 CQG FIX Trading | Logon successful. Session Token = HKcw60n+ctKYdOuJ1rKdXZw3B8XJVlNFWcMVLw3ozQo | 2016-03-22 07:20:23 CQG FIX Trading | Connected to data and trading server. | 2016-03-22 07:20:23 CQG FIX: Received a Logout message. Text = Trader Baird2nd's session has been disconnected. This could be due to a second login using the same credentials. Contact Customer Support for assistance. | 2016-03-22 07:20:25 CQG FIX: Sending a Logout message. Text = Received Logout message. | 2016-03-22 07:20:25 socket (10) | Shutdown and closed. | 2016-03-22 07:20:25 CQG FIX: Disconnected. | 2016-03-22 07:20:25 Connection to the external service has been lost. | 2016-03-22 07:20:25 CQG FIX Trading | Sending Web API Logoff message. | 2016-03-22 07:20:25 CQG WebAPI websocket (11) | SSL shutdown indicates not able to send 'close notify'. | 2016-03-22 07:20:25 CQG WebAPI websocket (11) | SSL has been shut down. | 2016-03-22 07:20:25 CQG WebAPI websocket (11) | SSL object has been freed. SSL state is now disconnected. | 2016-03-22 07:20:25 CQG WebAPI websocket (11) | Shutdown and closed. | 2016-03-22 07:20:25 CQG WebAPI | Websocket closed. | 2016-03-22 07:20:25 CQG FIX Trading | Websocket closed. | 2016-03-22 07:20:25 CQG FIX Trading | Disconnected. | 2016-03-22 07:20:25 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-03-22 07:20:25 Remote instance connected: E:\sierracharts\SierraChartInstance_2\SierraChart.exe | 2016-03-22 07:20:26 CQG FIX: Connecting to fixapi.cqgtrader.com. Port: 6912. | 2016-03-22 07:20:28 socket (0) | Resolved address fixapi.cqgtrader.com to IP 208.48.16.214. | 2016-03-22 07:20:28 socket (12) | Connected. | 2016-03-22 07:20:28 CQG FIX: Sending the Logon message. | 2016-03-22 07:20:29 CQG FIX Trading | Connected to trading server. | 2016-03-22 07:20:29 CQG FIX Trading | Connecting to market data server api.cqg.com | 2016-03-22 07:20:29 CQG WebAPI | Connecting to websocket server. | 2016-03-22 07:20:29 CQG WebAPI websocket (0) | Resolved address api.geo.cqg.com to IP 216.219.76.101. | 2016-03-22 07:20:29 CQG FIX - FCM name: AMP | 2016-03-22 07:20:29 CQG WebAPI websocket (13) | Connected. | 2016-03-22 07:20:29 CQG WebAPI websocket (13) | Starting SSL 3/2 connection. | 2016-03-22 07:20:29 CQG WebAPI websocket (13) | SSL connection established. | 2016-03-22 07:20:29 CQG WebAPI | Opening websocket. | 2016-03-22 07:20:29 CQG WebAPI | Sending websocket handshake. | 2016-03-22 07:20:29 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-03-22 07:20:29 CQG WebAPI | Web socket state is now open. | 2016-03-22 07:20:29 CQG FIX Trading | Websocket connected. | 2016-03-22 07:20:29 CQG FIX Trading | Sending market data logon message. | 2016-03-22 07:20:29 CQG FIX Trading | Logon successful. Session Token = QiWLLWcqrKrJqeIraTX4k8cdGo3NMkLFW6awXXzmPN0 | 2016-03-22 07:20:29 CQG FIX Trading | Connected to data and trading server. | 2016-03-22 07:20:29 CQG FIX: Received a Logout message. Text = Trader Baird2nd's session has been disconnected. This could be due to a second login using the same credentials. Contact Customer Support for assistance. | 2016-03-22 07:20:32 CQG FIX: Sending a Logout message. Text = Received Logout message. | 2016-03-22 07:20:32 socket (12) | Shutdown and closed. | 2016-03-22 07:20:32 CQG FIX: Disconnected. | 2016-03-22 07:20:32 Connection to the external service has been lost. | 2016-03-22 07:20:32 CQG FIX Trading | Sending Web API Logoff message. | 2016-03-22 07:20:32 CQG WebAPI websocket (13) | SSL shutdown indicates not able to send 'close notify'. | 2016-03-22 07:20:32 CQG WebAPI websocket (13) | SSL has been shut down. | 2016-03-22 07:20:32 CQG WebAPI websocket (13) | SSL object has been freed. SSL state is now disconnected. | 2016-03-22 07:20:32 CQG WebAPI websocket (13) | Shutdown and closed. | 2016-03-22 07:20:32 CQG WebAPI | Websocket closed. | 2016-03-22 07:20:32 CQG FIX Trading | Websocket closed. | 2016-03-22 07:20:32 CQG FIX Trading | Disconnected. | 2016-03-22 07:20:32 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-03-22 07:20:32 Remote instance connected: E:\sierracharts\SierraChartInstance_2\SierraChart.exe | 2016-03-22 07:20:33 CQG FIX: Connecting to fixapi.cqgtrader.com. Port: 6912. | 2016-03-22 07:20:35 socket (0) | Resolved address fixapi.cqgtrader.com to IP 208.48.16.214. | 2016-03-22 07:20:35 socket (14) | Connected. | 2016-03-22 07:20:35 CQG FIX: Sending the Logon message. | 2016-03-22 07:20:35 CQG FIX Trading | Connected to trading server. | 2016-03-22 07:20:35 CQG FIX Trading | Connecting to market data server api.cqg.com | 2016-03-22 07:20:35 CQG WebAPI | Connecting to websocket server. | 2016-03-22 07:20:35 CQG WebAPI websocket (0) | Resolved address api.geo.cqg.com to IP 216.219.76.101. | 2016-03-22 07:20:35 CQG FIX - FCM name: AMP | 2016-03-22 07:20:35 CQG WebAPI websocket (15) | Connected. | 2016-03-22 07:20:35 CQG WebAPI websocket (15) | Starting SSL 3/2 connection. | 2016-03-22 07:20:35 CQG WebAPI websocket (15) | SSL connection established. | 2016-03-22 07:20:36 CQG WebAPI | Opening websocket. | 2016-03-22 07:20:36 CQG WebAPI | Sending websocket handshake. | 2016-03-22 07:20:36 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-03-22 07:20:36 CQG WebAPI | Web socket state is now open. | 2016-03-22 07:20:36 CQG FIX Trading | Websocket connected. | 2016-03-22 07:20:36 CQG FIX Trading | Sending market data logon message. | 2016-03-22 07:20:36 CQG FIX Trading | Logon successful. Session Token = Lux0JOS5SNCKNybxtWCdF8q9gLwxxAoVDqo00kgoG+s | 2016-03-22 07:20:36 CQG FIX Trading | Connected to data and trading server. | 2016-03-22 07:20:36 CQG FIX: Received a Logout message. Text = Trader Baird2nd's session has been disconnected. This could be due to a second login using the same credentials. Contact Customer Support for assistance. | 2016-03-22 07:20:39 CQG FIX: Sending a Logout message. Text = Received Logout message. | 2016-03-22 07:20:39 socket (14) | Shutdown and closed. | 2016-03-22 07:20:39 CQG FIX: Disconnected. | 2016-03-22 07:20:39 Connection to the external service has been lost. | 2016-03-22 07:20:39 CQG FIX Trading | Sending Web API Logoff message. | 2016-03-22 07:20:39 CQG WebAPI websocket (15) | SSL shutdown indicates not able to send 'close notify'. | 2016-03-22 07:20:39 CQG WebAPI websocket (15) | SSL has been shut down. | 2016-03-22 07:20:39 CQG WebAPI websocket (15) | SSL object has been freed. SSL state is now disconnected. | 2016-03-22 07:20:39 CQG WebAPI websocket (15) | Shutdown and closed. | 2016-03-22 07:20:39 CQG WebAPI | Websocket closed. | 2016-03-22 07:20:39 CQG FIX Trading | Websocket closed. | 2016-03-22 07:20:39 CQG FIX Trading | Disconnected. | 2016-03-22 07:20:39 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-03-22 07:20:39 Remote instance connected: E:\sierracharts\SierraChartInstance_2\SierraChart.exe | 2016-03-22 07:20:39 CQG FIX: Connecting to fixapi.cqgtrader.com. Port: 6912. | 2016-03-22 07:20:42 socket (0) | Resolved address fixapi.cqgtrader.com to IP 208.48.16.214. | 2016-03-22 07:20:42 socket (16) | Connected. | 2016-03-22 07:20:42 CQG FIX: Sending the Logon message. | 2016-03-22 07:20:42 CQG FIX Trading | Connected to trading server. | 2016-03-22 07:20:42 CQG FIX Trading | Connecting to market data server api.cqg.com | 2016-03-22 07:20:42 CQG WebAPI | Connecting to websocket server. | 2016-03-22 07:20:42 CQG WebAPI websocket (0) | Resolved address api.geo.cqg.com to IP 216.219.76.101. | 2016-03-22 07:20:42 CQG FIX - FCM name: AMP | 2016-03-22 07:20:42 CQG WebAPI websocket (17) | Connected. | 2016-03-22 07:20:42 CQG WebAPI websocket (17) | Starting SSL 3/2 connection. | 2016-03-22 07:20:42 CQG WebAPI websocket (17) | SSL connection established. | 2016-03-22 07:20:42 CQG WebAPI | Opening websocket. | 2016-03-22 07:20:42 CQG WebAPI | Sending websocket handshake. | 2016-03-22 07:20:42 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-03-22 07:20:42 CQG WebAPI | Web socket state is now open. | 2016-03-22 07:20:42 CQG FIX Trading | Websocket connected. | 2016-03-22 07:20:42 CQG FIX Trading | Sending market data logon message. | 2016-03-22 07:20:42 CQG FIX Trading | Logon successful. Session Token = rOEpueTTtgXH9zd8NnCBFr4G5B66tQLUltmtwvgEwQU | 2016-03-22 07:20:42 CQG FIX Trading | Connected to data and trading server. | 2016-03-22 07:20:42 CQG FIX: Received a Logout message. Text = Trader Baird2nd's session has been disconnected. This could be due to a second login using the same credentials. Contact Customer Support for assistance. | 2016-03-22 07:20:45 CQG FIX: Sending a Logout message. Text = Received Logout message. | 2016-03-22 07:20:45 socket (16) | Shutdown and closed. | 2016-03-22 07:20:45 CQG FIX: Disconnected. | 2016-03-22 07:20:45 Connection to the external service has been lost. | 2016-03-22 07:20:45 CQG FIX Trading | Sending Web API Logoff message. | 2016-03-22 07:20:45 CQG WebAPI websocket (17) | SSL shutdown indicates not able to send 'close notify'. | 2016-03-22 07:20:45 CQG WebAPI websocket (17) | SSL has been shut down. | 2016-03-22 07:20:45 CQG WebAPI websocket (17) | SSL object has been freed. SSL state is now disconnected. | 2016-03-22 07:20:45 CQG WebAPI websocket (17) | Shutdown and closed. | 2016-03-22 07:20:45 CQG WebAPI | Websocket closed. | 2016-03-22 07:20:45 CQG FIX Trading | Websocket closed. | 2016-03-22 07:20:45 CQG FIX Trading | Disconnected. | 2016-03-22 07:20:45 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-03-22 07:20:45 Remote instance connected: E:\sierracharts\SierraChartInstance_2\SierraChart.exe | 2016-03-22 07:20:46 CQG FIX: Connecting to fixapi.cqgtrader.com. Port: 6912. | 2016-03-22 07:20:48 socket (0) | Resolved address fixapi.cqgtrader.com to IP 208.48.16.214. | 2016-03-22 07:20:48 socket (18) | Connected. | 2016-03-22 07:20:48 CQG FIX: Sending the Logon message. | 2016-03-22 07:20:48 CQG FIX Trading | Connected to trading server. | 2016-03-22 07:20:48 CQG FIX Trading | Connecting to market data server api.cqg.com | 2016-03-22 07:20:48 CQG WebAPI | Connecting to websocket server. | 2016-03-22 07:20:48 CQG WebAPI websocket (0) | Resolved address api.geo.cqg.com to IP 216.219.76.101. | 2016-03-22 07:20:48 CQG FIX - FCM name: AMP | 2016-03-22 07:20:48 CQG WebAPI websocket (19) | Connected. | 2016-03-22 07:20:49 CQG WebAPI websocket (19) | Starting SSL 3/2 connection. | 2016-03-22 07:20:49 CQG WebAPI websocket (19) | SSL connection established. | 2016-03-22 07:20:49 CQG WebAPI | Opening websocket. | 2016-03-22 07:20:49 CQG WebAPI | Sending websocket handshake. | 2016-03-22 07:20:49 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-03-22 07:20:49 CQG WebAPI | Web socket state is now open. | 2016-03-22 07:20:49 CQG FIX Trading | Websocket connected. | 2016-03-22 07:20:49 CQG FIX Trading | Sending market data logon message. | 2016-03-22 07:20:49 CQG FIX Trading | Logon successful. Session Token = hDj1VLXU9yOELPlWS+air4E82Xxdq7KjC6e52p8rph0 | 2016-03-22 07:20:49 CQG FIX Trading | Connected to data and trading server. | 2016-03-22 07:20:49 CQG FIX: Received a Logout message. Text = Trader Baird2nd's session has been disconnected. This could be due to a second login using the same credentials. Contact Customer Support for assistance. | 2016-03-22 07:20:52 CQG FIX: Sending a Logout message. Text = Received Logout message. | 2016-03-22 07:20:52 socket (18) | Shutdown and closed. | 2016-03-22 07:20:52 CQG FIX: Disconnected. | 2016-03-22 07:20:52 Connection to the external service has been lost. | 2016-03-22 07:20:52 CQG FIX Trading | Sending Web API Logoff message. | 2016-03-22 07:20:52 CQG WebAPI websocket (19) | SSL shutdown indicates not able to send 'close notify'. | 2016-03-22 07:20:52 CQG WebAPI websocket (19) | SSL has been shut down. | 2016-03-22 07:20:52 CQG WebAPI websocket (19) | SSL object has been freed. SSL state is now disconnected. | 2016-03-22 07:20:52 CQG WebAPI websocket (19) | Shutdown and closed. | 2016-03-22 07:20:52 CQG WebAPI | Websocket closed. | 2016-03-22 07:20:52 CQG FIX Trading | Websocket closed. | 2016-03-22 07:20:52 CQG FIX Trading | Disconnected. | 2016-03-22 07:20:52 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-03-22 07:20:52 CQG FIX: Connecting to fixapi.cqgtrader.com. Port: 6912. | 2016-03-22 07:20:55 socket (0) | Resolved address fixapi.cqgtrader.com to IP 208.48.16.214. | 2016-03-22 07:20:55 socket (20) | Connected. | 2016-03-22 07:20:55 CQG FIX: Sending the Logon message. | 2016-03-22 07:20:55 CQG FIX Trading | Connected to trading server. | 2016-03-22 07:20:55 CQG FIX Trading | Connecting to market data server api.cqg.com | 2016-03-22 07:20:55 CQG WebAPI | Connecting to websocket server. | 2016-03-22 07:20:55 CQG WebAPI websocket (0) | Resolved address api.geo.cqg.com to IP 216.219.76.101. | 2016-03-22 07:20:55 CQG FIX - FCM name: AMP | 2016-03-22 07:20:55 CQG WebAPI websocket (21) | Connected. | 2016-03-22 07:20:55 CQG WebAPI websocket (21) | Starting SSL 3/2 connection. | 2016-03-22 07:20:55 CQG WebAPI websocket (21) | SSL connection established. | 2016-03-22 07:20:55 CQG WebAPI | Opening websocket. | 2016-03-22 07:20:55 CQG WebAPI | Sending websocket handshake. | 2016-03-22 07:20:55 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-03-22 07:20:55 CQG WebAPI | Web socket state is now open. | 2016-03-22 07:20:55 CQG FIX Trading | Websocket connected. | 2016-03-22 07:20:55 CQG FIX Trading | Sending market data logon message. | 2016-03-22 07:20:55 CQG FIX Trading | Logon successful. Session Token = ZubpR2Qj+llJyWhFvpOErbp2MuSMrnbTMtTRSebzDrw | 2016-03-22 07:20:56 CQG FIX Trading | Connected to data and trading server. | 2016-03-22 07:20:56 CQG FIX Trading | Starting real-time market data updates for: F.US.CLEK16. ID: 1 | 2016-03-22 07:33:51 CQG FIX Trading | Sending symbol resolution request for F.US.CLEK16. ID: 3164 | 2016-03-22 07:33:51 Intraday data recording state for symbol F.US.CLEK16 is set to download 'Pending'. | 2016-03-22 07:33:51 Delaying start of download for F.US.CLEK16 | 2016-03-22 07:33:51 CQG FIX Trading | Received symbol resolution report for symbol F.US.CLEK16. Request ID: 3164. Contract ID: 1. | 2016-03-22 07:33:51 CQG FIX Trading | Requesting market data for F.US.CLEK16 | 2016-03-22 07:33:51 CQG FIX Trading | Starting real-time market data updates for: F.US.USAM16. ID: 2 | 2016-03-22 07:33:51 CQG FIX Trading | Sending symbol resolution request for F.US.USAM16. ID: 3165 | 2016-03-22 07:33:51 Intraday data recording state for symbol F.US.USAM16 is set to download 'Pending'. | 2016-03-22 07:33:51 HD Request # 2 | Downloading Intraday chart data for F.US.CLEK16 to the file F.US.CLEK16.scid. Service: cqg | 2016-03-22 07:33:51 HD Request # 2 | Download start Date-Time: 2016-03-22 07:18:59.000 | 2016-03-22 07:33:51 HD Request # 2 | Using server: ds5.sierracharts.com port 10149 | 2016-03-22 07:33:51 Socket (0) | Resolved address ds5.sierracharts.com to IP 204.15.192.106. | 2016-03-22 07:33:51 CQG FIX Trading | Received symbol resolution report for symbol F.US.USAM16. Request ID: 3165. Contract ID: 2. | 2016-03-22 07:33:51 CQG FIX Trading | Requesting market data for F.US.USAM16 | 2016-03-22 07:33:51 CQG FIX Trading | Starting real-time market data updates for: F.US.EPM16. ID: 3 | 2016-03-22 07:33:51 CQG FIX Trading | Sending symbol resolution request for F.US.EPM16. ID: 3166 | 2016-03-22 07:33:51 Intraday data recording state for symbol F.US.EPM16 is set to download 'Pending'. | 2016-03-22 07:33:51 Socket (29) | Connected. | 2016-03-22 07:33:51 HD Request # 2 | Sending historical data logon request message. | 2016-03-22 07:33:51 Requesting market depth updates for: F.US.CLEK16 if supported. | 2016-03-22 07:33:51 CQG FIX Trading | Requesting market data including full depth for F.US.CLEK16 | 2016-03-22 07:33:51 Requesting market depth updates for: F.US.EPM16 if supported. | 2016-03-22 07:33:51 Requesting market depth updates for: F.US.USAM16 if supported. | 2016-03-22 07:33:51 CQG FIX Trading | Requesting market data including full depth for F.US.USAM16 | 2016-03-22 07:33:51 CQG FIX Trading | Received symbol resolution report for symbol F.US.EPM16. Request ID: 3166. Contract ID: 3. | 2016-03-22 07:33:51 CQG FIX Trading | Requesting market data including full depth for F.US.EPM16 | 2016-03-22 07:33:51 HD Request # 2 | Requesting Intraday data. Start Date-Time: 2016-03-22 07:18:59. Record interval: 0. Symbol: F.US.CLEK16 | 2016-03-22 07:33:52 HD Request # 2 | Decompressing data. | 2016-03-22 07:33:52 HD Request # 2 | Receiving Intraday data for F.US.CLEK16 starting at 2016-03-22 07:18:59 | 2016-03-22 07:33:52 HD Request # 2 | Timestamp of first Intraday data file record written: 2016-03-22 07:19:00 | 2016-03-22 07:33:52 Socket (29) | Shutdown and closed. | 2016-03-22 07:33:52 The network socket for historical data has been closed. | 2016-03-22 07:33:52 HD Request # 2 | Received 1971 records from 2016-03-22 07:18:59 to 2016-03-22 07:33:42 (14.7 minutes) and wrote 1970 records for F.US.CLEK16 | 2016-03-22 07:33:52 HD Request # 2 | Intraday download COMPLETE for F.US.CLEK16. Completion time: 1s. Unique request ID: 1 | 2016-03-22 07:33:52 Removed historical data download ID 1 | 2016-03-22 07:33:52 Real-time Intraday chart data file updates started for F.US.CLEK16 | 2016-03-22 07:33:52 Opened cached Intraday file: E:\sierracharts\Data\F.US.CLEK16.scid | 2016-03-22 07:33:52 Intraday chart data file opened for F.US.CLEK16 | 2016-03-22 07:33:52 Delaying start of download for F.US.USAM16 | 2016-03-22 07:33:52 HD Request # 3 | Downloading Intraday chart data for F.US.USAM16 to the file F.US.USAM16.scid. Service: cqg | 2016-03-22 07:33:55 HD Request # 3 | Download start Date-Time: 2016-03-22 07:18:28.000 | 2016-03-22 07:33:55 HD Request # 3 | Using server: ds4.sierracharts.com port 10149 | 2016-03-22 07:33:55 Socket (0) | Resolved address ds4.sierracharts.com to IP 204.11.49.26. | 2016-03-22 07:33:55 Socket (30) | Connected. | 2016-03-22 07:33:55 HD Request # 3 | Sending historical data logon request message. | 2016-03-22 07:33:55 HD Request # 3 | Requesting Intraday data. Start Date-Time: 2016-03-22 07:18:28. Record interval: 0. Symbol: F.US.USAM16 | 2016-03-22 07:33:55 HD Request # 3 | Decompressing data. | 2016-03-22 07:33:55 HD Request # 3 | Receiving Intraday data for F.US.USAM16 starting at 2016-03-22 07:19:24 | 2016-03-22 07:33:55 HD Request # 3 | Timestamp of first Intraday data file record written: 2016-03-22 07:19:24 | 2016-03-22 07:33:55 Socket (30) | Shutdown and closed. | 2016-03-22 07:33:55 The network socket for historical data has been closed. | 2016-03-22 07:33:55 HD Request # 3 | Received 636 records from 2016-03-22 07:19:24 to 2016-03-22 07:33:48 (14.4 minutes) and wrote 636 records for F.US.USAM16 | 2016-03-22 07:33:55 HD Request # 3 | Intraday download COMPLETE for F.US.USAM16. Completion time: 1s. Unique request ID: 2 | 2016-03-22 07:33:55 Removed historical data download ID 2 | 2016-03-22 07:33:55 Real-time Intraday chart data file updates started for F.US.USAM16 | 2016-03-22 07:33:55 Opened cached Intraday file: E:\sierracharts\Data\F.US.USAM16.scid | 2016-03-22 07:33:55 Intraday chart data file opened for F.US.USAM16 | 2016-03-22 07:33:55 HD Request # 4 | Downloading Intraday chart data for F.US.EPM16 to the file F.US.EPM16.scid. Service: cqg | 2016-03-22 07:33:55 HD Request # 4 | Download start Date-Time: 2016-03-22 07:18:59.000 | 2016-03-22 07:33:55 HD Request # 4 | Using server: ds3.sierracharts.com port 10149 | 2016-03-22 07:33:55 Socket (0) | Resolved address ds3.sierracharts.com to IP 65.182.172.164. | 2016-03-22 07:33:55 Socket (31) | Connected. | 2016-03-22 07:33:55 HD Request # 4 | Sending historical data logon request message. | 2016-03-22 07:33:55 HD Request # 4 | Requesting Intraday data. Start Date-Time: 2016-03-22 07:18:59. Record interval: 0. Symbol: F.US.EPM16 | 2016-03-22 07:33:55 HD Request # 4 | Decompressing data. | 2016-03-22 07:33:55 HD Request # 4 | Receiving Intraday data for F.US.EPM16 starting at 2016-03-22 07:19:05 | 2016-03-22 07:33:55 HD Request # 4 | Timestamp of first Intraday data file record written: 2016-03-22 07:19:05 | 2016-03-22 07:33:55 Socket (31) | Shutdown and closed. | 2016-03-22 07:33:55 The network socket for historical data has been closed. | 2016-03-22 07:33:55 HD Request # 4 | Received 2333 records from 2016-03-22 07:19:05 to 2016-03-22 07:33:50 (14.8 minutes) and wrote 2333 records for F.US.EPM16 | 2016-03-22 07:33:55 Added 2 Time and Sales records to Intraday data file for F.US.EPM16 after download. | 2016-03-22 07:33:55 HD Request # 4 | Intraday download COMPLETE for F.US.EPM16. Completion time: 0s. Unique request ID: 3 | 2016-03-22 07:33:55 Removed historical data download ID 3 | 2016-03-22 07:33:55 Real-time Intraday chart data file updates started for F.US.EPM16 | 2016-03-22 07:33:55 Opened cached Intraday file: E:\sierracharts\Data\F.US.EPM16.scid | 2016-03-22 07:33:55 Intraday chart data file opened for F.US.EPM16 | 2016-03-22 07:33:55 F.US.CLEK16 10 Sec #7 | Reloading chart. | 2016-03-22 07:34:16 F.US.CLEK16 500 Trades #3 | Reloading chart. | 2016-03-22 07:36:02 F.US.CLEK16 500 Trades #3 | Reloading chart. | 2016-03-22 07:36:18 F.US.CLEK16 500 Trades #3 | Reloading chart. | 2016-03-22 07:37:17 F.US.CLEK16 500 Trades #3 | Reloading chart. | 2016-03-22 07:37:31 F.US.CLEK16 500 Trades #3 | Reloading chart. | 2016-03-22 07:37:35 F.US.CLEK16 500 Trades #3 | Reloading chart. | 2016-03-22 07:38:10 F.US.CLEK16 500 Trades #3 | Reloading chart. | 2016-03-22 07:38:58 |
| [2016-03-22 22:41:19] |
| |
|
This is the relevant message: CQG FIX: Received a Logout message. Text = Trader Baird2nd's session has been disconnected. This could be due to a second login using the same credentials. Contact Customer Support for assistance. | 2016-03-22 07:20:52
You are misunderstanding about how additional instances are meant to be used. You are not supposed to change the Service being used. It needs to be left at the default setting of DTC - Sub Instance. There is nothing special to do. The connection is handled automatically and uses the main instance connection. 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 |
| [2016-03-22 22:43:13] |
| User20450 - Posts: 330 |
|
i didnt change anything i just hit new instance , i didnt touch anything else
|
| [2016-03-22 22:51:02] |
| zippyzip - Posts: 293 |
|
fwiw i get data from cqg , the DTC sub says not included in my package , but i do have package 5 from broker is this the problem ? |
| [2016-03-22 23:14:18] |
| |
|
The DTC Sub Instance service is now allowed on your account. Restart Sierra Chart. 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 |
| [2016-03-22 23:19:09] |
| zippyzip - Posts: 293 |
|
thank u
|
To post a message in this thread, you need to log in with your Sierra Chart account: