Skip to contentSkip to conversation

scan/scan-s2 doesn't tune, but dvbtune does?

DISCUSSION Michael Akey 4 participants 7 messages Dec 14, 2009 – Dec 21, 2009 Media (V4L/DVB)

lore
Share & tools
lore
#0 lore raw

I can't get the scan/scan-s2 utilities to lock any transponders (DVB-S). My test satellite is AMC1 103W, the Pentagon Channel tp. This is probably some simple user error on my part, but I can't figure it out. I have a Corotor II with polarity changed via serial command to an external IRD. C/Ku is switched by 22KHz tone, voltage is always 18V. Ku is with tone off, C with tone on. Speaking of which, is there a way to manually set the tone from the arguments on the scan utilities?

Here's what I've tried and the results:

$ ./scan-s2 -a 0 -v -o zap -l 10750 INIT
API major 5, minor 0
scanning INIT
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder DVB-S  12100000 H 20000000 AUTO AUTO AUTO
initial transponder DVB-S2 12100000 H 20000000 AUTO AUTO AUTO
----------------------------------> Using DVB-S
Quoted 1 line
Quoted 1 line
Quoted 1 line

tune to: 12100:h:0:20000

DVB-S IF freq is 1350000

Quoted 10 lines
Quoted 10 lines
Quoted 10 lines

tuning status == 0x03
tuning status == 0x01
tuning status == 0x03
tuning status == 0x01
tuning status == 0x03
tuning status == 0x00
tuning status == 0x01
tuning status == 0x03
tuning status == 0x00
tuning status == 0x00

WARNING: >>> tuning failed!!!

Quoted 1 line
Quoted 1 line
Quoted 1 line

tune to: 12100:h:0:20000 (tuning failed)

DVB-S IF freq is 1350000

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

tuning status == 0x03
tuning status == 0x01
tuning status == 0x00
tuning status == 0x00

...snip...

Same thing happens if I use just 'scan' and not 'scan-s2.'

If I use dvbtune, it works though..

$ dvbtune -f 1350000 -p H -s 20000 -c 0 -tone 0 -m
Using DVB card "Conexant CX24116/CX24118"
tuning DVB-S to L-Band:0, Pol:H Srate=20000000, 22kHz=off
polling....
Getting frontend event
FE_STATUS:
polling....
Getting frontend event
FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI FE_HAS_SYNC
Bit error rate: 0
Signal strength: 51648
SNR: 26215
FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI FE_HAS_SYNC
Signal=51648, Verror=0, SNR=26215dB, BlockErrors=0, (S|L|C|V|SY|)
Signal=51776, Verror=0, SNR=26624dB, BlockErrors=0, (S|L|C|V|SY|)

The tuning file 'INIT' contains only the following line:
S 12100000 H 20000000 AUTO

I'm using v4l-dvb drivers from the main repo as of about a week ago. I am running kernel 2.6.32 on Debian testing. Any help is appreciated ..and hopefully it's just a simple flub on my part!

--Mike

#1 lore raw
Quoted 5 lines · Michael Akey

I can't get the scan/scan-s2 utilities to lock any transponders (DVB-S). My test satellite is AMC1 103W, the Pentagon Channel tp. This is probably some simple user error on my part, but I can't figure it out. I have a Corotor II with polarity changed via serial command to an external IRD. C/Ku is switched by 22KHz tone, voltage is always 18V. Ku is with tone off, C with tone on.

I'm afraid that I have a european background into which your use does not fit my expectations. What I expect is that the voltage will be determined by what sort of polarisation you are trying to receive (your fixed 18V would correspond to horizontally polarised transponders) whilst the 22kHz tone would be used to select within the Ku band between the low and high band (switchover between a universal LNB's 9750 and 10 600 MHz IF at actual frequency near 11 700 MHz).

Variants thereupon may depend on older installations, and while C band does exist, I've never personally bothered to use it or play with LNBs and such to learn those details. With this background, I'll attempt to interpret what I see below.

Quoted 7 lines
$ ./scan-s2 -a 0 -v -o zap -l 10750 INIT

initial transponder DVB-S 12100000 H 20000000 AUTO AUTO AUTO initial transponder DVB-S2 12100000 H 20000000 AUTO AUTO AUTO ----------------------------------> Using DVB-S

Quoted 1 line
Quoted 1 line
Quoted 1 line

tune to: 12100:h:0:20000

DVB-S IF freq is 1350000

This frequency would normally be tuned with 22kHz tone on, with a traditional Universal LNB. I can't be arsed to look up the particular bird on which your transponder lies to get its particulars (frequency 12100h, SR 20000 I will take from your parameters), but if this utility is selecting the 22kHz switching signal based on the frequency, it may assume that 12100 needs this tone, in spite of your specifying the LO intermediate frequency, which apparently you use to select between Ku band and when active, C band.

Quoted 5 lines

If I use dvbtune, it works though..

$ dvbtune -f 1350000 -p H -s 20000 -c 0 -tone 0 -m

tuning DVB-S to L-Band:0, Pol:H Srate=20000000, 22kHz=off

Here you're tuning directly to the IF frequency which the above utility determines from your specified LO value and desired tuning frequency.

I'd look at the source code for the above utilities which fail to see if it's deciding 22kHz tone based on the tuned frequencies. If so, and there aren't options to work around this as you can with directly specifying the IF to dvbtune' as above, then it may work to massage the input values you feed to scan' not to be the actual frequencies.

Quoted 2 lines

The tuning file 'INIT' contains only the following line:
S 12100000 H 20000000 AUTO

If this corresponds to 1 350 000 kHz IF, and you faked that your LNB had an IF of 9750 MHz, the corresponding ``tuning frequency'' would be 11 100 MHz, or 11100000 H in the above line. Horizontal polarisation corresponds to your 18V nicely. Otherwise it's a particular configuration which would be alien to me with my limited hands-on experience.

Note that what you get back from parsing the NIT tables when tuning the above transponder at the hacked value would need to be again adjusted similarly. But I don't know what the frequencies and bands are that are used by this bird, nor do I know what sort of consumer equipment is used outside the part of the world where I learned my knowledge of the trade.

Anyway, that's how I interpret your results. I'd be happy if someone with more intimate knowledge of those utilities, their options, and other setups, could give you a one-line cure for your woes -- otherwise I hope I've provided a bit of background to help you better understand what may be going on.

#2 lore raw
In reply to Michael Akey
Quoted 52 lines · Michael Akey

I can't get the scan/scan-s2 utilities to lock any transponders (DVB-S). My test satellite is AMC1 103W, the Pentagon Channel tp. This is probably some simple user error on my part, but I can't figure it out. I have a Corotor II with polarity changed via serial command to an external IRD. C/Ku is switched by 22KHz tone, voltage is always 18V. Ku is with tone off, C with tone on. Speaking of which, is there a way to manually set the tone from the arguments on the scan utilities?

Here's what I've tried and the results:

$ ./scan-s2 -a 0 -v -o zap -l 10750 INIT
API major 5, minor 0
scanning INIT
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder DVB-S  12100000 H 20000000 AUTO AUTO AUTO
initial transponder DVB-S2 12100000 H 20000000 AUTO AUTO AUTO
----------------------------------> Using DVB-S
Quoted 1 line
Quoted 1 line
Quoted 1 line

tune to: 12100:h:0:20000

DVB-S IF freq is 1350000

Quoted 10 lines
Quoted 10 lines
Quoted 10 lines

tuning status == 0x03
tuning status == 0x01
tuning status == 0x03
tuning status == 0x01
tuning status == 0x03
tuning status == 0x00
tuning status == 0x01
tuning status == 0x03
tuning status == 0x00
tuning status == 0x00

WARNING: >>> tuning failed!!!

Quoted 1 line
Quoted 1 line
Quoted 1 line

tune to: 12100:h:0:20000 (tuning failed)

DVB-S IF freq is 1350000

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

tuning status == 0x03
tuning status == 0x01
tuning status == 0x00
tuning status == 0x00

...snip...

Same thing happens if I use just 'scan' and not 'scan-s2.'

If I use dvbtune, it works though..

$ dvbtune -f 1350000 -p H -s 20000 -c 0 -tone 0 -m
Using DVB card "Conexant CX24116/CX24118"
tuning DVB-S to L-Band:0, Pol:H Srate=20000000, 22kHz=off
polling....
Getting frontend event
FE_STATUS:
polling....
Getting frontend event
FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI FE_HAS_SYNC
Bit error rate: 0
Signal strength: 51648
SNR: 26215
FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI FE_HAS_SYNC
Signal=51648, Verror=0, SNR=26215dB, BlockErrors=0, (S|L|C|V|SY|)
Signal=51776, Verror=0, SNR=26624dB, BlockErrors=0, (S|L|C|V|SY|)
Quoted 6 lines

The tuning file 'INIT' contains only the following line:
S 12100000 H 20000000 AUTO

I'm using v4l-dvb drivers from the main repo as of about a week ago. I am running kernel 2.6.32 on Debian testing. Any help is appreciated ..and hopefully it's just a simple flub on my part!

--Mike

Try using a non-auto FEC and rolloff.

Some devices won't accept auto for these parameters.

Cheers,

Lou

#3 lore raw
Quoted 71 lines · Lou Otway
Quoted 68 lines · Michael Akey

I can't get the scan/scan-s2 utilities to lock any transponders (DVB-S). My test satellite is AMC1 103W, the Pentagon Channel tp. This is probably some simple user error on my part, but I can't figure it out.  I have a Corotor II with polarity changed via serial command to an external IRD. C/Ku is switched by 22KHz tone, voltage is always 18V.  Ku is with tone off, C with tone on.  Speaking of which, is there a way to manually set the tone from the arguments on the scan utilities?

Here's what I've tried and the results:

$ ./scan-s2 -a 0 -v -o zap -l 10750 INIT
API major 5, minor 0
scanning INIT
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder DVB-S  12100000 H 20000000 AUTO AUTO AUTO
initial transponder DVB-S2 12100000 H 20000000 AUTO AUTO AUTO
----------------------------------> Using DVB-S
Quoted 1 line
Quoted 1 line
Quoted 1 line

tune to: 12100:h:0:20000

DVB-S IF freq is 1350000

Quoted 10 lines
Quoted 10 lines
Quoted 10 lines

tuning status == 0x03
tuning status == 0x01
tuning status == 0x03
tuning status == 0x01
tuning status == 0x03
tuning status == 0x00
tuning status == 0x01
tuning status == 0x03
tuning status == 0x00
tuning status == 0x00

WARNING: >>> tuning failed!!!

Quoted 1 line
Quoted 1 line
Quoted 1 line

tune to: 12100:h:0:20000 (tuning failed)

DVB-S IF freq is 1350000

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

tuning status == 0x03
tuning status == 0x01
tuning status == 0x00
tuning status == 0x00

...snip...

Same thing happens if I use just 'scan' and not 'scan-s2.'

If I use dvbtune, it works though..

$ dvbtune -f 1350000 -p H -s 20000 -c 0 -tone 0 -m
Using DVB card "Conexant CX24116/CX24118"
tuning DVB-S to L-Band:0, Pol:H Srate=20000000, 22kHz=off
polling....
Getting frontend event
FE_STATUS:
polling....
Getting frontend event
FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI
FE_HAS_SYNC
Bit error rate: 0
Signal strength: 51648
SNR: 26215
FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI
FE_HAS_SYNC
Signal=51648, Verror=0, SNR=26215dB, BlockErrors=0, (S|L|C|V|SY|)
Signal=51776, Verror=0, SNR=26624dB, BlockErrors=0, (S|L|C|V|SY|)

The tuning file 'INIT' contains only the following line:
S 12100000 H 20000000 AUTO

I'm using v4l-dvb drivers from the main repo as of about a week ago.  I am running kernel 2.6.32 on Debian testing.  Any help is appreciated ..and hopefully it's just a simple flub on my part!

Quoted 5 lines
Quoted 1 line

--Mike

Try using a non-auto FEC and rolloff.

Some devices won't accept auto for these parameters.

Michael,

The silicon in question doesn't do automatic FEC detection. Be sure to specify which FEC you need for the sat. If in doubt, walk through them all manually. Pilot auto detect is done in s/w was was added a long time ago.

- Steve

Signature · 2 lines
Steven Toth - Kernel Labs
http://www.kernellabs.com
#4 lore raw
Quoted 87 lines · Steven Toth
Quoted 77 lines · Lou Otway
Quoted 75 lines · Michael Akey

I can't get the scan/scan-s2 utilities to lock any transponders (DVB-S).
My test satellite is AMC1 103W, the Pentagon Channel tp. This is probably
some simple user error on my part, but I can't figure it out. I have a Corotor II with polarity changed via serial command to an external IRD.
C/Ku is switched by 22KHz tone, voltage is always 18V. Ku is with tone
off, C with tone on. Speaking of which, is there a way to manually set the tone from the arguments on the scan utilities?

Here's what I've tried and the results:

$ ./scan-s2 -a 0 -v -o zap -l 10750 INIT
API major 5, minor 0
scanning INIT
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder DVB-S  12100000 H 20000000 AUTO AUTO AUTO
initial transponder DVB-S2 12100000 H 20000000 AUTO AUTO AUTO
----------------------------------> Using DVB-S
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

