Support Board
Date/Time: Fri, 29 Nov 2024 14:38:27 +0000
SC 2478 + TWS 10.20.1j not sending trades to IB
View Count: 332
| [2023-01-31 21:22:59] |
| Jagui1 - Posts: 14 |
|
Currently I am working with SC 2466 + TWS 10.19-1c and everything is working fine. I get intraday history and realtime stock data from IB and can open trades from SC without any problem. Today I tested the latest SC and TWS stable on another pc, to check if it was possible for me to upgrade without issues. I installed SC 2478 and TWS 10.20.1j and I get intraday history and realtime stocks data from IB but can't open trades from SC. When I try to open a stock trade at market from SC, it gets disconnected from TWS. I know that TWS caused problems lately (I've been programming with their API for a long time, I know it is far from ideal). I don't want to push or make pressure, since at least we have a working SC + TWS combo. But this won't last forever, sooner or later we'll need restored trading compatibility, because trading from SC is much better and faster than from TWS. This is the Message Log: Triggering next historical data download in queue. | 2023-01-31 20:50:57.080 No download requests in the queue to start downloads for. | 2023-01-31 20:50:57.080 Message from IB: Error reading request. Unable to parse data. java.lang.NumberFormatException: For input string: "MKT". IB Error Code: 320. Request ID: 45. | 2023-01-31 20:51:10.318 IB TWS socket (1) | Socket gracefully closed by remote side. | 2023-01-31 20:51:10.318 IB TWS socket (1) | CloseSocket call. | 2023-01-31 20:51:10.327 Connection to the external service has been lost. | 2023-01-31 20:51:10.327 IB TWS socket (1) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2023-01-31 20:51:10.327 IB TWS socket (1) | Closed. | 2023-01-31 20:51:10.327 IB TWS socket (0) | CloseSocket call. | 2023-01-31 20:51:10.355 Interactive Brokers | Disconnected. | 2023-01-31 20:51:10.355 Will reconnect to the server in 2.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2023-01-31 20:51:10.355 And also the Trade Log: Interactive Brokers | Sent reqAutoOpenOrders request | 2023-01-31 20:51:01.760
Interactive Brokers | Received Open orders end message. | 2023-01-31 20:51:01.761 Interactive Brokers | Requesting Open orders. | 2023-01-31 20:51:13.395 Interactive Brokers | Sent reqAutoOpenOrders request | 2023-01-31 20:51:13.395 Interactive Brokers | Received Open orders end message. | 2023-01-31 20:51:13.406 Trading server did not acknowledge new order | Symbol: AAPL-STK-SMART/NYSE | TradeAccount: U7263112 | InternalOrderID: 10 | ServiceOrderID: 87 | Current Status: Order Sent | 2023-01-31 20:51:13.406 * Interactive Brokers | Requesting Open orders. | 2023-01-31 20:51:39.467 Interactive Brokers | Sent reqAutoOpenOrders request | 2023-01-31 20:51:39.467 Trading message from IB: Manual Order Cancel Time: The date, time, or time-zone entered is invalid. The correct format is yyyymmdd hh:mm:ss xx/xxxx where yyyymmdd and xx/xxxx are optional. E.g.: 20031126 15:59:00 US/Eastern Note that there is a space between the date and time, and between the time and time-zone. If no date is specified, current date is assumed. If no time-zone is specified, local time-zone is assumed(deprecated). You can also provide yyyymmddd-hh:mm:ss time is in UTC. Note that there is a dash between the date and time in UTC notation. Error Code: 10301. ServiceOrderID: 88. InternalOrderID: 13. | 2023-01-31 20:51:39.468 * Order cancellation failed | Manual Order Cancel Time: The date, time, or time-zone entered is invalid. The correct format is yyyymmdd hh:mm:ss xx/xxxx where yyyymmdd and xx/xxxx are optional. E.g.: 20031126 15:59:00 US/Eastern Note that there is a space between the date and time, and between the time and time-zone. If no date is specified, current date is assumed. If no time-zone is specified, local time-zone is assumed(deprecated). You can also provide yyyymmddd-hh:mm:ss time is in UTC. Note that there is a dash between the date and time in UTC notation. Internal Order ID: 13. Service Order ID: 88. Symbol: AAPL-STK-SMART/NYSE. Account: U7263112 | 2023-01-31 20:51:39.468 * Requesting order status for non-responsive order. Time since last action: 56.5 seconds | Symbol: AAPL-STK-SMART/NYSE | TradeAccount: U7263112 | InternalOrderID: 13 | ServiceOrderID: 88 | Current Status: Order Sent | 2023-01-31 20:52:36.272 * Trade Order Error - Order timed-out waiting for response from service/exchange server. Internal Order ID: 13. Service Order ID: 88. Symbol: AAPL-STK-SMART/NYSE. Account: U7263112 | 2023-01-31 20:53:06.271 * TradeActivity files query time: 0.007050 seconds. Entries: 0. Current queries: 1 | 2023-01-31 20:59:54.159 |
| [2023-02-02 14:24:18] |
| Sierra_Chart Engineering - Posts: 17228 |
|
We will look this over.
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, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2023-02-02 15:24:01] |
| fxzen - Posts: 14 |
|
Thank you, just confirming same issue, same versions.
|
To post a message in this thread, you need to log in with your Sierra Chart account: