Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Wed, 08 May 2024 20:30:32 +0000
Post From: Trading System Based on Alert Condition: Constraints/Limits
| [2018-10-07 21:28:39] |
| |
|
TSBAC fails to detect it when the entire condition becomes true. It would be exceptionally unlikely to be some kind of Sierra Chart software problem. You need to tell us why. Refer to this option on the Alerts tab to help you with this:Study/Chart Alerts And Scanning: Log Evaluated Formula at Each Evaluation It could also be related to this: Chart Studies: Study Calculation Precedence And Related Issues Now I break up ID53 into its basic components, and also combine it with a couple of other (no-shortcut, basic) conditions. It worked! My question is, why does SC impose such a limitation on TSBAC capabilities? What are you referring to?Any alert, however complex, entered into the BUY/SELL ENTRY/EXIT Alerts should work just as they would if they were standalone alerts not attached to TSBAC. We cannot know what the issue is. You need to go through this and debug this.Encapsulating complex conditions in alerts makes it easier for use elsewhere in the chart as opposed to repeatedly referencing the individual components from the encapsulated alert condition. 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-10-07 21:29:37
|