[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Server Time Change



PureBytes Links

Trading Reference Links

I tried these steps & they seemed to work yesterday (or so I thought). Today
I had a whole host of problems. I tried calling Omega but the minimum wait
was nearly a half-hour. So, I hope someone has a clue what I did or didn't
do right.

On my all-sessions charts (eg, ES & SP form BMI) the last bar seems to
contain all the previous bars' information; i.e., it remains "stuck", w/ the
H of the bar somewhere above the day's action and the Current price moving
up & down the bar. No new bars are created. Also, everytime there's a tick
the screen blanks out for a split second before restoring itself (even if
the price doesn't change).

If I change the time frame for a given chart (say, from 5min to 1min) the
problem resolves itself for the duration of the next bar (eg, 1min), then
it's back to the same problem mentioned above.

On my SP (Globex) this morning's opening tick went to the stratosphere & the
bar stayed stuck at the level of that tick (not the actual opening tick,
just some bizarre reading like 1380). Only when I switched timeframes back
and forth did it behave normally again.

Any tick-based ES chart thinks it's Oct 27 when I performed the steps Bob
suggetsed before this morning's open.

Actually, there are so many other weird anomolies I'll refrain from trying
to list them. Yesterday everything seemed normal before I made the change.
The opening tick was correct & so was the time. After I made the changes (to
all exchanges) I couldn't tell the difference but assumed it would've
effected the daily Close time. It wasn't until this morning's Open that
everything went haywire.

This shouldn't be that hard. I've managed to cope with everything from new
holidays to new contracts to splitting the spoo over the last several years.
For some reason this has me stymied. Help!

Michael

Bob Fulks wrote:

> There were other problems with the method I posted previously so this
> reflects what I now understand to be the recommended process in
> detail.