Support Board
Date/Time: Sun, 22 Dec 2024 11:54:44 +0000
FXCM/SC stop discrepancy
View Count: 1036
| [2015-02-05 04:16:02] |
| TechTrader - Posts: 116 |
|
Placed a BUY order on the FXCM platform with a protective SELL STOP below the BUY order. BUY order is filled and stop shows OK on the FXCM platform. When SC is in live mode, the filled order is as it should be but the protective SELL STOP shows as a BUY LIMIT order. This occurred on SC 1224 and pre release 1229. ?????
|
| [2015-02-05 04:53:41] |
| |
|
We are not observing this problem. And it is extremely unlikely an issue like this would be within Sierra Chart. It is next to impossible. We ran a test now and a Sell Stop attached order remained as a Sell Stop. 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 |
| [2015-02-05 05:20:41] |
| |
|
In order for us to help with this problem we need to get the latest FIX log at the time this problem occurs: Providing FIX Log to Support Does the problem consistently occur? 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 |
| [2015-02-05 09:36:41] |
| TechTrader - Posts: 116 |
|
I may not have explained the events clearly. The original buy order and its protective sell order were placed using the FXCM platform, not SC. When SC is live the buy order was not visible and the sell order as on the FXCM platform showed on SC as a buy limit. When the buy order filled it showed on SC correctly but the protective sell order as on the FXCM platform still showed on SC as a buy limit. Closing the position on the FXCM platform removed the sell stop and also the buy limit on SC. The attached file is a recreation of the original order sequence. |
Private File |
| [2015-02-05 19:58:45] |
| |
|
One other piece of information we need is what is the "Service order ID" of the order you see as a "buy limit" in Sierra Chart. You can see this in Trade >> Trade Orders and Positions >> Orders. If you are not sure at this point, then do the sequence of orders again which leads to what you are describing and make a note of the service order ID. Also, based upon what you are saying there is almost no doubt that the problem is on the FXCM side and they are providing incorrect information in the execution report. 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: 2015-02-05 20:02:12
|
| [2015-02-06 00:01:30] |
| TechTrader - Posts: 116 |
|
I agree the issue appears to be with FXCM. The attached log file corresponds with the following orders as shown by Trade >> Trade Orders and Positions >> Orders 11966 Buy Stop @ 1.53500 (entered on FXCM platform as Buy above market @ 1.53500) 11965 Buy Stop @ 1.52500 (entered on FXCM platform as Protective Sell Stop below market @ 1.52500) Also: 11968 Buy Limit @ 1.53100 (entered on FXCM platform as Buy below market A 1.53100) 11967 Buy Limit A 1.52100 (entered on FXCM platform as Protective Sell Stop below market @ 1.52100) |
Private File |
| [2015-02-06 22:21:20] |
| |
|
The numbers you give here look like internal order IDs. Not Service Order IDs and we cannot find any of them in the FIX log. We did find the order with a price 1.52100 in the FIX log and the FIX execution report indicated it was a Sell Stop. Therefore, the only explanation to what you are seeing is that there is a mapping problem with order IDs when orders are entered outside of Sierra Chart. We now see this. FXCM is using the same Client Order ID for different orders. This is a violation of the FIX protocol. This is directly from the FIX specification for ClOrdID: Unique identifier for Order as assigned by institution (identified by SenderCompID or OnBehalfOfCompID as appropriate). Uniqueness must be guaranteed within a single trading day. Firms, particularly those which electronically submit multi-day orders, trade globally or throughout market close periods,should ensure uniqueness across days, for example by embedding a date within the ClOrdID field.
We will bring this to their attention. 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: 2015-02-06 22:24:20
|
| [2015-02-07 00:04:40] |
| |
|
It is fastest for us to patch the problem on our side rather than waiting for FXCM to implement a solution, assuming they do. So we have implemented a patch to work around this. Basically we disregard the client order ID completely unless the order originated from Sierra Chart. 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: