Support Board
Date/Time: Sat, 28 Dec 2024 08:52:03 +0000
Not Responding
View Count: 1119
| [2016-02-09 13:24:19] |
| User75519 - Posts: 15 |
|
ever since version 1366. i keep getting not responding on my chart when studies are calculating. nothing has been changed. and this is causing my data service to get disconnected cause there is no ping response from the chart
|
| [2016-02-09 14:43:44] |
| SC Developer - David - Posts: 660 |
|
Refer to these sections here: https://www.sierrachart.com/index.php?page=doc/helpdetails30.html#h30.16 https://www.sierrachart.com/index.php?page=doc/helpdetails30.html#h30.18 |
| [2016-02-09 14:49:53] |
| |
|
Can you provide us your Chartbook so we can look into this. Here are instructions: https://www.sierrachart.com/index.php?page=PostingInformation.php#AttachFile 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-02-09 15:33:01] |
| User75519 - Posts: 15 |
|
here is the chartbook
|
 NotResponding.cht - Attached On 2016-02-09 15:32:41 UTC - Size: 18 B - 299 views |
| [2016-02-09 18:58:32] |
| |
|
This Chartbook is empty. It contains no charts.
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-02-09 19:23:48] |
| User75519 - Posts: 15 |
|
here they are
|
Private File Private File |
| [2016-02-09 22:26:42] |
| |
|
We had a look at this and it confirms why we are afraid when asking for a Chartbook. This is too complicated for us to get involved with. Refer to help topic 30: http://www.sierrachart.com/index.php?page=doc/helpdetails30.html If you can determine what particular study is using more CPU usage compared to a prior version we can look into it. Otherwise, we cannot help with this. You can determine what study might be causing a problem by removing all studies from all charts and just working with one study at a time and see what you can determine. 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-02-10 00:54:16] |
| User75519 - Posts: 15 |
|
the thing is that the CPU is not being used more , I monitor CPU usage constintly
|
| [2016-02-10 04:14:52] |
| |
|
It does not make sense that you would not notice an increase in CPU usage of the Sierra Chart process when it is freezing as a result of study calculations. In any case, you need to go through a process of elimination by removing studies one by one and determine which one is causing a problem. If it is a Sierra Chart study, let us know which one and we will see if there has been any changes to it which would be causing this issue. If so, we will resolve that. 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 |
To post a message in this thread, you need to log in with your Sierra Chart account: