Open position not displayed for CL and COIL

[chunhaoqi]

NT revision

Are there any plans to include this new API in the near future NT revisions?

[NinjaTrader_Dierk]

Sure, I outlined the sequence of actions in my post below.

[msawusch]

Status?

Did Interactive Brokers provide the new API and if so what is the status on this?

[NinjaTrader_Dierk]

IB did not yet provide a new API yet. IB did not provide an ETA.

[Harry]

Is this serious?

The problem does not look to difficult: IB's API communicates the month of the last trading date, and NT takes this as the contract month. For most of the futures this is identical, but for oils the last trading date belongs to the month prior to the contract month.

Starting from April NT and IB are only partly compatible! I really think that basic and simple problems like this one should be quickly solved.

[NinjaTrader_Dierk]

There is no need for speculation: IB confirmed that an TWS API change would need to take place. We will keep you updated as that API change was published by IB and incorporated in NT. Unfortunately the originating issue is beyond our control.

[Harry]

No good publicity for IB

Response from IB at 2009/07/21 confirms what Dierk says:

"IB is completely aware of the issue and this is a currently a project that is being worked on. Unfortunately this project has not been completed and may take a couple of months to be rolled out. Note: API Version 9.6 was released on January 20th. Since January 20th IB has made two modifications to that Build (current version 9.62). Unfortunately these updates where for other changes made to the API. Please look at the Release Notes in the Future to see when IB has released an update on this issue."

This is not at all a good publicity for IB. The problem created with the January release of the API is still months away from being solved in July. I suppose none of the customers of Interactive Brokers uses Ninja Trader to trade energy futures and vice versa.....

[garciaal]

Has this issue been resolved?

[NinjaTrader_Dierk]

Unfortunately not, since we're still waiting for IB

[msawusch]

IB says they already updated the API

[FONT='Arial','sans-serif']I received the email correspondence below from IB which states that they have already changed the API "awhile ago" Thus apparently we are now waiting on Ninjatrader to fix this problem. Please let us know the status. [/FONT]



[FONT='Arial','sans-serif']Mark,[/FONT]
[FONT='Arial','sans-serif']The changes were made to our code awhile ago.[/FONT]
[FONT='Arial','sans-serif']
[FONT='Verdana','sans-serif']David Nelson[/FONT]
[/FONT]
[FONT='Tahoma','sans-serif']From:[/FONT][FONT='Tahoma','sans-serif'] Mark Sawusch [mailto:[email protected]]
Sent: Wednesday, August 19, 2009 7:38 PM
To: [email protected]
Subject: RE: Forum API item[/FONT]



[FONT='Verdana','sans-serif']Please let me know what you mean by "we have addressed it." Does that mean you have made the necessary changes to the API or the changes to the API are still waiting to be done or you are not going to change the API?
Thanks,
Mark Sawusch
[/FONT]
[FONT='Verdana','sans-serif']From: [email protected]
To: [email protected]
Subject: FW: Forum API item
Date: Wed, 19 Aug 2009 14:28:04 -0400[/FONT]
[FONT='Verdana','sans-serif']Msaw1,[/FONT]
[FONT='Verdana','sans-serif']You submitted the suggestion below to the TWS feature Poll. [/FONT]
[FONT='Verdana','sans-serif']Ninjatrader has brought this to our attention a while ago and we have addressed it. [/FONT]
[FONT='Verdana','sans-serif']Thanks[/FONT]
[FONT='Verdana','sans-serif']David Nelson[/FONT]

[FONT='Verdana','sans-serif']4858[/FONT]

[FONT='Verdana','sans-serif']Added:[/FONT][FONT='Verdana','sans-serif'] 2009-07-22 13:39:02

Title: Oil Futures - API displaying the wrong date

Submitted by: msaw1
Please fix the bug (as discussed below) which makes it impossible to trade oil futures using Ninjatrader.

The reason why the Executions are seemingly displaying the wrong date is because the Execution is displaying the Expiration Date and not the Expiry month. Note: The Expiration Date is defined as the day the selected future contract will expire with IB, which can be different from the Expiry. Example: CL > May 09 expires on April 21st, '09 CL > June 09 expires on May 19th, '09 NG > May 09 expires on April 28th, '09 NG > June 09 expires on May 27th, '09 COIL > June 09 expires on May 14th '09 COIL > July 09 expires on June 15th '09 So if you submit orders for the above contracts the - State = accepted for.... will display the contract in the following format: "Underlying" & Expiry in format "MM-YY" but the Execution will show the contract in the format: "Underlying" & "Expiration Date in format MM-YY" Regards, -Angel API Technical Support[/FONT]

[NinjaTrader_Dierk]

I will ask again IB tech support on the status of that subject and will let you know.

[NinjaTrader_Dierk]

IB tech support told me that the TWS API required is not yet available.

[chunhaoqi]

IB API Beta Notes

I notice the following in IB API Beta notes. Is NT IB connector going to use this feature soon?

Fields added to the Contract Details Object
The following fields have been added to the Contract Details object:

• String contractMonth
• String industry
• String category
• String subcategory
• String timeZoneId
• String tradingHours
• String liquidHours

[NinjaTrader_Dierk]

This is not the information which we needed. IB announced to provide the information we need on the relevant events. Unfortunately there is no ETA yet.

[noincomenojobnoassets]

Hi guys,

since the inconsistency problem apparently still persists:

I've tried TWS 887 with NT 6.5.1000.13, and it looks like it's working so far. No wrong months and accurate display of positions and contracts in both TWS and NT.

No guarantees, of course, but to me it looks like this problem can still be circumvented by using TWS 887, even with newer NT versions.

Greetz


n.i.n.j.n.a.