Re: no locking on dvb-s2 22000 2/3 8PSK transponder on Astra 19.2E with tt s2-3200

2009-12-16 Thread Matthias Wächter
Am 15.12.2009 20:44, schrieb Newsy Paper:
 yes, this transponder is working again at blog.ors.at they say that they 
 updated the modulator. It is working now again but driver still has this bug, 
 so it's interesting what the update of the modulator changed exactly.

Today I received an answer from Peter Knorr, ORS, where he told me that
when they activated their modulator on 3 Dec 2009, it was set up to
output an inverted spectrum. What they did to fix our issue was to
switch off this inversion.

For me, personally, the issue with 19.2°/11302.75h is closed. Maybe
someone with knowledge about handling STB6100/STB0899 will be able to
finally solve the issue with transponders that have an inverted spectrum.

– Matthias
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: no locking on dvb-s2 22000 2/3 8PSK transponder on Astra 19.2E with tt s2-3200

2009-12-15 Thread Newsy Paper
yes, this transponder is working again at blog.ors.at they say that they 
updated the modulator. It is working now again but driver still has this bug, 
so it's interesting what the update of the modulator changed exactly.

regards

Newsy

--- Oleg Roitburd oroitb...@gmail.com schrieb am Mo, 14.12.2009:

 Von: Oleg Roitburd oroitb...@gmail.com
 Betreff: Re: no locking on dvb-s2 22000 2/3 8PSK transponder on Astra 19.2E  
 with tt s2-3200
 An: Newsy Paper newspaperman_germ...@yahoo.com
 CC: linux-media@vger.kernel.org
 Datum: Montag, 14. Dezember 2009, 13:07
 2009/12/9 Newsy Paper newspaperman_germ...@yahoo.com:
  Hi,
 
  no matter if I use Igors or Manus driver, there's no
 lock on 11303 h 22000 2/3 8psk. Other users at vdr-portal
 report same problem.
 
  The strange thing is that all other transponders that
 use 22000 2/3 8psk do work but this transponder doesn't. It
 worked fine until december 3rd when uplink moved to Vienna.
 I think they changed a parameter like rolloff or inversion
 and the dvb-s2 part of stb6100 is buggy.
 
 It works again. Very strange.
 
 $ sudo ./scan-s2 -x -2 -O S19.2E ORF.ini
 API major 5, minor 0
 scanning ORF.ini
 using '/dev/dvb/adapter0/frontend0' and
 '/dev/dvb/adapter0/demux0'
 initial transponder DVB-S2 11303000 H 2200 2/3 35 8PSK
 -- Using DVB-S2
  tune to: 11303:hC23M5O35S1:S19.2E:22000:
 DVB-S IF freq is 1553000
  parse_section, section number 0 out of 0...!
 service_id = 0x0
 service_id = 0x132F
 pmt_pid = 0x6B
 service_id = 0x1330
 pmt_pid = 0x6C
 service_id = 0x1331
 pmt_pid = 0x6D
  parse_section, section number 0 out of 0...!
   VIDEO     : PID 0x0DFF
   AUDIO     : PID 0x0E00
   AUDIO     : PID 0x0E01
   AC3       : PID 0x0E03
   TELETEXT  : PID 0x0E04
  parse_section, section number 0 out of 0...!
   CA ID     : PID 0x0D05
   CA ID     : PID 0x1702
   CA ID     : PID 0x1833
   CA ID     : PID 0x0648
   CA ID     : PID 0x0D95
   CA ID     : PID 0x09C4
   VIDEO     : PID 0x0B68
   AUDIO     : PID 0x0B69
   AC3       : PID 0x0B6B
   AUDIO     : PID 0x0B6A
   TELETEXT  : PID 0x0B6D
  parse_section, section number 0 out of 0...!
   CA ID     : PID 0x0D05
   CA ID     : PID 0x1702
   CA ID     : PID 0x1833
   CA ID     : PID 0x0648
   CA ID     : PID 0x0D95
   CA ID     : PID 0x09C4
   VIDEO     : PID 0x0780
   AUDIO     : PID 0x0781
   AC3       : PID 0x0783
   AUDIO     : PID 0x0782
   TELETEXT  : PID 0x0785
  parse_section, section number 0 out of 0...!
 0x03EF 0x132F: pmt_pid 0x006B ORF -- ORF1 HD (running,
 scrambled)
 0x03EF 0x1330: pmt_pid 0x006C ORF -- ORF2 HD (running,
 scrambled)
 0x03EF 0x1331: pmt_pid 0x006D ServusTV -- Servus TV HD
 (running)
  parse_section, section number 0 out of 0...!
 dumping lists (3 services)
 ORF1
 HD;ORF:11303:hC23M5O35S1:S19.2E:22000:1920:1921=ger,1922=ENG;1923=ger:1925:D05,1702,1833,648,D95,9C4:4911:1:1007:0
 ORF2
 HD;ORF:11303:hC23M5O35S1:S19.2E:22000:2920:2921=ger,2922=ENG;2923=ger:2925:D05,1702,1833,648,D95,9C4:4912:1:1007:0
 Servus TV
 HD;ServusTV:11303:hC23M5O35S1:S19.2E:22000:3583:3584=ger,3585=eng;3587=ger:3588:0:4913:1:1007:0
 
 Regards
 
 Oleg Roitburd
 

__
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen 
Massenmails. 
http://mail.yahoo.com 
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: no locking on dvb-s2 22000 2/3 8PSK transponder on Astra 19.2E with tt s2-3200

2009-12-14 Thread Oleg Roitburd
2009/12/9 Newsy Paper newspaperman_germ...@yahoo.com:
 Hi,

 no matter if I use Igors or Manus driver, there's no lock on 11303 h 22000 
 2/3 8psk. Other users at vdr-portal report same problem.

 The strange thing is that all other transponders that use 22000 2/3 8psk do 
 work but this transponder doesn't. It worked fine until december 3rd when 
 uplink moved to Vienna. I think they changed a parameter like rolloff or 
 inversion and the dvb-s2 part of stb6100 is buggy.

It works again. Very strange.

$ sudo ./scan-s2 -x -2 -O S19.2E ORF.ini
API major 5, minor 0
scanning ORF.ini
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder DVB-S2 11303000 H 2200 2/3 35 8PSK
-- Using DVB-S2
 tune to: 11303:hC23M5O35S1:S19.2E:22000:
DVB-S IF freq is 1553000
 parse_section, section number 0 out of 0...!
service_id = 0x0
service_id = 0x132F
pmt_pid = 0x6B
service_id = 0x1330
pmt_pid = 0x6C
service_id = 0x1331
pmt_pid = 0x6D
 parse_section, section number 0 out of 0...!
  VIDEO : PID 0x0DFF
  AUDIO : PID 0x0E00
  AUDIO : PID 0x0E01
  AC3   : PID 0x0E03
  TELETEXT  : PID 0x0E04
 parse_section, section number 0 out of 0...!
  CA ID : PID 0x0D05
  CA ID : PID 0x1702
  CA ID : PID 0x1833
  CA ID : PID 0x0648
  CA ID : PID 0x0D95
  CA ID : PID 0x09C4
  VIDEO : PID 0x0B68
  AUDIO : PID 0x0B69
  AC3   : PID 0x0B6B
  AUDIO : PID 0x0B6A
  TELETEXT  : PID 0x0B6D
 parse_section, section number 0 out of 0...!
  CA ID : PID 0x0D05
  CA ID : PID 0x1702
  CA ID : PID 0x1833
  CA ID : PID 0x0648
  CA ID : PID 0x0D95
  CA ID : PID 0x09C4
  VIDEO : PID 0x0780
  AUDIO : PID 0x0781
  AC3   : PID 0x0783
  AUDIO : PID 0x0782
  TELETEXT  : PID 0x0785
 parse_section, section number 0 out of 0...!
0x03EF 0x132F: pmt_pid 0x006B ORF -- ORF1 HD (running, scrambled)
0x03EF 0x1330: pmt_pid 0x006C ORF -- ORF2 HD (running, scrambled)
0x03EF 0x1331: pmt_pid 0x006D ServusTV -- Servus TV HD (running)
 parse_section, section number 0 out of 0...!
dumping lists (3 services)
ORF1 
HD;ORF:11303:hC23M5O35S1:S19.2E:22000:1920:1921=ger,1922=ENG;1923=ger:1925:D05,1702,1833,648,D95,9C4:4911:1:1007:0
ORF2 
HD;ORF:11303:hC23M5O35S1:S19.2E:22000:2920:2921=ger,2922=ENG;2923=ger:2925:D05,1702,1833,648,D95,9C4:4912:1:1007:0
Servus TV 
HD;ServusTV:11303:hC23M5O35S1:S19.2E:22000:3583:3584=ger,3585=eng;3587=ger:3588:0:4913:1:1007:0

Regards

Oleg Roitburd
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


no locking on dvb-s2 22000 2/3 8PSK transponder on Astra 19.2E with tt s2-3200

2009-12-09 Thread Newsy Paper
Hi,

no matter if I use Igors or Manus driver, there's no lock on 11303 h 22000 2/3 
8psk. Other users at vdr-portal report same problem.

The strange thing is that all other transponders that use 22000 2/3 8psk do 
work but this transponder doesn't. It worked fine until december 3rd when 
uplink moved to Vienna. I think they changed a parameter like rolloff or 
inversion and the dvb-s2 part of stb6100 is buggy.

regards

Newspaperman

__
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen 
Massenmails. 
http://mail.yahoo.com 
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: no locking on dvb-s2 22000 2/3 8PSK transponder on Astra 19.2E with tt s2-3200

2009-12-09 Thread Matthias Wächter
Am 09.12.2009 21:15, schrieb Newsy Paper:
 no matter if I use Igors or Manus driver, there's no lock on 11303 h 22000 
 2/3 8psk. Other users at vdr-portal report same problem.
 The strange thing is that all other transponders that use 22000 2/3 8psk do 
 work but this transponder doesn't. It worked fine until december 3rd when 
 uplink moved to Vienna. I think they changed a parameter like rolloff or 
 inversion and the dvb-s2 part of stb6100 is buggy.

Reviewing the code and having enabled debugging options for stb6100, I
am puzzled about the high bandwidth values.

I thought that the bandwidth of the frontend would always be around the
bandwidth of the transponder, plus some minimum locking range. 11303h is
a 26 MHz transponder, so I wonder about the excess in bandwidth: 39.7
MHz is requested, 40 MHz bandwidth is the result. I would expect a value
of 22 MSps * (1+0.35) Hz/S = 29.7 MHz (which is more than the
transponder’s 26 MHz, though ?) but less than 40 MHz as in the example
below. If too much bandwidth hits the decoder, it may be facing aliasing
from neighbor channels, but I don’t know if that is the root cause of
the problems. This is http://jusst.de/hg/v4l-dvb/ as advised by Manu.

Tuning to a 27.500 MSps transponder results in a whoppin’ 62 MHz
bandwidth setting. Is this reasonable?

  kernel: stb6100_set_bandwidth: set bandwidth to 3970 Hz
  kernel: stb6100_write_reg_range: Write @ 0x60: [9:1]
  kernel: stb6100_write_reg_range: FCCK: 0x4d
  kernel: stb6100_write_reg_range: Write @ 0x60: [6:1]
  kernel: stb6100_write_reg_range: F: 0xcf
  kernel: stb6100_write_reg_range: Write @ 0x60: [9:1]
  kernel: stb6100_write_reg_range: FCCK: 0x0d
  kernel: stb6100_read_regs: Read from 0x60
  kernel: stb6100_read_regs: LD: 0x81
  kernel: stb6100_read_regs: VCO: 0x64
  kernel: stb6100_read_regs: NI: 0x34
  kernel: stb6100_read_regs: NF: 0x2f
  kernel: stb6100_read_regs: K: 0x3d
  kernel: stb6100_read_regs: G: 0x39
  kernel: stb6100_read_regs: F: 0xcf
  kernel: stb6100_read_regs: DLB: 0xdc
  kernel: stb6100_read_regs: TEST1: 0x8f
  kernel: stb6100_read_regs: FCCK: 0x0d
  kernel: stb6100_read_regs: LPEN: 0xfb
  kernel: stb6100_read_regs: TEST3: 0xde
  kernel: stb6100_get_bandwidth: bandwidth = 4000 Hz
  kernel: stb6100_read_regs: Read from 0x60
  kernel: stb6100_read_regs: LD: 0x81
  kernel: stb6100_read_regs: VCO: 0x64
  kernel: stb6100_read_regs: NI: 0x34
  kernel: stb6100_read_regs: NF: 0x2f
  kernel: stb6100_read_regs: K: 0x3d
  kernel: stb6100_read_regs: G: 0x39
  kernel: stb6100_read_regs: F: 0xcf
  kernel: stb6100_read_regs: DLB: 0xdc
  kernel: stb6100_read_regs: TEST1: 0x8f
  kernel: stb6100_read_regs: FCCK: 0x0d
  kernel: stb6100_read_regs: LPEN: 0xfb
  kernel: stb6100_read_regs: TEST3: 0xde
  kernel: stb6100_set_frequency: Get frontend parameters
  kernel: stb6100_write_reg_range: Write @ 0x60: [1:11]
  kernel: stb6100_write_reg_range: VCO: 0x64
  kernel: stb6100_write_reg_range: NI: 0x34
  kernel: stb6100_write_reg_range: NF: 0x2f
  kernel: stb6100_write_reg_range: K: 0x3d
  kernel: stb6100_write_reg_range: G: 0x39
  kernel: stb6100_write_reg_range: F: 0xcf
  kernel: stb6100_write_reg_range: DLB: 0xdc
  kernel: stb6100_write_reg_range: TEST1: 0x8f
  kernel: stb6100_write_reg_range: FCCK: 0x0d
  kernel: stb6100_write_reg_range: LPEN: 0xeb
  kernel: stb6100_write_reg_range: TEST3: 0xde
  kernel: stb6100_set_frequency: frequency = 1552000, srate = 2200, g = 9, 
 odiv = 0, psd2 = 1, fxtal = 27000, osm = 6, fvco = 3104000, N(I) = 57, N(F) = 
 247
  kernel: stb6100_write_reg_range: Write @ 0x60: [1:11]
  kernel: stb6100_write_reg_range: VCO: 0xe6
  kernel: stb6100_write_reg_range: NI: 0x39
  kernel: stb6100_write_reg_range: NF: 0xf7
  kernel: stb6100_write_reg_range: K: 0x3c
  kernel: stb6100_write_reg_range: G: 0x39
  kernel: stb6100_write_reg_range: F: 0xcf
  kernel: stb6100_write_reg_range: DLB: 0xdc
  kernel: stb6100_write_reg_range: TEST1: 0x8f
  kernel: stb6100_write_reg_range: FCCK: 0x4d
  kernel: stb6100_write_reg_range: LPEN: 0xeb
  kernel: stb6100_write_reg_range: TEST3: 0xde
  kernel: stb6100_write_reg_range: Write @ 0x60: [10:1]
  kernel: stb6100_write_reg_range: LPEN: 0xfb
  kernel: stb6100_write_reg_range: Write @ 0x60: [1:1]
  kernel: stb6100_write_reg_range: VCO: 0x86
  kernel: stb6100_write_reg_range: Write @ 0x60: [1:1]
  kernel: stb6100_write_reg_range: VCO: 0x66
  kernel: stb6100_write_reg_range: Write @ 0x60: [1:9]
  kernel: stb6100_write_reg_range: VCO: 0x66
  kernel: stb6100_write_reg_range: NI: 0x39
  

