Blindscan Plugin - Needs Additional Supported Chips by blindscan-s2 Added

[ilikenwf]

In my case, adding Si2169D to the list for my Zgemma...

_blindscans2Nims = ('TBS-5925', 'DVBS2BOX', 'M88DS3103', 'Si2169D', 'Si2169')

But the project should already have a good idea in a makefile somewhere that dictates which tuners support blindscan-s2 since it gets built for them, so why not add them to the above?

[WanWizard]

@Dima73 ?

[ilikenwf]

Though to be fair no matter what settings I use, I usually end up finding nothing with this method which is odd...but that is less relevant to the issue of any tuner supporting the use of blindscan-s2 should be added to that list.

[Dima73]

        if n.canBeCompatible("DVB-S") and n.description.startswith("Si216"):
            have_Support_Blindscan = True

[ilikenwf]

Yes but it doesn't actually run without being added to the above "supported" list. It worked on the older openatv build the device came with, though, for what it's worth.

It is an S2/S2X receiver, in case the reporting is wrong or the kernel driver has changed how it reports the name. I can check on that if you can tell me where the device name is listed, somewhere in /dev I assume? lsdvb also craps out after installing, it sees the tuners but gives me errors and some messages in non-english text.

I know that before adding it to that list, that I'd just get "It seems manufacturer does not support blind scan for this tuner." instead of it even running @Dima73

[Dima73]

cat /proc/bus/nim_sockets

[ilikenwf]

NIM Socket 0:
    Type: DVB-S2X
    Name: Si2169D
    Has_Outputs: no
    Frontend_Device: 0
    I2C_Device: 4
    Supports_Blind_Scan: yes
NIM Socket 1:
    Type: DVB-S2X
    Name: Si2169D
    Has_Outputs: no
    Frontend_Device: 1
    I2C_Device: 4
    Supports_Blind_Scan: yes
NIM Socket 2:
    Type: DVB-T2
    Name: Si2168
    Has_Outputs: yes
    Frontend_Device: 2
    I2C_Device: 3
    Supports_Blind_Scan: yes

So it does support it...but yeah without the mods I got the not supported message.

[ilikenwf]

@Dima73 https://github.com/oe-alliance/oe-alliance-plugins/commit/c5b785eb1ea102b95f6c1513821232706ce2bcbf

oe-alliance already did this at some point themselves.

[ilikenwf]

The only issue is that upon running it it looks for really off the wall frequencies like 4260V which isn't valid.

[Dima73]

@Dima73 oe-alliance/oe-alliance-plugins@c5b785e

oe-alliance already did this at some point themselves.

self.auto_scan = nimmanager.nim_slots[self.feid].supportsBlindScan() or tunername.startswith('Si216') https://github.com/OpenPLi/enigma2-plugins/blob/python3/blindscan/src/dmmBlindScan.py#L473 Isn't it the same?

[ilikenwf]

Not since without adding it to that list (and installing blindscan-s2) you get the message "It seems manufacturer does not support blind scan for this tuner."

I'm starting to think there's either something else up beyond this with the kernel driver for the turner or something because the stock OS on this device was OpenATV, and on it, blindscan was working...I don't really want to use OpenATV, though.

[Dima73]

Open plugin menu "Utility from the manufacturer"/"Hardware type" use "Hardware type"

[ilikenwf]

I have used both, neither work on any given satellite. I'm currently parked and locked on 99.2W both with C and Ku band and neither tuner (instead of diseqc I have each LNB on a separate tuner for now), nothing is found, and the frequencies that are investigated seem outlandish. It goes over 4200 for the TP freq which makes no sense for C.

I've tried both with stable and nightlies.

[ilikenwf]

[ilikenwf]

What the heck is 4260V? It shouldn't be possible...it doesn't really matter though since nothing is found. I know TP other than those in satellites.xml exist because my crappy handheld GTMedia sat finder can see them and their channels without an issue. I can also find them if I manually scan, but these don't get saved in lamedb because they're not in satellites.xml, I assume.

[ilikenwf]

I run into this with hardware scan for both the source version of the plugin which I currently run since I modified it to support option 1 as well as we've been discussing, but both the precompiled and the source version of the plugin result in nothing found.

I don't know what would be different between OpenATV and openpli here beyond the kernel, something with the blindscan-s2 program, or otherwise. I also noticed that dvbtraffic doesn't work for some reason either...

Sorry to dump all this here. I just find that OpenPLi is much superior and lightweight compared to all the others, and would like to avoid running those if at all possible.

[Dima73]

Are the scan results the same in openATV?

[ilikenwf]

Unfortunately not. I need to get multiboot functioning properly, I think it is still on one of the partitions, but I haven't gotten around to that yet.

[ilikenwf]

I'll have to try current and v6 since I think it shipped with v6 which is very ancient...I'll flash the current openATV to slot 2 and give it a try, just a moment.

[ilikenwf]

Current 7.3 image of OpenATV - finding TP's.

[ilikenwf]

...And this does appear to be using the hardware only scanner, not blindscan-s2. This is why I lean towards a potential difference in the kernel driver?

uname -a gives me this which isn't all that handy since I think it's the same kernel major/minorversion openpli uses.

Linux zgemmah7 4.10.12 #1 SMP Wed Apr 26 13:58:00 UTC 2017 armv7l GNU/Linux

[ilikenwf]

I guess their plugin script could be somehow different too.

[Dima73]

OpenATV / OpenPLi code dmmBlindScan.py are the same on 99%

[ilikenwf]

Yes; I think openATV just uses the OE alliance version?

I can try a copy of that version if you'd like; but my gut tells me it's a kernel driver or some config thing somewhere. The Linux side of the fence is where I'm super familiar, less on the DVB side.

[Dima73]

I would suggest opening a new topic on the openPli forum.