Uplink Activity 6/13/08 1:35 PM EDT - First Sports moves at 61.5

[JohnH]

Using the new HDSKD channels uplinked this week:

UPLINK ACTIVITY: SAMPLE TAKEN 06-13-2008 13:37:00 TO 06-13-2008 13:38:03 ET


2 MOVE(S) (May include other changes as well.)

MOVE 5429 CSNCH MPEG4 HD Tp 30 EchoStar 3 61.5w SPORT? HIDE HD MAP 429
TO 5429 CSNCH MPEG4 HD Tp 20 EchoStar 3 61.5w SPORT? HIDE HD MAP 429

MOVE 5431 STO MPEG4 HD Tp 30 EchoStar 3 61.5w SPORT? HIDE HD MAP 431
TO 5431 STO MPEG4 HD Tp 20 EchoStar 3 61.5w SPORT? HIDE HD MAP 431

2 CHANGE(S) 5061 CHANNELS IN THE SYSTEM

 

[Smith P.]

And the changes happened at 10:45am PDT.

 

[kstuart]

JohnH -

Do you know how often and when the EPG data is changed/updated ?

 

[JohnH]

JohnH -

Do you know how often and when the EPG data is changed/updated ?

No. Sports and some others are done manually, when needed.

BTW: Somebody's clock is off by 10 minutes.

 

[kstuart]

No. Sports and some others are done manually, when needed.

So, there is no regular daily EPG update at a specific time (similar to the way software is usually updated at midnight Mountain Time) ??

 

[JohnH]

So, there is no regular daily EPG update at a specific time (similar to the way software is usually updated at midnight Mountain Time) ??

There may be some regular scheduled time, but I do not track such things.

 

[Smith P.]

Could be done if you know well how convert big-endian WORD to DEC.

 

[kstuart]

There may be some regular scheduled time, but I do not track such things.

It would be helpful to know when, in terms of when to schedule Update Reboot (i.e. Menu-8-4).

 

[Smith P.]

Oh, that one !

As I told at other site (perhaps here too) the "Update" time have nothing common with EPG/EEPG.
It's just bad fix for memory leaks, system tables corruption, etc - Linux itself pretty stable OS, but in the interpretation with a lot bugs, they made simple solution - no troubleshooting, no fixes, but just one reboot per day.

 

[kstuart]

Oh, that one !

As I told at other site (perhaps here too) the "Update" time have nothing common with EPG/EEPG.
It's just bad fix for memory leaks, system tables corruption, etc - Linux itself pretty stable OS, but in the interpretation with a lot bugs, they made simple solution - no troubleshooting, no fixes, but just one reboot per day.

That is "why", but regardless, the Menu-8-4 setting is when the individual subscriber gets a daily update of the EPG data.

One doesn't want to set the time for one hour before the actual EPG data stream receives its daily update.

 

[Smith P.]

OK, let me dig into that.

One second - what exactly EPG you're concern ? EEPG - 7..9 days or EPG 48 hrs ?

EDIT. Just realize - each time you force to update EPG, that screen telling about 5 min or so.
So, one round should take little less then 5 min;
oh, they spooling EEPG pretty fast - 4 mbps or 750 MB in 25 min.

 

[Smith P.]

