Support Board
Date/Time: Tue, 26 Nov 2024 11:29:25 +0000
DTC protocol - Teton weekend not working?
View Count: 368
| [2023-12-03 04:19:46] |
| User5044343 - Posts: 68 |
|
When I connect via DTC to a sierra instance with Teton - on the weekend there is no response to account balances etc - things that work during the week normally don't seem to be working on the weekend. Is that normal? Essentially I send in requests and I get no response. Not even a heartbeat. I do the same with Sierra connected to Interactive Brokers - and I get heartbeats back. |
| [2023-12-03 05:39:39] |
| Sierra_Chart Engineering - Posts: 17179 |
|
All of the trading data, is available 24 hours 7 days a week with Teton order routing. It does not matter if it is a weekend. You will see this information within Sierra Chart in Trade >> Trade Account Monitor, when connected to Teton order routing. Check that you do. 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, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2023-12-03 14:45:09] |
| User5044343 - Posts: 68 |
|
Trade account info shows up. But via dtc there is no heartbeat back. Only on Teton. IB connection works.
Date Time Of Last Edit: 2023-12-03 17:15:12
|
| [2023-12-03 18:27:32] |
| Sierra_Chart Engineering - Posts: 17179 |
|
If you are not getting heartbeat messages there is something you are not doing right on your side. Verify there is actually a connection and the connection encoding is set as you would expect. Also, the DTC Protocol Server in Sierra Chart is not at all affected by the external service Sierra Chart is connected to. 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, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2023-12-03 18:27:57
|
| [2023-12-04 02:01:27] |
| User5044343 - Posts: 68 |
|
Found the problem. I had the DTC server encoding option chosen as "JSON" in the "DTC protocol Server" section. When I enabled a sub-instance, the encoding switched to "Automatic" - so my scripts to that dtc server were sending json but the server was expecting binary. Once I added code to set the encoding when connecting to json it started working ( both the code and sub-instsance) Hexadecimal representation for encoding request message using binary encoding which is requesting JSON encoding: 0x10000600 0x08000000 0x02000000 0x44544300. Authentication and Connection Monitoring Messages: ENCODING_REQUEST [s_EncodingRequest structure] Client >> Server |
To post a message in this thread, you need to log in with your Sierra Chart account: