Thank you Textin for your concerns, let me see if I can explain this so that the current method makes sense:
The difference in frequencies are due to many varying factors. Here's a list of a few possibilities.
Satellite receiver frequency detection.
LNB Oscillator inaccuracies.
LNB drift due to temperature. (At Iceberg's location there is a thing called snow, where I am located we have never heard of snow
)
Published frequencies are only theoretical or planned values, the actual frequencies can vary due to many factors.
(If you scan in the daytime vs. night time you sometimes see a difference.)
I am going to use Dish Network's 119W satellite as an example:
(I am using this satellite as an example only because I can get the theoretical frequencies very easily)
(All the below frequencies are using the same LNB and dish.)
Dish Network's NIT: 12238.580 MHz
Broadlogic: 12239.400 MHz
Coolsat:12239.000 MHz
Pansat: 12239.000 MHz
Dish Network's NIT: 12267.740 MHz
Broadlogic: 12268.500 MHz
Coolsat:12266.000 MHz
Pansat: 12267.000 MHz
As you can see from above not all receivers connected to the same dish and LNB will not agree on one frequency.
So when I do update scans if a transponder is already in the database and the current frequency and the last scanned frequency are different the two are averaged.
In the end having the frequency off by a little bit does not matter because the receiver has
PLL (phase lock loop) circuitry inside that will lock on to the correct center frequency.
I hope all of this make sense, if it does not let me know and I might be able to clear up any confusions.
EDIT - Iceberg - You gave me Hispasat updates after Textin's March 25 2008 post?