|
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 been using Neoticker RT with IQFeed for two months, and I'm very happy with both of the products (I've had IQFeed for two years with very few complaints). The service from both companies is exceptional." - Comment from Public Forum
"With HUGE volume on AAPL and RIMM for 2 days, everyone in a trading room was whining about freezes, crashes and lag with *******, RealTick, TS and Cyber. InvestorRT with IQFeed was rock solid. I mean SOLID!" - Comment from Public IRC Chat
"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
"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
"Thank God for your Data Feed as the only Zippers I see are on my pants (LOL), and no more 200 pip spikes to mess up charts." - Comment from Spiro via Email
"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
"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
"Can I get another account from you? I am tired of ******* going down so often" - Comment from George
"Everything is working amazing now. I'm already impressed with the true-tick feed of IQFeed and it's ability to support my 480 symbol layout." - Comment from Tyler via Email
"I just wanted to tell you what a fine job you have been doing. While *******, from what I hear, has been down and out, off and on, IQ feed has held like a champ this week." - Comment from Shirin
|
|
|
|
Joined: |
Mar 24, 2023 10:47 AM |
Last Post: |
Apr 7, 2023 09:28 AM |
Last Visit: |
Apr 7, 2023 09:28 AM |
Website: |
|
Location: |
|
Occupation: |
|
Interests: |
|
|
|
drjubbs has contributed to 3 posts out of 21176 total posts
(0.01%) in 371 days (0.01 posts per day).
20 Most recent posts:
Thanks! It was the older protocol tripping me up, and a stupid mistake. I was setting the protocol on the admin port but not the history port.
I actually want LabelAtBeginning=1, the 0 in my command was an error. I initially left this parameter off, because I read the default was LabelAtBeginning=1. But I guess the default changed between protocol versions, which is why I later manually specified it (but then did so incorrectly).
Now to fetch a day's data with 0:00 being the first bar, I'm doing:
HIT,@ES#,60,20221101 000000,20221201 000000,,,,,,,s,1\r\n
Which is giving me what I want.
I basically see it every day:
HIT,@ES#,60,20221101,20221101,,,,,,,0\r\n
Here's the beginning of the reply, 0:00 is missing...
datetime high low open last volume 11/1/2022 0:01 3898 3897.5 3897.5 3897.75 63 11/1/2022 0:02 3897.75 3896.75 3897.75 3897 66 11/1/2022 0:03 3897.25 3896.5 3897 3896.75 60 11/1/2022 0:04 3896.75 3896.25 3896.75 3896.5 72
And here's the response around the transition to overnight trading. 17:00 has a trade, which it shouldn't if we're labeling beginning of period, and 18:00 is missing.
datetime high low open last volume 11/1/2022 16:59 3862.25 3861.75 3862 3862.25 255 11/1/2022 17:00 3862.25 3861.75 3862.25 3861.75 261 11/1/2022 18:01 3865.75 3862.75 3863 3864.25 539 11/1/2022 18:02 3864.5 3863.25 3864.5 3863.25 116
I'm having some trouble which I think is related to this topic. I'm making a HIT request for @ES#, 60 second interval.
I notice that 0:00:00 is missing for the day and after-hours trading starts at 18:01:00. This would be consistent with LabelAtBeginning being set to 0, but I tried using the default (which should be 1) and explicitly setting this argument to 1, and neither changed the result.
Am I doing something wrong? What am I missing?
|
|