A few bugs in IB Plugin 992

[clearpicks]

There are a few bugs I found in the IB Plugin (QT build 992).

1. cancelOrder and cancelAllOrders do not work anymore.

2. If "Confirm order before submitting" and "confirm EFS Orders" are checked, afting clicking the "Submit" button, the order would be submitted, however the "Order ticket dialog" would not close itslef and could not be manually closed either. The only way to keep going is to cancel the order in IB TWS, then IB Plugin would pop up an error message window showing "Failed to place order: Order Canceled -reason:".

3. All the stop orders submitted using IB Plugin APIs are marked as "will trigger only during regular trading hour" no matter how I configure the default order options in IB TWS regarding whether stop will be triggered outside of regular trading hour.

4. Somehow there are a few brokers being listed under "Trade" menu in eSignal, one is "Interactive Brokers", and the other two are shown as "IB". I know the two "TB" connections are created when I tried QuoteTrader. However I can not figure out a way to remove them. More strange thing is that after I choose to hide any one of them, the other two would also be hiden. Where is the QT configuration file located? Maybe I need to edit the QT configuration file directly to ensure a clean installation.

The first and the third are critical issues, which I can not figure out a workaround.

- Clearpicks

[eSignal_AlexM]

1 and 2. Following should be checked in TWS for correct work of IB plug-in
- Enable ActiveX
- Download Open Orders on Connection
- Fire openOrder on status change

Could you please check it?

3. support for triggering stop orders outside regular trading hours will eb added in October build.

4. You may set up your connections by running QuoteTrader Configurator located in the main menu
eSignal -> QuoteTrader Configurator

[clearpicks]

Amol.

Thank you. I forgot to check "Fire openOrder on status change" in IB TWS, which caused the problems 1 and 2.

It seems the excessive CPU usage problem I reported a few days ago has not been fixed in build 992, am I right? Hope it will be fixed in the next build.

Since I was testing my trading buttons, I just randomly sent buy/sell orders and the corresponsive protective stop orders. Then I noticed some orders got cancelled due to error 202 "Order Cancelled - reason: Order would cross related resting order". Could you tell me what that means? What is the exact scenario it would occur? If some limit buy/sell orders just get cancelled and the protective stop orders are still sent out, and I am not noticed in a prominent way ( a loud sound, a flashing warning sign, a pop up warning window, etc. ), it might cause big problems in real trading.

- Clearpicks

Originally posted by amol
1 and 2. Following should be checked in TWS for correct work of IB plug-in
- Enable ActiveX
- Download Open Orders on Connection
- Fire openOrder on status change

Could you please check it?

3. support for triggering stop orders outside regular trading hours will eb added in October build.

4. You may set up your connections by running QuoteTrader Configurator located in the main menu
eSignal -> QuoteTrader Configurator

[eSignal_AlexM]

Excessive CPU usage will be resolved in October build.

Regarding 202 error you may check TWS forum here http://www.interactivebrokers.com/discus/

I've found this link on the topic:

http://www.interactivebrokers.com/cgi-bin/discus/board-auth.pl?file=/36501/26325.html

[clearpicks]

Hello Amol,

Why do some error 202 messages give reason "Order would cross related resting order" while some others do not? Please refer to the attached screenshot, especially the message 95 and 35. I looked at the order window, order 158 is a limit buy order, while the order 159 is a sell stop order. Order 159 is the protective order of order 158. Similarly order 157 is the order 156's protective stop loss order. However when you look at the Open/Close field, order 156 and 159 are marked as Close while 157 and 158 are marked as Open. How is "Close/Open" attribution assigned, is it important in TWS API?

I understand the error message 202 with no reason "Order would cross related resting order" is generated as every order cancellation, so it is a normal message. I don't know when and which part ( IB TWS or IB Server or IB Plugin ? ) automatically cancels some limit orders due to the potencial crossing related resting order.

Help is greatly appreciated.

- Clearpicks

Originally posted by amol
Excessive CPU usage will be resolved in October build.

Regarding 202 error you may check TWS forum here http://www.interactivebrokers.com/discus/

I've found this link on the topic:
http://www.interactivebrokers.com/cg...501/26325.html

[clearpicks]

Messages window

[clearpicks]

Orders window

[eSignal_AlexM]

Please, check here

http://www.interactivebrokers.com/cgi-bin/discus/board-auth.pl?file=/2/42932.html

[clearpicks]

Thank you. So I would assume it was caused by IB paper account algorithm unless I see it again in real trading account.

Could you tell me what is the purpose of "Close/Open" in orders window as well as the order comfirmation window? Thanks.

- Clearpicks

Originally posted by amol
Please, check here
http://www.interactivebrokers.com/cg...=/2/42932.html

[eSignal_AlexM]

Open/Close applicable for FA accounts only.

It means whether this order supposed to open new position or close existing one.