Support Board
Date/Time: Sat, 18 Jan 2025 10:56:32 +0000
[Locked] - Get the wrong quote from a symbol
View Count: 745
| [2018-01-31 03:56:12] |
| User841591 - Posts: 42 |
|
I use IB as data feed to get the MHI option for HKFE Exchange. I get the quotes of MHI Put option with strike 32200 and 32800 without problem but not the 32400( Pls refer to the attached jpg). Pls advise how I can fix it.
|
 ScreenHunter_03 Jan. 31 1 10.55.jpg / V - Attached On 2018-01-31 03:54:52 UTC - Size: 247.65 KB - 268 views |
| [2018-01-31 04:15:24] |
| |
|
You really need to ask Interactive Brokers about this. There is no way we would know the answer to this or can help.
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 |
| [2018-01-31 05:14:35] |
| User841591 - Posts: 42 |
|
From the jpg attached, IB show the correct quote but not SC.
|
| [2018-01-31 05:21:41] |
| |
|
When we give you an answer, you need to understand we are speaking with tremendous expertise and 100% confidence. Contact Interactive Brokers about the nonsense from them. This is just yet again more crap and garbage from TWS. Understand that!!!!. We will not help with this. 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 |
| [2018-01-31 05:29:54] |
| User841591 - Posts: 42 |
|
I solved the problem when I update the SC to the current version. It is definitely the SC problem. Don't just think you are always right.
|
| [2018-01-31 05:32:23] |
| |
|
Don't just think you are always right. Yes we are always right!!! Even though you do not recognize that. This is a TWS problem. That is abundantly clear.We are not idiots. We actually considered the possibility a data reconnect would solve the problem coincidentally. We know these issues are on the TWS side. We would never accept that this was on our side. That is a total complete impossibility and it makes no sense whatsoever which is even confirmed by the screenshot and our intelligence. Even if the hypothetical case, that it was, we would always put the blame on Interactive Brokers because all of their problems and incompetency. A problem like this simply cannot be in SC. That is a complete impossibility. 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: 2018-01-31 05:35:14
|
| [2018-02-01 18:26:12] |
| |
|
This really also reaffirms the unreliability and issues that exist in TWS. and why we are very critical of Interactive Brokers and TWS. The very fact that they are not even mapping these price values to the proper IDs just demonstrates this overwhelmingly. This just shows total instability on the part of TWS and Interactive Brokers. Now if people look at post #6, and think we have some kind of attitude, then great. It is only a complement. The basis of our position and statements is this statement from the user: It is definitely the SC problem.
Now what would we do with a statement like that, with all of our massive experience, and intelligence, knowing Sierra Chart inside out and knowing about the boatload of problems with TWS and Interactive Brokers and how things work with the interface TWS provides. Here the user believes it is "definitely" a problem on our side and we know that is 100% false. They do not accept the TWS was providing faulty data. Besides, nothing has changed between versions which would even correct a problem like this, and we took no action even related to it because it is not an issue on our side either. So if you encountered it once, you are probably going to encounter it again. This can still happen again. The only reasonable conclusion is that TWS is mapping those high/low/volume values to the wrong integer identifier when sending the data out over the client socket. And then we also have all of the experience, where when problems are reported to Interactive Brokers because of the fact that they are a large organization and the technical support people do not have the proper competency, that problems go unrecognized, and ridiculous answers are given. And Interactive Brokers would just claim that it was never their problem to begin with. Very easy thing to do. This is why we are direct and to the point and assertive. 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: 2018-02-04 14:00:19
|
To post a message in this thread, you need to log in with your Sierra Chart account: