DTN IQFeed, DTN.IQ, DTN ProphetX Support Forums

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)

"If you are serious about your trading I would not rely on IB data for serious daytrading. Took me a while to justify the cost of IQ Feed and in the end, it's just a 2 point stop on ES. Better safe than sorry" - Comment from Public Forum

"My broker in Davenport suggested I give you a try as he uses your service and says its the best." - Comment from Bill via RT Chat

"IQ feed works very well, does not have all of the normal interruptions I have grown used to on *******" - Comment from Mark

"I had always used ******* but for the past 2 weeks have been trying DTN IQFeed. Customer support has been extraordinary. They call just to make sure your problem hasn't recurred." - Comment from Public Forum

"You have an excellent feed. Very few spikes for Spot Forex." - Comment from Public Forum Post

"I ran your IQFeed DDE vs. my broker vs. a level II window for some slow-moving options. I would see the level II quote change, then your feed update instantaneously. My broker's DDE, however, would take as much as 30 seconds to update. I am not chasing milliseconds, but half a minute is unacceptable." - Comment from Rob

"I have to tell you though that using the IQFeed API is about the easiest and cleanest I have seen for some time." - Comment from Jim

"Thanks for all of your help. Great customer service deserves to be recognized which one the reasons I've been a customer of DTN for over 10 years!" - Comment from Stuart

"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

Recent Posts

Information on DTN's Industries:
DTN Oil & Gas | DTN Trading | DTN Agriculture | DTN Weather

DTN.IQ/IQFeed on Twitter
DTN News and Analysis on Twitter

»Forums Index »Archive (2017 and earlier) »Data and Content Support »HIT timing off

Author	Topic: HIT timing off (3 messages, Page 1 of 1)
adrian -Interested User- Posts: 28 Joined: Oct 24, 2008	Posted: Jan 17, 2010 04:03 PM Msg. 1 of 3 I'm trying to get a set of 1min bars back starting at 9:30 EST and going for the next 20 minutes. I connect from Java using the TCP/IP and send: HIT,SKF,60,20100115 093000,20100115 095000,21,093000,160000,1,HIT_1,5 As I understand it, this should give data for 'SKF' in 1min (60 sec) bars, for Friday Jan 15th 2010 from 9:30am-9:50am. It will give a max of 21 bars and filters out after hours data. What I get is: HIT_1,2010-01-15 17:03:00,22.7000,22.7000,22.7000,22.7000,11787379,150, HIT_1,2010-01-15 17:05:00,22.6900,22.6900,22.6900,22.6900,11791379,4000, HIT_1,2010-01-15 17:28:00,22.7000,22.7000,22.7000,22.7000,11791879,500, HIT_1,2010-01-15 17:30:00,22.7200,22.7200,22.7200,22.7200,11791979,100, ... So it's not starting when I requested and it's giving after hours data which I said should be filtered. I tried this with similar dates on a number of other stocks and they all behaved similarly. Ideas for what I can do to fix this?
adrian -Interested User- Posts: 28 Joined: Oct 24, 2008	Posted: Jan 18, 2010 10:12 AM Msg. 2 of 3 I think I got diverted into the wrong forums, not sure how that happened. Sorry about that. And when I ran the program this morning it worked as expected. I don't know if there was some glitch over the weekend or what happened but everything's good now.
DTN_Steve_S -DTN Guru- Posts: 2093 Joined: Nov 21, 2005	Posted: Jan 19, 2010 02:12 PM Msg. 3 of 3 Hello adrian, sorry for the delay in responding. I'm glad it seems to be working for you once again. Just to verify, there was an issue with one of our server farms over the weekend that would explain the problems you saw.