Terrestrail HD channel Scan - Craigkelly

[Huevos]

So, for those using tuner drivers that don't differentiate between T (sd) and T2 (hd) the "system" attribute doesn't make any difference. For those using tuner drivers that do differentiate having the correct "system" attribute is required. As the "ABM.xml" file will be used on many boxes with many different tuner manufactures setting the "system=1" attribute for UK HD MUXs is recommended to support all OpenVix users.

Don't confuse ABM scans with enigma scans. In ABM we are using this value for custom transponder. In enigma it is being used for the scan itself.
Thanks for this clarification.

For my own benefit only, and out of curiosity...

In the terrestrial_uk_freeview.xml (or whichever file name that has been used in this thread) not all transmitters have a custom list of MUX (transponder) frequencies. They have only a single frequency allocated to the transmitter name in the <dvbtconfigs> section. For these entries how does the box/ABM know which MUX to scan or to allocate to that transmitter?

In the case of UK Freeview ABM scans just one transponder and this has all the data on it. The reason custom transponder data is needed is when the data fetched from that transponder is incomplete or incorrect.

While some people may be extremely lucky in that their aerial only picks up the signal from one transmitter many living in the transmitter region may actually receive signals from 2, 3 or 4 transmitters especially since analogue switch off when the broadcast digital power was increased and people fitting wide-band aerials (erroneously advertised as digital aerials). Transmissions from neighbouring transmitters are often unreliable.

That is why Abu maintains individual masts in terrestrial.xml.

[chaser]

This is still not working correctly. I still get 'Tune failed!' errors for non HD channels, and I can't understand why. Following the guide Abu posted earlier:

Firstly, I delete all channels using the command:

init 4 && sleep 10 && rm -f /etc/enigma2/lamedb && rm -f /etc/enigma2/*.tv && rm -f /etc/enigma2/*.radio  && rm -f /etc/enigma2/*.del &&  init 3

and confirm that the lamedb file in /etc/enigma2 has been deleted.

I then check file terrestrial.xml from /etc/tuxbox. It has the following Craigkelly entry:

	<terrestrial name="Craigkelly, Fife (Europe DVB-T/T2)" flags="5" countrycode="GBR">
		<transponder centre_frequency="474000000" bandwidth="0" system="1" constellation="3" guard_interval="4" transmission_mode="2" hierarchy_information="4" inversion="2" /><!-- Ch 21 (HD) -->
		<transponder centre_frequency="498000000" bandwidth="0" system="0" constellation="3" guard_interval="4" transmission_mode="2" hierarchy_information="4" inversion="2" /><!-- Ch 24 -->
		<transponder centre_frequency="522000000" bandwidth="0" system="0" constellation="3" guard_interval="4" transmission_mode="2" hierarchy_information="4" inversion="2" /><!-- Ch 27 -->
		<transponder centre_frequency="546000000" bandwidth="0" system="0" constellation="3" guard_interval="4" transmission_mode="2" hierarchy_information="4" inversion="2" /><!-- Ch 30 -->
		<transponder centre_frequency="570000000" bandwidth="0" system="1" constellation="3" guard_interval="4" transmission_mode="2" hierarchy_information="4" inversion="2" /><!-- Ch 33 (HD) -->
		<transponder centre_frequency="578000000" bandwidth="0" system="1" constellation="3" guard_interval="4" transmission_mode="2" hierarchy_information="4" inversion="2" /><!-- Ch 34 (HD) -->
		<transponder centre_frequency="618000000" bandwidth="0" system="0" constellation="3" guard_interval="4" transmission_mode="2" hierarchy_information="4" inversion="2" /><!-- Ch 39 -->
		<transponder centre_frequency="642000000" bandwidth="0" system="0" constellation="3" guard_interval="4" transmission_mode="2" hierarchy_information="4" inversion="2" /><!-- Ch 42 -->
		<transponder centre_frequency="666000000" bandwidth="0" system="0" constellation="3" guard_interval="4" transmission_mode="2" hierarchy_information="4" inversion="2" /><!-- Ch 45 -->
	</terrestrial>

This information looks correct for the transmitter.

I then check the terrestrial_uk_freeview.xml file from /usr/lib/enigma2/python/Plugins/SystemPlugins/AutoBouquetsMaker/providers. It has the following Craigkelly entries:

	<dvbtconfigs>
		...
		<configuration key="craigkelly_________" frequency="522000000">Craigkelly</configuration>
		...
	</dvbtconfigs>
	<customtransponders>
		...
		<customtransponder key="craigkelly_________" frequency="474000000" transport_stream_id="40bc" system="1"/>
		<customtransponder key="craigkelly_________" frequency="570000000" transport_stream_id="a000" system="1"/>
		<customtransponder key="craigkelly_________" frequency="578000000" transport_stream_id="b000" system="1"/>		
		...
	</customtransponders>

Again, this looks correct (assuming we only need the HD entries in this file???).

However, following the next step, and runing an ABM scan, the lamedb file which gets generated includes the following:

eDVB services /4/
transponders
eeee0000:40bc:233a
	t 474000000:0:5:5:0:3:4:4:2:0:1:0
/
eeee0000:b000:233a
	t 578000000:0:5:5:0:3:4:4:2:0:1:0
/
eeee0000:5040:233a
	t 658000000:0:2:0:2:1:0:0:0:0:0:0
/
eeee0000:107c:233a
	t 674000000:0:1:0:2:1:0:0:0:0:0:0
/
eeee0000:800f:233a
	t 714000000:0:2:0:0:1:0:0:0:0:0:0
/
eeee0000:6040:233a
	t 682000000:0:2:0:2:1:0:0:0:0:0:0
/
eeee0000:a000:233a
	t 570000000:0:5:5:0:3:4:4:2:0:1:0
/
eeee0000:2011:233a
	t 650000000:0:1:0:2:1:0:0:0:0:0:0
/
eeee0000:3005:233a
	t 634167000:0:2:0:2:1:0:0:0:0:0:0
/
end

These frequencies don't match the transmitter frequencies, and I think this is what is then causing the tuning problems (for example, when I tune to ITV2, it tries to tune into frequency 650 which is incorrect. It should be tuning to frequency 498). I don't understand where lamedb is picking these frequencies up from???

If I then run a manual scan, the correct frequencies get picked up, and everything starts working fine again, until ABM rescans:

eDVB services /4/
transponders
eeee0000:107c:233a
	t 522000000:0:5:5:3:2:4:4:2:0:0:0
/
eeee0000:2011:233a
	t 498000000:0:5:5:3:2:4:4:2:0:0:0
/
eeee0000:3005:233a
	t 642000000:0:5:5:3:2:4:4:2:0:0:0
/
eeee0000:40bc:233a
	t 474000000:0:5:5:3:2:4:4:2:0:0:0
/
eeee0000:5040:233a
	t 666000000:0:5:5:3:2:4:4:2:0:0:0
/
eeee0000:6040:233a
	t 618000000:0:5:5:3:2:4:4:2:0:0:0
/
eeee0000:800f:233a
	t 546000000:0:5:5:3:2:4:4:2:0:0:0
/
eeee0000:a000:233a
	t 570000000:0:5:5:3:2:4:4:2:0:0:0
/
eeee0000:b000:233a
	t 578000000:0:5:5:3:2:4:4:2:0:0:0
/
end

[abu baniaz]

why are we discussing two processes

delete lamedb, scan only your mast (not using abm). do all channels work? If so, attach lamedb files.

[abu baniaz]

Normally, we only need the HD frequncies in the custom transponder section. if there is an issue, we can add all the frequencies. However, we need a fully functional lamedb.

[chaser]

why are we discussing two processes

I was only redoing what you had asked earlier...

OK, we may need to add all the transponder data.

Please delete all channel data first. Link to thread with commands in my signature.
Delete providers.cache file
Use attached xml file.
Only use ABM.
Check problematic channels please.

delete lamedb, scan only your mast (not using abm). do all channels work? If so, attach lamedb files.

With manual scan for Craigkelly, all channels work. lamedb attached.

[abu baniaz]

Please place this in ABM provider folder, delete the providers cache, delete lamedb using previous command, run ABM only. Please check the channels again.

[chaser]

That's it working now, thanks. So, the missing SD channels in the terrestrial_uk_freeview.xml file was the issue?

[abu baniaz]

No, incorrect data on tables.By adding the custom transponders, we have overridden the data.

An image build is in progress, I shall add the changes after it finishes.

EDIT:
Added here
https://github.com/oe-alliance/AutoB...fcfa37be753d24