Join the 80,000 other DTN customers who enjoy the fastest, most reliable data available. There is no better value than DTN!

(Move your cursor to this area to pause scrolling)




"I've never had DTN go out on me since switching. ******* would go down a couple times every month when I was using them." - Comment from Bryce in AL.
"I am a hedge fund manager here. It’s funny, I have a Bloomberg terminal and a Bridge feed, but I still like having my DTN feed!" - Comment from Feras
"I've been using IQFeed 4 in a multi-threaded situation for the last week or two on 2600 symbols or so with 100 simultaneous daily charts, and I have had 100% responsiveness." - Comment from Scott
"Very impressed with the quality of your feed - ******* is a real donkey in comparison." - Comment from A.C. via Email
"Boy, probably spent a thousand hours trying to get ******* API to work right. And now two hours to have something running with IQFeed. Hmmm, guess I was pretty stupid to fight rather than switch all this time. And have gotten more customer service from you guys already than total from them… in five years." - Comment from Jim
"Can I get another account from you? I am tired of ******* going down so often" - Comment from George
"DTN has never given me problems. It is incredibly stable. In fact I've occasionally lost the data feed from Interactive Brokers, but still been able to trade because I'm getting good data from DTN." - Comment from Leighton
"I was on the phone with a friend who uses CQG and right after the Fed announcement, CQG was as much as 30 seconds behind DTN.IQ. Some quotes were off by as much as 15-18 cents. Your feed never missed a beat." - Comment from Roger
"I'm very glad I switched to IQFeed. It's working perfectly with no lag, even during fast market conditions." - Comment from Andy via Email
"Just a quick one to say I'm very impressed so far :) The documentation for developers is excellent and I've quickly managed to get an app written to do historical downloads. The system is very robust and pretty quick considering the extent of data that's available. The support guys have been very helpful too, in combination with the forums it's been plain sailing so far!" - Comment from Adam
Home  Search  Register  Login  Recent Posts

Information on DTN's Industries:
DTN Oil & Gas | DTN Trading | DTN Agriculture | DTN Weather
Follow DTNMarkets on Twitter
DTN.IQ/IQFeed on Twitter
DTN News and Analysis on Twitter
Viewing User Profile for: HenriM
About Contact
Joined: Sep 7, 2019 08:07 PM
Last Post: Sep 13, 2019 10:20 AM
Last Visit: Sep 14, 2019 11:59 AM
Website:  
Location:
Occupation:
Interests:
Avatar:
AIM:
ICQ:
MSN IM:
Yahoo IM:
Post Statistics
HenriM has contributed to 3 posts out of 19450 total posts (0.02%) in 209 days (0.01 posts per day).

20 Most recent posts:
IQFeed Developer Support » protocol 6.1 problem Sep 13, 2019 10:20 AM (Total replies: 5)

Thank you Gary,
problem solved:

I was downloading
IQFeed Client 6.1.0.20 September 4th, 2019 Download
from page
http://www.iqfeed.net/dev/api.cfm

when I downloaded
IQFeed (Datafeed) 6.1.0.20 September 4th, 2019 Download
http://www.iqfeed.net/index.cfm?displayaction=support§ion=download
my problem went away

Henri

IQFeed Developer Support » protocol 6.1 problem Sep 8, 2019 11:11 AM (Total replies: 5)

Thank you Yair,
I should have mentioned that before I posted this problem I have downloaded client 6.1.0.20 from September 4th but I always just download and install latest version of client without uninstalling anything. Hopefully that is the correct procedure.
I have just also checked VB value of System.Reflection.Assembly.GetExecutingAssembly().GetName().Version.ToString()
It retrieves value 6.1.0.0, which hopefully also indicates that protocol 6.1 has been installed correctly.
Thank you

Henri

IQFeed Developer Support » protocol 6.1 problem Sep 7, 2019 08:32 PM (Total replies: 5)

I'm getting response
"S,CURRENT PROTOCOL,6.0," on request S,SET PROTOCOL,6.0
and response "E,6.1 is not a valid protocol.," on request S,SET PROTOCOL,6.1
I'm using same code and only change 6.0 to 6.1 in it.
6.0 protocol works fine, but it doesn't recognize new field "Most Recent Trade Aggressor"
Any ideas?
Thank you

Henri


Time: Thu April 2, 2020 11:12 PM CFBB v1.2.0 16 ms.
© AderSoftware 2002-2003