67 replies to this topic

[zeros]

Thanks for explanation!

I wonder, if andy1 can test it or whether it would solve his problem also (Pluggable dualtuners on ET10000- Si2169 (DVB-C/T/T2) )?

[zeros]

Dimitrij, one more observation, related with your last remark-

in my case:

 

NIM Socket 2:

        Type: DVB-T

        Name: PCTV 290e

        Has_Outputs: no

        Frontend_Device: 2

 

My problems in DVB-T2, the stick PCTV 290e is also DVB-T2 capable, but it shows Type: DVB-T

And now we have in the code:

if "DVB-T2" in types: # DVB-T2 implies DVB-T support types.remove("DVB-T")

Could this cause me problems?

Edited by zeros, 4 February 2016 - 10:45.

[zeros]

I analized it and should be OK, I would advise to add that small change!? Thanks to Dimitrij.

Attached Files

•  Comparison-different-Teams.png   374.93KB   4 downloads

[Dimitrij]

I analized it and should be OK, I would advise to add that small change!?

Thank you for testing and comparison.
In the evening, I'll make patch.

[zeros]

Today again all OK here, no sound jitter and also all OK with timer recording!
My friend sent such a log, how it looks like with openATV & vusolo4k:

Welcome to openATV for vusolo4k
openatv 5.1 vusolo4k

vusolo4k login: root
Password:
Last login: Thu Feb 4 17:30:35 EET 2016 on pts/0
root@vusolo4k:~# cat /proc/bus/nim_sockets
NIM Socket 0:
Type: DVB-S2
Name: Vuplus DVB-S NIM(7376 FBC)
Frontend_Device: 0
NIM Socket 1:
Type: DVB-S2
Name: Vuplus DVB-S NIM(7376 FBC)
Frontend_Device: 1
NIM Socket 2:
Type: DVB-S2
Name: Vuplus DVB-S NIM(7376 FBC)
Frontend_Device: 2
NIM Socket 3:
Type: DVB-S2
Name: Vuplus DVB-S NIM(7376 FBC)
Frontend_Device: 3
NIM Socket 4:
Type: DVB-S2
Name: Vuplus DVB-S NIM(7376 FBC)
Frontend_Device: 4
NIM Socket 5:
Type: DVB-S2
Name: Vuplus DVB-S NIM(7376 FBC)
Frontend_Device: 5
NIM Socket 6:
Type: DVB-S2
Name: Vuplus DVB-S NIM(7376 FBC)
Frontend_Device: 6
NIM Socket 7:
Type: DVB-S2
Name: Vuplus DVB-S NIM(7376 FBC)
Frontend_Device: 7
NIM Socket 8:
Type: DVB-C
Name: Vuplus DVB-C NIM(TT3L10)
Mode 0: DVB-C
Mode 1: DVB-T2
Frontend_Device: 8
I2C_Device: 4
NIM Socket 9:
Type: DVB-C
Name: Vuplus DVB-C NIM(TT3L10)
Mode 0: DVB-C
Mode 1: DVB-T2
Frontend_Device: 9
I2C_Device: 4

NIM Socket 10:
Type: DVB-T2
Name: Sundtek DVB-T2 (III) (2/0) (USB)DVB-T2
Frontend_Device: 10
NIM Socket 11:
Type: DVB-C
Name: Vuplus DVB-T/C USB NIM(TURBO)
Frontend_Device: 11root@vusolo4k:~#

[Dimitrij]

fixed https://github.com/O...e17818267cfcb6b

[andy1]

Thanks for explanation!

I wonder, if andy1 can test it or whether it would solve his problem also (Pluggable dualtuners on ET10000- Si2169 (DVB-C/T/T2) )?

I have the same problems in todays update. No signal from slot A and B.

I have also tried et10000 update  of 20160130 which also failed. I noticed a big et. driver update here. Perhaps this could be a cause of the problem?

 

I had to revert back to the working img. of 20160127

 

These are my hardware configuration:

Tunerslot A: Si2169 (DVB-C-T/T2) configured for DVB-C

Tunerslot B: Si2169 0(DVB-C-T/T2) configured for DVB-T/T2

Tunerslot C: AVL6211 (DVB S/S2)  satellite configured

Tunerslot D: AVL6211 (DVB S/S2) equal to C

 

Thanks

[zeros]

Hi andy1,
Your Tuner A and Tuner B are dual tuners, right?
Please go next time after update to
Setup->Searvice searching->Tuner configuration->select first A
Reconfigure it!
Then the same with Tuner B.
To reconfigure again, I mean, you can choose from remote, whether it is DVB-T/T2 or DVB-C.
When tuners positions changed, then you have to do it in any case! (previous modification)

[Dimitrij]

ET models not dual tuners.

[zeros]

I'm sorry, I just wanted to say that the same tuners can be configured in both DVB-T/DVB-T2, or DVB-C. It must be reconfigure, because the previous patch (author of proposal was sundtek) changed their locations, but the cables andy1 didn't changed around.

Edited by zeros, 4 February 2016 - 21:34.

[andy1]

I'm sorry, I just wanted to say that the same tuners can be configured in both DVB-T/DVB-T2, or DVB-C. It must be reconfigure, because the previous patch (author of proposal was sundtek) changed their locations, but the cables andy1 didn't changed around.

You are right, they can be configured in both DVB-T/T2 and C.

 

I have now reconfigured slot A and B and as you proposed. The locations was swapped and the problem is solved. 

Everything works fine even with the latest img. of today.

 

Thank you very much.

[zeros]

When I checked the different Teams codes, I find on openatv such a difference:
on PLi, line 711:
if self.hasNimType("DVB-C") or self.hasNimType("DVB-T"):

and on ATV:
https://github.com/o...Manager.py#L173
line 1010:

if self.hasNimType("DVB-C") or self.hasNimType("DVB-T") or self.hasNimType("DVB-T2"):

 

I think we may add this *or self.hasNimType("DVB-T2"):* also?

 

The reason you can see on post #45

The Type may also be
NIM Socket 10:
 Type: DVB-T2
 Name: Sundtek DVB-T2 (III) (2/0) (USB)DVB-T2

 

What do you think?

Edited by zeros, 5 February 2016 - 09:09.

[Dimitrij]

It does not need to.

answer to hasNimType("DVB-T")  if DVB-T or DVB-T2 return True

[littlesat]

I also needed to reconfigure my DVB-T(2)/DVB-C tuner in my ET10000 post this patch.... it reverted back to DVB-T after an reboot... (I discovered it due to timer conflicts...). I even needed to remove the complete specific NIM from my /etc/enigma2/settings file... and then reboot and re-configure... But once done it is fine again!

Edited by littlesat, 5 February 2016 - 09:54.

[zeros]

Dimitrij,

pleas look thye code:

if self.hasNimType("DVB-C") or self.hasNimType("DVB-T") or self.hasNimType("DVB-T2"):
   print "Reading cables.xml"
   db.readCables(self.cablesList, self.transponderscable)
   print "Reading terrestrial.xml"
   db.readTerrestrials(self.terrestrialsList, self.transpondersterrestrial)

If that is missing:

or self.hasNimType("DVB-T2"):

then if I have a tuner, for example Sundtek DVB-T2 (III) (2/0) (USB)DVB-T2, which is stated as Type: DVB-T2

then if we want with such a tuner to make a scan, will not print the Reading cables.xml / Reading terrestrial.xm

as far as I understand. ?

But I can't get it to test at the moment, because my Sundtek DVB-T2 (III) (2/0) (USB)DVB-T2 is in heavy use (and not in my hands).

Edited by zeros, 5 February 2016 - 11:57.

[zeros]

The same happens with Vuplus DVB-C NIM(TT3L10)
If you want to scan DVB-T2 terrestrial.xml with it

NIM Socket 9:
Type: DVB-T2
Name: Vuplus DVB-C NIM(TT3L10)
Mode 0: DVB-C
Mode 1: DVB-T2
Frontend_Device: 9
I2C_Device: 4

And you will get finger. Only the manual scan will run with DVB-T2 Type tuner...

[Dimitrij]

Somewhere there is an error.
Who can help me?

config.Nims.3.terrestrial=2
config.Nims.2.configMode=nothing
config.Nims.4.terrestrial=2
config.Nims.4.multiType=1

See NIM Socket 3:Type: DVB-T2

root@et8500:~# cat /proc/bus/nim_sockets
NIM Socket 0:
        Type: DVB-S2
        Name: AVL6211
        Frontend_Device: 0
        Has_Ouput: yes
        I2C_Device: 0
NIM Socket 1:
        Type: DVB-S2
        Name: AVL6211
        Frontend_Device: 1
        Has_Ouput: yes
        I2C_Device: 1
NIM Socket 2:
        Type: DVB-S2
        Name: AVL6211
        Frontend_Device: 2
        Has_Ouput: yes
        I2C_Device: 2
NIM Socket 3:
        Type: DVB-T2
        Mode 0: DVB-T2
        Mode 1: DVB-C
        Mode 2: DVB-T
        Name: Si216x
        Frontend_Device: 3
        Has_Ouput: yes
        I2C_Device: 3
NIM Socket 4:
        Type: DVB-S2
        Name: Sundtek DVB-S/S2 (IV) (0/0) (USB)
        Frontend_Device: 4
        Has_Ouput: no
        I2C_Device: 12
root@et8500:~#

please see screenshots

Edited by Dimitrij, 6 February 2016 - 12:24.

[el bandido]

Your usb tuner is changing modes random or without cause? Did this ONLY happen on a hard boot or reboot  the receiver?

[zeros]

A: DVB-S2
B: DVB-S2
C: DVB-S2
D: you configured it to DVB-C as seen on screenshot (Si216x, which can be configured DVB-T2/DVB-C/DVB-T)
E: not visible on screenshot, but should be DVB-S2

Did you restart box after configurinig tuner D: ? If you did'nt, then you should and look it again from ... Settings

If the answer is Yes to the previous question
Whether the procedure previously was OK and you found this error now?

Your post #40 need also solution? Yes or no? I now began to feel that this was rather the problem description than an explanation.

Edited by zeros, 6 February 2016 - 17:46.

[Dimitrij]

The same happens with Vuplus DVB-C NIM(TT3L10)
If you want to scan DVB-T2 terrestrial.xml with it

NIM Socket 9:
Type: DVB-T2
Name: Vuplus DVB-C NIM(TT3L10)
Mode 0: DVB-C
Mode 1: DVB-T2
Frontend_Device: 9
I2C_Device: 4

And you will get finger. Only the manual scan will run with DVB-T2 Type tuner...

Not true.

Open manual scan fot this tuner and select 'Region'.

Region(terrestrial.xml) is empy?

Edited by Dimitrij, 6 February 2016 - 19:33.