Hi all,
one more datapoint for the TT 3200 tuning problems. I solved all my
locking problems by add 4MHz to the reported frequencies (coming from
the stream tables); note that one of the transponders always locked
even without this correction (its freq is 11093MHz, the others are :
11555, 11635, 11675MHz), so as you see the others are much higher.
Now there is another transponder at 11495MHz but this one I cant lock
on it even with my correction. Here are its characteristic as reported
by dvbsnoop when tuned to another transponder by szap:
Transport_stream_ID: 605 (0x025d)
Original_network_ID: 1 (0x0001) [= Astra Satellite Network 19,2°E
| Société Européenne des Satellites]
reserved_1: 15 (0x0f)
Transport_descriptor_length: 13 (0x000d)
DVB-DescriptorTag: 67 (0x43) [=
satellite_delivery_system_descriptor]
descriptor_length: 11 (0x0b)
0000: 43 0b 01 14 95 00 32 55 a1 03 00 00 04
C.....2U.....
Frequency: 18126080 (= 11.49500 GHz)
Orbital_position: 12885 (= 325.5)
West_East_flag: 1 (0x01) [= EAST]
Polarisation: 1 (0x01) [= linear - vertical]
Kind: 0 (0x00) [= DVB-S]
fixed ('00'): 0 (0x00)
Modulation_type: 1 (0x01) [= QPSK]
Symbol_rate: 3145728 (= 30.0000)
FEC_inner: 4 (0x04) [= 5/6 conv. code rate]
The difference between this one and the 4 other transponders I can lock
on is that this one has a different FEC (5/6) and the channels on it
are HD, but it is still DVB-S.
I know it works with my STB, so something is wrong here.
I would like to hack on szap or scan to be able to try several freq on
a row and get the logs from it. I will post the result ASAP.
IIRC szapping to the bad channel I get no lock but in the dmesg lock it
seems to get the carrier, weird...
I hope someone can make some sense out of that.
Oh and I am using multiproto as of just before the API change that
broke mythtv compat but I backported some fixes.
Bye
Manu
_______________________________________________
linux-dvb mailing list
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
