Support Board
Date/Time: Sat, 18 Jan 2025 19:29:07 +0000
Order Error - Unexpected BitMEX symbol format
View Count: 846
[2018-03-02 13:41:05] |
User104352 - Posts: 10 |
I can not do any orders on xbtusd since i updated to 64bit. Trade Activity Log: File read result: 6086 records inserted. 356 fill records inserted. 0 records filtered. | 2018-03-02 14:38:03 Trade Activity Log: File date-time limits: Sim records date-time limit is 2018-02-15 00:00:00. Non-sim records date-time limit is 2017-11-29 00:00:00. Non-sim fill record date-time limit is 2017-03-02 00:00:00. | 2018-03-02 14:38:03 Order Error - Unexpected BitMEX symbol format. Needs to be [Instrument]ÀH{ . Internal Order ID: 792. Service Order ID: (none). Symbol: XBTUSD-BMEX | 2018-03-02 14:38:56 * |
[2018-03-02 18:05:36] |
Sierra Chart Engineering - Posts: 104368 |
We are checking on this 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 |
[2018-03-02 18:28:13] |
Sierra Chart Engineering - Posts: 104368 |
We cannot reproduce but we made a couple of changes and we are going to release a new version in approximately 30 minutes. This will be prerelease version 1710. We will want you to test then. 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 18:28:40
|
[2018-03-02 21:14:51] |
User104352 - Posts: 10 |
Version 1710 solves this problem, thank you.
|
To post a message in this thread, you need to log in with your Sierra Chart account: