108 replies to this topic

[Abu Baniaz]

I am using a solo 4k with OpenPLi.

On some cable systems, the frequencies are not whole MHz. Please see below for the frequencies in my area. There is the theory that the rounding/centering will function. However, in real life this does not work.
It is therefore not possible to correctly view/select the exact frequency to scan. If the xml file has the exact/complete frequencies, you can find channels. The frequency displayed during the scan GUI rounded and not exact. At the scanning stage, the exact figure is shown.

If I scan 370000 (GUI shows this as 370), it does not find channels
If I scan 371000 (GUI shows this as 371), it does not find channels
If the xml file has 370750 (GUI shows this as 370)channels are found.

Although I have mentioned the Solo 4K, issue is not limited to it. My other DVB-C capable receivers are not supported by OpenPLI. But they exhibit the same issue when using based on open PLI images. There are regions with xxx250 and xxx500 frequencies. They also have the same problem with rounding not working.

 

t:ffff0000:0023:f020,c:114750:6952000:2:5:3:0:0
t:ffff0000:0026:f020,c:122750:6952000:2:5:3:0:0
t:ffff0000:0002:f020,c:338750:6952000:2:5:3:0:0
t:ffff0000:0003:f020,c:346750:6952000:2:5:3:0:0
t:ffff0000:0004:f020,c:354750:6952000:2:5:3:0:0
t:ffff0000:0005:f020,c:362750:6952000:2:5:3:0:0
t:ffff0000:0006:f020,c:370750:6952000:2:5:3:0:0
t:ffff0000:0007:f020,c:378750:6952000:2:5:3:0:0
t:ffff0000:0008:f020,c:386750:6952000:2:5:3:0:0
t:ffff0000:0009:f020,c:394750:6952000:2:5:3:0:0
t:ffff0000:001e:f020,c:402750:6952000:2:5:3:0:0
t:ffff0000:0065:f020,c:410750:6952000:2:5:3:0:0
t:ffff0000:0066:f020,c:418750:6952000:2:5:3:0:0
t:ffff0000:002b:f020,c:426750:6952000:2:5:3:0:0
t:ffff0000:002c:f020,c:434750:6952000:2:5:3:0:0
t:ffff0000:001f:f020,c:474750:6952000:2:5:3:0:0
t:ffff0000:0025:f020,c:482750:6952000:2:5:3:0:0
t:ffff0000:0027:f020,c:490750:6952000:2:5:3:0:0
t:ffff0000:000e:f020,c:506750:6952000:2:5:3:0:0
t:ffff0000:000f:f020,c:514750:6952000:2:5:3:0:0
t:ffff0000:0010:f020,c:522750:6952000:2:5:3:0:0
t:ffff0000:0011:f020,c:530750:6952000:2:5:3:0:0
t:ffff0000:0022:f020,c:538750:6952000:2:5:3:0:0
t:ffff0000:0020:f020,c:546750:6952000:2:5:3:0:0
t:ffff0000:001a:f020,c:554750:6952000:2:5:3:0:0
t:ffff0000:001b:f020,c:562750:6952000:2:5:3:0:0
t:ffff0000:001c:f020,c:570750:6952000:2:5:3:0:0
t:ffff0000:001d:f020,c:578750:6952000:2:5:3:0:0
t:ffff0000:000a:f020,c:594750:6952000:2:5:3:0:0
t:ffff0000:000b:f020,c:602750:6952000:2:5:3:0:0
t:ffff0000:000c:f020,c:610750:6952000:2:5:3:0:0
t:ffff0000:000d:f020,c:618750:6952000:2:5:3:0:0
t:ffff0000:0021:f020,c:626750:6952000:2:5:3:0:0
t:ffff0000:0024:f020,c:634750:6952000:2:5:3:0:0
t:ffff0000:0028:f020,c:642750:6952000:2:5:3:0:0
t:ffff0000:0029:f020,c:650750:6952000:2:5:3:0:0
t:ffff0000:0068:f020,c:658750:6952000:2:3:3:0:0
t:ffff0000:0001:f020,c:666750:6952000:2:3:3:0:0
t:ffff0000:002a:f020,c:674750:6952000:2:3:3:0:0
t:ffff0000:002d:f020,c:682750:6952000:2:3:3:0:0
t:ffff0000:0012:f020,c:690750:6952000:2:5:3:0:0
t:ffff0000:0013:f020,c:698750:6952000:2:5:3:0:0
t:ffff0000:0014:f020,c:706750:6952000:2:5:3:0:0
t:ffff0000:0015:f020,c:714750:6952000:2:5:3:0:0
t:ffff0000:0016:f020,c:722750:6952000:2:5:3:0:0
t:ffff0000:0017:f020,c:730750:6952000:2:5:3:0:0
t:ffff0000:0018:f020,c:738750:6952000:2:5:3:0:0
t:ffff0000:0019:f020,c:746750:6952000:2:5:3:0:0

I am attaching screenshots, one of which shows the exact frequency shown in service information. What scan GUI shows, what frequency "service scan" actually scans.

The cable scan plugin also has the same issue/problem of not being able to enter incomplete MHz frequencies

In summary, is it possible to modify the GUI to allow for the kHz to be specified when scanning DVB-C.

Thanks in advance

Attached Files

•  pli proper.jpg   47.33KB   10 downloads
•  pli scan.jpg   49.84KB   10 downloads
•  pli scan xml gui.jpg   50.42KB   10 downloads
•  pli scan xml scan1.jpg   31.2KB   10 downloads
•  pli scan xml scan2.jpg   47.32KB   10 downloads

[Dimitrij]

Simple

-		self.scan_cab.frequency = ConfigInteger(default = defaultCab["frequency"], limits = (50, 999))
+		self.scan_cab.frequency = ConfigInteger(default = defaultCab["frequency"], limits = (50000, 999000))

+

has changed three lines  Satfinder/ScanSetup.py

self.scan_cab.frequency.value*1000 --> self.scan_cab.frequency.value

Edited by Dimitrij, 26 September 2016 - 08:18.

[Abu Baniaz]

Many thanks. I can enter the 6 digit value.

Notes:
I could only find two instances of "self.scan_cab.frequency.value*1000"
Lines 1287 and 1486.

When I enter the manual scan menu, it loads up as 3 digits.Is it possible to populate the 6 digits?

Predefined transponder still has the 3 digit entry.

Attached Files

•  ScanSetup.py   75KB   1 downloads
•  6 digits.jpg   51.59KB   7 downloads
•  predefined.jpg   55.45KB   7 downloads

[Dimitrij]

Abu Baniaz

Using a custom cable.xml in /etc/enigma is not solving his issue?

[Abu Baniaz]

Hi,
I have the cables.xml file in etc/enigma2. Still autofilling 3 digits.

Attached Files

•  cables.xml   4.2KB   8 downloads

[Abu Baniaz]

Here is a debug log if it helps.

Attached Files

•  puttylog-20160926-194613.txt   17.31KB   5 downloads

[Dimitrij]

Add need frequencies in /etc/enigma2/cable.xml and start scan.

Channels are found?

Edited by Dimitrij, 26 September 2016 - 20:35.

[Abu Baniaz]

cable or cables ? I'm using cables.xml

If frequencies are in xml, it has always worked and found channels. Problem is just how the GUI represents/allows you to select what is available. It is showing MHz, should have decimal points, otherwise be in kHz.

Sent from my HTC One M9PLUS using Forum Fiend v1.3.3.

[Abu Baniaz]

Here is a video to explain things better. Hopefully you can see:

08 seconds: Service details. Value is 6 digits and in kHz. No changes made to this.
23 seconds: The pre-defined frequency (using my xml file) is shown as "370 MHz 3/4 6952 256QAM".
Entry in xml is <transponder frequency="370750" symbol_rate="6952000" fec_inner="3" modulation="5"/>

28 seconds: The scan is actually carried out on "370750/6952/3/4". This is only possible because my xml file has the 370750 entry

60 seconds: I select 370750. (This is only possible because of the changes you suggested. You could not do this before.)
65 seconds: The scan is carried out on "370750/6952/3/4".

Just to emphasise the last change you suggested is good, we just need to improve things. Mismatch of MHz in some places and kHz in others. The kHz one is better and allows for accurate selection

Attached Files

•  pli scan.zip   5.87MB   5 downloads

[Dimitrij]

Maybe this:

 

Not changed Satfinder/ScanSetup.py

Use custom /etc/enigma2/cables.xml

 

and all

Edited by Dimitrij, 27 September 2016 - 05:45.

[Abu Baniaz]

That did work and still works with your changes. Problem is you cannot see the .750

370750 is shown as 370 MHz. 370000 is also shown as 370 MHz. So unless you inspect the file, you don't know see what you will be scanning.

Sent from my HTC One M9PLUS using Forum Fiend v1.3.3.

[littlesat]

Please offer us a patch....

[Dimitrij]

	def humanReadableCabTransponder(self, tp):
		if tp[3] in range (6) and (tp[4] in range (10) or tp[4] == 15):
			mod_list = ['Auto', '16-QAM','32-QAM','64-QAM','128-QAM', '256-QAM']
			fec_list = {0:"Auto", 1:'1/2', 2:'2/3', 3:'3/4', 4:'5/6', 5:'7/8', 6:'8/9', 7:'3/5', 8:'4/5', 9:'9/10', 15:'None'}
			print str(tp[1]/1000) + " MHz " + fec_list[tp[4]] + " " + str(tp[2]/1000) + " " + mod_list[tp[3]]
-			return str(tp[1]/1000) + " MHz " + fec_list[tp[4]] + " " + str(tp[2]/1000) + " " + mod_list[tp[3]]
+			return str(tp[1]) + " kHz " + fec_list[tp[4]] + " " + str(tp[2]/1000) + " " + mod_list[tp[3]]
		return _("Invalid transponder data")

[Abu Baniaz]

Many thanks. That is working fine.
 working2.jpg   48.91KB   0 downloads

Query:
If I am on a channel on frequency 370750. I then go to perform a manual scan, select user defined transponder. Should it autoload 370750? It currently loads up as 000370
 userdefinedneedtweak.jpg   54.71KB   0 downloads

Thanks again for your continued assistance.

[Dimitrij]

defaultCab["frequency"] = frontendData.get("frequency", 0)

[Abu Baniaz]

I also changed line 1012. This got rid of the extra 0 in the symbol rate.

self.scan_cab.symbolrate = ConfigInteger(default = defaultCab["symbolrate"], limits = (1, 9999))

Much appreciated.

Attached Files

•  working 3.jpg   52.83KB   3 downloads
•  working 4.jpg   52.48KB   2 downloads
•  ScanSetup.py   74.99KB   0 downloads

Edited by Abu Baniaz, 27 September 2016 - 18:00.

[Abu Baniaz]

With regards to to commit on Github

Predefined transponder:
Values after decimal point are shown.

User defined transponder:
There are only 3 digits with no decimal point. You cannot enter the kKz values.

[Huevos]

[ScanSetup/Transponder/Satfinder] DVB-C, frequency entry should be in kHz, because MHz is too course for some scans. i.e. when frequency is 474.50 MHz scan fails because the closest available user value possible to enter via the GUI is 474 MHz. Also, DVB-T and DVB-C, display frequency as a float (MHz).

https://github.com/O...e08e40ed63ff9e4

[littlesat]

I'm afraid it might be better that they change the tuners config in the drivers so they catch-up within 1 MHz... But we cannot change th drivers
But could you also offer a commit request to us?

Edited by littlesat, 9 October 2016 - 08:07.

[Erik Slagter]

I already discussed this with dimitrij as well. Why not just recognise a decimal point in the input? Input remains in MHz (as usual), but users that need more fine grained control, can add a decimal point and specify hundreds (+ tens and units if required) of kHz.