Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sun, 28 Apr 2024 17:41:17 +0000
Volume at Price Threshold V2 Indicator - Recalculate
View Count: 1366
| [2017-01-31 14:21:31] |
| User104854 - Posts: 441 |
|
Hi. I use the Volume at Price Threshold Alert V2 indicator. I use it to draw lines at volume imbalances. As a new bar is created it leaves lines that are later invalidated as the volume on the other side changes. Once the bar is complete I have to hit re-calculate in order for it to refresh and remove these lines. Is there a way that I can have my chart auto-recalculate after each bar is created? Thanks.
|
| [2017-01-31 16:09:01] |
| |
|
We understand the reason for this problem. This will be resolved in the next release.
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 |
| [2017-02-08 20:44:53] |
| User104854 - Posts: 441 |
|
After I received this message from you I downloaded the latest pre-release and the line problem was resolved. The Sierra Chart program started going into 'not responding' mode quite often when I would reload charts which had never happened before. I then downloaded the latest version. The 'not responding' problem is resolved but the line problem is back. I have to re-calculate so that the lines on the V2 indicator will be accurate. Can you help? Thanks.
|
| [2017-02-08 21:31:33] |
| |
|
but the line problem is back.
This is because you are running version 1510. Not the latest prerelease.In regards to the problem of Sierra Chart not responding at times in the latest prereleases, we are not sure why that is happening. Some users are reporting that. But we have yet to determine the cause or even be able to reproduce it. 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 |
| [2017-02-08 23:19:22] |
| User104854 - Posts: 441 |
|
Ok. When does a pre-release turn into an actual version? Is that how it works? If so, when would this happen? Thanks.
|
| [2017-02-09 17:29:39] |
| |
|
We do not know the answer to this question other than to say this is a variable amount of time. The issue with the prerelease has been resolved but give us a few more days to do a more thorough review to make sure there are no further issues. 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 |
| [2017-02-10 14:04:07] |
| User104854 - Posts: 441 |
|
Everything appears to be working perfectly with the new pre-release. Thought you'd appreciate the feedback. Thank you.
|
| [2017-02-14 14:27:36] |
| User104854 - Posts: 441 |
|
I am still running into problems when I reload data with the program not responding and freezing the program. It typically happens when I reload my charts on replay. This has not happened before but seems to be happening with this latest pre-release. It sounds like others have had this issue as well. Please look into it.
|
| [2017-02-14 15:01:22] |
| User104854 - Posts: 441 |
|
Now every time I start the program and it's loading it says not responding before the data loads. I'm having issues even opening the program. Do I need to go back to a previous version?
|
| [2017-02-14 15:24:49] |
| |
|
What version of Sierra Chart are you having this with? We are not aware of any problem with version 1518.
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 |
| [2017-02-14 15:33:14] |
| User104854 - Posts: 441 |
|
1517. I'll update to 1518. I notice that you have a twitter account. Is that the best place to see when there are updates? I just checked the most recent tweet from you and it says that 1519 is out.
|
| [2017-02-14 15:42:00] |
| |
|
Yes use version 1518. And disregard Twitter. That is going to be removed immediately. 1519 is a prerelease but apparently there is an issue with it and it has been removed. 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 |
| [2017-02-14 16:08:28] |
| User104854 - Posts: 441 |
|
It seems like Twitter is the perfect way to let your users know when there is a new version out. There doesn't seem to be any type of communication to let us know when we need to update. Every time I've asked when I can find out when a new release is out I've never gotten a straight answer. If you have a solution please let me know.
|
| [2017-02-14 16:48:18] |
| User104854 - Posts: 441 |
|
I still don't understand when to download the current version or the pre-release. I downloaded the current version and it turns out that it was 1517. If I click on pre-release, where does it say that I will be putting version 1518 on my computer. I'd like to know before I actually install it. Thanks.
|
| [2017-02-14 17:00:38] |
| User104854 - Posts: 441 |
|
I am trying to download the latest pre-release and it keeps telling me it failed due to an error. A copy of the log is below. Please advise. Software version: 1517 | 2017-02-14 08:57:47 Uses New Spreadsheets | 2017-02-14 08:57:47 Usage end date: 2017-03-17 | 2017-02-14 08:57:47 Enabled for: Advanced Features. | 2017-02-14 08:57:47 Enabled for: Advanced Features 2. | 2017-02-14 08:57:47 Enabled for: Sierra Chart Historical Data Service. | 2017-02-14 08:57:47 Allow Support for Sierra Chart Data Feeds is enabled. | 2017-02-14 08:57:47 Current selected Data/Trading service: CQG FIX Trading | 2017-02-14 08:57:47 Chart Update Interval: 500 | 2017-02-14 08:57:47 Time Zone: -08:00:00 (PST-08PDT+01,M3.2.0/02:00,M11.1.0/02:00) | 2017-02-14 08:57:47 2017-02-14 08:57:47 Local computer time | 2017-02-14 08:57:47 2017-02-14 16:57:47 Local computer time in UTC | 2017-02-14 08:57:47 2017-02-14 08:57:47 Local computer time in SC Time Zone | 2017-02-14 08:57:47 2017-02-14 16:55:16 Server time in UTC | 2017-02-14 08:57:47 Local computer UTC time and Server UTC time difference: 1 seconds. | 2017-02-14 08:57:47 Program path: C:\SierraChart\ | 2017-02-14 08:57:47 Data Files path: C:\SierraChart\Data\ | 2017-02-14 08:57:47 OS Version Number: 6.2 | 2017-02-14 08:57:47 Locale Setting: C | 2017-02-14 08:57:47 A request for the latest software update has been made. | 2017-02-14 08:57:55 * The update is being downloaded in the background. When it is complete, you will be prompted. | 2017-02-14 08:57:55 * HTTP connection to www.sierrachart.com:80 (15) | Creating socket. | 2017-02-14 08:57:55 HTTP connection to www.sierrachart.com:80 (15) | Socket gracefully closed by remote side. | 2017-02-14 08:58:17 HTTP connection to www.sierrachart.com:80 (15) | Received socket Close event | 2017-02-14 08:58:17 HTTP connection to www.sierrachart.com:80 (15) | Adding bytes from final send buffer from buffered socket: 252 | 2017-02-14 08:58:17 HTTP connection to www.sierrachart.com:80 (15) | Initiating close of socket by core. | 2017-02-14 08:58:17 Failed to download software update due to an error. Request ID: 4. | 2017-02-14 08:58:17 * HTTP connection to www.sierrachart.com:80 (15) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2017-02-14 08:58:17 HTTP connection to www.sierrachart.com:80 (15) | Closed. | 2017-02-14 08:58:17 File >> Disconnect selected. | 2017-02-14 08:58:32 CQG FIX: DisconnectFIX called. | 2017-02-14 08:58:32 CQG FIX: Sending a Logout message. | 2017-02-14 08:58:32 CQG FIX Trading | Sending Web API Logoff message. | 2017-02-14 08:58:32 CQG WebAPI websocket (12) | Adding bytes from final send buffer from buffered socket: 8 | 2017-02-14 08:58:32 CQG WebAPI websocket (12) | Initiating close of socket by core. | 2017-02-14 08:58:32 CQG WebAPI | Websocket closed. | 2017-02-14 08:58:32 CQG WebAPI websocket (12) | Sending bytes from final send buffer: 8 | 2017-02-14 08:58:32 CQG WebAPI websocket (12) | Write in progress. Shutdown being delayed. | 2017-02-14 08:58:32 CQG WebAPI websocket (12) | Write has completed. Shutdown being performed. | 2017-02-14 08:58:32 CQG WebAPI websocket (12) | Shutdown started. Waiting for graceful close. | 2017-02-14 08:58:32 CQG FIX Trading | Websocket closed. | 2017-02-14 08:58:32 CQG FIX Trading | Disconnected. | 2017-02-14 08:58:32 CQG WebAPI websocket (12) | Socket gracefully closed by remote side. | 2017-02-14 08:58:32 CQG WebAPI websocket (12) | Closed. | 2017-02-14 08:58:32 CQG FIX: Received a Logout message. Text = NormalLogoutInitiatedByCounterparty | 2017-02-14 08:58:32 socket (11) | Initiating close of socket by core. | 2017-02-14 08:58:32 CQG FIX: Disconnected. | 2017-02-14 08:58:32 socket (11) | Shutdown started. Waiting for graceful close. | 2017-02-14 08:58:32 socket (11) | Socket gracefully closed by remote side. | 2017-02-14 08:58:32 socket (11) | Closed. | 2017-02-14 08:58:32 Checking for new symbol settings for service code cqg | 2017-02-14 08:58:42 Current selected Data/Trading service: CQG WebAPI | 2017-02-14 08:58:42 HTTPS connection to www.sierrachart.com:443 (16) | Creating socket. Using TLS 1.2. | 2017-02-14 08:58:42 Requesting symbol settings for service code cqg. Overwrite = on. | 2017-02-14 08:58:43 Symbol settings received. | 2017-02-14 08:58:43 Processed 903 symbol settings. | 2017-02-14 08:58:43 CQG WebAPI | Connecting to market data server api.cqg.com | 2017-02-14 08:58:45 CQG WebAPI | Connecting to websocket server. | 2017-02-14 08:58:45 CQG WebAPI websocket (17) | Creating socket. Using TLS 1.2. | 2017-02-14 08:58:45 CQG WebAPI | Opening websocket. | 2017-02-14 08:58:45 CQG WebAPI | Sending websocket handshake. | 2017-02-14 08:58:45 CQG WebAPI | Received websocket handshake acknowledgment. | 2017-02-14 08:58:46 CQG WebAPI | Web socket state is now open. | 2017-02-14 08:58:46 CQG WebAPI | Websocket connected. | 2017-02-14 08:58:46 CQG WebAPI | Sending market data logon message. | 2017-02-14 08:58:46 CQG WebAPI | Logon successful. Session Token = qKMgJEnzgj7tTTF0C/eAZVFfiKkAqfis3gJvK+uLaw8 | 2017-02-14 08:58:46 CQG WebAPI | Connected to data and trading server. | 2017-02-14 08:58:46 CQG WebAPI | Sending Trade Accounts request message. | 2017-02-14 08:58:46 CQG WebAPI | Brokerage name: AMP Account Name: 108286 | 2017-02-14 08:58:46 CQG WebAPI | Sending collateral subscribe request. | 2017-02-14 08:58:46 HTTPS connection to www.sierrachart.com:443 (16) | Socket gracefully closed by remote side. | 2017-02-14 08:58:48 HTTPS connection to www.sierrachart.com:443 (16) | Received socket Close event | 2017-02-14 08:58:48 HTTPS connection to www.sierrachart.com:443 (16) | Initiating close of socket by core. | 2017-02-14 08:58:48 HTTPS connection to www.sierrachart.com:443 (16) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2017-02-14 08:58:48 HTTPS connection to www.sierrachart.com:443 (16) | Closed. | 2017-02-14 08:58:48 CQG WebAPI | Sending positions subscribe request. RequestID=215937 | 2017-02-14 08:58:51 CQG WebAPI | Sending orders subscribe request. RequestID=215938 | 2017-02-14 08:58:51 A request for the latest software update has been made. | 2017-02-14 08:59:06 * The update is being downloaded in the background. When it is complete, you will be prompted. | 2017-02-14 08:59:06 * HTTP connection to www.sierrachart.com:80 (18) | Creating socket. | 2017-02-14 08:59:06 HTTP connection to www.sierrachart.com:80 (18) | Socket gracefully closed by remote side. | 2017-02-14 08:59:28 HTTP connection to www.sierrachart.com:80 (18) | Received socket Close event | 2017-02-14 08:59:28 HTTP connection to www.sierrachart.com:80 (18) | Adding bytes from final send buffer from buffered socket: 252 | 2017-02-14 08:59:28 HTTP connection to www.sierrachart.com:80 (18) | Initiating close of socket by core. | 2017-02-14 08:59:28 Failed to download software update due to an error. Request ID: 5. | 2017-02-14 08:59:28 * HTTP connection to www.sierrachart.com:80 (18) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2017-02-14 08:59:28 HTTP connection to www.sierrachart.com:80 (18) | Closed. | 2017-02-14 08:59:28 |
| [2017-02-14 17:21:59] |
| |
|
You can find the version numbers on the homepage of Sierra Chart which you can get to through Help >> Website. For unknown reasons, you have a problem on your side with the communication to the Sierra Chart website. At least through Sierra Chart itself. You can download the current version of Sierra Chart from this page: http://www.sierrachart.com/index.php?page=doc/download.php 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 |
| [2017-02-15 15:18:12] |
| User104854 - Posts: 441 |
|
I think the problem when I reload the charts and my computer not responding is with the Large Volume Trade Indicator. The chart loads like normal, but then it does it again as this indicator makes it reload, then it gets stuck and my computer says 'not responding' and I have to force close the program. This is happening a lot. I removed this indicator and hopefully this will resolve the problem. Please check it out as I'd like to continue using it. Thanks.
|
| [2017-02-15 17:56:19] |
| |
|
Make sure there is only one instance of the Large Volume Trade Indicator study on the chart. There can only be one. There are no known problems with this study. There is nothing for us to look into with it. The problem would be more likely due to the Market Depth Historical Graph study. We are still doing some work related to the loading of historical market depth data. The issue you are having might be resolved when that is done by tomorrow. 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: 2017-02-15 17:57:20
|
To post a message in this thread, you need to log in with your Sierra Chart account: