173 replies to this topic

[Erik Slagter]

BTW in a previous, very similar discussion, I already suggested the ultimate correct solution: add a RTC clock. We've been googling and it appears it just doesn't exists in a simple form that can be plugged into USB. I am quite sure I am could make something like this for $2 (using an ATtiny as USB to I2C gateway + a RTC chip), I am just not willing to spend the time on it. But who knows if some entrepeneur is interested.

[littlesat]

Doesn’t ntpd do a single shit with the -q option?

[SpaceRat]

Calling it bullshit does not detract from the problem.

Which problem?

[littlesat]

Doesn’t ntpd do a single shit with the -q option?

[SpaceRat]

Doesn’t ntpd do a single shit with the -q option?

A single shit and shot

-q no quit Set the time and quit
- prohibits these options:
saveconfigquit
wait-sync

[Erik Slagter]

This behavior mimics that of the ntpdate program,

Also the manual says the ntpdate program will be replaced "soon" and I know it has been mentioning this for at least 10 years

 

@Littlesat: you mentioned "-p" not "-q". "Path to the PID file".

Edited by Erik Slagter, 27 December 2017 - 18:41.

[Dimitrij]

BTW in a previous, very similar discussion, I already suggested the ultimate correct solution: add a RTC clock. We've been googling and it appears it just doesn't exists in a simple form that can be plugged into USB. I am quite sure I am could make something like this for $2 (using an ATtiny as USB to I2C gateway + a RTC chip), I am just not willing to spend the time on it. But who knows if some entrepeneur is interested.

https://www.keylok.c...real-time-clock

[littlesat]

I had to mention -qp but I mentioned -p only... ntpd is standard in the image, ntpdate not...

[Erik Slagter]

BTW in a previous, very similar discussion, I already suggested the ultimate correct solution: add a RTC clock. We've been googling and it appears it just doesn't exists in a simple form that can be plugged into USB. I am quite sure I am could make something like this for $2 (using an ATtiny as USB to I2C gateway + a RTC chip), I am just not willing to spend the time on it. But who knows if some entrepeneur is interested.

https://www.keylok.c...real-time-clock

Yes, that one, but it's expensive, which can't really be explained.

[Erik Slagter]

I had to mention -qp but I mentioned -p only... ntpd is standard in the image, ntpdate not...

We can fix that easily. As mentioned ntpdate is either a very simple replacement of ntpd, or it's a shell script that calls ntpd with -q

[MiLo]

BTW in a previous, very similar discussion, I already suggested the ultimate correct solution: add a RTC clock. We've been googling and it appears it just doesn't exists in a simple form that can be plugged into USB.

You could get an I2C RTC chip, with integrated battery, and connect it to any I2C inside the box (tuner slot?). That'd be more cost effective, but not very generic...

[mrvica]

for the good old dbox2 there was a RTC kit
https://www.dbox2.co...-interface.html
https://wiki.neutrin...2:RealTimeClock

Edited by mrvica, 28 December 2017 - 13:40.

[Abu Baniaz]

What is the command to sync time please?The following are not working for me.

 

root@vusolo4k:~# date
Thu Dec 28 23:17:52 GMT 2017
root@vusolo4k:~# ntpd -qp pool.ntp.org
root@vusolo4k:~# date
Thu Dec 28 23:17:58 GMT 2017
root@vusolo4k:~# ntpdate -s -u pool.ntp.org
root@vusolo4k:~# date
Thu Dec 28 23:18:26 GMT 2017
root@vusolo4k:~#

[WanWizard]

if that means your clock is currently off (by more than 120s), none of them will work. That is the main issue of this entire thread.

 

You might have more luck by stopping Enigma first using "init 4". 

[Abu Baniaz]

Thanks for suggestion. No joy with an init 4 either. So would be grateful for any other suggestions

[mrvica]

the same here, for a moment it looks good, something sets time back

root@inihde:/var/volatile/tmp# date
Thu Dec 28 17:36:53 CET 2017
root@inihde:/var/volatile/tmp# date -D %s -d $(($(date +%s) + 7200))
Thu Dec 28 19:36:58 CET 2017
root@inihde:/var/volatile/tmp# date
Thu Dec 28 17:37:03 CET 2017

root@inihde:/var/volatile/tmp# init 4

root@inihde:/var/volatile/tmp# date
Thu Dec 28 17:37:21 CET 2017
root@inihde:/var/volatile/tmp# date -D %s -d $(($(date +%s) + 120))
Thu Dec 28 17:39:36 CET 2017
root@inihde:/var/volatile/tmp# date
Thu Dec 28 17:37:41 CET 2017
root@inihde:/var/volatile/tmp#

[mattiL]

A poweroff for a few minutes solved it for me, after that time was set correctly.

[WanWizard]

If "init 4" doesn't work, than means it is not code in Enigma that refuses the clock change. Interesting...

[Erik Slagter]

 

BTW in a previous, very similar discussion, I already suggested the ultimate correct solution: add a RTC clock. We've been googling and it appears it just doesn't exists in a simple form that can be plugged into USB.

You could get an I2C RTC chip, with integrated battery, and connect it to any I2C inside the box (tuner slot?). That'd be more cost effective, but not very generic...

That would cost you about $ 0.20 but it has a few drawbacks:
- most of them are SOIC or smaller
- how are you going to adress them from user space, if the driver do not share the bus with user space (kernel i2c subsystem)

- possible address conflicts with tuners or other native hardware

So I still think USB is the way to go.

[Erik Slagter]

If "init 4" doesn't work, than means it is not code in Enigma that refuses the clock change. Interesting...

If you're using ntp instead of ntpdate, ntp will not adjust the clock immediately but it will gradually adjust it, over a large timespan. That's not what you want in this case.