Registered: Mar 2010
02-23-12 04:55 PM
Quote from travis:
In some cases (rarely but it is definitely a problem) I start my automated trading and, a few hours later, within the same session (within those 24 hours that do not have the forced disconnection), presumably after a disconnection, I get asked again for the login code from the IB security code card authentication.
What happens is I connect to my server, and see the popup window asking for the security codes, and since my trading is automated, this also means that the DDE data feed to excel has stopped (sometimes for hours) and my daily automated trading session has been compromised.
This has been happening for the past two months, at the frequency of once every two weeks, so it has happened already four times. Does anyone (from IB or forum users) know what I could do to fix this problem, which is not just my problem presumably? This is a very recent problem and before this, disconnections did not cause it, and IB TWS could get reconnected without the need for me to fill in the security codes again.
i pointed out this several times and also sent a personal email to the person in charge about that. See for instance:
They think they know how to code and do not listen to users.
my email to AN:
"Hi ... ,
this has already been outlined in the previous suggestions. But let me expand this point for you, because crucial.
Fully automated traders with good capital are clearly the the best clients for IB, as the bot generates automatically a lot of daily commissions (depending on the strategy chosen)
It is essential that operations for automated users be smooth, as any permanent interruption - that is not due to normal maintenance or market close - will have the following consequences:
- You lose commissions
- Disrupt strategies, with potential losses for the client, which may have his capability to trade reduced
- irritate clients
A bot tries to stay connected with an IB application (TWS/Gateway) all the time, clearly to ensure continuity to the trading operations.
You will have your periods of maintenance, market will closed and so on, but that is irrelevant and perfectly fine.
What is important is that, once an user starts up the TWS or the GATEWAY and the system challenges him, no matter what,
it should NEVER challenge the user again, as long as the application STAYS UP ON HIS COMPUTER. (Clearly, if, instead, the user shuts down the application, it is right to challenge him).
This is crucial. Imagine the common scenario where you have a good investors trading robotically and he leaves for 2-3 weeks (this happens all the time) leaving the bot working. What he can find at his return is that the Gateway after a disconnection is asking for credential (this happens!).
This would mean terrible losses for both the trader but also IB (which would lose a boatload of commissions.)
You would probably loose the client too, if this keeps happening.
Place a (nonserializable) boolean flag ("userChallenged") in both TWS and Gateway and just initialize it to true at start up, after the very first challenge.
When the flag is true the user should never ever be challenged: simply reconnect to IB using the stored good credentials (if system is on) or keep looping reconnection attempts (if IB system in maintenance or down).
PS. See screenshot attached.
Disconnections are normal and fine, but do not rechallenge! (occasionally it does, as it is now)
Blocking a trading machine with the challenge means that you lose commissions and the client gets very angry because of disruption of operations.
The only reactions i got are excuses and "explanations" which are much more insulting than direct offenses. Looks like that making up excuses is easier than making a 5 mins change.
But they do have time to add "features" nobody asked for ...