|
PureBytes Links
Trading Reference Links
|
I would like to try to find the cause of the "10/27" date problem on the BMI
feed. The cause could be either the TS4 program or the BMI datafeed. I am
in the process of writing a program which will alert the user in real time
if a bad BMI date/time stamp occurs. So, if a bad data stamp is received
and the user was running this program at least the problem could be isolated
to either TS4 or the BMI datafeed. The program obtains the datafeed
information from the serial feed and therefore requires a splitter or
equivalent. Attached is a GIF of the initial program in operation - note
that the datafeed time compares very favorably with my atomic clock
synchronized PC time. Also, note that the BMI datafeed contains two
"markers", a 30 second maker which contains month, day, hours, minutes and
seconds and a 5 minute marker which additionally contains year and day of
the week information.
If there is any interest, please let me know.
~Bob
-----Original Message-----
From: Carroll Slemaker <cslemaker1@xxxxxxxx>
To: omega-list@xxxxxxxxxx <omega-list@xxxxxxxxxx>
Date: Friday, July 13, 2001 11:15 AM
Subject: Bad Date Stamps !!!
>I have been a subscriber, first to Signal, then (and now) to BMI, for many
>years and prior to about a month ago had had only one occasion of receiving
>a bad time/date stamp on incoming data. But in the last month (or less) I
>have had THREE, the most recent occurring at 07:43 am (NY time) this
>morning. On each occasion the date is received as 10/27/2001.
>
>I know that others on this list have experienced this 10/27/2001 problem,
>but some apparently have NOT!
>
>What I would like to ask is:
>
>Have any of you experienced a recent increase in such experiences?
>
>Have any of you researched the matter and determined the cause?
>
>Thanks for any light you can shed on this annoying problem.
>
>Regards,
>Carroll Slemaker
>
>
Attachment:
Description: "BMI Time Monitor.gif"
|