Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £99! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £149! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

[VU+ Ultimo4K] ABM scans after running DVB-T frequency finder.

But it is a hack, because:
  • We don't know the BBC mux will always be at a lower frequency.
  • We don't know the repeat interval of the BBC mux complies with the timeout.
But we do know that the highest frequency doesn't work (for me), and the chances of bbc mux's moving I would say are nil.
And if the bbc muxes become non-compliant, nothing will probably work without "hacks".
 
Last edited:
deleted (site keeps freezing on me).
 
If you want to use logic, you could check the timeout of each SDT.

Maybe the timeout could be added to the "list", and the sort you posted earlier could include that as well.
 
So this looks like a complicated way to do this, (not tested):
Code:
-sort_list = [(x[0], x[1]["signalQuality"]) for x in list(self.transponders_unique.items())]
+sort_list = [(x[0], (x[1]["signalQuality"], x[1]["frequency"])) for x in list(self.transponders_unique.items())]

I've given it a go, it appears to work as far as it goes, the problem being that all the signalqualities are the same so the list doesn't change.

The last system=0 entry in the list is still selected.

Is the signalquality now high to low in the list?

How does 'Com7 National' get included, it should be there, but has a different network name ??

Code:
13:02:01.7877 {'frequency': 482000000, 'tsid': 4175, 'onid': 9018, 'system': 0, 'bandwidth': 8, 'signalQuality': 65535, 'network_name': 'East Yorks & Lincs', 'custom_transponder_needed': False}
13:02:01.7878 {'frequency': 490000000, 'tsid': 20544, 'onid': 9018, 'system': 0, 'bandwidth': 8, 'signalQuality': 65535, 'network_name': 'East Yorks & Lincs', 'custom_transponder_needed': False}
13:02:01.7879 {'frequency': 506000000, 'tsid': 8219, 'onid': 9018, 'system': 0, 'bandwidth': 8, 'signalQuality': 65535, 'network_name': 'East Yorks & Lincs', 'custom_transponder_needed': False}
13:02:01.7880 {'frequency': 514000000, 'tsid': 24640, 'onid': 9018, 'system': 0, 'bandwidth': 8, 'signalQuality': 65535, 'network_name': 'East Yorks & Lincs', 'custom_transponder_needed': False}
13:02:01.7880 {'frequency': 530000000, 'tsid': 16521, 'onid': 9018, 'system': 1, 'bandwidth': 8, 'signalQuality': 65535, 'network_name': 'East Yorks & Lincs', 'custom_transponder_needed': True}
13:02:01.7881 {'frequency': 545833000, 'tsid': 12294, 'onid': 9018, 'system': 0, 'bandwidth': 8, 'signalQuality': 65535, 'network_name': 'East Yorks & Lincs', 'custom_transponder_needed': False}
13:02:01.7882 {'frequency': 562000000, 'tsid': 32769, 'onid': 9018, 'system': 0, 'bandwidth': 8, 'signalQuality': 65535, 'network_name': 'East Yorks & Lincs', 'custom_transponder_needed': False}
13:02:01.7883 {'frequency': 746000000, 'tsid': 40960, 'onid': 9018, 'system': 1, 'bandwidth': 8, 'signalQuality': 65535, 'network_name': 'Com7 National', 'custom_transponder_needed': True}
 
Last edited:
So you want the signal quality low to high and the frequency high to low?

Code:
sort_list = [(x[0], (x[1]["signalQuality"], -x[1]["frequency"])) for x in list(self.transponders_unique.items())]
 
So you want the signal quality low to high and the frequency high to low?

Code:
sort_list = [(x[0], (x[1]["signalQuality"], -x[1]["frequency"])) for x in list(self.transponders_unique.items())]

Yes, if you still pick the last system=0 entry in the list.

It's difficult for me to confirm it's working when all the signal qualities are the same, but that looks ok .

I'll have a go tomorrow,
 
But looking at the details of the muxes there are lots of examples where the BBC mux is not the lowest frequency.
 
But looking at the details of the muxes there are lots of examples where the BBC mux is not the lowest frequency.

It always gave may the itv sd mux before, and that works ok, so it's pot luck again.
 
Try this...
Code:
-signalQuality = self.frontend.readFrontendData(iFrontendInformation.signalQuality)
+signalQuality = self.frontend.readFrontendData(iFrontendInformation.snrValue)
https://github.com/oe-alliance/Auto...uetsMaker/src/scanner/frequencyfinder.py#L395

Can't see what I've done wrong, but I'm seeing the same signal quality of 65535 in the xml file.

Maybe something to do with this .....

Code:
https://github.com/OpenViX/enigma2/blob/f0a0eb0709c0357849702e4451d6fdff28c928a5/lib/dvb/frontend.cpp#L1377

I tried signalQualitydB, but they all ended up with 305419896
 
Last edited:
I managed to work out what's happening after a day+ getting nowhere fast.

It looks like Frequency finder uses the last tuner available (in my case tuner E, a TT3L10 ). This tuner always gives 100% SNR, unlike the BCM3466 which varies +- 50%.

So disabling tuner E forces a BCM3466 to be used, which creates this terrestrial_finder.xml...

Code:
<provider>
	<name>East Yorks & Lincs terrestrial</name>
	<streamtype>dvbt</streamtype>
	<protocol>lcn</protocol>
	<dvbtconfigs>
		<configuration key="custom" frequency="482000000" system="0">East Yorks & Lincs terrestrial</configuration>
	</dvbtconfigs>

	<customtransponders>
		<!-- customtransponder key="custom" frequency="482000000" transport_stream_id="104f" system="0"/ --><!-- original_network_id="233a" signalQuality="33694" channel="22" -->
		<!-- customtransponder key="custom" frequency="490000000" transport_stream_id="5040" system="0"/ --><!-- original_network_id="233a" signalQuality="32338" channel="23" -->
		<!-- customtransponder key="custom" frequency="506000000" transport_stream_id="201b" system="0"/ --><!-- original_network_id="233a" signalQuality="33355" channel="25" -->
		<!-- customtransponder key="custom" frequency="514000000" transport_stream_id="6040" system="0"/ --><!-- original_network_id="233a" signalQuality="32338" channel="26" -->
		<customtransponder key="custom" frequency="530000000" transport_stream_id="4089" system="1"/><!-- original_network_id="233a" signalQuality="32677" channel="28" -->
		<!-- customtransponder key="custom" frequency="545833000" transport_stream_id="3006" system="0"/ --><!-- original_network_id="233a" signalQuality="30959" channel="30" -->
		<!-- customtransponder key="custom" frequency="562000000" transport_stream_id="8001" system="0"/ --><!-- original_network_id="233a" signalQuality="30959" channel="32" -->
		<customtransponder key="custom" frequency="746000000" transport_stream_id="a000" system="1"/><!-- original_network_id="233a" signalQuality="26552" channel="55" -->
	</customtransponders>

	<sections>
		<section number="1">Entertainment</section>
		<section number="100">High Definition</section>
		<section number="201">Children</section>
		<section number="230">News</section>
		<section number="260">BBC Interactive</section>
		<section number="670">Adult</section>
		<section number="700">Radio</section>
	</sections>

	<swapchannels>
		<channel number="1" with="101"/>	<!-- BBC One HD -->
		<channel number="2" with="102"/>	<!-- BBC TWO HD -->
		<channel number="3" with="103"/>	<!-- ITV HD -->
		<channel number="4" with="104"/>	<!-- Channel 4 HD -->
		<channel number="5" with="105"/>	<!-- Channel 5 HD -->
		<channel number="9" with="106"/>	<!-- BBC FOUR HD -->
		<channel number="201" with="204"/>	<!-- CBBC HD -->
		<channel number="202" with="205"/>	<!-- CBeebies HD -->
		<channel number="231" with="107"/>	<!-- BBC NEWS HD -->
	</swapchannels>

	<servicehacks>
	<![CDATA[

tsidonidlist= [
	"104f:233a",
	"5040:233a",
	"201b:233a",
	"6040:233a",
	"4089:233a",
	"3006:233a",
	"8001:233a",
	"a000:233a",
]

tsidonidkey = "%x:%x" % (service["transport_stream_id"], service["original_network_id"])
if tsidonidkey not in tsidonidlist:
	add_audio_channels_to_video_bouquet=True

	skip = True

	]]>
	</servicehacks>
</provider>

The same thing happens on my ET10K, the last is tuner D a SundTek USB DVB-T2 tuner, which again give 100% SNR's.

(No python changes, just made sure the "right" tuner was used.)
 
Last edited:
Which mast is your aerial pointing to? Would be an idea to update the custom transponders in the ABM file while you investigate this issue?
 
Which mast is your aerial pointing to? Would be an idea to update the custom transponders in the ABM file while you investigate this issue?

Belmont transmitter, I'm pretty sure the custom transponder does actually work. :)
 
OK. Let us know if any changes are required.

Main scanning frequency:
<configuration key="belmont____________" frequency="506000000">Belmont</configuration>




Custom transponders:
<customtransponder key="belmont____________" frequency="482000000" transport_stream_id="104f" system="0"/>
<customtransponder key="belmont____________" frequency="490000000" transport_stream_id="5040" system="0"/>
<customtransponder key="belmont____________" frequency="506000000" transport_stream_id="201b" system="0"/>
<customtransponder key="belmont____________" frequency="514000000" transport_stream_id="6040" system="0"/>
<customtransponder key="belmont____________" frequency="530000000" transport_stream_id="4089" system="1"/>
<customtransponder key="belmont____________" frequency="546000000" transport_stream_id="3006" system="0"/>
<customtransponder key="belmont____________" frequency="562000000" transport_stream_id="8001" system="0"/>
<customtransponder key="belmont____________" frequency="746000000" transport_stream_id="a000" system="1"/>
 
... that looks fine, the only subtle difference is C30, which shows as C30- on ukfree.tv, with a frequency of 545833000, but I think 3 significant digits is all that's needed.
 
Which mast is your aerial pointing to? Would be an idea to update the custom transponders in the ABM file while you investigate this issue?

It was established some time ago that the frequency finder gave incorrect results with the terrestrial tuners fitted to the Xtrend 10K. The problem manifested itself as values of 65535 being seen and some signals from the "wrong" transmitter being identified (in my case I can see 3 transmitters) At the time is was put down to a problem with the supplied drivers and as a result no changes were made to the Enigma/OpenVix code. If this is still happening be very wary about coming to conclusions about problems with the py3 code which is actually a problem/bug in the tuner drivers.

The (heated) discussion about the problem with the tuners is in this thread posted in 2018 (page 3 ish)
https://www.world-of-satellite.com/...dd-HD-channels-regions-REVISTED-Bluebell-Hill
 
Last edited:
So remove the reverse. It doesn't serve any really useful purpose these days now the tuner selection logic works 100%.
https://github.com/oe-alliance/Auto...uetsMaker/src/scanner/frequencyfinder.py#L292

That now works fine on the Ultimo4k, tuner A was in use recording, and also on live tv, so might it have used tuner B ?

Also work fine on my ET10K, using tuner A (and seemed to run a lot faster), and picks the highest signal quality....

Code:
		<configuration key="custom" frequency="506000000" system="0">East Yorks & Lincs terrestrial</configuration>
	</dvbtconfigs>

	<customtransponders>
		<!-- customtransponder key="custom" frequency="482000000" transport_stream_id="104f" system="0"/ --><!-- original_network_id="233a" signalQuality="47237" channel="22" -->
		<!-- customtransponder key="custom" frequency="490000000" transport_stream_id="5040" system="0"/ --><!-- original_network_id="233a" signalQuality="43803" channel="23" -->
		<!-- customtransponder key="custom" frequency="[COLOR="#FF0000"]506000000[/COLOR]" transport_stream_id="201b" system="0"/ --><!-- original_network_id="233a" signalQuality="[COLOR="#FF0000"]48102[/COLOR]" channel="25" -->
		<!-- customtransponder key="custom" frequency="514000000" transport_stream_id="6040" system="0"/ --><!-- original_network_id="233a" signalQuality="45520" channel="26" -->
		<customtransponder key="custom" frequency="530000000" transport_stream_id="4089" system="1"/><!-- original_network_id="233a" signalQuality="48102" channel="28" -->
		<!-- customtransponder key="custom" frequency="545833000" transport_stream_id="3006" system="0"/ --><!-- original_network_id="233a" signalQuality="45520" channel="30" -->
		<!-- customtransponder key="custom" frequency="562000000" transport_stream_id="8001" system="0"/ --><!-- original_network_id="233a" signalQuality="28337" channel="32" -->
		<customtransponder key="custom" frequency="746000000" transport_stream_id="a000" system="1"/><!-- original_network_id="233a" signalQuality="40369" channel="55" -->
	</customtransponders>
 
... that looks fine, the only subtle difference is C30, which shows as C30- on ukfree.tv, with a frequency of 545833000, but I think 3 significant digits is all that's needed.

Frequency is in MHz.

Code:
((474 + (bandwidth * (channel - 21))) * 1000000)

Where bandwidth is 8, and channel is between 21 and 69... which is probably outside the current range of the British terrestrial TV band.
 

OpenViX Feeds Status

Back
Top