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 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'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 just wanted to let you know how fast and easy I found it to integrate IQFeed into our existing Java code using your JNI client. In my experience, such things almost never go so smoothly - great job!" - Comment from Nate
"I am keeping IQFeed, much better reliabilty than *******. I may refer a few other people in the office to switch as well." - Comment from Don
"There is no doubt that IQFeed is the best data provider. I am very satisfied with your services. And IQFeed is the only one that I would recommend to my friends. Now, most of them are using your product in China." - Comment from Zhezhe
"I have been using IQFeed now for a few years in MultiCharts and I have zero complaints. Very, very rare to have any data hiccups or anything at all go wrong." - Comment from Public Forum
"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
"I would just like to say that IQFeed version 4 is running very well and I am very happy with its performance. I would also like to extend a big thanks for the fast and efficient help that I always receive. My questions and concerns are always addressed promptly. Way to go!" - Comment from Josh in CO.
"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 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
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
»Forums Index »Product Support »IQFeed Datafeed Wish List »Sequential Level1 and Level2 updates.
Author Topic: Sequential Level1 and Level2 updates. (12 messages, Page 1 of 1)

aQuant
-Interested User-
Posts: 48
Joined: Jul 20, 2012


Posted: Oct 17, 2014 02:50 PM          Msg. 1 of 12
Hello,

one thing that may be beneficial to sophisticated individuals with a limited budget (below NaNex prices) would be if Level1 updates and Level2 updates could come in a single sequence just as they do from CME for example. In other words the two feeds which are now 'independent' entities would come in a single sequence so that synchronization is guaranteed. For sophisticated orderflow analysis one needs to see certain events in the sequence they happened (trades interleaved with bid/ask size/orderbook updates). It is practically impossible to synchronize two independent L1 and L2 feeds even with millisecond timestamps-other than assuming neither of the feeds has any errors/omissions. Is an implementation of this feature conceivable?

aQuant
-Interested User-
Posts: 48
Joined: Jul 20, 2012


Posted: Oct 23, 2019 08:18 PM          Msg. 2 of 12
I requested this 5 years ago... but I understand the separation of L1 and L2 feeds is probably important and convenient organization of the feed data.

However, can we request the messages to contain a new field, message sequence ID, that comes directly from the exchange for both L1 and L2 update messages? This would allow the client to synchronize on their end. And you must be already parsing those from say CME in your data processing anyway. You could just pass them along (as optional field) to the client.
See
https://www.cmegroup.com/confluence/display/EPICSANDBOX/MDP+3.0+FIX+Tag+Library
and tag 83 message field described as:
Tag: RptSeq
FIX Type: Int
Description: MD Entry sequence number per instrument update. Reset weekly.

DTN_Stephen
-DTN Guru-
Posts: 453
Joined: Aug 22, 2014


Posted: Feb 7, 2020 01:21 PM          Msg. 3 of 12
Can you send an email to support@iqfeed.net

Attention: Stephen Shockey with your 6 digit Login ID so that I can research this.

Thank you.


Stephen Shockey
Senior Customer Support Representative and Product Support Specialist

DTN
800-779-7299
stephen.shockey@dtn.com

Edited by DTN_Stephen on Feb 7, 2020 at 01:22 PM

aQuant
-Interested User-
Posts: 48
Joined: Jul 20, 2012


Posted: Feb 7, 2020 02:16 PM          Msg. 4 of 12
Done.

DTN_Stephen
-DTN Guru-
Posts: 453
Joined: Aug 22, 2014


Posted: Feb 7, 2020 03:22 PM          Msg. 5 of 12
Thank you, I have received your email and we are researching your request. I will reach out to you via email by February 12th, 2020.

I appreciate your patience.

Stephen Shockey
Senior Customer Support Representative and Product Support Specialist

DTN
800-779-7299
stephen.shockey@dtn.com

jphiggs
-Interested User-
Posts: 6
Joined: Feb 24, 2019


