8 replies to this topic

[anas03]

hi

how i can set the time there is a difference of more than 60 min

and every day it increases by a minute

[WanWizard]

Normally the box gets its time from the transponder the box starts up with, and then updates it when you zap, but only if the delta isn't to box.

 

So the key is to make sure your box starts up on a channel on a good transponder ( in the channel list, select the channel, press the menu button, and select "set as startup channel" ). When done, put the box into deep standby, switch it off (or pull the plug if it doesn't have a switch), and go get a cup of coffee while you want to the capacitors of the power supply to empty fully so the internal clock stops. Then switch it back on again.

 

If you can't find any good transponder (happens in some parts of the world), and your box has internet access, you can install the system time plugin, and use internet time instead of transponder time.

[anas03]

yes it works, but when i disable but when i delete startup channel, I come back to the same problem

so i decided to install system time for an ntp

thanks

[WanWizard]

So why should you delete a startup channel?

[anas03]

only I don't want to fall on the same channel every time when I turn on the receiver

[littlesat]

Is you box connected to the www.... then install systemtime plugin.

[anas03]

I noticed a problem with the plugin systemtime

when I put the receiver in deep standby

the receiver start up by itself after a few seconds

[ccs]

....sounds more like a reboot.

[WanWizard]

If it is a crash, there must be a crash log in /media/hdd.

 

The systemtime plugin doesn't do anything more than add a cron job that runs ntpdate once an hour.