Can not tune 730mhz DVB-T2 SoloSe V2

  • Thread starter Thread starter kurben
  • Start date Start date
K

kurben

Hello.

I have a problem with my new SoloSe V2 Dual tuner DVB-T2.
It scans all the Swedish muxes except for this one:
MUX 7 UHF 730 MHz channel 53 32KE, 256 QAM, PP4, 3/5, Guard 19/256, 32,49 Mbit/s, DVB-T2

Strange because this mux works fine: MUX 6 UHF 618 MHz channel 39 32KE, 256 QAM, PP4, 2/3, Guard 1/16, 36,55 Mbit/s, DVB-T2

There are some diffences but not much.

I have tried the factory Vu+ image, Open black hole 0.1 (all updates) Ordinary Black hole 2.x, and also VTI. None of them tune the 730 mhz mux.

I have also tried with two new diffrent terrestial.xml specific for sweden.

It is not related to my antenna system as I have no problem with my other recivers.

I have contacted Vu+ support regarding this as I think it is related to a bug in the drivers for the new dual tuner.

What do you guys think?

I am also going to try connecting a USB DVB-T2 tuner (Pctv e290) and se if that works with the 730mhz mux. But I need a USB hub first.
 
kurben said:
Hello.

I have a problem with my new SoloSe V2 Dual tuner DVB-T2.
It scans all the Swedish muxes except for this one:
MUX 7 UHF 730 MHz channel 53 32KE, 256 QAM, PP4, 3/5, Guard 19/256, 32,49 Mbit/s, DVB-T2

Strange because this mux works fine: MUX 6 UHF 618 MHz channel 39 32KE, 256 QAM, PP4, 2/3, Guard 1/16, 36,55 Mbit/s, DVB-T2

There are some diffences but not much.

I have tried the factory Vu+ image, Open black hole 0.1 (all updates) Ordinary Black hole 2.x, and also VTI. None of them tune the 730 mhz mux.

I have also tried with two new diffrent terrestial.xml specific for sweden.

It is not related to my antenna system as I have no problem with my other recivers.

I have contacted Vu+ support regarding this as I think it is related to a bug in the drivers for the new dual tuner.

What do you guys think?

I am also going to try connecting a USB DVB-T2 tuner (Pctv e290) and se if that works with the 730mhz mux. But I need a USB hub first.
Click to expand...
Report it to Vu+ (www.vuplus.com).
 
I think I am not the only one who found this, the problem seems to be that Enigma2 does not support the complete DVB-T2 standard!!!

If you look at the code : #h**ps://github.com/oe-alliance/oe-alliance-tuxbox-common/blob/master/src/terrestrial.xml

You can see this part:

code_rate_{lp,hp}:
0 = 1/2,
1 = 2/3,
2 = 3/4,
3 = 5/6,
4 = 7/8,
5 = Auto (default),
6 = None

And the code_rate option 3/5 is missing and also 4/5


  • 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)

  • h**ps://en.wikipedia.org/wiki/DVB-T2

The same has been found on openpli: h**p://forums.openpli.org/topic/32811-enigma2-modification-needed/

Here is also the source for open black hole and on line 972 the "Terrestial" section is missing the Code rate 3/5 and also 4/5.
h**ps://github.com/OpenBlackHole/openblackhole-enigma2/blob/31306becf9b4152136d6122dc913b4b67b70af74/lib/python/Screens/ScanSetup.py

# terrestial
self.scan_ter.frequency = ConfigInteger(default = defaultTer["frequency"], limits = (50000, 999000))
self.scan_ter.channel = ConfigInteger(default = 21, limits = (1, 99))
self.scan_ter.inversion = ConfigSelection(default = defaultTer["inversion"], choices = [
(eDVBFrontendParametersTerrestrial.Inversion_Off, _("Off")),
(eDVBFrontendParametersTerrestrial.Inversion_On, _("On")),
(eDVBFrontendParametersTerrestrial.Inversion_Unknown, _("Auto"))])
# WORKAROUND: we can't use BW-auto
self.scan_ter.bandwidth = ConfigSelection(default = defaultTer["bandwidth"], choices = [
(1712000, "1.712MHz"),
(5000000, "5MHz"),
(6000000, "6MHz"),
(7000000, "7MHz"),
(8000000, "8MHz"),
(10000000,"10MHz")
])
#, (eDVBFrontendParametersTerrestrial.Bandwidth_Auto, _("Auto"))))
self.scan_ter.fechigh = ConfigSelection(default = defaultTer["fechigh"], choices = [
(eDVBFrontendParametersTerrestrial.FEC_1_2, "1/2"),
(eDVBFrontendParametersTerrestrial.FEC_2_3, "2/3"),
(eDVBFrontendParametersTerrestrial.FEC_3_4, "3/4"),
(eDVBFrontendParametersTerrestrial.FEC_5_6, "5/6"),
(eDVBFrontendParametersTerrestrial.FEC_6_7, "6/7"),
(eDVBFrontendParametersTerrestrial.FEC_7_8, "7/8"),
(eDVBFrontendParametersTerrestrial.FEC_8_9, "8/9"),
(eDVBFrontendParametersTerrestrial.FEC_Auto, _("Auto"))])
self.scan_ter.feclow = ConfigSelection(default = defaultTer["feclow"], choices = [
(eDVBFrontendParametersTerrestrial.FEC_1_2, "1/2"),
(eDVBFrontendParametersTerrestrial.FEC_2_3, "2/3"),
(eDVBFrontendParametersTerrestrial.FEC_3_4, "3/4"),
(eDVBFrontendParametersTerrestrial.FEC_5_6, "5/6"),
(eDVBFrontendParametersTerrestrial.FEC_6_7, "6/7"),
(eDVBFrontendParametersTerrestrial.FEC_7_8, "7/8"),
(eDVBFrontendParametersTerrestrial.FEC_8_9, "8/9"),
(eDVBFrontendParametersTerrestrial.FEC_Auto, _("Auto"))])


Can some coder please fix this?
 
kurben said:
I think I am not the only one who found this, the problem seems to be that Enigma2 does not support the complete DVB-T2 standard!!!

If you look at the code : #h**ps://github.com/oe-alliance/oe-alliance-tuxbox-common/blob/master/src/terrestrial.xml

You can see this part:

code_rate_{lp,hp}:
0 = 1/2,
1 = 2/3,
2 = 3/4,
3 = 5/6,
4 = 7/8,
5 = Auto (default),
6 = None

And the code_rate option 3/5 is missing and also 4/5


  • 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)

  • h**ps://en.wikipedia.org/wiki/DVB-T2
The same has been found on openpli: h**p://forums.openpli.org/topic/32811-enigma2-modification-needed/

Here is also the source for open black hole and on line 972 the "Terrestial" section is missing the Code rate 3/5 and also 4/5.
h**ps://github.com/OpenBlackHole/openblackhole-enigma2/blob/31306becf9b4152136d6122dc913b4b67b70af74/lib/python/Screens/ScanSetup.py

