Not weird.
Oscam contains code that disables time changes. If you change it (no matter how), oscam changes it back (irritating, but true). So it is important that the box has the correct time when oscam starts.
OpenPLi 8.1 automatically does an ntp update as soon as the network interface comes up. We start oscam with --wait 60, meaning it will wait for up to 60 seconds for the correct time.
This leaves room for a race condition: say your network (or your dhcp server) is slow, and enigma starts and tunes before ntp has updated the time, then with the default settings, enigma will detect that, and take the time from the transponder. If that time is wrong, you're stuck with that wrong time as soon as oscam starts.
There are a few solutions:
- make sure Enigma starts on a known good transponder so it pickes up the correct time
- set the time sync method to "ntp" instead of "auto", so transponder time is ignored
- fix your slow network (dhcp response)
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
grab2.jpg 124.79KB
3 downloads
