Xtrend Et10k-Timer Recording Didn’t Records Properly

[ccs]

All that change did is to produce the error message. Before that it just trapped the error and silently returned.

Yes, but is it likely that there will be a fix for the "error" when it is detected?

[Huevos]

@CCS can I have a step by step list to create the error. Exact steps please.

Also please try the attached file and see if the same error occurs.

[ccs]

@CCS can I have a step by step list to create the error. Exact steps please.

Also please try the attached file and see if the same error occurs.

Hi, is this the "InitNimManager] tunerTypeChanged error: global name 'self' is not defined" problem you're referring to, or the issue with 4 T2 tuners being used at the same time?

[ccs]

A simple reboot from deep standby causes InitNimManager] tunerTypeChanged error: global name 'self' is not defined - first debug log.

2nd debug log includes your NimManager.py

[birdman]

A simple reboot from deep standby causes InitNimManager] tunerTypeChanged error: global name 'self' is not defined - first debug log.

But only if you have more than one dual DVB-C/DVB-T2 tuner and want to run them as DVB-T2.

I reproduced this on my Xtrend et8000. It had actually been reporting it for ages.
It is an error, but it doesn't actually stop anything being done (probably) as the previous code also produced an error (a different one) but that was inside a try/except clause and just returned.

[ccs]

Maybe I should also have pointed out that in the 2 debug logs in #79, tuner D is configured as disabled.

[birdman]

Maybe I should also have pointed out that in the 2 debug logs in #79, tuner D is configured as disabled.

Doesn't matter. If it is set to DVB-T2 then, even if it is disabled, the code to set it to DVB-T2 will still run (and do nothing beyond produce an error message, as all of the tuners seem to be linked in some way and only the first one can pick up a raw channel).

[Huevos]

No step by step yet then? One for each problem.

[ccs]

No step by step yet then? One for each problem.

Isn't post #79 enough detail?

And can I ask again, is the issue using 4 t2 tuners simultaneously on an et10K the other one?

[birdman]

No step by step yet then? One for each problem.

• Install DVB-C/DVB-T2 tuners on your system (at least two of them)
• Configure them as DVB-T2
• Boot the system
• Look at the log

[Huevos]

Thanks Birdman.

@CCS, so your second log in post #79 shows the NimManager.py I supplied sets the tuners correctly, right?

[ccs]

Thanks Birdman.

@CCS, so your second log in post #79 shows the NimManager.py I supplied sets the tuners correctly, right?

The 'self' is not defined error has gone, and there are no other obvious NimManager errors, but 4 simultaneous T2 tuners still don't work.
I only mentioned that problem earlier because I felt that there was a slight chance that NinManager wasn't setting them all up correctly, and the 'self' error may have been part of the reason.

I can try others things out, but at the moment my ET10K is struggling, I suspect RAM problems, but only time will tell.
It hangs sometimes while booting, I can init 4, init 3 and then it always continues to work fine.

Nothing to do with your NimManager.py - it isn't installed.

[Huevos]

Could be a hardware thing. There might be a limitation on the max number of DVB-T2 tuners possible, or their order.

[ccs]

Could be a hardware thing. There might be a limitation on the max number of DVB-T2 tuners possible, or their order.

Yes - the manual mentions DVB-C to be avoided in slot D, that's why I thought there was a slight chance that defaulting to C could be the reason.

I'll post the Nim slots allocated before and after your patch to see what's changed.

[ccs]

Before patch (ie current 5.1.019)....

cat /proc/bus/nim_sockets
NIM Socket 0:
        Type: DVB-T2
        Name: Si2169
        Has_Outputs: yes
        Frontend_Device: 0
        I2C_Device: 2
NIM Socket 1:
        Type: DVB-T2
        Name: Si2169
        Has_Outputs: yes
        Frontend_Device: 1
        I2C_Device: 3
NIM Socket 2:
        Type: DVB-T2
        Name: Si2169
        Has_Outputs: yes
        Frontend_Device: 2
        I2C_Device: 4
NIM Socket 3:
        Type: DVB-T2
        Name: Si2169
        Has_Outputs: yes
        Frontend_Device: 3
        I2C_Device: 4
NIM Socket 4:
        Type: DVB-C
        Name: Sundtek DVB-C (III) (1/0) (USB)
        Has_Outputs: no
        Frontend_Device: 4
        I2C_Device: -1
root@et10000:~#

NIM sockets 3 and 4 both have the same I2C_Device: 4 for some reason.

Debug log...

<    33.558> [NimManager][enumerateNIMs] slot: 0 - entry: {'name': 'Si2169', 'frontend_device': 0, 'has_outputs': True, 'isempty': False, 'i2c': 2, 'type': 'DVB-T2'}
<    33.560> [NimManager][enumerateNIMs] slot: 1 - entry: {'name': 'Si2169', 'frontend_device': 1, 'has_outputs': True, 'isempty': False, 'i2c': 3, 'type': 'DVB-T2'}
<    33.562> [NimManager][enumerateNIMs] slot: 2 - entry: {'name': 'Si2169', 'frontend_device': 2, 'has_outputs': True, 'isempty': False, 'i2c': 4, 'type': 'DVB-T2'}
<    33.563> [NimManager][enumerateNIMs] slot: 3 - entry: {'name': 'Si2169', 'frontend_device': 3, 'has_outputs': True, 'isempty': False, 'i2c': 4, 'type': 'DVB-T2'}