Support Board
Date/Time: Sun, 24 Nov 2024 03:26:28 +0000
Post From: ***Interactive Brokers is Garbage*** (Technical Support is Now Fully Ended!!)
| [2020-02-10 01:42:06] |
| |
|
One example of a problem someone blamed on us, is that when Sierra Chart is downloading historical data whether it be from TWS, or from the Sierra Chart servers, is that it disconnects from TWS. This is not at all a Sierra Chart problem. It is TWS which is doing the disconnection. There is no code in Sierra Chart which will disconnect the TWS connection unless there is an invalid server version upon the initial connection or you have set an automatic daily reconnection at a particular time (Global Settings >> Data/Trade Service Settings >> Advanced). About three years ago, we completely updated the protocol being used with TWS because they started supporting a new protocol, a properly designed protocol from the old completely messed up and unreliable up design they had before, where in the currently used protocol, they provide at the beginning of each message the length of the message. Rather than previously determining the length from the fields which are present and based on message type and server version. In the past, if there was some problem with "framing", that could lead to a disconnection on the Sierra Chart side. But that no longer exists. When TWS does a disconnect, in some cases it is because it thinks a field is faulty, when it is not, but they should never be doing that. It just should gracefully handle an invalid field even though there was not a problem to begin with. 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: 2020-02-10 01:42:40
|