Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Wed, 24 Apr 2024 13:32:32 +0000
SC 1850; issue with sc.SendOrdersToTradeService
View Count: 855
| [2019-01-02 12:27:45] |
| @sstfrederik - Posts: 403 |
|
Hi, After a note from one of my clients I ran some tests and it appears that version 1850 has an issue with sc.SendOrdersToTradeService. My AT has this variable set consistently (see code below) and worked fine previously, but this does not seem to work for SC 1850. I tested SC version 1808 and 1853, which are fine. When going live the trade service log gives the following message indicating sc.SendOrdersToTradeService not set correctly. Trade service log on this: F.US.CLEG19 [CV] 550 Trades #1 | SendOrdersToTradeService is not consistent with 'Trade >> Trade Simulation Mode On' setting. Order action ignored. | 2019-01-02 07:12:28 This post is meant to make you aware of my observation and help with any future support requests on this version. Kind regards, Frederik if (sc.GlobalTradeSimulationIsOn == 1) sc.SendOrdersToTradeService = 0; else sc.SendOrdersToTradeService = 1; Date Time Of Last Edit: 2019-01-02 12:46:32
|
| [2019-01-02 14:33:34] |
| |
|
We definitely do not believe there is a problem with that ACSIL variable. Either in that version or any version. That really is an impossibility. There is some other explanation.
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-01-02 14:34:05
|
| [2019-01-02 15:51:26] |
| @sstfrederik - Posts: 403 |
|
I think it is something different indeed. Since what version are studies not recalculated when switching between trade sim mode and live mode? The variable is just not set after a switch frm sim to live and vice versa. When chart is recalculated it is fine. |
| [2019-01-02 18:42:05] |
| |
|
Okay to cause the recalculation use sc.MaintainTradeStatisticsAndTradesData=1.
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-01-02 18:42:25
|
| [2019-01-02 19:00:52] |
| @sstfrederik - Posts: 403 |
|
That is set already since day 1 on this study. Something has changed between SC versions. 1842 has no issues, 1850 does not recalculate when switching between sim or live. The study is the same. I can change the code, but would not prefer that. I set sc.SendOrdersToTradeService when sc.Index == 0. So when a recalculation happens it is set again. I can just set it throughout each call of the study, but that is less efficient. |
| [2019-01-02 19:25:08] |
| |
|
There is no problem with setting it on each call. We see a full recalculation is not occurring when going in and out of simulation mode. We could add that capability for ACSIL studies. But we are hesitant because it does cause performance issues and this is the reason for the recent change. 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-01-02 19:35:52
|
| [2019-01-02 19:33:09] |
| @sstfrederik - Posts: 403 |
|
Not looking for new capabilities, just pointing out an observation of different behavior between SC versions. To close the discussion I will just change my study code. Thanks for your time looking into this. |
To post a message in this thread, you need to log in with your Sierra Chart account: