Time 30 minutes ahead on two modded Tivo HD's

[mr.sneezy]

Hi all,

I've modded two Tivo HD's this year, one mine and one for a local friend, and we're in Adelaide. They've both been running for a while now and we've noticed that the clock is 30 minutes fast on both units. I thought it might sort itself out, but it hasn't. So it's like the time zone is +10H UTC instead of +9.5H UTC.
Anyone know where we correct this 30 minute time issue ?
Cheers,
Martin

[Darren King]

Did you set the postcode to the CBD for your state? In your case 5000?

[DavidKeegel]

It is probably because of the postcode you used for Guided Setup on each TiVo. If postcode is between 5100 and 5999 then that would definitely explain the time difference - you should see clock 30 minutes fast and tv guide 30 minutes fast.
If that is it (or you're not sure) then I suggest doing Guided Setup again and make sure you use postcode 5000 (for anywhere in South Australia).

[mr.sneezy]

It is probably because of the postcode you used for Guided Setup on each TiVo. If postcode is between 5100 and 5999 then that would definitely explain the time difference - you should see clock 30 minutes fast and tv guide 30 minutes fast.
If that is it (or you're not sure) then I suggest doing Guided Setup again and make sure you use postcode 5000 (for anywhere in South Australia).

Thanks,
Nope I used my local postcode. I must have missed that bit of info about CBD code.
Can I run guided setup again without prerequisites, or do I need to clear or delete any info or files first ?
Thanks,
Martin

[Darren King]

Yes just run Guided Setup again and use 5000 as your postcode.

[mr.sneezy]

Yes just run Guided Setup again and use 5000 as your postcode.

Yes this sorted it out. Took two goes to get the Guided Setup to properly complete though, it hung the first time after it said complete the first time.

Hey a question.
If devs have access to the code in the right place, why not make the guided setup just use the state level post code digit to set the boxes time zone, instead of all four digits ?
i.e. 5 instead of 5XXX, truncate the uses post code to one digit and add the zeros back if 5000 is needed.

Cheers,
Martin

[edcba]

Yes this sorted it out. Took two goes to get the Guided Setup to properly complete though, it hung the first time after it said complete the first time.

Hey a question.
If devs have access to the code in the right place, why not make the guided setup just use the state level post code digit to set the boxes time zone, instead of all four digits ?
i.e. 5 instead of 5XXX, truncate the uses post code to one digit and add the zeros back if 5000 is needed.

Cheers,
Martin

That won't work. Canberra has different programs from Sydney, but both have postcodes starting with 2.

[DavidKeegel]

If devs have access to the code in the right place, why not make the guided setup just use the state level post code digit to set the boxes time zone, instead of all four digits ?
i.e. 5 instead of 5XXX, truncate the uses post code to one digit and add the zeros back if 5000 is needed.


I have made some changes to the way 5xyz and 6xyz postcodes are translated to time zones (for x>=1) which I think should work better. There are also minor code changes (should have no discernable impact) to 4xyz postcodes and DST handling (ie disabling DST) for 6xyz. And also supporting DST transitions 2018-2022 (previously only transitions up to April 2018 were coded).

Note: I have not made any changes to how guide data works. I don't expect postcodes 5xyz or 6xyz (where xyz!=000) to work any better for guide data (which is a different issue) than they did before. So I still encourage South Australians to use postcode 5000, and West Australians to use postcode 6000, just as everyone else in Australia should use their state/territory capital city postcode (assuming your capital city has the same time that you do) when you do a guided setup, until further notice. Do we have anyone from places like Broken Hill, Eucla, Lord Howe Island (where time is different to the state capital) with a tivo?

[cpab]

G'day David, Darren and All,

Problem came up here in the West. At least in northern Perth suburbs. Ran out of programme data this morning.

Tivos won't connect to the Tivo Service.

Mine was ok yesterday, 'cos I did a few recordings last night, but all "to be announced" this morning.

[Jep]

G'day David, Darren and All,

Problem came up here in the West. At least in northern Perth suburbs. Ran out of programme data this morning.

Tivos won't connect to the Tivo Service.

Mine was ok yesterday, 'cos I did a few recordings last night, but all "to be announced" this morning.

Yes I the same problem on both our Tivos, so might be a Perth thing. Last successful connection on Tuesday after that N18 failed while configuring error.

[Cassba1]

Yes I the same problem on both our Tivos, so might be a Perth thing. Last successful connection on Tuesday after that N18 failed while configuring error.

I also have exactly the same problem also in Perth.

[DavidKeegel]

Yes I the same problem on both our Tivos, so might be a Perth thing. Last successful connection on Tuesday after that N18 failed while configuring error.

I take it from Wednesday onwards the Connect to TiVo Service was not working in Perth (or WA in general), which meant you did not get any new guide data. And after a few days of not connecting successfully, you ran out of guide data, and then you let us know that Connect to TiVo Service stopped working.

I have reverted the DST change stuff I did for WA (postcode 6xxx) on Tuesday.
Does that fix the problem with Connect to TiVo Service? (And thus mean West Australians can get guide data again.)

If it is still broken, it would be good if someone could have a look in /var/log/tclient (or the old version, /var/log/Otclient).
One easy way to view logs like that is TiVo > Messages & Settings > Account & System Information > Backdoors > View Logs.
Use Right (on the direction wheel) about half a dozen times to change logs to tclient.
Then use Up to scroll through the log. Look for PhoneHome and HServer.
It's probably easiest to look at the logs soon after a Connect to TiVo Service fails so the relevant output is near the bottom of the log.

Or use something like winscp (with ssh protocol) to copy /var/log/tclient to a PC and look at it there. Or upload it from there to this forum.

[BrownCow]

Hi peeps - I'm also from Perth (northern suburbs) and both my Tivos ran out of program guide yesterday (Thursday 29/03). Last successful connection for one of them was Monday 26/03 6:08pm.

Anyway after trying unsuccessfully all day to connect (kept getting configuration error N18), it looks like its now back working again. :) Its been at the Loading Info stage for more than 30 mins and is at about 15%.

Just prior to it starting working again, I connected to the Tivo using WinSCP and uploaded the tclient file to my laptop so I could send it your way as requested. Not sure if you need it now in any case but when I tried attaching it to this post using the File Upload Manager, the following error dialog appeared:
"From forum: oztivo.net
The following errors occurred:
tclient: Invalid File"
Let me know if you still want to have a look at the tclient file and I'll send it your way via email or some other means.

[cpab]

Good morning Mister Sunshine..... Good on yer David......Don't do it again. Lol

But really we thank you very much.

It's a reminder to us all that someone cares and is working on the development and improvement of the OzTivo Service.

I just checked and saw these latest posts,,,, turned on the TV and voila, programme data is back.

Thankyou again David Keegel.

[DavidKeegel]

Sorry I messed up getting guide data in WA from Tuesday to Friday.
Thanks for not yelling at me.

If you have a TiVo in WA and don't have programme guide information yet, please do Messages & Settings > Settings > Network > Connect to TiVo Service to trigger a connection now, if your TiVo hasn't connected since 8:20pm AWST on Good Friday and you don't want to wait for the automatic connection every 25 hours or so. (So everyone's TiVo should have connected successfully by 10pm AWST tonight at the latest, even if you don't trigger a connection.)

I have a log file to study (to work out hopefully why the WA part of my change didn't work), but I'm in no rush to change this again. If I do change it (later), I will test it with postcode 6000 on a different dial code first before I put it in the standard S3 dial code 140. (I had tested this change earlier on a different dial code, but not with a WA postcode.)