Support Board
Date/Time: Sun, 02 Feb 2025 22:11:06 +0000
Notice: Transact Websocket Connectivity Issue
View Count: 8074
| [2019-09-13 02:29:01] |
| U_winks - Posts: 190 |
|
Don't be tricked by Transact or Infinity Futures into updating to v1986 and above. Their websocket connection is still useless. User Crtfyd did that and encountered this problem, which SC Support confirmed: The Transact websocket connection does not provide market depth data. Only the top of book. But you should still see bars based on the top of book. We are looking into this now.
NO BID ASK | Post: 191752 Ok we looked into this, the problem is the new Transact websocket data feed does not even provide best bid and ask size data either.
NO BID ASK | Post: 191759 Stick to v1941 for the time being, as advised by Transact staff themselves: FYI: Just got off phone with Transact. He had me revert back to version 1941 (last one to work before new socket) and Bid/Ask works fine. He said first time he's heard of it. He said stay on this version until further notice. So you guys can do your stuff wherever the problem may be.
Reference thread: NO BID ASK |
| [2019-09-13 04:49:55] |
| Marmany - Posts: 308 |
|
Been with TransAct since PFG went bust in 2012, no problems until they launched their own charting program 4 months ago. This was of no interest as it does not yet have auto trading. In my opinion they are discouraging auto trading from Sierra users. Put that idea to one of their Customer Service people a couple of weeks ago. He slammed the phone down on me. Have switched to Dorman, the TTfix link works very well. |
| [2019-09-13 06:40:37] |
| |
|
Put that idea to one of their Customer Service people a couple of weeks ago. He slammed the phone down on me. This could be just because they do not want to provide any technical support related to this.And it is not any different, when we say things like this in regards to telephone support on our website: Often questions involve fees and costs for external services and especially questions about exchange fees. We do not earn any money these fees and costs. Furthermore, the rules surrounding exchange fees are illogical, confusing and unfair to put it kindly. It is not proper for us to be spending time on the telephone at our expense and time answering questions about things that we do not control and that we earn no money from. It simply is not worth our time and we have no interest in this whatsoever. If we would get a question like this is from an open phone line, which you are not paying for at 50 USD per hour, we would hang up the phone promptly on you. We have zero tolerance for these types of questions. This particular item ranks near the top as to one of the reasons we will not provide an open telephone line.
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-09-13 06:41:28
|
| [2019-09-13 12:26:01] |
| |
|
So you know we are in close contact with top people at Transact and no one is rude to us and they are ready for us to test again with their revised websocket trading interface which we will today.
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-09-13 15:07:25
|
| [2019-09-13 14:55:52] |
| Meklon - Posts: 223 |
|
while Transact ... and taking other side of the loosing position (which by the way is illegal).
Support, There was a post this morning applied to this thread using my account that made some presumptuous accusations against Transact. Specifically about them "taking other side" of their customers trades. I suspect there is a possible identity theft happening and someone have gained access to my credentials. I was able to delete the post as it was linked to my account and have opened an account support ticket to address this problem. For the record: I have not made that post and had no intention of making one. I have also changed the password to my account. Please let me know what other steps can be taken to prevent this from happening again. Date Time Of Last Edit: 2019-09-13 15:12:07
|
| [2019-09-13 15:04:49] |
| |
|
Changing the password is important. We also need to see how to log out any other user who is using your account on this board. We will check on that. For your information, the IP of that post above, that you did not make is from New Jersey. 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-09-13 15:05:37
|
| [2019-09-13 15:10:41] |
| Meklon - Posts: 223 |
|
Thank you for looking into this. Hopefully changing the password to a much stronger one will be sufficient.
|
| [2019-09-18 16:18:12] |
| |
|
Transact is now supporting Trading through their websocket connection for Simulated Live and Demo. You will need to run Sierra Chart prerelease version 1989 for proper support for this. Some issues were resolved. Update with Help >> Download Prerelease. This has been thoroughly tested by Sierra Chart and also Transact has done testing. Live trading is currently not supported, only simulated trading using the Simulated Live connection or demo connection. Live trading will come soon. 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-09-18 16:18:31
|
| [2019-09-19 13:36:37] |
| User358559 - Posts: 15 |
|
Seems to work well but SC Dom does not show market depth levels
|
| [2019-09-19 13:54:46] |
| |
|
Yes we will remind them about the market depth data now.
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 |
| [2019-09-19 14:04:02] |
| |
|
Regarding Market Depth data on the websocket connection this was their response: We are looking into adding the depth. I do not have a timeline.
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-09-19 14:04:09
|
| [2019-09-19 18:51:09] |
| |
|
Letting you know, that Transact has added best bid size and ask size fields to their websocket data feed and that will be out in a day or two. It will need a new version of Sierra Chart which we may release this evening or tomorrow.
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-09-19 18:51:25
|
| [2019-09-23 10:58:18] |
| User90125 - Posts: 715 |
|
Is this available in prerelease 1991?
|
| [2019-09-23 11:00:50] |
| |
|
Yes.
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 |
| [2019-09-24 18:58:09] |
| User63632 - Posts: 43 |
|
v 1991 not showing orders/order fills on charts with transact bridge. Market depth on SC dome not yet working yet
|
| [2019-09-25 09:26:09] |
| |
|
In regards to post #91, make sure there is no checkmark by Trade >> Trade Simulation Mode. More information is here: https://www.sierrachart.com/index.php?page=doc/TransAct.php#Trading We know about the depth limitation. That will be available next week. 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 |
| [2019-09-29 15:34:11] |
| User316362 - Posts: 210 |
|
Have the issues with TransAct been resolved yet? Anyone? I last tried v1991. I tested with TransAct support on trading from the charts. They claimed that the order price being passed from Sierra was incorrect and shut off trading. I believe subsequently that Sierra corrected this problem. However, I have not tested with them since. They kept saying everything was working from their side. In any case, I have two questions; 1. Is live trading from the charts working with TransAct now? 2. If so, are the orders also reflected in the TransAct DOM (Ladder) at the same time as it was with the old TransAct Bridge (v 1941)? Anyone? Date Time Of Last Edit: 2019-09-29 16:15:34
|
| [2019-09-29 17:27:49] |
| User90125 - Posts: 715 |
|
I noticed this reply from SC Engineering on an unrelated issue: FO Futures Contracts Are NOT 2020 Ones | Post: 193028 you need to update Sierra Chart to the latest version and that latest version does support trading with Transact. Instructions:
Software Download: Fast Update So there is no problem with updating and you are far better off. The websocket connection at this point in time is far more reliable than the bridge. I tried it out on a fresh install of v1991 on one of my dev laptops. Worked like a charm, with one major exception. 1. Trading from the chart worked as expected. Still no market depth data on the Chart/Trade DOM though. 2. Orders showed up at the same time on the open Transact DOM, just like it did with the legacy AT bridge. However... 3. Subscription to symbols listed in the Quoteboard and/or Intraday File Update List (IFUL) in v1991 is patchy, at best, unlike the old TA Bridge in v1941. Regardless of how many symbols are listed in the Quoteboard and IFUL, I'd expect all those symbols to be subscribed as available, and actively reporting data during market hours. This currently is not the case with websocket connection in v1991. In fact, it is the one remaining issue (aside from the promised market depth data on the DOM), that SC and Transact should fully address before certifying the new websocket connection as ready for primetime. During market hours, the attached Quoteboard works as intended in v1941 (with the old TA bridge). Not so in v1991, as the websocket doesn't subscribe and populate all of the active symbols for whatever reason. In fact, one has to disconnect and reconnect the data feed several times, in the hope that the websocket connection will FULLY populate the Quoteboard with all of the working symbols with active data. Perhaps SC Engineering could take a closer look at this issue with Transact so that users of the older TA bridge in v1941 can finally migrate to the current versions of SC once and for all. |
 QB_20190926.SymbolList - Attached On 2019-09-29 16:55:11 UTC - Size: 315 B - 320 views |
