oe-alliance / AutoBouquetsMaker

Automatically build and update bouquets from the DVB stream.
GNU General Public License v3.0
23 stars 59 forks source link

Dreambox DM920 - Freeview UK failure. #301

Open NicZ1 opened 2 weeks ago

NicZ1 commented 2 weeks ago

Trying to get the Freeview channels. I have a DM920 with the combi tuner S2/C/T2: First Twin Tuner: Tuner A connected to Tivusat@13E, Tuner B not connected Second Multi Tuner: Tuner C/S2 connected to Freesat 28.2, Tuner C/T2 connected to terrestrial aerial, Tuner D/S2 connected to Freesat 28.2.

S2 services are working ok. When trying to get Freeview I get Tuner Failed message. I checked with the manual Signal Finder and I get the list of channels with a very good signal quality over the frequency ABM is looking for my location so I know my set up is ok. I have attached the log file. abm.log

Many thanks

AbuBaniaz commented 2 weeks ago

We actually need the enigma2 debug log. Anyway.. We have ABM set to tune to 666 MHz for BBC One SD, which seems to match what is on wikipedia. So I don't know why it is not locking. I don't know if we need another workaround for that tuner type in ABM. Does an Enigma2 scan work?

Can you enable the "Show DVB-T frequency finder" in ABM's configure menu, then run the "Frequency finder applet". If it does work, please upload the xml file that is created.

1

2

NicZ1 commented 2 weeks ago

Thank you for replying. I have done the steps above and the frequency finder doesn't work. While scanning it finds one transponder on 618Mhz - Ch39 and then at the end it just shows "Only DVB-T2 multiplexes found. Insufficient data to create a provider file". Interestingly, an Enigma2 scan doesn't wok either if I do it by XML. If I switch to UHF band then it finds only a few channel on the 618Mhz. But if I do an Enigma2 Signal Finder on 666Mhz then I get an excellent signal and the list of services.

I have attached the Enigma2 Debug Log, the ABM Log, a couple of screenshot about the Signal Finder. The more I look into this the more I get confused. It seems to me that ABM in not at fault here but the underlying Enigma2 tuners management.

abm.log Enigma2_debug_2024-06-19_09-27-25.log Screenshot 2024-06-19 103833 Screenshot 2024-06-19 103745

AbuBaniaz commented 2 weeks ago

Please do not waste time with ABM log. It does not show all the entries. We need the enigma2 debug log showing the ABM execution.

Does Terrestrial Scan plugin work or does it do the similar thing? You will have to install it.

Most of the code changes to support the DM 920 in ViX is by @DimitarCC I am sure he or someone else capable will be able to look this at some stage.

Huevos commented 2 weeks ago

Please try TerrestrialScan plugin and report back.

NicZ1 commented 1 week ago

@AbuBaniaz @Huevos Thank you both.

I have run Terrestrial Scan twice. First using the XML file, then using the whole UHF band.

First run is at 48203.1714 in the Log. Second run is at 48223.1243.

The First run didn't find anything, I suppose because the XML file limits the search at only the frequencies that are relevant - which none work.

The second run fails up to the point where it can gets a lock on the 618Mhz and it finds the transponder and its services. That is the only frequency that works for the whole scan.

Still a mystery why 618 is the only frequency that works.

Enigma2_debug_2024-06-21_09-13-12.log

TwolDE2 commented 1 week ago

@NicZ1 so this says tuner C - do you have setup on tuner A & B for Sat??????

Huevos commented 1 week ago

It would be helpful for us to see the settings file.

NicZ1 commented 1 week ago

@Huevos My configuration is as follow: First Twin Tuner: A-S2 connected to 13E, B-S2 to nothing (I will eventually connect it to 13E) Second Multi Tuner: C-S2 connected to 28.2E, C-T2 connected to Terrestrial aerial Hannington D-S2 connected to 28.2E, D-T2 connected as C-T2 above but I have also tried to set it as Not Connected - no difference. I have also tried to set the C-S2 and D-S2 to Not connected just to try as I thought that maybe the Tuners Manager was getting confused - No difference. Settings file attached (renamed as .txt so that I can upload it here)

settings.txt

TwolDE2 commented 1 week ago

@NicZ1 . thanks helps if I read from start of these posts.... However, from what I see on the WEB, you can simultaneously only have Sat / Sat Sat / DVB-T2 (H.265) Sat / DVB-C So can you test with C disabled and D set to T2 Hannington??..

TwolDE2 commented 1 week ago