tune to: 12100:h:0:20000

DVB-S IF freq is 1350000

Quoted 11 lines
Quoted 11 lines
Quoted 11 lines

tuning status == 0x03
tuning status == 0x01
tuning status == 0x03
tuning status == 0x01
tuning status == 0x03
tuning status == 0x00
tuning status == 0x01
tuning status == 0x03
tuning status == 0x00
tuning status == 0x00

WARNING: >>> tuning failed!!!

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

tune to: 12100:h:0:20000 (tuning failed)

DVB-S IF freq is 1350000

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines

tuning status == 0x03
tuning status == 0x01
tuning status == 0x00
tuning status == 0x00

...snip...

Same thing happens if I use just 'scan' and not 'scan-s2.'

If I use dvbtune, it works though..

$ dvbtune -f 1350000 -p H -s 20000 -c 0 -tone 0 -m
Using DVB card "Conexant CX24116/CX24118"
tuning DVB-S to L-Band:0, Pol:H Srate=20000000, 22kHz=off
polling....
Getting frontend event
FE_STATUS:
polling....
Getting frontend event
FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI
FE_HAS_SYNC
Bit error rate: 0
Signal strength: 51648
SNR: 26215
FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI
FE_HAS_SYNC
Signal=51648, Verror=0, SNR=26215dB, BlockErrors=0, (S|L|C|V|SY|)
Signal=51776, Verror=0, SNR=26624dB, BlockErrors=0, (S|L|C|V|SY|)

The tuning file 'INIT' contains only the following line:
S 12100000 H 20000000 AUTO

I'm using v4l-dvb drivers from the main repo as of about a week ago. I am running kernel 2.6.32 on Debian testing. Any help is appreciated ..and hopefully it's just a simple flub on my part!

Quoted 6 lines
Quoted 2 lines

--Mike

Try using a non-auto FEC and rolloff.

Some devices won't accept auto for these parameters.

Quoted 10 lines

Michael,

The silicon in question doesn't do automatic FEC detection. Be sure to specify which FEC you need for the sat. If in doubt, walk through them all manually. Pilot auto detect is done in s/w was was added a long time ago.

- Steve

Steve et al,

It would appear that it does in fact do auto FEC since I don't specify it with dvbtune and it works just fine (with both my Prof 7300 and 7301.) I think it's a tone issue, but then again, why does attempting to scan something on both bands C and Ku (tone on, and tone off respectively) not work? I figured if it's a tone issue that only one band would work.

I tried setting the FEC and even the delivery system (S1 rather than S) and it makes no difference. I could try the DVB-S2 NBC mux on that satellite too.. but I'm not sure why that would make a difference.

If you folks have any other ideas, let me know. Thanks for your responses so far!

--Mike

#5 lore raw
Quoted 122 lines · Michael Akey
Quoted 102 lines · Steven Toth
Quoted 90 lines · Lou Otway
Quoted 87 lines · Michael Akey

I can't get the scan/scan-s2 utilities to lock any transponders (DVB-S). My test satellite is AMC1 103W, the Pentagon Channel tp. This is probably
some simple user error on my part, but I can't figure it out.  I have a Corotor II with polarity changed via serial command to an external IRD. C/Ku is switched by 22KHz tone, voltage is always 18V.  Ku is with tone off, C with tone on.  Speaking of which, is there a way to manually set the
tone from the arguments on the scan utilities?

Here's what I've tried and the results:

$ ./scan-s2 -a 0 -v -o zap -l 10750 INIT
API major 5, minor 0
scanning INIT
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder DVB-S  12100000 H 20000000 AUTO AUTO AUTO
initial transponder DVB-S2 12100000 H 20000000 AUTO AUTO AUTO
----------------------------------> Using DVB-S
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

tune to: 12100:h:0:20000

DVB-S IF freq is 1350000

Quoted 12 lines
Quoted 12 lines
Quoted 12 lines

tuning status == 0x03
tuning status == 0x01
tuning status == 0x03
tuning status == 0x01
tuning status == 0x03
tuning status == 0x00
tuning status == 0x01
tuning status == 0x03
tuning status == 0x00
tuning status == 0x00

WARNING: >>> tuning failed!!!

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

tune to: 12100:h:0:20000 (tuning failed)

DVB-S IF freq is 1350000

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

tuning status == 0x03
tuning status == 0x01
tuning status == 0x00
tuning status == 0x00

