For a few days we have a problem connecting the TWS (IB). The WL/IB connection is already working - but as soon as we go to "Account" or "Quotes Window" Wealth Lab crashes when IB is connected.
If IB is not connected, there is no crash wenn go to Quotes or Account.
But when we want to get streaming quotes from IB, WL crashes again, even though IB hasn't been connected yet.
What is the best way for us to document the error so that you can support us? What can trigger the error?
We have already reinstalled WL with "repair". The problem is still ongoing.
We would now like to uninstall the single extension from IB to fix the error. Does that make sense or how do you do that? Or do you have other suggestions?
Thanks!
If IB is not connected, there is no crash wenn go to Quotes or Account.
But when we want to get streaming quotes from IB, WL crashes again, even though IB hasn't been connected yet.
What is the best way for us to document the error so that you can support us? What can trigger the error?
We have already reinstalled WL with "repair". The problem is still ongoing.
We would now like to uninstall the single extension from IB to fix the error. Does that make sense or how do you do that? Or do you have other suggestions?
Thanks!
Rename
1. The first thing to consider is, what has changed in the last few days when the problem started?
2. What versions are you running?
a. WealthLab
b. IB Provider
c. IB TWS
Re: .. get streaming quotes... even though IB hasn't been connected yet.
When you request anything from the IB provider, the first thing it does is connect to a running instance of TWS.
2. What versions are you running?
a. WealthLab
b. IB Provider
c. IB TWS
Re: .. get streaming quotes... even though IB hasn't been connected yet.
When you request anything from the IB provider, the first thing it does is connect to a running instance of TWS.
I have to correct what I said above. The crash also happens without connecting WL to IB.
I was able to save an error message instead.
I was able to save an error message instead.
1. The first thing to consider is, what has changed in the last few days when the problem started?
The API settings were temporarily changed in the TWS because we want to test access via the server. But that was reset to the original settings.
2. What versions are you running?
a. WealthLab
Build 32
b. IB Provider
c. IB TWS
latest: Build 10.21.1p - March 7th
The API settings were temporarily changed in the TWS because we want to test access via the server. But that was reset to the original settings.
2. What versions are you running?
a. WealthLab
Build 32
b. IB Provider
c. IB TWS
latest: Build 10.21.1p - March 7th
Okay, this popped up a couple weeks ago. This is an IB problem. It's caused because we're subscribing to BTC.USD for the most coverage to generate a "heartbeat" and the IBApi.EDecoder is having problems with a " " (whitespace) thousands separator.
We're solving it in the next IB Provider by not subscribing to BTC for the heartbeat if the local group separator is a white space. Although now I'm reconsidering that and may just use a forex contract like EUR.USD.
The only way you can get around it now is to change your machine's thousands separator. Unfortunately, this will affect some of your WealthLab settings, so it's best to start with a fresh settings file if you do that.
We're solving it in the next IB Provider by not subscribing to BTC for the heartbeat if the local group separator is a white space. Although now I'm reconsidering that and may just use a forex contract like EUR.USD.
The only way you can get around it now is to change your machine's thousands separator. Unfortunately, this will affect some of your WealthLab settings, so it's best to start with a fresh settings file if you do that.
Ok - Thanks.
That means I can't connect IB to WL at the moment and have to wait for your IB Extension update, right? The workaround you suggested is to complicated...
But that also means that TWS/IB live trading via various APIs is currently not possible, if I understand that correctly.
Is this an issue affecting all customers or is it a problem related to my local settings?
That means I can't connect IB to WL at the moment and have to wait for your IB Extension update, right? The workaround you suggested is to complicated...
But that also means that TWS/IB live trading via various APIs is currently not possible, if I understand that correctly.
Is this an issue affecting all customers or is it a problem related to my local settings?
It's an IB API Decoder problem with your local settings that appears when a client subscribes to anything that has a quote above 1000.
Corrected above - it happens when the currency group separator is a whitespace.
Corrected above - it happens when the currency group separator is a whitespace.
Your Response
Post
Edit Post
Login is required