Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Thu, 25 Apr 2024 21:28:19 +0000
ACSIL Price2 for Stop Limit order is different in trade activity log
View Count: 1123
| [2016-08-03 02:29:47] |
| @sstfrederik - Posts: 403 |
|
Hi, I have noticed that the NewOrder.Price2 is not set correctly when using a Stop limit order in acsil. It is working in this case: -Long: price1 = 30; price2 = 31; Not working when trying to accomplish this: -Long: price1 = 30; price2 = 29; In trade activity log price2 = 31; While I use my Message log to output the price2 just before the BuyEntry order is given, which shows 29 as the price2. When using the Stop-Limit Order Limit Offset manually this order works fine. I can not figure out what is wrong. I will put a simple code example together tomorrow and see if I can show this is actually happening. |
| [2016-08-03 05:44:15] |
| |
|
It was not intended to set Price2 in this way where it is lower for a Buy stop order. So if it is not working, it is not supported. We do not need any further information. 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-08-03 05:44:41
|
| [2019-03-15 18:56:29] |
| gomifromparis - Posts: 244 |
|
Hi, This logic stills seems effective as of today, it is impossible to have a negative offset using ACSIL on a stop limit. You guys still holding on this ? It seems strange that if you want to gain a couple ticks, you can input negative offsets in the chart order manager, but not in ACSIL ? Thanks |
| [2019-03-17 07:25:13] |
| |
|
There is the Triggered Limit order type which will do what you want which can be used from ACSIL both as a parent order and as an Attached Order. We will update the documentation with 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: 2019-03-17 08:43:09
|
| [2019-03-17 08:42:41] |
| |
|
We currently see that the Triggered Limit type cannot be used as an Attached Stop order in ACSIL but that will be supported in 1884.
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: