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

Re: TS2000i charts starting times have shifted one hour



PureBytes Links

Trading Reference Links

John,

The file/Desktop offset from GMT only changes the clock in the chart
window.  Useless for anything in Tradestation.

In the GS edit a symbol then click the the sessions tab and see what
Display Session Times in says.  Should be Local Time.  Now check your
Windows clock.  Is it set correctly?  Maybe you flipped over to
Mountain time somehow.  If so change any session times back to what
they were before if the Windows clock is wrong.

Was your computer off?  Is the motherboard battery dead?

Jimmy

Sunday, October 24, 2004, 5:55:54 PM, you wrote:

j> Normally, most of my TS2000i charts start at 6:30am PST, and
j> end at 1:00pm or 1:15pm(E-mini) PST.
j> Today I just noticed that all charts were starting at 7:30am,
j> ending at 2:00pm.  Even my USZ4 bonds
j> charts are now starting at 7:30am.  Looking in the Global
j> Server/Edit Symbol/Sessions shows that the
j> starting times have all changed to 7:30am, the end times to 14:00.

j> In File/Desktop Options the datafeed is set to Hyperserver, and
j> the "offset from datafeed time" is 0
j> (and I don't remember if it was set differently, but on my 2nd
j> computer it's also set at 0). I also
j> noticed in the Global Server that the "time to start
j> maintenance" has changed to 1:00am local time(I
j> usually have this set to 4 or 5am).

j> I reset the Sessions times for one symbol to 6:30am and 1pm. 
j> This started the chart at 6:30 but
j> there was a gap with no bars from 6:30 to 7:30am.  Changing the
j> "offset from datafeed time" to -60
j> or +60 doesn't seem to change anything.

j> I'm using DTN IQFeed and Hyperserver Lite, and I'm on the West
j> Coast.  I've figured this type of
j> problem many times with TS4, but I'm not sure what to do with
j> TS2000i.  Would someone point me in
j> the right direction?


j> John



-- 
Best regards,
 Jimmy                            mailto:jhsnowden@xxxxxxxxxxxxx