Posted: Jun 17, 2022 10:36 AM          Msg. 6 of 12
What was the response to this?

DTN_Stephen
-DTN Guru-
Posts: 453
Joined: Aug 22, 2014


Posted: Jun 17, 2022 12:10 PM          Msg. 7 of 12
Unfortunately my response was almost 2 1/2 years ago and without knowing that customers login ID I do not have easy access to the answer that was provided. If you would like to contact us at support@iqfeed.net with you 6 digit IQ Login ID we can begin research on this again.

Please enter in the subject line Attention: Stephen Shockey.

Stephen Shockey
Senior Customer Support Representative and Product Support Specialist

DTN
800-779-7299
support@iqfeed.net

DTN_Gary_Stephen
-DTN Guru-
Posts: 288
Joined: Jul 3, 2019


Posted: Jun 17, 2022 03:04 PM          Msg. 8 of 12
Protocol 6.2, which became the official release version in September 2021, has improvements to the Level 2 messages that should obviate the need for this feature.

First, keep in mind that there are two different kinds of watches: Market By Order or Market By Price Level. Market By Price Level is similar to how a "watch" worked in protocol 6.1; Order Level is a new command that returns information about each actual orders that makes up the price level. Currently this data is only available for CME and ICE futures; other symbols can be watched by Price Level.

Market By Order messages include an "Order Priority" that tells you how to prioritize orders of the same side (buy/sell) and price. Furthermore, Buy and Sell offers are each their own message, as opposed to one message potentially including both (differentiated by the BidInfoValid and AskInfoValid data points). Both Market By Order and Market By Price Level messages include a precise time/date stamp.

Sincerely,
Gary Stephen
DTN IQFeed Implementation Support Specialist

aQuant
-Interested User-
Posts: 48
Joined: Jul 20, 2012


Posted: Jun 17, 2022 08:14 PM          Msg. 9 of 12
Hello,

as I originally requested this (and subsequently inquired) I thought I would add this note.
It's not true that MBO or any existing enhancements in 6.2 will 'obviate' this request that I posted years ago and never got any good response on it. I can provide specific real examples as to why it's impossible to synchronize the two distinct L1 and L2 (MBO or MBP) data feeds in the current approach-even if they all carry precise time stamps to microsecond (which they currently do for CME). I outlined (in my 10/23/2019 post) how this option could be offered relatively easily (with most burden offloaded to the interested developers-however, making it at least theoretically possible to synchronize the two feeds). Even more so confounding that you must already be parsing this field in the process. In summary, any sophisticated analysis that requires the knowledge of trade match events and their relation to order book changes does need this and to be able to do it deterministically and with guaranteed correctness the two feeds must be obtained with sequential IDs (even if on different channels/threads as is currently the case).

DTN_Gary_Stephen
-DTN Guru-
Posts: 288
Joined: Jul 3, 2019


Posted: Jun 24, 2022 10:12 AM          Msg. 10 of 12
You are correct that "obviate" was a bad choice of words on my part. I meant to say that the new features would be helpful, but they don't make it 100% possible to pair up bids and trades. This is still not feasible with L1 and L2 data as it is now.

Beyond that, DTN is currently having a discussion about this topic. Integrating the "message sequence Id" field will have some complexities, and we have to make sure it will accomplish what you expect it to. I'll post more on this thread when I have an update.

Sincerely,
Gary Stephen
DTN IQFeed Implementation Support Specialist

aQuant
-Interested User-
Posts: 48
Joined: Jul 20, 2012


Posted: Jun 24, 2022 04:55 PM          Msg. 11 of 12
Great, I am glad it's being debated at least. Thank you.

jphiggs
-Interested User-
Posts: 6
Joined: Feb 24, 2019


Posted: Jan 29, 2023 12:43 PM          Msg. 12 of 12
Still interested to know what may have come from DTN's discussion about this topic.
 

 

Time: Sat February 4, 2023 10:26 PM CFBB v1.2.0 16 ms.
© AderSoftware 2002-2003