Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sat, 27 Apr 2024 12:21:55 +0000
Mapped mystery CQG FIX Trading connection disappearance to versions 1998 and beyond
View Count: 636
| [2019-10-30 05:37:28] |
| User50927 - Posts: 90 |
|
As I previously reported, there appears to be a bug in the newer versions of SC that causes the CQG FIX Trading connection to mysteriously vanish from the pulldown menu in the Data/Trade Service Settings and subsequently, forces a switch to the much slower (on my system at least) CQG WebAPI connection. I've used package 5, the same F52 machine, and a fiber-optic connection to Advantage Fut for several years now and I've never experienced this type of problem before. But after spending some time systematically installing previous versions of the software starting with v1987, I was able to confirm that the problem started with v1998 and it's still there in v2005. Version 1997 was the last version that worked well and it's the one that I'm currently running. I hope this finding allows engineering to assist me with my problem ASAP. Thanks. |
| [2019-10-30 07:04:01] |
| User915027 - Posts: 17 |
|
forces a switch to the much slower (on my system at least) CQG WebAPI connection
How much slower? How did you measure this delay with Web API? |
| [2019-10-30 07:23:30] |
| User50927 - Posts: 90 |
|
I did not quantify the slow down because it's pretty obvious since the mouse pointer gets very sticky on the screen and I could never trade a fast market without incurring significant delays.
|
| [2019-10-30 07:38:40] |
| User50927 - Posts: 90 |
|
BTW, major issues with the CQG WebAPI had been reported by other users since I first started using CQG data many years ago, which is the reason why I stuck with CQG FIX all this time and NEVER had any connection problems until now. Personally, I don't understand why SC is pulling that option down from the menu ahead of schedule and before their direct-routing roll out in just a few months. They didn't even wait for v2000 to begin to it down as their 2019-10-17 announcement claims. Again, what seems to be the rush when the TT back end also has issues according to other users and therefore there are no good alternatives available at the moment?
|
| [2019-10-30 07:53:04] |
| |
|
The CQG Web API is not slower than CQG FIX on the Sierra Chart side. This is impossibility. There could never be a problem like this. I did not quantify the slow down because it's pretty obvious since the mouse pointer gets very sticky on the screen and I could never trade a fast market without incurring significant delays. This problem does not exist in regards to the CQG Web API and there is no one including you who is experiencing anything like this related to the CQG Web API. That is 100% definite.There is another issue. Refer to help topic 30: High CPU Usage | Inactive User Interface | Poor Performance | Long Time to Load Chart Data | Charts Reloading Often And the other thing that you apparently do not even know, is you are using the CQG Web API all along these years! There are two connections. To CQG FIX and CQG Web API in your case! The CQG Web API is used for market data. This is a necessary connection. You are not just using CQG FIX. You have always been using the CQG Web API! Apparently you did not realize that. CQG FIX is being removed for several different reasons including simplifying connectivity to CQG. CQG is in agreement with this. It is being done in newer versions now so that there is not a sudden problem when CQG removes the FIX connection for Sierra Chart users from their system in January 2020. Additionally, this thread you started and your other thread, only confirm to us even more why CQG FIX must go. It is creating unnecessary confusion and false conclusions. Our position on this is not going to change. 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: 2019-10-30 09:22:48
|
| [2019-10-30 08:16:10] |
| |
|
Again, what seems to be the rush when the TT back end also has issues according to other users We do not know what you are referring to other than two TT related incidents in August one of which was resolved on our side, and TT has address the other issues and we have not seen anything like those since. We did see one report of an order that was not acknowledged by TT but this is all.There are about 12,000 order fills with the TT service for the month of October for orders originating from Sierra Chart and a lot more, for orders which are not. 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: 2019-10-30 08:24:55
|
| [2019-10-30 09:30:51] |
| User50927 - Posts: 90 |
|
My concern about TT stems from a couple of comments you recently made: "There have been some issues recently with TT but on balance we think you are better off. But this is ultimately a decision that you will need to make." Those comments do not inspire much confidence (sounds like trading one set of problems for another), but I'll switch over anyways because you are not giving me a choice and then switch over to the direct routing system in another couple of months. Finally, I understand your frustration with other clients regarding the recent flood of complains about CQG connectivity but that has nothing to do with me because my system was working fine for many years until now, and I haven't changed anything on my end either, plus I use a high-end F52 Falcon model so CPU has never been an issue. BTW, your in-house QC testing might not be comprehensive enough to catch the wide range of problems that users can experience, so the fact that you can't detect a problem on your end does not necessarily invalidate a problem with your software. Keep that in mind the next time you decide to use so many absolutes in future replies - I still can't believe how unnecessarily abusive you sounded above. Thanks. |
| [2019-10-30 09:50:00] |
| |
|
We have 0% belief that whatever issue you are having with performance relates to the CQG Web API because at all times when you are using CQG FIX the CQG Web API is being used. So if you are switching expressly to the CQG Web API whether intentionally or upon an update, nothing has changed in this regard. Since the CQG Web API has always been used. I still can't believe how unnecessarily abusive you sounded above. Really? We are just telling a basic truth. Your problem is not with the Web API. It simply could not be because you have been using it at all times when connected to CQG.
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: 2019-10-30 09:52:00
|
| [2019-10-30 10:23:39] |
| |
|
And if there is a problem with the CQG Web API that is causing a performance issue, there is a very simple test. After you open up your Chartbook and are connected to the CQG Web API, close all the Chartbooks with File >> Close All Chartbooks. Then interact with Sierra Chart through the different menus and later open a single chart without any studies, and see if you notice any performance problem. But still, this would be inconclusive and would really only demonstrate something about maybe a new version and your system which is causing a performance issue. It simply could not be with the CQG Web API. 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: 2019-10-30 10:30:51
|
| [2019-10-30 10:28:41] |
| User50927 - Posts: 90 |
|
That's sooooooooo much better guys. Why didn't you write something clear and simple like that before? Whatever the problem might be, I don't care anymore and I hope it's resolved when I switch over to TT. Many thanks.
|
| [2019-10-30 10:34:15] |
| |
|
Actually post #10 does not really make sense. We should delete it because it would not prove anything. The problem could not be with the CQG Web API.
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: 2019-10-30 10:34:45
|
To post a message in this thread, you need to log in with your Sierra Chart account: