Difference between revisions of "DVB-C USB Devices"

From LinuxTVWiki
Jump to: navigation, search
(Supported DVB-C USB Devices: Update current status of TechnoTrend TT-connect CT-3650 CI)
(20 intermediate revisions by 6 users not shown)
Line 9: Line 9:
 
<br>
 
<br>
  
If you are experiencing problems with USB devices, it may not be the fault of the tuner.  For example AMD 700 series chipsets (e.g. 780G) have a problem with USB ports which results in tuners working or partially working or not working at all. This can be solved by using a separate USB adapter with a reliable chipset (e.g. VIA 6212L, NEC).
+
If you are experiencing problems with USB devices, it may not be the fault of the tuner.  For example AMD 700 series chipsets (e.g. 780G) have a problem with USB ports which results in tuners working or partially working or not working at all. This can be solved by using a separate USB adapter with a reliable chipset (e.g. VIA 6212L, NEC). Otherwise a single USB2.0 port may not sustain two HD recordings; check with `lsusb -t` that two devices do not share the same Bus.
 
<br>
 
<br>
  
Line 50: Line 50:
 
|
 
|
 
|-
 
|-
|[[DVBWorld]]<br> [[DVBWorld DVB-C USB|DW3101]]
+
|[[Pinnacle|PCTV]]<br>[[PCTVSystems_QuatroStick-_510e|QuatroStick (510e)]]
 
|
 
|
* Philips CU1216 tuner
 
* [[NXP TDA1002x|NXP/Philips TDA10023HT]] demodulator
 
 
|NO Card reader
 
|NO Card reader
|http://liplianin.at.tut.by/ds110en.html
+
|Appears in Documentation_video4linux_CARDLIST.em28xx, so presumably supported.  
|[http://www.worlddvb.com/product/htm/usbc.htm]
+
|
 
+
 
|-
 
|-
|[[Sundtek]]<br> Sundtek MediaTV Pro
+
|[[Pinnacle|PCTV]]<br>[[PCTVSystems_QuatroStick-nano_520e|QuatroStick nano (520e)]]
 
|
 
|
* ?
+
*[[EMPIA_Technology|Empia]] [[Em28xx_devices|EM2884]]
|
+
*[[Micronas]] DRX 3926K demodulator
* ?
+
*[[NXP_Semiconductors|NXP]] TDA18271HDC2 tuner
|
+
|NO Card reader
* Opensource Kernelspace driver available for improving the datatransfer, but usually works without it and entirely in userspace (devicesetup is entirely done in Userspace). Drivers are proprietary but well supported. (since mid 2009)
+
|  
* Manufacturer provides [http://support.sundtek.de/index.php?topic=4.0 Driver] for Intel 32-bit, 64-bit, ARM (eabi4) and PowerPC(PlayStation 3 first Rev.), MIPS as far as website info goes (further architectures are available upon request). Driver claims support for AnalogTV, Composite, S-Video, VBI/Closed Caption, FM-Radio, DVB-T, DVB-C, Remote Control (keyboard emulation and lirc support)
+
*Driver support seems to be available in kernel as of 2012/03/19 ([http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=commit;h=c247d7b107c6654bb73d539485df649db5c0796f] [http://patchwork.linuxtv.org/patch/10404/] [http://www.mail-archive.com/linux-media@vger.kernel.org/msg38055.html])
|
+
*"Analog is not supported currently. Only DVB-T and DVB-C."
 
+
*"There seems to be still problems for locking DVB-C channels which have strong signal. Attenuator helps. I think it is demodulator IF/RF AGC issue. Lets fix it later. Patches are welcome."
 
+
Will not work out of the box yet (as of 2012/04/16). You will need to build the latest media drivers, and download the firmware file [[http://www11.zippyshare.com/v/17827014/file.html|dvb-demod-drxk-pctv.fw]]
 +
|[[File:Pctv_quatrostick_nano_520e.jpg|thumb|520e]]
 
|-
 
|-
 
|[[TechniSat]]<br> [[TechniSat CableStar USB / Cable4PC USB|CableStar USB / Cable4PC USB]]
 
|[[TechniSat]]<br> [[TechniSat CableStar USB / Cable4PC USB|CableStar USB / Cable4PC USB]]
Line 115: Line 113:
 
|  
 
|  
 
* DVB-C and DVB-T supported ([[http://www.spinics.net/lists/linux-media/msg18971.html]] [[http://www.spinics.net/lists/linux-media/msg36404.html]])
 
* DVB-C and DVB-T supported ([[http://www.spinics.net/lists/linux-media/msg18971.html]] [[http://www.spinics.net/lists/linux-media/msg36404.html]])
* CI supported from kernel 3.2 ([[https://lkml.org/lkml/2011/10/31/95]])
+
* CI supported from kernel 3.2 ([http://www.tbsdtv.com/download/]])
* Module dvb_usb_ttusb2 is needed, has the misleading name "Pinnacle 400e DVB-S USB2.0 support"
+
* Module dvb_usb_ttusb2 is needed.
 +
* Works well with [https://www.lonelycoder.com/tvheadend/ Tvheadend]
 +
|[[File:TT-connect CT-3650 CI.jpg|thumb|CT-3650 CI]]
 +
|}
 +
 
 +
== Supported by 3rd Party Drivers ==
 +
{{3rd_party_drivers}}
 +
 
 +
{| border=1 cellpadding=2 cellspacing=0 valign="top"
 +
|- bgcolor=#efefef valign="top"
 +
|'''Manufacturer<BR>Model'''
 +
|'''Components'''
 +
|'''Connectors'''
 +
|'''Comments'''
 +
|'''Pictures'''
 +
 
 +
|-
 +
|[[DVBSKY]]<br> [[DVBSKY_T680C|T680C]]
 +
|?
 +
|Common Interface
 +
|Needs v4l-dvb fork from dvbsky
 +
|[http://www.dvbsky.net/Products_T680C.html]
 +
|-
 +
|[[DVBWorld]]<br> [[DVBWorld DVB-C USB|DW3101]]
 
|
 
|
 +
* Philips CU1216 tuner
 +
* [[NXP TDA1002x|NXP/Philips TDA10023HT]] demodulator
 +
|NO Card reader
 +
|http://liplianin.at.tut.by/ds110en.html
 +
|[http://www.worlddvb.com/product/htm/usbc.htm]
 +
|-
 +
|[[Sundtek]]<br> Sundtek MediaTV Pro
 +
|
 +
* ?
 +
|
 +
* ?
 +
|
 +
* Opensource Kernelspace driver available for improving the datatransfer, but usually works without it and entirely in userspace (devicesetup is entirely done in Userspace). Drivers are proprietary but well supported. (since mid 2009)
 +
* Manufacturer provides [http://support.sundtek.de/index.php?topic=4.0 Driver] for Intel 32-bit, 64-bit, ARM (eabi4) and PowerPC(PlayStation 3 first Rev.), MIPS as far as website info goes (further architectures are available upon request). Driver claims support for AnalogTV, Composite, S-Video, VBI/Closed Caption, FM-Radio, DVB-T, DVB-C, Remote Control (keyboard emulation and lirc support)
 +
|
 +
|-
 +
|[[TBS]]<br> [[TBS5680 DVB-C TV Tuner CI USB|TBS5680 DVB-C TV Tuner CI USB]]
 +
|
 +
* CY7C68013
 +
* TDA10024 DVB-C demodulator
 +
* TDA18252
 +
 +
| Common Interface (CI) - Tested successfully with latest kernel and Viaccess/Conax/Irdeto CAM.
 +
 +
|
 +
* DVB-C supported ([[http://www.tbsdtv.com/products/tbs5680-dvb-c-tv-tuner-ci-usb.html]])
 +
* CI supported from latest kernel  ([http://www.tbsdtv.com/download/]])
 +
* Proprietary drivers replace the DVB drivers for other non-TBS devices with old ones
 +
 +
|
 +
 +
|-
 +
|[[TBS]]<br> [[TBS5880_USB_DVB-T2/T/C_CI_hybrid_TV_Box|5880 DVB-T2/T/C CI hybrid TV Box]]
 +
|
 +
* DNOT44QCH266A
 +
* CY7C68013
 +
 +
| Common Interface (CI)
 +
 +
|
 +
* DVB-C, DVB-T, DVB-T2 supported
 +
* CI supported from latest kernel  ([http://www.tbsdtv.com/download/]])
 +
* Proprietary drivers replace the DVB drivers for other non-TBS devices with old ones
  
 
|}
 
|}
Line 126: Line 190:
 
* Tongshi DVB-C USB [http://www.tongshi.com/cp_dvb_e.htm]  ... ''is this just a reference design?''
 
* Tongshi DVB-C USB [http://www.tongshi.com/cp_dvb_e.htm]  ... ''is this just a reference design?''
 
* [[TechniSat CableStar Combo HD CI]]
 
* [[TechniSat CableStar Combo HD CI]]
 +
* [[MSI DigiVox Trio]] (seems similar in hardware to PCTV Quatrostick nano 520e?)
  
 
==Also See==
 
==Also See==

Revision as of 22:30, 14 July 2013

On this page you will find information regarding DVB-C USB devices.

Please be aware that:
  • The information contained here is likely non-exhaustive and, despite best efforts to do otherwise, may contain errors. (Please help to keep these lists up-to-date so that they are useful for everyone!)
  • If your device is not listed, try:
    • searching the existing mailing list archives:
      • Linux-Media Mailing List (LMML) archives (via vger or .... )
      • or from the older mailing lists (now largely deprecated in favour of the LMML):
        • dvb mailing list archives (via spinics or MARC ... )
        • v4l mailing list archives (via .... )
    • searching for information with Google or other internet search engine
    • by posting a question about the device directly to the LMML (but please do conduct a search first, as it may already have been discussed!)
    • Note: when it comes to support, it is generally a good idea to try the current V4L-DVB sources because some device drivers can be very new and thus may have not made their way into the mainstream kernel.
In any regard, in respect to the above listed suggestions, you may find it to be the case that your device is actually already supported or that experimental support is available.
  • Because the component constitution on many devices are often similar or identical, there may be devices that are unlisted but may actually work with the existing driver framework for previously supported devices. In such a case, your non-listed but working device will likely be reported in your system messages as being one of those previously supported devices. If you encounter such an occurrence, please do report your success on the LMML so that proper detection/identification of your device can be added within the drivers.
  • Lastly, it bears worth repeating the request: Please help to keep these lists up-to-date so that they are useful for everyone!



Supported DVB-C USB Devices

The following table lists the confirmed working DVB-C USB device and provides a brief summary of their features and components. If you need more technical information on a device, have a look at its specific wiki article.

If you are experiencing problems with USB devices, it may not be the fault of the tuner. For example AMD 700 series chipsets (e.g. 780G) have a problem with USB ports which results in tuners working or partially working or not working at all. This can be solved by using a separate USB adapter with a reliable chipset (e.g. VIA 6212L, NEC). Otherwise a single USB2.0 port may not sustain two HD recordings; check with `lsusb -t` that two devices do not share the same Bus.


Manufacturer
Model
Components Connectors Comments Pictures


Anysee
E30C Plus
Card reader
  • dvb-usb-anysee.ko
  • Note: the newest version not yet supported by the driver, but the earlier three versions are. Would need help from someone with the newest device. At least in kernel 2.6.27 the card reader is not supported (empirical evidence and notes in the driver).
Anysee
Anysee E30 Combo Plus

Version 1

  •  ?

Version 2

  • DNOD44CDV086A tuner
  • TDA18212 demodultator
Card reader - not tested
  • dvb-usb-anysee.ko
  • USB device ID: 1c73:861f
  • This is a combined (Combo) DVB-T and DVB-C -device. The default mode is DVB-C. DVB-T -mode can be selected with a command "sudo modprobe dvb-usb-anysee delsys=1". Both modes seem to work.
  • Includes a remote control - only number and volume buttons work, so you still need another input method.
  • Note: The device comes in two versions, version 1 is supported from Linux kernel version 2.6.28 and version 2 is supported in Linux kernel version 3.0.0 (possibly earlier). Version 2 can be distinguished from version 1 by the loop antenna output which is absent on version 1.
PCTV
QuatroStick (510e)
NO Card reader Appears in Documentation_video4linux_CARDLIST.em28xx, so presumably supported.
PCTV
QuatroStick nano (520e)
NO Card reader
  • Driver support seems to be available in kernel as of 2012/03/19 ([1] [2] [3])
  • "Analog is not supported currently. Only DVB-T and DVB-C."
  • "There seems to be still problems for locking DVB-C channels which have strong signal. Attenuator helps. I think it is demodulator IF/RF AGC issue. Lets fix it later. Patches are welcome."

Will not work out of the box yet (as of 2012/04/16). You will need to build the latest media drivers, and download the firmware file [[4]]

520e
TechniSat
CableStar USB / Cable4PC USB
TechnoTrend
PCLine DVB-C USB
TechnoTrend
TT-Connect C-1100 USB
  • dvb-ttusb-budget.ko
TechnoTrend
TT-Connect C-1200 USB
  • TechnoTrend USB IR also works
  • Support in lirc 0.8.2.
TechnoTrend
TT-connect CT-3650 CI
  • Philips TDA8274 tuner
  • TDA10023 DVB-C demodulator
  • TDA10048 DVB-T demodulator
  • Cypress FX2
Common Interface (CI) - Tested successfully with kernel 3.2 and a Viaccess 4.0 DVB-T CAM.
  • DVB-C and DVB-T supported ([[5]] [[6]])
  • CI supported from kernel 3.2 ([7]])
  • Module dvb_usb_ttusb2 is needed.
  • Works well with Tvheadend
CT-3650 CI

Supported by 3rd Party Drivers

Sometimes a manufacturer forks v4l-dvb all on their own and writes a driver for their device so they can claim Linux support.

In-Kernel Drivers

Advantages:
1. It's possible your device will work.. for the moment.
2. If the manufacturer provides open source drivers with an acceptable license, volunteers could technically implement this code in the Linux kernel for true support. However.. :

Disadvantages:
1. The quality of the code (if open, there are also cases where you just get a binary blob) too often just isn't good enough and there's still too much work to be done to make the device work. There was probably a reason the manufacturer didn't just send their patches to the linux-media mailinglist.
2. Depending on what exactly the manufacturer did, you may have to reinstall the drivers every time your kernel is updated.
3. When the manufacturer stops updating the drivers, the drivers will quickly refuse to install as newer kernels are released.

In case a manufacturer provides open source drivers the patches can be sent to the linux-media mailinglist Linux-Media Mailing List (LMML). Keep in mind however that if the license isn't compatible with the Linux kernel or the quality of the code isn't good enough, these will not become a part of the Linux kernel.

Closed source userspace drivers (mostly Sundtek)

Advantages:
1. Same driver for nearly all Linux versions starting from 2.6.15 on.
2. No need to reinstall drivers when your kernel is updated.
3. Your device could work well.
4. Drivers can be profiled easily and more accurately than in kernelspace.
5. If the driver crashes, it won't crash the kernel. (so the system will stay uneffected).
6. If the manufacturer would stop to support the drivers, the userspace driver will still continue to work with newer Linux systems since the Kernelspace <-> Userspace interfaces are fixed and are not meant to be changed.
7. Application based drivers are modern since they use modern Linux interfaces (eg. stable Userspace USB Interfaces since 2006) which did not exist when legacy Kernel drivers were invented
Disadvantages:
1. You can't look into the sources. For end-users this is generally not a problem, but for programmers and people who like to hack their devices or are trying to fix bugs, it would be a disadvantage. If you just want to watch television, this does not concern you.

Examples: Currently relevant since Linux has an unstable USB 3.0 Kernel stack: Sundtek based tuners are used to debug general USB 3.0 Kernel issues, because the application based drivers themselves cannot crash the system. Such Kernel issues also affect legacy drivers but legacy drivers are able to trigger other problems (follow-up problems) by themselves which could be triggered due the faulty Linux USB 3.0 stack which makes debugging much harder.

Manufacturer
Model
Components Connectors Comments Pictures
DVBSKY
T680C
? Common Interface Needs v4l-dvb fork from dvbsky [8]
DVBWorld
DW3101
NO Card reader http://liplianin.at.tut.by/ds110en.html [9]
Sundtek
Sundtek MediaTV Pro
  •  ?
  •  ?
  • Opensource Kernelspace driver available for improving the datatransfer, but usually works without it and entirely in userspace (devicesetup is entirely done in Userspace). Drivers are proprietary but well supported. (since mid 2009)
  • Manufacturer provides Driver for Intel 32-bit, 64-bit, ARM (eabi4) and PowerPC(PlayStation 3 first Rev.), MIPS as far as website info goes (further architectures are available upon request). Driver claims support for AnalogTV, Composite, S-Video, VBI/Closed Caption, FM-Radio, DVB-T, DVB-C, Remote Control (keyboard emulation and lirc support)
TBS
TBS5680 DVB-C TV Tuner CI USB
  • CY7C68013
  • TDA10024 DVB-C demodulator
  • TDA18252
Common Interface (CI) - Tested successfully with latest kernel and Viaccess/Conax/Irdeto CAM.
  • DVB-C supported ([[10]])
  • CI supported from latest kernel ([11]])
  • Proprietary drivers replace the DVB drivers for other non-TBS devices with old ones
TBS
5880 DVB-T2/T/C CI hybrid TV Box
  • DNOT44QCH266A
  • CY7C68013
Common Interface (CI)
  • DVB-C, DVB-T, DVB-T2 supported
  • CI supported from latest kernel ([12]])
  • Proprietary drivers replace the DVB drivers for other non-TBS devices with old ones

Currently Unsupported DVB-C USB Devices

If you own one or more devices from the following list and you want to help with support development, please contact the Linux-Media Mailing List (LMML). Note that if your device is similar to or contains components for which driver development is currently being undertaken, then it is possible that you will pique the(se) developer's interest and can obtain some assistance that, possibly, leads to full support for your device.

However, please note that inquiries to the mailing list:

  • should NOT be treated as an order drop-off line/queue. You're soliciting help from volunteer developers who work on V4L-DVB matters in their spare time, and such work can be non-trivial (i.e. requiring even _thousands_ of hours work). So being demanding is one sure route to being ignored. (Honestly, this point really shouldn't even need to be written, but you'd be surprised at the number of irrational individuals who write into the mailing list demanding this or that).
  • may pass without even garnering a response -- that's a distinct by-product of the fact that there are only a limited number of developers, whom might be able to help, that are associated with the project. Often times, even if they wished to help, their energies are entirely tied up with other projects. In such cases, the best path might be to try to spearhead the driver development for your device yourself, or arrange to hire someone who can.

Also See