开云体育

Here is my call -> reqMktDepth(reqId, m_contract, 5, false, TagValueListSPtr()); I am incrementing reqId every time I request, and the contract is for NQ e-mini expiring for december, NQZ3. My algo

Fantastic! That was the issue. Now works. Thank you very much Jurgen and Gordon for you quick responses and assistance. Very grateful indeed!

I can't say for sure, but I can believe that this case would not generate an error. For TWS/IBGW this could very much look like on order change. They may not look at those two as separate orders

Jürgen did answer while I was also answering. His suggestion is sounder, you should avoid "hard" assignment of order id.

should be +2 I would expect an error message to be generated but as the "transmit" is collective maybe your takeprofit it is silently overwritten by your trailstop. I am not familiar enough with

Without a lot of research into your code what jumps at me is that you assign the same orderId to the profitTaker and trailStop orders. Both are set to "parent.orderId + 1'. Using this incremental

I am at my wits end here, and have pulled out what his left of my hair trying to resolve this. The code below is basically to place two identical orders, but one with take profit and the other

Any clue you can give on which instrument generate it ? At what time ? How many rows did you look for ? What did you choose for isSmartDepth ? I would be very interested to know if you still see

Hi All, Lately, I have been seeing the error code: 317 periodically appear when streaming reqMktDepth() repeatedly, in my main trade logic loop. Currently, I am building the order book through the

/g/insync/message/9550 Think you need to join the ib -insync group. There more code examples there.

Hi all, Have a newbie question here. I've gone through the notebooks and code recipes on the ib-insync page but needing more example code. Where can I find more extensive code samples based on

Jurgen, I will perform this check from now on.

Richard, I think you're spot on,? can now remember I have had a power failure when testing over the weekend, this is probably when it messed up. Thank you for the insights, good to know!

The latest order ids for each client id are stored, on the client computer, in the xml settings files for TWS and Gateway For example my tws.xml has this: <MapOfStrings varName="ddeIdMap"> <Entry

Yes I can see now LMT BUY 100.000000@0 zero price somehow. Thank you!

" Field #44 ( https://www.onixs.biz/fix-dictionary/4.2/tagnum_44.html ) " in the error message refers to the FIX protocol TWS/IBGW use when they communicate with IBKR. It's a "price" field, so you

We don't have enough detail about your setup to give you a definitive answer, but my best guess is that your client does not properly manage the next valid orderId. It is not sufficient that you

Yes, next valid is requested first thing in the morning. Sorry can you elaborate, why a week?

Got multiple errors like this lately: ibapi.wrapper: ANSWER error {'reqId': 161494, 'errorCode': 201, 'errorString': 'Order rejected - reason:Message must contain field # 44',

First of all this is really weird case. I never seen this type of issue. Are you waiting for next valid order id event before starting with other things? But if you really want to Hack it then use