I'm in Wellington too, so if you want me to test the DVB-S unit in another situation I'd be happy to oblige.

For me, 22khz is OFF, and Diseqc is NONE.

LNB Power is ON.

As a matter of interest, what operating System you using?   I know that a lot of USB DVB-S units will not currently run under Win 10.

Rickles:

As a matter of interest, what operating System you using?   I know that a lot of USB DVB-S units will not currently run under Win 10.

     >But are the driver and windows 10 a possible issue? <

I guess it's possible because incorrect BDA drivers do affect digital reception from varying sources.

Rickles:

     >But are the driver and windows 10 a possible issue? <

I guess it's possible because incorrect BDA drivers do affect digital reception from varying sources.

     >Is there a generic or universal driver?<

None that I can find ... I actually have a USB DVB-S device sitting here at the moment that will work on everything except Win 10

Rickles:

 

     >Is there a generic or universal driver?<

 

None that I can find ... I actually have a USB DVB-S device sitting here at the moment that will work on everything except Win 10

 

Define "work".  Usually, Windows drivers will simply not work at all on a later version of Windows that they are incompatible with, rather than appear to work and then do strange things.  I would not expect drivers that do actually load and do tune in some transponders to then fail to tune other frequencies due to an incompaibility with the Windows version.  The page on the TBS site for the 5980 does only say the Windows drivers were updated for Windows 8, but the main specification for the 5980 here:

http://www.tbsdtv.com/products/tbs5980-dvb-s2-ci-tv-tuner-usb.html

lists Windows 10 under "System Requirements".  Windows 8 drivers normally work in Windows 10, but if there is any doubt, emailing TBS support should clear it up.  TBS are a reputable company - I would not expect them to be selling something as Windows 10 compatible if it was not, and if this is a bug causing the problem, I would expect they would want to fix it.

In my opinion, and with only the limited information available on this thread, this problem does not feel like a driver problem.  It feels exactly like what I was getting when I had the wrong LOF setting in minisatip - a scan would only find one or two transponders, where the combination of the bad LOF setting and the transponder frequency for some other transponder, when combined, matched the real frequency for a transponder.  So I think it is likely that the problem is still a wrong LOF setting.  If the LOF setting does not match the hardware, then if a transponder gets tuned in, the channels reported will not match the transponder frequency reported, which seems to be what is happening here.

I have done a quick search, and these are all the LOF settings I have found for Sky NZ dishes so far:

10750, 10600, 11300

See here:

http://www.legiontv.co.nz/archives/122

for help identifying an LNB.

It should also be possible to calculate the correct LOF frequency using the difference between the reported frequency a transponder is tuned on and the actual frequency it is transmitted on as reported on the Lyngsat site.  That difference should be the difference between the LOF that was used to tune with and the correct LOF frequency.

fe31nz:[snip]

 

I have done a quick search, and these are all the LOF settings I have found for Sky NZ dishes so far:

 

10750, 10600, 11300

 

This. And as noted earlier, add 10700 to that list.

fe31nz:

 

 

 

 

 

It should also be possible to calculate the correct LOF frequency using the difference between the reported frequency a transponder is tuned on and the actual frequency it is transmitted on as reported on the Lyngsat site.  That difference should be the difference between the LOF that was used to tune with and the correct LOF frequency.

 

Interesting,  so I'm currently using LOF1 10750, LOF2 0 and LOFSW 11800, I can only pick up the Sky transponder 12267 which TransEdit reports it 12268.

This means if I subtract 12267 from the reported 12268 that I need to adjust LOF1 by 1? (eg to 10749 or 10751?)

     >Define "work".  Usually, Windows drivers will simply not work at all on a later version of Windows that they are incompatible with,<

I would agree ... my unit will not 'work' because it lacks a driver and shows this as an unknown device in Device Manager.

     >I would not expect drivers that do actually load and do tune in some transponders to then fail to tune other frequencies due to an incompaibility with the Windows version.<

That would seem to be a sensible conclusion ... which is why I offered to test the OP's device on my system.

indapie2000:

 

fe31nz:

 

It should also be possible to calculate the correct LOF frequency using the difference between the reported frequency a transponder is tuned on and the actual frequency it is transmitted on as reported on the Lyngsat site.  That difference should be the difference between the LOF that was used to tune with and the correct LOF frequency.

 

 

Interesting,  so I'm currently using LOF1 10750, LOF2 0 and LOFSW 11800, I can only pick up the Sky transponder 12267 which TransEdit reports it 12268.

 

This means if I subtract 12267 from the reported 12268 that I need to adjust LOF1 by 1? (eg to 10749 or 10751?)

 

Yes.  If you receive real frequency 12267 on 12268, then you need to subtract 1 from the LOF setting, so 10749 would be correct.  That would likely mean that your LNB is ancient and its frequency has drifted with age.

The channels on 12267 are DVB-S2 HD channels - this is what I see on that frequency using Linux dvbtune and scan-s2:

SKY Sport 3 HD;SkyNZ:1517:H:S0.0W:22500:1001:1111=ang;1101=ang:0:0:1174:169:9:0
SKY Sport 4 HD;SkyNZ:1517:H:S0.0W:22500:1002:1112=ang;1102=ang:0:0:1201:169:9:0
ESPN HD;SkyNZ:1517:H:S0.0W:22500:1003:1103=eng:0:0:1175:169:9:0
SoHo HD;SkyNZ:1517:H:S0.0W:22500:1005:1105;1105:0:0:1170:169:9:0
SKY ARENA HD;SkyNZ:1517:H:S0.0W:22500:1006:1106;1106:0:0:1181:169:9:0
THE ZONE HD;SkyNZ:1517:H:S0.0W:22500:1016:1116;1116:0:0:1251:169:9:0
beIN SPORTS 1 HD;SkyNZ:1517:H:S0.0W:22500:1007:1107=eng:0:0:1235:169:9:0

So if those are the channels you are seeing, then that is real frequency 12267.  If not, please list all the channels you are seeing on 12268 so I can find a match and give you the correct frequency.

But I think it is still very unlikely that you have a "universal" type LNB that has two local oscillators and needs a switch setting - I would delete that LOFSW setting, or set it to 65535 (maximum 16-bit integer value) to disable it.  Most NZ dishes use "standard" LNBs with one local oscillator only.  The switch setting tells your DVB-S/S2 card when to send a 22 kHz tone signal to tell the LNB to switch to its second local oscillator.  If there is no second local oscillator, sending that signal can switch off the one-and-only local oscillator and you get no signal at all.  That seems to be what happens with my dish.  So if you have a switch setting in place, any frequencies that you scan or tune to that are above the switch setting will not work as the local oscillator will be off and no signal will be received.

Just did a blind scan under LOF1 10750, LOF2 0 and LOFSW 65535. Still haven't heard back from the body corp yet so no idea if these are the correct settings, but 10750 is the only one that seems to bring up anything and it's always the same Sky channels.

The Sky channels Sky Sport 3, Sky Sport 4, ESPN, SoHo, Sky Arena, The Zine and beIN Sports 1 all appeared on the following TPs

12262, 12267 and 3 lots of 12268 (the channel groupings showed up 3 times under this TP)