Keyboard Shortcuts
Likes
Search
TWS Gateway: Requested market data is not subscribed
I am trying to get market data (reqMktData) for IBM. I define a contract like this:
contract = Contract()I then connect to the gateway I got running: app = TwsApp()From the gateway, I keep getting: 17:38:12:884 -> ---9-1-1-
17:38:12:945 -> ---54-2--1-2104-Market data farm connection is OK:usfarm-
17:38:12:947 -> ---34-2--1-2106-HMDS data farm connection is OK:ushmds-
17:38:12:951 -> ---84-2--1-2158-Sec-def data farm connection is OK:secdefil-
17:38:12:970 <- 1-11-1-0-IBM-STK--0.0---NYSE-NYSE-USD---0--0-0--
17:38:13:408 -> ---54-2--1-2119-Market data farm is connecting:usfarm.nj-
17:38:14:562 -> ---84-2--1-2104-Market data farm connection is OK:usfarm.nj-
17:38:15:049 -> ---d4-2-1-354-Requested market data is not subscribed.Delayed market data is available.IBM NYSE/TOP/ALL- I'm logged in with the paper account on the gateway. Is that what causes this? Or have I misunderstood something with subscriptions? I am subscribed to?NYSE (Network A/CTA) - Trader Workstation (in addition to all the GFIS subscription for which fees have been waived for non-pros). |
开云体育Look and you'll see in the code... exchange = "NYSE", guess what
, you and most people do not have market data from "NYSE".? I consider that to be premium and its a paid for subscription to
IB. Try ... exchange = "BATS" instead. On 19/05/2022 11:49 am, Kanda Bongo
wrote:
I am trying to get market data (reqMktData) for IBM. I define a contract like this: |
Well, we do get market data for "IBM" on exchange "NYSE" and we do not have very special market data subscriptions.
toggle quoted message
Show quoted text
The only difference between our approach and the code snippet from Kanda Bongo is that we, as a matter of practice, never make Contract objects for requests ourselves. We rather make reqContractDetails queries with the smallest amount of information that uniquely identifies the instrument (such as symbol "IBM" on exchange "NYSE") and use the full featured contract object we receive from IBKR for subsequent requests (such as market data or order placement). The coontract we receive for "IBM" on "NYSE" below and it works great for requesting market data. 闯ü谤驳别苍 "contract" : { On Thu, May 19, 2022 at 11:40 AM, Colin B Maharaj wrote:
|
Will use reqContractDetails as well.?
With regards to , I ran into some difficulties. If I understand the first table on the page correctly, both the paper and the live sessions should have access to live data simultaneously if run from the same device. That does not seem to work. My steps: 1) Logged into the client portal and set up sharing of live data with the paper account in Account Settings - Account Configuration - Paper Trading Account 2) Logged out of the client portal. 3) Started an instance of the IB gateway and used it to log into the live account. 4) Started another instance of the IB gateway (on the same device) and used it to log into the paper account. 5) Ran the script above against the live account and got live data. 6) Ran the script above against the paper account and got "Requested market data is not subscribed". I then exited both instances and started a new one with the paper account. That session got access to live data without problems. Am I reading the table wrong? Or has it got something to do with the IB Gateway? I see it is not mentioned in the notes at the bottom of . Thanks. |
works well for us and you read that table correctly. I see no reason why "IB Gateway" should act any different from TWS for the purpose of data sharing and believe the term "TWS" includes "IB Gateway".
toggle quoted message
Show quoted text
I am wondering whether it just takes (took) a little time for your sharing setting change to propagate to the entire IBKR infrastructure. Certain subscription changes, for example, may not take place until after the nightly maintenance window. 闯ü谤驳别苍 On Fri, May 20, 2022 at 11:36 AM, Kanda Bongo wrote: Will use reqContractDetails as well.? |
开云体育Interesting thought, but as that Wikipedia article also says, ‘Many network interfaces, however, support changing their MAC address’ and ‘two NICs connected to two different networks can share the same MAC address’. ? So if your guess is correct, that would give a potential way to overcome this restriction. For example, I run a set of virtual machines under Hyper-V, and that allows the virtual network adapters’ MAC address to be changed. So I could potentially set up clients on two different virtual networks, give them the same MAC address, and see if that bypasses the restriction. Might be an interesting experiment to try (when there’s nothing better to do…). |
开云体育I just wanted to add that I’m not trying to suggest we should actually try to get round this restriction on any kind of real usage, just that this experiment might confirm that it is in fact the MAC address that is used to check for the same device. ? We should of course abide by the terms and conditions that IB holds us to. ? ? From: [email protected] <[email protected]> On Behalf Of Richard L King
Sent: 04 July 2022 10:48 To: [email protected] Subject: Re: [TWS API] TWS Gateway: Requested market data is not subscribed ? Interesting thought, but as that Wikipedia article also says, ‘Many network interfaces, however, support changing their MAC address’ and ‘two NICs connected to two different networks can share the same MAC address’. ? So if your guess is correct, that would give a potential way to overcome this restriction. For example, I run a set of virtual machines under Hyper-V, and that allows the virtual network adapters’ MAC address to be changed. So I could potentially set up clients on two different virtual networks, give them the same MAC address, and see if that bypasses the restriction. Might be an interesting experiment to try (when there’s nothing better to do…). |
With a browser there's standard information passed back to the server (browser & version, OS & version, screen size, etc). When TWS or the Gateway connects who knows what is sent. It might send all sorts of data including it's own version number, the MAC address, the processor serial number, etc. Anything to identify a unique device.
|