Integrity Test Ka Band updateDVB

Llew

cerca trova...
Staff member
My Satellite Setup
Triple Dragon, Dreambox 8000, Echostar AD3000ip, TBS6522,6925,6983 PCie cards.
Gibertini 1.25m motorised dish driven by the AD3000, with either Inverto BU Quad or Norsat / XMW Ka LNBs . SMW 1.05m + 3 other dishes. Speccy: Promax HD Ranger+
My Location
The Flatlands of East Anglia
Tuning test on 16E Ka TP 21537H gets 21538H. Will try to resolve the close-spaced frequencies in Spectrum Scan.

Ka Test updateDVB.webp
 
I am able to lock Emirem TV on 21537H or thereabouts if I'm very careful to choose the right spot in Spectrum Scan.
Much easier to use Blindscan, but there are unintended consequencies, namely a multiple lock of some frequencies.
In the example shown, Emirem TV 21537H is found all the way from 21528H to its true frequency. Much the same with Canal 2 0n 21576H, which is found in several locks up to 21583H.

EBSPro Blindscan correctly identifies only the true transponder frequencies. Blindscanning in both cases is in 1 MHz steps.

Not sure why updateDVB is acting like this, maybe needs an increase in step size (can't see a way of changing this).

21536H.webp
16E Ka.webp
16E Ka scan EBSPro.webp
 
Sorry I didnt see this earlier, I did some changes to the STV091X driver, maybe that fixed the problem?

The driver looks at the frequency offset, if it is less then 1mhz I dont bother adjusting and retuning, I dont think it would really make alot of difference. so on SR < 1000 it might get confused but even then I think it would still be ok, but if there is a bunch of tp's less then 1000 all packed tightly together Im guessing that most software would have an issue with it. updateDVB's min step is 1mhz as Im guessing most blindscan software is.

UDL
 
Sorry I didnt see this earlier, I did some changes to the STV091X driver, maybe that fixed the problem?

The driver looks at the frequency offset, if it is less then 1mhz I dont bother adjusting and retuning, I dont think it would really make alot of difference. so on SR < 1000 it might get confused but even then I think it would still be ok, but if there is a bunch of tp's less then 1000 all packed tightly together Im guessing that most software would have an issue with it. updateDVB's min step is 1mhz as Im guessing most blindscan software is.

UDL
Thanks for your reply UDL, As you suggested to do elsewhere, I'll be doing an update for the app in due course, and see if the driver has solved this problem.
Can be done, as EBSPro shows.
 
It definitely can be done, its mostly a compromise between finding everything and speed. switching to 100khz steps would slow the blindscan down approx 10x. There are idea's that I could play with though, I'll think about it, maybe I can find a better balance.

UDL
 
OK, got round to trying these close TPs on 16E Ka since a git pull update.

Much better now, thanks @updatelee.

(The quality of some of the video source material transmitted on these African diaspora channels leaves much to be desired)

16E Ka BScan.webp

16E Ka 21535H.webp
 
Back
Top