HDD Thomson DTR6000AU Clock Erratic

[tifino]

Been missing some recordings over the last week. Noticed that my clock intermittently jumps back several hours. Sometimes jumps back 24hours.
For example if I checked my EPG for a display of my current time at 28/12/2003 02:07, the displayed time could either be correct, or showing 28/12/2003 01:47, or could be 27/12/2003 02:07.
If I correct the error, it sometimes keeps the correct time, or maybe immediately jumps out wrong again.

Also whilst inputting new recording sessions the resultant session reported shows a recording date shifted by 24 hours.
For example if I now inputted a rec programme for 30/12/2003 at 13:33, the resultant displays shows I will get a recording happening at 29/12/2003 at 13:00.

I am conversant with the auto/manual settings of this model, so I have already disregarded the notion of 'finger-trouble'

The erratic nature is playing havoc. But wait!! there's more....

With the new year almost here, some of my upcoming recording sessions i.e of the weekly nature already mean the need to input recording dates for 01/01, 02/01 etc. My machine reports these inputs as invalid dates. To circumvent this in the interim, I have to resort to inputting upcoming sessions on a 'daily' recording basis, hopefully only until jan04 is with us.

Anybody else having this sort of trouble???

[tony_h]

"tifino" <tifino.z3qnx@no-mx.forums.eyo.com.au> wrote in message
news:tifino.z3qnx@no-mx.forums.eyo.com.au...
>
> Been missing some recordings over the last week. Noticed that my clock
> intermittently jumps back several hours. Sometimes jumps back 24hours.

Sounds like one of the TV stations has their clocks wrong. Is there any way
of stopping your STB from getting the time from the TV broadcasts until the
broadcasters get their act together and send the right time?

I had the same prob in Sydney with my Topfield 5000PVRt and channel 10 was
20mins behind. I missed the 1st 20mins of 2 recordings I setup. Luckily
10 is now accurate (actually 3 of the 5 broadcasters are 2mins behind, but I
can live with 2mins).

Cheers

[John McGhie]

I have just replaced my DTR6000AU for the second time in six weeks after yet another complete failure. They seem to overheat, and the software is by no means finished.

I confirm that I too am unable to enter the 2nd of January as a record date, and am also get weird clock problems. I have put my clock onto "Manual" because the Auto Mode seems determined to set it to "Yesterday".

I think we may have a "Year 2004 problem" with this box.

Cheers

Been missing some recordings over the last week. Noticed that my clock intermittently jumps back several hours. Sometimes jumps back 24hours.
For example if I checked my EPG for a display of my current time at 28/12/2003 02:07, the displayed time could either be correct, or showing 28/12/2003 01:47, or could be 27/12/2003 02:07.
If I correct the error, it sometimes keeps the correct time, or maybe immediately jumps out wrong again.

Also whilst inputting new recording sessions the resultant session reported shows a recording date shifted by 24 hours.
For example if I now inputted a rec programme for 30/12/2003 at 13:33, the resultant displays shows I will get a recording happening at 29/12/2003 at 13:00.

I am conversant with the auto/manual settings of this model, so I have already disregarded the notion of 'finger-trouble'

The erratic nature is playing havoc. But wait!! there's more....

With the new year almost here, some of my upcoming recording sessions i.e of the weekly nature already mean the need to input recording dates for 01/01, 02/01 etc. My machine reports these inputs as invalid dates. To circumvent this in the interim, I have to resort to inputting upcoming sessions on a 'daily' recording basis, hopefully only until jan04 is with us.

Anybody else having this sort of trouble???

[tony_h]

"John McGhie" <John.McGhie.z8kak@no-mx.forums.eyo.com.au> wrote in message
news:John.McGhie.z8kak@no-mx.forums.eyo.com.au...
>
> I have just replaced my DTR6000AU for the second time in six weeks after
> yet another complete failure. They seem to overheat, and the software
> is by no means finished.

Yuk... although software and complete box failure don't quite go hand in
hand.

> I confirm that I too am unable to enter the 2nd of January as a record
> date, and am also get weird clock problems. I have put my clock onto
> "Manual" because the Auto Mode seems determined to set it to
> "Yesterday".

But do you have to set a 10 (or 11 now) hour offset to GMT? GMT will
certainly be "yesterday" at some times of our day.
I don't know what options your box has, my experience is only from the
Topfield 5000PVRt Auto mode.

Cheers
Tony

[Bernd Felsche]

"tony_h" <tony_h@REMOVE.bigpond.net.au> writes:

>"John McGhie" <John.McGhie.z8kak@no-mx.forums.eyo.com.au> wrote in message
>news:John.McGhie.z8kak@no-mx.forums.eyo.com.au...
>>
>> I have just replaced my DTR6000AU for the second time in six weeks after
>> yet another complete failure. They seem to overheat, and the software
>> is by no means finished.

>Yuk... although software and complete box failure don't quite go hand in
>hand.

The mistake is to place the small box in a small cavity. It really
does need those 10cm at the top and 4 cm at both sides; or
equivalent forced convection.

I've grown tired of my parents cooking their expensive TV, VCR's and
DVD in a tight cabinet and installed a small, usually-quiet,
temperature-sensitive fan at the back to circulate air from around
the TV and blowing past the other goodies. It makes a difference of
about 10 degrees C at the back of the shelf.

>> I confirm that I too am unable to enter the 2nd of January as a record
>> date, and am also get weird clock problems. I have put my clock onto

Any date in a month less than the current one is a problem. I found
yesterday that programming for 31/12 wasn't working either. Although
it said it updated the timer, the date appeared to revert to 30/12
when listing the timer events.

>> "Manual" because the Auto Mode seems determined to set it to
>> "Yesterday".

Hmmm... not found where i could choose between time sources.

>But do you have to set a 10 (or 11 now) hour offset to GMT? GMT will
>certainly be "yesterday" at some times of our day.

Or even "last year" :-)

The offset has to be set. IMO; should be a proper timezone setting.

>I don't know what options your box has, my experience is only from the
>Topfield 5000PVRt Auto mode.
--
/"\ Bernd Felsche - Innovative Reckoning, Perth, Western Australia
\ / ASCII ribbon campaign | I'm a .signature virus!
X against HTML mail | Copy me into your ~/.signature
/ \ and postings | to help me spread!

[tifino]

"tifino" <tifino.z3qnx@no-mx.forums.eyo.com.au> wrote in message
news:tifino.z3qnx@no-mx.forums.eyo.com.au...
>
> Been missing some recordings over the last week. Noticed that my clock
> intermittently jumps back several hours. Sometimes jumps back 24hours.

Sounds like one of the TV stations has their clocks wrong. Is there any way
of stopping your STB from getting the time from the TV broadcasts until the
broadcasters get their act together and send the right time?



I had the same prob in Sydney with my Topfield 5000PVRt and channel 10 was
20mins behind. I missed the 1st 20mins of 2 recordings I setup. Luckily
10 is now accurate (actually 3 of the 5 broadcasters are 2mins behind, but I
can live with 2mins).


Cheers

from tifino. To stop the over air clock I can set the thomson clock to 'Manual', which results in a displayed time that is offset by the sonamed 'offset'. This gives the correct time as whatever you input as such. If you try to input the time to display correctly you bring the 'offset' to 0:00:00, however that will upset future recordings by, as in my time zone, a magnitude error of 11 hours. Scratch that idea, so go back to 'Auto'.
In Auto, I of course can force the clock to any time and date. But, because it is in 'auto' again, the station clock updates mine, but in my case the clock will then show a date time with the original error. In my case, at this time it is 1jan03 at 18:33, but my thomson is again displying 31dec03 at 18:33.

This error in 'auto' is identical no matter what carrier in being rcvd. tifino.

[tifino]

"John McGhie" <John.McGhie.z8kak@no-mx.forums.eyo.com.au> wrote in message
news:John.McGhie.z8kak@no-mx.forums.eyo.com.au...
>
> I have just replaced my DTR6000AU for the second time in six weeks after
> yet another complete failure. They seem to overheat, and the software
> is by no means finished.