Re: no locking on dvb-s2 22000 2/3 8PSK transponder on Astra 19.2E with tt s2-3200

2009-12-09 Thread BOUWSMA Barry
On Wed, 9 Dec 2009, Newsy Paper wrote:

 no matter if I use Igors or Manus driver, there's no lock on 11303 h 22000 
 2/3 8psk. Other users at vdr-portal report same problem.
 
 The strange thing is that all other transponders that use 22000 2/3 8psk do 
 work but this transponder doesn't. It worked fine until december 3rd when 
 uplink moved to Vienna. I think they changed a parameter like rolloff or 
 inversion and the dvb-s2 part of stb6100 is buggy.

Oh jeez, non-wrapping mail...  Anyway, without bothering to see
what I'm replying to, here's the value I get from parsing the
NIT table today:

  Frequency: 18023029 (=  11.30275 GHz)
  Orbital_position: 402 (=  19.2)
  West_East_flag: 1 (0x01)  [= EAST]
  Polarisation: 0 (0x00)  [= linear - horizontal]
  Kind: 1 (0x01)  [= DVB-S2]
  Roll Off Faktor: 0 (0x00)  [= Alpha 0.35]
  Modulation_type: 2 (0x02)  [= 8PSK]
  Symbol_rate: 2228224 (=  22.)
  FEC_inner: 2 (0x02)  [= 2/3 conv. code rate]



Now, I get the following for a different transponder, with a
different roll-off:

  Frequency: 17920117 (=  11.17075 GHz)
  Orbital_position: 402 (=  19.2)
  West_East_flag: 1 (0x01)  [= EAST]
  Polarisation: 0 (0x00)  [= linear - horizontal]
  Kind: 1 (0x01)  [= DVB-S2]
  Roll Off Faktor: 1 (0x01)  [= Alpha 0.25]
  Modulation_type: 2 (0x02)  [= 8PSK]
  Symbol_rate: 2228224 (=  22.)
  FEC_inner: 2 (0x02)  [= 2/3 conv. code rate]


But at the same time I see the same roll-off reported on all
but the 0,25 transponder within the limited NIT table I
nabbed, regardless of 9/10 FEC or 2/3+22000.

I don't know if the above NIT data is 100% accurate, or if
it reflects a change from what it was before.  Actually, I
don't know if I'm parsing everything, because I vaguely
recall there are other selectable options on a real receiver
(which I've never had in front of me) pertaining to pilot
on or off, which apparently affect tuning ability.


barry bouwsma
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html