Setting the stop frequency at 12200 should find a transponder at 12189 because 12189 is less than 12200.
Setting the stop frequency at 12050 should not allow a transponder at 12189 to be registered. Here are the code lines in the blindscan plugin that would not let that happen:
if freq >= self.blindscan_start_frequency.value and freq <= self.blindscan_stop_frequency.value and symbolrate >= self.blindscan_start_symbol.value * 1000 and symbolrate <= self.blindscan_stop_symbol.value * 1000:
add_tp = True
else:
add_tp = False
Results 11 to 15 of 15
-
08-18-2018,08:08 PM
-
08-18-2018,09:01 PM
That's what I thought but it must be 150mhz off. 12050= 12200
There is a game on 91w Ku at 12120 tonite do a blind scan with 12050 as the stop and see if you get it.
open pli 6.2 release is what i use with VU+ zero 4K.
attached some scans and you can see setting the stop at 11960 did not find tp 12120 where setting the stop at 11975 did find the tp 12120.
that shows it is around 150 mhz off.Last edited by Megatron817; 08-18-2018 at 09:41 PM.
-
Post Thanks / Like - 1 Thanks, 0 Likes, 0 Kiss My Assel bandido thanked for this post
-
08-18-2018,09:42 PM
Are you using Circular for lnb type in antenna setup?
-
08-18-2018,09:49 PM
yes, still using Circular settings.
-
08-18-2018,10:07 PM
I need to think about that a minute, and it is a little late to do that today. But you are correct about the 150 MHz.
The enigma2 plugin thinks the lnb is universal, so we have to trick it to run the standard 10750 lnb... We tell it to start 150 MHz lower--which makes it scan 150 MHz higher... We can add a few lines to the plugin file and fix this. Or run it like it is and understand the problem.
While we are at it, we can fix it where it shows 11700 for a start frequency instead of 11550 in the blindscan logs, but that will take a few more lines of code. Maybe this winter I will have time to go back through the plugin file and fix some of these items.
-
Post Thanks / Like - 2 Thanks, 0 Likes, 0 Kiss My AssMegatron817, eastof111 thanked for this post