[vdr] vdr-plugin-dvbapi, howto connect to oscam?

cedric.dewijs at telfort.nl cedric.dewijs at telfort.nl
Tue Dec 24 17:30:47 CET 2013


Hi All,
I am trying to connect vdr-plugin-dvbapi to oscam. both programs are running on the D-link DNS-323 NAS. The NAS is running debian armel
https://github.com/manio/vdr-plugin-dvbapi
When I stream an encrypted channel into my browser, I see the following errors in /var/log/oscam/oscam.log
013/12/24 16:14:37  14F4DA8 c [DVBAPI] Receiver sends PMT command 3 for channel 001F
2013/12/24 16:14:37  14F4DA8 c [DVBAPI] Receiver wants to demux srvid 001F on adapter 0000 camask 0001 index 0000
2013/12/24 16:14:37  14F4DA8 c [ADD PID 0] CAID: 0B00 ECM_PID: 0BCB PROVID: 000000
2013/12/24 16:14:37  14F4DA8 c Found 1 ECMpids and 2 STREAMpids in PMT
2013/12/24 16:14:37  14F4DA8 c [DVBAPI] Receiver wants to demux srvid 001F on adapter 0000 camask 0001 index 0000
2013/12/24 16:14:37  14F4DA8 c New program number: 001F (0B00:001F unknown) [pmt_list_management 3]
2013/12/24 16:14:37  14F4DA8 c [DVBAPI] Demuxer #0 no suitable readers found that can be used for decoding!
2013/12/24 16:14:37  14F4DA8 c [DVBAPI] Demuxer #0 (re)starting decodingrequests on all 1 ecmpids!
2013/12/24 16:14:37  14F4DA8 c [DVBAPI] Demuxer #0 no suitable readers found that can be used for decoding!
2013/12/24 16:14:37  14F4DA8 c [DVBAPI] Demuxer #0 (re)starting decodingrequests on all 1 ecmpids!
2013/12/24 16:14:38  14F4DA8 c [DVBAPI] Demuxer #0 no suitable readers found that can be used for decoding!
2013/12/24 16:14:38  14F4DA8 c [DVBAPI] Demuxer #0 (re)starting decodingrequests on all 1 ecmpids!
2013/12/24 16:14:38  14F4DA8 c [DVBAPI] Demuxer #0 no suitable readers found that can be used for decoding!
2013/12/24 16:14:39  14F4DA8 c [DVBAPI] Demuxer #0 (re)starting decodingrequests on all 1 ecmpids!
2013/12/24 16:14:39  14F4DA8 c [DVBAPI] Demuxer #0 no suitable readers found that can be used for decoding!
2013/12/24 16:14:39  14F4DA8 c ERROR: Can't open device /dev/dvb/adapter0/ca0 (errno=2 No such file or directory
And in /var/log/syslog:
Dec 24 16:14:37 debian vdr: [14383] Streamdev: Accepted new client (HTTP) 192.168.31.112:58954
Dec 24 16:14:37 debian vdr: [14383] DVBAPI: 0.0 set CAM decrypt (SID 31, caLm 4, HasCaDescriptors 1)
Dec 24 16:14:37 debian vdr: [14808] streamdev-livestreaming thread started (pid=14370, tid=14808)
Dec 24 16:14:37 debian vdr: [14807] streamdev-writer thread started (pid=14370, tid=14807)
Dec 24 16:14:37 debian vdr: [14809] receiver on device 1 thread started (pid=14370, tid=14809)
Dec 24 16:14:37 debian vdr: [14810] TS buffer on device 1 thread started (pid=14370, tid=14810)
Dec 24 16:14:39 debian vdr: [14383] client (HTTP) 192.168.31.112:58954 has closed connection
Dec 24 16:14:39 debian vdr: [14383] streamdev-server: closing HTTP connection to 192.168.31.112:58954
Dec 24 16:14:39 debian vdr: [14808] streamdev-livestreaming thread ended (pid=14370, tid=14808)
Dec 24 16:14:39 debian vdr: [14383] DVBAPI: 0.0 set CAM decrypt (SID 31, caLm 5, HasCaDescriptors 1)
Dec 24 16:14:39 debian vdr: [14810] TS buffer on device 1 thread ended (pid=14370, tid=14810)
Dec 24 16:14:39 debian vdr: [14809] buffer stats: 0 (0%) used
Dec 24 16:14:39 debian vdr: [14809] receiver on device 1 thread ended (pid=14370, tid=14809)
Dec 24 16:14:39 debian vdr: [14807] streamdev-writer thread ended (pid=14370, tid=14807)
Dec 24 16:14:39 debian vdr: [14383] buffer stats: 0 (0%) used
When I start VDR, I see the following in /var/log/syslog:
Dec 24 16:08:51 debian vdr: [14370] VDR version 1.7.28 started
Dec 24 16:08:51 debian vdr: [14370] loading plugin: /usr/lib/vdr/plugins/libvdr-dvbapi.so.1.7.28
Dec 24 16:08:51 debian vdr: [14370] loading /var/lib/vdr/setup.conf
Dec 24 16:08:51 debian vdr: [14370] loading /var/lib/vdr/sources.conf
Dec 24 16:08:51 debian vdr: [14370] loading /var/lib/vdr/diseqc.conf
Dec 24 16:08:51 debian vdr: [14370] loading /var/lib/vdr/scr.conf
Dec 24 16:08:51 debian vdr: [14370] loading /var/lib/vdr/channels.conf
Dec 24 16:08:51 debian vdr: [14370] loading /var/lib/vdr/timers.conf
Dec 24 16:08:51 debian vdr: [14370] loading /var/lib/vdr/commands.conf
Dec 24 16:08:51 debian vdr: [14370] loading /var/lib/vdr/reccmds.conf
Dec 24 16:08:51 debian vdr: [14370] loading /var/lib/vdr/svdrphosts.conf
Dec 24 16:08:51 debian vdr: [14370] loading /var/lib/vdr/keymacros.conf
Dec 24 16:08:52 debian vdr: [14370] DVBAPI: Probe: capturing device 0/0 (subsystem ID 00000000)
Dec 24 16:08:52 debian vdr: [14370] DVBAPI: creating standard device 0/0
Dec 24 16:08:52 debian vdr: [14370] new device number 1
Dec 24 16:08:53 debian vdr: [14370] frontend 0/0 provides DVB-T with QPSK,QAM16,QAM64 ("DiBcom 7000PC")
Dec 24 16:08:53 debian vdr: [14370] DVBAPI: Using software decryption on card 0/0
Dec 24 16:08:53 debian vdr: [14370] DVBAPI: SCCIAdapter: built caid table with 1 caids for 65 channels
Dec 24 16:08:53 debian vdr: [14370] found 1 DVB device
Dec 24 16:08:53 debian vdr: [14380] SC-CI adapter on device 0 thread started (pid=14370, tid=14380)
Dec 24 16:08:53 debian vdr: [14370] initializing plugin: dvbapi (1.0.5): DVBAPI type SOFTCAM
Dec 24 16:08:53 debian vdr: [14370] DVBAPI: plugin version 1.0.5 initializing (VDR 1.7.28)
Dec 24 16:08:53 debian vdr: [14370] SVDRP listening on port 6419
Dec 24 16:08:53 debian vdr: [14370] starting plugin: dvbapi
Dec 24 16:08:53 debian vdr: [14370] DVBAPI: plugin started
Dec 24 16:08:53 debian vdr: [14370] DVBAPI: 0.0: doReply changed, reset triggered
Dec 24 16:08:53 debian vdr: [14370] DVBAPI: 0.0: now using CAIDs version 16843009
Dec 24 16:08:53 debian vdr: [14370] DVBAPI: 0.0: status 'present'
Dec 24 16:08:53 debian vdr: [14370] DVBAPI: 0.0: status 'reset'
Dec 24 16:08:54 debian vdr: [14370] DVBAPI: 0.0: status 'ready'
Dec 24 16:08:54 debian vdr: [14380] CAM 1: module ready
Dec 24 16:08:54 debian vdr: [14380] DVBAPI: CaInfo: 0.0 sending CA info
Dec 24 16:08:55 debian vdr: [14380] CAM 1: replies to QUERY - multi channel decryption possible
Dec 24 16:08:55 debian vdr: [14370] switching to channel 1
Dec 24 16:08:55 debian vdr: [14370] CAM 1: assigned to device 1
Dec 24 16:08:55 debian vdr: [14370] DVBAPI: Forcing transfermode on card 0/0
Dec 24 16:08:55 debian vdr: [14370] setting watchdog timer to 60 seconds
Dec 24 16:08:55 debian vdr: [14370] ERROR: no OSD provider available - using dummy OSD!
Dec 24 16:08:56 debian vdr: [14370] max. latency time 1 seconds
Dec 24 16:08:58 debian vdr: [14370] DVBAPI: Forcing transfermode on card 0/0
I have the following configuration:
cat /etc/oscam/oscam.conf
# main configuration
[global]
nice          = -1
WaitForCards  = 1
# logging
pidfile       = /var/run/oscam.pid
logfile       = /var/log/oscam/oscam.log
usrfile       = /var/log/oscam/oscamuser.log
cwlogdir      = /var/log/oscam/cw
# monitor
[monitor]
port          = 8988
aulow         = 120
monlevel      = 1
# protocols
[newcamd]
key            = 000102030405060708090A0B0C0D
port           = 15050 at 0B00:0E030
[dvbapi]
        enabled = 1
        au = 1
        boxtype = pc
        user = vdr
        pmt_mode = 4
        request_mode = 1
