Home >> Support Board

Support Board

Date/Time: Sun, 05 May 2024 11:35:50 +0000

How to Post a Message for Support

[Locked] - Direct BitMEX Trading Support

View Count: 10293

[2018-03-02 08:08:58] #25 [Go To First Post]
coin boss - Posts: 19
Anyone else having some serious problems with bitmex stop orders, i am on the new connetion (direct trading). It seems as though the stop market orders are not working as i want them to. And after a little digging i found out why. My guess is that Bitmex allows 3 different stop market triggers, the one that i want it to be using is the last price of the actual bitmex trades, but there is also the option of using the Mark price, or the index price. It looks like the orders through sierra are using the MARK price. so when price actually hits your level, it will NOT take you out of the trade. So the question is, how do we set the stop market order type so that the trigger price is the LAST price. In the photo you can see the actual trigger price is not close to what the bitmex price is at... and when the trade was closed it was way way lower and you are blown out at that low lever.. and its costing me a lot of money, but im glad i figured out the reason why now. I just need to know how to let Sierra signal the proper stop market trigger type, the way stops normally work. I can see another thread where someone mentioned the same issue a while ago, and the reply was: Indeed, the execInst was set to Mark Price. I changed it to Last Price and this will be released in prod ASAP. Sorry for the inconvenience. But it looks like its still the same issue with the current version.. or is there a way to change this trigger. Thanks for your help.


1.JPG / V - Attached On 2018-03-02 07:52:08 UTC - Size: 209.82 KB - 717 views 3.JPG / V - Attached On 2018-03-02 08:02:42 UTC - Size: 54.97 KB - 614 views

[2018-03-02 19:15:46] #26 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
We are not specifying the execution instruction with a stop order so it must be defaulting to the mark price. Will make sure to specify it as last price. For now use the client-side managed stop order type named Stop with Last Triggering. Sierra Chart must be running though for this order to be triggered. 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-03-02 19:16:39

[2018-03-02 19:25:40] #27 [Go To First Post]
coin boss - Posts: 19
is there a way to specify it? I guess the question is, what do most traders want. for me i want the actual price. there is a case for using the underlying price they use, because bitmex tends to be a bit whippy due to lower liquidity. but, in general, a "normal" stop should be when a transaction takes place on that exchange at the trigger price. Ok, I will try that order and see if it executes fast enough. And I guess you will let us know if you are able/when you are able to switch the order to execute with last price trigger? Thanks.

[2018-03-02 19:54:51] #28 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
We are definitely going to get to this today. And we intend to make this an adjustable setting for Stop orders to include all of the choices. 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-03-02 20:34:10] #29 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Also in the latest version of Sierra Chart, there is in Global Settings >>Data/Trade Service Settings >> Service Settings a field to manually specify the execution instructions which are included with an order. This applies to all orders and you have to make sure you enter the text correctly as specified by BitMEX. 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-03-02 20:34:30

[2018-03-02 21:22:26] #30 [Go To First Post]
coin boss - Posts: 19
I tried that stop with last triggering, it did not work at all. Also I am unable to edit the Service setting area to add a field or anything. I just downloaded the newest version.

[2018-03-02 22:47:50] #31 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
I tried that stop with last triggering, it did not work at all. We are testing this now. This is a new order type that has not yet been thoroughly tested. We should have said to use it first in Trade Simulation Mode as the What is New page documents for it. We should have the problem resolved in a couple of hours. Also I am unable to edit the Service setting area to add a field or anything. I just downloaded the newest version. You first need to select the field in the list and then below there is an edit box to enter the text. This is just how like Study Input settings work. 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-03-02 22:48:06

[2018-03-02 23:00:21] #32 [Go To First Post]
coin boss - Posts: 19
you mean when you have service: Bitmex Trading direct in the drop down menu.. then you go to service setting and add a field? That does not work. There are 3 fields: server, API key, API Secret. No other fields are there, and when you click on a blank field, it does not allow you to enter anything for that field. i have enclosed a screenshot. You say you are going to add an adjustable setting, and are getting to it today. So perhaps i will just wait until its done. For now I am just using their website to add the stop manually.


service.JPG / V - Attached On 2018-03-02 22:59:33 UTC - Size: 68.49 KB - 418 views

[2018-03-02 23:21:40] #33 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
OK now we understand the difficulties. You are not running the latest prerelease. You need to be on the latest prerelease. Update with Help >> Download Prerelease. Also, we have that Stop with Last Triggering stop order issue resolved and will have a new release out in about an hour. It was not being allowed to be changed to a market order type or being recognized as a stop order by the external service client to do to several safety checks. 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-03-03 04:29:39] #34 [Go To First Post]
coin boss - Posts: 19
Ok I downloaded the release. I see the execinst area... but if I set LastPrice there, it is trying to use that variable for all orders, so if i am entering with a limit order it throws an error and does not place. I guess the problem is that setting is a global setting for all orders (?).

