2 replies to this topic

[Aizecu]

Please correct me if I were wrong.

 

According to enigma.eDVBFrontendParametersTerrestrial Class Reference

• FEC_1_2 = _enigma.eDVBFrontendParametersTerrestrial_FEC_1_2  
• FEC_2_3 = _enigma.eDVBFrontendParametersTerrestrial_FEC_2_3  
• FEC_3_4 = _enigma.eDVBFrontendParametersTerrestrial_FEC_3_4  
• FEC_5_6 = _enigma.eDVBFrontendParametersTerrestrial_FEC_5_6  
• FEC_7_8 = _enigma.eDVBFrontendParametersTerrestrial_FEC_7_8  
• FEC_Auto = _enigma.eDVBFrontendParametersTerrestrial_FEC_Auto

 

As far as I know, these parameters refer to "Code Rate".

• DVB-T has (1/2, 2/3, 3/4, 5/6, 7/8)
• DVB-T2 has (1/2, 3/5, 2/3, 3/4, 4/5)

 

It seems that the current parameters supports only DVB-T.

 

Probably, there are other parameters that also need to be updated in order to fully support DVB-T2.

( I don't certainly know about that )

 

In GUI has the same problem too, parameters are limited.

/usb/lib/enigma2/python/Tools/Transponder.py

/usb/lib/enigma2/python/Screens/ScanSetup.py

 

Anyway, enigma needs to be updated first.

Again, Am I correct ?

 

Thank you

Attached Files

•  t2t2.png   132.03KB   25 downloads

Edited by Aizecu, 1 March 2014 - 18:13.

[littlesat]

We do not have T2 in our region... So for us this is not possible to debug and test.

[Aizecu]

I have T2 in my region and it's about this problem. 

 

We do not have T2 in our region... So for us this is not possible to debug and test.

I wish other developers who could be able test T2 were around here. 

 

http://en.wikipedia.org/wiki/DVB-T2

 

Thank you.