# terrestial
self.scan_ter.frequency = ConfigInteger(default = defaultTer["frequency"], limits = (50000, 999000))
self.scan_ter.channel = ConfigInteger(default = 21, limits = (1, 99))
self.scan_ter.inversion = ConfigSelection(default = defaultTer["inversion"], choices = [
(eDVBFrontendParametersTerrestrial.Inversion_Off, _("Off")),
(eDVBFrontendParametersTerrestrial.Inversion_On, _("On")),
(eDVBFrontendParametersTerrestrial.Inversion_Unknown, _("Auto"))])
# WORKAROUND: we can't use BW-auto
self.scan_ter.bandwidth = ConfigSelection(default = defaultTer["bandwidth"], choices = [
(1712000, "1.712MHz"),
(5000000, "5MHz"),
(6000000, "6MHz"),
(7000000, "7MHz"),
(8000000, "8MHz"),
(10000000,"10MHz")
])
#, (eDVBFrontendParametersTerrestrial.Bandwidth_Auto, _("Auto"))))
self.scan_ter.fechigh = ConfigSelection(default = defaultTer["fechigh"], choices = [
(eDVBFrontendParametersTerrestrial.FEC_1_2, "1/2"),
(eDVBFrontendParametersTerrestrial.FEC_2_3, "2/3"),
(eDVBFrontendParametersTerrestrial.FEC_3_4, "3/4"),
(eDVBFrontendParametersTerrestrial.FEC_5_6, "5/6"),
(eDVBFrontendParametersTerrestrial.FEC_6_7, "6/7"),
(eDVBFrontendParametersTerrestrial.FEC_7_8, "7/8"),
(eDVBFrontendParametersTerrestrial.FEC_8_9, "8/9"),
(eDVBFrontendParametersTerrestrial.FEC_Auto, _("Auto"))])
self.scan_ter.feclow = ConfigSelection(default = defaultTer["feclow"], choices = [
(eDVBFrontendParametersTerrestrial.FEC_1_2, "1/2"),
(eDVBFrontendParametersTerrestrial.FEC_2_3, "2/3"),
(eDVBFrontendParametersTerrestrial.FEC_3_4, "3/4"),
(eDVBFrontendParametersTerrestrial.FEC_5_6, "5/6"),
(eDVBFrontendParametersTerrestrial.FEC_6_7, "6/7"),
(eDVBFrontendParametersTerrestrial.FEC_7_8, "7/8"),
(eDVBFrontendParametersTerrestrial.FEC_8_9, "8/9"),
(eDVBFrontendParametersTerrestrial.FEC_Auto, _("Auto"))])


Can some coder please fix this?
Click to expand...
Again, WRITE TO VU+ WITH THESE INFOS!
 
I have done that and also informed OpenPli as from what I understand the code to the Open Black hole is based from.
 
I have now tested with a USB DVB-T2 tuner (PCTV 290e ) . This tuner can tune the 730 mhz mux without problems. That means that the bug is not in Enigma2 code but rather in the Vu+ driver for the built in tuner.

I have the new Vu+ SoloSe v2 with the new Dual DVB-T2 tuners. I will once again contact Vu+ and probably not get en answer as the two other times I have done that....





But at least we now know the problem lies in the Vu+ drivers and not the actual code for Enigma2...
 
kurben said:
I have now tested with a USB DVB-T2 tuner (PCTV 290e ) . This tuner can tune the 730 mhz mux without problems. That means that the bug is not in Enigma2 code but rather in the Vu+ driver for the built in tuner.

I have the new Vu+ SoloSe v2 with the new Dual DVB-T2 tuners. I will once again contact Vu+ and probably not get en answer as the two other times I have done that....





But at least we now know the problem lies in the Vu+ drivers and not the actual code for Enigma2...
Click to expand...
I've wrote in the past to Vu+ and they have not answered me BUT they have made fixes against my reports.
So report your issue to Vu+ and wait.
 
Done some more extensive testing and tried almost all of the available images and these are the results:

OpenPli 4.0 2015-08-29 (No tune channel 53, Working CI/CAM)

Open Black Hole 0.1 (No tune channel 53, Working CI/CAM)

OpenATV 5.1 (Tune working on Channel 53, NO working CI/CAM)

Black Hole 2.1.7 (No tune channel 53, NO working CI/CAM)

OpenVIX 3.2.003 (No tune channel 53 Working CI/CAM)

VU+ Factory image: vuplus-image-vusolose-20150723160653 (Tune working on channel 53! CI/CAM Working.)


So two images have the tuning working on channel 53 DVB-T2 but only the VU+ factory image does this while also has a working CI/CAM solution. So for the moment I have to use the VU+ image that is very vanilla.
 
Found the issue, If I tune manually to channel 53 set to DVB-T2 and everything to auto EXCEPT for PLPID set to 001 then Open Black hole finds all channels on the mux! Would it be possible to have a Auto option for the PLPID? That could possibly solve this issue.
 
You must log in or register to reply here.
Back
Top