E2 on a new Atemio Nemsis

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.
 
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.
 
el bandido said:
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.
Click to expand...

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.
 
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. ??
 
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.
 
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.
 
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
Code: 
https://github.com/oe-alliance/oe-alliance-plugins/commits/2.3/Blindscan
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
Code: 
https://github.com/oe-alliance/oe-alliance-plugins/commit/992fcebc91856ae1db0d4c30c064232867a3471a
 
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.
 
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.
 

Attachments

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?
 
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.
 
Back
Top