Hi,
I built a vdr box, with a Viaccess CAM, to access TPS.
CAM module is detetected correctly.
I can access the smartcard data through the menu.
my ca.conf has a line :
10002 TPS
WHen I try to put a line "CaCaps = 1 10002" in setup.conf , this line is removed when vdr is launched.
I get "Channel not available" when I try to go to a TPS channel.
I run vdr 1.3.36 on a Fedora Core 4 using livna RPMs.
I am lost.
Thank you for your help.
Pierre JUHEN
Pierre JUHEN wrote:
Hi,
I built a vdr box, with a Viaccess CAM, to access TPS.
CAM module is detetected correctly.
I can access the smartcard data through the menu.
my ca.conf has a line :
10002 TPS
WHen I try to put a line "CaCaps = 1 10002" in setup.conf , this line is removed when vdr is launched.
I get "Channel not available" when I try to go to a TPS channel.
I run vdr 1.3.36 on a Fedora Core 4 using livna RPMs.
In VDR 1.3.36 the ca.conf doesn't have much meaning an ymore. Set the CA parameter of the encrypted channel to 0, then tune to it and VDR should automatically detect the CAM and use it.
Klaus
It didn't help much.
Now the channel is available but the screen remains black, no soud.
Here is the trace of the session :
Jan 7 11:14:49 vdr vdr[5144]: VDR version 1.3.36 started Jan 7 11:14:49 vdr vdr[5144]: loading plugin: /usr/lib/vdr/libvdr-mplayer.so.1.3.36 Jan 7 11:14:49 vdr vdr[5144]: loading plugin: /usr/lib/vdr/libvdr-femon.so.1.3.36 Jan 7 11:14:49 vdr vdr[5144]: loading plugin: /usr/lib/vdr/libvdr-remote.so.1.3.36 Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/setup.conf Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/sources.conf Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/diseqc.conf Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/channels.conf Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/timers.conf Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/commands.conf Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/reccmds.conf Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/svdrphosts.conf Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/ca.conf Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/remote.conf Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/keymacros.conf Jan 7 11:14:51 vdr vdr[5144]: found 1 video device Jan 7 11:14:51 vdr vdr[5144]: initializing plugin: mplayer (0.9.13): Media replay via MPlayer Jan 7 11:14:51 vdr vdr[5144]: loading /etc/vdr/plugins/mplayersources.conf Jan 7 11:14:52 vdr vdr[5144]: initializing plugin: femon (0.9.4): DVB Signal Information Monitor (OSD) Jan 7 11:14:52 vdr vdr[5144]: initializing plugin: remote (0.3.3): Remote control Jan 7 11:14:52 vdr vdr[5144]: setting primary device to 1 Jan 7 11:14:52 vdr vdr[5144]: SVDRP listening on port 2001 Jan 7 11:14:52 vdr vdr[5144]: loading /etc/vdr/themes/sttng-default.theme Jan 7 11:14:52 vdr vdr[5144]: starting plugin: mplayer Jan 7 11:14:52 vdr vdr[5144]: starting plugin: femon Jan 7 11:14:52 vdr vdr[5144]: starting plugin: remote Jan 7 11:14:52 vdr vdr[5144]: remote: unable to open '/dev/input/event0': Permission non accord� Jan 7 11:14:52 vdr vdr[5144]: remote: no translation found for '%s: %s' in language 6 (Fran�is) Jan 7 11:14:52 vdr vdr[5144]: ERROR: /dev/input/event0: Permission non accord� Jan 7 11:14:54 vdr vdr[5144]: ERROR: /dev/input/event0: Permission non accord� Jan 7 11:14:56 vdr vdr[5144]: remote: warning: unable to open input device Jan 7 11:14:56 vdr vdr[5144]: loading /etc/vdr/themes/sttng-default.theme Jan 7 11:14:56 vdr vdr[5144]: switching to channel 1 Jan 7 11:15:20 vdr vdr[5144]: CAM: Viaccess, 01, 0500, 0500 ..... Jan 7 11:21:29 vdr vdr[5144]: edited channel 417 TPS Star:10757:vC34:S13.0E:27500:420:430=fra,431=eng:440:0:1204:0:11200:0 Jan 7 11:21:32 vdr vdr[5144]: switching to channel 417 Jan 7 11:21:33 vdr vdr[5144]: retuning due to modification of channel 417 Jan 7 11:21:33 vdr vdr[5144]: switching to channel 417
Thank you
Klaus Schmidinger a écrit :
Pierre JUHEN wrote:
Hi,
I built a vdr box, with a Viaccess CAM, to access TPS.
CAM module is detetected correctly.
I can access the smartcard data through the menu.
my ca.conf has a line :
10002 TPS
WHen I try to put a line "CaCaps = 1 10002" in setup.conf , this line is removed when vdr is launched.
I get "Channel not available" when I try to go to a TPS channel.
I run vdr 1.3.36 on a Fedora Core 4 using livna RPMs.
In VDR 1.3.36 the ca.conf doesn't have much meaning an ymore. Set the CA parameter of the encrypted channel to 0, then tune to it and VDR should automatically detect the CAM and use it.
Klaus
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Pierre JUHEN wrote:
It didn't help much.
Now the channel is available but the screen remains black, no soud.
Here is the trace of the session :
Jan 7 11:14:49 vdr vdr[5144]: VDR version 1.3.36 started Jan 7 11:14:49 vdr vdr[5144]: loading plugin: /usr/lib/vdr/libvdr-mplayer.so.1.3.36 Jan 7 11:14:49 vdr vdr[5144]: loading plugin: /usr/lib/vdr/libvdr-femon.so.1.3.36 Jan 7 11:14:49 vdr vdr[5144]: loading plugin: /usr/lib/vdr/libvdr-remote.so.1.3.36 Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/setup.conf Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/sources.conf Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/diseqc.conf Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/channels.conf Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/timers.conf Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/commands.conf Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/reccmds.conf Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/svdrphosts.conf Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/ca.conf Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/remote.conf Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/keymacros.conf Jan 7 11:14:51 vdr vdr[5144]: found 1 video device Jan 7 11:14:51 vdr vdr[5144]: initializing plugin: mplayer (0.9.13): Media replay via MPlayer Jan 7 11:14:51 vdr vdr[5144]: loading /etc/vdr/plugins/mplayersources.conf Jan 7 11:14:52 vdr vdr[5144]: initializing plugin: femon (0.9.4): DVB Signal Information Monitor (OSD) Jan 7 11:14:52 vdr vdr[5144]: initializing plugin: remote (0.3.3): Remote control Jan 7 11:14:52 vdr vdr[5144]: setting primary device to 1 Jan 7 11:14:52 vdr vdr[5144]: SVDRP listening on port 2001 Jan 7 11:14:52 vdr vdr[5144]: loading /etc/vdr/themes/sttng-default.theme Jan 7 11:14:52 vdr vdr[5144]: starting plugin: mplayer Jan 7 11:14:52 vdr vdr[5144]: starting plugin: femon Jan 7 11:14:52 vdr vdr[5144]: starting plugin: remote Jan 7 11:14:52 vdr vdr[5144]: remote: unable to open '/dev/input/event0': Permission non accord� Jan 7 11:14:52 vdr vdr[5144]: remote: no translation found for '%s: %s' in language 6 (Fran�is) Jan 7 11:14:52 vdr vdr[5144]: ERROR: /dev/input/event0: Permission non accord� Jan 7 11:14:54 vdr vdr[5144]: ERROR: /dev/input/event0: Permission non accord� Jan 7 11:14:56 vdr vdr[5144]: remote: warning: unable to open input device Jan 7 11:14:56 vdr vdr[5144]: loading /etc/vdr/themes/sttng-default.theme Jan 7 11:14:56 vdr vdr[5144]: switching to channel 1 Jan 7 11:15:20 vdr vdr[5144]: CAM: Viaccess, 01, 0500, 0500 ..... Jan 7 11:21:29 vdr vdr[5144]: edited channel 417 TPS Star:10757:vC34:S13.0E:27500:420:430=fra,431=eng:440:0:1204:0:11200:0 Jan 7 11:21:32 vdr vdr[5144]: switching to channel 417 Jan 7 11:21:33 vdr vdr[5144]: retuning due to modification of channel 417 Jan 7 11:21:33 vdr vdr[5144]: switching to channel 417
Are you sure that this channel is currently broadcasting anything?
Klaus
Klaus Schmidinger a écrit :
Pierre JUHEN wrote:
Hi,
I built a vdr box, with a Viaccess CAM, to access TPS.
CAM module is detetected correctly.
I can access the smartcard data through the menu.
my ca.conf has a line :
10002 TPS
WHen I try to put a line "CaCaps = 1 10002" in setup.conf , this line is removed when vdr is launched.
I get "Channel not available" when I try to go to a TPS channel.
I run vdr 1.3.36 on a Fedora Core 4 using livna RPMs.
In VDR 1.3.36 the ca.conf doesn't have much meaning an ymore. Set the CA parameter of the encrypted channel to 0, then tune to it and VDR should automatically detect the CAM and use it.
Klaus
Pierre JUHEN wrote:
Yes, It's a main channel, and I still have the TPS set-top-box : channel is active, and working on the set top box.
Then are you sure that the channel data is correct? When I program this channel here and tune to it, it doesn't make any attempt to update the channel data or CA descriptors.
Klaus
Klaus Schmidinger a écrit :
Are you sure that this channel is currently broadcasting anything?
Yes, all the TPS channels are correct.
The trace I sent was the one when I did what you advise : put the CA parameter to free to air (0) that's why it changed.
Klaus Schmidinger a écrit :
Pierre JUHEN wrote:
Yes, It's a main channel, and I still have the TPS set-top-box : channel is active, and working on the set top box.
Then are you sure that the channel data is correct? When I program this channel here and tune to it, it doesn't make any attempt to update the channel data or CA descriptors.
Klaus
Klaus Schmidinger a écrit :
Are you sure that this channel is currently broadcasting anything?
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Pierre JUHEN wrote:
Yes, all the TPS channels are correct.
The trace I sent was the one when I did what you advise : put the CA parameter to free to air (0) that's why it changed.
Well, then I'm afraid I don't know what else to do.
If you tune to an encrypted channel with CA=0, one of the first things you should see in your log file is soemthing like
changing caids of channel 46 from 0 to 1801,1722,1702
which indicates that VDR has received the current caids and then
retuning due to modification of channel 46
which indicates that it reinitializes the CAM settings for this channel.
Nothing like that happens when I tune to the channel you gave me, that's why I assume that something could be wrong with the channel data.
Klaus
Klaus Schmidinger a écrit :
Pierre JUHEN wrote:
Yes, It's a main channel, and I still have the TPS set-top-box : channel is active, and working on the set top box.
Then are you sure that the channel data is correct? When I program this channel here and tune to it, it doesn't make any attempt to update the channel data or CA descriptors.
Klaus
Klaus Schmidinger a écrit :
Are you sure that this channel is currently broadcasting anything?
I did a fresh scandvb.
EPG is correct for the channel.
I check : I can access the smartcard, it asks for the PIN, I can read it after it accepted the PIN.
But there is nothing like :
changing caids of channel 46 from 0 to 1801,1722,1702
in the logs
I am LOST (in german translations... ;-)))
Thanks, Pierre _________
Klaus Schmidinger a écrit :
Pierre JUHEN wrote:
Yes, all the TPS channels are correct.
The trace I sent was the one when I did what you advise : put the CA parameter to free to air (0) that's why it changed.
Well, then I'm afraid I don't know what else to do.
If you tune to an encrypted channel with CA=0, one of the first things you should see in your log file is soemthing like
changing caids of channel 46 from 0 to 1801,1722,1702
which indicates that VDR has received the current caids and then
retuning due to modification of channel 46
which indicates that it reinitializes the CAM settings for this channel.
Nothing like that happens when I tune to the channel you gave me, that's why I assume that something could be wrong with the channel data.
Klaus
Klaus Schmidinger a écrit :
Pierre JUHEN wrote:
Yes, It's a main channel, and I still have the TPS set-top-box : channel is active, and working on the set top box.
Then are you sure that the channel data is correct? When I program this channel here and tune to it, it doesn't make any attempt to update the channel data or CA descriptors.
Klaus
Klaus Schmidinger a écrit :
Are you sure that this channel is currently broadcasting anything?
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Pierre JUHEN schrieb:
I did a fresh scandvb.
EPG is correct for the channel.
I check : I can access the smartcard, it asks for the PIN, I can read it after it accepted the PIN.
But there is nothing like :
changing caids of channel 46 from 0 to 1801,1722,1702
in the logs
I am LOST (in german translations... ;-)))
Thanks, Pierre _________
Maybe you need to allow VDR to update its channels? (Setup->DVB->Update channels)
Christoph Haubrich wrote:
Pierre JUHEN schrieb:
I did a fresh scandvb.
EPG is correct for the channel.
I check : I can access the smartcard, it asks for the PIN, I can read it after it accepted the PIN.
But there is nothing like :
changing caids of channel 46 from 0 to 1801,1722,1702
in the logs
I am LOST (in german translations... ;-)))
Thanks, Pierre _________
Maybe you need to allow VDR to update its channels? (Setup->DVB->Update channels)
It didn't work here, either, and I have updating channels enabled.
Klaus
Pierre JUHEN wrote:
I did a fresh scandvb.
EPG is correct for the channel.
I check : I can access the smartcard, it asks for the PIN, I can read it after it accepted the PIN.
But there is nothing like :
changing caids of channel 46 from 0 to 1801,1722,1702
in the logs
Well, without this it can't work. Maybe your provider isn't broadcasting these things according to the DVB standard?
Klaus
I am LOST (in german translations... ;-)))
Thanks, Pierre _________
Klaus Schmidinger a écrit :
Pierre JUHEN wrote:
Yes, all the TPS channels are correct.
The trace I sent was the one when I did what you advise : put the CA parameter to free to air (0) that's why it changed.
Well, then I'm afraid I don't know what else to do.
If you tune to an encrypted channel with CA=0, one of the first things you should see in your log file is soemthing like
changing caids of channel 46 from 0 to 1801,1722,1702
which indicates that VDR has received the current caids and then
retuning due to modification of channel 46
which indicates that it reinitializes the CAM settings for this channel.
Nothing like that happens when I tune to the channel you gave me, that's why I assume that something could be wrong with the channel data.
Klaus
Klaus Schmidinger a écrit :
Pierre JUHEN wrote:
Yes, It's a main channel, and I still have the TPS set-top-box : channel is active, and working on the set top box.
Then are you sure that the channel data is correct? When I program this channel here and tune to it, it doesn't make any attempt to update the channel data or CA descriptors.
Klaus
Klaus Schmidinger a écrit :
Are you sure that this channel is currently broadcasting anything?
Klaus Schmidinger Klaus.Schmidinger@cadsoft.de writes:
But there is nothing like : changing caids of channel 46 from 0 to 1801,1722,1702 in the logs
Well, without this it can't work. Maybe your provider isn't broadcasting these things according to the DVB standard?
I don't think so. I receive TPS on my system without a problem.
And I get a lot of "changing caids" messages in my log.
E.g: Jan 7 17:20:14 gandalf vdr[3069]: changing ca descriptors of channel 251 Jan 7 17:20:15 gandalf vdr[3069]: changing caids of channel 1508 from 604,608,500,4AA1 to 0 Jan 7 17:20:15 gandalf vdr[3069]: changing ca descriptors of channel 1508 Jan 7 17:20:15 gandalf vdr[3069]: changing caids of channel 1508 from 0 to 604,608,500,4AA1 Jan 7 17:20:15 gandalf vdr[3069]: changing ca descriptors of channel 1508 Jan 7 17:20:16 gandalf vdr[3069]: changing caids of channel 256 from 606,500,B00 to 0 Jan 7 17:20:16 gandalf vdr[3069]: changing ca descriptors of channel 256
Cheers
Dominique, which vdr version are you running ?
Thank you
Pierre
Dominique Dumont a écrit :
Klaus Schmidinger Klaus.Schmidinger@cadsoft.de writes:
But there is nothing like : changing caids of channel 46 from 0 to 1801,1722,1702 in the logs
Well, without this it can't work. Maybe your provider isn't broadcasting these things according to the DVB standard?
I don't think so. I receive TPS on my system without a problem.
And I get a lot of "changing caids" messages in my log.
E.g: Jan 7 17:20:14 gandalf vdr[3069]: changing ca descriptors of channel 251 Jan 7 17:20:15 gandalf vdr[3069]: changing caids of channel 1508 from 604,608,500,4AA1 to 0 Jan 7 17:20:15 gandalf vdr[3069]: changing ca descriptors of channel 1508 Jan 7 17:20:15 gandalf vdr[3069]: changing caids of channel 1508 from 0 to 604,608,500,4AA1 Jan 7 17:20:15 gandalf vdr[3069]: changing ca descriptors of channel 1508 Jan 7 17:20:16 gandalf vdr[3069]: changing caids of channel 256 from 606,500,B00 to 0 Jan 7 17:20:16 gandalf vdr[3069]: changing ca descriptors of channel 256
Cheers
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Pierre JUHEN pierre.juhen@wanadoo.fr writes:
Dominique, which vdr version are you running ?
I'm running vdr 1.3.37-1.ds for debian patched and packaged by Darren Salt.
Note that if you have a SCM CAM (the red one), 2.6.14 is the minimal kernel version to get a proper initialisation of the CAM.
HTH
Dominique Dumont wrote:
Klaus Schmidinger Klaus.Schmidinger@cadsoft.de writes:
But there is nothing like : changing caids of channel 46 from 0 to 1801,1722,1702 in the logs
Well, without this it can't work. Maybe your provider isn't broadcasting these things according to the DVB standard?
I don't think so. I receive TPS on my system without a problem.
And I get a lot of "changing caids" messages in my log.
E.g: Jan 7 17:20:14 gandalf vdr[3069]: changing ca descriptors of channel 251 Jan 7 17:20:15 gandalf vdr[3069]: changing caids of channel 1508 from 604,608,500,4AA1 to 0 Jan 7 17:20:15 gandalf vdr[3069]: changing ca descriptors of channel 1508 Jan 7 17:20:15 gandalf vdr[3069]: changing caids of channel 1508 from 0 to 604,608,500,4AA1 Jan 7 17:20:15 gandalf vdr[3069]: changing ca descriptors of channel 1508 Jan 7 17:20:16 gandalf vdr[3069]: changing caids of channel 256 from 606,500,B00 to 0 Jan 7 17:20:16 gandalf vdr[3069]: changing ca descriptors of channel 256
Cheers
Can you please post your channels.conf entries for these channels?
Klaus
Klaus Schmidinger Klaus.Schmidinger@cadsoft.de writes:
Dominique Dumont wrote:
Well, without this it can't work. Maybe your provider isn't broadcasting these things according to the DVB standard?
I don't think so. I receive TPS on my system without a problem. And I get a lot of "changing caids" messages in my log. E.g: Jan 7 17:20:14 gandalf vdr[3069]: changing ca descriptors of channel 251 Jan 7 17:20:15 gandalf vdr[3069]: changing caids of channel 1508 from 604,608,500,4AA1 to 0 Jan 7 17:20:15 gandalf vdr[3069]: changing ca descriptors of channel 1508 Jan 7 17:20:15 gandalf vdr[3069]: changing caids of channel 1508 from 0 to 604,608,500,4AA1 Jan 7 17:20:15 gandalf vdr[3069]: changing ca descriptors of channel 1508 Jan 7 17:20:16 gandalf vdr[3069]: changing caids of channel 256 from 606,500,B00 to 0 Jan 7 17:20:16 gandalf vdr[3069]: changing ca descriptors of channel 256 Cheers
Can you please post your channels.conf entries for these channels?
Hmm, these channels are not from TPS. I've been hasty: I picked them randomly from my syslog...
Here are 2 recent ca desc changes that are from TPS with their corresponding channel.conf entry:
Jan 7 18:00:25 gandalf vdr[3069]: changing ca descriptors of channel 14 TPS Cinefamily:10757:vC34:S13.0E:27500:720:730=fra,731=eng:740:1:1207:176:11200:0
Jan 7 18:00:27 gandalf vdr[3069]: changing ca descriptors of channel 11 TPS Star:10757:vC34:S13.0E:27500:420:430=fra,431=eng:440:1:1204:176:11200:0
Note that there are no "caids change" message.
Hope this helps
On Sat, Jan 07, 2006 at 08:22:39PM +0100, Dominique Dumont wrote:
Here are 2 recent ca desc changes that are from TPS with their corresponding channel.conf entry:
TPS Cinefamily:10757:vC34:S13.0E:27500:720:730=fra,731=eng:740:1:1207:176:11200:0 TPS Star:10757:vC34:S13.0E:27500:420:430=fra,431=eng:440:1:1204:176:11200:0
You have something strange here : according to http://www.lyngsat.com/packages/tps.html the frquency should be 10758.
I don't know if your system is wrong or lyngsat ???
Channels.conf has been generated directly by scandvb -o vdr ...
Gregoire Favre a écrit :
On Sat, Jan 07, 2006 at 08:22:39PM +0100, Dominique Dumont wrote:
Here are 2 recent ca desc changes that are from TPS with their corresponding channel.conf entry:
TPS Cinefamily:10757:vC34:S13.0E:27500:720:730=fra,731=eng:740:1:1207:176:11200:0 TPS Star:10757:vC34:S13.0E:27500:420:430=fra,431=eng:440:1:1204:176:11200:0
You have something strange here : according to http://www.lyngsat.com/packages/tps.html the frquency should be 10758.
I don't know if your system is wrong or lyngsat ???
The channels are the same except except you have the code rate (C34).
I have a SCM (red) CAM.
Pierre
Dominique Dumont a écrit :
Klaus Schmidinger Klaus.Schmidinger@cadsoft.de writes:
Dominique Dumont wrote:
Well, without this it can't work. Maybe your provider isn't broadcasting these things according to the DVB standard?
I don't think so. I receive TPS on my system without a problem. And I get a lot of "changing caids" messages in my log. E.g: Jan 7 17:20:14 gandalf vdr[3069]: changing ca descriptors of channel 251 Jan 7 17:20:15 gandalf vdr[3069]: changing caids of channel 1508 from 604,608,500,4AA1 to 0 Jan 7 17:20:15 gandalf vdr[3069]: changing ca descriptors of channel 1508 Jan 7 17:20:15 gandalf vdr[3069]: changing caids of channel 1508 from 0 to 604,608,500,4AA1 Jan 7 17:20:15 gandalf vdr[3069]: changing ca descriptors of channel 1508 Jan 7 17:20:16 gandalf vdr[3069]: changing caids of channel 256 from 606,500,B00 to 0 Jan 7 17:20:16 gandalf vdr[3069]: changing ca descriptors of channel 256 Cheers
Can you please post your channels.conf entries for these channels?
Hmm, these channels are not from TPS. I've been hasty: I picked them randomly from my syslog...
Here are 2 recent ca desc changes that are from TPS with their corresponding channel.conf entry:
Jan 7 18:00:25 gandalf vdr[3069]: changing ca descriptors of channel 14 TPS Cinefamily:10757:vC34:S13.0E:27500:720:730=fra,731=eng:740:1:1207:176:11200:0
Jan 7 18:00:27 gandalf vdr[3069]: changing ca descriptors of channel 11 TPS Star:10757:vC34:S13.0E:27500:420:430=fra,431=eng:440:1:1204:176:11200:0
Note that there are no "caids change" message.
Hope this helps
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Here are the lines :
TPS Cin�tar:10757:v:S13.0E:27500:120:130=fra,131=eng:140:0:1201:176:11200:0 TPS Homecin�a:10757:v:S13.0E:27500:220:230=fra,231=eng:240:1:1202:176:11200:0 TPS Cin�oile:10757:v:S13.0E:27500:320:330=fra,331=eng:340:1:1203:176:11200:0 TPS Star:10757:v:S13.0E:27500:420:430=fra,431=eng:440:1:1204:176:11200:0 TPS Cineculte:10757:v:S13.0E:27500:520:530=fra,531=eng:540:1:1205:176:11200:0 TPS Cinextreme:10757:v:S13.0E:27500:620:630=fra,631=eng:640:1:1206:176:11200:0 TPS Cinefamily:10757:v:S13.0E:27500:720:730=fra,731=eng:740:1:1207:176:11200:0 TPS Cinecomedy:10757:v:S13.0E:27500:820:830=fra,831=eng:840:1:1208:176:11200:0 TPS Cineclub:10757:v:S13.0E:27500:920:930=fra,931=eng:940:1:1209:176:11200:0
What's important ot notice :
I did a fresh scandvb : the CA field was 1 before launching vdr
After launching vdr, the CA field is now 176.
On the screen, TV / OSD, if I force "Free to air", and chooses the channels, and then back to channels setup, the CA field is put to 1280.
???????
Thanks,
Pierre
PS : I run on Fedocra core 4 wis kernel 2.6.14-1.1653_FC4
Klaus Schmidinger a écrit :
Dominique Dumont wrote:
Klaus Schmidinger Klaus.Schmidinger@cadsoft.de writes:
But there is nothing like : changing caids of channel 46 from 0 to 1801,1722,1702 in the logs
Well, without this it can't work. Maybe your provider isn't broadcasting these things according to the DVB standard?
I don't think so. I receive TPS on my system without a problem. And I get a lot of "changing caids" messages in my log.
E.g: Jan 7 17:20:14 gandalf vdr[3069]: changing ca descriptors of channel 251 Jan 7 17:20:15 gandalf vdr[3069]: changing caids of channel 1508 from 604,608,500,4AA1 to 0 Jan 7 17:20:15 gandalf vdr[3069]: changing ca descriptors of channel 1508 Jan 7 17:20:15 gandalf vdr[3069]: changing caids of channel 1508 from 0 to 604,608,500,4AA1 Jan 7 17:20:15 gandalf vdr[3069]: changing ca descriptors of channel 1508 Jan 7 17:20:16 gandalf vdr[3069]: changing caids of channel 256 from 606,500,B00 to 0 Jan 7 17:20:16 gandalf vdr[3069]: changing ca descriptors of channel 256
Cheers
Can you please post your channels.conf entries for these channels?
Klaus
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Pierre JUHEN wrote:
Here are the lines :
TPS Cin�tar:10757:v:S13.0E:27500:120:130=fra,131=eng:140:0:1201:176:11200:0 TPS Homecin�a:10757:v:S13.0E:27500:220:230=fra,231=eng:240:1:1202:176:11200:0 TPS Cin�oile:10757:v:S13.0E:27500:320:330=fra,331=eng:340:1:1203:176:11200:0 TPS Star:10757:v:S13.0E:27500:420:430=fra,431=eng:440:1:1204:176:11200:0 TPS Cineculte:10757:v:S13.0E:27500:520:530=fra,531=eng:540:1:1205:176:11200:0 TPS Cinextreme:10757:v:S13.0E:27500:620:630=fra,631=eng:640:1:1206:176:11200:0 TPS Cinefamily:10757:v:S13.0E:27500:720:730=fra,731=eng:740:1:1207:176:11200:0 TPS Cinecomedy:10757:v:S13.0E:27500:820:830=fra,831=eng:840:1:1208:176:11200:0 TPS Cineclub:10757:v:S13.0E:27500:920:930=fra,931=eng:940:1:1209:176:11200:0
What's important ot notice :
I did a fresh scandvb : the CA field was 1 before launching vdr
After launching vdr, the CA field is now 176.
On the screen, TV / OSD, if I force "Free to air", and chooses the channels, and then back to channels setup, the CA field is put to 1280.
I entered the data of your first channel and tuned to it, but this channel doesn't seem to broadcast any PAT data, so I never get any "changing ca descriptors" log entries.
For a test I tuned to
4funTV:10719:vC34:S13.0E:27500:163:92:0:0:4404:0:0:0
just to see whether I can receive low band vertical transponders on S13.0E at all. I got video and audio right away. However, this transponder also doesn't seem to broadcast any NIT/PAT/SDT data (at least none that VDR recognizes).
Klaus
Klaus Schmidinger wrote:
Pierre JUHEN wrote:
Here are the lines :
TPS
Cin�tar:10757:v:S13.0E:27500:120:130=fra,131=eng:140:0:1201:176:11200:0
TPS
Homecin�a:10757:v:S13.0E:27500:220:230=fra,231=eng:240:1:1202:176:11200: 0
TPS
Cin�oile:10757:v:S13.0E:27500:320:330=fra,331=eng:340:1:1203:176:11200:0
TPS Star:10757:v:S13.0E:27500:420:430=fra,431=eng:440:1:1204:176:11200:0 TPS
Cineculte:10757:v:S13.0E:27500:520:530=fra,531=eng:540:1:1205:176:11200:0
TPS
Cinextreme:10757:v:S13.0E:27500:620:630=fra,631=eng:640:1:1206:176:11200:0
TPS
Cinefamily:10757:v:S13.0E:27500:720:730=fra,731=eng:740:1:1207:176:11200:0
TPS
Cinecomedy:10757:v:S13.0E:27500:820:830=fra,831=eng:840:1:1208:176:11200:0
TPS Cineclub:10757:v:S13.0E:27500:920:930=fra,931=eng:940:1:1209:176:11200:0
What's important ot notice :
I did a fresh scandvb : the CA field was 1 before launching vdr
After launching vdr, the CA field is now 176.
On the screen, TV / OSD, if I force "Free to air", and chooses the channels, and then back to channels setup, the CA field is put to 1280.
I entered the data of your first channel and tuned to it, but this channel doesn't seem to broadcast any PAT data, so I never get any "changing ca descriptors" log entries.
For a test I tuned to
4funTV:10719:vC34:S13.0E:27500:163:92:0:0:4404:0:0:0
just to see whether I can receive low band vertical transponders on S13.0E at all. I got video and audio right away. However, this transponder also doesn't seem to broadcast any NIT/PAT/SDT data (at least none that VDR recognizes).
I just tested it and my vdr updates channel data for these channels:
Jan 8 12:08:33 LFS vdr[4613]: edited channel 1013 4fun.TV;CYFRA +:10719:vC34:S13.0E:27500:163:92=pol,1:0:0:4404:318:11000:0 Jan 8 12:08:35 LFS vdr[4613]: switching to channel 1013 Jan 8 12:08:36 LFS vdr[4613]: changing pids of channel 1013 from 163+163:92=pol,1:0 to 163+163:92=pol:0 Jan 8 12:08:36 LFS vdr[4613]: retuning due to modification of channel 1013 Jan 8 12:08:36 LFS vdr[4613]: switching to channel 1013
Jan 8 12:00:47 LFS vdr[4613]: edited channel 1504 TPS Cinéstar:10758:vC34:S13.0E:27500:120:130=fra,131=eng:140:0:1201:176:11200:0 Jan 8 12:01:00 LFS vdr[4613]: switching to channel 1504 Jan 8 12:01:01 LFS vdr[4613]: changing caids of channel 1504 from 0 to 500,100 Jan 8 12:01:01 LFS vdr[4613]: retuning due to modification of channel 1504 Jan 8 12:01:01 LFS vdr[4613]: switching to channel 1504 Jan 8 12:01:01 LFS vdr[4613]: info: Kanal nicht verfügbar!
Here comes Channel not available, of course, because I have no CAM.
I think your problem is, that nid/tid of your channels.conf entry are wrong (0:0). VDR probably added a second version of these channels with the right nid/tid values.
Greetings, Thomas
Thomas Bergwinkl wrote:
Klaus Schmidinger wrote: ...
I entered the data of your first channel and tuned to it, but this channel doesn't seem to broadcast any PAT data, so I never get any "changing ca descriptors" log entries.
For a test I tuned to
4funTV:10719:vC34:S13.0E:27500:163:92:0:0:4404:0:0:0
just to see whether I can receive low band vertical transponders on S13.0E at all. I got video and audio right away. However, this transponder also doesn't seem to broadcast any NIT/PAT/SDT data (at least none that VDR recognizes).
I just tested it and my vdr updates channel data for these channels:
Jan 8 12:08:33 LFS vdr[4613]: edited channel 1013 4fun.TV;CYFRA +:10719:vC34:S13.0E:27500:163:92=pol,1:0:0:4404:318:11000:0 Jan 8 12:08:35 LFS vdr[4613]: switching to channel 1013 Jan 8 12:08:36 LFS vdr[4613]: changing pids of channel 1013 from 163+163:92=pol,1:0 to 163+163:92=pol:0 Jan 8 12:08:36 LFS vdr[4613]: retuning due to modification of channel 1013 Jan 8 12:08:36 LFS vdr[4613]: switching to channel 1013
Jan 8 12:00:47 LFS vdr[4613]: edited channel 1504 TPS Cinéstar:10758:vC34:S13.0E:27500:120:130=fra,131=eng:140:0:1201:176:11200:0 Jan 8 12:01:00 LFS vdr[4613]: switching to channel 1504 Jan 8 12:01:01 LFS vdr[4613]: changing caids of channel 1504 from 0 to 500,100 Jan 8 12:01:01 LFS vdr[4613]: retuning due to modification of channel 1504 Jan 8 12:01:01 LFS vdr[4613]: switching to channel 1504 Jan 8 12:01:01 LFS vdr[4613]: info: Kanal nicht verfügbar!
Here comes Channel not available, of course, because I have no CAM.
I think your problem is, that nid/tid of your channels.conf entry are wrong (0:0). VDR probably added a second version of these channels with the right nid/tid values.
Greetings, Thomas
You're absolutely right - I already had these channels in my channels.conf, so adding them again with NID/TID both 0 didn't give the expected result.
When I tune to the channels I already have in my channels.conf, everything works just fine.
Klaus
On a practical point of vue, what shall I do ?
. Edit manually channels.conf based on ??? (Lyngsat) ?
Thanks
Pierre
Klaus Schmidinger a écrit :
Thomas Bergwinkl wrote:
Klaus Schmidinger wrote: ...
I entered the data of your first channel and tuned to it, but this channel doesn't seem to broadcast any PAT data, so I never get any "changing ca descriptors" log entries.
For a test I tuned to
4funTV:10719:vC34:S13.0E:27500:163:92:0:0:4404:0:0:0
just to see whether I can receive low band vertical transponders on S13.0E at all. I got video and audio right away. However, this transponder also doesn't seem to broadcast any NIT/PAT/SDT data (at least none that VDR recognizes).
I just tested it and my vdr updates channel data for these channels: Jan 8 12:08:33 LFS vdr[4613]: edited channel 1013 4fun.TV;CYFRA +:10719:vC34:S13.0E:27500:163:92=pol,1:0:0:4404:318:11000:0 Jan 8 12:08:35 LFS vdr[4613]: switching to channel 1013 Jan 8 12:08:36 LFS vdr[4613]: changing pids of channel 1013 from 163+163:92=pol,1:0 to 163+163:92=pol:0 Jan 8 12:08:36 LFS vdr[4613]: retuning due to modification of channel 1013 Jan 8 12:08:36 LFS vdr[4613]: switching to channel 1013
Jan 8 12:00:47 LFS vdr[4613]: edited channel 1504 TPS Cinéstar:10758:vC34:S13.0E:27500:120:130=fra,131=eng:140:0:1201:176:11200:0
Jan 8 12:01:00 LFS vdr[4613]: switching to channel 1504 Jan 8 12:01:01 LFS vdr[4613]: changing caids of channel 1504 from 0 to 500,100 Jan 8 12:01:01 LFS vdr[4613]: retuning due to modification of channel 1504 Jan 8 12:01:01 LFS vdr[4613]: switching to channel 1504 Jan 8 12:01:01 LFS vdr[4613]: info: Kanal nicht verfügbar!
Here comes Channel not available, of course, because I have no CAM.
I think your problem is, that nid/tid of your channels.conf entry are wrong (0:0). VDR probably added a second version of these channels with the right nid/tid values.
Greetings, Thomas
You're absolutely right - I already had these channels in my channels.conf, so adding them again with NID/TID both 0 didn't give the expected result.
When I tune to the channels I already have in my channels.conf, everything works just fine.
Klaus
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Pierre JUHEN wrote:
On a practical point of vue, what shall I do ?
. Edit manually channels.conf based on ??? (Lyngsat) ?
Make sure your channels are in your channels list ony _once_. The it should work.
Klaus
Klaus Schmidinger a écrit :
Thomas Bergwinkl wrote:
Klaus Schmidinger wrote: ...
I entered the data of your first channel and tuned to it, but this channel doesn't seem to broadcast any PAT data, so I never get any "changing ca descriptors" log entries.
For a test I tuned to
4funTV:10719:vC34:S13.0E:27500:163:92:0:0:4404:0:0:0
just to see whether I can receive low band vertical transponders on S13.0E at all. I got video and audio right away. However, this transponder also doesn't seem to broadcast any NIT/PAT/SDT data (at least none that VDR recognizes).
I just tested it and my vdr updates channel data for these channels: Jan 8 12:08:33 LFS vdr[4613]: edited channel 1013 4fun.TV;CYFRA +:10719:vC34:S13.0E:27500:163:92=pol,1:0:0:4404:318:11000:0 Jan 8 12:08:35 LFS vdr[4613]: switching to channel 1013 Jan 8 12:08:36 LFS vdr[4613]: changing pids of channel 1013 from 163+163:92=pol,1:0 to 163+163:92=pol:0 Jan 8 12:08:36 LFS vdr[4613]: retuning due to modification of channel 1013 Jan 8 12:08:36 LFS vdr[4613]: switching to channel 1013
Jan 8 12:00:47 LFS vdr[4613]: edited channel 1504 TPS Cinéstar:10758:vC34:S13.0E:27500:120:130=fra,131=eng:140:0:1201:176:11200:0
Jan 8 12:01:00 LFS vdr[4613]: switching to channel 1504 Jan 8 12:01:01 LFS vdr[4613]: changing caids of channel 1504 from 0 to 500,100 Jan 8 12:01:01 LFS vdr[4613]: retuning due to modification of channel 1504 Jan 8 12:01:01 LFS vdr[4613]: switching to channel 1504 Jan 8 12:01:01 LFS vdr[4613]: info: Kanal nicht verfügbar!
Here comes Channel not available, of course, because I have no CAM.
I think your problem is, that nid/tid of your channels.conf entry are wrong (0:0). VDR probably added a second version of these channels with the right nid/tid values.
Greetings, Thomas
You're absolutely right - I already had these channels in my channels.conf, so adding them again with NID/TID both 0 didn't give the expected result.
When I tune to the channels I already have in my channels.conf, everything works just fine.
Klaus
Not much time since my last post, but :
1/ I updated the kernel to 2.6.15
2/ Checked that there is only one line per channel in channels.conf.
Up to now, no success.
Could it be linked to the CAM firmware : I have a Viaccces red label CAM, whose hardware is 1.04.
Thanks,
Pierre JUHEN
I updated the CIM using the method described in http://www.scmmicro.com/support/dtv_faq.html. http://www.scmmicro.com/support/dtv_faq.html
Good news, the method works, I am now in version 1.08, which is said to be compatible with TPS.
Effectively, the behavior changes :
VDR asks for the CAM to be inserted.
But it answers now "No right".
Shall I wait longer to get rights from the air ?
Has it to do with the maturity (set to 15) on the CAM ?
Thank you for your help ?
Pierre JUHEN
Pierre JUHEN pierre.juhen@wanadoo.fr writes:
I updated the CIM using the method described in http://www.scmmicro.com/support/dtv_faq.html
Good news, the method works, I am now in version 1.08, which is said to be compatible with TPS.
Interesting. Did you use vdr or another set top box to update the firmware of the CAM ?
Cheers
Pierre JUHEN pierre.juhen@wanadoo.fr writes:
I updated the CIM using the method described in http://www.scmmicro.com/support/dtv_faq.html
Good news, the method works, I am now in version 1.08, which is said to be compatible with TPS.
Interesting. Did you use vdr or another set top box to update the firmware of the CAM ?
Cheers
Hi again,
I did the manipulations described in Developer/cams.txt.
Step 1 through 6 are OK.
Step 7 and up do not occur.
My configuration :
Hauppauge Nexus-S ver 2.1 or 2.2 Viaccess Red module ver appl 1.08 (latest) Smartcard TPS
Kernel 2.6.15 vdr 1.3.37
Could someone help me to go further ?
Thanks,
Pierre
Included a log showing step 1 through 5
Pierre JUHEN wrote:
Hi again,
I did the manipulations described in Developer/cams.txt.
Step 1 through 6 are OK.
Step 7 and up do not occur.
My configuration :
Hauppauge Nexus-S ver 2.1 or 2.2 Viaccess Red module ver appl 1.08 (latest) Smartcard TPS
Kernel 2.6.15 vdr 1.3.37
Could someone help me to go further ?
Thanks,
Pierre
Included a log showing step 1 through 5
Resetting slot 0...ok. Resetting slot 1...ok. Module ready in slot 0 Creating connection: slot 0, tcid 1 9 --> 00 01 82 01 01 9 <-- 00 01 83 01 01 80 02 01 00 . . . . . . . . . 9 --> 00 01 A0 01 01 9 <-- 00 01 80 02 01 80 . . . . . . 9 --> 00 01 81 01 01 9 <-- 00 01 A0 07 01 91 04 00 01 00 41 80 02 01 00 . . . . . . . . . . A . . . . OpenSession 00010041 New Resource Manager (session id 1) 9 --> 00 01 A0 0A 01 92 07 00 00 01 00 41 00 01 9 <-- 00 01 80 02 01 00 . . . . . . 1: ==> Profile Enq 9 --> 00 01 A0 09 01 90 02 00 01 9F 80 10 00 9 <-- 00 01 80 02 01 00 . . . . . . 9 --> 00 01 A0 01 01 9 <-- 00 01 80 02 01 80 . . . . . . 9 --> 00 01 81 01 01 9 <-- 00 01 A0 82 00 09 01 90 02 00 01 9F 80 11 00 80 02 01 00 . . . . . . . . . . . . . . . . . . . 1: <== Profile 1: ==> Profile Change 9 --> 00 01 A0 09 01 90 02 00 01 9F 80 12 00 9 <-- 00 01 80 02 01 00 . . . . . . 9 --> 00 01 A0 01 01 9 <-- 00 01 80 02 01 80 . . . . . . 9 --> 00 01 81 01 01 9 <-- 00 01 A0 82 00 09 01 90 02 00 01 9F 80 10 00 80 02 01 00 . . . . . . . . . . . . . . . . . . . 1: <== Profile Enquiry 1: ==> Profile 9 --> 00 01 A0 1D 01 90 02 00 01 9F 80 11 14 00 01 00 41 00 02 00 41 00 03 00 41 00 24 00 41 00 40 00 41 9 <-- 00 01 80 02 01 00 . . . . . . 9 --> 00 01 A0 01 01 9 <-- 00 01 80 02 01 80 . . . . . . 9 --> 00 01 81 01 01 9 <-- 00 01 A0 07 01 91 04 00 02 00 41 80 02 01 00 . . . . . . . . . . A . . . . OpenSession 00020041 New Application Information (session id 2) 9 --> 00 01 A0 0A 01 92 07 00 00 02 00 41 00 02 9 <-- 00 01 80 02 01 00 . . . . . . 2: ==> Application Info Enq 9 --> 00 01 A0 09 01 90 02 00 02 9F 80 20 00 9 <-- 00 01 80 02 01 00 . . . . . . 9 --> 00 01 A0 01 01 9 <-- 00 01 80 02 01 80 . . . . . . 9 --> 00 01 81 01 01 9 <-- 00 01 A0 82 00 17 01 90 02 00 02 9F 80 21 0E 01 05 00 05 00 08 56 69 61 63 63 65 73 73 80 02 01 00 . . . . . . . . . . . . . ! . . . . . . . V i a c c e s s . . . . 2: <== Application Info 9 --> 00 01 A0 01 01 9 <-- 00 01 80 02 01 80 . . . . . . 9 --> 00 01 81 01 01 9 <-- 00 01 A0 07 01 91 04 00 03 00 41 80 02 01 00 . . . . . . . . . . A . . . . OpenSession 00030041 New Conditional Access Support (session id 3) 9 --> 00 01 A0 0A 01 92 07 00 00 03 00 41 00 03 9 <-- 00 01 80 02 01 00 . . . . . . 3: ==> Ca Info Enq 9 --> 00 01 A0 09 01 90 02 00 03 9F 80 30 00 9 <-- 00 01 80 02 01 00 . . . . . . 9 --> 00 01 A0 01 01 9 <-- 00 01 80 02 01 80 . . . . . . 9 --> 00 01 81 01 01 9 <-- 00 01 A0 82 00 0B 01 90 02 00 03 9F 80 31 02 05 00 80 02 01 00 . . . . . . . . . . . . . 1 . . . . . . . 3: <== Ca Info 0500 9 --> 00 01 A0 01 01 9 <-- 00 01 80 02 01 80 . . . . . . 9 --> 00 01 81 01 01 9 <-- 00 01 A0 07 01 91 04 00 24 00 41 80 02 01 00 . . . . . . . . $ . A . . . . OpenSession 00240041 New Date Time (session id 4) 9 --> 00 01 A0 0A 01 92 07 00 00 24 00 41 00 04 9 <-- 00 01 80 02 01 00 . . . . . . 9 --> 00 01 A0 01 01 9 <-- 00 01 80 02 01 80 . . . . . . 9 --> 00 01 81 01 01 9 <-- 00 01 A0 82 00 0A 01 90 02 00 04 9F 84 40 01 0A 80 02 01 00 . . . . . . . . . . . . . @ . . . . . . 4: <== Date Time Enq, interval = 10 4: ==> Date Time 9 --> 00 01 A0 10 01 90 02 00 04 9F 84 41 07 D1 FD 08 18 46 00 00 9 <-- 00 01 80 02 01 00 . . . . . . 9 --> 00 01 A0 01 01 9 <-- 00 01 80 02 01 00 . . . . . . 9 --> 00 01 A0 01 01 9 <-- 00 01 80 02 01 00 . . . . . . 3: ==> Ca Pmt 9 --> 00 01 A0 82 01 BB 01 90 02 00 03 9F 80 32 82 01 B0 03 04 B4 01 00 00 02 01 A4 00 89 01 09 0F 05 00 E1 CC 10 01 00 13 01 20 14 03 00 7C 08 09 0F 05 00 E1 CE 10 01 00 13 01 20 14 03 02 26 08 09 0F 05 00 E1 D0 10 01 00 13 01 20 14 03 00 81 08 09 0F 05 00 E1 D1 10 01 00 13 01 20 14 03 01 50 08 09 0F 05 00 E1 D4 10 01 00 13 01 20 14 03 02 00 08 09 0F 05 00 E1 D5 10 01 00 13 01 20 14 03 00 83 08 09 0F 05 00 E1 CD 10 01 00 13 01 20 14 03 02 26 18 09 0F 05 00 E1 D7 10 01 00 13 01 20 14 03 02 00 18 04 01 AE 00 89 01 09 0F 05 00 E1 CC 10 01 00 13 01 20 14 03 00 7C 08 09 0F 05 00 E1 CE 10 01 00 13 01 20 14 03 02 26 08 09 0F 05 00 E1 D0 10 01 00 13 01 20 14 03 00 81 08 09 0F 05 00 E1 D1 10 01 00 13 01 20 14 03 01 50 08 09 0F 05 00 E1 D4 10 01 00 13 01 20 14 03 02 00 08 ...
This CA_PMT data appears rather long.
What is the channels.conf entry of this channel?
Klaus
9 <-- 00 01 80 02 01 00 . . . . . . 9 --> 00 01 A0 01 01 9 <-- 00 01 80 02 01 00 . . . . . . 9 --> 00 01 A0 01 01 9 <-- 00 01 80 02 01 80 . . . . . . 9 --> 00 01 81 01 01 9 <-- 00 01 A0 07 01 91 04 00 40 00 41 80 02 01 00 . . . . . . . . @ . A . . . . OpenSession 00400041 New MMI (session id 5) 9 --> 00 01 A0 0A 01 92 07 00 00 40 00 41 00 05 9 <-- 00 01 80 02 01 00 . . . . . . 9 --> 00 01 A0 01 01 9 <-- 00 01 80 02 01 80 . . . . . . 9 --> 00 01 81 01 01 9 <-- 00 01 A0 82 00 0B 01 90 02 00 05 9F 88 01 02 01 01 80 02 01 00 . . . . . . . . . . . . . . . . . . . . . 5: <== Display Control 5: ==> Display Reply 9 --> 00 01 A0 0B 01 90 02 00 05 9F 88 02 02 01 01 9 <-- 00 01 80 02 01 00 . . . . . . 9 --> 00 01 A0 01 01 9 <-- 00 01 80 02 01 80 . . . . . . 9 --> 00 01 81 01 01 9 <-- 00 01 A0 82 00 50 01 90 02 00 05 9F 88 0C 82 00 45 01 9F 88 03 0F 56 69 61 63 63 65 73 73 20 4D 6F 64 75 6C 65 9F 88 03 00 9F 88 03 1D 4F 4B 20 74 6F 20 72 65 74 75 72 6E 20 74 6F 20 74 68 65 20 4D 61 69 6E 20 6D 65 6E 75 9F 88 03 08 4E 6F 20 72 69 67 68 74 80 02 01 00 . . . . . P . . . . . . . . . . E . . . . . V i a c c e s s M o d u l e . . . . . . . . O K t o r e t u r n t o t h e M a i n m e n u . . . . N o r i g h t . . . . 5: <== Menu Last 5: <== Text Last 'Viaccess Module' 5: <== Text Last '' 5: <== Text Last 'OK to return to the Main menu' 5: <== Text Last 'No right' 9 --> 00 01 A0 01 01 9 <-- 00 01 80 02 01 00 . . . . . . 5: ==> Close MMI 9 --> 00 01 A0 09 01 90 02 00 05 9F 88 00 00 9 <-- 00 01 80 02 01 00 . . . . . . 9 --> 00 01 A0 01 01 9 <-- 00 01 80 02 01 80 . . . . . . 9 --> 00 01 81 01 01 9 <-- 00 01 A0 05 01 95 02 00 05 80 02 01 00 . . . . . . . . . . . . . CloseSession 00000005 9 --> 00 01 A0 06 01 96 03 00 00 05 9 <-- 00 01 80 02 01 00 . . . . . . 9 --> 00 01 A0 01 01 9 <-- 00 01 80 02 01 00 . . . . . . 4: ==> Date Time 9 --> 00 01 A0 10 01 90 02 00 04 9F 84 41 07 D1 FD 08 18 57 00 00 9 <-- 00 01 80 02 01 00 . . . . . . 9 --> 00 01 A0 01 01 9 <-- 00 01 80 02 01 00 . . . . . . 9 --> 00 01 A0 01 01 9 <-- 00 01 80 02 01 00 . . . . . . 9 --> 00 01 A0 01 01 9 <-- 00 01 80 02 01 00 . . . . . . 9 --> 00 01 A0 01 01 9 <-- 00 01 80 02 01 00
Thank you Klaus, for your support.
Here is the channels.conf entry
TPS Star:10757:v:S13.0E:27500:420:430=fra,431=eng:440:1:1204:176:11200:0
Smartcard works perfectly on my plain TPS set-top-box, it's a legal one.
Thank you again.
Pierre
Klaus Schmidinger a écrit :
Pierre JUHEN wrote:
Hi again,
I did the manipulations described in Developer/cams.txt.
Step 1 through 6 are OK.
St . . . . . . 3: ==> Ca Pmt 9 --> 00 01 A0 82 01 BB 01 90 02 00 03 9F 80 32 82 01 B0 03 04 B4 01 00 00 02 01 A4 00 89 01 09 0F 05 00 E1 CC 10 01 00 13 01 20 14 03 00 7C 08 09 0F 05 00 E1 CE 10 01 00 13 01 20 14 03 02 26 08 09 0F 05 00 E1 D0 10 01 00 13 01 20 14 03 00 81 08 09 0F 05 00 E1 D1 10 01 00 13 01 20 14 03 01 50 08 09 0F 05 00 E1 D4 10 01 00 13 01 20 14 03 02 00 08 09 0F 05 00 E1 D5 10 01 00 13 01 20 14 03 00 83 08 09 0F 05 00 E1 CD 10 01 00 13 01 20 14 03 02 26 18 09 0F 05 00 E1 D7 10 01 00 13 01 20 14 03 02 00 18 04 01 AE 00 89 01 09 0F 05 00 E1 CC 10 01 00 13 01 20 14 03 00 7C 08 09 0F 05 00 E1 CE 10 01 00 13 01 20 14 03 02 26 08 09 0F 05 00 E1 D0 10 01 00 13 01 20 14 03 00 81 08 09 0F 05 00 E1 D1 10 01 00 13 01 20 14 03 01 50 08 09 0F 05 00 E1 D4 10 01 00 13 01 20 14 03 02 00 08 ...
This CA_PMT data appears rather long.
What is the channels.conf entry of this channel?
Klaus
Pierre JUHEN wrote:
Thank you Klaus, for your support.
Here is the channels.conf entry
TPS Star:10757:v:S13.0E:27500:420:430=fra,431=eng:440:1:1204:176:11200:0
Looks ok. When I tune to that channel my VDR also sends such a lengthy CA_PMT to the CAM, and when I activate DEBUG_CA_DESCRIPTORS in pat.c I can see that these are actually ok.
Smartcard works perfectly on my plain TPS set-top-box, it's a legal one.
Maybe they did something that allows your smartcard to work _only_ in the TPS set-top-box, and not in a CAM?
Klaus
Klaus Schmidinger a écrit :
Pierre JUHEN wrote:
Hi again,
I did the manipulations described in Developer/cams.txt.
Step 1 through 6 are OK.
St . . . . . . 3: ==> Ca Pmt 9 --> 00 01 A0 82 01 BB 01 90 02 00 03 9F 80 32 82 01 B0 03 04 B4 01 00 00 02 01 A4 00 89 01 09 0F 05 00 E1 CC 10 01 00 13 01 20 14 03 00 7C 08 09 0F 05 00 E1 CE 10 01 00 13 01 20 14 03 02 26 08 09 0F 05 00 E1 D0 10 01 00 13 01 20 14 03 00 81 08 09 0F 05 00 E1 D1 10 01 00 13 01 20 14 03 01 50 08 09 0F 05 00 E1 D4 10 01 00 13 01 20 14 03 02 00 08 09 0F 05 00 E1 D5 10 01 00 13 01 20 14 03 00 83 08 09 0F 05 00 E1 CD 10 01 00 13 01 20 14 03 02 26 18 09 0F 05 00 E1 D7 10 01 00 13 01 20 14 03 02 00 18 04 01 AE 00 89 01 09 0F 05 00 E1 CC 10 01 00 13 01 20 14 03 00 7C 08 09 0F 05 00 E1 CE 10 01 00 13 01 20 14 03 02 26 08 09 0F 05 00 E1 D0 10 01 00 13 01 20 14 03 00 81 08 09 0F 05 00 E1 D1 10 01 00 13 01 20 14 03 01 50 08 09 0F 05 00 E1 D4 10 01 00 13 01 20 14 03 02 00 08 ...
This CA_PMT data appears rather long.
What is the channels.conf entry of this channel?
Klaus
Thank you Klaus.
My smartcard is quite old, too old.
Maybe the set-top-box does something to manage the compatibilty between the compability between the stream and the smartcard.
I will ask TPS.
Regards,
Pierre
Klaus,
I looked on the internet.
My smartcard has been here since 1999.
In 2002, TPS went from Viaccess I to Viaccess II.
On the non-TPS terminal, they had to retrofit the smartcard.
On the TPS terminal, I guess there is a "patch" to trick the smartcard.
This patch is of course non present on vdr.
Thank you again for your support.
Pierre
Pierre JUHEN pierre.juhen@wanadoo.fr writes:
Smartcard works perfectly on my plain TPS set-top-box, it's a legal one.
Whoa there ! To receive TPS on STB others than the device rented by TPS, you need to change your subscription to get a "carte W" which is different from the regular smard card provided by TPS.
We can discuss details off-line if you want.
Cheers
Post scriptum : on the OSD, the scrambling data is 1280, which is 0x500.
This seems coherent with the Viaccess CAM: 010,0500,0500 in the /var/log/messages
I upgraded many things on my vdr box :
kernel -> 2.6.15 vdr -> 1.3.37 Viaccess module -> 1.08
(Some forums said version 1.04 module was not compatible with TPS, that's why I upgraded).
As expected, it changed the things.
But I still cannot access to TPS channels.
Now, if I tune to a TPS channel : I have a "Viaccess module : No right, click to OK to go back to the main menu".
If I remove the smartcard : it says "Viaccess module : please insert your smartcard".
I can read the smart card data, it checks the pincode OK.
I don't understand.
Please help me.
Thank you
Pierre JUHEN
Hello Pierre,
On Sat, 07 Jan 2006 14:33:10 +0100 Pierre JUHEN pierre.juhen@wanadoo.fr wrote:
| It didn't help much. | | Now the channel is available but the screen remains black, no soud. | | Here is the trace of the session : | | Jan 7 11:14:49 vdr vdr[5144]: VDR version 1.3.36 started | Jan 7 11:14:49 vdr vdr[5144]: loading plugin: | /usr/lib/vdr/libvdr-mplayer.so.1.3.36 | Jan 7 11:14:49 vdr vdr[5144]: loading plugin: | /usr/lib/vdr/libvdr-femon.so.1.3.36 | Jan 7 11:14:49 vdr vdr[5144]: loading plugin: | /usr/lib/vdr/libvdr-remote.so.1.3.36 | Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/setup.conf | Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/sources.conf | Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/diseqc.conf | Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/channels.conf | Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/timers.conf | Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/commands.conf | Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/reccmds.conf | Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/svdrphosts.conf | Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/ca.conf | Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/remote.conf | Jan 7 11:14:49 vdr vdr[5144]: loading /etc/vdr/keymacros.conf | Jan 7 11:14:51 vdr vdr[5144]: found 1 video device | Jan 7 11:14:51 vdr vdr[5144]: initializing plugin: mplayer (0.9.13): | Media replay via MPlayer | Jan 7 11:14:51 vdr vdr[5144]: loading /etc/vdr/plugins/mplayersources.conf | Jan 7 11:14:52 vdr vdr[5144]: initializing plugin: femon (0.9.4): DVB | Signal Information Monitor (OSD) | Jan 7 11:14:52 vdr vdr[5144]: initializing plugin: remote (0.3.3): | Remote control | Jan 7 11:14:52 vdr vdr[5144]: setting primary device to 1 | Jan 7 11:14:52 vdr vdr[5144]: SVDRP listening on port 2001 | Jan 7 11:14:52 vdr vdr[5144]: loading /etc/vdr/themes/sttng-default.theme | Jan 7 11:14:52 vdr vdr[5144]: starting plugin: mplayer | Jan 7 11:14:52 vdr vdr[5144]: starting plugin: femon | Jan 7 11:14:52 vdr vdr[5144]: starting plugin: remote | Jan 7 11:14:52 vdr vdr[5144]: remote: unable to open | '/dev/input/event0': Permission non accord� | Jan 7 11:14:52 vdr vdr[5144]: remote: no translation found for '%s: %s' | in language 6 (Fran�is) | Jan 7 11:14:52 vdr vdr[5144]: ERROR: /dev/input/event0: Permission non | accord� | Jan 7 11:14:54 vdr vdr[5144]: ERROR: /dev/input/event0: Permission non | accord�
Looks like you have permission issue for /dev/input/event0. Fix that first
Thanks,
Philippe
| Jan 7 11:14:56 vdr vdr[5144]: remote: warning: unable to open input device | Jan 7 11:14:56 vdr vdr[5144]: loading /etc/vdr/themes/sttng-default.theme | Jan 7 11:14:56 vdr vdr[5144]: switching to channel 1 | Jan 7 11:15:20 vdr vdr[5144]: CAM: Viaccess, 01, 0500, 0500 | ..... | Jan 7 11:21:29 vdr vdr[5144]: edited channel 417 TPS | Star:10757:vC34:S13.0E:27500:420:430=fra,431=eng:440:0:1204:0:11200:0 | Jan 7 11:21:32 vdr vdr[5144]: switching to channel 417 | Jan 7 11:21:33 vdr vdr[5144]: retuning due to modification of channel 417 | Jan 7 11:21:33 vdr vdr[5144]: switching to channel 417 | | Thank you | | Klaus Schmidinger a écrit : | | > Pierre JUHEN wrote: | > | >> Hi, | >> | >> I built a vdr box, with a Viaccess CAM, to access TPS. | >> | >> CAM module is detetected correctly. | >> | >> I can access the smartcard data through the menu. | >> | >> my ca.conf has a line : | >> | >> 10002 TPS | >> | >> WHen I try to put a line "CaCaps = 1 10002" in setup.conf , this line | >> is removed | >> when vdr is launched. | >> | >> I get "Channel not available" when I try to go to a TPS channel. | >> | >> I run vdr 1.3.36 on a Fedora Core 4 using livna RPMs. | > | > | > In VDR 1.3.36 the ca.conf doesn't have much meaning an ymore. | > Set the CA parameter of the encrypted channel to 0, then tune to | > it and VDR should automatically detect the CAM and use it. | > | > Klaus | > | > _______________________________________________ | > vdr mailing list | > vdr@linuxtv.org | > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr | > | > | | | | _______________________________________________ | vdr mailing list | vdr@linuxtv.org | http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Philippe Gramoullé a écrit :
Looks like you have permission issue for /dev/input/event0. Fix that first
Thanks,
Philippe
The problem is that /dev/input/event0 is created by udev whn the dvb driver is loaded.
How to do that ?
Add a chmod 666 /dev/input/event0 somewhere in the vdr stat script ?
Or something else (in vdr-rules) ?
But it does not impact the conditionnal access, it impacts only the remote control.
For now on, I am validating the box using SVDRP, it does not harm.
Thanks,
Pierre
On Sat, 2006-01-07 at 15:17 +0100, Pierre JUHEN wrote:
The problem is that /dev/input/event0 is created by udev whn the dvb driver is loaded.
How to do that ?
Add a chmod 666 /dev/input/event0 somewhere in the vdr stat script ?
Or something else (in vdr-rules) ?
If you're using the Livna rpm's, there's a commented out example how to do that for event2 in /etc/udev/rules.d/51-vdr.rules. Just change it to event0, uncomment it, and the device node should be created with VDR-friendly permissions after the next reboot. (Before the next reboot, you can try it out with "chgrp video /dev/input/event0".)
-
Christoph Haubrich -
Dominique Dumont -
Gregoire Favre -
Klaus Schmidinger -
Philippe Gramoullé -
Pierre JUHEN -
ssDominique Dumont
-
Thomas Bergwinkl -
Ville Skyttä