so C & D all sat disabled, set T2 , reboot and test T2

NicZ1 commented 1 week ago

@TwolDE2 @Huevos @AbuBaniaz Sorry for the late answer. Disabling C & D All Sat and Cable didn't make any difference. I also tried to do a Manual Scan (with Network Scan) choosing the 666Mhz transponder and that worked. In fact the Manual Scan works also with the C-S2 and D-S2 enabled.

sh1

I did the exact same tests with another image (BlackHole 10.5) and it showed the exact same behaviour.

Debug log attached: Terrestrial Scan at 133.7324 Manual Scan with Network Scan at 376.6290

Thanks a lot for all your time and effort on this.

Enigma2_debug_2024-06-23_15-37-48.log

Huevos commented 1 week ago

TerrestrialScan

<   302.2346> [eDVBFrontend3] tune
<   302.2348> [eDVBChannel] OURSTATE: tuning
<   302.2352> [eDVBFrontend3] startTuneTimeout 5000
<   302.2356> [eDVBFrontend3] setFrontend 1
<   302.2358> [eDVBFrontend3] setting frontend
<   302.3981> [eDVBFrontend3] fe event: status 0, inversion off, m_tuning 1
<   302.3993> [TerrestrialScan][checkTunerLock] TUNING
<   302.5587> [eDVBFrontend3] fe event: status 1, inversion off, m_tuning 2
<   302.7187> [eDVBFrontend3] fe event: status 0, inversion off, m_tuning 3
<   302.8787> [eDVBFrontend3] fe event: status 1, inversion off, m_tuning 4
<   303.0387> [eDVBFrontend3] fe event: status 0, inversion off, m_tuning 5
<   303.1987> [eDVBFrontend3] fe event: status 1, inversion off, m_tuning 6
<   303.3587> [eDVBFrontend3] fe event: status 0, inversion off, m_tuning 7
<   303.5187> [eDVBFrontend3] fe event: status 1, inversion off, m_tuning 8
<   303.6787> [eDVBFrontend3] fe event: status 0, inversion off, m_tuning 9
<   303.7387> [eDVBFrontend3] fe event: status 20, inversion off, m_tuning 10
<   303.7390> [eDVBFrontend3] FE_TIMEDOUT! ..abort
<   303.7393> [eDVBChannel] OURSTATE: failed, fatal
<   303.8097> [TerrestrialScan][checkTunerLock] TUNING FAILED

ServiceScan

<   314.4825> [eDVBFrontend3] tune
<   314.4827> [eDVBChannel] OURSTATE: tuning
<   314.4953> [eDVBFrontend3] startTuneTimeout 5000
<   314.4954> [eDVBFrontend3] setFrontend 1
<   314.4954> [eDVBFrontend3] setting frontend
<   314.4955> [eDVBFrontend3] fe event: status 0, inversion off, m_tuning 1
<   314.8021> [eDVBFrontend3] fe event: status 1, inversion off, m_tuning 2
<   314.8936> [eDVBFrontend3] fe event: status 6, inversion off, m_tuning 3
<   314.9660> [eDVBFrontend3] fe event: status 7, inversion off, m_tuning 4
<   315.0406> [eDVBFrontend3] fe event: status 1f, inversion off, m_tuning 5
<   315.0407> [eDVBChannel] OURSTATE: ok

Most likely Dream doesn't like at least one of the auto parameters supplied by TerrestrialScan and ABM. We need to figure out which one.

So go to one of the terrestrial channels you managed to tune with ServiceScan. Open Satfinder. Change predefined transponder to manual transponder. Take a screengrab. Post here.

NicZ1 commented 1 week ago

@Huevos Here they are

SignalFinder1 SignalFinder2

Huevos commented 1 week ago

Can you add a copy of /etc/enigma2/lamedb please?

NicZ1 commented 1 week ago

@Huevos Attached lamedb.txt

Huevos commented 1 week ago

What is your ABM region?

NicZ1 commented 1 week ago

@Huevos For satellite it's BBC South/ITV Meridian SE - for terrestrial it's Region Hannington

Huevos commented 1 week ago

Can you try the attached file. Unzip. Transfer terrestrial_uk_freeview.xml to /usr/lib/enigma2/python/Plugins/SystemPlugins/AutoBouquetsMaker/providers Then try ABM again.

UK.zip

NicZ1 commented 1 week ago

@Huevos Unfortunately that didn't work. Scan done with C & D S2 disabled. Log attached. Enigma2_debug_2024-06-24_13-39-22.log