...snip...

Same thing happens if I use just 'scan' and not 'scan-s2.'

If I use dvbtune, it works though..

$ dvbtune -f 1350000 -p H -s 20000 -c 0 -tone 0 -m
Using DVB card "Conexant CX24116/CX24118"
tuning DVB-S to L-Band:0, Pol:H Srate=20000000, 22kHz=off
polling....
Getting frontend event
FE_STATUS:
polling....
Getting frontend event
FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI
FE_HAS_SYNC
Bit error rate: 0
Signal strength: 51648
SNR: 26215
FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI
FE_HAS_SYNC
Signal=51648, Verror=0, SNR=26215dB, BlockErrors=0, (S|L|C|V|SY|)
Signal=51776, Verror=0, SNR=26624dB, BlockErrors=0, (S|L|C|V|SY|)

The tuning file 'INIT' contains only the following line:
S 12100000 H 20000000 AUTO

I'm using v4l-dvb drivers from the main repo as of about a week ago.  I am
running kernel 2.6.32 on Debian testing.  Any help is appreciated ..and hopefully it's just a simple flub on my part!

Quoted 7 lines
Quoted 2 lines

--Mike

Try using a non-auto FEC and rolloff.

Some devices won't accept auto for these parameters.

Quoted 10 lines

Michael,

The silicon in question doesn't do automatic FEC detection. Be sure to specify which FEC you need for the sat. If in doubt, walk through them all manually. Pilot auto detect is done in s/w was was added a long time ago.

- Steve

Steve et al,

It would appear that it does in fact do auto FEC since I don't specify it with dvbtune and it works just fine (with both my Prof 7300 and 7301.)  I think it's a tone issue, but then again, why does attempting to scan something on both bands C and Ku (tone on, and tone off respectively) not work?  I figured if it's a tone issue that only one band would work.

Quoted 6 lines

I tried setting the FEC and even the delivery system (S1 rather than S) and it makes no difference.  I could try the DVB-S2 NBC mux on that satellite too.. but I'm not sure why that would make a difference.

If you folks have any other ideas, let me know.  Thanks for your responses so far!

It doesn't do auto FEC in S2 mode, only S mode.

Signature · 2 lines
Steven Toth - Kernel Labs
http://www.kernellabs.com
#6 lore raw
In reply to Michael Akey
Quoted 15 lines · Michael Akey
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines

I can't get the scan/scan-s2 utilities to lock any transponders (DVB-S).
My test satellite is AMC1 103W, the Pentagon Channel tp. This is
probably
some simple user error on my part, but I can't figure it out. I have a Corotor II with polarity changed via serial command to an external IRD.
C/Ku is switched by 22KHz tone, voltage is always 18V. Ku is with tone
off, C with tone on. Speaking of which, is there a way to manually set the
tone from the arguments on the scan utilities?

I think
it's a tone issue, but then again, why does attempting to scan something on both bands C and Ku (tone on, and tone off respectively) not work? I figured if it's a tone issue that only one band would work.

Quoted 6 lines

I tried setting the FEC and even the delivery system (S1 rather than S) and it makes no difference. I could try the DVB-S2 NBC mux on that satellite too.. but I'm not sure why that would make a difference.

If you folks have any other ideas, let me know. Thanks for your responses so far!

Hi Mike,

I overlooked your description of your Corotor and IRD earlier, and now, with poor connectivity, I can't really look up the details and match them with my experiences.

I have a switch that is activated by the 22kHz signal and which used to be used for old analogue setups to select between two positions. I'm not sure if there is a discrete component like this in your setup, but if there is, is it possible for you to bypass it and get directly to the C- or Ku-band LNB? Or am I failing to do research to show me this is not possible...

In any case, I'd do what I can to get directly to the LNB. Also, your mention of polarity switching is, well, alien to me. I suspect the card is expecting to use 13V or 18V to get vertical or horizontal polarisation; for circular polarisation I wouldn't know what handedness corresponds to what switching.

Anyway, the 18V you say is constant, would be supplied by the horizontal polarisation. If you're able to get that 22kHz switch out of the way, and scan the Ku-band LNB directly, you ought to be able to see the same results with giving the directly-used frequency values, or subtracting 1 000 000kHz to convert your 10750MHz to the 9750MHz expected by the low-band Universal LNB local oscillator frequency -- the latter normally not generating the 22kHz signal.

I don't know if this will help at all, or if it's possible, and I apologise for my ignorance about your specific dish(es?).

barry bouwsma