Hi, Support or Users!
I have an issue with sending the limit orders to TWS thru API. I tried to use the order manager to get a quote and form a limit order, stage, or send it directly from here. A few days ago I was successful with the same but IBKR demo account during market hours only with streaming from Yahoo. Now I'm trying the same with a real account before and after the market start - unsuccessful. The wealth lab crashes with no messages and logs available. For test, I tried to use excel trader to TWS API with good results, so I assume TWS settings are OK.
Any advice?
I have an issue with sending the limit orders to TWS thru API. I tried to use the order manager to get a quote and form a limit order, stage, or send it directly from here. A few days ago I was successful with the same but IBKR demo account during market hours only with streaming from Yahoo. Now I'm trying the same with a real account before and after the market start - unsuccessful. The wealth lab crashes with no messages and logs available. For test, I tried to use excel trader to TWS API with good results, so I assume TWS settings are OK.
Any advice?
Rename
Which WealthLab and IB Provider Builds?
What symbol?
When does it "crash", exactly?
From the description it sounds like you're connected to IB, entering a symbol in the Order Manager for a manual trade and tabbing off. Is that when it crashes?
Posting a picture of the crash environment may help.
What symbol?
When does it "crash", exactly?
From the description it sounds like you're connected to IB, entering a symbol in the Order Manager for a manual trade and tabbing off. Is that when it crashes?
Posting a picture of the crash environment may help.
QUOTE:This has nothing to do with WealthLab's connection to TWS unless you're trying to use the same ClientId. That would be a problem, though it certainly shouldn't result in a crash.
For test, I tried to use excel trader to TWS API with good results, so I assume TWS settings are OK.
Hi, latest today builds uploaded. TWS updated too.
TSLA, AAPL tried
It crashes any attempt to send the order, from the order mgr. and also when the triggered position being to sent TWS from quotes window.
TSLA, AAPL tried
It crashes any attempt to send the order, from the order mgr. and also when the triggered position being to sent TWS from quotes window.
Hi,
Please upload a screenshot of what you think is the crash when replying. Thanks.
Please upload a screenshot of what you think is the crash when replying. Thanks.
Also, what version of TWS are you using? It's important that it's at least 10.12 to be compatible with the API version WealthLab uses.
After the "place" button push WL collapse. A bit complex to catch by prn scr. No logs and messages show. Just disappears.
Latest TWS reinstalled today
There must be a local settings issue that's not handled properly.
What is your locale - "Region" and "Regional Format"?
For what it's worth, this is what we see.
What is your locale - "Region" and "Regional Format"?
For what it's worth, this is what we see.
Cone, I've had the same issue and it was a local settings issue. You can add a pre startup check to wl to ensure this and other critical machine settings are ok
There are no critical machine settings that I'm aware of. If the software isn't handling the locale correctly, then it's a bug that has to be fixed.
This is Windows 10 Rus, so the settings are the default for this region.
The error is occurring in an IBApi parser when:
1. the Streaming Provider subscribes to BTC.USD (5-second) bars. We do that in order to get a round-the-clock "heartbeat". This occurs upon the first streaming subscription - in this case, as soon as you tab off the symbol box.
- AND -
2. The digit grouping symbols is a whitespace.
I expected this would be a problem with any symbol that returned prices above $1,000, but it's not - just BTC.USD.
We'll figure out a way around it in the next release (or maybe IB can fix it on their end), but for now, the only way to get past it is to use a digit grouping symbol that's anything but a white space. :/
1. the Streaming Provider subscribes to BTC.USD (5-second) bars. We do that in order to get a round-the-clock "heartbeat". This occurs upon the first streaming subscription - in this case, as soon as you tab off the symbol box.
- AND -
2. The digit grouping symbols is a whitespace.
I expected this would be a problem with any symbol that returned prices above $1,000, but it's not - just BTC.USD.
We'll figure out a way around it in the next release (or maybe IB can fix it on their end), but for now, the only way to get past it is to use a digit grouping symbol that's anything but a white space. :/
Thanks, Cone, ww5, seems I get it working, after the change of regional settings to western (the US taken in my case). No need to reinstall Windows, just changed the settings and reboot the machine.
Hi. I am on trial, but I hope you can help me with information.
IB Extension crashes when I try to get any historical data(any stock, T/KO/BAC/etc) from TWS API.
The only workaround is to change Regional format in Windows to "English(United States)". The sample IB API C# app and another charting software(will not mention it here) doesn't care about region settings.
Do you plan to fix this bug?
Without taking this bug and some Binance Extension bugs into account, WL8 is great piece of software and I would like to use it after the trial period ends.
Environment:
Windows 10 LTSC 21H2 Build 19044.2130
Windows Region settings: Country: Poland; Regional format: Polish (Poland)
TWS 10.22.1f
Wealth-Lab 8 Build 33
Interactive Brokers Extension Build 27
IB Extension crashes when I try to get any historical data(any stock, T/KO/BAC/etc) from TWS API.
The only workaround is to change Regional format in Windows to "English(United States)". The sample IB API C# app and another charting software(will not mention it here) doesn't care about region settings.
Do you plan to fix this bug?
Without taking this bug and some Binance Extension bugs into account, WL8 is great piece of software and I would like to use it after the trial period ends.
Environment:
Windows 10 LTSC 21H2 Build 19044.2130
Windows Region settings: Country: Poland; Regional format: Polish (Poland)
TWS 10.22.1f
Wealth-Lab 8 Build 33
Interactive Brokers Extension Build 27
As far as I can tell, this is a bug in the IBApi - its signature is all over that call stack. I'll investigate some more to be sure, but it needs to be fixed by IB.
Does Poland use white spaces for the (thousand) group separator?
Does Poland use white spaces for the (thousand) group separator?
You're not on a trial @hotrad, you're the blacklisted user comm. No sense to hide behind Polish VPNs.🤷♂️
I just updated the IBAPI to 10.22 latest and could *not* duplicate the problem while using a whitespace for the digit grouping symbol.
@Geotrader, I'm not sure if you're still having trouble, but update to IB Build 30 when becomes available.
@Geotrader, I'm not sure if you're still having trouble, but update to IB Build 30 when becomes available.
Your Response
Post
Edit Post
Login is required