Nt 7

[NinjaTrader_Ben]

Hello,

Thank you. Someone will reply as soon as they have more information.

[NinjaTrader_Ray]

Thanks again for reporting.

We have researched this issue and are unfortunately unable to provide a resolution. The challenges we face are that the IB API in this area is not 100% clear and historically, we made adjustments to utilize IB's Daily Volume reach some level of accurancy for volume. Since we made these changes, our users have reported that volume is reported accurately however, this logic for some reason does not work in the case you have reported. We realize that this is not optimal in your case and wish it were not so. If you are a paying user of our product and feel that this limitation is unacceptable, we are happy to provide you a full refund. Just send an email to our sales group and reference this post.

[Goose4all]

will there be a solution in NT7?

or will this be a permanent issue?

[NinjaTrader_Jason]

Unfortunately there will not be a solution with the release of NinjaTrader 7.

[paulchow2k]

Unfortunately there will not be a solution with the release of NinjaTrader 7.

Jason,
I looked around other packages Time & Sales Solution that interfaces with Interactive Brokers for the last few days. I looks like I might have found hints on how another package get around this problem. I want to stick with NinjaTrader and I'll be in heaven if we could fix this issue.

paul

http://www.amibroker.com/ib.html

+ fix for non-US indices traded with different currencies than USD+ Implemented workaround to IB weird way of sending tickSize events

Problem was that IB sometimes repeats many times the same tick and sometimes skips some ticks and cumulate them into one tickSize LAST_SIZE event.
This is because IB feed was NOT designed as tick-by-tick and never intended to create time&sales series, but rather solely to update TWS display grid.
Now the plugin tries to workaround this weirdness by ignoring duplicate tickSize LAST_SIZE events (with the same size) and correcting missing ticks usign CUMULATIVE volume sent with tickSize VOLUME event. Correction is needed because without it we would end up having incorrect total volume (sometimes real trades may have same events so multiple REAL ticks may have same price/size, unfortunatelly there is no way to detect whenever it is real trade or duplicate generated by IB, so correction according to cumulative volume is the only way to go).

[NinjaTrader_Dierk]

Thanks for sharing this. We will consider applying code changes with upcoming NT releases. However, due to the nature of the problem (unclear IB API specs) each vendor takes a different approach. Thus, there is no guarantee this problem ever would be resolved.

[paulchow2k]

Thanks for sharing this. We will consider applying code changes with upcoming NT releases. However, due to the nature of the problem (unclear IB API specs) each vendor takes a different approach. Thus, there is no guarantee this problem ever would be resolved.

Hi Dierk,
Thanks for the letting me know. I understand that Interactive Brokers have updated the IB API http://www.interactivebrokers.com/sm...?topic=83640.0 which I understand address some of the issues.

I was wondering if NT7 in the future might update their interface.

My Australian Data provider has DDE and RTD capabilities. Will NT7 interface to an external data provider?

[PULSE has full capabilities in sharing data with Microsoft Excel. This data sharing is performed using either Dynamic Data Exchange (DDE) or RealTimeData (RTD). ]

regards

[NinjaTrader_JoshP]

Paul,

Announcements will be made when available.

[paulchow2k]

Paul,

Announcements will be made when available.

Thanks Josh,
I'm told that the Latest version of TWS API should address the Time & Sales issue that NT 6.5 is having when it comes to securities. You might also need to include currency when requesting for securities as TWS now support so many different exchanges.

Hope NT7 will support IB's new API

regards

[NinjaTrader_Dierk]

To clarify: NT never used the IB API software components but always directly accessed the sockets as documented by the IB sample code. Thus, any update on the IB API software components are irrelevant.

[TraderEyal]

Q2 is here

So, we're in Q2 now, can we have an update on the NT7 Beta please?

[NinjaTrader_Dierk]

Nothing has changed: We still plan to have the first public beta of NT7 in Q2 09.

[TraderEyal]

That's a good start :-) I was half expecting a change to the next digit on the Q counter. Are you guys going to keep us in the dark on the ETA? For what reason?

Nothing has changed: We still plan to have the first public beta of NT7 in Q2 09.

[NinjaTrader_Dierk]

Unfortunately we don't have any further information regarding the ETA at this time.

[Druid]

That's a good start :-) I was half expecting a change to the next digit on the Q counter. Are you guys going to keep us in the dark on the ETA? For what reason?

We are all anxious to get the NT 7 update but it must be remembered that software development is a complex excercise. I for one would rather have a late delivery with limited bugs than an "on time" delivery with unlimited bugs. Anyone who has dealt with Microsoft DOS and windows upgrades over the years can attest to the aggravation caused by premature software releases.