E2 on a new Atemio Nemsis

[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.