I got some info for you:
- captured changing version of EEPG ( didn't test if data changed too, but most likely because of changes in SDT just before that): 3:27am and 5:10am ( SDT version changed 3:10am and 5am same night - time is PDT);
- the EEPG stream occupying 4 Mbps;
- each round of spooling same version of EEPG take ~5 min;
- size of EEPG tables in one round is ~130 MB ( for ALL sats);
- EEPG data sending for sat in orders: ... 119 -> 61.5 -> 110 -> 148 -> 129 -> 105 -> 121 -> 118 -> 77 -> 72.7 -> 119 ...
- number of tables per sat in order above: ~30000, ~26000, ~90000, ...

I'll watch the changes for some time, but seems to me new version of EEPG tied to changing version of SDT. Practically each 4 hours.
As to check changes data inside of EEPG, this analysis will take more time.

 

[Smith P.]

Updates in a post above.

 

[kstuart]

So, if you "get new Guide data" at 5:15 am PDT, that gets you the 5:10 am EEPG update, or am I missing another factor ? Is it 5:35 am if I want 129 (5x5minutes) ??

And thanks for checking this !

 

[Smith P.]

As I saw, first changed SDT ( channels ), then EEPG version. I would try to run both to see the relation.

 

[Smith P.]

UPDATE.

Changes in EEPG stream:

3:26:30am: Begin build new EEPG Ver:17
3:30:55am: All sections (171063/129291454) of EEPG Ver 17 collected.

5:00:05am: Begin build new EEPG Ver:18
5:04:30am: All sections (171063/129185676) of EEPG Ver 18 collected.

11:00:06am: Begin build new EEPG Ver:19
11:04:31am: All sections (171063/129255752) of EEPG Ver 19 collected
[SDT not changed this time]

Missed 5pm window, but did catch the new version:
~5pm: All sections (171063/130070373) of EEPG Ver 20 collected

11:00:07pm: Begin build new EEPG Ver:21
11:04:34pm: DVBMonitor: All sections (171063/130243849) of EEPG Ver 21 collected
[SDT not changed this time]

3:27:51am: Begin build new EEPG Ver:22
3:32:18am: All sections (171063/130243849) of EEPG Ver 22 collected

5:00:08am: Begin build new EEPG Ver:23
5:04:35am: All sections (171063/130323041) of EEPG Ver 23 collected

7:28:00am: Begin build new EEPG Ver:24
7:32:27am: All sections (171063/130323124) of EEPG Ver 24 collected

The numbers above represents a number of EEPG sections and total lenght of the sections.

Based on the short observations, I would conlude - EEPG updating by same period as channel's list [SDT] each 4 hours or more often by other reason.
Follow the info it would be safe to tell: internal guide in each DVR updating in same manner and do not require total reboot as I'm objected before.

ADD. Some info to compare timing:

New NIT v23 total: 381. [03:10:08 06/15/08]

All sections (491/266916) of SDT Ver 20 collected
SDT total: 5061. [03:10:45 06/15/08]


All sections (491/266916) of SDT Ver 21 collected
SDT total: 5061. [05:00:45 06/15/08]

 

[kstuart]

Follow the info it would be safe to tell: internal guide in each DVR updating in same manner and do not require total reboot as I'm objected before.

The Guide info in the DVR is contained on the hard drive, and is only changed once a day, at the "Update Time." specified in the ViP622 in Menu-8-4 "Updates".

The Guide info on the Hard Drive is updated from the EPG stream only due to:

a) Reboot, which then starts a "Program Guide Information Updating, Please Wait" screen, or

b) Switch Check Test, which starts the same Guide update process.

DVR timers are not affected by EEPG info that is in the stream, but is not in the hard drive Guide info file (except for authorization to tune to the channel, which requires the EEPG stream).

I often get DVR timers that will always record a certain program, only to find when I go to play the program that it is some other program, complete with the Info for the other program - indicating that the EEPG info was updated after my Guide hard drive info file was created, but before the broadcast.

 

[Smith P.]

I recall when the EEPG came, DRV[PVR] did not require to reboot each night.
Is current 501...510 do that now? Or rest of DVR models:721,921,942,522,625 ?

 

[kstuart]

I recall when the EEPG came, DRV[PVR] did not require to reboot each night.
Is current 501...510 do that now? Or rest of DVR models:721,921,942,522,625 ?

The EEPG does not require a reboot.

But a reboot always updates the EEPG.

I always rebooted my 501's every night manually, now the ViP622 does that automatically.

 

[Smith P.]

Well, let me say different way - EEPG updating pretty often, a few times per day;
SW in DVR handles the process correctly, using append/purge function to cut old record and add new.

No reboot required to maintain EEPG DB inside DVR.