I could not stream the CBOE e-mini [@YM#, @ES#, @NQ# and @RTY#] using the IQFeed B11. I have these in a streaming "Quotes and Price Triggers" window as symbol quotes and the S&P @ES# in a streaming inter-day chart. However the chart would update with "Reload Chart Data from Provider" with the latest data but no streaming.
After trying several things for a period of time, I went back and reinstall WL8 IQFeed B10; now things are back up running as before.
After trying several things for a period of time, I went back and reinstall WL8 IQFeed B10; now things are back up running as before.
Rename
Thanks for the info and we'll work on that. If anyone sees more incompatibilities with that Build 11 upgrade to IQFeed 6.2 protocol, please let us know.
When I tried it with Build 11, streaming worked fine for those symbols as long as you have a record for those symbols in Tools > Markets & Symbols. You need to assign a futures market to those symbols, like CME, otherwise it will default to the U.S. Market and filter the ticks if the Pre/Post Filter is checked.
So the solution is to:
1. Assign the market in Tools > Markets & Symbols
2. Or simply uncheck the market Filter at the bottom of the chart (or in the Strategy Monitor settings).
It's important to create these records anyway to give WealthLab the contract specifications.
So the solution is to:
1. Assign the market in Tools > Markets & Symbols
2. Or simply uncheck the market Filter at the bottom of the chart (or in the Strategy Monitor settings).
It's important to create these records anyway to give WealthLab the contract specifications.
Thanks,
I looked at the change log after the fact (this morning), I did not change over to the new client; I am using the 6.1.0.20 IQFeed client. FYI, I always uncheck Pre/Post filter and have a market for those symbols.
So this leads to a new question, will WL6 work with the new IQFeed client (backward compatibility)? No way??
I looked at the change log after the fact (this morning), I did not change over to the new client; I am using the 6.1.0.20 IQFeed client. FYI, I always uncheck Pre/Post filter and have a market for those symbols.
So this leads to a new question, will WL6 work with the new IQFeed client (backward compatibility)? No way??
QUOTE:Build 11 requires you to upgrade the IQFeed client to 6.2 because Build 11 uses that protocol. Consequently, I'd expect incompatibilities with WL IQ Provider Build 11 with IQFeed clients prior to 6.2.
will WL6 work with the new IQFeed client (backward compatibility)?
On the other hand, you can use WL IQ Provider Build 10 with IQFeed clients 6.2 or 6.1. That's because 6.2 also supports the 6.1 protocol.
If you want to ease into the upgrade, you can first upgrade to IQFeed client 6.2 and use it with WL IQ Provider Build 10. Later you can upgrade to WL IQ Provider Build 11.
Really there were no other changes than pointing to the new protocol, which doesn't affect anything that Wealth-Lab currently uses. It just brings us up-to-date to use newer features, if required.
Does this apply to WL6?
An upgrade for WL6 customers is not required. They can upgrade the IQFeed client to 6.2, but continue to use WL6 with the adapter that hits the 6.1 protocol
Okay thanks,
I will upgrade during post-market. I have one more question, you may or may not know the answer.
I'm currently running both WL6 and WL8 at the same time on the same machine using the IQFeed 6.1 client. If I do this with the 6.2 client and one is using 6.1 protocol and the other using 6.2 protocol, will both WL6 and WL8 work in this configuration?
[FYI, Have not converted all WL6 code to WL8 code]
I will upgrade during post-market. I have one more question, you may or may not know the answer.
I'm currently running both WL6 and WL8 at the same time on the same machine using the IQFeed 6.1 client. If I do this with the 6.2 client and one is using 6.1 protocol and the other using 6.2 protocol, will both WL6 and WL8 work in this configuration?
[FYI, Have not converted all WL6 code to WL8 code]
Yes. Answered in Post #6.
Your support is greatly appreciated!
Your Response
Post
Edit Post
Login is required