| [2019-09-30 11:32:02] |
| |
|
They claimed that the order price being passed from Sierra was incorrect and shut off trading.
Yes, this is resolved and working properly. The problem was that Transact uses integers for order prices and market data and those represent the number of ticks. So to translate these values to the true floating-point value, requires the use of a multiplier. This multiplier was at the default value of 1 when using one of the Sierra Chart data feeds. This was the reason for the order price issue. It is resolved in 1991.I believe subsequently that Sierra corrected this problem. However, I have not tested with them since. They kept saying everything was working from their side. In any case, I have two questions; 1. Is live trading from the charts working with TransAct now? 2. If so, are the orders also reflected in the TransAct DOM (Ladder) at the same time as it was with the old TransAct Bridge (v 1941)? In regards to post # 94, we definitely see this as an issue on the Transact side. And also 1993 will support market depth from Transact. 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 |
| [2019-09-30 12:33:41] |
| User90125 - Posts: 715 |
|
we definitely see this as an issue on the Transact side. And also 1993 will support market depth from Transact.
Perhaps, if you haven't already, you could relay the issue with subscribing to all active symbols in the QuoteBoard to Transact. I will load a current copy of v1993 on a dev box and see what the impact of the changes are vis-a-vis market depth data from Transact in the SC chart/trade DOM. --- Also just received this in the message log for v1991 64-bit (bulid 28578M) Price Websocket | Received frame with length 122936 | 2019-09-30 07:41:02.416
Price Websocket | Received frame with length 122936 | 2019-09-30 07:41:02.418 Price Websocket | Received frame with length 122936 | 2019-09-30 07:41:02.558 Price Websocket | Received frame with length 122936 | 2019-09-30 07:41:02.590 Price Websocket | Received frame with length 122936 | 2019-09-30 07:41:02.611 Price Websocket | Received frame with length 122936 | 2019-09-30 07:41:02.638 Price Websocket | Received frame with length 122936 | 2019-09-30 07:41:02.669 Price Websocket | Received frame with length 122936 | 2019-09-30 07:41:02.688 Price Websocket | Received frame with length 122936 | 2019-09-30 07:41:02.845 Price Websocket | Received frame with length 122936 | 2019-09-30 07:41:02.848 Price Websocket | Received frame with length 122936 | 2019-09-30 07:41:02.994 Price Websocket | Received frame with length 122936 | 2019-09-30 07:41:03.351 Price Websocket | Received frame with length 122936 | 2019-09-30 07:41:03.352 Price Websocket | Received frame with length 122936 | 2019-09-30 07:41:03.494 Price Websocket | Received frame with length 122936 | 2019-09-30 07:41:03.640 Price Websocket | Received frame with length 122936 | 2019-09-30 07:41:03.650 Price Websocket | Received frame with length 122936 | 2019-09-30 07:41:03.783 Price Websocket | Received frame with length 122936 | 2019-09-30 07:41:03.935 Price Websocket | Received frame with length 122936 | 2019-09-30 07:41:03.947 Price Websocket | Received frame with length 122936 | 2019-09-30 07:41:04.124 Price Websocket | Received frame with length 122936 | 2019-09-30 07:41:04.137 Price Websocket | Received frame with length 122936 | 2019-09-30 07:41:04.139 Price Websocket | Received frame with length 122936 | 2019-09-30 07:41:04.298 TransAct WS | Received frame with length 122926 | 2019-09-30 07:41:04.298 Price Websocket | Received frame with length 84480 | 2019-09-30 07:41:04.313 Price Websocket | Received frame with length 84480 | 2019-09-30 07:41:04.313 Price Websocket | Received frame with length 84480 | 2019-09-30 07:41:04.335 Price Websocket | Received frame with length 84480 | 2019-09-30 07:41:04.486 Price Websocket | Received frame with length 84480 | 2019-09-30 07:41:04.493 Price Websocket | Received frame with length 84480 | 2019-09-30 07:41:04.633 Price Websocket | Received frame with length 84480 | 2019-09-30 07:41:04.653 Price Websocket | Received frame with length 84480 | 2019-09-30 07:41:04.820 Price Websocket | Received frame with length 84480 | 2019-09-30 07:41:04.962 Price Websocket | Received frame with length 84480 | 2019-09-30 07:41:05.116 Price Websocket | Received frame with length 84480 | 2019-09-30 07:41:05.286 Price Websocket | Received frame with length 84480 | 2019-09-30 07:41:05.437 TransAct WS | Received frame with length 84470 | 2019-09-30 07:41:05.437 Received Date-time from server. Delay adjusted UTC Date-time: 2019-09-30 11:58:57.015. Round-trip delay: 00:00:00.245 | 2019-09-30 07:58:56.831 Computer time to server time difference: 00:00:00.184 | 2019-09-30 07:58:56.831 Successfully set the system Date-time to: 2019-09-30 11:58:57.015 UTC. | 2019-09-30 07:58:57.015 Price Websocket | Received frame with length 132959 | 2019-09-30 08:13:56.388 Price Websocket | Received frame with length 132959 | 2019-09-30 08:13:56.721 Price Websocket | Received frame with length 132959 | 2019-09-30 08:13:57.041 Price Websocket | Received frame with length 132959 | 2019-09-30 08:13:57.207 Price Websocket | Received frame with length 132959 | 2019-09-30 08:13:57.418 Price Websocket | Received frame with length 132959 | 2019-09-30 08:13:57.598 Price Websocket | Received frame with length 132959 | 2019-09-30 08:13:57.793 Price Websocket | Received frame with length 132959 | 2019-09-30 08:13:57.800 Price Websocket | Received frame with length 132959 | 2019-09-30 08:13:57.957 Price Websocket | Received frame with length 132959 | 2019-09-30 08:13:57.961 Price Websocket | Received frame with length 132959 | 2019-09-30 08:13:58.126 Price Websocket | Received frame with length 132959 | 2019-09-30 08:13:58.312 Price Websocket | Received frame with length 132959 | 2019-09-30 08:13:58.470 Price Websocket | Received frame with length 132959 | 2019-09-30 08:13:58.473 Price Websocket | Received frame with length 132959 | 2019-09-30 08:13:58.659 Price Websocket | Received frame with length 132959 | 2019-09-30 08:13:58.665 Price Websocket | Received frame with length 132959 | 2019-09-30 08:13:58.697 Price Websocket | Received frame with length 132959 | 2019-09-30 08:13:58.742 Price Websocket | Received frame with length 132959 | 2019-09-30 08:13:58.757 Price Websocket | Received frame with length 132959 | 2019-09-30 08:13:58.921 TransAct WS | Received frame with length 132949 | 2019-09-30 08:13:58.921 Message log also sent for analysis. Thanks again for your support. |
| [2019-09-30 19:54:32] |
| User90125 - Posts: 715 |
|
So in v1993 with the Transact WS websocket connection, the Quoteboard now does not show the following fields at all (which worked previously in v1991): Bid Ask BidSize AskSize BidAskSpread Could you verify and let Transact know about it, since it seems to coincide with the release of Market Depth Data on the SC DOM. |
| [2019-09-30 21:32:59] |
| |
|
In regards to post #96, contact Transact about this . They should be able to tell from their server-side what the issue is. We will remove those messages. That is provides additional confirmation to us, that this problem with lost connections and websocket frame corruptions was definitively never on the Sierra Chart side. The corruption was coming from the Transact side. We did indicate that previously and that is with certainty. In regards to post #97, that is something we need to take care of. That will be solved in the next release. 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 |
| [2019-10-01 14:33:04] |
| User358559 - Posts: 15 |
|
This morning v1993 (10 am EST) charts lagging in CL with Transact Dom. Changed to 1941 and now no lag even in quick moves. Any suggestions
|
| [2019-10-01 14:43:16] |
| |
|
No suggestions from our side. Transact will need to resolve.
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 |
To post a message in this thread, you need to log in with your Sierra Chart account: