116 replies to this topic

[Rob van der Does]

I have my ET8k setup as a 'slave box', using automated import of services & EPG from the master box (DUO2) after reboot/E2-restart. Directly after booting up there is no EPG, but when I do the import manually (via the extension menu) all is fine. As the box always goes to 'deep sleep' this is very unhandy

 

What could be wrong in my setup?

[Pr2]

Do you wait long enough to have the epg fully reloaded into memory?

Do you have a local storage attached to your ET8K to have epg.dat written to?

[Rob van der Does]

Yes to both questions.

1- Nothing gets loaded, no matter how long I wait. Doing the manual import works instantly.

2- The box has an USB-stick attached as HDD-replacement.

[ims]

2- The box has an USB-stick attached as HDD-replacement.

I have suspicious, that USB stick is not ideal for it... I had same problem on Osninoplus, where I have microSD in adapter "as HDD" only.

It is long time, when I saw this problem...  from this time i am using import when box goes from standby only...

 

I forgot details ... I think, there is imported epg from server, then is saved to usb/disk as "epg.loading" and then this file is renamed to epg.dat and readed to epg cache. I think, that stick is slow for save imported epg and then is readed empty file...

 

 

Edited by ims, 26 August 2018 - 18:17.

[Rob van der Does]

The epg-data of the slave box is neatly saved as epg.dat on the local USB-stick.

It's the import from the epg.dat data from the server box that does only work when doing the import manually (not when set to do so after boot/E2-start).

 

IMHO if the stick would be too slow, the manual import wouldn't work either?

[ims]

As I wrote, it is long time ... but if you will see what happens, one time you will see epg.dat, then epg.loading and then again epg.dat

Standby/wake-up ... system is stable in this time

Edited by ims, 27 August 2018 - 07:20.

[Rob van der Does]

So in fact you say that it's not a good idea to set it to automated import after reboot?

Or should there a delay be built in the logic, to await system to be ready?

[ims]

I did not investigate it more ...  may be - more delay. May be, faster storage ? Try it with usb hdd, if it will be better...

[twol]

Rob, I know I am comparing Apples with Pears, but I just reflashed my oldish ET7500 this morning (with Vix - yes, I know!) which uses the ViX C/S mode and both Bouquets and EPG are upto date - neither Crossepg or epgimporter are active and the only add on to the box is an old usb stick.
So I am guessing there is an issue in how OpenPli handle the transfer.

Edited by twol, 27 August 2018 - 17:36.

[ims]

As I saw now, on H7S with internal hdd is epg after restart ok. On osninoplus with microSD (fat32 + ext3) is after restart problem.

 

@twol ... on vix it works well, PLi it has wrong ?

[twol]

As I saw now, on H7S with internal hdd is epg after restart ok. On osninoplus with microSD (fat32 + ext3) is after restart problem.

@twol ... on vix it works well, PLi it has wrong ?

Different code - nobody is wrong, just saying that a similar solution does work in a different image.... so maybe a timing issue?
Never looked at either ViX or Pli code for this area,so cannot comment further.... just knw that at one point fallback code was similar before later developments

Edited by twol, 27 August 2018 - 18:47.

[littlesat]

Did you enable the download after e2 restart?

[Rob van der Does]

 

As I saw now, on H7S with internal hdd is epg after restart ok. On osninoplus with microSD (fat32 + ext3) is after restart problem.

@twol ... on vix it works well, PLi it has wrong ?

Different code - nobody is wrong, just saying that a similar solution does work in a different image.... so maybe a timing issue?
Never looked at either ViX or Pli code for this area,so cannot comment further.... just knw that at one point fallback code was similar before later developments

 

I now installed ViX on the ET8k and automated import (after reboot) does work fine, using the same USB-stick.

[ims]

Pli epg import works after reboot fine too. Only restart gui failed, as I saw yesterday.

[Rob van der Does]

Back on PLi for a new test: I have no idea why, but I can't reproduce the problem any more.....

[littlesat]

I'm thinking about some kind of 'race'....

 

After a reboot E2 creates an epg.dat on that (slow) USB stick or SD... after the restart the box reads this epg.dat from the USB stick or SD card and then also a new epg.dat is downloaded from the server box (in a different thread)... that overwrites the epg.dat that currently is read which might lead to weird things... 

 

I think when we enable this import we should unsure not read the epg.dat at the startup of e2.

Edited by littlesat, 28 August 2018 - 08:39.

[Rob van der Does]

Indeed: when automated import is enabled there is no need to read the local (saved) data.

[littlesat]

At least the read of this data at start of E2 should be disabled.... But I cannot find at this moment where this is done...

[Pr2]

In EPGimport I think.

[littlesat]

Nope... somewhere in E2 (cpp I think) where the epg.dat file is read...