PDA

View Full Version : Blind Scanning .... Does it work..?



DrProzac
09-08-17, 21:44
Can anyone confirm if Blind Scanning works on this box.

I've tried a few different times on different SATS and run the Blind Scan, and I always get the same Error message at the end saying No transponders were found with those parameters?

I'm not sure if I'm doing something wrong, or if it just doesn't work?

Looking at the Original Guide on Vix Manual, is says about having the option to put in a Start and End Frequency, as well as all the rest of the Parameters, I can only seem to have the options of

H V etc, and Symbol rate.

So I'm not sure if this is no longer supported or maintained?

Huevos
09-08-17, 22:15
What image are you using?

DrProzac
09-08-17, 23:05
Sorry forgot that part,...
Brand & Model: Edision OS mega
Chipset (Frontprocessor Version): BCM73565 (7)
Main Memory: 430168 kB free / 584636 kB total
Box Uptime: 2d 2:49
Software
System OE: OE-Alliance 4.0
Firmware version: OpenViX 5.0.024 (2017-08-04)
Kernel / Drivers: 4.11.0 / 20170723


I just seem to get the same results all the time when I try.
I'm sure it something I'm doing wrong.

Huevos
10-08-17, 12:36
Post a screen grab of how you have the plugin configured.

DrProzac
10-08-17, 13:07
I'm just using the Built in BLIND Scan Access from Main menu

54548

MENU
Setup
Tuner Config
Blind Scan

And these are the Parameters I was doing a test On

54547

If your saying Plugin maybe I'm in the wrong place then?

Huevos
10-08-17, 13:26
Looks like something is broken in the plugin. I check it out later.

And, yes, it is a plugin.

DrProzac
10-08-17, 13:33
This is what I get when the scan is in Progress.

54549

So is that the correct place I was in, or should it appear under the Plugins section?
I've only been back to using an E2 Box for a few months, and never have had it working so far (ie the last few updates) I couldn't get it to work either..

Andy_Hazza
10-08-17, 14:22
Like Huevos says, you would need to install the plugin. He will advise I'm sure as this is his area.


Sent from my iPhone using Tapatalk

cactikid
10-08-17, 14:29
with your photos above you are scanning 28.2??

the error is on a different sat?

i presume a motorised or multi lnbs in use and not just a fixed dish at 28.2?

DrProzac
10-08-17, 14:42
with your photos above you are scanning 28.2??

the error is on a different sat?



Yes sorry that probably confused things.
Initial Screen shots were on 28.2E

The Blind Scan I actually run was on 7E.

I still get the same Error regardless of what sat I scan on.

Tuner A is Motor
Tuner B is Fixed on 28.2E

DrProzac
10-08-17, 14:50
For Completeness.

5455054551

This is on Tuner A

el bandido
10-08-17, 16:30
DVB-S/S2 Blindscan has been broken in Broadcom Tuner A of the OS Mini for a long time. Could blindscan in the OS Mega tuner be broken too?

Just as a reminder, blindscan only supports 3 lnb types, or these l.o. frequencies.
Universal (9750/10600)
Circular (10750)
C band (5150)
I doubt blindscan would work correctly with Unicable, or other lnb types besides these three.

DrProzac
11-08-17, 08:18
Maybe I've miss understood.

I thought with my set-up and Blindscan working, I could just do a Blind Scan on either 28.2E and find any missing transponders, the same with 7E 9E and 10E for feeds?

Have I missed something?

Huevos
11-08-17, 15:51
DVB-S/S2 Blindscan has been broken in Broadcom Tuner A of the OS Mini for a long time. Could blindscan in the OS Mega tuner be broken too?

Just as a reminder, blindscan only supports 3 lnb types, or these l.o. frequencies.
Universal (9750/10600)
Circular (10750)
C band (5150)
I doubt blindscan would work correctly with Unicable, or other lnb types besides these three.Where is that reported?

Huevos
11-08-17, 15:54
I don't understand why the box is not showing start and stop frequencies. On Vu Solo4k...

54563

cactikid
11-08-17, 16:20
changing sats does your motor move dish as if dish is off and is there a signal finder on box to check what signal and/lock ?
kingofsats could give you a channel frequency to check, i remember in trying usals for motorised years ago.

Huevos
11-08-17, 16:22
Screenshot of the tuner config on each satellite/tuner combo you are scanning.

DrProzac
11-08-17, 18:17
Attached Screenshots.


5456654567
I still however can't find a BlindScan Pluging to download.

Huevos
11-08-17, 18:24
You already have it loaded.

DrProzac
11-08-17, 18:28
changing sats does your motor move dish as if dish is off and is there a signal finder on box to check what signal and/lock ?
kingofsats could give you a channel frequency to check, i remember in trying usals for motorised years ago.

When I change channel to a Different SAT I get the following Displayed.

Yes the motor moves fine.

54568

I;m not sure if that is what you meant though??
Do you mean from Normal Scanning (Signal Finder)

Or Do you mean if I select another SAT and Frequency Here does the motor say it's moving?
54569

If it's the later No. I don't get the Motor Icon up.

It just waits a while and then shows the New SAT and New Frequecy

54570

DrProzac
11-08-17, 18:30
You already have it loaded.


Is it the Skin I'm using possibly missing some of the Fields?

DrProzac
11-08-17, 18:34
Just tried Vix-Night-HD didn't make a Difference.
Noticed as soon as I go into Blind Scan

As Soon as I hit the Option the Mini TV Goes off. [BLACK SCREEN]
(Although when I do a Web-IF) Screen shot it still shows so not sure that's relevent.


On your Examples it looks like you still have a Live Picture?

Huevos
11-08-17, 19:14
@ElBandito, this is the commit that breaks the plugin.
https://github.com/oe-alliance/oe-alliance-plugins/commit/f71be2e470acfc6de2ee6783a68c84cfb00a7084

I'm going to revert it. It needs to work properly for all users.

DrProzac
11-08-17, 19:24
@ElBandito, this is the commit that breaks the plugin.
https://github.com/oe-alliance/oe-alliance-plugins/commit/f71be2e470acfc6de2ee6783a68c84cfb00a7084

I'm going to revert it. It needs to work properly for all users.

Your comment on GITHUB, says about For users

It breaks the plugin for every user that is using "Configuration Mode" == "Simple". Other errors too.

Does that mean if I change the way my Tuner is set-up it should work?
Or is the other Error's going to stop it working as well?

Are you able to BlindScan without issues?

DrProzac
11-08-17, 19:39
Just read the code a bit more.

So I've changed to Config Type Advanced (on TunerB) and set up as SIngle SAT.
Just trying a Blind Scan on there now.
With Limited Parameters.

At least It's now showing the Frequency and not missing them

DrProzac
11-08-17, 19:55
Parameters Used.

54575

Active Scan Going.

54576

This is how the TUNER B is now set-up

54577

Is there anything else I should changed.

Also how would I set-up TUNER A for the USALS Motor?
Would something like this work (with Correct LAT and LON)

54578

Huevos
12-08-17, 02:50
Plugin works fine for me now and finds channels. If it doesn't find anything for you I suggest it is a drivers problem.

DrProzac
12-08-17, 08:06
So did you do an update?

If so how do I get the new update?

Or do I just need to change my Tuners to use Advanced rather than simple?
And did my Config look ok for TUNER B

Huevos
12-08-17, 17:24
Yes I did an update. Get the latest file from here:
https://raw.githubusercontent.com/oe-alliance/oe-alliance-plugins/0f7944f2e10115d03f69f2710bfec759ed282569/Blindscan/src/plugin.py

But if the drivers are screwed on your STB like it says elsewhere in this thread, the changes to the .py file won't make any difference.

DrProzac
12-08-17, 19:53
Bit beyond me that...

No Idea how to do a Manual update, I thought I might just be able to copy the file into the Correct Directory, but it looks like it's compiled on the Box already in

/usr/bin/blindscan

Oh well... thanks for all your help though

Huevos
12-08-17, 20:10
You just copy the plugin.py file to...
/usr/lib/enigma2/python/Plugins/SystemPlugins/Blindscan

Restart the box, then delete the file.

DrProzac
12-08-17, 20:14
Thanks again.

I was looking in the wrong Directory then anyway! :)

Huevos
12-08-17, 20:18
it looks like it's compiled on the Box already in

/usr/bin/blindscanThat is the closed source binary. That is the bit that communicates between the plugin and the tuner.

DrProzac
12-08-17, 20:31
Well Just doing a Scan on 28.2E
On the 1st Screen I had the Option to select a Start and End Frequency, but on the next screen when it starts scanning they are different (not the full range selected)

I'm guessing that it's not going to work?

54589

I'm guessing it's not working as the Mini TV bit is still showing a Live Picture.
If this was scanning the Live TV bit would be Blank

Unless it's using the 2nd Tuner?

Huevos
12-08-17, 20:47
What is not going to work? The info screen shows what it is currently scanning... and it is using the tuner you selected. If it doesn't return a proper result it is because the driver supplied by the manufacturer is broken.

DrProzac
12-08-17, 20:49
What is not going to work? The info screen shows what it is currently scanning... and it is using the tuner you selected. If it doesn't return a proper result it is because the driver supplied by the manufacturer is broken.

What I meant was, I have an Active scan going on 28.2E.
On the mini TV next to where the scan is going, it still showing Live TV (BBC ONE HD)
If it's still showing the live TV Picture, it can't be scanning can it?

5459054591

Huevos
12-08-17, 21:25
Which tuner are you scanning?

DrProzac
12-08-17, 21:32
Was scanning Tuner A (motor.)
When scanning should it start building a list of Transponders it's found, or does it just do that at the end?

It's finished now but not Transponders Found.

54592

Going to Try on Fixed Tuner Now (now Tuner C)

Huevos
12-08-17, 21:44
Yes it does build a list but it is not displayed. The found transponders are listed in the xml file in the /tmp folder. But if you get a message, "no transponders found" it won't find channels. If so test again using the other tuner.

Switch on debug logs and post the logs here.

DrProzac
12-08-17, 21:49
Well Tuner C run through very Quickly.

54593

SO that looks like it worked?
So Maybe I'll need to Make Tuner C the Motor Cable, and Scan that way.

Huevos
12-08-17, 22:06
What about tuner A?

DrProzac
12-08-17, 22:07
Right.

Trying Again on Tuner A on 7E this time.
I think when I scanned on 28.2E on tuner A dish was still on 13E and Live picture was from fixed Tuner.


Now I've moved dish to 7E on working channel.
Started the Scan
Live Picture has stopped

So Looks like it is scanning now, but it's no where near as fast as when it done a scan on 28.2E

DrProzac
12-08-17, 22:24
Here are the Params Used.
54594
Forgot to Switch on Debug Logs.
So starting again.


Here is the Scan in progress.
(notice the Frequency range isn't the same again)

54595

DrProzac
12-08-17, 22:49
On 2/4
The Frequency now seems to have the full range selected.

54596

Perhaps I've never paid that much attention to it, I'm sure it never done the HiBand before.

Huevos
12-08-17, 23:28
Ok, just so you know how it works...
Select the tuner, then the satellite, then if it is a motorised dish give the dish time to orientate itself towards the satellite before starting the scan, otherwise the scan will start before the dish reaches the satellite.

DrProzac
12-08-17, 23:35
Yet, got that part.

It's failed however.

Looking at the DEBUG Log (if you want the whole lot?)


< 4373.496> [Blindscan][doClock] self.is_runable False
< 4374.496> [Blindscan][doClock] started
< 4374.496> [Blindscan][doClock] self.is_runable False
< 4375.496> [Blindscan][doClock] started
< 4375.496> [Blindscan][doClock] self.is_runable False
< 4376.496> [Blindscan][doClock] started
< 4376.496> [Blindscan][doClock] self.is_runable False
< 4377.496> [Blindscan][doClock] started
< 4377.496> [Blindscan][doClock] self.is_runable False
< 4378.496> [Blindscan][doClock] started
< 4378.496> [Blindscan][doClock] self.is_runable False
< 4379.432> [Blindscan][blindscanContainerClose] cnt: 0 , data: []
< 4381.459> [Skin] processing screen MessageBox:
< 4381.463> [Skin] Skin error in screen 'MessageBox' widget 'widget': [Skin] {Magic-FHD/skin.xml}: [Skin] source 'menu_path_compressed' was not found in screen 'MessageBox'!. Please contact the skin's author!
< 4381.493> [Skin] processing screen MessageBox_summary:
< 4381.505> [Blindscan][doClock] started
< 4381.509> [Blindscan][doClock] self.is_runable True
< 4381.510> [Blindscan][doClock] Done
< 4381.526> [Task] job Components.Task.Job name=SoftcamCheck #tasks=1 completed with [] in None
< 4381.857> [eConsoleAppContainer] Starting /usr/bin/grab
< 4384.453> [eDVBFrontend] close frontend 0
< 4412.512> [eConsoleAppContainer] Starting /usr/bin/grab
< 4440.497> [MessageBox] Timeout!
< 4443.953> [eConsoleAppContainer] Starting /usr/bin/grab
< 4474.869> [eConsoleAppContainer] Starting /usr/bin/grab

DrProzac
12-08-17, 23:40
Here is a snip of the Start.



< 161.493> [ActionMap] ColorActions green
< 161.493> [Blindscan][keyGo] started
< 161.494> [Blindscan][doRun] started
< 161.494> [Blindscan][doRun] add scan item: (70, '7.0E Eutelsat 7A/7B', 0) , vertical , low
< 161.495> [Blindscan][doRun] add scan item: (70, '7.0E Eutelsat 7A/7B', 0) , vertical , high
< 161.495> [Blindscan][doRun] add scan item: (70, '7.0E Eutelsat 7A/7B', 0) , horizontal , low
< 161.496> [Blindscan][doRun] add scan item: (70, '7.0E Eutelsat 7A/7B', 0) , horizontal , high
< 162.496> [Blindscan][doClock] started
< 162.496> [Blindscan][doClock] self.is_runable True
< 162.496> [Blindscan][doClock] running status-[1]: [70][vertical][low]
< 162.497> [Blindscan][prepareScanData] started
< 162.508> [Blindscan] self.frontend: <enigma.iDVBFrontendPtr; proxy of <Swig Object of type 'ePtr< iDVBFrontend > *' at 0x6ee554a0
< 162.509> [TuneTest] tuning to transponder with data (11015, 0, 1, 0, 0, 70, 0, 0, 0, 0)
< 162.509> [eDVBFrontend] (0)tune
< 162.509> [eDVBSatelliteEquipmentControl] Entry for 7,0? not in Rotor Table found... i try gotoXX?
< 162.509> [eDVBSatelliteEquipmentControl] siteLatitude = (REMOVOVED BY ME), siteLongitude = (REMOVED BY ME), 7.000000 degrees
< 162.509> [eDVBSatelliteEquipmentControl] PolarmountHourAngle=173.111718
< 162.509> [eDVBSatelliteEquipmentControl] RotorCmd = e06e
< 162.509> [eDVBSatelliteEquipmentControl] RotorCmd e06e, lastRotorCmd e06e
< 162.509> [eDVBFrontend] prepare_sat System 0 Freq 11015000 Pol 1 SR 0 INV 0 FEC 0 orbpos 70 system 0 modulation 0 pilot 0, rollof
< 162.509> [eDVBFrontend] tuning to 1265 mhz
< 162.509> [eDVBChannel] OURSTATE: tuning
< 162.510> [Blindscan][prepareScanData] prepared command: [blindscan --start=950 --stop=1950 --min=2 --max=45 --slot=0 --i2c=2 --ve
< 162.510> [eConsoleAppContainer] Starting /bin/sh
< 162.529> [Skin] processing screen MessageBox:
< 162.532> [Skin] Skin error in screen 'MessageBox' widget 'widget': [Skin] {Magic-FHD/skin.xml}: [Skin] source 'menu_path_compress
< 162.574> [Skin] processing screen MessageBox_summary:
< 162.583> [eDVBFrontend] setVoltage 1
< 162.583> [eDVBFrontend] sleep 10ms
< 162.593> [eDVBFrontend] set sequence pos 3
< 162.593> [eDVBFrontend] update current switch params
< 162.593> [eDVBFrontend] startTuneTimeout 20000
< 162.593> [eDVBFrontend] setFrontend 1
< 162.593> [eDVBFrontend] setting frontend 0
< 162.593> [eDVBFrontend] (0)fe event: status 0, inversion off, m_tuning 1
< 162.593> [eDVBFrontend] sleep 500ms
< 163.174> [eConsoleAppContainer] Starting /usr/bin/grab
< 163.496> [Blindscan][doClock] started
< 163.497> [Blindscan][doClock] self.is_runable False
< 164.496> [Blindscan][doClock] started
54598

DrProzac
13-08-17, 00:47
Just for Isolating the Problem.

I've now moved the Motor onto Tuner C.
Fixed onto Tuner A.

Doing a Blind Scan again on 10E this time on Tuner C to see if I get anything.

This will then isolate if it's the Tuner Type (as suspected) or my config on the Tuner.

After Blind Scanning on 10E it then started a Channel Scan.
So it looks like it is the type of Tuner on Tuner A and Tuner B


Tuner A, slotdescription = Broadcom BCM73XX, multitype = 0
Tuner B, slotdescription = Broadcom BCM73XX, multitype = 0
Tuner C, slotdescription = FTM-4862 (Availink AVL6862), multitype = False

So looks like it is a driver issue?

I'll try a Test on Tuner A (Fixed on 28.2) and see if that fails next as well, but I'm guessing it will.

DrProzac
13-08-17, 01:51
DVB-S/S2 Blindscan has been broken in Broadcom Tuner A of the OS Mini for a long time. Could blindscan in the OS Mega tuner be broken too?



From my very very Basic testing I would say Yes, as I can only seem to get a success on Tuner C

< 32.783> [NimManager] slotname = Tuner A, slotdescription = Broadcom BCM73XX, multitype = 0
< 32.783> [NimManager] slotname = Tuner B, slotdescription = Broadcom BCM73XX, multitype = 0
< 32.783> [NimManager] slotname = Tuner C, slotdescription = FTM-4862 (Availink AVL6862), multitype = False

el bandido
13-08-17, 05:22
It would be nice if the blindscan could be fixed in the Broadcom BCM73XX tuner.

I took a bit of time and made a video of the OS Mini blindscanning using the Simple mode instead of Advanced. I expect to start a separate thread so some of these issues can be corrected. Video is in the link below.



https://mega.nz/#!309WRBrD!55m8RlGpHzyZ13djiGlM7_y7ySzFBvZVepdoANF USb0

cristo4
03-09-17, 19:20
Maybe a little bit offtopic, but i am very interested in BCM 73xx tuner sensitivity. Has anyone tested against BCM4505 tuner? How does it work with weak signals? It locks the signal, or does it need bigger sat dish?