Enigma2 Blindscan Plugin Updated by Huevos

Huevos started updating the blindscan plugin a few days ago. He was nice enough to take some input and give us some things we really need in the blindscan plugin for North America. I will review what has changed and what is updated or added in this thread.

Older receivers had trouble with blindscan and the drivers for the tuners that control blindscan were poorly written. Any receiver after about 2014 usually had improved drivers except for Vu+ and maybe a few others. The Vu+ Duo2 needs some filtering of the blindscan data or you will get garbage, such as transponders with the same frequency and polarization but with different symbol rates.

A filter has been in the blindscan for a long time. This filter looks at the transponders in satellites.xml and makes corrections to the transponders found in blindscan. North America does not have a good satellites.xml as compared to most of Europe for many reasons. So the blindscan transponder filter has never worked as good in North America as it does in Europe.

We also use a Standard lnb with a 10750 l.o. while most of Europe would use the Universal lnb. When the blindscan plugin was originally built, it only worked for one type of lnb which was universal. Huevos added the C band lnb to the blindscan, and now has correctly added the 10750 lnb, Huevos also added Ka lnbs and other features to the blindscan plugin.

Please remember when you use these features who made them possible, and Thank Huevos for them. Correctly installing the 10750 lnb and adding other features took a considerable amount of time, and a lot of it was done for North America.

Disable sync with known transponders
[Only registered and activated users can see links. Click Here To Register...]

This feature will disable the blindscan filters and allow what the receiver actually finds to be scanned, including any errors. The OS Nino Pro seems to work fine with this filter disabled. The Vu+ Duo2 will return some garbage when this filter is disabled.
(Default = OFF)

User Defined LNB Settings
[Only registered and activated users can see links. Click Here To Register...]


Many different User Defined lnb settings may now be used. The math is automatic, and should work for most lnbs that have l.o.'s above 9750. Shown in the above screen grab is the universal lnb set for the 10600 l.o. This was done so I do not have a 4 step blindscan when only two steps is really needed.

10750 L.o. lnbs should also now use the User Defined setting instead of the old Circular setting.

Ka L.o.'s were also added to User Defined. I do not think we have any Ka satellites active at this time, but Europe does.

Error messages and other safeguards have been added in order to help keep the receiver working correctly.

Attached is a test plugin that works for the OpenVix (OE Alliance) Image. Feel free to test and report what you find. Be sure to ask questions on anything you are not sure about. For those that cannot install this plugin, a version of this plugin will be in OpenVix images soon.

Hey EB where are plugin stored?

Path to blindscan plugin is: /usr/lib/enigma2/python/Plugins/SystemPlugins/Blindscan

Backup the whole Image before installing anything like this. A Backup is not mandatory, but it is a good idea.

The OE Alliance blindscan plugin will not work in OpenPLi images. I am running this blindscan plugin in SatDreamGr which is part OpenPLi, but I had to make a few changes to get working.

Got the blind scan folder and box branding for the OEA core after adding the new plugin.py and reflashed Openpli 7.0rc, transfered files. Got it working on openpli. Thanks EB!

The 150mhz Off stop Freq. issue is fixed too. Fantastic Job Huevos! Thank you!

Set "Disable sync with known transponders" to Yes. See if you scan more transponders like that. I do not think the Zero 4K needs that filter.

Didn't see no difference on 91w picked up the same amount of channels. I'll keep testing. Thanks

Setting "Disable sync with known transponders" to yes caused it to scan a differnt frequency and I got duplicate channels. Say my known transponder was 11842 and the blind scan found 11843 you get the same channel on both frequencies so I think it is probably best to leave it set"no".

I am running it set to Yes on the Nino Pro without any issues. Thanks for testing it though.

The duplicates didn't appear in the service scan from the blind scan. You find the duplicates in your Satellite services with the zero 4k. Set to yes would be alright if you are just setting up the receiver and didn't have any channels saved in satellite services with the default known transponder. Just don't make a new blind scan and use no with disable sync with known transponders or you could get duplicates in the satellite services. 97w ku is the satellite I found the duplicates. A wok around would be to update the satellite .xml with the found frequencies from using yes during the blind scan,

Tell you the truth circular lnb setting is working. I forgot to set user defined 10750. when I scroll over to user defined from circular it was set 9750lofl,10600lofh so it was definitely using the circular lnb setting. found the same amount of channels using both settings. But I will leave it set to user defined 10750.

Are you clearing All Services before each blindscan?

No, not clearing. I am trying that now with (yes) desync known transponders. ok clearing messed up my favorites. Get a lot of <n/a> in my favorites list.
A rescan with clearing and NO fixed the favorites list.

That is because the transponders are being found on a slightly different frequency than the transponder that the favorites were made with.

Yes that's the issue. I like the desync feature but I think the satellite .xml will need to reflect the same frequency as the bindscan finds. I know how to edit the Satellite .xml file to make it custom. Only thing everyone would have to use thier own custom .xml file if they don't want to have the issue of selecting yes desync known transponders.

EB, you know what the (Yes) disable sync feature will work fine for me on 91W and 105W. I just wont use it on 103w or 97w where most favorites are. Then I shouldn't have any issues.

Save your settings before you scan, then reload settings when finished. That takes 2-3 minutes to restore everything the way it was, and cleans up any messes that were made.

I re done my fav's with the new frequencies and reflected them in my custom satellite .xml file so I should be good on 97w and 103w. Just can't use clear before scan on 103w because it will delete the Radio channels. Should not make much of a mess now.

Attached is SatDreamGr blindscan plugin. This version can also run in OpenPLi with some modifications. This is a nice one for my Vu+ Duo2.

Thanks EB, I like the satdreamgr blindscan better. Can open xml file with yellow button and look at found transponders.I don't know how to modify for openpli.

Quote:

---

Originally Posted by Megatron817 [Only registered and activated users can see links. Click Here To Register...]

Got the blind scan folder and box branding for the OEA core after adding the new plugin.py and reflashed Openpli 7.0rc, transfered files. Got it working on openpli. Thanks EB!

---

Hi Megatron,

What exactly did you do to modify to get it to work on OpenPLI?

I saved the blind scan plugin folder and box branding file from the OE-alliance then reflashed openpli and transfered files into openpli.

These Blindscan updates will be in OpenPli images within a few days at the most unless something major happens.

Quote:

---

Originally Posted by el bandido [Only registered and activated users can see links. Click Here To Register...]

Attached is SatDreamGr blindscan plugin. This version can also run in OpenPLi with some modifications. This is a nice one for my Vu+ Duo2.

---

Great! Looking forward to trying it out.

Did VU+ raise the supported symbol Rate? I can now enter 60 where before 45 was the limit. A blindscan using 1-60 worked with no issues actually worked better than ever on 91w be it not many wild feeds on there now.

Vu+ Never updated the blindscan much after it was released. Some tuners can got up to 60 so support is being added for those tuners.

Using the SDG:

[Only registered and activated users can see links. Click Here To Register...]

I am getting the following:

[Only registered and activated users can see links. Click Here To Register...]
and
[Only registered and activated users can see links. Click Here To Register...]

and after hitting the exit button button I get a green screen which reboots the receiver.

Is this sdg py only for v. 6 or will it work for v. 5?

Error in the coding it seems. Let me see what can be done about that.

Try this one ( Attached).
Note: File removed due to bad coding by me.

The Vu+ blindscan issue should be fixed in the next SatDreamGr online update. Please let me know if it is not fixed after next update. Until then, you may use the plugin in the post above. Thanks.

Satdreamgr-6 has the updated blindscan in the feeds but satdreamgr-5 no. Says no more updates for experimental 5 on thier web site.
I tried the updated plugin py with satdream-5 no go it crashed here too. The good news is for satdream-5 the old version works just as good if not better than satdream-6 and the updated plugin. Just my opinion but I found more with the old.

Quote:

---

Originally Posted by el bandido [Only registered and activated users can see links. Click Here To Register...]

Try this one ( Attached).

---

Thanks...

SDG v. 5 missing the blind scan in searching menu after installing the py file.

Updated to SDG v. 6 10-28-18 and installed the py and missing blind scan in search menu.

[Only registered and activated users can see links. Click Here To Register...]

Will go back to v. 5 even though there haven't been updates for a while now. Hopefully, they will correct the Duo2 version in the next few updates.

Missing a colon in Line#46. Try this one.

Note: Removed file due to coding issue.

Quote:

---

Originally Posted by el bandido [Only registered and activated users can see links. Click Here To Register...]

Missing a colon in Line#46. Try this one.

---

SDG 5, green screen.
SDG 6, scanned 87 ku new xpdrs only and everything went well. Then 97 ku, all xpdrs and it crashed. Line 1395 on green screen. Couldn't read the complete error fast enough.

Looks like v. 6 has a problem displaying the Pd1loi-HD-night skin correctly, so I guess the author should be notified.

[Only registered and activated users can see links. Click Here To Register...]

The PLi-HD-FullNight which is probably the original displays fine.

I've backed up v. 6 with backup suite and will try again as updates are made. Will return to v. 5 as everything seems to work, plus I like the skin.

The plugin in post#35 works on my Duo2. Hard to know what happened without the crash log or some other good clue. Telnet this: init 4 && enigma2 will output the crash in the terminal. Anyway, Might just be best for you to wait until the blindscan file is updated online, which will probably be tomorrow.

t2mi Is not defined in some images yet. That definition has been disabled in the attached plugin.
The attached plugin should run in SatDreanGr 5,6 using Duo2, And in OpenPli images.

(SatDreamGr 6 is the only image out of the above that has t2mi defined.)

I'll restore v. 6 tomorrow and give it a shot again. As long as v. 5 is working, I have no problem waiting for the bugs to be ironed out.

Done some more scanning with the updated plugin. The vix plugin I am using on openpli rc 7.0 finds channels on 91w ku as far as I can tell almost identical as the old plugin. The Satdreamgr-6 must have a different filter. I can find these transponders with openpli with the vix plugin 11823 v 3000 1 scrambled channel FAA-HD and another transponder at 11827 V 3000 with 2 Scambled channels ANG HD 48 and ANG-HD.They are right close together. Satdreamgr-6 finds 11827 but not 11823. I know it doesn't matter they are scrambled and you can't watch them anyway but for scanning testing purposes Just an observation in my Findings.