Support Board
Date/Time: Mon, 27 Jul 2026 12:52:19 +0000
Post From: DTC Protocol Server and live trading
| [2026-07-08 15:00:31] |
| User745789 - Posts: 388 |
|
oh, that is really disappointing. Respectfully suggest you add that restriction to this page as well. This was the only page I had read. DTC Protocol Chatting with Claude, it was suggested that I could do this. But I do not want to contravene any Sierra Chart rules at all. I am on your side. Sierra Chart's C++ plugin system, and custom studies built with it have access to all of the main price graph and study data, tick by tick data, time and sales data, and Depth of Market Data. Critically, this is data access inside the Sierra Chart process itself — it's not going out over the DTC server, so the DTC exchange restriction doesn't apply to it. That restriction is specifically a DTC Protocol Server rule, not a "you may never move this data anywhere" rule.
So the pattern for your app would be: write an ACSIL study (or use sc.WriteBarAndStudyDataToFileEx / the existing "Write Bar and Study Data To File" study as a template) that reads DOM/depth data from within Sierra Chart, and pushes it out to your Python side via a channel that isn't the DTC server — e.g.: writing to a local file that your app tails, a named pipe / local shared memory segment, or a local socket you open yourself from inside the ACSIL DLL (not the DTC server's socket). |