Yuk... although software and complete box failure don't quite go hand in
hand.

> I confirm that I too am unable to enter the 2nd of January as a record
> date, and am also get weird clock problems. I have put my clock onto
> "Manual" because the Auto Mode seems determined to set it to
> "Yesterday".

But do you have to set a 10 (or 11 now) hour offset to GMT? GMT will
certainly be "yesterday" at some times of our day.
I don't know what options your box has, my experience is only from the
Topfield 5000PVRt Auto mode.

Cheers
Tony

from tifino. I find to change my 'offset' away from my timezone of GMT+11hrs, will upset the timer recording. You'll be able to disp[lay a correct time, but the recording will be in error by 11hrs.

the 2004 problem. Over the last week, including today I am still unable to input any time recording for 01/01, 02/01. Today is a notable example. Today is 1jan04. oh yea hip hooray. My thomson of course thinks it is still 31jan03. Now theoretically, if I follow my established practice of inputting future recordings, including my extra 1 day offset due to 'auto', I would have to input 1jan04 as the date for my recording today. This is because the resultant timer recording would be reported to occur on 31jan03, which is the date on my Thomson today. There are problems with this. Firstly I cant input any jan04 date anyway because of the obscure problem with jan04 dates. But secondly, If I were to change todays timedate to be 1 jan04, I have to input 2jan04, but it still doesnt solve the timer problem because I still am unable to input 2jan04 due to it being in the jan04 category.
DrWho today is my example for todays rec session. I simply pressed the record button. What will tomorrow be like.......

[tifino]

"tony_h" <tony_h@REMOVE.bigpond.net.au> writes:

>"John McGhie" <John.McGhie.z8kak@no-mx.forums.eyo.com.au> wrote in message
>news:John.McGhie.z8kak@no-mx.forums.eyo.com.au...
>>
>> I have just replaced my DTR6000AU for the second time in six weeks after
>> yet another complete failure. They seem to overheat, and the software
>> is by no means finished.

>Yuk... although software and complete box failure don't quite go hand in
>hand.

The mistake is to place the small box in a small cavity. It really
does need those 10cm at the top and 4 cm at both sides; or
equivalent forced convection.

I've grown tired of my parents cooking their expensive TV, VCR's and
DVD in a tight cabinet and installed a small, usually-quiet,
temperature-sensitive fan at the back to circulate air from around
the TV and blowing past the other goodies. It makes a difference of
about 10 degrees C at the back of the shelf.

>> I confirm that I too am unable to enter the 2nd of January as a record
>> date, and am also get weird clock problems. I have put my clock onto

Any date in a month less than the current one is a problem. I found
yesterday that programming for 31/12 wasn't working either. Although
it said it updated the timer, the date appeared to revert to 30/12
when listing the timer events.

>> "Manual" because the Auto Mode seems determined to set it to
>> "Yesterday".

Hmmm... not found where i could choose between time sources.

>But do you have to set a 10 (or 11 now) hour offset to GMT? GMT will
>certainly be "yesterday" at some times of our day.

Or even "last year" :-)

The offset has to be set. IMO; should be a proper timezone setting.

>I don't know what options your box has, my experience is only from the
>Topfield 5000PVRt Auto mode.
--
/"\ Bernd Felsche - Innovative Reckoning, Perth, Western Australia
\ / ASCII ribbon campaign | I'm a .signature virus!
X against HTML mail | Copy me into your ~/.signature
/ \ and postings | to help me spread!

from tifino. My Thomson can be stone cold but still have the same charactristics.

Yep the clock always falls by back one day after you have set it. In 'auto' at least the time will be correctif your appropriate timezone is inputted. You have to input the extra hour if you are in a state that has to suffer daylight saving.

Yep the same thing happens when inputting timer recordings. The resultant timer will be behin by one day. If you had wanted a timer rec for 20dec, then inputting 21dec will record the programme that will be transmitted on 20dec.

pity the same thing aint happening this jan04. its manual press record button for me if the prob cant be worked out.