[2018-03-03 06:29:57] #35 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Yes we were concerned about that. We have now released version 1711 with the new setting to set this particular execution instruction for stop orders. And 1711 also corrects the problem with the Client-side managed stop orders which use last and bid/ask triggering. 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-03-03 17:50:55] #36 [Go To First Post]
coin boss - Posts: 19
It is still not working, it is still using mark price... you can see the trigger price is not equal to the current price. I have attached photos. Do i have to have the STOP set to a certain type?


1.JPG / V - Attached On 2018-03-03 17:48:29 UTC - Size: 70.69 KB - 555 views 2.JPG / V - Attached On 2018-03-03 17:48:38 UTC - Size: 59.95 KB - 563 views 3.JPG / V - Attached On 2018-03-03 17:50:25 UTC - Size: 135.44 KB - 635 views

[2018-03-03 19:04:46] #37 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
We apologize for this. There was a small error preventing that particular instruction from getting actually set with the order. This is now resolved. Update with Help >> Download Prerelease: Software Download: Fast Update The version number is still the same. 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-03-04 16:31:57] #38 [Go To First Post]
User342238 - Posts: 44
Hi, I'm having an issue with a different order type on Bitmex. When I use the sell ask or buy bid from the trading dom, quite often my orders are filled as market orders and I get hit with the market taker fee. I want my order to join, ie get behind the best offer when it reaches the exchange. Thanks

[2018-03-04 21:19:42] #39 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
We cannot help with this. You need to ask BitMEX about this. You can see the specific details of the submitted order in the Trade Activity Log: Trade Activity Log: Viewing Historical Trade Activity You also need to realize, that the determination of the bid and ask prices are what Sierra Chart has received at the time of the order submission. Those can be old by the time the order gets to the exchange. 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-03-04 21:20:54

[2018-03-05 01:32:52] #40 [Go To First Post]
coin boss - Posts: 19
Re: the previous question about limit order executing as market. That happens to me also. it is most likely because the order moves by the time it gets executed at the exchange. There is a command to stop this when you send the limit order. I have attached 2 photos. It is an execinst variable... so theoretically, just like the "lastprice" variable that sierracharts created an option to add, they can also do the same with the post only. Its actually a big deal for trading short term. it can make or break the trade being profitable if trading for 10 or 20 ticks. The execinst variable is: ParticipateDoNotInitiate. I notice there is an "additional execinst for orders:" where you can add a execinst variable.. but im afraid that might be a blanket variable used for all orders.. we would need there to be a separate one for limit orders.


Capture.JPG / V - Attached On 2018-03-05 01:29:48 UTC - Size: 59.59 KB - 932 views Capture2.JPG / V - Attached On 2018-03-05 01:29:53 UTC - Size: 111.87 KB - 483 views

[2018-03-05 03:36:26] #41 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
In Global Settings >> Data/Trade Service Settings you can enable the setting to specify ParticipateDoNotInitiate with orders. It is there. We can make it for limit orders only if that is how it is only intended to be used. 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-03-05 04:39:01] #42 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
This is what BitMEX told us: Yes, you cannot send execInst=ParticipateDoNotInitiate for ordType=Market or Stop or MarketIfTouched, nor can you send it with timeInForce=ImmediateOrCancel or FillOrKill So we will make sure these rules are followed for that execution instruction. 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-03-05 04:39:17

[2018-03-05 16:45:38] #43 [Go To First Post]
User342238 - Posts: 44
I would prefer it not be changed actually, as when I am using these buttons I"d rather get filled at market than not at all. If there was a way to actually join the market upon reaching the exchange, that would be really helpful... so my vote is status quo..

[2018-03-05 17:03:26] #44 [Go To First Post]
User342238 - Posts: 44
On second thought, it would be cool if you could just add the post-only function to the buy/sell buttons, while leaving the functioning of regular limit orders in the dom as they are. This would add functionality for sure....

[2018-03-05 18:33:11] #45 [Go To First Post]
User960746 - Posts: 25
Following the instructions, In Global Settings >> Data/Trade Service Settings you can enable the setting to specify ParticipateDoNotInitiate with orders. It is there. I can't find the option ParticipateDoNotInitiate in the Data/Trade Service Settings. I am new to the Sierra Chart, could you please give a instruction with images? Thank you.

[2018-03-05 23:19:56] #46 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
You need to update to the latest "Prerelease": Software Download: Fast Update 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-03-06 16:59:59] #47 [Go To First Post]
User620704 - Posts: 20
When using attached orders in conjunction with the ParticipateDoNotInitiate option, only the original order seems to get placed (so no accompanying limit/stop orders are going through)? update: the limit side of the order looks like it is there... Date Time Of Last Edit: 2018-03-06 17:18:07

[2018-03-06 22:18:15] #48 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
One thing to keep in mind is that the target and stop orders are held until the parent fills: Attached Orders: General Management of Attached Orders 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-03-07 03:15:06] #49 [Go To First Post]
User271989 - Posts: 44
this still happening to everyone? New order rejected - BitMEX Trading Direct error: The system is currently overloaded. Please try again later. Internal Order ID: 1769. Service Order ID: (none). Symbol: XBTUSD-BMEX \| 2018-03-07 03:13:08 *

[2018-03-07 03:39:34] #50 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Looks like we need to create our own exchange which is planned. 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: