E2 on a new Atemio Nemsis

[Pixl]

My other thread on the Atemio Nemsis was getting rather long. Thought I'd start a new one here since the issues seem to be more of the E2 beast rather than the receiver it's loaded on.

I've done well at getting my tuner lnb1 set up for C band. I wanted to add a second dish which is Ku, port #4 on my diseqc 1.1 switch, so I set up LNB2, but can't get it to work. Here is a screen shot of the setup. I question my selections for LOF/L, LOF/H, and threshold what ever that is.

[Only registered and activated users can see links] ([Only registered and activated users can see links])

[chewie]

Is it in the same tuner as your C-band is? if it is, try another tuner.
Chewie

[eastof111]

Also, looking at your signature, you show the ku as being a universal vs. your menu setup is showing a standard linear lnb.

[el bandido]

Why are you using LNB2 instead of LNB1?

[Pixl]

Is it in the same tuner as your C-band is? if it is, try another tuner.
Chewie

Yes, same tuner, has 8 port switch downline to feed 3 different dishes with one coax.

[Pixl]

Also, looking at your signature, you show the ku as being a universal vs. your menu setup is showing a standard linear lnb.

East, this is not the main Ku dish listed in my signature, but is a fixed 1.2m dish for 103w weird skew. Uses a standard lnbf with 10750 LO.

[eastof111]

Pixl, then the settings seem to be correct for that lnb. Again, back to the basics of running a straight cable until you get a scan then adding the switch and scanning again etc. Sometimes posting a hand drawn diagram, helps alleviate the guessing of how the system is connected.

On mine. I prefer to separate C and Ku on two tuners... makes life easier for me, especially for recording later on.

[Pixl]

Why are you using LNB2 instead of LNB1?

I just thought I should since it is physicaly different from the lnb for C band. I am trying another scan with it set to lnb1. It breaks the scan into 4 parts. Vert, horz, 10700 to 11700, and 11700 to 12750, even though I did not specify a two band universal. It locks one TP 11920 H 4599, but no channels found.
Again if you guys can look at these settings, what should be entered for LOF, LOF/L, LOF/H, threshold when using a single band standard Ku lnb?


[Only registered and activated users can see links] ([Only registered and activated users can see links])

[Pixl]

. Sometimes posting a hand drawn diagram, helps alleviate the guessing of how the system is connected. On mine. I prefer to separate C and Ku on two tuners... makes life easier for me, especially for recording later on.

Not too much to understand, my system has been simplified over time. Most all Ku is on a separate dish, no switches, to separate tuner. My C band is this setup shared by a couple stray Ku dishes.

Tuner> 8 port 1.1 switch> port 8> Cband lnb.
____________________>port 4> 103w Ku. lnb.
____________________> port 6> 15w Ku. lnb.

This setup was working with the Raptor I just pulled out of service.

[eastof111]

Your LNB is only single band, so no threshold switching is necessary with a standard lnb. I have always used 10750 or 11700 just to remind me that it's a ku setting when I quickly zoom through my settings in the tuner section.

The threshold setting is the frequency at which the receiver tells the LNB to switch from Low Band to High Band.

"It breaks the scan into 4 parts. Vert, horz, 10700 to 11700, and 11700 to 12750, even though I did not specify a two band universal."
Some of the images I used did do that with a standard ku lnb when the scan start frequency isn't changed. Change the scan start frequency to 11700 and the end frequency to 12200 and it should give you a two part scan process instead of four.

In regards to the threshold, if you were using a universal, the settings would be:
Lo 9750, Hi 10700, Threshold 11700 and have the 22khz switching on.

[Pixl]

I had to go back to configuring Ku on the LNB2 template. Setting up Ku on LNB1 template greys out all my C band sat channels. At this point I was able to get the Huntington beach cams and several NBC channels by doing a manual scan on those TPs. So this tells me the Ku dish and switch port 4 is working. Something not right with the LO settings that affect blind scan on Ku. Blind scan works great on C band. The lnb menu choices does not have a predefined setting for a standard single band Ku lnb. Anyone have blindscan working with Ku ??

[Pixl]

Change the scan start frequency to 11700 and the end frequency to 12200 and it should give you a two part scan process instead of four.
I have tried this and it does drop back to a 2 part scan, but finds nothing.

[eastof111]

This is my current setting for 103º ku using 8x1-> on input 2 -> 4x1 -> on input 2.

Here are some pixs.

[Pixl]

This is my current setting for 103º ku using 8x1-> on input 2 -> 4x1 -> on input 2.

Here are some pixs.

East,

I matched my settings to your screen shots ( only a minor change to the scan range) it stops on several TPs along the way, but finds no channels. Maybe something broken in the blindscan of my image?

[eastof111]

You might play with the voltage mode under the advanced setting and change it to 13 v then scan and see what happens. The same for 18v.

But prior to doing that go to the sat finder and select the appropriate tuner, then the sat, then user defined transponder then see if it scans Huntington.

[Pixl]

You might play with the voltage mode under the advanced setting and change it to 13 v then scan and see what happens. The same for 18v.

But prior to doing that go to the sat finder and select the appropriate tuner, then the sat, then user defined transponder then see if it scans Huntington.

Might be one of my posts got behind. See my post #11 above. I am able to get Huntington that way. So the dish, lnb, and switch setting is working. Just something with blind scan on Ku. C band is ok.

What image are you using?

[eastof111]

Yeah, I missed that one.

I remember last year when the Duo2 came out, we were having blind scan problems with some of the tuners and we had to wait till they issued new drivers and eventually new images. I wonder if this is the same case with your receiver and image.

Currently using NFR in flash and I have ATV in usb stick.

Another possibility is when you keep re-flashing an image it will reinstall the system satellite.xml file and if it differs in size and content from your original that you uploaded earlier with your settings, it will create havoc sometimes.

[eastof111]

Pixl, you caught my curiosity, so I loaded up ATV and I am getting the same blind scan results.

1 - Satfinder finds and scans 103º on my fixed dish, but no blind scan.
2 - I did a blind scan of 97º ku with the fixed dish and it produced about half of what should be there.
3 - Switched to the bud and Satfinder finds and scans 103º, but no blind scan.
4 - Moved the bud back and forth while watching Satfinder and the signal for 103º did decrease and return to normal when centered.

So, either my settings got corrupted or the image has switch bugs or both.

When I have time this week, I will start from scratch with ATV and load a new image, new sat file and set up my fixed ku dishes and see if they blind scan properly with the 8x1 switch. Then I'll check the bud which uses a 2x1 switch.

[Pixl]

Thanks for testing that. You getting the same results makes me look toward the software. The blindscan for C band has a single band template. But for Ku there is no single band template. Just user defined dual band. This may be the trouble, what values do you put in for the box to handle it as a single band scan? I've tried 10750 for lo and hi, also tried different combinations of 10750 and 00000, 11700, and 12200.

[eastof111]

I am still trying to figure out what has changed because I've never had a problem blind scanning with my bud before. Satfinder is working (my guess) because it is reading the info from the lamedb file. The current sat.xml (old) system file is what is being read by the blind scan option. Since the lamedb and sat.xml file don't match, I am guessing that's why the blind scan option is not working correctly.

I will try to update the file today using telnet to put the receiver to sleep and see what happens. This has always worked in the past for me.

[eastof111]

Loaded a new sat file after putting the receiver to sleep. File from satellites-xml.eu see attached pix.

Blind scanned with bud and as you can see it is still scanning frequencies that are not in the new sat file table.

In the past have always used 10750-10750-10750 when connected to my 8x1 switch on port 1 without any problems. Now it's connected to a 2x1 switch with same settings and the result is no blind scan. Also, tried your numbers and it made no difference, including 12700.

I guess it's time for a fresh flash and start from scratch.

[Pixl]

Blind scanned with bud and as you can see it is still scanning frequencies that are not in the new sat file table.

I'm not sure what I see in your photos, but I always thought "blind" scan meant it was blindly looking at all frequencies at a pre determined spacing, usually just a few meg. Doesn't seem it would need files at all unless you are doing a automatic scan which only looks at TPs on file.

Still you may be on to something as I too have moved the lamedb and sat.xml in and out a few times.
My satfinder works fine, gets TPs in just a few seconds so again the switch, lnb, and dish are ok.

[eastof111]

Just re-flashed NFR, cleaned out the system bouquets, etc. Using the flashed sat.xml file, the bud blind scanned and found only two channels on tuner A. Did the same with the fixed dish and zero on tuner C. It's scanning in 6 meg increments and missing 11940.

Checked Satfinder and at least I can see my switches are working by the difference in dbs in tuner A and C.

[eastof111]

Seeing most of the images use the same blind scan search engine, I would guess it should have the same effect. I guess I'll have to re-check the others too.

[Pixl]

I got something to work right. I moved the cable from my main Ku dish (the one that has a universal lnb set up) and put it on tuner B. Using the universal lnb template it blind scanned in just a few channels with the dish pointed at 91w, all with freq listed above 12500. So I changed to user defined lnb template, 9750/10600 but with the tone set to "on" locks it to the hi band. It blind scaned in everything I usually see on 91w and then some, all with the correct TP frequency listed.
To summarize what I found today, Universal setup doesn't work correctly on any lnb as someone mentioned earlier.
User defined lnb setup works correctly with a universal lnb.
User defined lnb setup does not work with a single band Ku lnb.

[Pixl]

Seeing most of the images use the same blind scan search engine, I would guess it should have the same effect. I guess I'll have to re-check the others too.

Yes, good thing to check. Seems this would already be known unless it is a side effect of a recent update.

[eastof111]

Well, glad you have it working.

[Pixl]

Well, glad you have it working.

Well not really. I still need my fixed 103w w/single lnb to work.

[Pixl]

So.. continuing on, if I can get some help from East or anyone who has a single band Ku lnb working correctly on E2 please take two steps forward :)

[eastof111]

Pixl, you might post on the ATV or PLI forum and see if they have any recommendations.

[eastof111]

Pixl, still looking as to why it isn't scanning with user defined settings....

Changed tuner settings to unicable and switched channel setting to satCR 2 and it did blind scan very, very fast on my fixed dish. Haven't tried the bud yet. So, there's something screwed up. Like I said the PLI guys should hopefully have an answer.

[eastof111]

Changed the setting to 10750-10750-10750 for unicable and rescanned on the fixed dish.

[el bandido]

So.. continuing on, if I can get some help from East or anyone who has a single band Ku lnb working correctly on E2 please take two steps forward :)

In the past, I have had a single ku band lnb with a 10750 l.o. working without problems using an E2 image. I would expect some of the settings mentioned here to have worked for you.Try updating the image o saving the image and loading something different. OpenATV has provisions for updating online without losing any of your settings or installed plugins.

[eastof111]

Had some time and played with the user defined settings again last night. I used 10600-10600-10600 or 10600-10600-10750 both with Tone Mode ON and the blind scan worked very well on most sats until I got to 91W Galaxy 17. It kept scanning the Nimiq sat next door. So, I tried other settings on that particular sat to see if it would scan correctly. See below.

91W Galaxy 17
1- 10750-10750-10750-Tone Mode ON - Scan 11700-12200 - finds Nimiq only
2- 10750-10750-10750-Tone Mode OFF - Scan 11700-12200 - finds nothing
3- 10750-10750-10600-Tone Mode ON - Scan 11700-12200 - finds Nimiq only
4- 10750-10750-10600-Tone Mode OFF - Scan 11700-12200 - finds nothing

5- 10600-10600-10600-Tone Mode ON - Scan 11700-12200 - finds Nimiq only
6- 10600-10600-10600-Tone Mode OFF - Scan 11700-12200 - finds U.S. only
7- 10600-10600-10750-Tone Mode ON - Scan 11700-12200 - finds Nimiq only
8- 10600-10600-10750-Tone Mode OFF - Scan 11700-12200 - finds U.S. only

For now, the standard ku lnb seems to work with the 10600-10600-10750-Tone Mode OFF settings.

I also played some more with the unicable settings but not all sats would blind scan.

I guess I'll keep using the 10600-10600-10750-Tone Mode OFF settings until something else changes again.

[el bandido]

I will try to install a 10750 lnb as a test, but these settings work for me with universal lnb.

10247

[Pixl]

East, EB,

Thanks for following up on this. I am back to work (barely) and don't get the time to play with this as I did almost all day the last 6 weeks while I was on medical leave. Please don't let the issue cool off, I just will be testing your findings as time allows. :)

[el bandido]

I will try to find time tomorrow to install a 10750 lnb on one of the dishes.

[el bandido]

Had similar problem blindscanning with OpenPLi. My solution was to delete the blindscan plugin and reinstall it. This can be done in the plugin menu. Blindscan should be in system plugins. Delete blindscan and reinstall.

[eastof111]

Thanks, but that may be a solution with PLI, but ATV doesn't use the plugin. Reinstalling a fresh image of ATV still had the same problems, so did NFR and VIX.

[el bandido]

Look in the plugin menu and I think you will see blindscan as a removable plugin. Will check later...

[eastof111]

As far I know, NFR has no blind scan plugin, either in extensions or system plugins, the function is embedded in to the image. The same for ATV, LD, VIX and SF_Team. Unless I missed something.

Last time I checked BH, VTI, RuDream, Satdream, Vu+ and SPA only had the Euro blind scan available for loading from the plugin extensions menu. I've always hoped they would embed the same blind scan function in to the image as VIX, ATV, etc., but they haven't as far as I know.

PLI seems to be the only image to have the non-Euro blind scan as a plugin. But, I haven't checked BH, VTI, RuDream, Satdream, Vu+ and SPA within the last few days, so I could be wrong.

What numbers did you use in the user defined settings with PLI for the standard lnb to work?

[el bandido]

See screenshot in post#35. I do not have a bona fide 10750 lnb mounted on any dish yet, but maybe will get there this evening. Will also try to load up OpenATV image and see what it does for me.

I noticed last night after updating OpenPLi that my blindscan was performing very poorly and could not figure why. My blindscan results with PLi seemed to be similar to what had been posted. Deleting and reinstalling blindscan fixed my issues. But again, we are using slightly different images.

[eastof111]

Another thought to consider is that I always use images in multiboot to test. From what I've read, even though an image boots up from a usb or hard drive multiboot image, it still uses files which are in flash. If the flash image is currently not compatible with the currently running multiboot image there may be problems.

I just loaded PLI 12-05 to my usb stick. Upon boot, the only things I changed were the video settings. Rebooted. then assigned just one lnb setting to one tuner. Selected satfinder for that sat and lnb and I got a green screen with a reboot. Loaded the blind scan plugin and got the same results.

Restored my prior PLI settings from 11-26 and PLI works fine except for the blind scanning on a standard ku lnb.

I guess I will try loading PLI to flash tonight and see what results.

[eastof111]

Loaded PLI 12-05 into flash and bypassed the wizard. Changed the video settings, then activated one sat on one tuner. Selected Satfinder and it gives me a green screen.

Rebooted and did a factory reset. Reset to the same settings as above. Installed the blind scan plugin and scanned the one sat using 10750-10750-10750 and got zilch. Used Satfinder and also got zilch. But at least no green screen.

Changed to 10600-10600-10750 and blind scan worked on that sat. Checked Satfinder and it also found the sat transponders.

Going to try the same with NFR and see if I get the same results.

[Pixl]

Now I'm in trouble. At first today I had some success with blind scanning 103w Ku by setting the LO to 10750-10750-12200 tone on. I scaned in over 50 channels but all with the wrong frequency listed. I tried removing the blind scan plug in EB suggested, then re-install, but no joy there. Next I removed the blind scan plugin and installed a second plug in listed as "blind scan PO" what ever that means. Now the box locks up at the boot up screen.

[eastof111]

Isn't this fun! If you can access via Filezilla do a server search for the PO and delete it and you should be back up.

[el bandido]

Try looking for your PO Here:

/usr/lib/enigma2/python/Plugins/SystemPlugins

[Pixl]

Isn't this fun! If you can access via Filezilla do a server search for the PO and delete it and you should be back up.


Try looking for your PO Here:

/usr/lib/enigma2/python/Plugins/SystemPlugins

By the time I read these suggestions I had messed up the whole box, had to reload everything but now working. East I saw your post on the ATV site about this blind scan 10750 problem, hope someone answers it. I've got time today to try a few more guesses.

[eastof111]

Nothing at ATV yet... PLI one response.

[Pixl]

I put up a post at atemio4you as well. One thing I'm seeing after searching these Euro forums for blindscan, is most don't seem to care much about it. One post about a blind scan problem said they know about it but there are other issues more important on the list. Apparently blindscan is only used by a few people as a novelty as they rarely find any new channels.

[eastof111]

Too bad, that seems to be the case for almost a year now. I guess we should be grateful for what we currently have.

[Pixl]

Close to success. I blind scanned in 72 channels on 103w Ku from my fixed dish with single 10750 lnb. Here are screenshots of the settings.

[Only registered and activated users can see links] ([Only registered and activated users can see links])

[Only registered and activated users can see links] ([Only registered and activated users can see links])

[Only registered and activated users can see links] ([Only registered and activated users can see links])

As you can see I used the settings for a universal dual band lnb. I suspect the frequency of each TP is wrong, but I can't seem to find how to display that.

[eastof111]

When you select the channel service (CH11), go to menu> system>information> service> multiplex (yellow button). Also, depending on which skin you use, hitting the ok button while on that channel should pop up the info bar and hitting ok a second time should pop up the frequency info along with the pids. But, to see the second info bar, you have to first assign it in the display settings in system menu.

[el bandido]

I installed a 10750 lnb and get similar blindscan results.
Maybe posting the contents of the blindscan folder will help somebody solve or fix the issue. The folder can be found in: /usr/lib/enigma2/python/Plugins/SystemPlugins

[eastof111]

Heh, heh, I guess I may have to start using universals on my fixed dishes. :disagree:

[Pixl]

10279
I installed a 10750 lnb and get similar blindscan results.
Maybe posting the contents of the blindscan folder will help somebody solve or fix the issue. The folder can be found in: /usr/lib/enigma2/python/Plugins/SystemPlugins


Here is the blindscan folder pulled off my Atemio Nemesis. Looks like you need a program that can read .pyo files.

[Pixl]

I installed a 10750 lnb and get similar blindscan results.
Maybe posting the contents of the blindscan folder will help somebody solve or fix the issue. The folder can be found in: /usr/lib/enigma2/python/Plugins/SystemPlugins

EB,

What similar results did you get with the 10750 lnb?

My guess about the problem is that the software does not know what to do with a value of 10750, maybe out of range, where 10600 works just fine.

[Pixl]

When you select the channel service (CH11), go to menu> system>information> service> multiplex (yellow button). Also, depending on which skin you use, hitting the ok button while on that channel should pop up the info bar and hitting ok a second time should pop up the frequency info along with the pids. But, to see the second info bar, you have to first assign it in the display settings in system menu.

OK, found it. Lyngsat lists Huntington Beach North at 11940 V 20000
Nemesis scans it in at 10941 V 19998 using setup shown in post #52 above.

[eastof111]

One PLI response "Blindscan is supported by the manufacturer itself, OpenPLi only passes it on." Just slight coincidence that two receivers have the same problem. Could the reason be they use the same drivers?

[el bandido]

EB,

What similar results did you get with the 10750 lnb?

My guess about the problem is that the software does not know what to do with a value of 10750, maybe out of range, where 10600 works just fine.
You are correct. Hit the nail on the head.

I have been using Enigma2 off and on for a few years. These types of problems or bugs used to be very common. At one point, receiving transponders on c band was a turkey shoot. I bought every c band lnb that I could find trying to find one that would get all available c band transponders.

To be fair, not many have tested blindscan with a 10750 lnb. I have universal lnbs on my two ku dishes, and do not use 10750 lnbs because of the Atlantic satellites. I expect this problem will be fixed, but it may take a while. It will probably depend on how busy Huevos is...

[Pale-Rider]

asking for help with almost any issue from Pli will be met with ask the manufacturer for a answer, they have very little interest in providing end user support and prefer others to do it first, then supply a working patch to them. If you want a serious answer with regard to blind scanning ask Huevos on the ViX forum, he is the one who pretty much single handidly rewrote the blind scanning app in ViX vastly improving the poor offering from the manufacturer, and is the most likely to offer real suggestions of how to go further. PeterJ is also another one to maybe ask but he's more into improving ABM to work with other services.

[Pixl]

I don't know anyone at the VIX forum, I just signed up there yesterday. So if one of you guys know your way around there would be great to pose this 10750 question.

[Pale-Rider]

I don't know anyone at the VIX forum, I just signed up there yesterday. So if one of you guys know your way around there would be great to pose this 10750 question.

You dont need to know any one there. Just post your question in this section
[Only registered and activated users can see links] and I will make a post in the mods room to bring it to Huevos's attention (I am a admin over there by the name pheonix (yes I know it is not the correct spelling of phoenix but it's purposely spelt that way)).

[Pixl]

