UK frequency offsets

[Humous]

I'm confused about the UK frequency offsets.

The frequencies in the transponder list are as follows:

482000

506000

530000

538000

562000

578000

 

With a Hauppauge NOVA-T Stick or Airstar these work fine but with a Pinnacle 2000i I had to change the 578000 to 578166 to get it to work.

Seeing that the actual frequencies of the others are -167 (which is what is in the NIT) I'm confused about what is going on here.

 

If I use the actual frequencies:

481883

505883

529883

537883

561883

578166

then the NOVA-T Stick and Airstar only see channels on 578166 but the Pinnacle 2000i sees channels on all of them.

[Griga]

That's really strange. The catch range and oscillator frequency of different DVB-T devices may vary a bit, but usually they should all work with the actual frequencies - except if the driver automatically adds/subtracts a local frequency offset, maybe read from a registry key created by the installer, dunno... DVBViewer doesn't do something like that.

[CX23882-19]

The Pinnacle 2000i is capable of auto-locking to offsets, but you need to enable it:

 

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PinnacleRoyalTS\DriverParameters]
"ZL35x_CaptureRange"=dword:00000001

ZL35x_CaptureRange = 0 means the demodulator will only lock onto the frequency requested by the application, so if you have a multiplex on 762166kHz, you need to tune 762.166MHz in DVBViewer

ZL35x_CaptureRange = 1 means the demodulator will lock onto a frequency +/-200kHz from the frequency requested by the application, so if you have a multiplex on 762166kHz you can tune 762.000MHz in DVBViewer and it will still find it

 

 

It won't hurt to set this too:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PinnacleRoyalTS\DriverParameters]
"MT2060_EnableSpurAlgorythm"=dword:00000000

The MT2060's spur avoidance algorithm seems to introduce errors on Tuner 1 when tuning Tuner 2 and vice versa (at least as implemented on the 2000i), and even on a frequency susceptible to spurs, I see no advantage in having this enabled.

Edited December 14, 2008 by CX23882-19