cat /etc/oscam/oscam.server
# reader configuration
[reader]
label    = reader1
protocol = mouse
detect   = CD
device   = /dev/ttyUSB0
group    = 1
emmcache = 1,3,2
services = services1
caid     = 0B00
mhz      = 500
cardmhz  = 500
cat /etc/oscam/oscam.services
# definition of services
#
# format:
# [name]
# caid=CAID[,CAID]...
# provid = provider ID[,provider ID]...
# srvid = service ID[,service ID]...
[services1]
caid=0B00
provid=0E030
srvid=
cat /etc/oscam/oscam.user
# user configuration
[account]
user       = user1
pwd        = password1
monlevel   = 0
uniq       = 0
group      = 1
au         = 1
ident      = 0B00:0E030
caid       = 0B00
# user for group 2 with monitor access, AU enabled
#[account]
user       = user2
pwd        = password2
monlevel   = 0
uniq       = 0
group      = 1
au         = 1
ident      = 0B00:0E030
caid       = 0B00
What could this be? A remote PC running VDR + vdr-plugin-sc can get the keys from the NAS without problems via the newcamd protocol.
Regards,
Cedric
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.linuxtv.org/pipermail/vdr/attachments/20131224/ad0122d0/attachment-0001.html>


More information about the vdr mailing list