Difference between revisions of "TerraTec Cinergy DT USB XS Diversity"

From LinuxTVWiki
Jump to: navigation, search
(Add category info.)
(updated remote control section)
Line 30: Line 30:
  
  
=== Specific to the model ===
+
==== Specific to the model ====
 
[[Image:TerraTec_Cinergy_DT_USB_XS_Diversity-remote.jpg|thumb|50px|TerraTec-DT-USB-XS-Diversity-Remote]]
 
[[Image:TerraTec_Cinergy_DT_USB_XS_Diversity-remote.jpg|thumb|50px|TerraTec-DT-USB-XS-Diversity-Remote]]
 +
The remote is supported using the [http://www.linuxtv.org/pipermail/linux-dvb/2008-February/023844.html Key repeat for dib0700 IR receiver] patch. This patch has not made it into the tree, yet (see section '''Drivers''' above).
  
The remote does not seem to be supported right now, even if the IR-receiver is registered and all devices are set up correctly. There seems to be a problem with the toggle bit [http://www.linuxtv.org/pipermail/linux-dvb/2008-February/023507.html].
+
The dvb-usb-dib0700 module needs to be loaded with the option ''dvb_usb_dib0700_ir_proto=0'' to set the IR protocol to NEC (which is used by this device).
  
The dcb-usb-dib0700 module needs to be loaded with the option ''dvb_usb_dib0700_ir_proto=0'' to set the IR protocol to NEC.
+
 
 +
This refers (at least) to gentoo GNU/Linux:
  
 
To force loading the modul with this option create/edit the file /etc/modprobe.d/dvb and add the line
 
To force loading the modul with this option create/edit the file /etc/modprobe.d/dvb and add the line

Revision as of 22:40, 22 February 2008

TerraTec-DT-USB-XS-Diversity-Stick

A DVB-T USB device from TerraTec.

It is supported under Linux.

Overview/Features

features two tuners, and have two antennas. You'll have adapter0 and adapter1 in /dev/dvb, which you can use separately.

The "Diversity" option is a hardware based feature that allows for the device's two receivers to be configured in a combined use mode to achieve better reception on a single channel. The diversity feature of the DiBcom demodulators is currently not implemented in the Linux-DVB drivers, so only the dual tuner configuration is presently supported on such devices [1].

It seems that either this tuner stick does not have a very sensitive tuner, or the small antennas that come with it are simply insufficient for real-life use, unless one lives next door to a broadcast tower and has a direct line-of-sight to it. It is thus likely that an external antenna with a builtin amplifier is needed when this tuner is used.

Identification

This device's USB ID is 005a:0ccd.

(The device shown here is: Bus 001 Device 002: ID 0ccd:005a TerraTec Electronic GmbH, don't know if the ID has to be swapped to be read correctly, though)

Other Images


Making it Work (generic for all dib0700)

Firmware

August 21, 2008 - New firmware file fixing the last cause for i2c errors and disconnects and providing a new, more modular i2c request formatting.

You will need the dvb-usb-dib0700-1.20.fw firmware file in /lib/firmware or the relevant place for your distribution.

You may need to change the name of the file to dvb-usb-dib0700-1.10.fw or create a link until the driver code reflects that change.

For archival purposes: dvb-usb-dib0700-1.10.fw firmware file

August 29,2008 - Issues with Firmware 1.20. Some issues have been found with the latest version of the firmware. Users may wish to continue to use 1.10 unless they have patched their v4l-dvb code with dib0700_new_i2c_api.patch.

November 15,2008 - Issues with Firmware 1.20.

  • The above mentioned dib0700_new_12c_api.patch is not available discretely but is now rolled into the mercurial drivers
  • dvb-usb-dib0700-1.20.fw firmware file is now stable for reception, but remote control functionality is broken; any key press is repeated until the next key is pressed. The only way to get remote control functionality presently is to roll back to 1.10 firmware and suffer the occasional disconnect.
  • The mercurial drivers have been changed so they now load 1.20 firmware. To revert to 1.10 firmware you need to rename your firmware file to dvb-usb-dib0700-1.20.fw or provide a link of that name.
  • To avoid spurious remote control signals with 1.20 firmware, you need to edit /etc/modprobe.d/options or from Ubuntu onwards /etc/modprobe.d/options.confand add:
options dvb_usb disable-rc-polling=1

November 28,2008 - i2c errors. Changes were made to the remote control drivers on November 16,2008 to correct the repeat key problem. The card is generally stable for dual tuner reception and remote control function with Firmware 1.20.

November 10,2009 - mt2060 I2C write failed. Possible regression of a driver bug raised against Ubuntu running 2.6.27-14 and 2.6.31-2.17 causing mt2060 I2C errors in MythTV useage with firmware 1.20. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/397696 Recommend check the kernel extensions listed here for Low Noise Activation and rc_polling are loaded with correct config file name for your distribution, EIT listings information is turned off until a suitable delay (500ms-1000ms)is added to a single card (not both) and the card has correctly been added to the database as two tuners (no additional NULL entries) in the mythtv recordcard table.

Drivers

It requires the dib0700 driver. Just use Mercurial by following the How to Obtain, Build and Install V4L-DVB Device Drivers instructions.

Forcing the activation of LNAs (Low Noise Amplifier)

You may have to force LNA to get this card working:

In /etc/modprobe.d/options add:

options dvb_usb_dib0700 force_lna_activation=1

Disabling the remote control sensor

You may want to disable the remote control sensor if you are using another one and want to avoid error messages in the logs:

In /etc/modprobe.d/options add:

options dvb_usb disable_rc_polling=1

All relevant kernel modules options

In /etc/modprobe.d/options add:

options [module name] [option name]=[setting]

Get the parameters list using

modinfo [name of kernel module]

The debug values are bit fields, with each bit representing a different category. Add values to turn on multiple debugging categories.

dib3000mc
debug
Turn on debugging
Values: integer
Default: 0 (off)
buggy_sfn_workaround
Enable work-around for buggy SFNs
Values: integer
Default: 0 (disabled)
mt2060
debug
Turn on debugging
Values: integer
Default: 0 (off)
dvb_usb_dib0700
force_lna_activation
Force the activation of LNAs (Low Noise Amplifier), if applicable for the device
Values: integer
Default: 0 (automatic/off)
dvb_usb_dib0700_ir_proto
Set IR protocol
Values: integer 0=NEC, 1=RC5, 2=RC6
Default: 1
debug
Set debugging level
Values: integer (bitmap) 1=info, 2=fw, 4=fwdata, 8=data
Default: 0 (none)
dvb_usb
debug
Set debugging level
Values: integer (bitmap) 1=info, 2=xfer, 4=pll, 8=ts, 16=err, 32=rc, 64=fw, 128=mem, 256=uxfer
Default: 0 (none)
disable_rc_polling
Disable remote control polling
Values: integer
Default: 0 (enabled)
force_pid_filter_usage
Force all DVB USB devices to use a PID filter, if any
Values: integer
Default: 0 (disabled)
dvb_core
dvb_net_debug
Enable debug messages
Values: integer
Default: 0 (disabled)
frontend_debug
Turn on frontend core debugging
Values: integer
Default: 0 (off)
dvb_shutdown_timeout
Wait n seconds after close() before suspending hardware
Values: integer
Default: 0
dvb_force_auto_inversion
Set whether INVERSION_AUTO is forced on
Values: integer
Default: 0 (off)
dvb_override_tune_delay
Wait n milliseconds for lock after a tuning attempt
Values: integer
Default: 0
dvb_powerdown_on_sleep
Turn LNB power off on sleep
Values: integer
Default: 1 (enabled)
cam_debug
Enable verbose debug messages
Values: integer
Default: 0 (off)
debug
Turn on debugging
Values: integer
Default: 0
dvbdev_debug
Turn on device debugging
Values: integer
Default: 0 (off)
dibx000_common
debug
Turn on debugging
Values: integer
Default: 0 (off)

Remote control support

Using evdev

As long as the evdev module is loaded, a remote that is recogniced as hid device will be treated as a usb keyboard and this means that you can avoid using lirc.

However, many of the keys on your remote may generate keycodes which are not mapped to anything, by default.

In X you can use xev to find the keycodes and xmodmap to map them to useful symbols. Unfortunately, some keys may generate keycodes that X doesn't recognize at all and the device does not support keymaps, or this would be easy to fix.

Using LIRC

Usually remote controls in linux are managed by the lirc software collection.

To get lirc up and running you need to configure some things.

  • Settings for the hardware
    • Where does lirc get its input from? aka. the DEVICE. E.g. /dev/input/event3
    • How to handle the input? aka. the DRIVER. E.g. devinput
  • Settings for mapping driver output generated by your remote (a bunch of hex numbers) to key names (something like 0..9, Volume+, Next, Record)
  • Settings for mapping key presses to actions (usually located in your .lircrc)
Mythubuntu case

On mythubuntu 10.10, you just have to add this line in /etc/udev/rules.d/65-persistent-hauppauge.rules

SUBSYSTEM=="input", KERNEL=="event*", ATTRS{idVendor}=="2040", ATTRS{idProduct}=="8400", SYMLINK+="lirc0"
Device/driver settings

Find the IR receiver's device by looking in the dmesg output for a line similar to:

input: IR-receiver inside an USB DVB receiver as /class/input/input4

Additionally, the IR receiver will be listed if you execute the command:

cat /proc/bus/input/devices

For example:

I: Bus=0003 Vendor=2040 Product=9950 Version=0100
N: Name="IR-receiver inside an USB DVB receiver"
P: Phys=usb-0000:07:01.2-1/ir0
S: Sysfs=/class/input/input4
U: Uniq=
H: Handlers=kbd event4 
B: EV=3
B: KEY=14afc336 284284d00000000 0 480058000 219040000801 9e96c000000000 90020000000ffd

In this example, the remote control gives output into /dev/input/event4.

The event number depends on your particular system and can vary.

Eventually this event number can even vary at every reboot.

You could create a new udev rule in /etc/udev/rules.d/65-persistent-hauppauge.rules.

KERNEL=="event*", ATTRS{name}=="IR-receiver inside an USB DVB receiver", SYMLINK+="input/dvb-ir"

This would make IR receivers handled by the usb_dvb framework always always be linked to /dev/input/dvb-ir.

But Linux systems running recent udev will automatically create non-varying names, a nicer and automatic way of providing a stable input event name:

$ ls -la /dev/input/by-path/
total 0
drwxr-xr-x 2 root root 140 2008-02-07 20:31 .
drwxr-xr-x 4 root root 280 2008-02-07 20:31 ..
lrwxrwxrwx 1 root root   9 2008-02-07 20:31 pci-0000:00:1a.1-usb-0:2:1.0-event-kbd -> ../event1
lrwxrwxrwx 1 root root   9 2008-02-07 20:31 pci-0000:00:1a.1-usb-0:2:1.1-event-mouse -> ../event2
lrwxrwxrwx 1 root root   9 2008-02-07 20:31 pci-0000:00:1a.1-usb-0:2:1.1-mouse -> ../mouse1
lrwxrwxrwx 1 root root   9 2008-02-07 20:31 pci-4-1--event-ir -> ../event4
lrwxrwxrwx 1 root root   9 2008-02-07 20:31 platform-pcspkr-event-spkr -> ../event3

LIRC will use it without needing a special kernel module. use the dev/input (or devinput. Check this with the command "lircd --device=help".) driver and specify the input event device in /etc/lirc/hardware.conf

# /etc/lirc/hardware.conf
#
# Arguments which will be used when launching lircd
LIRCD_ARGS=""

#Don't start lircmd even if there seems to be a good config file
#START_LIRCMD=false

#Try to load appropriate kernel modules
LOAD_MODULES=true

# Run "lircd --driver=help" for a list of supported drivers.
DRIVER="dev/input"
# If DEVICE is set to /dev/lirc and devfs is in use /dev/lirc/0 will be
# automatically used instead
REMOTE_DEVICE="/dev/input/by-path/pci-4-1--event-ir"
MODULES=""

# Default configuration files for your hardware if any
LIRCD_CONF="/etc/lirc/lircd.conf"
LIRCMD_CONF=""

If you have REMOTE and TRANSMITTER sections in your hardware.conf file, they should look like this:

#Chosen Remote Control
REMOTE="Terratec Cinergy DT USB XS Diversity"
REMOTE_MODULES=""
REMOTE_DRIVER="devinput"
REMOTE_DEVICE="/dev/input/by-path/pci-1-5-event-ir"
REMOTE_LIRCD_CONF="/etc/lirc/lircd.conf"
REMOTE_LIRCD_ARGS=""
#Chosen IR Transmitter
TRANSMITTER="None"
TRANSMITTER_MODULES=""
TRANSMITTER_DRIVER=""
TRANSMITTER_DEVICE=""
TRANSMITTER_LIRCD_CONF=""
TRANSMITTER_LIRCD_ARGS=""
Remote key setup

See device specific section below or try [2].


Sample .lircrc

A sample .lircrc can be found LircrcExample here.

Keys repeated twice

But there is still the problem of the key repeats for it, so that each keypress will be repeated twice. The patches, as mentioned above, may not work, but a workaround is possilbe. It is described in http://ubuntuforums.org/showthread.php?p=4253678

Simply add config = echo " > /dev/null before the main config in .mythtv/lircrc or .lircrc

 begin
  prog = mythtv
  button = Mute
  config = echo " > /dev/null
  config = |
  ...
 end

So each 2nd keypress will be suppressed. This works in some application but not others (e.g. vlc).

Alternatively there is a patch for the kernel driver that solves it, it can be found here.

Finally if that doesn't work and you have the silver remote (A415-HPG-WE-A ) then changing the lircd.conf line as follows can prevent the duplicate key presses. This has the side-effect of disabling key repeats for the remote entirely. Change toggle_bit_mask 0x80000000 to toggle_bit_mask 0x00000000

Note: do not try to comment out (using #) any line in this file, or lirc won't work anymore.

Do NOT do this:

 #toggle_bit_mask 0x80000000
 toggle_bit_mask 0x00000000

Replace the original line instead.


Specific to the model

TerraTec-DT-USB-XS-Diversity-Remote

The remote is supported using the Key repeat for dib0700 IR receiver patch. This patch has not made it into the tree, yet (see section Drivers above).

The dvb-usb-dib0700 module needs to be loaded with the option dvb_usb_dib0700_ir_proto=0 to set the IR protocol to NEC (which is used by this device).


This refers (at least) to gentoo GNU/Linux:

To force loading the modul with this option create/edit the file /etc/modprobe.d/dvb and add the line

options dvb-usb-dib0700 dvb_usb_dib0700_ir_proto=0

Then run the command update-modules (as root) to rebuild the file /etc/modprobe.conf. This file is used by modprobe when loading modules.


Sample kernel output

From 2.6.23-tuxonice-r6 (gentoo) with drivers compiled from repository 11th Feb 08:

$ dmesg | grep -i dvb
dvb-usb: found a 'Terratec Cinergy DT XS Diversity' in cold state, will try to load a firmware
dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.fw'
dvb-usb: found a 'Terratec Cinergy DT XS Diversity' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (Terratec Cinergy DT XS Diversity)
DVB: registering frontend 0 (DiBcom 7000PC)...
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (Terratec Cinergy DT XS Diversity)
DVB: registering frontend 1 (DiBcom 7000PC)...
input: IR-receiver inside an USB DVB receiver as /class/input/input6
dvb-usb: schedule remote query interval to 150 msecs.
dvb-usb: Terratec Cinergy DT XS Diversity successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_dib0700


User experiences

Date: 22.8. 2007

Distro: Ubuntu Feisty, AMD64

Kernel: 2.6.20-16-generic

The drivers shipping with Feisty are not recent enough, so installed the current v4l-dvb distribution ([3]. It can be downloaded through Mercurial's web interface (see 'bz2' & 'gz'). Otherwise, you'd have to install & use Mercurial to fetch the source.

Downloaded the new dvb-usb-dib0700-03-pre1.fw firmware from [4] & copied it to /lib/firmware (if that does not work, flash the stick with the latest firmware from Terratec on a Windows PC).

After these steps, the stick works - I was able to find channels & get TV out of them.

Update: 19.11. 2007

Tuners using the dvb-usb-dib0700 module may be unable to tune to a particular channel multiplex while receiving others just fine. This appears to be a fairly common problem that is caused by some sort of amplifier setting not getting used when it should; look for lines with "filter timeout" when running 'scan', if you are missing all channels of a particular multiplex.

In short, if experiencing this problem, try setting the following (in /etc/modprobe.d/options or /etc/modules.conf):

dvb_usb_dib0700.force_lna_activation=1

After the module has been reloaded, you might be able to find and view the missing channels :-) You can check /sys/module/dvb_usb_dib0700/parameters/force_lna_activation on your system to make sure the parameter has been set.

Finally, this stick works just fine on 32-bit Ubuntu Gutsy as well.



(note: the following is likely dated by now)

openSUSE 10.2 (i586) Kernel 2.6.22.1-ccj51-default

Compiling the driver vv4.tgz from http://www.chez.com/treza/mt2266.htm

(on my system a netdevice.h was needed in /lib/modules/2.6.22.1-ccj51-default/build/include/linux)

Copying the firmware dvb-usb-dib0700-01.fw to /lib/firmware

Reboot, connect the stick, kaffeine, enjoy.

Update: 3.2.2008

Tuner works partially fine with Kernel 2.6.24-gentoo + xorg-server-1.4 + kaffeine 0.8.6 with xine-lib-1.1.10

In 2.6.24 (vanilla) kernel you need to load "mt2266" module manually. The "dvb_usb_dib0700" module is usually autoloaded when you put the stick in place. "mt2266" must be loaded first.

Unfortunatly the Diversity Mode (two tuners running as one for better receive) doesn't work. Furthermore the Windows receiver has a mucher better receive quality :-(. I.e. in Windows Im getting all 23(24) channels, in Linux only 19(20).

External links