(I am a admin over there by the name pheonix (yes I know it is not the correct spelling of phoenix but it's purposely spelt that way)).

As is my screen name Pixl !

[Pale-Rider]

As is my screen name Pixl !


I always have to add that bit in LOL, I constantly get people moaning that i cant even spell phoenix correctly.

[eastof111]

Every time I go to the Vix site and see Pheonix, I just think the transposing of the "o" and ''e'' is a geographical phenomenon, just like driving on the wrong side of the road. LOL :hmmm::cool1:

[Pale-Rider]

Every time I go to the Vix site and see Pheonix, I just think the transposing of the "o" and ''e'' is a geographical phenomenon, just like driving on the wrong side of the road. LOL :hmmm::cool1:

Nope we spell it the same as you (unlike the way we spell colour) It's just a private dig at a old friend from long ago.

[eastof111]

Just a little light, very dry humor intended, nothing more. Thanks for your assistance with your posting at VIX, hopefully we may get the ku problem resolved.

[Pixl]

I appreciate you guys getting involved, and with this problem spanning different receivers and images its solution will help many of us using E2. Seems the Euro crowd don't use 10750 lnbs that are popular here and don't play with blindscan much. Understandably how many time would one of us blindscan DTV or Dish. The TP's stay mostly the same for years. But who else are we going to ask for help if the tuner drivers are written in propriety code.

[chewie]

Hello Pixl
OPEN ATV just came out with Ver. 4.3 for my VU+, I don't know what is new.
Regards.
Chewie

[chewie]

Hello PixL
For some reason I was not able to load this version on my multiboot, I also noticed this new version is not under the regular site I go to, strange, well i am not going to load it on the Receiver just yet .
Regards.
Chewie

[Pixl]

I read there yesterday that 4.3 was still in beta and they were asking people who had found it not to load it yet. I wonder if I can rip the blindscan folder and try it in my Nemesis.

[eastof111]

Pixl, don't know if you've tried OpenNFR yet, but it is also available for your receiver.

Don't know how good it is on the Nemesis, but I am currently testing it in flash on the Duo2.

Here''s the file in case you get the itch to try it later on.

[Pixl]

ok, thanks. Didn't know about that one.

[eastof111]

There's are few others, but I haven't figured out if they have blind scan yet.

[el bandido]

I read there yesterday that 4.3 was still in beta and they were asking people who had found it not to load it yet. I wonder if I can rip the blindscan folder and try it in my Nemesis.

You can rip and install another blindscan folder, but it may not work. The blindscan feature would disappear if it did not work, and may require reloading the image to get it back.

More than likely, this bug exists in all E2 blindscan plugins, and the plugin we are using in all of E2 our receivers is probably made by the same person. I expect this problem to be fixed but it may take a while like the C band transponder reception did. Installing an universal lnb will be the best short term option.

[Pixl]

. Installing an universal lnb will be the best short term option.

In trying to keep with good engineering practices I'd rather keep the feed horn that was original equipment with this Channel Master/Primestar 1.2m dish. It has a C-120 flange and an expensive Invacom LNB would be needed.
Hopefully we can get the request for a fix over to someone who knows and cares about this.

[Pale-Rider]

It's not that people dont care about blindscan because they do and Huevos has spent a ton of his own time working on and improving blindscan even trying to get Pli to incorporate his changes. The main hurdle here is that the primary developers are based in a area where they can not directly receive the services needed to look into things. even in Europe there are times when a Dev in say England cant access certain satellites that devs in say Portugal can and in those situations we have had to setup boxes to allow remote access where possible.

Please dont be disheartened by the posts so far in the thread on the ViX forum as we are trying to get people to look into your issues but we need a lot of data before we can even start to look into things, and we have asked Huevos if he can look into it for you. That said Huevos does also have a real life as a satellite installer in Spain and is currently working on improving ABM to work with more providers. My personal hope would be to get ABM working for the North American providers first then look into blindscan for this region if possible.

One last thing I would suggest is that you remain active in the thread on the ViX forum and provide as much of the info requested as you can, and dont worry about rob he's not a native English speaker and can come off as a little rough at times but he means well and if any one he would be the person pushing to get this sorted for you.

[Pale-Rider]

Another thing here is that people keep refering to blindscan as if it's differnet in most images, well thats not true, for the OE-A at least all member teams and those who are not members but still build from the OE-A git, obtain their blindscan plugins from here.
[Only registered and activated users can see links] and as you can see it has been forked 63 times. so maybe start there ?.

[el bandido]

The main hurdle here is that the primary developers are based in a area where they can not directly receive the services needed to look into things.

This problem can be tested and seen almost anywhere in the world. Most Ku satellites that are available in Europe and other countries have linear transponders above 11700 MHz. The only other item you need to test and look into things would be a standard lnb (l.o. 10750). So this problem can be seen almost anywhere in the world providing you have standard lnb installed.

[Pixl]

Pale,

Thanks for explaining that. I didn't mean to have any "tone" in my posts about this, but sometime the typewritten word can sound like that. Being a newcomer to E2 I am just realizing all the work in the underlying structure.

I must say you lost me with your post #79. I took a look at the link and it is all way over me. And what does "forked 63 times" mean? Also what is ABM ?

[Pale-Rider]

Pale,

Thanks for explaining that. I didn't mean to have any "tone" in my posts about this, but sometime the typewritten word can sound like that. Being a newcomer to E2 I am just realizing all the work in the underlying structure.

I must say you lost me with your post #79. I took a look at the link and it is all way over me. And what does "forked 63 times" mean? Also what is ABM ?

Sorry If I inferred you had a tone that was not my intention.

Debugging issues in E2 requires a lot of input from those reporting issues especially in circumstances like this where the devs dont have access to the services you are trying to get your self and a standard LNB as mentioned in the post above yours may very well be standard for north america but may not be not in Europe where the devs are who are working on this, so that wont help here.

My reference to the GIT was more to show that the central blindscan plugin in most if not all OE-A based images stems from a single source and by forked I mean it has been copied 63 times by other teams and individuals to use in their own images etc, this also allows those who have forked the code to issue pull requests back up stream allowing their fixes and improvements to be added back into the primary source, but most wont do that.

ABM refers to a plugin named AutoBouquets Maker in ViX and some other OE-A based images to scan and generate channel lists from the providers own broadcast data, for 28.2 east this has radically changed the way channel lists are built and cut down a standard scan time down from almost 30 minutes to just over 1 or 2 minutes as well as instantaneously ordering the channels as per the providers own channel lists numbers.

I know there is a lot to take in here and I dont want to scare you off but on order to fix a issue we first need to be made aware it exists then need to work together to find the solution, I am not a coder but I am very interested in getting more international groups working together to better Enigma2 for all users no matter where they are.

[Pale-Rider]

Here is the reply Huevos just made to the thread you made on the ViX forum.


The closed source binary (from the manufacturer) is written for a universal LNB. The only reason C-band 5150 LO LNBs work is because we added a workaround. If you want to use an LNB other than universal you will need to add another workaround in the plugin.

Not really sure how you would proceed from here though.

[eastof111]

Regarding ABM for N.A., I did pm Peter many months ago per your earlier suggestion. Just waiting patiently that something will come our way. I and assume many others here are willing to cooperate as much as possible.

[el bandido]

The closed source binary (from the manufacturer) is written for a universal LNB. The only reason C-band 5150 LO LNBs work is because we added a workaround. If you want to use an LNB other than universal you will need to add another workaround in the plugin.

Similar to what Erik at PLi said, just more detailed.
Whether we like the answer or not, at least we get the same or similar answer from two sources.

[eastof111]

"Not really sure how you would proceed from here though."

Someone must have a contact source of the coders that develop for the manufacturer.

[Pixl]

a standard LNB as mentioned in the post above yours may very well be standard for north america but may not be not in Europe where the devs are who are working on this, so that wont help here.

There has got to be plenty of people in the business that know about 10750 LNBs. Every receiver I've owned in the past right up to the Optibox Raptor has had provisions for using a 10750 lnb.

[el bandido]

Attached is a screenshot of the blindscan plugin opened in an editor.

Look at lines 840-845. These lines partially show the work-around for the C band blindscan in the VU+ Duo2. We need to look and see if something similar can be done for the 10750 lnb. I think it is doable, but it will take a person that knows Python. I have very limited knowledge in this area, but I do see some things to try as time permits.

[eastof111]

Can't read it, too small. Is this the same file as plugin.pyo?

[Pixl]

Too small for me to read too. But looks like what I've been trying to do for two days, open the plugin.pyo. I've loaded a few .pyo editors, but no success.

[eastof111]

Here's the file you can use Notepad to open.

[eastof111]

EB, did you ever setup your computer for compiling a pyo file after editing it?

[el bandido]

You do not compile a pyo file. Just delete the original py file and replace it with the pyo that has been modified. It will automatically compile on reboot...

[Pixl]

Here's the file you can use Notepad to open.

East,

I tried that earlier, all you see is mostly machine language.

[el bandido]

Not Notepad. You will need to open it with Notepad++.

[eastof111]

The file was converted and renamed to a txt file so it will open with a text editor.

[eastof111]

You do not compile a pyo file. Just delete the original py file and replace it with the pyo that has been modified. It will automatically compile on reboot...

Cool will have to try it.

[Pale-Rider]

Here's the file you can use Notepad to open.

The standard windows notepad application is not recommended for working with these files as it corrupts them upon saving, use something like notepad++

[Pale-Rider]

You do not compile a pyo file. Just delete the original py file and replace it with the pyo that has been modified. It will automatically compile on reboot...

For clarification a .pyo file is a human readable Python file.
A .py file is the machine readable Python file.

You simply place the .pyo file into the required directory on the receiver and reboot, the image will convert the..pyo file or to use the correct term compile it. But remember to remove the .pyo file once it has been compiled otherwise every time you reboot you will essentially be generating a new .py file overwriting the one already on the box.

[Pale-Rider]

You do not compile a pyo file. Just delete the original py file and replace it with the pyo that has been modified. It will automatically compile on reboot...

Yes that's the way most coders get into enigma but sooner or later if you want to do some serious work in enigma you are going to have to get used to working from GitHub. Also be prepared for a lot of system crashes when doing this kind of work so get used to keeping multiple image backups and multiple backups of the files you are working with. And lastly only make small changes to the files at first so you know what you have changed in case you do end up with a system crash, if you change too much in one go it will be a total nightmare to debug and find the error.

[Pixl]

East, your file does open in a text reader. I think I see what EB mentioned but I don't have line numbers. I'll C/P here.

def correctBugsCausedByDriver(self, tplist):
if self.is_c_band_scan:
x = 0
for transponders in tplist:
if tplist[x].frequency > 4200000:
tplist[x].frequency = 5150000 - tplist[x].frequency - 9750000
x += 1



Looks like they are making 5150 be interpreted as 9750.

[el bandido]

Correct.
Now what we need to find is a blindscan pattern that is consistent, but repeatable. We need to try and get the 10750 lnb to blindscan satellites and display transponders on a satellite that are consistent. Then we can try and fix the found transponder frequencies, similar to what was done with the c band lnb.

[Pixl]

Correct.
Now what we need to find is a blindscan pattern that is consistent, but repeatable. We need to try and get the 10750 lnb to blindscan satellites and display transponders on a satellite that are consistent. Then we can try and fix the found transponder frequencies, similar to what was done with the c band lnb.

Here is what I found so far that might help. On 103w Ku Huntington Beach is down linked at 11940 V.
My single band lnb down converts 11940-10750=1190 sent down the coax.
The Nemesis thinks I'm using the lower LO, so 1190+9750=10940 which is what I see displayed on the screen as the TP received for Huntington Beach.

I'll check tonight to see what happens when TPs above the threshold on 11700 are received using the upper LO.

[Pixl]

Is there a way to display all the TP freq. in a nice view as I'm used to with the Raptor and most other receivers I've had instead of having to coax each channel individually with several steps. ??

[el bandido]

Use blindscan and save the transponders to XML...

[eastof111]

I wanted to see if there were differences in the pyo files of the embedded blind scan function of OpenNFR vs. the plugin blind scan function of PLI. There seems to be some slight variations between the two files.

[eastof111]

Someone was considerate in inserting comments....

[el bandido]

Not really considerate. Comments and remarks are more of a necessity, else you forget what you did, were doing, or were trying to do. Comments may also help others that are making changes.

I will try and put the 10750 lnb back on tomorrow and see if I can get some consistency with it when scanning for transponders.

[Pale-Rider]

It's standard practice for coders to add such comments within their work, as a way for others to follow and where necessary add their own improvements, unfortunately not all will do so.

You can see exactly who made did what and when here
[Only registered and activated users can see links] you can also click on the individual entries to see exactly what was added or removed at every step of the way along with any and all comments made by the authors. such as this one here
[Only registered and activated users can see links]

[eastof111]

I've seen my share of coders actually removing comments.

[Pale-Rider]

Unfortunately so have I but that tends to happen when people decompile Python files as the process of deco piling the files only outputs the code and not the comments. Which is why I can't stress enough that people work from the source rather than rip files from images.

[eastof111]

Agree. Makes life much easier when everyone cooperates.

[el bandido]

This is the best solution I see for using a 10750 l.o. lnb with the current E2 blindscan plugin:
(A) Use the lnb Universal setting
(B) Change the Scan stop frequency in the Blind scan menu to 11700
(C) All found transponders will be displayed 1 GHz lower.

For example, The 11809 transponder for LPB at 87W will be displayed as 10809 when using these settings and a Standard 10750 l.o. lnb.
Another way to put it is: All transponders that begin with 11 will be displayed as 10, and all transponders that begin with 12 will be displayed as 11.

This 10750 lnb problem is probably pretty easy to fix for somebody that works with the plugin. Changes will probably need to be made in more than one area to be successful, so I would expect it to take some time.

Universal lnb settings could be described as as scanning the IF of the receiver (950-2150 MHz) using the low l.o. frequency, then changing to the high l.o. frequency and scanning the receiver's IF again. This would explain why you get duplicate channels during a blindscan when using Universal lnb settings with a Standard lnb.


Attached are some blindscan logs.
blindscan_87W_11-12-2014_09-47-13 = Scan done using 10750 lnb and 1700 as upper cutoff.
blindscan_87W_11-12-2014_09-23-41 = Scan done with 10750 lnb and default settings.
blindscan_87W_11-12-2014_10-05-33 = Scan done with default settings and Universal lnb.


We could expect similar problems and a similar solution if we used a circular 11250 l.o. lnb with the current blindscan plugin. I have modified an Universal lnb to work as circular instead of linear, so I did not see any problems with the circular transponders using the modified lnb.

[Pixl]

EB,

Your findings jive with what I'm seeing too. All my scans are 1000 low, but at least the blind scan is working to a usable degree.

In your post you mentioned attaching blindscan logs, but I don't see them. Can you re-post?

In your service info screen shot I see "roll off 0.35" what is that?

[el bandido]

Look under the pictures and click on "blindscan.rar". There are three files atttached in that .rar file.
"roll off 0.35" Is a DVB-S2 filtering setting. A .pdf file explaining this is attached.