Support Board
Date/Time: Sun, 15 Jun 2025 15:55:24 +0000
DLL version not in sync with 2758
View Count: 319
| [2025-05-19 09:07:25] |
| fxtrades123 - Posts: 19 |
|
There is a function I need on the 2758 version for my study to work properly. but my compiler says 2755. when I went into sierrchart.h it says 2755. but the chart gui says 2758. I triple checked I downloaded and 2758 from the software download page correctly. I also tried going to help, and downloading the most current version twice, then checking sierrachart.h file but it still says 2755. any thoughts on how I can get the dll compiler to match the chart. any thoughts? Thanks |
| [2025-05-19 15:35:34] |
| John - SC Support - Posts: 40422 |
|
The sierrachart.h file is not updated with every release. The last release in which it was updated was 2755, which is why that is what is showing in the file. There is no newer version, so we are curious what function you are looking for? For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2025-05-19 17:11:52] |
| fxtrades123 - Posts: 19 |
|
I was just checking to make sure I could run 2758 fully with all functions since it said 2755 on the compiler DLL. I am running 2 scripts with 2 separate accounts and need them to communicate and be able to identify the 2 separate accounts. One for buy and one for sell. And do separate functions for each. Example Cancel order on one and have an open order on the other. But 2758 looks like it has an account string label where as 2752 does not. That’s why I was wanting to make sure it saying 2755 on the compiler in sierrachart.h won’t set it back to a version that did not have this new account identifier string that I could use for both scripts connected via shared state. Thanks |
| [2025-05-19 19:01:14] |
| John - SC Support - Posts: 40422 |
|
You will be fine.
For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2025-05-19 19:15:45] |
| fxtrades123 - Posts: 19 |
|
Thank you, so just to make sure the version 2758 does have the account string to specify separate accounts for separate functions? Like 2 accounts with a shared state able to do different functions without a brute all or nothing? |
| [2025-05-19 19:51:34] |
| John - SC Support - Posts: 40422 |
|
We do not know what function you are referring to. We assumed that you already had something you were referencing. If you do not have something specific you are referencing, then what are you looking for and why do you think it exists in the recent versions? For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2025-05-19 20:45:14] |
| fxtrades123 - Posts: 19 |
|
(v2752) sc.CancelOrder(OrderID); This approach attempts to manage orders for two separate accounts in a dual-script trading setup. Sierra Chart v2752 does not allow specifying accounts when cancelling orders, causing the strategy to fail. (v2758) #define SC_DLL_BUILD_NUMBER 2758 sc.CancelOrder(OrderID, sc.SelectedTradeAccount); This updated method clearly specifies which account’s order should be cancelled. Sierra Chart v2758 supports explicit account specification, enabling correct operation of a dual-account trading strategy. I just want to confirm that this approach works with 2758. And that the 2755 compiler version won’t not accept this for 2758. |
| [2025-05-19 21:02:20] |
| John - SC Support - Posts: 40422 |
|
You have us very confused. Where are you getting the information that shows this: (v2758)
#define SC_DLL_BUILD_NUMBER 2758 sc.CancelOrder(OrderID, sc.SelectedTradeAccount); For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2025-05-19 21:12:23] |
| fxtrades123 - Posts: 19 |
|
I found it on with the help of AI but basically, I have a dual account strategy that needs 2 separate accounts and 2 charts (2 separate file paths) for this to run properly. I am trying to see if I am able to have those 2 accounts be able to do spectate functions buying and selling on the same symbol. I’ve got it doing it that way via shared state file json. But I am having trouble being able to accurately have the 2 accounts do separate functions. Example, one account hits the tp and the other account cancel the open order. So I want both account scripts to be able to act independently but communicate what they are doing to each other so the other one knows via json shared stage file.
|
| [2025-05-19 21:22:37] |
| John - SC Support - Posts: 40422 |
|
Ok, now we understand what is going on. Whatever AI you were using was wrong. They gave you what you wanted to hear instead of the reality. There is no function for the following: sc.CancelOrder(OrderID, sc.SelectedTradeAccount); There is only the existing function for the following: sc.CancelOrder(OrderID); The functions that are available within ACSIL are all called out in the 'sierrachart.h' file in the ACS_Source folder under your main Sierra Chart installation. So always look there first to see if something exists. We have updated the documentation recently so everything up to version 2755 of ACSIL should be listed in our documentation as well at the following links: ACSIL Interface Members - Variables and Arrays ACSIL Interface Members - Functions Automated Trading From an Advanced Custom Study But admittedly, we do get behind with that documentation, which is why we reference you to the sierrachart.h file first. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2025-05-19 21:28:44] |
| fxtrades123 - Posts: 19 |
|
Okay I double check it and it corrected itself. Is there a way to do this reliably? A label or an identifier that the 2 accounts could run separate but communicate their actions via shared state so one account script knows what the other has done/completed? Thank you for your time guys |
| [2025-05-19 21:56:40] |
| fxtrades123 - Posts: 19 |
|
If y’all have any suggestions on how I would do this. Something to identify the accounts so the shared state can reliably action stuff on either account but making them communicate when an action is done. Like one account hits a tp and the json knows this and communicates to the other to cancel the open stop order and both move together. Like they act independently of each other but when one does something (event) the other knows and responds accordingly. Like an account string label maybe for buy/sell/account number/ specifying letters or numbers etc. or some kind of identifier if that makes sense. If this is possible that would be amazing.
|
To post a message in this thread, you need to log in with your Sierra Chart account: