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)




"This is an excellent value, the system is generous (allowing for 500 stocks) and stable (and really is tick-by-tick), and the support is fantastic." - Comment from Shirin via Email
"Thanks for following up with me. You guys do a great job in tech support." - Comment from Phelps
"IQ feed works very well, does not have all of the normal interruptions I have grown used to on *******" - Comment from Mark
"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
"Thanks for the great product and support. During this week of high volume trading, my QuoteTracker + IQ Feed setup never missed a beat. Also, thanks for your swiftness in responding to data issues. I was on ******* for a few years before I made the switch over early this year, and wish I had done it a long time ago." - Comment from Ken
"I just wanted to let u know that your data feed/service is by far the best!!! Your unfiltered tick data is excellent for reading order flow and none of your competitors delivers this quality of data!" - Comment from Peter via Email
"I just wanted to say how happy I am with your service. I was able to download the API docs last week and I was able to replicate Interactive Brokers historical bar queries and realtime bar queries over the weekend. That was about one of the fastest integrations that I've ever done and it works perfectly!!!!" - Comment from Jason via Email
"Everything is working great ! Very impressive client. The news refreshes better and is more pertinent than the ******* feed I paid $ 100/month for. I Also like the charts a lot." - Comment from Leon
"I noticed that ******* quotes locked up shortly after the interest rate announcement yesterday while yours stayed stable." - Comment from Ron in Utah
"Just a thank you for the very helpful and prompt assistance and services. You provided me with noticeably superior service in my setup compared to a couple of other options I had looked at." - Comment from John
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: jmcstone
About Contact
Joined: Oct 29, 2017 09:18 PM
Last Post: May 15, 2020 07:57 AM
Last Visit: May 15, 2020 07:57 AM
Website:  
Location:
Occupation:
Interests:
Avatar:
AIM:
ICQ:
MSN IM:
Yahoo IM:
Post Statistics
jmcstone has contributed to 5 posts out of 21196 total posts (0.02%) in 2,393 days (0.00 posts per day).

20 Most recent posts:
Data and Content Support » NTG Stock Split on May 01, 2020 May 15, 2020 07:57 AM (Total replies: 1)

On May 1 NTG had a 1:10 stock split - and it doesn't look like it is being reflected correctly in the daily historical data. Here is the price data that I am receiving:

2020-04-29, 201, 222, 198.5, 221, 1937527
2020-04-30, 230, 239, 205, 212, 2547621
2020-05-01, 20.67, 21.99, 18.8, 18.83, 160033
2020-05-04, 18.49, 19.0536, 17.42, 18.99, 125591

Thanks, Jeff

IQFeed Developer Support » History requests are slow to fill Feb 21, 2019 10:22 AM (Total replies: 3)

Hello,

Has there been any progress on this issue?

I am having about 50% of my requests fail due to no response from IQFeed.

Initially the program had a timeout of 5 seconds, and after reading this post, I increased it to 120 seconds. Unfortunately, increasing the timeout didn't help - I am still seeing the same failure rate.

Additional behaviour that I have noticed:
- When ran over the weekend, when there was no new data being returned - the import ran great with nearly 0 timeouts
- If I request large amounts of data for a lot of securities say - the last 10 years of minute data - it doesn't appear to have any problems
- When there is no historical data lookup response - subsequent requests on the same socket all meet the same fate - so, I have to close the socket and open a new one

Not sure if this makes any difference; but, I am running the IQFeed client in a Linux docker container.

Here is a sample portion of the IQConnect.txt (I added line numbers to each line) where it fails on line #12 - the request for ACET. It times out and opens a new socket, and tries again on line #25 - where the response is returned immediately.

1 FROM CLIENT LookupRequest 48 2 2019-02-21 15:26:15 HDT,ACAD,20190219,,,1,18,
2 TO CLIENT LookupData 48 2 2019-02-21 15:26:15 18,2019-02-19,23.7400,22.8100,23.2500,22.9800,1137206,0,
3 18,2019-02-20,23.4100,22.5800,23.0200,22.8200,923336,0,

4 TO CLIENT LookupRequest 48 2 2019-02-21 15:26:15 18,!ENDMSG!,

5 TO CLIENT LookupData 48 2 2019-02-21 15:26:15 18,!ENDMSG!,

6 TO CLIENT Admin 9 1 2019-02-21 15:26:15 S,STATS,66.112.156.224,60005,500,253,3,0,1,4,Feb 21 3:24PM,Feb 21 10:26AM,Connected,6.0.1.1,412013,175302.52,380.47,1992.07,315775.64,566.17,3588.36,

7 FROM CLIENT LookupRequest 48 2 2019-02-21 15:26:15 HDT,ACC,20190219,,,1,19,
8 TO CLIENT LookupData 48 2 2019-02-21 15:26:16 19,2019-02-19,45.7900,45.1200,45.1200,45.5800,1121809,0,
9 19,2019-02-20,45.6300,43.0500,45.4000,44.5900,2291901,0,

10 TO CLIENT LookupRequest 48 2 2019-02-21 15:26:16 19,!ENDMSG!,

11 TO CLIENT LookupData 48 2 2019-02-21 15:26:16 19,!ENDMSG!,

12 FROM CLIENT LookupRequest 48 2 2019-02-21 15:26:16 HDT,ACET,20190219,,,1,20,
13 TO CLIENT Admin 9 1 2019-02-21 15:26:16 S,STATS,66.112.156.224,60005,500,253,3,0,1,4,Feb 21 3:24PM,Feb 21 10:26AM,Connected,6.0.1.1,412013,175690.00,387.48,1974.04,316459.56,567.49,3555.73,

14 TO CLIENT Admin 9 1 2019-02-21 15:26:17 S,STATS,66.112.156.224,60005,500,253,3,0,1,4,Feb 21 3:24PM,Feb 21 10:26AM,Connected,6.0.1.1,412013,175810.31,120.31,1953.45,316737.44,564.21,3519.30,

15 TO CLIENT Admin 9 1 2019-02-21 15:26:18 S,STATS,66.112.156.224,60005,500,253,3,0,1,4,Feb 21 3:24PM,Feb 21 10:26AM,Connected,6.0.1.1,412013,176266.27,455.96,1936.99,317491.14,566.30,3488.91,

16 TO CLIENT Admin 9 1 2019-02-21 15:26:19 S,STATS,66.112.156.224,60005,500,253,3,0,1,4,Feb 21 3:24PM,Feb 21 10:26AM,Connected,6.0.1.1,412013,176729.33,463.06,1920.97,318318.65,569.15,3459.99,

17 TO CLIENT Admin 9 1 2019-02-21 15:26:20 S,STATS,66.112.156.224,60005,500,253,3,0,1,4,Feb 21 3:24PM,Feb 21 10:26AM,Connected,6.0.1.1,412013,177000.99,271.67,1903.24,318804.28,568.23,3428.00,

18 TO CLIENT Admin 9 1 2019-02-21 15:26:21 S,STATS,66.112.156.224,60005,500,253,3,0,1,4,Feb 21 3:24PM,Feb 21 10:26AM,Connected,6.0.1.1,412013,177334.88,333.89,1886.54,319422.41,568.76,3398.11,

19 TO CLIENT Admin 9 1 2019-02-21 15:26:22 S,STATS,66.112.156.224,60005,500,253,3,0,1,4,Feb 21 3:24PM,Feb 21 10:26AM,Connected,6.0.1.1,412013,177676.81,341.93,1870.28,320007.53,568.92,3368.50,

20 STATUS Information 9 0 2019-02-21 15:26:23 LOOKUP SOCKET ACCEPTED 3 -
21 TO CLIENT Admin 9 1 2019-02-21 15:26:23 S,STATS,66.112.156.224,60005,500,253,4,0,1,4,Feb 21 3:24PM,Feb 21 10:26AM,Connected,6.0.1.1,412013,178195.88,519.08,1856.21,320907.01,572.39,3342.78,

22 FROM CLIENT LookupRequest 49 3 2019-02-21 15:26:23 S,SET PROTOCOL,6.0
23 TO CLIENT LookupData 49 3 2019-02-21 15:26:23 S,CURRENT PROTOCOL,6.0

24 TO CLIENT LookupData 49 3 2019-02-21 15:26:23 S,CURRENT PROTOCOL,6.0

25 FROM CLIENT LookupRequest 49 3 2019-02-21 15:26:23 HDT,ACET,20190219,,,1,21,
26 TO CLIENT LookupData 49 3 2019-02-21 15:26:24 21,2019-02-19,1.1000,1.0300,1.0300,1.0300,388158,0,
27 21,2019-02-20,0.8100,0.3450,0.3795,0.3531,19447377,0,

28 TO CLIENT LookupRequest 49 3 2019-02-21 15:26:24 21,!ENDMSG!,

29 TO CLIENT LookupData 49 3 2019-02-21 15:26:24 21,!ENDMSG!,

30 FROM CLIENT LookupRequest 49 3 2019-02-21 15:26:24 HDT,ACGL,20190219,,,1,22,
31 TO CLIENT LookupData 49 3 2019-02-21 15:26:24 22,2019-02-19,32.1500,31.3100,31.4600,32.0700,1228392,0,
32 22,2019-02-20,32.3500,31.9700,32.1000,32.3000,1011966,0,

33 TO CLIENT LookupRequest 49 3 2019-02-21 15:26:24 22,!ENDMSG!,

34 TO CLIENT LookupData 49 3 2019-02-21 15:26:24 22,!ENDMSG!,


Let me know if there is any additional diagnostic data that would help you out - I would be more than willing to help!!

Regards, Jeff


I apologize - I reposted this question in the "DTN.IQ Client Software Support" section as the questions seem more appropriate for that area of the forum.


I am just starting to use the streaming interval bars. I plan on streaming bars on multiple securities with each security having multiple different intervals (example: 1 min bars, 5 min bars, and 15 min bars - all on the same symbol).

The documentation states that a "S,REPLACED PREVIOUS WATCH,[Symbol],[RequestID]" message may be returned. Under what circumstances will a previous watch be replaced? That is, what fields in the request must match for it to replace a previous request (Symbol, Interval, IntervalType, BeginFilterTime, EndFilterTime, ...)?

Also, the documentation is not clear if the RequestId is the previous RequestId or the new RequestId (it would actually be nice to have both values returned). In fact, the RequestId should be on the SYMBOL LIMIT REACHED and the INVALID PARAMETERS FOR REQUEST messages also - so, that you can accurately associate the message to the request.

One last question - what is the use for Update Interval? Does it delay the sending of a bar - or, does it do something such as updating a 1 min bar every 15 seconds?

Thanks


I am just starting to use the streaming interval bars. I plan on streaming bars on multiple securities with each security having multiple different intervals (example: 1 min bars, 5 min bars, and 15 min bars - all on the same symbol).

The documentation states that a "S,REPLACED PREVIOUS WATCH,[Symbol],[RequestID]" message may be returned. Under what circumstances will a previous watch be replaced? That is, what fields in the request must match for it to replace a previous request (Symbol, Interval, IntervalType, BeginFilterTime, EndFilterTime, ...)?

Also, the documentation is not clear if the RequestId is the previous RequestId or the new RequestId (it would actually be nice to have both values returned). In fact, the RequestId should be on the SYMBOL LIMIT REACHED and the INVALID PARAMETERS FOR REQUEST messages also - so, that you can accurately associate the message to the request.

One last question - what is the use for Update Interval? Does it delay the sending of a bar - or, does it do something such as updating a 1 min bar every 15 seconds?

Thanks


Time: Fri May 17, 2024 6:56 AM CFBB v1.2.0 9 ms.
© AderSoftware 2002-2003