Support Board
Date/Time: Sun, 19 Jan 2025 15:20:03 +0000
SC stopped transferring orders to Bitmex
View Count: 1441
| [2018-02-27 16:21:29] |
| unset |
|
I have a Bitmex trading account setup on SC. Had been working fine. Now price still streams on SC, but order transmission is not working. Execution on Bitmex website is working. Beyond SC not working, SC is also now showing a position that does not exist anymore. How can I clear that position from SC? Log: Trade Activity Log: File read result: 1963 records inserted. 1295 fill records inserted. 146 records filtered. | 2018-02-27 11:04:41 Trade Activity Log: File date-time limits: Sim records date-time limit is 2018-02-12 00:00:00. Non-sim records date-time limit is 2018-01-27 00:00:00. Non-sim fill record date-time limit is 2017-02-27 00:00:00. | 2018-02-27 11:04:41 BitMEX | Requesting trade accounts from server. | 2018-02-27 11:05:00 BitMEX | Received 1 accounts from service. | 2018-02-27 11:05:01 BitMEX | Requesting historical order fills for all trade accounts. Number of days: 1 | 2018-02-27 11:05:01 BitMEX | Received 21 order fills. Inserting the ones that do not exist. | 2018-02-27 11:05:01 BitMEX | Requesting Trade Positions data. | 2018-02-27 11:05:06 BitMEX | Received first Trade Positions report from DTC server. | TradeAccount: xxxxxxxxxxx:xxxxx | 2018-02-27 11:05:06 BitMEX | Received last Trade Positions report from DTC server. Clearing nonexisting Trade Positions. | 2018-02-27 11:05:06 BitMEX order update (Order reject). Info: BitMEX Trading Master - DTC order update (Order reject). Info: (monitor.ml.Error ("connection attempt timeout" 52.214.218.140:443 src/tcp.ml:112:11) ("Raised at file \"src/import0.ml\" (inlined), line 234, characters 22-32" "Called from file \"src/error.ml\" (inlined), line 9, characters 14-30" "Called from file \"src/error.ml\" (inlined), line 5, characters 2-50" "Called from file \"src/tcp.ml\", line 112, characters 11-76" "Called from file \"src/job_queue.ml\", line 159, characters 6-47" "Caught by monitor try_with_or_error")). Internal Order ID: 1724. Service Order ID: 592557. Symbol: XBTUSD-BMEX | 2018-02-27 11:06:16 * BitMEX order update (Order reject). Info: BitMEX Trading Master - DTC order update (Order reject). Info: (monitor.ml.Error ("connection attempt timeout" 52.214.218.140:443 src/tcp.ml:112:11) ("Raised at file \"src/import0.ml\" (inlined), line 234, characters 22-32" "Called from file \"src/error.ml\" (inlined), line 9, characters 14-30" "Called from file \"src/error.ml\" (inlined), line 5, characters 2-50" "Called from file \"src/tcp.ml\", line 112, characters 11-76" "Called from file \"src/job_queue.ml\", line 159, characters 6-47" "Caught by monitor try_with_or_error")). Internal Order ID: 1725. Service Order ID: 592558. Symbol: XBTUSD-BMEX | 2018-02-27 11:08:38 * BitMEX | Requesting Trade Positions data. | 2018-02-27 11:08:49 BitMEX | Received first Trade Positions report from DTC server. | TradeAccount: xxxxxxxxxxx:xxxxx | 2018-02-27 11:08:49 BitMEX | Received last Trade Positions report from DTC server. Clearing nonexisting Trade Positions. | 2018-02-27 11:08:49 |
| [2018-02-27 19:52:28] |
| |
|
Use the new direct BitMEX trading integration support now available. This is fully documented here: Direct BitMEX Trading Support 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-27 19:52:42
|
| [2018-03-27 03:10:40] |
| unset |
|
I've been having lots of issues with Bitmex orders. I am using the new direct BitMEX trading integration as instructed. I am getting the following error message: "New order rejected - BitMEX Trading Direct error: This request has expired - `expires` is in the past. Current time: 1522119799. Internal Order ID: 1952. Service Order ID: (none). Symbol: XBTUSD-BMEX | 2018-03-26 22:48:04 *" This rejection took place on the XBTUSD perpetual swap - it does not expire. Please help. |
| [2018-03-27 03:45:44] |
| |
|
This would mean your computer clock is not set accurately. However, it is much less likely you are going to get this error in the latest version. Update following these instructions: 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-04-07 04:08:50] |
| unset |
|
I continue having constant issues with the Bitmex trading feed. Problems are 3: 1) Order rejected as system overloaded --- this is Bitmex's fault. 2) Order rejected - BitMEX Trading Direct error: This request has expired - `expires` is in the past --- I ran this SC on a VM and do not see clock as out of sync. 3) Resting orders and positions DISAPPEAR intermittently from SC, which leads to issues such as undesired double entries --- this started with the BitMEX Trading Direct connection, never before Even without issue #1, issues #2 and #3 make SC unreliable & costly. Any way to troubleshoot #2 and #3? Can you explain the benefits of the BitMEX Trading Direct connection vs the BitMEX (trading) connection? Could not find the answer on the relevant thread (Direct BitMEX Trading Support ). Date Time Of Last Edit: 2018-04-07 06:00:29
|
| [2018-04-07 06:01:09] |
| |
|
2,3. Update to the current version: 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 |
To post a message in this thread, you need to log in with your Sierra Chart account: