23 replies to this topic

[abumarya]

before was 5 to 10 minutes delay

now 2 to 3 minutes

 

when it will be right

 

thanks

 

[littlesat]

....????

[Erik Slagter]

It will be "right" as soon as the provider that broadcasts the service your receiver starts up with, starts broadcasting the correct time.

Edited by Erik Slagter, 14 May 2017 - 12:03.

[abumarya]

same provider no change

the other images the time is correct

 

thanks

[littlesat]

They get time from internet... You can install the plugin for that on openpli,and you have the same...(systemtime plugin)

Edited by littlesat, 14 May 2017 - 20:43.

[Pr2]

Would be nice to know which box he is using in case it is the time difference bug already mentioned on the forum.

[abumarya]

dm7020hd

[abumarya]

i am not expert (only user )

can you give the plugin and tell me where to add it

[WanWizard]

The systemtime plugin.

[Erik Slagter]

I think it's quite a waste to use ntp while on 99.99% of all transponders the time is correct.

[esgraon]

"Set system time manually" option is available, but changes no time.

The same is with the "Sync Internet" option.

Any idea - what is wrong?

 

DM7020hd, OpenPLi 4.0 (2017-05-20), Kernel / Drivers: 3.2 / 3.2-20161019-r7.0.0

[Dimitrij]

Test, in telnet:

date

date 1230100509

date

[esgraon]

root@dm7020hd:~# date

Wed May 24 16:50:33 CEST 2017

root@dm7020hd:~# date 1230100509

date: invalid date '0912301005'

root@dm7020hd:~# date

Wed May 24 16:50:49 CEST 2017

 

Am I doing something wrong?

[esgraon]

!! After this test I can increase the system time manually !!

No decreasing, no sync with transponder or internet.

Correct transponder sync is after cold restart only, not manually....

[s3n0]

Try to change the date again. But with correct command please .

root@formuler3:~# date -?
date: invalid option -- '?'
BusyBox v1.24.1 (2017-02-28 16:54:30 CET) multi-call binary.

Usage: date [OPTIONS] [+FMT] [TIME]

Display time (using +FMT), or set time

        [-s,--set] TIME Set time to TIME
        -u,--utc        Work in UTC (don't convert to local time)
        -R,--rfc-2822   Output RFC-2822 compliant date string
        -I[SPEC]        Output ISO-8601 compliant date string
                        SPEC='date' (default) for date only,
                        'hours', 'minutes', or 'seconds' for date and
                        time to the indicated precision
        -r,--reference FILE     Display last modification time of FILE
        -d,--date TIME  Display TIME, not 'now'
        -D FMT          Use FMT for -d TIME conversion

Recognized TIME formats:
        hh:mm[:ss]
        [YYYY.]MM.DD-hh:mm[:ss]
        YYYY-MM-DD hh:mm[:ss]
        [[[[[YY]YY]MM]DD]hh]mm[.ss]
        'date TIME' form accepts MMDDhhmm[[YY]YY][.ss] instead

So try to change the date/time again... for example with the command:

date -s "2017-05-25 12:30:00"

Then check the changes with "date" command again:

root@formuler3:~# date

Thu May 25 12:30:02 CEST 2017

Also you may try to testing a command certain for the time synchronization:

 

ntpdate pool.ntp.org

.....or this:

rdate -s time.nist.gov

Edited by s3n0, 25 May 2017 - 14:13.

[esgraon]

Shame on me...   It is so difficult to be a moron...

 

root@dm7020hd:~# date

Thu May 25 15:34:48 CEST 2017

root@dm7020hd:~# date -s "2017-05-25 15:30:00"

Thu May 25 15:30:00 CEST 2017

root@dm7020hd:~# date

Thu May 25 15:35:39 CEST 2017

 

root@dm7020hd:~# date

Thu May 25 15:41:10 CEST 2017

root@dm7020hd:~# date -s "2017-05-25 15:50:00"

Thu May 25 15:50:00 CEST 2017

root@dm7020hd:~# date

Thu May 25 15:50:30 CEST 2017

 

root@dm7020hd:~# date

Thu May 25 15:52:20 CEST 2017

root@dm7020hd:~# date -s "2017-05-25 15:48:00"

Thu May 25 15:48:00 CEST 2017

root@dm7020hd:~# date

Thu May 25 15:53:10 CEST 2017

 

It works, but increasing only....

[s3n0]

.....and what about the command:

ntpdate pool.ntp.org

 

.....or you can try:

rdate -s time.nist.gov

 

It works ? Or nope ? Both commands are used to set the real time according to the internet server. The "rdate" command with the "-s" argument synchronizes the time only when the internet time with the local time in the box does not match.

 

I'm sorry but... I still do not quite understand. What exactly is your problem ?

[Pedro_Newbie]

Set the correct date an time in this format

date -s YYYYMMDDhhmm.ss

So setting the date to 26-05-2017 and the time 08.17.20 use:

date -s 201705260817.20

[esgraon]

@ s3n0

 

>.....and what about the command: ntpdate pool.ntp.org

>.....or you can try: rdate -s time.nist.gov

> It works ? 

 

Yes it works, but only when the current system time value is smaller as the server time value.

 

> What exactly is your problem ?

 

1. Set system time manually don't works when “manually set time value <  "system time value”.

2. Internet sync don't works when “server time value <  system time value”.

3. Transponder sync don't works when “transponder time value <  system time value”.

Edited by esgraon, 26 May 2017 - 07:22.

[s3n0]

Unfortunately, I do not have good experience with Enigma2 systems. It looks like your time is constantly being checked by some service running on the system. I'm just trying to guess - for example: it's possible that the time setting checks for a service that writes LOG (date and time dependent) and therefore protects itself.

Enable if you do not have active debug / crash LOG and try to find the bug in it. Or send a LOG file here to a discussion forum.

Did the SHELL commands do not really work for time synchronization? I think these commands use exclusive hardware access to real time clocks and should not be affected by any running service on the system.

Try updating your OpenPLi. And what about trying to flasch the entire OpenPLi system into the box again? Alternatively, reset the box to factory settings. Do not forget, of course, to back up everything before.

If everything worked on a clean OpenPLi system, the bug is definitely in a plug-in or some service. Then you can still test another system, like OpenATV, that everything will work there. Otherwise it could be a hardware fault!

Why do you need to change local time at all? Sorry, I still do not understand. If everything is okay after the box is restarted, why do you want to change it?