Difference between revisions of "DVB-C USB Devices"

From LinuxTVWiki
Jump to: navigation, search
m (Supported DVB-C USB Devices)
(Supported DVB-C USB Devices)
Line 127: Line 127:
* 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 ([[http://www.spinics.net/lists/linux-media/msg37983.html]] [[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.
* Module dvb_usb_ttusb2 is needed.
* Works well with [https://www.lonelycoder.com/tvheadend/ Tvheadend]
* Works well with [https://www.lonelycoder.com/tvheadend/ Tvheadend]
|[[File:TT-connect CT-3650 CI.jpg|thumb|CT-3650 CI]]
|[[File:TT-connect CT-3650 CI.jpg|thumb|CT-3650 CI]]
|[[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/Irdto CAM.
* DVB-C supported ([[http://www.tbsdtv.com/products/tbs5680-dvb-c-tv-tuner-ci-usb.html]] [[http://www.spinics.net/lists/linux-media/msg36404.html]])
* CI supported from latest kernel ([http://www.tbsdtv.com/download/]])

Revision as of 08:43, 10 September 2012

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).

Components Connectors Comments Pictures

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 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.
NO Card reader http://liplianin.at.tut.by/ds110en.html [1]
QuatroStick nano (520e)
NO Card reader
  • Driver support seems to be available in kernel as of 2012/03/19 ([2] [3] [4])
  • "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 [[5]]

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)

CableStar USB / Cable4PC USB
TT-Connect C-1100 USB
  • dvb-ttusb-budget.ko
TT-Connect C-1200 USB
  • TechnoTrend USB IR also works
  • Support in lirc 0.8.2.
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 ([[6]] [[7]])
  • CI supported from kernel 3.2 ([8]])
  • Module dvb_usb_ttusb2 is needed.
  • Works well with Tvheadend
CT-3650 CI
  • CY7C68013
  • TDA10024 DVB-C demodulator
  • TDA18252
Common Interface (CI) - Tested successfully with latest kernel and Viaccess/Conax/Irdto CAM.
  • DVB-C supported ([[9]] [[10]])
  • CI supported from latest kernel ([11]])

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 developers' 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 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 garnering a response—a distinct byproduct of the fact that there are 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 hire someone who can.

Also See