TechnoTrend TT-connect CT-3650 CI: Difference between revisions

From LinuxTVWiki
Jump to navigation Jump to search
(→‎Driver support: Add CAM type)
mNo edit summary
Line 35: Line 35:
</pre>
</pre>


Beware that the initialization of the CAM in most cases will fail as seen above ("Invalid PC card inserted") due to the CAM being in sleep-mode. Once an application requests to use the CAM, it will wake up and get initialized automatically. The CI has been tested to work with a Viaccess 4.0 CAM and MythTV (v0.24 and v0.25). According to the developer of the driver, VDR is tested to work fine as well.
Beware that the initialization of the CAM in most cases will fail as seen above ("Invalid PC card inserted") due to the CAM being in sleep-mode. Once an application requests to use the CAM, it will wake up and get initialized automatically. The CI has been tested to work successfully with a DVB-T Viaccess 4.0 CAM and MythTV (v0.24 and v0.25). According to the developer of the driver, the CI should also work fine when using VDR for playback.


Many applications for DVB playback currently doesn't support the structure of the combined tuner, eg. with each tuner having their own frontend devices (/dev/dvb/adaptor0/frontend0 and /dev/dvb/adaptor0/frontend1) while the other devices are shared between the tuners (/dev/dvb/adaptor0/demux0 exists, but there's no demux1). In such cases it might be needed to make a workaround with hardlinks, as mentioned in [http://www.mail-archive.com/linux-media@vger.kernel.org/msg43015.html this mail on the linux-media list].
Many applications for DVB playback currently doesn't support the structure of the combined tuner, eg. with each tuner having their own frontend devices (/dev/dvb/adaptor0/frontend0 and /dev/dvb/adaptor0/frontend1) while the other devices are shared between the tuners (/dev/dvb/adaptor0/demux0 exists, but there's no demux1). In such cases it might be needed to make a workaround with hardlinks, as mentioned in [http://www.mail-archive.com/linux-media@vger.kernel.org/msg43015.html this mail on the linux-media list].

Revision as of 21:45, 14 February 2012

TT-connect CT-3650 CI.jpg

A combined DVB-C and DVB-T USB 2.0 device from TechnoTrend with integrated CI.

Overview/Features

TODO - See external product page link below.

Driver support

Both the DVB-C and DVB-T part of the tuner are supported in current kernels. As of kernel 3.2, the CI interface is now also supported and can be used to decrypt pay-TV with the use of a CAM.

Log from initialization on kernel 3.2.5:

[ 9528.631071] usb 2-1.1: new high-speed USB device number 5 using ehci_hcd
[ 9529.289469] IR NEC protocol handler initialized
[ 9529.293534] IR RC5(x) protocol handler initialized
[ 9529.296526] IR RC6 protocol handler initialized
[ 9529.298099] dvb-usb: found a 'Technotrend TT-connect CT-3650' in warm state.
[ 9529.298676] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 9529.298682] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 9529.298960] DVB: registering new adapter (Technotrend TT-connect CT-3650)
[ 9529.299433] IR JVC protocol handler initialized
[ 9529.302624] IR Sony protocol handler initialized
[ 9529.308074] IR MCE Keyboard/mouse protocol handler initialized
[ 9529.312022] lirc_dev: IR Remote Control driver registered, major 248 
[ 9529.313240] IR LIRC bridge handler initialized
[ 9529.315511] ttusb2: CI initialized.
[ 9529.315520] DVB: registering adapter 0 frontend 0 (Philips TDA10023 DVB-C)...
[ 9529.336842] DVB: registering adapter 0 frontend 1 (NXP TDA10048HN DVB-T)...
[ 9529.362972] Registered IR keymap rc-tt-1500
[ 9529.363171] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/rc/rc0/input15
[ 9529.363616] rc0: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/rc/rc0
[ 9529.363623] dvb-usb: schedule remote query interval to 150 msecs.
[ 9529.364156] dvb-usb: Technotrend TT-connect CT-3650 successfully initialized and connected.
[ 9529.364198] usbcore: registered new interface driver dvb_usb_ttusb2
[ 9536.512472] dvb_ca adapter 0: Invalid PC card inserted :(

Beware that the initialization of the CAM in most cases will fail as seen above ("Invalid PC card inserted") due to the CAM being in sleep-mode. Once an application requests to use the CAM, it will wake up and get initialized automatically. The CI has been tested to work successfully with a DVB-T Viaccess 4.0 CAM and MythTV (v0.24 and v0.25). According to the developer of the driver, the CI should also work fine when using VDR for playback.

Many applications for DVB playback currently doesn't support the structure of the combined tuner, eg. with each tuner having their own frontend devices (/dev/dvb/adaptor0/frontend0 and /dev/dvb/adaptor0/frontend1) while the other devices are shared between the tuners (/dev/dvb/adaptor0/demux0 exists, but there's no demux1). In such cases it might be needed to make a workaround with hardlinks, as mentioned in this mail on the linux-media list.

External Links